nanog mailing list archives

Re: Out of ideas - Comcast issue BGP peering with Tata

From: Gaurav Kansal via NANOG <nanog () nanog org>
Date: Wed, 22 Nov 2023 11:40:21 +0530

Hi friend,

Any idea how many segments are in routing table which are still not part of RIR holder ship ?

Regards,
Gaurav Kansal

On 22-Nov-2023, at 07:40, nanog () nanog org wrote:

Special note, deprecation of non-authoritative registries

Please note that 'route' and 'route6' objects created after 2023-Aug-15 in non-authoritative registries like RADB, 
NTTCOM, ALTDB won't be processed. It is recommended to create RPKI ROA objects instead. In rare cases if that's not 
possible, 'route' and 'route6' must be created in the authoritative registry - AfriNIC, APNIC, ARIN, LACNIC, RIPE, 
RIPE, NIC.br or IDNIC.


So basically, a giant #@*&$^ you to any legacy holders that aren’t paying an RIR.

Great!!

Thanks, Tata

Current thread:

Out of ideas - Comcast issue BGP peering with Tata Jamie Chetta via NANOG (Nov 17)
- Re: Out of ideas - Comcast issue BGP peering with Tata jim deleskie (Nov 17)
  - Re: Out of ideas - Comcast issue BGP peering with Tata Tom Beecher (Nov 17)
- Re: Out of ideas - Comcast issue BGP peering with Tata Mike Hammett (Nov 17)
  - Re: Out of ideas - Comcast issue BGP peering with Tata Diego Eduardo Zorrilla Fierro (diefierr) via NANOG (Nov 17)
    - Re: Out of ideas - Comcast issue BGP peering with Tata TJ Trout (Nov 17)
- Re: Out of ideas - Comcast issue BGP peering with Tata Lukas Tribus (Nov 17)
  - Re: Out of ideas - Comcast issue BGP peering with Tata owen--- via NANOG (Nov 21)
    - Re: Out of ideas - Comcast issue BGP peering with Tata Gaurav Kansal via NANOG (Nov 21)
    - Re: Out of ideas - Comcast issue BGP peering with Tata owen--- via NANOG (Nov 22)