Hi, 830 and 831 udp ports are de-assigned. As for the others what made me comment was the abstract that says this document release unused ports. The introduction which say “several” so I assumed that this is a list of the unused ones mostly because of the third paragraph that say the document release this unused assignments. Again, this is just what I understood from the abstract and introduction sections and why I made the comment. You can keep or change since the important part is the iana actions which are ok.
Roni On Tue, 8 Jul 2025 at 8:38 <[email protected]> wrote: > Hi Roni, > > > > Aah, I see. That sentence is actually part of a context paragraph that > lists examples of assigned port numbers. That text also cites 830 which we > don’t de-assign, etc. > > > > CURRENT: > > The "Service Name and Transport Protocol Port Number" registry > > [IANA-SERVICE] records several NETCONF-related port and service name > > assignments such as 830 for NETCONF over Secure Shell (SSH) > > [RFC6242], 831 for NETCONF over the Blocks Extensible Exchange > > Protocol (BEEP) [RFC4744], 832 for NETCONF over the Simple Object > > Access Protocol (SOAP) [RFC4743], 4334 for NETCONF Call Home > > [RFC8071], and 6513 for NETCONF over Transport Layer Security (TLS) > > [RFC7589][I-D.ietf-netconf-over-tls13]. > > > > We may delete the examples if this is confusing (i.e., starting from “such > as”), but I’m afraid we will lose characterization of “several” in that > sentence. Will think about this. > > > > Thank you. > > > > Cheers, > > Med (as author) > > > > *De :* Ron Even <[email protected]> > *Envoyé :* mardi 8 juillet 2025 00:52 > *À :* BOUCADAIR Mohamed INNOV/NET <[email protected]> > *Cc :* [email protected]; [email protected]; > [email protected]; [email protected] > *Objet :* Re: draft-ietf-netconf-port-numbers-03 ietf last call Genart > review > > > > > > Hi > > The following text in the introduction section > > > > 4334 for NETCONF Call Home [RFC8071 > <https://www.rfc-editor.org/rfc/rfc8071>], and 6513 for NETCONF over > Transport Layer Security (TLS) [RFC7589 > <https://www.rfc-editor.org/rfc/rfc7589>][I-D.ietf-netconf-over-tls13 > <https://datatracker.ietf.org/doc/html/draft-ietf-netconf-over-tls13-04>]. > > However, many of these assignments are for a transport protocol (i.e., > UDP) for which the requesting application does not apply. Also, many of the > assignments are for protocols that are not deployed and were tagged as > Historic: [RFC4743 <https://www.rfc-editor.org/rfc/rfc4743>] and [RFC4744 > <https://www.rfc-editor.org/rfc/rfc4744>]. > > This document de-assigns these unused port numbers. > > These two ports are mentioned here but based on the rest of the document I > don’t see why > > Roni > > > > On Mon, 7 Jul 2025 at 9:15 <[email protected]> wrote: > > Hi Roni, > > Thank you for the review. > > > The introduction section mentions ports 4334 and 6513 as candidates > > for release but the IANA considerations section do not mention them. > > Why are they in the introduction if not released? > > Can you please clarify which part of the text you are referring to? > > The only mention I see is the one where we list current assignments, which > is OK. > > Thanks. > > Cheers, > Med (as author) > > > -----Message d'origine----- > > De : Roni Even via Datatracker <[email protected]> > > Envoyé : lundi 7 juillet 2025 07:20 > > À : [email protected] > > Cc : [email protected]; last- > > [email protected]; [email protected] > > Objet : draft-ietf-netconf-port-numbers-03 ietf last call Genart > > review > > > > > > Document: draft-ietf-netconf-port-numbers > > Title: NETCONF Transport Port Numbers > > Reviewer: Roni Even > > Review result: Ready with Issues > > > > I am the assigned Gen-ART reviewer for this draft. The General Area > > Review Team (Gen-ART) reviews all IETF documents being processed by > > the IESG for the IETF Chair. Please treat these comments just like > > any other last call comments. > > > > For more information, please see the FAQ at > > > > <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw > <https://w/> > > iki.ietf.org%2Fen%2Fgroup%2Fgen%2FGenArtFAQ&data=05%7C02%7Cmohamed.b > > oucadair%40orange.com%7Ca35a4424051b45edc24108ddbd15eb6b%7C90c7a20af > > 34b40bfbc48b9253b6f5d20%7C0%7C0%7C638874624028652238%7CUnknown%7CTWF > > pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI > > sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=4Tks3oXGIpS%2F6 > > 3DjgKwLxnZzPEfW0eg5u2GdCQiO9tA%3D&reserved=0>. > > > > Document: draft-ietf-netconf-port-numbers-03 > > Reviewer: Roni Even > > Review Date: 2025-07-06 > > IETF LC End Date: 2025-07-15 > > IESG Telechat date: Not scheduled for a telechat > > > > Summary: > > The document is ready for publication as a standard track RFC with a > > minor issue Major issues: > > > > Minor issues: > > The introduction section mentions ports 4334 and 6513 as candidates > > for release but the IANA considerations section do not mention them. > > Why are they in the introduction if not released? > > > > Nits/editorial comments: > > > > > ____________________________________________________________________________________________________________ > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez > recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and > delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > ____________________________________________________________________________________________________________ > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > >
_______________________________________________ Gen-art mailing list -- [email protected] To unsubscribe send an email to [email protected]
