NTAC Peering Working Group

[Jeff Bartig <>]

NTAC,

Following up on my earlier email and discussions we had on recent NTAC and Peering & Routing WG calls, I now have some more details to share on the Microsoft peering changes.

I met with Microsoft at NANOG73 and finalized a plan for moving the existing R&E private interconnects to TR-CPS, adding additional private peering capacity, and eliminating most public peering.  These changes will upgrade us from the current 120G of private interconnect capacity to a new total of 220G.  The plan is to accomplish all of these changes over the coming month.  We are holding off on upgrading the capacity at Palo Alto, since there is a project underway to replace that PoP with a new PoP at Equinix-San Jose.  When the San Jose PoP is online, we will establish private peering with Microsoft at that location.

Let me know if you have any questions or concerns.

Jeff

Current R&E Microsoft interconnections:
Ashburn:  40G (2x2x10G)
Chicago:  40G (2x2x10G)
Los Angeles:  20G (2x1x10G)

Current TR-CPS Microsoft Interconnections:
Ashburn:  public peering
Chicago:  public peering
Dallas:  20G (2x1x10G)
Seattle:  public peering
Palo Alto:  public peering
Los Angeles:  public peering

Proposed end state:
Ashburn:  80G (2x4x10G)
New York:  20G (2x1x10G)
Chicago:  40G (2x2x10G)
Dallas:  40G (2x2x10G)
Seattle:  20G (2x1x10G)
Palo Alto:  public peering (keep until move to San Jose)
Los Angeles:  20G (2x1x10G)

Note:  2x4x10G indicates that Microsoft has 2 routers and we have a 4x10G LAG to each of those routers.  Even in cases where there is just a 10G interconnect, it is now common peering practice for that to be configured as a 1x10G LACP LAG to facilitate easier capacity augments in the future.


Jeff Bartig wrote on 5/15/18 11:46 AM:

NTAC Members,

Microsoft has had a long history of connectivity with Internet2.  Initially, Microsoft Research was an industry network participant and had connectivity to the R&E network dating back at least 15 years ago.  Microsoft currently peers with TR-CPS and for a brief period was a Net+ provider, establishing peering with the R&E network.  Microsoft's industry network participant and Net+ agreements both ended a while ago, but they maintained their peering with the R&E network/AS11537.  During recent meetings with Microsoft about peering capacity augments, this issue was discussed.

In the near future, I'll be working with Microsoft to decom the peering they have with Internet2's R&E network/AS11537.  Microsoft currently has private interconnects with AS11537 in Ashburn (4x10G), Chicago (4x10G), and Los Angeles (2x10G).  These 10 10G interconnects will be reconfigured to be used for peering between Microsoft and Internet2 TR-CPS (AS11164).  In addition, I am working with Microsoft on additional TR-CPS capacity augments, with a goal that the consolidated TR-CPS capacity with Microsoft will be much greater once these changes are completed.

The specific implementation details and timeline for these changes are being negotiated with Microsoft, but it will likely be implemented over the next 1-2 months.  I made a brief announcement of these changes at the NTAC monthly call 2 weeks ago.  The Peering/Routing WG will be meeting this afternoon, which will be another opportunity for discussion.  If you are not able to attend and have feedback or questions, please contact me, respond to this email, or use the NTAC slack channel.

Jeff

--
Jeff Bartig
Interconnection Architect
Internet2  AS11164 / AS11537
+1-608-616-9908

--
Jeff Bartig
Interconnection Architect
Internet2  AS11164 / AS11537
+1-608-616-9908