I thought the bigger /32 prefix should be advertised from AS64511 to both AS13335 and AS64510.
Is there free BGP peering for the purpose of only passing on the NLRIs?
It's interesting that on the "open positions" page, the location filter appears to be strictly string matching, e.g. "US" does not cover "New York, US"
I don't think it makes sense for AS64511 (example customer) to advertise the /32 to AS13335 (Cloudflare) when they only want the /48 to be routed through Cloudflare.
> Things get more interesting when AS64510 signals for 2001:db8::/48 to be withdrawn by Cloudflare (AS13335)
Typo - shouldn't that be AS64511?
...and...
> The MRAI specifies the minimum amount of time ... between each BGP advertisement update.
Each update _per prefix, per peer_. RFC4271 sec.9.2.1.1 says
---
[MRAI] determines the minimum amount of time that must elapse between an advertisement
and/or withdrawal of routes to a particular destination by a BGP speaker to a peer
---
4 comments
[ 2.4 ms ] story [ 21.5 ms ] threadIs there free BGP peering for the purpose of only passing on the NLRIs?
It's interesting that on the "open positions" page, the location filter appears to be strictly string matching, e.g. "US" does not cover "New York, US"
Typo - shouldn't that be AS64511?
...and...
> The MRAI specifies the minimum amount of time ... between each BGP advertisement update.
Each update _per prefix, per peer_. RFC4271 sec.9.2.1.1 says
--- [MRAI] determines the minimum amount of time that must elapse between an advertisement and/or withdrawal of routes to a particular destination by a BGP speaker to a peer ---