Folks, this is the first example of having use-case documents IANA request bits they need in LISP control messages. So the m-bit is being unspecified in 6833bis and specified in LISP-MN.
Cheers, Dino > Begin forwarded message: > > From: [email protected] > Subject: [lisp] I-D Action: draft-ietf-lisp-mn-03.txt > Date: October 2, 2018 at 5:24:10 PM PDT > To: <[email protected]> > Cc: [email protected] > Reply-To: [email protected] > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Locator/ID Separation Protocol WG of the > IETF. > > Title : LISP Mobile Node > Authors : Dino Farinacci > Darrel Lewis > David Meyer > Chris White > Filename : draft-ietf-lisp-mn-03.txt > Pages : 23 > Date : 2018-10-02 > > Abstract: > This document describes how a lightweight version of LISP's ITR/ETR > functionality can be used to provide seamless mobility to a mobile > node. The LISP Mobile Node design described in this document uses > standard LISP functionality to provide scalable mobility for LISP > mobile nodes. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-lisp-mn/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-lisp-mn-03 > https://datatracker.ietf.org/doc/html/draft-ietf-lisp-mn-03 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-mn-03 > > > 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/ > > _______________________________________________ > lisp mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
