PIM Join/ Prune Attributes for LISP Environments using Underlay Multicast
draft-vgovindan-pim-jp-extensions-lisp-00
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Vengada Govindan
|
|
Last updated |
|
2021-02-21
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
html
xml
pdf
htmlized (tools)
htmlized
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force V. Govindan
Internet-Draft Cisco
Intended status: Experimental 21 February 2021
Expires: 25 August 2021
PIM Join/ Prune Attributes for LISP Environments using Underlay
Multicast
draft-vgovindan-pim-jp-extensions-lisp-00
Abstract
This document specifies an extension to PIM Join/ Prune messages.
This document defines one PIM Join/ Prune attribute that support the
construction of multicast distribution trees where the root and
receivers are located in different Locator/ID Separation Protocol
(LISP) sites using underlay IP Multicast. This attribute allows the
receiver site to signal the underlay multicast group to the control
plane of the root ITR (Ingress Tunnel Router).
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 25 August 2021.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
Govindan Expires 25 August 2021 [Page 1]
Internet-Draft PIM Join Attributes for LISP Mcast February 2021
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. The case for requiring a new PIM Join/ Prune Extension . . . 3
3. Receiver ETR Group Address Attribute . . . . . . . . . . . . 3
3.1. Receiver Group Address Attribute Format . . . . . . . . . 3
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. Normative References . . . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
The construction of multicast distribution trees where the root and
receivers are located in different LISP sites [RFC6830] is defined in
[RFC6831].
[RFC6831] specifies that (root-EID,G) data packets are to be LISP-
encapsulated into (root-RLOC,G) multicast packets. This document
defines a TLV that facilitates the construction of trees for (root-
RLOC, G).
Specifically, the assignment of the underlay multicast group needs to
be done in consonance with the downstream xTR nodes and avoid
unnecessary replication or traffic hairpinning.
Since the Receiver RLOC Attribute TLV defined in [RFC8059] only
addresses the Ingress Replication case, an additional TLV is defined
by this draft to include scenarios where the underlay uses Multicast
transport. The TLV definition proposed here complies with the base
specification [RFC5384].
This document uses terminology defined in [RFC6830], such as EID,
RLOC, ITR, and ETR.
Govindan Expires 25 August 2021 [Page 2]
Internet-Draft PIM Join Attributes for LISP Mcast February 2021
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. The case for requiring a new PIM Join/ Prune Extension
When LISP based Multicast trees are built using IP Multicast in the
underlay, the mapping between the overlay group address and the
underlay group address becomes a very crucial. It is possible that
under certain circumstances, differnt subsets of xTRs subscribing to
Show full document text