PIM Join Attributes for LISP Environments
draft-ietf-pim-join-attributes-for-lisp-04

The information below is for an old version of the document
Document Type Active Internet-Draft (pim WG)
Last updated 2016-09-16 (latest revision 2016-06-14)
Replaces draft-arango-pim-join-attributes-for-lisp
Stream IETF
Intended RFC status Experimental
Formats pdf htmlized 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 AD Evaluation::Revised I-D Needed
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alvaro Retana
Send notices to "Mike McBride" <mmcbride7@gmail.com>, aretana@cisco.com
Network Working Group                                          J. Arango
Internet-Draft                                                 S. Venaas
Intended status: Experimental                              Cisco Systems
Expires: December 16, 2016                                   I. Kouvelas
                                                    Arista Networks Inc.
                                                            D. Farinacci
                                                             lispers.net
                                                           June 14, 2016

               PIM Join Attributes for LISP Environments
             draft-ietf-pim-join-attributes-for-lisp-04.txt

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 LISP sites.  These attributes
   allow the receiver site to select between unicast and multicast
   underlay transport and to convey the receiver ETR's RLOC address to
   the control plane of the root ITR.

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 http://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 December 16, 2016.

Copyright Notice

   Copyright (c) 2016 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

Arango, et al.          Expires December 16, 2016               [Page 1]
Internet-Draft  PIM Join Attributes for LISP Environments      June 2016

   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 . . . . . . . . . . . . . . . . . . .   3
     4.1.  Transport Attribute Format  . . . . . . . . . . . . . . .   4
     4.2.  Using the Transport Attribute . . . . . . . . . . . . . .   4
   5.  Receiver ETR RLOC Attribute . . . . . . . . . . . . . . . . .   5
     5.1.  Receiver RLOC Attribute Format  . . . . . . . . . . . . .   5
     5.2.  Using the Receiver RLOC Attribute . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

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.

   [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.

   The unicast LISP-encapsulated Join/Prune message specifies the (root-
   EID,G) state that needs to be established in the root site, but
   conveys nothing about the receivers capability or desire to use
   multicast as the underlying transport.  This document specifies a
   Join/Prune attribute that allows the receiver ETR to select the
   desired transport.

   Knowledge of the receiver ETR's RLOC address is also essential to the
   control plane of the root ITR.  It determines the downstream
   destination for unicast head-end replication and identifies the

Arango, et al.          Expires December 16, 2016               [Page 2]
Show full document text