Document Action: Management Guidelines for the Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block to Historic

The IESG <iesg-secretary@ietf.org> Fri, 06 October 2023 15:30 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: Management Guidelines for the Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block to Historic
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, draft-ietf-lisp-eid-block-mgmnt@ietf.org, draft-ietf-lisp-eid-block@ietf.org, iana@iana.org, lisp-chairs@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <169660623041.37056.12977529219349205706@ietfa.amsl.com>
Date: Fri, 06 Oct 2023 08:30:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/qlg00KUyf1RT-fCkR1Wnvwk-_hI>

The IESG has approved changing the status of the following document:
- Management Guidelines for the Locator/ID Separation Protocol (LISP)
Endpoint Identifier (EID) Block
  (rfc7955) to Historic

This document action is documented at:
https://datatracker.ietf.org/doc/status-change-lisp-eid-block-to-historic/

A URL of the affected document is:
https://datatracker.ietf.org/doc/rfc7955/

Status Change Details:

RFC 7954 created an experimental IPv6 prefix, namely 2001:5::/32, to be used
as an Endpoint-IDentifier (EID) space for the Locator/Identifier Separation
Protocol (LISP).  The reserved address space was requested for an initial
3-year period starting in September 2016 (until September 2019), with an
option to extend it by three years (until September 2022) upon the decision
of the IETF. RFC 7955 describes a framework for the management of the prefix
created by RFC 7954. As described in RFC 7955, RIPE NCC volunteered to
provide registration service during the experiment (up to 2022 at the latest).

The initial experiment was supposed to last three years, until September 2019.
The option to extend the experiment to three more years was subject to the
requirements written in section 10 of RFC 7954:

   Following the policies outlined in
   [RFC5226], upon IETF Review, the decision should be made on whether
   to have a permanent EID block assignment by September 2019.  If no
   explicit action is taken or, if the IETF Review outcome is that it is
   not worth having a reserved prefix as a global EID space, the whole
   /32 will be taken out from the "IANA IPv6 Special-Purpose Address
   Registry" and put back in the free pool managed by IANA.

In August 2019 RIPE NCC contacted the LISP WG asking if any action was
ongoing concerning the extension of the experiment. The LISP WG concluded
that very few requests have been made during three years and there was no
compelling reason to extend the experiment. No further action has been taken
by the LISP WG or the IETF. As such, in accordance with Section 10 of RFC
7954, RIPE NCC de-registered the existing assignments and IANA put the prefix
back in the free pool (removing the entry from
https://www.iana.org/assignments/iana-ipv6-special-registry). Such an action
did not have any impact on other existing LISP specifications, hence moving
these documents to historic status will as well have no consequences.
Further, LISP WG is working on moving experimental specifications for which
sufficient experience and deployment is available to the status of "proposed
standard", updating them as needed.

At this point, RFC 7954 and RFC 7955 refer to a prefix that does not exists
anymore and is not used by any LISP document. As such it make sense to move
both documents to the status of "HISTORIC". This note, associated with the
status change of the two RFCs will allow to keep track of the LISP EID prefix
experiment.

Personnel

   Jim Guichard is the responsible Area Director.

Document Action: Management Guidelines for the Lo… The IESG