PIM Join Attributes for Locator/ID Separation Protocol (LISP) Environments
RFC 8059

Document Type RFC - Experimental (January 2017; No errata)
Last updated 2017-01-20
Replaces draft-arango-pim-join-attributes-for-lisp
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Mike McBride
Shepherd write-up Show (last changed 2016-06-21)
IESG IESG state RFC 8059 (Experimental)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to "Mike McBride" <mmcbride7@gmail.com>, aretana@cisco.com
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                         J. Arango
Request for Comments: 8059                                     S. Venaas
Category: Experimental                                     Cisco Systems
ISSN: 2070-1721                                              I. Kouvelas
                                                    Arista Networks Inc.
                                                            D. Farinacci
                                                             lispers.net
                                                            January 2017

                          PIM Join Attributes
         for Locator/ID Separation Protocol (LISP) Environments

Abstract

   This document defines two PIM Join/Prune attributes that support the
   construction of multicast distribution trees where the root and
   receivers are located in different Locator/ID Separation Protocol
   (LISP) sites.  These attributes allow the receiver site to select
   between unicast and multicast underlying transport and to convey the
   RLOC (Routing Locator) address of the receiver ETR (Egress Tunnel
   Router) to the control plane of the root ITR (Ingress Tunnel Router).

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  This document is a product of the Internet Engineering
   Task Force (IETF).  It represents the consensus of the IETF
   community.  It has received public review and has been approved for
   publication by the Internet Engineering Steering Group (IESG).  Not
   all documents approved by the IESG are a candidate for any level of
   Internet Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc8059.

Arango, et al.                Experimental                      [Page 1]
RFC 8059        PIM Join Attributes for LISP Environments   January 2017

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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
   2.  Requirements Notation . . . . . . . . . . . . . . . . . . . .   3
   3.  PIM Join/Prune Attributes . . . . . . . . . . . . . . . . . .   3
   4.  The Transport Attribute . . . . . . . . . . . . . . . . . . .   4
     4.1.  Transport Attribute Format  . . . . . . . . . . . . . . .   4
     4.2.  Using the Transport Attribute . . . . . . . . . . . . . .   5
   5.  Receiver ETR RLOC Attribute . . . . . . . . . . . . . . . . .   5
     5.1.  Receiver RLOC Attribute Format  . . . . . . . . . . . . .   6
     5.2.  Using the Receiver RLOC Attribute . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The construction of multicast distribution trees where the root and
   receivers are located in different LISP sites [RFC6830] is defined in
   [RFC6831].  Creation of (root-EID,G) state in the root site requires
   that unicast LISP-encapsulated Join/Prune messages be sent from an
   ETR on the receiver site to an ITR on the root site.  The term "EID"
   is short for "Endpoint ID".

   [RFC6831] specifies that (root-EID,G) data packets are to be LISP-
   encapsulated into (root-RLOC,G) multicast packets.  However, a wide
   deployment of multicast connectivity between LISP sites is unlikely
   to happen any time soon.  In fact, some implementations are initially
   focusing on unicast transport with head-end replication between root
   and receiver sites.

Arango, et al.                Experimental                      [Page 2]
Show full document text