PRIVATE IP +

 

Part I: Rates and Charges.

Part II: Service Description and Requirements.

Part III: Terms and Conditions.

Part IV: Service Level Agreement.

Part V: Definitions.

Schedule 1 – Customer Indian Affiliate/user Undertakings

 

Part I: Rates and Charges.

 

1.      Details.  Customer will pay the monthly recurring charges (“MRCs”) which are fixed for the Service Commitment, and non-recurring charges (“NRCs”) for Private IP + (“Private IP”) as specified below and in the applicable Service Order or Online Terms.  Customer will pay additional MRCs, which are fixed for the Service Commitment and NRCs for any optional features that may be applicable to the particular Private IP service and subscribed to in this Contract.

2.      Dynamic Bandwidth.  Dynamic Bandwidth will be charged in arrears based on actual Port bandwidth settings.  Dynamic Bandwidth will be provisioned and therefore invoiced at the bandwidth specified on the Contract unless otherwise changed by Customer.  

3.      Administrative Charges.  “Administrative” NRCs as specified below are applicable to Private IP.  The charges shown herein are quoted in United States dollars; actual charges will be billed in invoice currency.

 

                      

Part II: Service Description and Requirements.   

 

1.      Verizon offers two variations of this service: Private IP Layer 2 (“Private IP Layer 2 Service” or “Layer 2”) and Private IP Service (NOT ALL VARIATIONS ARE AVAILABLE IN ALL REGIONS; PLEASE CHECK WITH YOUR ACCOUNT MANAGER FOR AVAILABLE VARIATIONS.)

1.1.           General Private IP Layer 2.

1.1.1.      Private IP Layer 2 Service is only available under Contracts in the United States. Private IP Layer 2 Service provides point-to-point routing and allows Customer to retain control of routing and architectural and topology changes, which distinguishes Layer 2 Service from Private IP Service. Company provider edge switches are located in close proximity to each Customer Site and enable a Customer to retain routing control of data traffic. Private IP Layer 2 Service provides encapsulation of native Frame Relay and Multilink Frame Relay over a multi-protocol label switching transport infrastructure. Encapsulation is the inclusion of one data structure within another structure so that the first data structure is hidden during transportation across the IP Network.

1.1.2.      Customer must provide the equipment which is necessary to support the Private IP Layer 2 Service at Customer Sites and at local access connections.  Verizon can provide such equipment under a separate service attachment.

2.      General: Private IP.  Verizon Private IP and Private IP Gateway ("Private IP" or “PIP Service”) is a wide area data networking service providing any to any connectivity to transport Customer application data between Customer Sites.

3.      Private IP provides in respect of each Customer Site, the provision of dedicated Private IP Ports at an agreed bandwidth at the relevant Verizon Point of Presence (“PoP”).  Customer’s traffic is labelled as AF3 by Verizon unless Customer selects the Class of Service (“CoS”) option below in Section 5.9.

4.      Optional Feature for Private IP Layer 2.

4.1.           An optional feature of Private IP Layer 2 Service is the addition of one or more Private IP permanent visual circuits ("PVCs") which can be provisioned on Customer's Private IP Layer 2 port.  This enables the Customer's Private IP Layer 2 Service to communicate with Private IP sites and facilitates enhanced reporting features.  Sections 5.2, 5.4, 5.6, 5.7, 6.3 and 7.1 of this Part II Service Description and Requirements are not applicable to Layer 3 PVCs.  

4.2.           The PVC provides Customer with a Private IP connection with the features and functionality of Private IP as described in this Part II Service Description and Requirements.

4.3.           Customer must subscribe to PVC on a per port basis.

5.      Optional Features.  The Private IP comprises the following optional features (NOT ALL OPTIONS ARE AVAILABLE IN ALL REGIONS; PLEASE CHECK WITH YOUR ACCOUNT MANAGER FOR AVAILABLE OPTIONS).

5.1.           WAN Analysis, powered by Computer Associates (“CA”). WAN Analysis, powered by CA, is a web-based reporting tool for the Customer’s Private IP Network.  Private IP WAN Analysis, powered by CA, is not available for dedicated Customer Sites that are connected via MPLS VPN Interprovider Connections (“MVIC”).There are 4 reporting options available detailed below:

