rfc9780v3.txt   rfc9780.txt 
skipping to change at line 104 skipping to change at line 104
This document describes procedures for using such modes of the BFD This document describes procedures for using such modes of the BFD
protocol to detect data plane failures in point-to-multipoint (P2MP) protocol to detect data plane failures in point-to-multipoint (P2MP)
MPLS Label Switched Paths (LSPs) and Segment Routing (SR) point-to- MPLS Label Switched Paths (LSPs) and Segment Routing (SR) point-to-
multipoint policies with an SR over MPLS (SR-MPLS) data plane. multipoint policies with an SR over MPLS (SR-MPLS) data plane.
The document also describes the applicability of LSP Ping (an in-band The document also describes the applicability of LSP Ping (an in-band
solution) and out-of-band solutions to bootstrap a BFD session in solution) and out-of-band solutions to bootstrap a BFD session in
this environment. this environment.
Historically, an address in the IPv6-mapped IPv4 loopback range Historically, an address in the IPv6-mapped IPv4 loopback address
::ffff:127.0.0.1/128 was mandated, although functionally, an IPv6 block ::ffff:127.0.0.1/128 was mandated, although functionally, an
address from that range is not analogous to its IPv4 counterpart. IPv6 address from that address block is not analogous to its IPv4
Furthermore, using the loopback address as the destination address, counterpart. Furthermore, using the loopback address as the
even for an inner IP encapsulation of a tunneled packet, violates destination address, even for an inner IP encapsulation of a tunneled
Section 2.5.3 of [RFC4291]. Hence, IANA has allocated 100:0:0:1::/64 packet, violates Section 2.5.3 of [RFC4291]. Hence, IANA has
as a new Dummy IPv6 Prefix (Section 7.1) for destination IPv6 allocated 100:0:0:1::/64 as a new Dummy IPv6 Prefix (Section 7.1) for
addresses used for IP/UDP encapsulation of management, control, and destination IPv6 addresses used for IP/UDP encapsulation of
OAM (Operations, Administration, and Maintenance) packets. A source- management, control, and OAM (Operations, Administration, and
only IPv6 dummy address is used as the destination to generate an Maintenance) packets. A source-only IPv6 dummy address is used as
exception and a reply message to the request message received. This the destination to generate an exception and a reply message to the
document starts the transition to using the IPv6 addresses from the request message received. This document starts the transition to
Dummy IPv6 Prefix address block 100:0:0:1::/64 as the IPv6 using the IPv6 addresses from the Dummy IPv6 Prefix address block
destination address in the IP/UDP encapsulation of active OAM over 100:0:0:1::/64 as the IPv6 destination address in the IP/UDP
the MPLS data plane. Thus, this document updates [RFC8562] by encapsulation of active OAM over the MPLS data plane. Thus, this
recommending the use of an IPv6 address from the Dummy IPv6 Prefix document updates [RFC8562] by recommending the use of an IPv6 address
address block 100:0:0:1::/64 (Section 7.1) while acknowledging that from the Dummy IPv6 Prefix address block 100:0:0:1::/64 (Section 7.1)
an address from the ::ffff:127.0.0.1/128 range might be used by while acknowledging that an address from the ::ffff:127.0.0.1/128
existing implementations. This document discourages the use of an address block might be used by existing implementations. This
address in the IPv6-mapped IPv4 loopback range. document discourages the use of an address in the IPv6-mapped IPv4
loopback address block.
This document also describes the behavior of the active tail for head This document also describes the behavior of the active tail for head
notification. notification.
2. Conventions Used in This Document 2. Conventions Used in This Document
2.1. Terminology 2.1. Terminology
ACH: Associated Channel Header ACH: Associated Channel Header
skipping to change at line 188 skipping to change at line 189
3.1. IP Encapsulation of Multipoint BFD 3.1. IP Encapsulation of Multipoint BFD
[RFC8562] defines IP/UDP encapsulation for multipoint BFD over P2MP [RFC8562] defines IP/UDP encapsulation for multipoint BFD over P2MP
MPLS LSP. This document updates Section 5.8 of [RFC8562] regarding MPLS LSP. This document updates Section 5.8 of [RFC8562] regarding
the selection of the IPv6 destination address as follows: the selection of the IPv6 destination address as follows:
* The sender of an MPLS echo request SHOULD use an address from the * The sender of an MPLS echo request SHOULD use an address from the
Dummy IPv6 Prefix address block 100:0:0:1::/64 (see Section 7.1). Dummy IPv6 Prefix address block 100:0:0:1::/64 (see Section 7.1).
* The sender of an MPLS echo request MAY select the IPv6 destination * The sender of an MPLS echo request MAY select the IPv6 destination
address from the ::ffff:7f00/104 range. address from the ::ffff:7f00/104 address block.
Section 1.2 of [RFC6790] lists several advantages of generating the Section 1.2 of [RFC6790] lists several advantages of generating the
entropy value by an ingress Label Switching Router (LSR) compared to entropy value by an ingress Label Switching Router (LSR) compared to
when a transit LSR infers entropy using the information in the MPLS when a transit LSR infers entropy using the information in the MPLS
label stack or payload. This specification further clarifies the label stack or payload. This specification further clarifies the
following if multiple alternative paths for the given P2MP LSP following if multiple alternative paths for the given P2MP LSP
Forwarding Equivalence Class (FEC) exist: Forwarding Equivalence Class (FEC) exist:
* The MultipointHead SHOULD use the Entropy Label [RFC6790] used for * The MultipointHead SHOULD use the Entropy Label [RFC6790] used for
LSP Ping [RFC8029] to exercise those particular alternative paths; LSP Ping [RFC8029] to exercise those particular alternative paths;
 End of changes. 2 change blocks. 
21 lines changed or deleted 22 lines changed or added

This html diff was produced by rfcdiff 1.48.