I am presuming your phrasing is slightly misleading. If you
individually are the only user of the block, I do not see how we can
justify asking RIPE to continue the assignment.
Yours,
Joel
On 8/1/2019 1:00 PM, Dino Farinacci wrote:
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] <mailto:[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] <mailto:[email protected]>>
*Reply-To: *RIPE NCC Support <[email protected] <mailto:[email protected]>>
##- 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 1, 14:09 CEST
Dear Colleagues,
The RIPE NCC have assigned LISP EID prefix 2001:5:3::/48 tolispers.net
<http://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 <https://tools.ietf.org/html/rfc7954>], 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
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
