Kent, I have not heard a strong requirement to have the open issue fixed in this version of the RFC. We would therefore like to defer it to a bis document.
I will wait for the LC to complete, and update the draft to address all the comments received during the LC. Thanks. > On Jan 17, 2018, at 3:33 PM, Kent Watsen <[email protected]> wrote: > > > H Mahesh, > >>> - There is an open issue in the document (section 8) - are we going >>> to resolve that during WG last call or is this a leftover? >> >> This will be resolved in the next version of the module. It is >> documented under Issues tab in GitHub. Should we remove it from >> the draft? > > Most of Juergen's comments are editorial in nature and can truly be handled > as part of the LC process, but this open issue has me worried, as it may > result in a significant technical change. > > What will it take to close this open issue? Is it just a matter of the > getting the WG to agree that it's not an issue, or do we already know that it > is a real issue and only the solution is pending? > > Thanks, > Kent > > > > Mahesh Jethanandani [email protected] _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
