NTAC Peering Working Group

["Schmiedt, Dan" <>]

   

1. Agenda Bash

1. No agenda bashing noted.

Update on peering and I2PX

1. Jeff has been busy with travel recently – CAIDA workshop and NANOG.

1. At NANOG – had opportunity to meet with several peers who are at 165 Halsey (replacing 111 8^th NTC).  Halsey is now online and a BGP Neighbor is up.

1. https://internet2.edu/internet2-adds-site-in-new-jersey-expanding-network-peering-capabilities/
2. Microsoft is currently out of ports. 
3. NYEX is happy to work but is migrating to anew platform and occupied for the next several weeks.
4. Peering forum – peering coordinators come together in a room.  Kind of like speed dating for peering.

1. Spoke to Disney peering.  Expanding to multiple locations across country.  Will turn up public peering to gauge traffic, and depending on load will likely move to private interconnects.  Positive response from community.  Also includes Hulu now.  Will likely include ESPN content in the future.  Plans to begin steaming live data in future, currently relying on 3^rd party CDNs.

At CAIDA workshop:

1. Active measurement content, BGP content. 
2. Updates from RouteViews.  Want to deprecate existing route servers and get folk to switch to new API (in beta). Do not yet have a “classic” CLI interface using this new API at this point, which seems to be what most network operators really want to use.

Jeff has been looking at IIJ Internet Yellow pages – graph database imports data from multiple BGP and DNS sources.  Graph visualization/query tool to look at data.

1. See: https://iyp.iijlab.net
2. I2 is interested in using this and providing data.

Last time Jeff noted that AWS peering in SEAT was upgraded to dual 100G and was looking to de-peer AWS on west coast.  Was premature on saying that, as one of the new 100Gs went down because of a bad optic on AWS end.  So, he did not decom the R&E peer but will be doing so early next week.

1. Will withdraw routes from AWS West in R&E table.  Those routes and others are in I2PX table, so dual-connected sites should still have equivalent connectivity.  Non-I2PX sites will see traffic re-route through paid transit routes.

E-Sports ASNs – anything new to report?  Nothing new at this point.  I2 sees much traffic through Valve at public exchanges.  Jeff will be looking to transition Valve to private interconnects.  Let Jeff know if there are other Esports networks that I2 should consider peering with.Bytedance traffic – did we see it come back?  Yes, later that week it came back on ByteDance CDN. 

1. See Kentik write-up: https://www.kentik.com/blog/tiktok-emerges-from-shutdown-without-bytedances-us-cdn/

List of E-Sports peering sites?  Dave F working on an updated list. Network Weather Update – Trends and Coming Events

1. Limelight and Edgecast (edgio) – those did finally go down and migrated to Akamai, who took over contracts from bankruptcy court.

Internet2 Network Updates

1. No significant changes noted. 
2. Converted netflow to IPFIX on all core routers.
3. Setting up IPv6 global mesh.

Campus border route policy best practices

1. No new updates.
2. Jeff interested in offering tutorials whenever/however needed.  Could be a virtual/online workshop.  Half-day was not enough time to get a hands-on component – would need a full day to add hands-on.
3. Noted good discussion in NTAC Slack on BGP Policy and communities.  Check it out if you missed it –  WiscNET and MERIT contributed some interesting material.

1. See: https://internet2.slack.com/archives/G57KBJ0JF/p1739542898552699

Community peering needs and issues

1. Nothing noted.

Any other business?

1. JoAnne – asked how important external DNS is to folks.  Quad9 approached her recently and was looking for places to put resolvers.

1. Most campus runs own DNS infrastructure.
2. Quad9 instances are at most NA exchange points, so these are already out there.
3. LinkOregon – noted that they run caching servers for smaller member organizations.  Closest Quad9 is in Seattle, nothing in Oregon.
4. KanREN has a Quad9 node.
5. Noted caution – if we look at this, be sure it is only done regionally.
6. Front Range GigaPOP recently deployed a Quad9 node in Denver.
7. Would need to think through Anycast policy.
8. Dave F is willing to discuss/engage but historically has not gotten much engagement from others on the anycast topic.
9. Discussion: https://datatracker.ietf.org/doc/html/draft-ietf-grow-anycast-community
10. For R&E: do not want to pref anycast – needs to fall to AS-PATH length as primary discriminator, as that is the point of anycast – you are trying to get topologically closest server. 
11. Dave F: GROW is Global Routing Operations Workgroup in IETF – where operation BGP practices are discussed.  Encourage participation if interested; low-noise group with good content.