Dear all,
I know that this draft is not yet on my table, but in order to speed up
the process, I read v3.
- Editorial: I see many instances of (see term) or (see terms).
This doesn't add any value IMO.
If there are some chance for misinterpretation of those terms,
capitalize the terms specified in the terminology section.
- Any reason why the "backwards compatibility" (section 3) is not
numbered as a requirement in section 4? I.e. a new requirement 5. Or is
it because it's a special requirement?
Numbering all the requirements might ease the comparison of the 3
different proposed solutions.
- There is a requirement in asynchronous configuration operations
definition:
Once applied, there MUST be a mechanism for the client
to determine when the request has completed processing and
whether the intended config is now fully effective or there are
any errors from applying the configuration change, which could be
from an asynchronous notification or via a client operation.
Why isn't it a numbered requirement in section 4?
Regards, Benoit
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
