NTAC Peering Working Group

["Brock, Anthony W" <>]

Notes from the 7/18 NTAC Peering & Routing SIG call:

 

1. Agenda Bash
2. Update on peering and I2PX

1. I2PX peers with Wasabi

                                                               i.      Upgraded Ashburn & LA (both connections) to 100g

                                                             ii.      Have a newer region in the Dallas area, so started a conversation for adding peering in this region

2. Working with CloudFlare

                                                               i.      WIP to add peering in 7 locations at 100g

                                                             ii.      Chicago is completed

                                                           iii.      Dallas is close

                                                           iv.      Waiting for cross connects at other locations

3. Fastly

                                                               i.      Working on 2 interconnections (moving 100g at NY & Dallas)

                                                             ii.      Expect to be completed in coming days

4. Zoom

                                                               i.      Historically been a NET+, so currently in the R&E table

                                                             ii.      Have 100g in New Jersey & San Jose

                                                           iii.      Have 3 10g in original data centers (NY, Denver, & SF area); now only used for VoIP service

                                                           iv.      Are turning down the original data centers

                                                             v.      Turning up new data centers in Santa Clara and in Ashburn

1. No current peering
2. Calls hosted out of these areas are likely to be routed over commodity Internet
3. Looking to establish connectivity at 100g
4. Ashburn should be straightforward
5. Santa Clara facility is more challenging

1. I2 is not currently present in the facility
2. I2 is at Lumen facility (roughly 0.5 miles away)
3. Another possibility is an Exchange located in SF & LA; Zoom might investigate upgrading their current peering from 10g to 100g
4. Zoom might also return to an Equinox San Jose facility in a year
5. Some options might require moving the routes from R&E table to I2PX

Network Weather Update – Trends and Coming Events

1. Still summer break, traffic has been low on I2PX
2. R&E tends to be consistent year-round

Internet2 Network Updates

1. Have been working on 400g upgrade for R&E peerings on the east coast

                                                               i.      Focused on MAN LAN (New York) & WIX (Virginia)

                                                             ii.      Currently QFX 10002

                                                           iii.      Will be replaced with Arista

                                                           iv.      Also working on Boston exchange for trans-Atlantic connectivity

                                                             v.      Working with Starlight and Pacific Wave on potential upgrades

2. Investigating some 400g options that might improve their ability to deploy and respond to needs

Other business

1. New Route Reports (Steve Wallace):

                                                               i.      There are new additions

                                                             ii.      Nobody has a “completely” clean report

                                                           iii.      Pay special attention to the AS path column

1. Column will be red is dropping because of peer lock (i.e., the path includes a major peering provider in the AS path)

                                                           iv.      Some technical debt from the NGI project; those routes are in yellow that need to be cleaned up

                                                             v.      Now correctly reporting AS sets; they now appear correctly (again)

                                                           vi.      Currently reject approximately 10% of received routes

                                                          vii.      2 common route policy issues (Jeff Bartig):

1. Not raising the preference of local routes
2. Networks not making use of BGP communities to flag the origin of a route (i.e., not restricting advertised routes to customer routes)

Call ended at 4:34 EDT