Subject: Re: [lisp] #202067 - LISP EID assignments from 2001:5::/32

From: Dino Farinacci <[email-masked]>
Date: Thu, 15 Aug 2019 09:35:12 -0700

I am cc’ing the LISP WG which you did not have on your To: list orignally.

Dino

> On Aug 15, 2019, at 4:42 AM, RIPE NCC Support <[email-masked]> wrote:
> 
> ##- Please type your reply above this line -##
> You are registered as a CC on this ticket (202067). Reply to this email to add a comment to the request.
> 
> 
> Mike Petrusha (RIPE NCC Support) 
> Aug 15, 13:42 CEST
> 
> Dear LISP WG,
> 
> The RIPE NCC received no formal reply from the IETF.
> Considering this and also based on the recent emails exchanged in the LISP WG on this topic, we understand that no formal decision was made as mentioned in RFC 7954: LISP EID Block
> 
> " By the end of the first period, the IETF will provide a decision on
>   whether to transform the prefix into a permanent assignment or to put
>   it back in the free pool"
> Therefore, it is our current understanding that we need to act in accordance with https://tools.ietf.org/html/rfc7954#section-7
> "  If no explicit action is carried out by the end of the experiment (by
>    September 2019), it is automatically considered that there was not
>    sufficient interest in having a permanent allocation; therefore, the
>    address block will be returned to the free pool."
> and also based on RFC 7955, https://tools.ietf.org/html/rfc7955
> "According to the 3+3 year experimentation plan, defined in
> [RFC 7954], all registrations MUST end by August 2019, unless
> the IETF community decides to grant a permanent LISP EID
> address block."
> the RIPE NCC will complete de-registration of four existing LISP EID assignments within 2001:5::/32 in August 2019 and will then return 2001:5::/32 to the IANA in September 2019.
> 
> --
> Mike Petrusha
> RIPE NCC
> 
> 
> 
> Mike Petrusha (RIPE NCC Support) 
> Aug 1, 14:16 CEST
> 
> Dear Colleagues,
> 
> We await your reply with regards to 2001:5::/32 LISP EID prefix
> --
> Sincerely,
> 
> Mike Petrusha
> RIPE NCC
> 
> 
> 
> Mike Petrusha (RIPE NCC Support) 
> Jul 30, 09:34 CEST
> 
> Dear LISP WG,
> 
> This e-mail is from the RIPE NCC, the Internet Registry in Europe.
> 
> The RIPE NCC provides temporary LISP EID assignments from LISP EID prefix 2001:5::/32 in accordance with RFC 7955: LISP EID Block Management, https://tools.ietf.org/html/rfc7955
> 
> We are contacting you as we are approaching August 2019, at which point we need to start removing existing LISP EID assignments within 2001:5::/32 (unless IETF made a decision to extend this period).
> 
> Following RFC 7955, https://tools.ietf.org/html/rfc7955
> "According to the 3+3 year experimentation plan, defined in
> [RFC 7954], all registrations MUST end by August 2019, unless
> the IETF community decides to grant a permanent LISP EID
> address block."
> 
> In accordance with RFC 7954: LISP EID Block
> https://tools.ietf.org/html/rfc7954#section-6
> "  IANA allocated the requested address space in September 2016 for a
>    duration of 3 (three) years (through September 2019), with an option
>    to extend this period by 3 (three) more years (until September 2022).
>    By the end of the first period, the IETF will provide a decision on
>    whether to transform the prefix into a permanent assignment or to put
>    it back in the free pool..."
> 
> Could you please let us know whether such decision was made by the IETF?
> 
> 
> According to https://tools.ietf.org/html/rfc7954#section-7
> "  In order to trigger the process for a permanent allocation, a
>    document is required.  Such a document has to articulate the
>    rationale for why a permanent allocation would be beneficial.  More
>    specifically, the document has to detail the experience gained during
>    experimentation and all of the technical benefits provided by the use
>    of a LISP-specific prefix. "
> 
> Could you please let us know if such document was created?
> 
> 
> According to https://tools.ietf.org/html/rfc7954#section-7
> "  If no explicit action is carried out by the end of the experiment (by
>    September 2019), it is automatically considered that there was not
>    sufficient interest in having a permanent allocation; therefore, the
>    address block will be returned to the free pool."
> 
> Based on this, the RIPE NCC is ready to proceed with removing existing LISP EID assignments within 2001:5::/32 in August 2019 (as defined by RFC 7955) and returning 2001:5::/32 to the IANA in September 2019 (as defined by RFC 7954).
> 
> We await your reply.
> 
> --
> Sincerely,
> 
> Mike Petrusha
> RIPE NCC
> 
> 
> This email is a service from RIPE NCC Support.
> [R5DPD5-K8OP]