NTAC Peering Working Group

[Jeff Bartig <>]

Dan: Thank you for providing the detailed notes from the Peering and Routing SIG.

A minor correction is needed to Peering and Routing SIG minutes in the Community Peering and Needs section. Rather than “I2” in these bullets, it should say “KanREN”:

6. Community peering needs and issues
* No needs/issues noted.
* I2 has turned up full transit services with Zayo.
* Noted that they have been very easy to work with.
* Much of traffic that has flowed through Hurricane traffic is now taking this new path, which is fortuitous as I2 will be turning down HE peering in the future.

This update was from Brad at KanREN. KanREN recently turned up paid transit service with Zayo for the first time. Brad reported it was a good experience. KanREN is using Zayo to replace transit they historically had with Hurricane.

Internet2 I2PX peers with both Zayo/AS6461 and Hurricane/AS6939. For both of these peers, I2PX receives just their customer routes and only sends I2PX participant (customer) routes to them.

If you read the original (uncorrected) notes above and were excited about the possibility of full transit in I2PX solving some problem you have, please reach out to me. I’m interested in chatting about the problem you are trying to solve.

Jeff

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

On 17 Jun 2025, at 15:38, "Schmiedt, Dan" wrote:

    

1. Agenda Bash
   1. No bashing of the agenda was noted
2. Update on peering and I2PX
   1. Jeff was at NANOG in Denver last week.  Good conversations with carriers. 
      1. Presentation by Google on changes they have been making to peering.  Slides publicly available.  Expect recording to be available soon.
      2. Slides: https://storage.googleapis.com/site-media-prod/meetings/NANOG94/5452/20250609_Schwartz_Inside_Google_Peering__v1.pdf
      3. Summary: Evolution of Google’s approach to peering. 
      4. Early Google network with growth of Youtube, etc – focused on open peering with anyone anywhere with goad to avoid transit costs to carry then-new traffic volumes. 
      5. More recently, with growth of public exchanges, etc, Google wanted more control over their traffic – seeing downstream congestion that was impacting customer traffic.  Very hard to predict how traffic might flow. 
      6. Changes:
         1. Google stopped peering with all route servers. 
         2. Stopped peering with remote exchanges. 
         3. Most recently: no new public peers anywhere. 
         4. Existing peerings remaining in place for now and are focusing on PNI’s moving forward. 
         5. 10G PNI’s deprecated.  New ones must be at least 100G and must have >10G google traffic. 
         6. Must be be at least dual 100G connectivity. 
         7. Discouraging peering with smaller networks, customer networks. 
         8. New: verified peering partner program.  Providers can get silver or gold certification. 
         9. Google then points to those providers as places to get got transit with Google. 
         10. I2 meets requirements for “Gold” certification; paperwork passed on to I2 legal to determine legal feasibility. 
      7. Also met with Google peering coordinator to discuss pending requests like 111 8^th ave NYC.  Now have a plan on how to proceed. 
         1. Preference was to us 400G but google is short on 400G there – so will be dual 100G LAG pairs.
         2. Any location today at 100G moving to 2x 100G LAGs.  10G interfaces moving to 100G.
      8.  Also met with Disney streaming.
         1. New Peering coordinator interested in peering with I2 but his leadership needs traffic stats and traffic does not flow through I2 ASes without peering. 
         2. Will be turning up initial peering to show justification.
3. Network Weather Update – Trends and Coming Events
   1. It is summertime, low campus traffic observed.
4. Internet2 Network Updates
   1. New router installed in Baton Rouge, previously an optical only node. Came from request form LONI.
   2. Swapped out 8202 in LOSA core POP for NCS 57D2 to get per-VLAN shaping as required by cloud providers. Working to turn up capacity with cloud providers.
      1. https://www.cisco.com/c/en/us/products/collateral/routers/network-convergence-system-5500-series/ncs-57d2-18dd-fixed-chassis-ds.html
5. Campus border route policy best practices
   1. No new information.
   2. Jeff submitted proposal for route policy workshop at TechX.
   3. Dave Farmer – working on anycast peering best practices.  Jeff was able to provide some useful comparison data to Dave.
6. Community peering needs and issues
   1. No needs/issues noted.
   2. I2 has turned up full transit services with Zayo.
   3. Noted that they have been very easy to work with. 
   4. Much of traffic that has flowed through Hurricane traffic is now taking this new path, which is fortuitous as I2 will be turning down HE peering in the future.
7. Any other business?
   1. No other business was noted. 
8. Adjourn at 4:26 EDT