Skip to Content.
Sympa Menu

ntacpeering - Notes from 12/19 NTAC Peering & Routing SIG call

Subject: NTAC Peering Working Group

List archive

Notes from 12/19 NTAC Peering & Routing SIG call


Chronological Thread 
  • From: "Schmiedt, Dan" <>
  • To: "" <>
  • Subject: Notes from 12/19 NTAC Peering & Routing SIG call
  • Date: Tue, 19 Dec 2023 21:45:21 +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=arcselector9901; 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=Q4vYcIWyveJa1kFu7pu/U485Z7LNbQRzGTq5SIDiDVA=; b=irJd58ryxmR+8QasjS+JWeQxw9/QnVNwW7n5cO351qQQD3OpM/wk1tom82WnJ61SELxlJLU0oxdhqq/NYTmA2rMn2IA6JWjt6LuBDecPvNcBC3ln6Zb1jqzglIQFt9cS8t0JqHHk/gqqmAovfJAQaQyGy2f2oEzQNpD0DCOLykQMk88xdk/kE3OFW0cKFqdDrLBK76lPqmAH39e6dSTmQurAI6Shtq4ADLLqWkwrVtNlObgEv3GmmxK+W1thuSQZT56XIDGJeoDBScGNV7HbamV96gwRNcuDRUuubtQCT1QRilX4zkqxRtcx1uR6Rd1bc+31TyAWQZpR5tvfhMASdQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cL8f5O7dzr116Uh14WaJA+zMZ9ix5/ygxcFIVODv+Gc362yrbE0tgQqQx60kWMlncOuM/jW3iid53DBzJ1S9kQV22AlgbQYgc2+TUAX4WUy7vwiyZvo61TWBIFOHtJ6geBZi7o+mjDVwR0wqKchn7cpdLNkLlVhDwkEKDifaNMyRjynJib0ohpeDk2UIvnwjBmjLXut5bu+GKzJe5W4YIi8Kew0Dq83Q5ma7yuv2cOiDCstA2yu9YunYdIKXxzlMpBW57aBwlkDOL/MSsHMJBDjtZMvDuloFGBLlhBP5HZeML6LwNwuQtMFf5/CD/9g8huARKFVC9keQCUKmlYIWdA==

 

  1. Agenda Bash
  1. Steve Wallace: Down to last week to open ticket with ARIN if they want to lock in lower fees.  220 orgs signed since February.  480 yet to sign.
Update on peering and I2PX
  1. Jeff Bartig: Planning for 2024:  there is renewed interest in removing remaining Net+ routes from R&E table and moving to I2PX.  Amazon is probably the biggest concern.
  1. Concern is that if these routes removed from R&E, what paths would affected orgs take to Amazon?  I2PX is sometimes not available to connector participants because of connector policies.
  2. Recognition that there will be breakage either way.  Jeff will be collecting data in order that we/I2 can make a more informed decision in the future.
  3. This will likely be a challenge for most of the first half of 2024.
  4. Discussion of blending I2PX and R&E tables on campus border routers.  Would a discussion of “how we do things” be helpful?
  5. Many campus routing policies are likely decades old.  Engineers may be scared to touch them and may not understand them
  6. Dave Farmer will try to put together some slides on how he handles border policy, and we will go over at next SIG call.
  7. Dan will remind the group prior to the next call so other orgs can be ready to highlight how they handle border policy.
  8. Aim would be to be able to do an “office hours” for members in the near future.
Network Weather Update – Trends and Coming Events
  1. Fortnite update was significant.
Internet2 Network Updates
  1. None noted.
Any other business?
  1. Farmer: noted that Cisco has found a bug in BGP code of IOSXR 7.9.2.  If refresh routes, default route lost tags and so was rejected by other routers.  Appears to be in mainline BGP code. 

 

 

 



  • Notes from 12/19 NTAC Peering & Routing SIG call, Schmiedt, Dan, 12/19/2023

Archive powered by MHonArc 2.6.24.

Top of Page