Ldp Ipv6 Interoperability Considerations; Interoperability With Implementations Compliant With Draft-Ietf-Mpls-Ldp-Ipv6 - Alcatel-Lucent 7450 Manual

LDP IPv6 Interoperability Considerations

•
The behavior at the sender and receiver nodes is updated to support both LDP IPv4 and IPv6 target
FEC stack TLVs. Specifically:
1. The IP family (IPv4/IPv6) of the UDP/IP echo request message will always match the
2. The src-ip-address option is extended to accept IPv6 address of the sender node. If the
3. The IP family of the UDP/IP echo reply message must match that of the received echo
4. For lsp-trace, the downstream information in DSMAP/DDMAP will be encoded as the
5. The sender node inserts the experimental value of 65503 in the Router Alert Option in the
Finally, vccv-ping and vccv-trace for a single-hop PW are updated to support IPv6 PW FEC 128
and FEC 129 as per RFC 6829. In addition, the PW OAM control word is supported with VCCV
packets when the control-word option is enabled on the spoke-SDP configuration. The value of
the Channel Type field is set to 0x57 indicates that the Associated Channel carries an IPv6 packet,
as per RFC 4385.
LDP IPv6 Interoperability Considerations
Interoperability with Implementations Compliant with draft-ietf-mpls-
ldp-ipv6
SR OS implementation uses a 128-bit LSR-ID as defined in draft-pdutta-mpls-ldp-v2 to establish
an LDP IPv6 session with a peer LSR. This is done such that a routable system IPv6 address can
be used by default to bring up the LDP task on the router and establish link LDP and T-LDP
sessions to other LSRs, as is the common practice with LDP IPv4 in existing customer
deployments. More importantly, this allows for the establishment of control plane independent
LDP IPv4 and LDP IPv6 sessions between two LSRs over the same interface or set of interfaces.
The SR OS implementation allows for two separate LDP IPv4 and LDP IPv6 sessions between
two LSRs over the same interface or a set of interfaces because each session uses a unique LSR-ID
(32-bit for IPv4 and 128-bit for IPv6).
Page 614
use of 127/8 IPv4 mapped IPv6 address; that is, in the range ::ffff:127/104, as the
path-destination address when the user wants to exercise a specific LDP ECMP path.
family of the LDP target FEC stack TLV as entered by the user in the prefix option.
user did not enter a source IP address, the system IPv6 address will be used. If the user
entered a source IP address of a different family than the LDP target FEC stack TLV, an
error is returned and the test command is aborted.
request message.
same family as the LDP control plane of the link LDP or targeted LDP session to the
downstream peer.
echo request packet's IPv6 header as per RFC 5350. Once a value is allocated by IANA
for MPLS OAM as part of draft-ietf-mpls-oam-ipv6-rao, it will be updated.
7450 ESS MPLS Guide