draft-ietf-lisp-eid-block-mgmnt-05.txt   draft-ietf-lisp-eid-block-mgmnt-06.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: January 4, 2016 Bredbandsfylket Troms Expires: February 25, 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
July 3, 2015 August 24, 2015
LISP EID Block Management Guidelines LISP EID Block Management Guidelines
draft-ietf-lisp-eid-block-mgmnt-05.txt draft-ietf-lisp-eid-block-mgmnt-06.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 January 4, 2016. This Internet-Draft will expire on February 25, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
10. Procedures to be followed by RIPE NCC . . . . . . . . . . . . 7 10. Procedures to be followed by RIPE NCC . . . . . . . . . . . . 7
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
12.1. Normative References . . . . . . . . . . . . . . . . . . 8 12.1. Normative References . . . . . . . . . . . . . . . . . . 8
12.2. Informative References . . . . . . . . . . . . . . . . . 8 12.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. LISP Terms . . . . . . . . . . . . . . . . . . . . . 9 Appendix A. LISP Terms . . . . . . . . . . . . . . . . . . . . . 10
Appendix B. Document Change Log . . . . . . . . . . . . . . . . . 12 Appendix B. Document Change Log . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 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
skipping to change at page 8, line 29 skipping to change at page 8, line 29
12. References 12. References
12.1. Normative 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-12 (work in EID Block", draft-ietf-lisp-eid-block-12 (work in
progress), May 2015. 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, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[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, DOI 10.17487/RFC4632,
August 2006, <http://www.rfc-editor.org/info/rfc4632>.
[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. DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
12.2. Informative References 12.2. Informative References
[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,
DOI 10.17487/RFC2860, June 2000,
<http://www.rfc-editor.org/info/rfc2860>.
[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. DOI 10.17487/RFC6830, January 2013,
<http://www.rfc-editor.org/info/rfc6830>.
[RFC6831] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "The [RFC6831] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "The
Locator/ID Separation Protocol (LISP) for Multicast Locator/ID Separation Protocol (LISP) for Multicast
Environments", RFC 6831, January 2013. Environments", RFC 6831, DOI 10.17487/RFC6831,
January 2013, <http://www.rfc-editor.org/info/rfc6831>.
[RFC6832] Lewis, D., Meyer, D., Farinacci, D., and V. Fuller, [RFC6832] Lewis, D., Meyer, D., Farinacci, D., and V. Fuller,
"Interworking between Locator/ID Separation Protocol "Interworking between Locator/ID Separation Protocol
(LISP) and Non-LISP Sites", RFC 6832, January 2013. (LISP) and Non-LISP Sites", RFC 6832, DOI 10.17487/
RFC6832, January 2013,
<http://www.rfc-editor.org/info/rfc6832>.
[RFC6833] Fuller, V. and D. Farinacci, "Locator/ID Separation [RFC6833] Fuller, V. and D. Farinacci, "Locator/ID Separation
Protocol (LISP) Map-Server Interface", RFC 6833, Protocol (LISP) Map-Server Interface", RFC 6833,
January 2013. DOI 10.17487/RFC6833, January 2013,
<http://www.rfc-editor.org/info/rfc6833>.
[RFC6834] Iannone, L., Saucez, D., and O. Bonaventure, "Locator/ID [RFC6834] Iannone, L., Saucez, D., and O. Bonaventure, "Locator/ID
Separation Protocol (LISP) Map-Versioning", RFC 6834, Separation Protocol (LISP) Map-Versioning", RFC 6834,
January 2013. DOI 10.17487/RFC6834, January 2013,
<http://www.rfc-editor.org/info/rfc6834>.
[RFC6835] Farinacci, D. and D. Meyer, "The Locator/ID Separation [RFC6835] Farinacci, D. and D. Meyer, "The Locator/ID Separation
Protocol Internet Groper (LIG)", RFC 6835, January 2013. Protocol Internet Groper (LIG)", RFC 6835, DOI 10.17487/
RFC6835, January 2013,
<http://www.rfc-editor.org/info/rfc6835>.
[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, DOI 10.17487/RFC6836,
January 2013, <http://www.rfc-editor.org/info/rfc6836>.
[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, DOI 10.17487/
RFC6837, January 2013,
<http://www.rfc-editor.org/info/rfc6837>.
[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, DOI 10.17487/
RFC7020, August 2013,
<http://www.rfc-editor.org/info/rfc7020>.
[RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the [RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the
Registration Data Access Protocol (RDAP)", RFC 7481, Registration Data Access Protocol (RDAP)", RFC 7481,
March 2015. DOI 10.17487/RFC7481, March 2015,
<http://www.rfc-editor.org/info/rfc7481>.
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.
skipping to change at page 12, line 16 skipping to change at page 12, line 32
logical next-hop on the overlay network. The primary function of logical next-hop on the overlay network. The primary function of
LISP+ALT routers is to provide a lightweight forwarding LISP+ALT routers is to provide a lightweight forwarding
infrastructure for LISP control-plane messages (Map-Request and infrastructure for LISP control-plane messages (Map-Request and
Map-Reply), and to transport data packets when the packet has the Map-Reply), and to transport data packets when the packet has the
same destination address in both the inner (encapsulating) same destination address in both the inner (encapsulating)
destination and outer destination addresses ((i.e., a Data Probe destination and outer destination addresses ((i.e., a Data Probe
packet). See [RFC6830] for more details. packet). See [RFC6830] for more details.
Appendix B. Document Change Log Appendix B. Document Change Log
Version 06 Posted August 2015.
o Fixed Authors addresses and typo in section 10.
Version 05 Posted July 2015.
o Added explicit text about RIPE NCC providing the registration
service during the temporary experiment.
Version 04 Posted December 2014. Version 04 Posted December 2014.
o Added two clarification sentences to address the comments of E. o Added two clarification sentences to address the comments of E.
Lear and D. Saucez during WG LC. Lear and D. Saucez during WG LC.
Version 03 Posted October 2014. Version 03 Posted October 2014.
o Re-worded the document so to avoid confusion on "allocation" and o Re-worded the document so to avoid confusion on "allocation" and
"assignement". The document now reffers to "registration". As "assignement". The document now reffers to "registration". As
for comments by G. Huston and M. Binderberger. for comments by G. Huston and M. Binderberger.
skipping to change at page 13, line 14 skipping to change at page 13, line 39
policy applies. policy applies.
Version 00 Posted December 2013. Version 00 Posted December 2013.
o Rename of draft-iannone-lisp-eid-block-mgmnt-03.txt. o Rename of draft-iannone-lisp-eid-block-mgmnt-03.txt.
Authors' Addresses Authors' Addresses
Luigi Iannone Luigi Iannone
Telecom ParisTech Telecom ParisTech
France
Email: ggx@gigix.net Email: ggx@gigix.net
Roger Jorgensen Roger Jorgensen
Bredbandsfylket Troms Bredbandsfylket Troms
Norway
Email: rogerj@gmail.com Email: rogerj@gmail.com
David Conrad David Conrad
Virtualized, LLC Virtualized, LLC
USA
Email: drc@virtualized.org Email: drc@virtualized.org
Geoff Huston Geoff Huston
APNIC - Asia Pacific Network Information Center APNIC - Asia Pacific Network Information Center
Australia
Email: gih@apnic.net Email: gih@apnic.net
 End of changes. 25 change blocks. 
20 lines changed or deleted 52 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/