Hi Shunwan,
I’ve just re-checked RFC5539, and the referenced section 3 of RFC2545 and I can
find nothing about using VPN-IPv6 for encoding the next-hop. Section 3 of
RFC5539 is very clear that it’s a 16-byte GU IPv6 address or 32-bytes with a GU
and LL address.
Can you point me to the text
Hi Ian,
Thanks for your response!
The opinion I have collected is:
Per RFC4634, the IPv4-VPN routes shall carry the V4 Next-hop, beginning with an
8-octet RD and ending with a 4-octet IPv4 address.
Per RFC4659, the IPv6-VPN routes shall carry the V6 Next-hop, beginning with an
8-octet RD and
Hi,
My reading of Section 3 of RFC5549 is that the v6 next-hop is encoded as an
IPv6 address:
The BGP speaker receiving the advertisement MUST use the Length of
Next Hop Address field to determine which network-layer protocol the
next hop address belongs to. When the Length of Next
Dear authors and WGs,
RFC5549 Section 6.2 says:
.. 6.2. IPv4 VPN over IPv6 Core
..
..The extensions defined in this document may be used for support of
..IPV4 VPNs over an IPv6 backbone. In this application, PE routers
..would advertise VPN-IPv4 NLRI in the MP_REACH_NLRI along with
