LISP Control-Plane Multicast Signaling
draft-farinacci-lisp-mr-signaling-06

 
Document
Type Active Internet-Draft (individual)
Last updated 2015-02-16
Stream (None)
Intended RFC status (None)
Formats plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

Internet Engineering Task Force                             D. Farinacci
Internet-Draft                                               lispers.net
Intended status: Experimental                               M. Napierala
Expires: August 20, 2015                                            AT&T
                                                       February 16, 2015

                 LISP Control-Plane Multicast Signaling
                  draft-farinacci-lisp-mr-signaling-06

Abstract

   This document describes an alternate method to signal multicast tree
   building among xTRs in multicast capable LISP sites.  This approach
   avoids the need to run a multicast routing protocol on the LISP
   overlay.

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 August 20, 2015.

Copyright Notice

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

Farinacci & Napierala    Expires August 20, 2015                [Page 1]
Internet-Draft   LISP Control-Plane Multicast Signaling    February 2015

Table of Contents

   1.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Definition of Terms . . . . . . . . . . . . . . . . . . . . .   4
   4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Join-Request/Leave-Request Encoding Formats . . . . . . . . .   6
   6.  Replication Considerations  . . . . . . . . . . . . . . . . .   8
   7.  Interworking Considerations . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     10.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  10
   Appendix B.  Document Change Log  . . . . . . . . . . . . . . . .  10
     B.1.  Changes to draft-farinacci-lisp-mr-signaling-06.txt . . .  10
     B.2.  Changes to draft-farinacci-lisp-mr-signaling-05.txt . . .  10
     B.3.  Changes to draft-farinacci-lisp-mr-signaling-04.txt . . .  10
     B.4.  Changes to draft-farinacci-lisp-mr-signaling-03.txt . . .  10
     B.5.  Changes to draft-farinacci-lisp-mr-signaling-02.txt . . .  10
     B.6.  Changes to draft-farinacci-lisp-mr-signaling-01.txt . . .  10
     B.7.  Changes to draft-farinacci-lisp-mr-signaling-00.txt . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

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

   The Locator/ID Separation Architecture [RFC6830] provides a mechanism
   to separate out Identification and Location semantics from the
   current definition of an IP address.  By creating two namespaces, an
   Endpoint ID (EID) namespace used by sites and a Routing Locator
   (RLOC) namespace used by core routing, the core routing
   infrastructure can scale by doing topological aggregation of routing
   information.

   Since LISP creates a new namespace, a mapping function must exist to
   map a site's EID prefixes to its associated locators.  For unicast
Show full document text