5.1.1        Provider Edge (“PE”) Statistics Reporting. PE Statistics Reporting provides performance information from the PIP network. PE Statistics data is polled nightly so data to the Verizon Enterprise Center will be delayed approximately 24-48 hours. PE Statistics also provides performance data between probes collocated with PE devices across the PIP network (PE–to-PE Response Path). At-a-Glance, Top-N, and Trend reports are available on PE elements. Provider Edge statistics will not be available via WAN Analysis for any Provider Edge devices that use the IPv6 protocol.

5.1.2        WAN Analysis Standard Select.

·        WAN Analysis Standard Select is a chargeable option for those Customers who have not chosen a CoS.   

·        This report option provides more detailed data for the performance of Customer Network components. On-Demand reporting allows the Customer to filter data based upon their requirements (day of week, a specific week, month of year, etc.) Other reports allow Customer to simulate load and bandwidth changes to existing network infrastructure.

5.1.3        WAN Analysis Enhanced Traffic Management (“ETM”) Reporting.  WAN Analysis ETM Reporting provides three additional types of scheduled device reports:

·        Customer Edge (“CE”) Response Path Reports. Allows reports of information such as latency for up to 10 response paths per Managed Device (a “Managed Device” being an item of Service Equipment that has been designated by Verizon as a device utilized by Customer that is connected to the Private IP).

·        CE Quality of Service (“QoS”) Performance.  Reports quality and performance of each differentiated services code point (i.e. DSCP) CoS on Managed Devices; and adds integrated QoS device support providing a consolidated view of all QoS on Managed Devices.  Reports available to be generated by Customer includes: At-a-Glance (quick view), Top-N (network-wide analysis), and Trend (detailed statistical) reports with PE elements.

·        CE Network Protocol Performance: Allows Customer to define and monitor up to 20 Customer Network protocols and provides a report detailing the traffic volume for each of the selected protocols on the Customer Network.

5.1.4     WAN Analysis Enhanced Traffic Management (“ETM”) Select Reporting.

5.1.4.1  WAN Analysis ETM Select Reporting includes all the features and reports of WAN Analysis ETM Reporting in addition to near real-time end user CE performance exceptions and alarms, near real-time trending capabilities and CE network status maps.  Customer may access scheduled and on-demand reports designed to help Customer with capacity analysis and reporting on their network infrastructure. Statistics provided include, but are not limited to, CE CPU, memory and Interface utilization, Interface errors, and Quality of Service (QoS) statistics by individual Class of Service (CoS) queue.  For devices with Cisco IOS Customer can obtain reports on Cisco IP SLA response paths and recognized applications using Network Based Application Recognition (NBAR).  Customer is further able to project a visual representation of their network with performance exceptions and performance related faults. Customer can also set up e-mail notification for their users to be notified by e-mail when certain exceptions occur on the network.

5.1.4.2  ETM Select Reporting offers optional configuration of traffic monitoring across an IP network known as “netflow”.  In order to select the additional netflow reporting, Verizon requires Customer to activate this feature on one interface per CE device.  Customer will be responsible for configuring Customer’s CE device with IP flow configuration, in order to receive netflow reports.  Only CE devices with IP flow configuration will receive netflow reporting.  Netflow reports identify performance problems by viewing which applications and hosts are consuming the most bandwidth, measuring enterprise-wide WAN utilization and identifying the applications, hosts, and conversations   consuming bandwidth.  Circuits with over 100 Mbps of bandwidth cannot be monitored by netflow.

5.1.4.3  Customer must designate a netflow Customer Product Administrator (NCPA), together with relevant contact details including e-mail address.  The NCPA will control who has access to the Customer’s netflow data.  Customer will be responsible for notifying Verizon of NCPA changes.

5.2.           Diversity and Router Diversity.  These optional features enable access to the Private IP Network under circumstances where primary access is unavailable.  Diversity features are subjected to availability and are available on a reasonable effort basis.  They are not guaranteed.  The term of such features is co-extensive with the term for Customer’s Private IP.

5.2.1.      Diversity Features.  The following diversity features are available.

·     Geographic Diversity automatically directs a second Customer circuit to a different Verizon gateway at a different Verizon PoP; and

·     Geographic Diversity automatically directs a second Customer circuit to a different Verizon gateway at a different Verizon PoP; and

·      Router Diversity automatically directs a second Customer circuit to a different Private IP switch or router.                        

