Hi,
I support this draft going to the AD.
Best regards,
-Lori
On 5/20/18 8:17 PM, Joel Halpern 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
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 wrote:
> This starts a 4 week implicit adoption call and explicit last call for
> the LISP Map Versioning
Yeah, if we wanted to take longer we could put in a filename change.
But it doesn't actually matter. (usually, we need the name right so
folks can find the document. I don't think that is a problem in this
case.) I will do what is needed to attach it to the LISP WG page.
Yours,
Joel
On
Note the name of the WG document should be draft-ietf-lisp-rfc6834bis-00 (note
“rfc” added).
Cheers,
Dino
> On May 20, 2018, at 11:17 AM, Joel Halpern wrote:
>
> This starts a 4 week implicit adoption call and explicit last call for the
> LISP Map Versioning draft
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