LISP EID Block Management Guidelines
draft-ietf-lisp-eid-block-mgmnt-05

The information below is for an old version of the document
Document Type Active Internet-Draft (lisp WG)
Last updated 2015-07-16 (latest revision 2015-07-03)
Stream IETF
Intended RFC status Informational
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 Waiting for AD Go-Ahead
Consensus Boilerplate Unknown
Telechat date
Responsible AD Brian Haberman
Send notices to damien.saucez@gmail.com, lisp-chairs@ietf.org
IANA IANA review state Version Changed - Review Needed
IANA action state None
Network Working Group                                         L. Iannone
Internet-Draft                                         Telecom ParisTech
Intended status: Informational                              R. Jorgensen
Expires: January 4, 2016                           Bredbandsfylket Troms
                                                               D. Conrad
                                                        Virtualized, LLC
                                                               G. Huston
                                            APNIC - Asia Pacific Network
                                                      Information Center
                                                            July 3, 2015

                  LISP EID Block Management Guidelines
                 draft-ietf-lisp-eid-block-mgmnt-05.txt

Abstract

   This document proposes a framework for the management of the LISP EID
   Prefix.  The framework described relies on hierarchical distribution
   of the address space, granting temporary usage of sub-prefixes of
   such space to requesting organizations.

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 January 4, 2016.

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

Iannone, et al.          Expires January 4, 2016                [Page 1]
Internet-Draft          LISP EID Block Management              July 2015

   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.  Requirements Notation  . . . . . . . . . . . . . . . . . . . .  3
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Definition of Terms  . . . . . . . . . . . . . . . . . . . . .  3
   4.  EID Prefix Registration Policy . . . . . . . . . . . . . . . .  3
   5.  EID Prefixes Registration Requirements . . . . . . . . . . . .  4
   6.  EID Prefix Request Template  . . . . . . . . . . . . . . . . .  5
   7.  Policy Validity Period . . . . . . . . . . . . . . . . . . . .  6
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . .  7
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7
   10. Procedures to be followed by RIPE NCC  . . . . . . . . . . . .  7
   11. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . .  8
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     12.1.  Normative References  . . . . . . . . . . . . . . . . . .  8
     12.2.  Informative References  . . . . . . . . . . . . . . . . .  8
   Appendix A.  LISP Terms  . . . . . . . . . . . . . . . . . . . . .  9
   Appendix B.  Document Change Log . . . . . . . . . . . . . . . . . 12
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13

Iannone, et al.          Expires January 4, 2016                [Page 2]
Internet-Draft          LISP EID Block Management              July 2015

1.  Requirements Notation

   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 [RFC2119].

2.  Introduction

   The Locator/ID Separation Protocol (LISP - [RFC6830]) and related
   mechanisms ([RFC6831], [RFC6832], [RFC6833], [RFC6834], [RFC6835],
   [RFC6836], [RFC6837]) separates the IP addressing space into two
   logical spaces, the End-point IDentifier (EID) space and the Routing
   LOCator (RLOC) space.  The first space is used to identify
   communication end-points, while the second is used to locate EIDs in
   the Internet routing infrastructure topology.

   The document [I-D.ietf-lisp-eid-block] requested an IPv6 address
   block reservation exclusively for use as EID prefixes in the LISP
   experiment.  The rationale, intent, size, and usage of the EID
Show full document text