Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block
RFC 7954
Internet Engineering Task Force (IETF) L. Iannone
Request for Comments: 7954 Telecom ParisTech
Category: Experimental D. Lewis
ISSN: 2070-1721 Cisco Systems, Inc.
D. Meyer
Brocade
V. Fuller
September 2016
Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block
Abstract
This document directs IANA to allocate a /32 IPv6 prefix for use with
the Locator/ID Separation Protocol (LISP). The prefix will be used
for local intra-domain routing and global endpoint identification, by
sites deploying LISP as Endpoint Identifier (EID) addressing space.
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/rfc7954.
Iannone, et al. Experimental [Page 1]
RFC 7954 LISP EID Block September 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
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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3
3. Rationale and Intent . . . . . . . . . . . . . . . . . . . . 3
4. Expected Use . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Block Dimension . . . . . . . . . . . . . . . . . . . . . . . 5
6. 3+3 Allocation Plan . . . . . . . . . . . . . . . . . . . . . 6
7. Allocation Lifetime . . . . . . . . . . . . . . . . . . . . . 7
8. Routing Considerations . . . . . . . . . . . . . . . . . . . 7
9. Security Considerations . . . . . . . . . . . . . . . . . . . 8
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
11.1. Normative References . . . . . . . . . . . . . . . . . . 9
11.2. Informative References . . . . . . . . . . . . . . . . . 10
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
Iannone, et al. Experimental [Page 2]
RFC 7954 LISP EID Block September 2016
1. Introduction
This document directs the IANA to allocate a /32 IPv6 prefix for use
with the Locator/ID Separation Protocol (LISP [RFC6830]), LISP Map-
Server ([RFC6833]), LISP Alternative Topology (LISP+ALT [RFC6836])
(or other) mapping systems, and LISP Interworking ([RFC6832]).
This block will be used as global Endpoint Identifier (EID) space.
2. Definition of Terms
The present document does not introduce any new terms with respect to
the set of LISP Specifications ([RFC6830], [RFC6831], [RFC6832],
[RFC6833], [RFC6834], [RFC6835], [RFC6836], [RFC6837]), but it
assumes that the reader is familiar with the LISP terminology.
[LISP-INTRO] provides an introduction to the LISP technology,
including its terminology.
3. Rationale and Intent
Discussion within the LISP working group led to the identification of
several scenarios in which the existence of a LISP-specific address
block brings technical benefits. The most relevant scenarios are
described below:
Early LISP destination detection: With the current specifications,
Show full document text