rfc9798v2.txt | rfc9798.txt | |||
---|---|---|---|---|
skipping to change at line 100 ¶ | skipping to change at line 100 ¶ | |||
Specifically, the assignment of the underlay multicast group needs to | Specifically, the assignment of the underlay multicast group needs to | |||
be done in consonance with the downstream Tunnel Router (xTR) nodes | be done in consonance with the downstream Tunnel Router (xTR) nodes | |||
needed to avoid unnecessary replication or traffic hairpinning. | needed to avoid unnecessary replication or traffic hairpinning. | |||
Since the Receiver RLOC Attribute defined in [RFC8059] only addresses | Since the Receiver RLOC Attribute defined in [RFC8059] only addresses | |||
the Ingress Replication case, this document extends the scope of that | the Ingress Replication case, this document extends the scope of that | |||
PIM Join/Prune attribute to include scenarios where the underlay uses | PIM Join/Prune attribute to include scenarios where the underlay uses | |||
multicast transport. The scope extension complies with the base | multicast transport. The scope extension complies with the base | |||
specification [RFC5384]. | specification [RFC5384]. | |||
This document uses terminology defined in [RFC9300], such as EID, | This document uses terminology defined in [RFC6831], such as EID, | |||
RLOC, ITR, and ETR. | RLOC, ITR and ETR. | |||
1.1. Requirements Language | 1.1. Requirements Language | |||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | |||
"OPTIONAL" in this document are to be interpreted as described in | "OPTIONAL" in this document are to be interpreted as described in | |||
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all | BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all | |||
capitals, as shown here. | capitals, as shown here. | |||
2. The Case for Extending the Received ETR RLOC Attribute of RFC 8059 | 2. The Case for Extending the Received ETR RLOC Attribute of RFC 8059 | |||
End of changes. 1 change blocks. | ||||
2 lines changed or deleted | 2 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |