ntacpeering - Notes from 8/20 NTAC Peering & Routing Call
Subject: NTAC Peering Working Group
List archive
- From: "Brock, Anthony W" <>
- To: "" <>
- Subject: Notes from 8/20 NTAC Peering & Routing Call
- Date: Tue, 20 Aug 2024 21:01:20 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=oregonstate.edu; dmarc=pass action=none header.from=oregonstate.edu; dkim=pass header.d=oregonstate.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=rSwpHZuoibuGPfjZMGpXd2W3vbIDfwMb5fwTy8/p1o8=; b=hwy8/2f63kA+Y0lG5hJxruc2RsZ+d43C2tppfC2S3RAUuYiofKzU6YwQHSr7UlJRA0U8U9N/EhYRuh9iIFXkNeJWBelC2oRfRgl1130Dr6GgqKI/C5IjSqFil4ee0TII3Nzfxplq5YYqRO11m4UhxyyCICcBa+9osTZHq6JS2UWi06mbcJnpjIeBUqXWOvsCu5TLLuT2Cuc7RyOQVqBPsue/qqZtNPTgj/lEheW1BCrTQOMwXXnkMRzhAPMGSnvcsmwPwyPPkahFMucCnWj29hjikzViohpOdJIChl1ysNjv1gWsPBPjC2HdBYt9guLaqf+YL5FGRwP+fRd5jbByGA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=DAjFc4GnGdEVJ8FGiAAYvhzeJyGX/63oZnRQrEAZMDG9lwvvjrwJYoKBV7J/VLrrJo2bUQnCjlodVB4PPykJULCuNiah+Hfma8a37ZztPq4WKeV7WmufQxz1/Dc+mMiltA1QMTOIJLxGz7u8Bekcbvu62qjbtAEh5eeUufBPdRIYtebU6WG5gEbc7IG8e80h4JsI0sSNrS7ZJfpRHM8mgMol4W301sAkpRiDNBZVG2KdRm1s3yXhlHhBcoeAJ2k0/wQRljA/5K1DVwaomGnFv6RAlBxcvdPAasGdCXaduC3BYKGqk4ZiPsrjOsakES6p0SDi2mKMseSuJMgTxXTM8w==
i. Continuing work on capacity augments ii. Continuing consolidation of NET+ into I2PX routing table; hope to complete this month
i. Yesterday evening one of the international NRENs (in the middle-east) has started advertising I2's R&E routes to their upstream transit provider ii. Campuses started encountered difficulties with Microsoft and Google related services; most of these issues appear to be related to the campus advertising more specific routes to I2 than to their commodity providers. However it may have impacted campuses where their AS path was shorter when routed through this NREN iii. Performance issue was due to high latency and low bandwidth (1g) on the impacted link to the NREN iv. Impact from the issue was resolved by shutting down the peering once v. I2 is looking for ways to detect and prevent this type of issue, but solutions are challenging vi. Campuses and regionals should investigate solutions such as BGP Alerter that might help them diagnose and resolve future issues
i. Currently adjusting to recent I2PX changes; merging I2PX & R&E tables
i. In July a connected network saw some of their IP space being announced overseas ii. Mitigated most of the issue by creating a ROA (they had the appropriate agreement with ARIN); some issues continued with parts (but not all) of Google's network iii. Issue lasted for weeks iv. Currently 800 organizations connected to I2 have appropriate agreements but lack the ROA
|
- Notes from 8/20 NTAC Peering & Routing Call, Brock, Anthony W, 08/20/2024
Archive powered by MHonArc 2.6.24.