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

[owen--- via NANOG <nanog () nanog org>]

Depends on your definition of “RIR holder ship”.

ALL (legitimate) prefixes are delegated/registered by an RIR at some level.

However, some of them are non-contract and/or non-paid. APNIC is, I believe, the only RIR that eliminated all 
non-contract registrants. I’m not sure of the exact situation in LACNIC or AFRINIC, but I believe it is generally the 
same as RIPE and ARIN. Non-contract (for lack of a better term) prefixes cannot get IRR or RPKI services from their 
RIRs, and usually don’t come with membership (voting rights). Otherwise, they are basically treated the same as other 
registrations, though they also don’t pay fees.

Owen


> On Nov 21, 2023, at 22:10, Gaurav Kansal <gaurav.kansal () nic in> wrote:
>
> 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