RFC5549 is obsolete. Replacement is RFC8950. The idea is that IPv4 prefixes can be advertised via BGP with an IPv6 next-hop address. So, if fully implemented on *all* IXP customers the IXP would not need an IPv4 prefix for the peering LAN any more.
You can check yourself if your router implements this, on Cisco do a "show bgp neighbor", - "Extended Nexthop Encoding: advertised" means that your router supports it - "Extended Nexthop Encoding: advertised and received" means your router and your peer supports it best regards Wolfgang > On 8. Nov 2022, at 14:55, Nick Hilliard <[email protected]> wrote: > > this is kinda the problem with RFC 5549, no? I.e. it deals only with > signaling rather than transport. So even if it's deployed, the IXP will still > need to provide ipv4 addresses for transport purposes -- Wolfgang Tremmel Phone +49 69 1730902 0 | [email protected] Executive Directors: Ivaylo Ivanov and Sebastian Seifert | Trade Registry: AG Cologne, HRB 51135 DE-CIX Management GmbH | Lindleystrasse 12 | 60314 Frankfurt am Main | Germany | www.de-cix.net -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/address-policy-wg
