[netconf] Re: [IANA #1379432] RE: I-D Action: draft-boucadair-netconf-port-numbers-00.txt

[Andy Bierman <[e-mail]>]

Hi,


On Mon, Oct 7, 2024 at 7:39 AM <[e-mail]> wrote:

> Hi Amanda, all,
>
> Thank you for sharing this feedback.
>
> Great to hear that we don't need an RFC for the fixes in 3.1/3.2/3.3.
>
>

NETCONF has never been designed or approved to run over UDP.
The NETCONF WG requested TCP port numbers only.

I do not understand why the NETCONF WG is requesting UDP port numbers at
this time.




> As a logistic matter, can we use this discussion to trigger the process of
> examining the requested actions? (seeks for AD approvals/experts, etc.)
>
> Cheers,
> Med
>
>
Andy


> PS: I updated the draft to remove 3.4 as that one is not actually needed.
>
> > -----Message d'origine-----
> > De : Sabrina Tanamal via RT <[e-mail]>
> > Envoyé : vendredi 4 octobre 2024 19:55
> > À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>
> > Cc : [e-mail]; [e-mail]; [e-mail];
> > [e-mail]
> > Objet : [IANA #1379432] RE: [netconf] I-D Action: draft-boucadair-
> > netconf-port-numbers-00.txt
> >
> > Hi Med, all,
> >
> > Thanks for the note.
> >
> > Looping in Zahed, the WIT AD, for input.
> >
> > Ordinarily, to release or change registrations made by an RFC,
> > IANA needs either another RFC or directions from the IESG (such as
> > a status change document or, rarely, a decision at a telechat,
> > which might not result in a useful reference beyond a quick
> > statement in the official minutes).
> >
> > It may be possible to take care of most of these without an RFC,
> > though.
> >
> > Section 3.1: RFC 6262 didn't tell us to register the UDP port. If
> > the UDP registration is erroneous, we could ask the AD (as opposed
> > to IESG) approval to confirm that it could be listed as "Reserved"
> > instead (per our standard procedure when only the TCP port is
> > registered). The AD might suggest consulting the port expert
> > before moving forward.
> >
> > Sections 3.2 and 3.3: I see that the status for 4743 and 4744 was
> > changed to "historic" in 2012. Currently, when we see a status
> > change -- I'm not sure when this one came through -- we ask
> > whether any registrations should be marked "deprecated" or
> > "obsolete." We didn't do this at the time. We could also ask the
> > ADs if we could proceed with the actions in Sections 3.2 and 3.3
> > now based on the de-assignment procedure recommendation in Section
> > 8.2 of RFC 6335. As noted above, this may also require
> > consultation with the port expert.
> >
> > Section 3.4: given that draft-ietf-netconf-over-tls13 is in the
> > RFC Editor's queue, is it possible to update that document's IANA
> > Considerations section to refer to RFC 8446 instead of itself?
> >
> > Best regards,
> > Sabrina
> >
> > On Tue Oct 01 10:08:59 2024, [e-mail] wrote:
> > > Hi Kent, all,
> > >
> > > Cool, thanks.
> > >
> > > I don't know whether we actually need a document to "fix" this.
> > I'm
> > > adding IANA and our AD for advice on how to proceed for these
> > matters.
> > >
> > > Cheers,
> > > Med
> > >
> > > > -----Message d'origine-----
> > > > De : Kent Watsen <[e-mail]>
> > > > Envoyé : jeudi 26 septembre 2024 16:37 À : BOUCADAIR Mohamed
> > > > INNOV/NET <[e-mail]> Cc : [e-mail]
> > Objet
> > > > : Re: [netconf] I-D Action: draft-boucadair-netconf-port-
> > > > numbers-00.txt
> > > >
> > > >
> > > > Hi Med,
> > > >
> > > > Thank you for initiating this effort.  Honestly, I didn’t know
> > that
> > > > those unnecessary allocations existed.  It is goodness to
> > release
> > > > unneeded allocations.
> > > >
> > > > Kent / contributor
> > > >
> > > >
> > > > > On Sep 26, 2024, at 8:50 AM, [e-mail]
> > > > wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > An attempt to clean up NETCONF-related assignments,
> > especially
> > > > for those in 0-1023 range. We might consider repurposing some
> > of
> > > > them (e.g., QUIC).
> > > > >
> > > > > Cheers,
> > > > > Med
> > > > >
> > > > > -----Message d'origine-----
> > > > > De : [e-mail] <[e-mail]>
> > Envoyé
> > > > :
> > > > > jeudi 26 septembre 2024 14:40 À : [e-mail]
> > Objet :
> > > > I-D
> > > > > Action: draft-boucadair-netconf-port-numbers-00.txt
> > > > >
> > > > > Internet-Draft draft-boucadair-netconf-port-numbers-00.txt
> > is
> > > > now available.
> > > > >
> > > > > Title:   NETCONF Transport Port Numbers
> > > > > Author:  Mohamed Boucadair
> > > > > Name:    draft-boucadair-netconf-port-numbers-00.txt
> > > > > Pages:   9
> > > > > Dates:   2024-09-26
> > > > >
> > > > > Abstract:
> > > > >
> > > > > This document releases NETCONF-related port number IANA
> > > > assignments
> > > > > that were made for inappropriate transport protocols or for
> > > > an
> > > > > Historic NETCONF-related protocol.
> > > > >
> > > > > Discussion Venues
> > > > >
> > > > > This note is to be removed before publishing as an RFC.
> > > > > Discussion of this document takes place on the Network
> > > > Configuration
> > > > > Working Group mailing list ([e-mail]) which is
> > > > archived at
> > > > >
> > > >
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> > > >
> > Fmailarchive.ietf.org%2Farch%2Fbrowse%2Fnetconf%2F&data=05%7C02%7
> > > >
> > Cmohamed.boucadair%40orange.com%7C4bee2c4bc314482efabb08dcde3c1e7
> > > >
> > e%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638629597012519675
> > > >
> > %7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> > > >
> > TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=qhP3oGAev4J%2B3tO5n
> > > > dYLqxkcOfG%2BuIxk1Tf9yvmwrU8%3D&reserved=0.
> > > > >
> > > > > Source for this draft and an issue tracker can be found at
> > > > >
> > > >
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> > > > Fgithub.com%2Fboucadair%2Fnetconf-port-
> > > >
> > numbers&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C4bee2c4bc
> > > >
> > 314482efabb08dcde3c1e7e%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C
> > > >
> > 0%7C638629597012538950%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD
> > > >
> > AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sda
> > > >
> > ta=o3reMdiuYBR7FP0xYQhAs%2FJiFWurDLml4T8BAbimf%2FA%3D&reserved=0.
> > > > >
> > > > > The IETF datatracker status page for this Internet-Draft is:
> > > > >
> > > >
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> > > > Fdata
> > > > > tracker.ietf.org%2Fdoc%2Fdraft-boucadair-netconf-port-
> > > > numbers%2F&data=
> > > > >
> > > >
> > 05%7C02%7Cmohamed.boucadair%40orange.com%7C4bee2c4bc314482efabb08
> > > > dcde3
> > > > >
> > > >
> > c1e7e%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C63862959701254
> > > > 9473%
> > > > >
> > > >
> > 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
> > > > iI6Ik
> > > > >
> > > >
> > 1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=bJ4deuMbNsKReFAjnJZGP%2BQ
> > > > 9WM%2
> > > > > FQCaSws%2Bq4Wyyov8c%3D&reserved=0
> > > > >
> > > > > There is also an HTML version available at:
> > > > >
> > > >
> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> > > > Fwww.
> > > > > ietf.org%2Farchive%2Fid%2Fdraft-boucadair-netconf-port-
> > numbers-
> > > > 00.html
> > > > >
> > > >
> > &data=05%7C02%7Cmohamed.boucadair%40orange.com%7C4bee2c4bc314482e
> > > > fabb0
> > > > >
> > > >
> > 8dcde3c1e7e%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C63862959
> > > > 70125
> > > > >
> > > >
> > 60132%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzI
> > > > iLCJB
> > > > >
> > > >
> > TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=fK95LJd24FT65DoSn9P
> > > > hH8i5
> > > > > x1KVWope%2Fberxg7ihXg%3D&reserved=0
> > > > >
> > > > > _______________________________________________
> > > > > I-D-Announce mailing list -- [e-mail] To
> > > > unsubscribe send
> > > > > an email to [e-mail]
> > > > >
> > > >
> > _________________________________________________________________
> > > > _____
> > > > > ______________________________________
> > > > > 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.
> > > > >
> > > > > _______________________________________________
> > > > > netconf mailing list -- [e-mail] To unsubscribe send
> > an
> > > > email
> > > > > to [e-mail]
> > >
> > >
> > __________________________________________________________________
> > ____
> > > ______________________________________
> > > 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.
> _______________________________________________
> netconf mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>