5.2.2.      Availability.  Diversity features do not guarantee that Customer’s Private IP will be always available when the primary access is not available.  If Customer is ordering Router Diversity and the closest PoP has only one router, then Customer will be backhauled to the next closest Verizon Private IP router at an extra charge.  No Service Level Agreement is provided for Diversity.

5.3       Dynamic Bandwidth.  Dynamic Bandwidth offers the Customer the ability to dynamically manage its CAR and Private IP Port values through features (called the dynamic committed access rate (“DCAR”) and the dynamic bandwidth Private IP Port (“DPort”) on a web-based interface accessed through the Verizon Enterprise Center.  Dynamic Bandwidth changes to Private IP Port or CAR can be made once per 24 hour period.  These changes can be processed immediately or scheduled up to 365 days in advance.  Where changes are scheduled in advance, only one change may take effect in each 24 hour period.  Dynamic Bandwidth will be charged in arrears based on actual Port bandwidth settings.  Dynamic Bandwidth will be provisioned and therefore invoiced at the maximum bandwidth specified on the Contract unless otherwise changed by Customer.  Billing rate changes made through DPort or CAR will be applied based upon midnight Greenwich Mean Time. 

5.3.1     Dynamic Bandwidth currently offers the following options (subject to the restrictions below):

5.3.1.1     Dynamic Bandwidth Looking Glass lists all Customer Sites as well as all technical details, and includes any Customer Sites that may not have the Dynamic Bandwidth feature active.

5.3.1.2     DCAR enables Customer to change EF Realtime CAR values.

5.3.1.3     DPort enables Customer to upgrade or downgrade Private IP Port speed selections.

5.3.1.4     Dynamic Bandwidth Order Records includes Customer Site specific records of Private IP Port and CAR changes for the past 365 days or scheduled future orders up to 365 days.  Customers can subscribe for recurring reports which will be provided via e-mail.

5.3.2     Dynamic Bandwidth features are subject to the following restrictions:

5.3.2.1     The maximum bandwidth and Private IP Port speed available to the Customer is as stated in the Contract.

5.3.2.2     The DPort feature is only available on unchannelized Access circuits.

5.3.2.3     DPort is not available for use at Customer Sites using any indirect Access, DSL Access to Private IP, or any sites with NxT1, NXE1 or STM16 Access.

5.4       Private IP Port Only.  Cross connection charges apply to Private IP Port Only (“Port Only”) services.  Port Only services are available when Customer access is collocated in the same building as the Port Only capable IP hub.  Port Only services may be available when Customer is collocated within an adjacent building if agreed to by Verizon

5.5.      Private IP Gateway Ports.  Customer may request an interconnection between two Private IP networks and Verizon will create an interface between these two Private IP networks.  This interconnection gateway is a shared port designed to support multiple customers.  There are multiple gateways in place connecting the two Private IP networks and they operate in pairs.  Such gateways to the Private IP network are as follows: Secure Cloud interconnect gateway, private wireless gateway, satellite gateway, and the MVIC gateway which connects the Private IP network to a MPLS Partner’s network.

5.5.1     Secure Cloud Interconnect Service. In addition to the Private IP Service where Verizon maintains provider edge equipment, Private IP Service is available in select locations through arrangements with third party Cloud providers (“Secure Cloud Interconnect”) using an interconnection. Customer will receive invoices and customer support services from Verizon for the Secure Cloud Interconnect. Secure Cloud Interconnect has unique pricing and other partner-specific terms including, but not limited to, rules pertaining to the amount of AF traffic that is allowed. The Secure Cloud Interconnect Partner rate applies to the MPLS service to the Secure Cloud Interconnect Partner’s network.

5.5.2     Private Wireless Gateway. The Private IP Wireless Gateway is a shared port designed to support multiple customers.

5.5.3     Satellite Gateway. . Verizon can provide a satellite gateway port to receive Customer’s satellite traffic to the PIP Network. Each Customer individual Virtual LAN (“VLAN”) will be mapped to a Private IP PVC/CAR. Since multiple sites share a VLAN and PVC to the Private IP Network, the Private IP CAR must be sized according to Customer’s expected traffic and the total instantaneous traffic load that the satellite network can handle.  Customer understands that since remote satellite terminals are aggregated on a per customer basis using an individual VLAN per customer, when Customer adds, changes, or disconnects remote satellite terminals, the CAR may need to be reengineered to handle the new traffic load.

5.5.4     MVIC Service. In addition to the Private IP Service locations where Verizon maintains provider edge equipment, Private IP Service is available in select locations through arrangements with third party MPLS service providers (“MPLS Partners”) using MPLS VPN Interprovider Connection (MVIC).  MVIC connects the Verizon Private IP Network to an MPLS Partner’s MPLS networks.  Customer will receive all invoices and customer support services only from Verizon (in countries where Verizon is working with an MPLS Partner, in-country provision of any these services by Verizon is as authorized agent for the MPLS Partner or as a reseller).  MVIC for each MPLS Partner has unique pricing, and other MPLS Partner-specific terms including, but not limited to, rules pertaining to the amount of AF traffic that is allowed, or the number of Classes of Service available. The “MPLS Partner” rate applies to the MPLS service on the MPLS Partner’s network and a MVIC “Interconnect” rate applies to the MVIC connecting the Verizon Private IP Network to the MPLS Partner’s network.

5.6       Application Analysis and Application Priority.  Application Analysis and Application Priority are available through an amendment to the Contract.

5.7       IP Multicasting.  IP Multicasting permits Customer to simultaneously deliver a single stream of data to multiple recipients in multicast groups, which consist of Customer-designated frame relay or ATM Ports within its Private IP Network.  A monthly recurring charge per multicast group applies.

5.8       Multiple Virtual Routing and Forwarding (VRF).  Customer may create multiple virtual private network connections via a single Private IP port. Customer may use such connections to extend the privacy and security of the Private IP to the various LANs at Customer’s Site. Customer understands that packet drops may occur if Customer creates an oversubscription of virtual private network connections on the Private IP port and Verizon is not responsible for such packet drops. Customer may select port or private virtual connection (“PVC”) level queuing.

5.9       Where Customer chooses the Private IP CoS (Class of Service) Verizon offers different classes of service which follow the Internet Engineering Task Force (“IETF”) Differentiated Services (“Diff-Serv”) model: an Expedited Forwarding (“EF”) Committed Access Rate (“CAR”) at the agreed bandwidth at the relevant Verizon PoP.  Customer can choose the EF Realtime CAR value.  Customer can choose AF4, AF3, AF2, AF1, and BE priority classes by setting the corresponding Diff-Serv Code Point (“DSCP”).  The BE priority class is the default setting if no priority classes are set by Customer.  The provisioning of CoS within the CAR is as agreed in the Contract.

5.10      The reactive monitoring of the Private IP Network.

5.11      The allocation of the required Data Link Connection Identifier (DLCI) numbers.

6.      Customer Service and Support. Technical Support is available 24 hours a day 7 days a week via the local Verizon Customer Service Centers.  The telephone numbers of the appropriate Verizon Customer Service Center will be provided to Customer.

7.      Service Requirements.

7.1       Extranet Service.  Extranet Service permits Customer to connect with one or more other Customer-designated customers (“Extranet Users”) by creating secure extranet connections via a Verizon Private IP Network PVC to connect to another customer’s site on the Verizon Private IP Network.  To obtain Extranet Service, Customer and Extranet Users must execute an agreement for Private IP and a separate Private IP Extranet Agreement with Verizon.

7.2       Route Limits and IPv4 and IPv6 Protocols.  Customer may not introduce into the Private IP Network more routes than it has been assigned, based on the topology and number of sites in Customer’s network.  Verizon allows the following number of routes in Customer‘s Virtual Routing and Forwarding (VRF) table based upon the number of Customer Circuits in a given VPN.

 

 

            Additional maximum routes restrictions may apply for Customers using MVIC and such restrictions will be provided upon request.  Verizon reserves the right to apply a Charge in the event Customer exceeds the noted maximum routes per Customer Sites and Customer agrees to pay such Charge. Customer must select a suitable number of IP addresses to be used in conjunction with the Private IP and in accordance with Verizon’s then-current applicable assignment guidelines. Customer must select IPv4 protocol and/or IPv6 protocol. The IPv6 protocol may not be available in all areas.

7.3       Requested Implementation Date (“RID”).  Customer may request a RID for delivery of the Private IP.  Based on this request Verizon will determine the date of delivery which will be communicated to the Customer either by letter, fax, e-mail or verbally following acceptance of the Contract.  As regards upgrades of an existing circuit to Dynamic Bandwidth, such date of delivery will be the first business day of a calendar month.  A change to the RID may incur charges as set out in the Contract.

7.4       Scheduled Maintenance.  Scheduled maintenance on the Verizon Network will be performed during a standard maintenance window as notified to Customer from time to time.  Verizon reserves the right to change any notified maintenance times, where necessary, upon prior notice to the Customer.  Verizon also reserves the right to perform emergency maintenance without prior notice.

7.5       Bandwidth Shaping.  Verizon’s Private IP Network may require Verizon to provision 'bandwidth shaping' overhead adjustments on the Ethernet Interfaces at the PE egress and Customer may be required to apply policies at Customer's CE egress to prevent packet loss due to Ethernet protocol overhead used within the Private IP Network, which reduces the actual bandwidth available to Customer and is dependent on Customer's traffic profile.

7.6       DLCI Numbers.  Verizon will allocate the required Data Link Connection Identifier (DLCI) numbers for the Private IP network and communicate these to Customer.  Customer can submit its own DLCI numbers on the Contract and Verizon will, where reasonably possible, allocate those DLCI numbers to Customer.

7.7       Provisioning Entities in China.  Licensed local telecommunication suppliers will be used as Provisioning Entities for any portion(s) of the Private IPs not provided by Verizon or its Affiliates.  In China where Verizon is not licensed to provide any portion of the Private IP and such portion is provided by a licensed local telecommunication supplier, such portion of the Private IP will be part of a greater international network of Private IP provided by Verizon to the Customer.

7.8       Restriction on Selling Encryption Services in India.  Customer understands and acknowledges that in accordance with the licenses and with statutory guidelines which govern the provision of the Private IP by Verizon in India, Customer is not allowed to employ encryption on any equipment (including CPE and Customer Equipment) which is directly or indirectly connected to the Network in India without the required approvals.  Customer must ensure that any encryption equipment connected to the Network for specific requirements has the prior evaluation and approval of the Department of Telecommunications or authorities specially designated for the purpose. 

8.   Proactive Notification. Proactive notification is a feature that monitors the Network for service disruptions and informs Customer of circuit outages. Additional terms for proactive notification are available at: /business/service_guide/reg/cp_proactive_notification_feature.htm

 

Part III: Terms and Conditions.

 

1.      In addition to the Master Terms, the following service-specific terms and conditions apply:

1.1.           India Ports.  This clause applies if: (a) Customer is not an entity duly incorporated under Indian law, as amended from time to time; and (b) the Private IP contains a Port in India.  Customer will procure the signing by its Indian Affiliate/user receiving the Private IP in India of a document in the form set out in Schedule 1 hereto.

1.2.           WAN Analysis.  All reports and information provided by WAN Analysis are for Customer’s informational purposes only and may not form the basis for service level agreement claims.  Customer agrees that such reports are Verizon confidential information.

1.3.           VOIP Restrictions.  Customer acknowledges that a number of jurisdictions impose restrictions and/or licensing or registration conditions on VOIP transmission over the Network.  To the extent such regulations apply, Customer shall comply with those regulations and indemnify, defend, and hold Verizon harmless for any claims arising from Customer's violation of such regulations thereof.

1.4.           WAN Analysis Data Processing. By contracting for the provision of the Service, Customer acknowledges that any processing of Customer Data occurs exclusively at the direction and discretion of Customer, such direction and discretion exercised by entry into the Contract for receipt of the Private IP.

1.5.           Restriction on Selling Encryption Services in India.  Customer hereby indemnifies and hold harmless Verizon, from and against any claims, suits, judgments, settlements, losses, damages, expenses (including reasonable attorneys’ fees and expenses), and costs (including allocable costs of in-house counsel) asserted against or incurred by Verizon arising out of a failure by Customer to comply with the restrictions described in section above entitled “Restriction on Selling Encryption Services in India” or as otherwise imposed by the licenses or statutory guidelines from time to time.

 

Part IV: Service Level Agreement.

 

1.      The service level agreement (“SLA”) for Private IP 2013 may be found at the following URLs: 

 

Private IP Service Level Agreement for U.S. Services

Private IP Service Level Agreement for non-U.S. Services

 

 

Part V: Definitions.

 

1.      In addition to the Definitions, the following service-specific definitions apply:

 

 

 

Schedule 1 – Customer Indian Affiliate/user Undertakings

 

Please click here, for the Customer Indian Affiliate/user Undertakings for U.S. Services.

Please click here, for the Customer Indian Affiliate/user Undertakings for non-U.S. Services.