]> Telecom ParisTech

France ggx@gigix.net

Bredbandsfylket Troms

Norway rogerj@gmail.com

Virtualized, LLC

United States drc@virtualized.org

Asia Pacific Network Information Centre (APNIC)

Australia gih@apnic.net

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.

The Locator/ID Separation Protocol (LISP ) and related mechanisms (, , , , , , ) 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. 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 . 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.

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 .

This document does not introduce any new terms related to the set of LISP Specifications (, , , , , , , ), but assumes that the reader is familiar with the LISP terminology. provides an introduction to the LISP technology, including its terminology.

The request for registration of EID prefixes MUST be done under the following policies: EID prefixes are made available in the reserved space on a temporary basis and for experimental uses. The requester of an experimental prefix MUST provide a short description of the intended use or experiment that will be carried out (see ). If the prefix will be used for activities not documented in the original description, renewal of the registration may be denied. EID prefix registrations MUST be renewed on a regular basis to ensure their use by active participants in the experiment. The registration period is 12 months. A renewal SHOULD NOT cause a change in the EID prefix registered in the previous request. The conditions of registration renewal are to be the same as the conditions of the first EID prefix registration request. It is preferable that EID prefixes whose registrations have expired not be reused. When an EID prefix registration is removed from the registry, then the reuse of the EID prefix in a subsequent registration on behalf of a different end user should be avoided where possible. If the considerations of overall usage of the EID block prefix requires reuse of a previously registered EID prefix, then a minimum delay of at least one week between removal and subsequent registration SHOULD be applied by the registry operator. When the reserved experimental LISP EID block expires, all EID prefix registrations expire as well. The further disposition of these prefixes and the associated registry entries are to be specified in the announcement of the cessation of this experiment.

All EID prefix registrations MUST satsify the following requirements: All EID prefix registrations MUST use a globally unique EID prefix. The EID prefix registration information, as specified in , MUST be collected upon initial registration and renewal, and made publicly available through interfaces allowing both the retrieval of specific registration details (search) and the enumeration of the entire registry contents (e.g., RDAP (), WHOIS, HTTP, or similar access methods). The registry operator MUST permit the delegation of EID prefixes in the reverse DNS space to holders of registered EID prefixes. Anyone can obtain an entry in the EID prefix registry, on the understanding that the prefix so registered is for the exclusive use in the LISP experimental network, and that their registration details (as specified in ) are openly published in the EID prefix registry.

The following is a basic request template for prefix registration to ensure a uniform process. This template is inspired by IANA's online "Private Enterprise Number (PEN) Request" form <http://pen.iana.org/pen/PenApplication.page>. Note that all details in this registration become part of the registry and will be published in the LISP EID Prefix Registry managed by RIPE NCC. The EID Prefix Request template MUST at a minimum contain: Organization (In the case of individuals requesting an EID prefix, this section can be left empty) Organization Name Organization Address Organization Phone Organization Website Contact Person (Mandatory) Name Address Phone Fax (optional) Email EID Prefix Request (Mandatory) Prefix Size Expressed as an address prefix length. Prefix Size Rationale Lease Period Note well: All EID Prefix registrations will be valid until the earlier date of 12 months from the date of registration or August 2019. All registrations may be renewed by the applicant for further 12-month periods, ending on August 2019. According to the 3+3 year experimentation plan, defined in , all registrations MUST end by August 2019, unless the IETF community decides to grant a permanent LISP EID address block. In the latter case, registrations following the present document policy MUST end by August 2022 and a new policy (to be decided -- see ) will apply thereafter. Experiment Description Experiment and Deployment Description Interoperability with Existing LISP Deployments Interoperability with Legacy Internet Reverse DNS Servers (Optional) Name Server Name Name Server Address Name Server Name Name Server Address (Repeat if necessary)

The policy outlined in the present document is tied to the existence of the experimental LISP EID block requested in and is valid until August 2019. If the IETF decides to transform the block into a permanent allocation, the usage period reserved for the LISP EID block will be extended for three years (until August 2022) to allow time for the IETF to define, following the policies outlined in , the final size of the EID block and create a transition plan, while the policy in the present document will still apply. Note that, as stated in , the transition of the EID block into a permanent allocation has the potential to pose policy issues (as recognized in , Section 4.3); hence, discussion with the IANA, the Regional Internet Registry (RIR) communities, and the IETF community will be necessary to determine the appropriate policy for permanent EID prefix management, which will be effective after August 2022.

This document does not introduce new security threats in the LISP architecture nor in the Legacy Internet architecture. For accountability reasons and in line with the security considerations in , each registration request MUST contain accurate information about the requesting entity (company, institution, individual, etc.) and valid and accurate contact information of a referral person (see ).

IANA allocated the following IPv6 address block for experimental use as the LISP EID prefix : Address Block: 2001:5::/32 Name: EID Space for LISP RFC: Further details are at: www.iana.org/assignments/iana-ipv6-special-registry To grant requesting organizations and individuals exclusive use of EID prefixes out of this reserved block (limited to the duration of the LISP experiment as outlined in ), there is an operational requirement for an EID registration service. Provided that the policies and requirements outlined in Sections , , and are satsified, EID prefix registration is accorded based on a "First Come First Served" basis. There is no hard limit to the number of registrations an organization or individual can submit, as long as the information described in is provided, in particular point 4: "Experiment Description". For the duration defined in , RIPE NCC will manage the LISP EID prefix as described herein. Therefore, this document has no IANA actions.

RIPE NCC will provide the registration service following the EID Prefix Registration Policy () and the EID Prefix Registration Requirements () provided in this document. The request form provided by RIPE NCC will include at least the information from the template in . RIPE NCC will make all received requests publicly available. While this document does not suggest any minimum allocation size; RIPE NCC is allowed to introduce such a minimum size for management purposes.

&rfc2119; &rfc5226; &rfc2860; &rfc6830; &rfc6831; &rfc6832; &rfc6833; &rfc6834; &rfc6835; &rfc6836; &rfc6837; &rfc7020; &DraftRDAP;

Thanks to A. Retana, J. Arkko, P. Yee, 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&nbhy;13-INFR-0009 LISP-Lab Project <www.lisp-lab.org> and the EIT KIC ICT&nbhy;Labs SOFNETS Project.