[lisp] RFC 6834bis

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 15 May 2018 14:19 UTC

To: "lisp@ietf.org" <lisp@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <0d7fde71-c672-cc24-e523-8383731c5589@joelhalpern.com>
Date: Tue, 15 May 2018 10:19:47 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/60oYALk1NN-mupF5viQCHjXAGL8>
Subject: [lisp] RFC 6834bis
Precedence: list

Luigi notied that there is one more document that our PS set depends on.
RFC 6834: Locator/ID Separation Protocol (LISP) Map-Versioning

Since we will need to move this to PS, the rules prohibit us from simply 
doing a downref.

As such, unless our AD tells us we can't expedite this, the plan is:

Luigi will prepare draft-iannone-lisp-rfc6834bis.

As soon as he posts it, I will issue a 4 week joint adoption and last 
call.  We think this one is dead simple and as such there will be no 
problems with it.

   -- We will need to see strong support from the working group for 
advancing it.
   -- small errors can be fixed as part of this
   -- If someone has problems with our doing this, they can object and 
we will slow it all down.  In particular, if there turn out to be hard 
spots where it is not technically simple, then we have to slow down and 
do it right.

Assuming it completes the 4 week call without issues, Luigi will issue 
any necessary revisions, I will do a shepherd writeup, and we will add 
it to the stack of things being advanced.

If someone sees a problem with this plan, please speak up.
Yours,
Joel

[lisp] RFC 6834bis Joel M. Halpern
Re: [lisp] RFC 6834bis Dino Farinacci