PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast

PIM Join/Prune Attributes for Locator/ID Separation Protocol (LISP) Environments Using Underlay Multicast Cisco Systems, Inc.

venggovi@cisco.com

Cisco Systems, Inc.

Tasman Drive San Jose CA 95134 United States of America stig@cisco.com

RTG pim This document specifies an update to the Receiver RLOC (Routing Locator) field of the PIM Join/Prune attribute that supports the construction of multicast distribution trees where the source and receivers are located in different Locator/ID Separation Protocol (LISP) sites and are connected using underlay IP multicast. This attribute allows the receiver site to signal the underlay multicast group to the control plane of the root Ingress Tunnel Router (ITR). This document updates RFC 8059.

Introduction The construction of multicast distribution trees where the root and receivers are located in different LISP sites is defined in . specifies that (EID, G) data packets are to be LISP- encapsulated into (RLOC, G) multicast packets. In this document, we use the term root-EID or root-RLOC to refer to the source of the multicast tree rooted at the EID or RLOC. defines PIM Join/Prune attribute extensions to construct multicast distribution trees. Please refer to for the definition of the terms Endpoint ID (EID) and Routing Locator (RLOC). This document extends the Receiver ETR RLOC PIM Join/Prune attribute to facilitate the construction of underlay multicast trees for (root-RLOC, G). Specifically, the assignment of the underlay multicast group needs to be done in consonance with the downstream Tunnel Router (xTR) nodes needed to avoid unnecessary replication or traffic hairpinning. Since the Receiver RLOC Attribute defined in only addresses the Ingress Replication case, this document extends the scope of that PIM Join/Prune attribute to include scenarios where the underlay uses multicast transport. The scope extension complies with the base specification . This document uses terminology defined in , such as EID, RLOC, ITR and ETR.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

The Case for Extending the Received ETR RLOC Attribute of RFC 8059 When LISP-based multicast trees are constructed using IP multicast in the underlay, the mapping between the overlay group address and the underlay group address becomes a crucial engineering decision.

Flexible Mapping of Overlay to Underlay Group Ranges Three distinct types of overlay to underlay group mappings are possible:

Many-to-one mapping: Many (root-EID, G) flows originating from an RLOC can be mapped to a single underlay multicast (root-RLOC, G-u) flow.
One-to-many mapping: Conversely a single same overlay flow can be mapped to two or more flows -- e.g., (root-RLOC, G-u1) and (root-RLOC, G-u2) -- to cater to the requirements of downstream xTR nodes.
One-to-one mapping: Every (root-EID, G) flow is mapped to a unique (root-RLOC, G-u) flow.

Multicast Address Range Constraints Under certain conditions, different subsets of xTRs subscribing to the same overlay multicast stream may be constrained to use distinct underlay multicast mapping ranges. This introduces a trade-off between replication overhead and the flexibility of address range assignment, which may be necessary in specific use cases like Proxy Tunnel Routers or when using nodes with limited hardware resources as explained below.

Inter-site Proxy Tunnel Routers (PxTR):: When multiple LISP sites are interconnected through a LISP-based transit, the site border node (i.e., PxTR) connects the site-facing interfaces with the external LISP core. In such cases, different ranges of multicast group addresses may be used for constructing (S-RLOC, G) trees within the LISP site and in the external LISP core. This distinction is desirable for various operational reasons.
Hardware resource restrictions:: Platform limitations may necessitate engineering decisions to restrict multicast address ranges in the underlay due to hardware resource constraints.

Updates to RFC 8059

Scope There are no changes to the syntax or semantics of the Transport Attribute defined in . The scope of the updates to is limited to the case where the "Transport" field of the Transport Attribute is set to zero (multicast) only.

Receiver ETR RLOC Attribute The definition of the "Receiver RLOC" field of the Receiver ETR RLOC attribute (see ) is updated as follows: OLD:

Receiver RLOC:

The RLOC address on which the receiver ETR wishes to receive the unicast-encapsulated flow.

NEW:

Receiver RLOC:

The RLOC address on which the receiver ETR wishes to receive the encapsulated flow. A unicast IP Receiver RLOC address is used for unicast-encapsulated flows. Alternately, a multicast IP Receiver RLOC address is used for multicast-encapsulated flows. A multicast IP address MUST be used only when the underlay network of the LISP core supports IP multicast transport.

The definitions of the other fields of the Receiver ETR RLOC Attribute remain unchanged. When the ITR needs to track the list of ETRs from which the PIM joins are received, the ITR MUST use the source IP address field of the incoming PIM Join/Prune message. The source IP address of the PIM Join/Prune MUST be an ETR RLOC IP address.

Using the Receiver RLOC Attribute When the ETR determines to use the multicast underlay:

It chooses an underlay multicast group that it can join. This is a matter of local decision, which is beyond the scope of this document.
It identifies the upstream LISP site where the underlay multicast tree needs to be rooted.
It constructs the PIM Join/Prune message as specified in . Only the Receiver RLOC attribute is encoded as above.

When the ITR receives a PIM Join/Prune message:

It allocates a new entry in the outgoing interface list for every unique underlay multicast mapping.
The ITR MAY apply local policy to perform any kind of rate-limiting on the number of copies it needs to make in the underlay. Such actions are beyond the scope of this document.

IANA Considerations This document has no IANA actions.

Security Considerations An attack vector arises where an attacker sends numerous PIM Join messages with different group addresses. This could interfere with legitimate multicast traffic if the group addresses overlap. Additionally, resource exhaustion may occur if replication is requested for a large number of groups, potentially resulting in significant resource consumption. To mitigate these risks, PIM authentication mechanisms could be employed to validate join requests. Furthermore, implementations may consider explicit tracking mechanisms to manage joins more effectively. Configurable controls could be introduced, allowing for a maximum permissible number of groups for each ETR RLOC used as the source of overlay joins. These controls would limit the impact of such attacks and ensure that resource allocation is managed appropriately.

Normative References

Acknowledgements The authors would like to thank , , , , , and for their valuable comments. The authors also thank and for their contributions to the document. The authors thank for his valuable comments.