rfc9798v3.txt | rfc9798.txt | |||
---|---|---|---|---|
Internet Engineering Task Force (IETF) V. Govindan | Internet Engineering Task Force (IETF) V. Govindan | |||
Request for Comments: 9798 Cisco | Request for Comments: 9798 S. Venaas | |||
Updates: 8059 S. Venaas | Updates: 8059 Cisco Systems, Inc. | |||
Category: Experimental Cisco Systems, Inc. | Category: Experimental June 2025 | |||
ISSN: 2070-1721 June 2025 | ISSN: 2070-1721 | |||
PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) | PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) | |||
Environments Using Underlay Multicast | Environments Using Underlay Multicast | |||
Abstract | Abstract | |||
This document specifies an update to the Receiver RLOC (Routing | This document specifies an update to the Receiver RLOC (Routing | |||
Locator) field of the PIM Join/Prune attribute that supports the | Locator) field of the PIM Join/Prune attribute that supports the | |||
construction of multicast distribution trees where the source and | construction of multicast distribution trees where the source and | |||
receivers are located in different Locator/ID Separation Protocol | receivers are located in different Locator/ID Separation Protocol | |||
skipping to change at line 163 ¶ | skipping to change at line 163 ¶ | |||
Hardware resource restrictions: | Hardware resource restrictions: | |||
Platform limitations may necessitate engineering decisions to | Platform limitations may necessitate engineering decisions to | |||
restrict multicast address ranges in the underlay due to hardware | restrict multicast address ranges in the underlay due to hardware | |||
resource constraints. | resource constraints. | |||
3. Updates to RFC 8059 | 3. Updates to RFC 8059 | |||
3.1. Scope | 3.1. Scope | |||
No changes are proposed to the syntax or semantics of the Transport | There are no changes to the syntax or semantics of the Transport | |||
Attribute defined in [RFC8059]. | Attribute defined in [RFC8059]. | |||
The scope of the updates to [RFC8059] is limited to the case where | The scope of the updates to [RFC8059] is limited to the case where | |||
the "Transport" field of the Transport Attribute is set to zero | the "Transport" field of the Transport Attribute is set to zero | |||
(multicast) only. | (multicast) only. | |||
3.2. Receiver ETR RLOC Attribute | 3.2. Receiver ETR RLOC Attribute | |||
The definition of the "Receiver RLOC" field of the Receiver ETR RLOC | The definition of the "Receiver RLOC" field of the Receiver ETR RLOC | |||
attribute (see Section 5.1 of [RFC8059]) is updated as follows: | attribute (see Section 5.1 of [RFC8059]) is updated as follows: | |||
skipping to change at line 289 ¶ | skipping to change at line 289 ¶ | |||
The authors would like to thank Dino Farinacci, Victor Moreno, Alvaro | The authors would like to thank Dino Farinacci, Victor Moreno, Alvaro | |||
Retana, Aswin Kuppusami, Joe Clarke, and Peter Yee for their valuable | Retana, Aswin Kuppusami, Joe Clarke, and Peter Yee for their valuable | |||
comments. The authors also thank Sankaralingam T and Amit Kumar for | comments. The authors also thank Sankaralingam T and Amit Kumar for | |||
their contributions to the document. The authors thank Gunter Van de | their contributions to the document. The authors thank Gunter Van de | |||
Velde for his valuable comments. | Velde for his valuable comments. | |||
Authors' Addresses | Authors' Addresses | |||
Vengada Prasad Govindan | Vengada Prasad Govindan | |||
Cisco | Cisco Systems, Inc. | |||
Email: venggovi@cisco.com | Email: venggovi@cisco.com | |||
Stig Venaas | Stig Venaas | |||
Cisco Systems, Inc. | Cisco Systems, Inc. | |||
Tasman Drive | Tasman Drive | |||
San Jose, CA 95134 | San Jose, CA 95134 | |||
United States of America | United States of America | |||
Email: svenaas@cisco.com | Email: stig@cisco.com | |||
End of changes. 4 change blocks. | ||||
6 lines changed or deleted | 6 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |