Skip to Content.
Sympa Menu

ntacpeering - Notes from 7/16 NTAC Peering & Routing call

Subject: NTAC Peering Working Group

List archive

Notes from 7/16 NTAC Peering & Routing call


Chronological Thread 
  • From: "Schmiedt, Dan" <>
  • To: "" <>
  • Subject: Notes from 7/16 NTAC Peering & Routing call
  • Date: Tue, 16 Jul 2024 20:55:27 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=tamu.edu; dmarc=pass action=none header.from=tamu.edu; dkim=pass header.d=tamu.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=ifQGG0CL7GTfBpIJerwx/HOgjLIcIwGTy/vykIWmjo4=; b=Tnf8Pz1MOR4qnA8aNCyRXY4PabEpt+XIqmFI6awAwTd4nALGYdW7rNxog+pSmNF8vHN6uH4/RkZFnPw9CvOTo9wTUplhGp8t9RUD4WRVwM9p1VvRsrvAJxWzvF/ocVrCy3Bkl0ZzrztZfGIjYMsubiSyvDbnstKjjukIsDuLD+w73hqX5TpzAA1PyvvnexsRk5TPrlPSf7Bjb9B1MyEmvm8feubER0QriBfZH6JExu0FTUNajTa8uzEgrWqBWgKZDLJN6PE/4MTQbY7Oc9G/vXsKxFf2GSAslR3ZksWTjmuLQz9XIpH1LsZJA41CxxCe48a8S4R24l9Eqy2Dpkqjxw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=iuNIUIZqRRGIvrDoFKNyrPEFj6gEGNctiyFWLZMKeLbBzrJPD25sTLABk/D/26aJThioVMDgegMXydzOo09//85Cu0Majt+Xy1+VkcmHP5D16ubyNZGGFXaf08LF/b2jS7Vk4Sp3DF60R5b+74qcXnqEdHcs69iO94KZB9CgiBKDcOcnzfRUsd1vYdpdrau7t7708s3ocGmixEuG3p5zStEeQn19kifB4q3OgVFsQC5XNDFdwLKFOF4YjsuP5neAJA501fjFdNHAHXCKTibHTAbVAcsHkX1eToueIlDMg5yqqf7xaiRoPbfCI/5F678vYGRha7pMvNv9hhkSVzc5rg==

  1. Agenda Bash
  1. Jeff B- consolidation of Net+ peers into I2PX
Update on peering and I2PX
  1. Fairly quiet this summer – making sure some capacity augments are in place before fall semester start. Specifically:

                                                              i.      Google, in several locations, dealing with them having pulled out of locations like MICE, and out of route servers.  Google has moved out of many public exchanges and prefers PNIs.

                                                            ii.      Amazon, related to moving peering to I2PX.

  1. Net+ cloud providers that have peerings in R&E table.  After 2018, all went in I2PX.  Targeting mid-August for completion.  Two largest are Amazon and DropBox.  Also Crashplan, Zoom VoIP, ServiceNow. 

                                                              i.      Concern: if networks are following BCP of localprefing I2 routes, routes will change for those providers, potentially putting large volumes on commodity links.  Can provide connectivity to Amazon outside of region.  Discussion on local peering vs I2PX, eg TX and MN.

  1. Farmer:  see worthwhile article on CDNs:

                                                              i.      https://www.streamingmediablog.com/2024/07/cdn-market-size.html

  1. Steve Schallehn: What is best list of I2 community strings?

                                                              i.      https://docs.globalnoc.iu.edu/i2network/maps-documentation/documentation/bgp-communities.html

  1. Update on Cloudflare: peering in 3 or 4 metros, others in progress.
  2. Please let Jeff know if any concerns on consolidation efforts.
Network Weather Update – Trends and Coming Events
  1. Semester starts in about a month.
Internet2 Network Updates
  1. R&E peering perspective: now have in production 400G from Boston to Paris.  Replacing 100G from DC to London; all traffic migrated.
  2. All Peering exchange locations: MANLAN, WIX, Boston are all 400G capable Arista switches (7280R3’s)  that replace the Juniper 10K2’s. https://www.arista.com/assets/data/pdf/Datasheets/7280R3-Data-Sheet.pdf
  3. NA-REX providing lit services to connect those 3 with other R&E exchanges in US.  Goal to have ready for Supercomputing this fall.
  4. Engineering team worked on config change son routed network.  Route Distinguisher had been made up of router loopback IP + VRF ID.  Now using RD of AS+unique Identifier.  Basically, a per-VRF identifier.  Will help with new netflow analysis tools.
Campus border route policy best practices
  1. Jeff submitted tutorial proposal for TechX – was accepted for half-day timeslot.  Looking for input or suggestions on content, ways to make it more hands-on.  Could likely use help/hands in the room from this working group. Will solidify plans as we get closer to TechX.
  2. Jeff has been working with Steve Wallace and network researcher at CAIDA to look at R&E routing.  Using SCAMPER – allows researcher to generate network traffic.  Utilizes a host with two interfaces – one connects to R&E and another to a VRF with transit routes.  One interface has pre-pends.  Ping an R&E site and SCAMPER can see which interface echo-reply comes from.  Shows whether a university is localpref’ing I2 or not and thereby using commodity path to reach another R&E institution.
Any other business?
  1. None.
Adjourn at 3:50ish

 

 



  • Notes from 7/16 NTAC Peering & Routing call, Schmiedt, Dan, 07/16/2024

Archive powered by MHonArc 2.6.24.

Top of Page