Skip to main content

IETF Last Call Review of draft-ietf-netconf-port-numbers-03
review-ietf-netconf-port-numbers-03-tsvart-lc-tuexen-2025-07-16-00

Request Review of draft-ietf-netconf-port-numbers
Requested revision No specific revision (document currently at 07)
Type IETF Last Call Review
Team Transport Area Review Team (tsvart)
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 Michael Tüxen
State Completed
Request IETF Last Call review on draft-ietf-netconf-port-numbers by Transport Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/tsv-art/n8g-lARZBIpT-Gay9J7EMbg4p3I
Reviewed revision 03 (document currently at 07)
Result Ready w/nits
Completed 2025-07-16
review-ietf-netconf-port-numbers-03-tsvart-lc-tuexen-2025-07-16-00
This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

I have only found the following three nits:

1. The abstract mentions that port number assignments that not stood the
   test of time are removed. However, the introduction mentions that also
   port number assignments are removed for which the protocols do not
   apply (like SSH/UDP).
   For consistency, I would list both motivations for assignment removal
   in the abstract and introduction.

2. The introduction mentions that
   "... many of these assignments are for a transport protocol (i.e., UDP)
    for which the requesting application does not apply"
   and then the document actually removes one.
   Maybe the use of "many" can be improved to be more precise.

3. The introduction mentions that
   "... many of the assignments are for protocols that are not deployed
    and were tagged as Historic"
   and then the document actually removes three.
   Maybe the use of "many" can be improved to be more precise.