Network Working Group L. Iannone
Internet-Draft Telecom ParisTech
Intended status: Informational D. Lewis
Expires: August 4, 2014 Cisco Systems, Inc.
D. Meyer
Brocade
V. Fuller
January 31, 2014
LISP EID Block
draft-ietf-lisp-eid-block-08.txt
Abstract
This is a direction to 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 EID (Endpoint IDentifier)
addressing space.
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 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
Iannone, et al. Expires August 4, 2014 [Page 1]Internet-Draft LISP EID Block January 2014
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 . . . . . . . . . . . . . . . . . . . . . . . 6
6. 3+3 Allocation Plan . . . . . . . . . . . . . . . . . . . . . 6
7. Routing Considerations . . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
11.1. Normative References . . . . . . . . . . . . . . . . . . 9
11.2. Informative References . . . . . . . . . . . . . . . . . 10
Appendix A. LISP Terminology . . . . . . . . . . . . . . . . . . 11
Appendix B. Document Change Log . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
Iannone, et al. Expires August 4, 2014 [Page 2]Internet-Draft LISP EID Block January 20141. 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 term with respect to
the set of LISP Specifications ( [RFC6830], [RFC6831], [RFC6832],
[RFC6833], [RFC6834], [RFC6835], [RFC6836], [RFC6837]). To help the
reading of the present document the terminology introduced by LISP is
summarized in Appendix A.
3. Rationale and Intent
Discussion within the LISP Working Group led to identify several
scenarios in which the existence of a LISP specific address block
datatracker.ietf.org