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

[Lukas Tribus <lukas () ltri eu>]

On Fri, 17 Nov 2023 at 15:17, Jamie Chetta via NANOG <nanog () nanog org> wrote:
> I am out of ideas on how to get this fixed.  Long story short I am a customer of Comcast and am advertising my own 
> /24 block I own through them.  Comcast of course BGP peers with multiple ISPs.  Other ISPs are accepting my prefix 
> just fine, except Tata.

Why don't you share the exact prefix so people can actually look into it?

Tata is doing some strict filtering [1] at least for customers (but
maybe for peers as well), so if you only rely on non-authoritative
registries for recent objects, this may be the reason:

> 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.



cheers


[1] https://lg.as6453.net/doc/cust-routing-policy.html