I went again through RFC6834 while I was reviewing RFC6830/33bis. I think it can be sent to the AD.
Thanks, Alberto On Sun, May 20, 2018 at 11:18 AM Joel Halpern <[email protected]> wrote: > This starts a 4 week implicit adoption call and explicit last call for > the LISP Map Versioning draft revision with the purpose of moving this > work onto the standards track. > > Please read the draft. > And then speak up as to whether you agree or disagree with us sending > this document to our AD for IETF LC and IESG review as a Proposed > Standard RFC. > > We will allow 4 weeks for this call, ending on Sunday, June 17. > > Thank you, > Joel > > PS: I will try to find a way to mark this suitably in the data tracker, > but I suspect it does not have a state to reflect this. > > > -------- Forwarded Message -------- > Subject: I-D Action: draft-iannone-6834bis-00.txt > Date: Sun, 20 May 2018 11:09:40 -0700 > From: [email protected] > Reply-To: [email protected] > To: [email protected] > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Locator/ID Separation Protocol (LISP) > Map-Versioning > Authors : Luigi Iannone > Damien Saucez > Olivier Bonaventure > Filename : draft-iannone-6834bis-00.txt > Pages : 19 > Date : 2018-05-20 > > Abstract: > This document describes the LISP (Locator/ID Separation Protocol) > Map-Versioning mechanism, which provides in-packet information about > Endpoint ID to Routing Locator (EID-to-RLOC) mappings used to > encapsulate LISP data packets. The proposed approach is based on > associating a version number to EID-to-RLOC mappings and the > transport of such a version number in the LISP-specific header of > LISP-encapsulated packets. LISP Map-Versioning is particularly > useful to inform communicating Ingress Tunnel Routers (ITRs) and > Egress Tunnel Routers (ETRs) about modifications of the mappings used > to encapsulate packets. The mechanism is optional and transparent to > implementations not supporting this feature, since in the LISP- > specific header and in the Map Records, bits used for Map-Versioning > can be safely ignored by ITRs and ETRs that do not support or do not > want to use the mechanism. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-iannone-6834bis/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-iannone-6834bis-00 > https://datatracker.ietf.org/doc/html/draft-iannone-6834bis-00 > > > 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. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > I-D-Announce mailing list > [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] > https://www.ietf.org/mailman/listinfo/lisp >
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
