Last Call Review of draft-ietf-netconf-netconf-client-server-37
review-ietf-netconf-netconf-client-server-37-secdir-lc-migault-2024-09-25-00
| Request | Review of | draft-ietf-netconf-netconf-client-server-37 |
|---|---|---|
| Requested revision | 37 (document currently at 41) | |
| Type | IETF Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2024-08-30 | |
| Requested | 2024-08-15 | |
| Requested by | Mahesh Jethanandani | |
| Authors | Kent Watsen | |
| I-D last updated | 2025-12-17 (Latest revision 2025-12-04) | |
| Completed reviews |
Yangdoctors IETF Last Call review of -04
by Andy Bierman
(diff)
Secdir IETF Last Call review of -37 by Daniel Migault (diff) Yangdoctors IETF Last Call review of -37 by Andy Bierman (diff) Opsdir IETF Last Call review of -37 by Tim Chown (diff) Tsvart IETF Last Call review of -37 by Lars Eggert (diff) Genart IETF Last Call review of -37 by Ines Robles (diff) |
|
| Comments |
This document was meant to be a part of a cluster of 9 documents, 7 of which form the "stack" of groupings used by this draft. Those "stack" groupings roughly map to the different layers of the OSI 7 layer stack, with this draft coming in at the application layer. References to those documents can be found in the document. |
|
| Assignment | Reviewer | Daniel Migault |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-netconf-netconf-client-server by Security Area Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/secdir/7Wbonu7iO_RWu449yqXBif6zios | |
| Reviewed revision | 37 (document currently at 41) | |
| Result | Ready | |
| Completed | 2024-09-25 |
review-ietf-netconf-netconf-client-server-37-secdir-lc-migault-2024-09-25-00
Hi, I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. Document editors and WG chairs should treat these comments just like any other last call comments. The use of security protocols is left to specific YANG modules, so the security considerations remain quite generic and maybe the client and server module security consideration might be even grouped in a single section. yours, Daniel