On 10/16/2017 8:01 PM, Alia Atlas wrote:
I don't believe that a document has to be Standards Track to create a
registry that will require Standards Track going forward.
It is a bit unusual, but I don't see a process problem.
If our documents get converted to Standards Track, this won't be a
On 6/25/2017 6:54 AM, Dan Romascanu wrote:
Reviewer: Dan Romascanu
Review result: Ready with Issues
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat these comments ju
Thanks for your review.
On 8/9/2016 4:41 PM, Paul Kyzivat wrote:
it will be unlikely that a new implementer, schooled in the subject
matter, will be able to create a correct implementation.
The material in this draft describes running code. There are at least
two independent, interoperable
I just posted the -09 version of the draft, which has the requested
changes (including most of Meral's suggestions and also including the
typos pointed out today by Martin).
I changed the start of the mLDP range to 0x43; the choice of 0x41 is
also defensible (as Martin has argued), but it is p
