Spirent TestCenter: Why should I set IPv6 next hop and IPv6 link local next hop addresses while sending IPv6 routes for BGP with 'IPv4 only' encapsulation?

Doc ID: FAQ14201

Printer Friendly Email Article Link

Spirent TestCenter: Why should I set IPv6 next hop and IPv6 link local next hop addresses while sending IPv6 routes for BGP with 'IPv4 only' encapsulation?

Environment/Versions

Spirent TestCenter
BGP with 'IPv4 only'

Answer

It is working as per RFC.

from the RFC4659 (https://www.rfc-editor.org/rfc/rfc4659.txt):

3.2.1.2. BGP Speaker Requesting IPv4 Transport

When the IPv6 VPN traffic is to be transported to the BGP speaker using IPv4 tunneling (e.g., IPv4 MPLS LSPs, IPsec-protected IPv4 tunnels), the BGP speaker SHALL advertise to its peer a Next Hop.

Network Address field containing a VPN-IPv6 address:

- whose 8-octet RD is set to zero, and

- whose 16-octet IPv6 address is encoded as an IPv4-mapped IPv6 address [V6ADDR] containing the IPv4 address of the advertising BGP speaker. This IPv4 address must be routable by the other BGP Speaker.

Attachments

Attachment

BGP_IPVPN.rar

Version 2.0

Publish Date 2013-09-17

Categories
Product : Spirent TestCenter,Routing,Spirent TestCenter,BGP

Customer Service Center

Spirent KB Article

Spirent TestCenter: Why should I set IPv6 next hop and IPv6 link local next hop addresses while sending IPv6 routes for BGP with 'IPv4 only' encapsulation?