IETF Last Call Review of draft-ietf-netconf-port-numbers-03
review-ietf-netconf-port-numbers-03-opsdir-lc-dhody-2025-07-14-00
| Request | Review of | draft-ietf-netconf-port-numbers |
|---|---|---|
| Requested revision | No specific revision (document currently at 07) | |
| Type | IETF Last Call Review | |
| Team | Ops Directorate (opsdir) | |
| Deadline | 2025-07-15 | |
| Requested | 2025-07-01 | |
| Requested by | Mahesh Jethanandani | |
| Authors | Mohamed Boucadair | |
| I-D last updated | 2025-12-09 (Latest revision 2025-09-16) | |
| Completed reviews |
Intdir IETF Last Call review of -03
by Bernie Volz
(diff)
Tsvart IETF Last Call review of -03 by Michael Tüxen (diff) Opsdir IETF Last Call review of -03 by Dhruv Dhody (diff) Genart IETF Last Call review of -03 by Roni Even (diff) Artart IETF Last Call review of -03 by Barry Leiba (diff) Secdir Telechat review of -07 by Magnus Nyström |
|
| Assignment | Reviewer | Dhruv Dhody |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-netconf-port-numbers by Ops Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/ops-dir/mqkduCUs8XpwfC8_DWzPQdzjisQ | |
| Reviewed revision | 03 (document currently at 07) | |
| Result | Ready | |
| Completed | 2025-07-14 |
review-ietf-netconf-port-numbers-03-opsdir-lc-dhody-2025-07-14-00
Reviewer: Dhruv Dhody Review Result: Ready (with comments) I have reviewed this document as part of the Operational Directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in the last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. Thanks for doing this cleanup exercise. # IANA While the OLD/NEW style is clear, I am unsure if that should be preserved in the IANA consideration section of the published RFC. Does IANA have any opinion on this style? Also, since RFC 6335 asks the de-assigned port to be marked as Reserved, I am unsure whether leaving the port number empty (as currently done in the new text) will align with the updated IANA registry page. Related question: Should this update also fill in some of the empty fields (like Assignee and Contact), or is it better to keep them empty as done in the past? # Minor The introduction lists two issues - (1) the use of transport protocols (udp), (2) protocols not deployed. On the other hand, the abstract only mentions "(2)". Should it also mention "(1)"? Thanks! Dhruv