Skip to Content.
Sympa Menu

ntacpeering - NTAC Peering&Routing Re: Meeting tuesday 17th at 4:00

Subject: NTAC Peering Working Group

List archive

NTAC Peering&Routing Re: Meeting tuesday 17th at 4:00


Chronological Thread 
  • From: Darrell Newcomb <>
  • To:
  • Subject: NTAC Peering&Routing Re: Meeting tuesday 17th at 4:00
  • Date: Tue, 17 Jan 2012 12:50:24 -0800

Below are some points of reference or background on a few of today's agenda items:


On Jan 17, 2012, at 6:39 AM, Dale Finkelson wrote:
2. Update on recent circuit upgrades.

Of the fall-2011 projected and planned upgrades:

Additional capacity between exchange point routers and backbone/ aggregation devices in Chicago and Virginia areas were complete in early January. Two 10GE links in each city; are now providing the head-room needed to move forward the migration of participant connectors to the integrated network.

For reference the following URL shows links that are connecting exchange point sites together:
http://atlas.grnoc.iu.edu/atlas.cgi?map_name=Internet2%20TR-CPS

A southern cross-county link is pending in January as our Internet2 engineers continue to work toward that.

Additional capacity in the NY-Chicago-Virginia triangle was slated to be brought online via the BTOP optical transport. Of those One link between New York and Virginia was completed some weeks ago. Two Chicago - Virginia links had been recently set for completion last week, but is not yet online.

------

Exchange port upgrades pending:
-- One additional Ashburn Exchange port to be moved to integrated network on Jan. 20th.
-- Additional exchange point connections pending in: Ashburn, Chicago, and New York.


3. Update on TR-CPS migration, consolidation and implementation


4. TR/CPS Capacity monitoring Updates

https://routerproxy.grnoc.iu.edu/tr-cps/

http://atlas.grnoc.iu.edu/atlas.cgi?map_name=Internet2%20TR-CPS

Interface graphing (via SNAPP) had been pending tools alteration to support redacting specific peer facing interfaces. This is to adhere to expectations and mutual agreement by a handful of 3rd party networks, though that is the exception rather than the norm where generally interface usage should be visible. The software changes to support this are believed to be mostly sorted and will see NOC activity in the coming weeks.


5. BGP Community Tags

Following up on topic from past meetings about announcement control to/ from commercial networks attached to the R&E RIB and to affirm direction before NOC implements those improvements. The two items with broad support were noted as:

Per-ASN announcement controls (toward commerical non-members/ Net+ and other commerical):
• 65000:<ASN> Do not advertise at all to the peer ASN
• 65001:<ASN> Prepend once toward peer ASN
• 65002:<ASN> Prepend twice toward peer ASN
• 65003:<ASN> Prepend thrice toward peer ASN
• 65009:<ASN> Allow advertisement toward peer ASN if otherwise excluded by more general community control (e.g. 11537:2002)

Per commercial-network opt-out:
(existing) 11537:2002 - Block prefix to commercial R&E peers
Replicate the above for other commerical groups as they may arise (e.g. Net+)

http://noc.net.internet2.edu/i2network/maps-documentation/documentation/bgp-communities.html#BGP%20Community%20Controls%20for%20TR-CPS




  • Meeting tuesday 17th at 4:00, Dale Finkelson, 01/17/2012
    • NTAC Peering&Routing Re: Meeting tuesday 17th at 4:00, Darrell Newcomb, 01/17/2012

Archive powered by MHonArc 2.6.16.

Top of Page