Internet Engineering Task Force D. Farinacci
Internet-Draft lispers.net
Intended status: Experimental M. Napierala
Expires: September 4, 2014 AT&T
March 3, 2014
LISP Control-Plane Multicast Signaling
draft-farinacci-lisp-mr-signaling-04
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 September 4, 2014.
Copyright Notice
Copyright (c) 2014 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 September 4, 2014 [Page 1]Internet-Draft LISP Control-Plane Multicast Signaling March 2014Table of Contents
1. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 6
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Join-Request/Leave-Request Encoding Formats . . . . . . . . . 9
6. Replication Considerations . . . . . . . . . . . . . . . . . . 11
7. Interworking Considerations . . . . . . . . . . . . . . . . . 12
8. Security Considerations . . . . . . . . . . . . . . . . . . . 13
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . 15
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 16
Appendix B. Document Change Log . . . . . . . . . . . . . . . . . 17
B.1. Changes to draft-farinacci-lisp-mr-signaling-04.txt . . . 17
B.2. Changes to draft-farinacci-lisp-mr-signaling-03.txt . . . 17
B.3. Changes to draft-farinacci-lisp-mr-signaling-02.txt . . . 17
B.4. Changes to draft-farinacci-lisp-mr-signaling-01.txt . . . 17
B.5. Changes to draft-farinacci-lisp-mr-signaling-00.txt . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
Farinacci & Napierala Expires September 4, 2014 [Page 2]Internet-Draft LISP Control-Plane Multicast Signaling March 20141. 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].
Farinacci & Napierala Expires September 4, 2014 [Page 3]Internet-Draft LISP Control-Plane Multicast Signaling March 20142. 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
datatracker.ietf.org