CPS FAQ

Any Internet2 Connector can connect to the Commercial Peering Service.    Additionally, Connectors can advertise any of their customer prefixes to the service, including prefixes that cannot routed on the Internet2 IP Network.

It's important to note that Connectors cannot route to each other through the Commercial Peering Service.   Connectors can only route to the peer networks through this service.   Connector to Connector connectivity must go through the regular Internet2 IP Network. 

It is easy for Internet2 Connectors to get connected to the Commercial Peering Service (CPS).    Simply call or email the Internet2 NOC and let them know you'd like to get connected to CPS.  An engineer will contact you to go over the steps to get connected and answer any questions you may have.

The engineer will ask you some questions about how your Commodity Internet (CI) connections are currently configured and how much CI bandwidth you currently use.    They will verify that your existing Internet2 connection can sustain your current  Internet2 traffic loads, the anticipated traffic loads of your CI bandwidth and any unused "overhead" bandwidth you'd like to maintain on your link.

If you do not already have 802.1q VLAN encapsulation (or Frame-Relay encapsulation) enabled on your connection, the engineer will schedule a time to add this to your link.

Once that's done, they will work with you to configure a second VLAN (or DLCI) and BGP session for CPS and schedule a time to turn-up the service.

You will need to provide the NOC with a list of BGP ASN's (or a reference to an IRR AS-SET Object ) that you will be advertising to the  Peering Service.

This is probably the most common question asked and is a difficult one to answer.

First, each Connector will have different traffic patterns, so just because one Connector reduces their CI load by 50% doesn't mean other Connectors will see the same thing.  

Second, Internet'2 Commercial Peering Service is still fairly new (started in October of 2006).    As Internet2 gets connected to additional exchange points and establishes new peerings relationships, the reductions in CI usage can increase dramatically.   In some cases, an single peer network can off-load as much as 10-15% of a Connector's overall CI usage.

In general, the current Internet2 CPS Connectors are seeing a 30-40% reduction in CI usage (as of April 11, 2007).

Internet2 CPS is free for Internet2 Connectors.

Internet2 CPS uses the same Autonomous System number as the  Internet2 IP network (AS11537) even though it is a completely separate routing domain.

Internet2 CPS is currently deployed as an MPLS Layer-3 VPN (aka VRF) on all of the Internet2 T640 routers.   This provides complete separation of routing from the Internet2 IP network (formerly known as Abilene).   

MPLS Layer-3 VPNs were chosen because they are standards-based and well-proven as well as simple and easy to deploy.   Using Juniper's Logical Routers features for the routing separation would have allowed the use of a different ASN, but there are currently software limitations (specifically the lack of Netflow data when using LRs) that prevented the use of this feature.    This choice will be evaluated again if/when Netflow is supported within Logical Routers.   

 

Internet2 introduces single AS11537 between the peers and its connectors. In areas where there is a regional network router used to connect to Internet2, but campuses have their own ISP connections, the AS of the regional network also needs to be considered. In general, adding 3 or 4 AS-PATH prepends to announcements to campus attached commodity providers will assure that inbound traffic prefers the peering service over other links.

Yes, absolutely.   Internet2 has implemented a set of BGP communities that, along with your own local BGP import policy, will allow you to control your traffic path to/from the Internet2 CPS peer networks.

If you do not want CPS peer network X to send traffic to you over Internet2 CPS, you can tag your prefixes with the BGP Community 65000:ABC  where "ABC" is the BGP ASN of peer network X.    If your BGP import policy is also set to reject Internet2's advertisements of routes from ASN "ABC", you will not send traffic to network X over Internet2 CPS either.

If you want traffic to/from peer network Y to be preferred through a different path, but want to use the Internet2 CPS path as a backup, you can tag your prefixes with 65001:XYZ, 65002:XYZ, or 65003:XYZ where "XYZ" is the BGP ASN of network Y.     These communities will cause Internet2 to pad the AS-PATH towards peer network Y 1, 2 or 3 times respectively (using AS11537 for the pad).    

All of these communities are specific to individual peer networks and do not affect routing to/from the other peer networks.   

The current participating Connectors are:

• Northern Crossroads (NOX)
• Indiana GigaPoP
• Oregon GigaPoP
• Great Plains Network (GPN)
• CIC (Iowa, UIUC, WiscNet, Northern Lights Gigapop)
• LONI (Louisiana Optical Networking Initiative)
• MERIT (Merit, OArnet)
• MREN
• University of South Florida (USF)/Florida Lambda Rail (FLR)
• MAGPI
• Utah Education Network (UEN, FRGP)
  
• University of Memphis
• Kentucky Regional Optical Network (KyRON)
• Three Rivers Optical Exchange (3ROX)
• North Carolina Research and Education Network (NCREN)

TR-CPS connectors should subscribe to the i2-tr-cps-ops-l list to receive operational information such as scheduled maintenance announcements, information on new peers and prefix counts, outage status, etc.

To subscribe, send a note to listserv@indiana.edu with "subscribe i2-tr-cps-ops-l" in the body, or contact the Internet2 Network NOC.

The list archive is accessible to subscribers only. Subscribers should register a listserv password for themselves, then they may logon, and view the archives. The email address used to register must match the email used to subscribe to the i2-tr-cps-ops-l list.