Mike, I have cc’ed the LISP WG in this response. Thanks for providing the active assignments.
As a member of the LISP WG, I would like to vote for an update to RFC 7955 to have the 2001:5::/32 block stay allocated until 2022. Thanks Mike. Dino > On Aug 2, 2019, at 2:33 AM, RIPE NCC Support <[email protected]> wrote: > > ##- Please type your reply above this line -## > Ticket (202719) has been updated. To add additional comments, reply to this > email. > > Mike Petrusha (RIPE NCC Support) > Aug 2, 11:33 CEST > > Dear Dino, > > We sent a number of e-mails to LISP WG and received no reply still. > > We are not sure if this reply will appear on the mailing list, if not, could > you please forward it there. > > With regards to the questions about number of assignments: > as you can see at > https://apps.db.ripe.net/db-web-ui/#/query?searchtext=-rMT%20inet6num%202001:5::%2F32 > there are currently fouractive registrations within 2001:5::/32 > > Also, from https://www.ripe.net/ripe/mail/archives/lisp-announce/ you can see > that another five assignments existed in the past and have either expired or > were returned. > > ----- Forwarded message ----- > > Date: Tue, 30 Jul 2019 09:34:31 +0200 > From: "RIPE NCC" <[email protected]> > To: Deborah Brungard <[email protected]>, > Luigi Iannone <[email protected]>, > Joel Halpern <[email protected]>, > Padma Pillay-Esnault <[email protected]>, > LISP WG <[email protected]> > Subject: LISP EID assignments from 2001:5::/32 > > > 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 > > > > farinacci > Aug 1, 19:00 CEST > > I am still using this block but RIPE wants to remove it per IETF > recommendations. Should we update RFC 7955 to indicate the “experiment” is > still continuing? > > Dino > > > Begin forwarded message: > > > > From: RIPE NCC Support <[email protected]> > > Subject: #202719 - Re: LISP EID prefix 2001:5:3::/48 > > Date: August 1, 2019 at 5:09:09 AM PDT > > To: farinacci <[email protected]> > > Reply-To: RIPE NCC Support <[email protected]> > > > Mike Petrusha (RIPE NCC Support) > Aug 1, 14:09 CEST > > Dear Colleagues, > > The RIPE NCC have assigned LISP EID prefix 2001:5:3::/48 to lispers.net on > 2016-11-16. > > The assigned prefix will be removed on 31 August 2019. > > According to 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." > > > -- > Sincerely, > > Mike Petrusha > RIPE NCC > > > This email is a service from RIPE NCC Support. > [PMZV6Q-QO6Q] _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
