Dear chairs, all, FWIW, we submitted a -bis version of 8113 to update the status from Exp to Standard track.
We made some changes to the text published in 8113 that you can track at: https://github.com/boucadair/rfc8113bis/blob/master/wdiff%20rfc8113.txt%20draft-boucadair-lisp-rfc8113bis-00.pdf Please let us know if any action is still required from us. Thank you. Cheers, Med > -----Message d'origine----- > De : [email protected] [mailto:[email protected]] > Envoyé : jeudi 13 septembre 2018 14:51 > À : BOUCADAIR Mohamed IMT/OLN; JACQUENET Christian IMT/OLN > Objet : New Version Notification for draft-boucadair-lisp-rfc8113bis-00.txt > > > A new version of I-D, draft-boucadair-lisp-rfc8113bis-00.txt > has been successfully submitted by Mohamed Boucadair and posted to the > IETF repository. > > Name: draft-boucadair-lisp-rfc8113bis > Revision: 00 > Title: Locator/ID Separation Protocol (LISP): Shared Extension > Message & IANA Registry for Packet Type Allocations > Document date: 2018-09-13 > Group: Individual Submission > Pages: 5 > URL: https://www.ietf.org/internet-drafts/draft-boucadair-lisp- > rfc8113bis-00.txt > Status: https://datatracker.ietf.org/doc/draft-boucadair-lisp- > rfc8113bis/ > Htmlized: https://tools.ietf.org/html/draft-boucadair-lisp-rfc8113bis- > 00 > Htmlized: https://datatracker.ietf.org/doc/html/draft-boucadair-lisp- > rfc8113bis > > > 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. It also defines a registry for LISP Packet Type > allocations. > > This document obsoletes RFC 8113. > > > > > 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. > > The IETF Secretariat _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
