Skip to Content.
Sympa Menu

ntacpeering - Re: NTAC Peering call, 1/19/10, 4:00 EST

Subject: NTAC Peering Working Group

List archive

Re: NTAC Peering call, 1/19/10, 4:00 EST


Chronological Thread 
  • From: Jeff Bartig <>
  • To:
  • Subject: Re: NTAC Peering call, 1/19/10, 4:00 EST
  • Date: Tue, 19 Jan 2010 14:32:55 -0600

On Mon, Jan 18, 2010 at 08:51:44AM -0500, Linda Roos wrote:
> Hi,
>
> The NTAC call will be held on Tuesday, January 19, at 4:00 EST. Here
> are the call details:
>
> 734- 615- 7474 or 866- 411- 0013 access code 0133542

Peering WG,

The text included below is a DRAFT announcement from the TR/CPS
Consolidation Team about proposed sharing of routes between TR and
CPS. We would like feedback on the text either on the call today
or via e-mail if you are unable to attend. Sorry about the late
notice. The draft was just completed.

Jeff


------------------------------------------------------------
DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT DRAFT
------------------------------------------------------------

DRAFT Announcement of TR/CPS Peering
------------------------------------

As we've discussed before here in the Peering WG the TransitRail
and CPS services have been making headway toward integrating into
a combined service. The network footprints now have physical
interconnects built in 4 locations: Chicago, Los Angeles, Seattle,
and Virginia/Washington DC.

In the interim, these interconnects will allow the TR and CPS
networks to share routes to peers the other network does not have.
This will enhance the connectivity provided to both TransitRail and
CPS connectors. Once the consolidation agreements are in place,
these interconnects will shift purposes. When we consolidate into
a single layer 3 peering network, these interconnects can provide
the layer 2 path between Internet2 connectors and the peering
network.

In today's meeting we'd like to discuss the potential exchange of
these routes in the near-term and seek feedback.

For this proposed initial change a subset of TransitRail and CPS
peers will be exchanged to enhance the connectivity provided to
users of both services. The Peer Networks involved include the
following.

AS11164/TransitRail -> AS11537/CPS (~50k prefixes):
# Abovenet(AS6461)
# Charter(22212)
# ChinaTelecom(4134)
# Cogent(174)
# Comcast(7922)
# DaCom(3786)
# Earthlink(4355)
# Frontier(5650)
# IIJ (AS2497/Japan)
# Integra Telecom(7385)
# TWCable(7843)

AS11537/CPS -> AS11164/TransitRail (~2k prefixes initially):
# Rogers Communications(812)
# Partial Global Crossing (3549)


This initial set of routes should enable 1-4 Gbps of new traffic
volume and represent a relatively small percentage change(<10%) of
traffic received by a given regional/campus network via either
service. Engineers will monitor the sets of routes and adjust
appropriately to avoid congestion of peer-facing links. TransitRail
and CPS engineers may be broadening the sets of peers exchanged as
traffic levels allow. When those take place both TransitRail and
CPS customers will be made aware of any significant changes or
increases in routes.

Networks using these services will generally not need to make any
configuration changes, though any networks that have enacted prefix
limits on session with TransitRail or CPS may need to increase their
limits; suggested limits today would be 250k or higher. The
existing 6550x:<ASN> or 6500x:<ASN> BGP community controls will
continue to operate as expected on both networks.

If you would like to avoid this enhancement for your network please
tag 65500:11537 and 65000:11164 on your announcements toward
TransitRail or CPS respectfully and if desired filter routes with
the respective (11537 or 11164) in the as-path. This will allow you
to continue to take advantage of your directly homed service, but
your routes will not be passed on to the remote service.

The team working toward this is happy to capitalize on the opportunity
to enhance the service and connectivity for all TR & CPS users.





Archive powered by MHonArc 2.6.16.

Top of Page