Hello, By seeing Alberts presentation on SFC today I was just thinking that we could split 6830 in two documents.
One document to present the data-plane (mostly Sec 5). One document to present the control-plane (mostly Sec 6). As Albert said the mapping system is generic (with LCAF). Therefore it would make it more logical (to me at least) to have a document to strictly talk about the mapping system and it would increase the appeal of the mapping system by not requiring people to care about the LISP encapsulation if they only need the mapping system function. Cheers, Damien Saucez On 27 Oct 2015, at 01:25, Joel M. Halpern <[email protected]> wrote: > It seemed to us that there was likely some confusiona bout how we expect to > handle the revision of RCC 6830. The following is what we currently expect. > > Once we have a new charter approved, the chairs will appoint an editor for > the revision of rfc6830. That may be one of the existing authors, or a new > person. We will ask for volunteers. > > Once we have an author, they will submit a starting ID called > draft-ietf-lisp-rfc6830bis-00 which will be identical in content to the > existing RFC. That may require assistance from the RFC Editor to ensure that > we get all the changes they made during final edit. > > At that point, we will use the trouble ticket system to record issues that > people bring up. We will also discuss on the list what changes we wish to > make according to the charter. Things will tehn proceed in the usual > fashion, using the trouble ticket system to help make sure we do not drop any > of the issues. > > Yours, > Joel & Luigi > > _______________________________________________ > lisp mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lisp _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
