Management Guidelines for the Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block
RFC 7955
|
| Document |
Type |
|
RFC - Informational
(September 2016; No errata)
|
|
Last updated |
|
2016-09-21
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Damien Saucez
|
|
Shepherd write-up |
|
Show
(last changed 2015-01-16)
|
| IESG |
IESG state |
|
RFC 7955 (Informational)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Brian Haberman
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
No IANA Actions
|
Internet Engineering Task Force (IETF) L. Iannone
Request for Comments: 7955 Telecom ParisTech
Category: Informational R. Jorgensen
ISSN: 2070-1721 Bredbandsfylket Troms
D. Conrad
Virtualized, LLC
G. Huston
APNIC
September 2016
Management Guidelines for the Locator/ID Separation Protocol (LISP)
Endpoint Identifier (EID) Block
Abstract
This document proposes a framework for the management of the Locator/
ID Separation Protocol (LISP) Endpoint Identifier (EID) address
block. The framework described relies on hierarchical distribution
of the address space, granting temporary usage of prefixes of such
space to requesting organizations.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
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/rfc7955.
Iannone, et al. Informational [Page 1]
RFC 7955 LISP EID Block Management 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3
3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3
4. EID Prefix Registration Policy . . . . . . . . . . . . . . . 3
5. EID Prefixes Registration Requirements . . . . . . . . . . . 4
6. EID Prefix Request Template . . . . . . . . . . . . . . . . . 4
7. Policy Validity Period . . . . . . . . . . . . . . . . . . . 6
8. Security Considerations . . . . . . . . . . . . . . . . . . . 6
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
10. Procedures to be Followed by RIPE NCC . . . . . . . . . . . . 7
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
11.1. Normative References . . . . . . . . . . . . . . . . . . 8
11.2. Informative References . . . . . . . . . . . . . . . . . 8
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
The Locator/ID Separation Protocol (LISP [RFC6830]) and related
mechanisms ([RFC6831], [RFC6832], [RFC6833], [RFC6834], [RFC6835],
[RFC6836], [RFC6837]) separate the IP addressing space into two
logical spaces, the Endpoint Identifier (EID) space and the Routing
Locator (RLOC) space. The first space is used to identify
communication endpoints, while the second is used to locate EIDs in
the Internet routing infrastructure topology.
[RFC7954] requests an IPv6 address block reservation exclusively for
use as EID prefixes in the LISP experiment. The rationale, intent,
size, and usage of the EID address block are described in [RFC7954].
Iannone, et al. Informational [Page 2]
RFC 7955 LISP EID Block Management September 2016
This document proposes a management framework for the registration of
EID prefixes from that block, allowing the requesting organization
exclusive use of those EID prefixes limited to the duration of the
LISP experiment.
2. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
Show full document text