draft-ietf-lisp-eid-block-mgmnt-04.txt   draft-ietf-lisp-eid-block-mgmnt-05.txt 
Network Working Group L. Iannone Network Working Group L. Iannone
Internet-Draft Telecom ParisTech Internet-Draft Telecom ParisTech
Intended status: Informational R. Jorgensen Intended status: Informational R. Jorgensen
Expires: July 4, 2015 Bredbandsfylket Troms Expires: January 4, 2016 Bredbandsfylket Troms
D. Conrad D. Conrad
Virtualized, LLC Virtualized, LLC
G. Huston G. Huston
APNIC - Asia Pacific Network APNIC - Asia Pacific Network
Information Center Information Center
December 31, 2014 July 3, 2015
LISP EID Block Management Guidelines LISP EID Block Management Guidelines
draft-ietf-lisp-eid-block-mgmnt-04.txt draft-ietf-lisp-eid-block-mgmnt-05.txt
Abstract Abstract
This document proposes a framework for the management of the LISP EID This document proposes a framework for the management of the LISP EID
Prefix. The framework described relies on hierarchical distribution Prefix. The framework described relies on hierarchical distribution
of the address space, granting temporary usage of sub-prefixes of of the address space, granting temporary usage of sub-prefixes of
such space to requesting organizations. such space to requesting organizations.
Status of this Memo Status of this Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 4, 2015. This Internet-Draft will expire on January 4, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 20 skipping to change at page 2, line 20
Table of Contents Table of Contents
1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3 3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3
4. EID Prefix Registration Policy . . . . . . . . . . . . . . . . 3 4. EID Prefix Registration Policy . . . . . . . . . . . . . . . . 3
5. EID Prefixes Registration Requirements . . . . . . . . . . . . 4 5. EID Prefixes Registration Requirements . . . . . . . . . . . . 4
6. EID Prefix Request Template . . . . . . . . . . . . . . . . . 5 6. EID Prefix Request Template . . . . . . . . . . . . . . . . . 5
7. Policy Validity Period . . . . . . . . . . . . . . . . . . . . 6 7. Policy Validity Period . . . . . . . . . . . . . . . . . . . . 6
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7 8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 10. Procedures to be followed by RIPE NCC . . . . . . . . . . . . 7
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
11.1. Normative References . . . . . . . . . . . . . . . . . . 8 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
11.2. Informative References . . . . . . . . . . . . . . . . . 8 12.1. Normative References . . . . . . . . . . . . . . . . . . 8
12.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. LISP Terms . . . . . . . . . . . . . . . . . . . . . 9 Appendix A. LISP Terms . . . . . . . . . . . . . . . . . . . . . 9
Appendix B. Document Change Log . . . . . . . . . . . . . . . . . 12 Appendix B. Document Change Log . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Requirements Notation 1. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
The Locator/ID Separation Protocol (LISP - [RFC6830]) and related The Locator/ID Separation Protocol (LISP - [RFC6830]) and related
skipping to change at page 4, line 43 skipping to change at page 4, line 43
1. All EID prefix registrations MUST use a globally unique EID 1. All EID prefix registrations MUST use a globally unique EID
prefix. prefix.
2. If there is more than one registry operator, all operators MUST 2. If there is more than one registry operator, all operators MUST
use the same registry management policies and practices. use the same registry management policies and practices.
3. The EID Prefix registration information as specified in 3. The EID Prefix registration information as specified in
Section 6, MUST be collected upon initial registration and Section 6, MUST be collected upon initial registration and
renewal, and made publicly available though interfaces allowing renewal, and made publicly available though interfaces allowing
both retrieval of specific registration details (search) and both retrieval of specific registration details (search) and
enumeration of the entire registry contents (e.g., enumeration of the entire registry contents (e.g., [RFC7481],
[I-D.ietf-weirds-rdap-sec], whois, http, or similar access whois, http, or similar access methods).
methods).
4. The registry operator MUST permit the delegation of EID prefixes 4. The registry operator MUST permit the delegation of EID prefixes
in the reverse DNS space to holders of registered EID prefixes. in the reverse DNS space to holders of registered EID prefixes.
5. Anyone can obtain an entry in the EID prefix registry, on the 5. Anyone can obtain an entry in the EID prefix registry, on the
understanding that the prefix so registered is for the exclusive understanding that the prefix so registered is for the exclusive
use in the LISP experimental network, and that their registration use in the LISP experimental network, and that their registration
details (as specified in Section 6) are openly published in the details (as specified in Section 6) are openly published in the
EID prefix registry. EID prefix registry.
skipping to change at page 7, line 28 skipping to change at page 7, line 28
This document does not introduce new security threats in the LISP This document does not introduce new security threats in the LISP
architecture nor in the Legacy Internet architecture. architecture nor in the Legacy Internet architecture.
For accountability reasons, and in line with the security For accountability reasons, and in line with the security
considerations in [RFC7020], each registration request MUST contain considerations in [RFC7020], each registration request MUST contain
accurate information on the requesting entity (company, institution, accurate information on the requesting entity (company, institution,
individual, etc.) and valid and accurate contact information of a individual, etc.) and valid and accurate contact information of a
referral person (see Section 6). referral person (see Section 6).
9. Acknowledgments 9. IANA Considerations
Thanks to J. Curran, A. Severin, B. Haberman, T. Manderson, D. Lewis,
D. Farinacci, M. Binderberger, D. Saucez, E. Lear, for their helpful
comments.
The work of Luigi Iannone has been partially supported by the ANR-13-
INFR-0009 LISP-Lab Project (www.lisp-lab.org) and the EIT KIC ICT-
Labs SOFNETS Project.
10. IANA Considerations
This document provides only management guidelines for the reserved This document provides only management guidelines for the reserved
LISP EID prefix requested in [I-D.ietf-lisp-eid-block]. LISP EID prefix requested in [I-D.ietf-lisp-eid-block].
There is an operational requirement for an EID registration service There is an operational requirement for an EID registration service
that ensures uniqueness of EIDs according to the requirements that ensures uniqueness of EIDs according to the requirements
described in Section 5. Furthermore, there is an operational described in Section 5. Furthermore, there is an operational
requirement for EID registration service that allows a lookup of the requirement for EID registration service that allows a lookup of the
contact information of the entity that registered the EID. contact information of the entity that registered the EID.
IANA is to ensure both of these services are provided in a globally IANA and RIPE NCC agreed for the latter to run such service on behalf
uniform fashion for the duration of the experiment. of the former, for the duration of the experiment and following the
procedures outlined in Section 10.
11. References 10. Procedures to be followed by RIPE NCC
11.1. Normative References RIPE NCC will provide the registration service following the EID
Prefix Registration Policy (Section 4) and the EID Prefix
Registration Requirements (Section 5) provided in this document. The
request form provided by RIPE NCC will include at least the
information from the template in Section 6. RIPE NCC will make
publicly available all received requests. While this document does
not suggests any minimum allocation size, RIPE NCC is allowed to
introduce such minimum size for menagement purposes.
11. Acknowledgments
Thanks to A. de la Haye, A. Cima, A Pawlik, J. Curran, A. Severin, B.
Haberman, T. Manderson, D. Lewis, D. Farinacci, M. Binderberger, D.
Saucez, E. Lear, for their helpful comments.
The work of Luigi Iannone has been partially supported by the ANR-13-
INFR-0009 LISP-Lab Project (www.lisp-lab.org) and the EIT KIC ICT-
Labs SOFNETS Project.
12. References
12.1. Normative References
[I-D.ietf-lisp-eid-block] [I-D.ietf-lisp-eid-block]
Iannone, L., Lewis, D., Meyer, D., and V. Fuller, "LISP Iannone, L., Lewis, D., Meyer, D., and V. Fuller, "LISP
EID Block", draft-ietf-lisp-eid-block-09 (work in EID Block", draft-ietf-lisp-eid-block-12 (work in
progress), July 2014. progress), May 2015.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing [RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing
(CIDR): The Internet Address Assignment and Aggregation (CIDR): The Internet Address Assignment and Aggregation
Plan", BCP 122, RFC 4632, August 2006. Plan", BCP 122, RFC 4632, August 2006.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
11.2. Informative References 12.2. Informative References
[I-D.ietf-weirds-rdap-sec]
Hollenbeck, S. and N. Kong, "Security Services for the
Registration Data Access Protocol",
draft-ietf-weirds-rdap-sec-12 (work in progress),
December 2014.
[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of
Understanding Concerning the Technical Work of the Understanding Concerning the Technical Work of the
Internet Assigned Numbers Authority", RFC 2860, June 2000. Internet Assigned Numbers Authority", RFC 2860, June 2000.
[RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The [RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The
Locator/ID Separation Protocol (LISP)", RFC 6830, Locator/ID Separation Protocol (LISP)", RFC 6830,
January 2013. January 2013.
[RFC6831] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "The [RFC6831] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "The
skipping to change at page 9, line 26 skipping to change at page 9, line 32
[RFC6836] Fuller, V., Farinacci, D., Meyer, D., and D. Lewis, [RFC6836] Fuller, V., Farinacci, D., Meyer, D., and D. Lewis,
"Locator/ID Separation Protocol Alternative Logical "Locator/ID Separation Protocol Alternative Logical
Topology (LISP+ALT)", RFC 6836, January 2013. Topology (LISP+ALT)", RFC 6836, January 2013.
[RFC6837] Lear, E., "NERD: A Not-so-novel Endpoint ID (EID) to [RFC6837] Lear, E., "NERD: A Not-so-novel Endpoint ID (EID) to
Routing Locator (RLOC) Database", RFC 6837, January 2013. Routing Locator (RLOC) Database", RFC 6837, January 2013.
[RFC7020] Housley, R., Curran, J., Huston, G., and D. Conrad, "The [RFC7020] Housley, R., Curran, J., Huston, G., and D. Conrad, "The
Internet Numbers Registry System", RFC 7020, August 2013. Internet Numbers Registry System", RFC 7020, August 2013.
[RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the
Registration Data Access Protocol (RDAP)", RFC 7481,
March 2015.
Appendix A. LISP Terms Appendix A. LISP Terms
LISP operates on two name spaces and introduces several new network LISP operates on two name spaces and introduces several new network
elements. This section provides high-level definitions of the LISP elements. This section provides high-level definitions of the LISP
name spaces and network elements and as such, it must not be name spaces and network elements and as such, it must not be
considered as an authoritative source. The reference to the considered as an authoritative source. The reference to the
authoritative document for each term is included in every term authoritative document for each term is included in every term
description. description.
Legacy Internet: The portion of the Internet that does not run LISP Legacy Internet: The portion of the Internet that does not run LISP
 End of changes. 15 change blocks. 
38 lines changed or deleted 48 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/