Hi Alvaro, The draft says the following:
IANA is requested to replace the reference to RFC8113<https://tools.ietf.org/html/rfc8113> with the RFC number to be assigned to this document. Which seems reasonable to keep track on the document that created the registry while being aligned with obsoleted RFCs. Cheers, Med De : lisp [mailto:[email protected]] De la part de Alvaro Retana Envoyé : lundi 24 septembre 2018 17:31 À : Luigi Iannone; [email protected] list Cc : [email protected] Objet : Re: [lisp] Call fo adoption of draft-boucadair-lisp-rfc8113bis-01.txt [Speaking as a WG participant.] Hi! I don’t object to the adoption. The main change with respect to rfc8113, that doesn’t seem right to me, is that rfc8113 defined the LISP Packet Types registry, but this document only adds to it. In the weird world of Updating and Obsoleting RFCs, I think this means that we’re left with no document being the originator of the registry. Note that rfc6833bis, which requests that the references from the registry point to it *and* to rfc8113, also doesn’t define the registry (which is the correct thing to do).. My 2c. Alvaro. On September 19, 2018 at 11:05:05 AM, Luigi Iannone ([email protected]<mailto:[email protected]>) wrote: Folks, here is another piece of the work done in our WG that needs to be moved to PS. It is the updated version of RFC 8113, nothing changed just updated coherently with the current status of the other documents. Because this documents is really really short we will have just one week adoption call followed be one week WG Last Call. This email officially starts the one week call for adoption. Please spend 10 minutes having a look at the document and send an email on whether you agree or not to adopt it. Thanks Ciao Luigi Begin forwarded message: From: [email protected]<mailto:[email protected]> Subject: I-D Action: draft-boucadair-lisp-rfc8113bis-01.txt Date: 19 September 2018 at 16:49:31 CEST To: <[email protected]<mailto:[email protected]>> Reply-To: [email protected]<mailto:[email protected]> A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations Authors : Mohamed Boucadair Christian Jacquenet Filename : draft-boucadair-lisp-rfc8113bis-01.txt Pages : 5 Date : 2018-09-19 Abstract: This document specifies a Locator/ID Separation Protocol (LISP) shared message type for defining future extensions and conducting experiments without consuming a LISP packet type codepoint for each extension. This document obsoletes RFC 8113. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-boucadair-lisp-rfc8113bis/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-boucadair-lisp-rfc8113bis-01 https://datatracker.ietf.org/doc/html/draft-boucadair-lisp-rfc8113bis-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-boucadair-lisp-rfc8113bis-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt _______________________________________________ lisp mailing list [email protected]<mailto:[email protected]> https://www.ietf..org/mailman/listinfo/lisp<https://www.ietf.org/mailman/listinfo/lisp>
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
