Hi,
Thank you all for the good input on this thread.
With the understanding that a 00 working group document is a starting
point for the working group rather than a document that is ready for
last call - we believe there is sufficient support to adopt this
document as a starting point for the requirements we wish to address on
this topic.
It is clear that there is still work to be done on this document before
we can declare consensus on it and, not surprisingly, that there is more
work to be done on the solution.
Authors,
Please resubmit this document as draft-ietf-netmod-yang-revision-reqs-00
with the only change being the name and publication date. The -01
version should focus on resolving issues raised during adoption. Of
course the document is subject to normal WG input and processing.
Please note the 'file' name change -this is to indicate that the
requirements are not presupposing a specific solution. It is also
consistent with how versioning is defined within the document currently.
Note: we would like to try to continue the list discussion in next
week's session and ask the Authors/DT to summarize issues raised during
the adoption call and lead a discussion to help resolve these issues.
Thank you,
Lou (and Kent and Joel)
On 3/13/2019 4:22 PM, Kent Watsen wrote:
Seeing as how we all need to read this draft anyways, in preparation
for our meeting in Prague, it seems like a good time for this poll.
Thusly, this email begins a 1-week adoption poll for:
https://tools.ietf.org/html/draft-verdt-netmod-yang-versioning-reqs-02
Please voice your support or objections before March 20.
Note that this draft defines *requirements* and its intended status is
"Informational." I believe that it is good for WGs to formalize
requirements, even taking such drafts thru Last Call, in order to
ensure consensus on the requirements. This is the "adoption" call, to
ascertain if the WG agrees with that statement; if adopted, a separate
"last call" will be issued to ensure to correctness of the draft's
content.
Kent (and Lou and Joel)
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
