RT-Owner: sabrina.tanamal
From: "Sabrina Tanamal via RT" <iana-issues@iana.org>
In-Reply-To: <rt-5.0.3-880457-1729651179-1681.1379432-37-0@icann.org>
References: <RT-Ticket-1379432@icann.org>
 <172735438321.270107.8438028122125542597@dt-datatracker-6c75f7dfff-hrjh6>
 <DU2PR02MB10160EF4FD3677671B13F3001886A2@DU2PR02MB10160.eurprd02.prod.outlook.com>
 <010001922ec3dd9c-ecf7fac2-3d13-4c9e-abc3-f66bdb446d18-000000@email.amazonses.com>
 <DU2PR02MB10160A9305BE806FBFE09151488772@DU2PR02MB10160.eurprd02.prod.outlook.com>
 <rt-5.0.3-1442791-1728064521-553.1379432-37-0@icann.org>
 <DU2PR02MB1016034CDA71378B23744457F884C2@DU2PR02MB10160.eurprd02.prod.outlook.com>
 <rt-5.0.3-789714-1729596667-374.1379432-37-0@icann.org>
 <rt-5.0.3-880457-1729651179-1681.1379432-37-0@icann.org>
Message-ID: <rt-5.0.3-390876-1730739116-1550.1379432-37-0@icann.org>
To: mohamed.boucadair@orange.com
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Date: Mon, 04 Nov 2024 16:51:56 +0000
MIME-Version: 1.0
Message-ID-Hash: 62GMCVLG4YYWIPRXAJQGPD3KF22LKFSW
CC: zahed.sarker.ietf@gmail.com, netconf@ietf.org, kent@watsen.net
Reply-To: iana-issues@iana.org
Subject: =?utf-8?q?=5Bnetconf=5D_=5BIANA_=231379432=5D_RE=3A_I-D_Action=3A_draft-bouc?=
	=?utf-8?q?adair-netconf-port-numbers-00=2Etxt?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/netconf/i1sDI9AJafUgPVQqCrc10Qjv29U>

Hi Zahed,=20

Have you had a chance to review this one? Please see below.=20

Let us know if we should take these to Joe Touch.=20

Thanks,
Sabrina

On Wed Oct 23 02:39:39 2024, amanda.baber wrote:
> Hi Zahed,
>=20
> Should we take these to Joe Touch, the lead port expert, and get back
> to you?
>=20
> =3D=3D=3D
>=20
> 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.
>=20
> 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.
>=20
> =3D=3D=3D
>=20
> thanks,
> Amanda
>=20
> On Tue Oct 22 11:31:07 2024, mohamed.boucadair@orange.com wrote:
> > Hi Amanda, Zahed,
> >
> > Any update about this request?
> >
> > Thank you.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De=C2=A0: BOUCADAIR Mohamed INNOV/NET
> > > Envoy=C3=A9=C2=A0: lundi 7 octobre 2024 16:38
> > > =C3=80=C2=A0: 'iana-issues@iana.org' <iana-issues@iana.org>
> > > Cc=C2=A0: netconf@ietf.org; mjethanandani@gmail.com; kent@watsen.net;
> > > zahed.sarker.ietf@gmail.com
> > > Objet=C2=A0: RE: [IANA #1379432] RE: [netconf] I-D Action: draft-
> > > boucadair-netconf-port-numbers-00.txt
> > >
> > > 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.
> > >
> > > 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
> > >
> > > PS: I updated the draft to remove 3.4 as that one is not actually
> > > needed.
> > >
> > > > -----Message d'origine-----
> > > > De=C2=A0: Sabrina Tanamal via RT <iana-issues@iana.org> Envoy=C3=A9=
=C2=A0:
> > > vendredi 4
> > > > octobre 2024 19:55 =C3=80=C2=A0: BOUCADAIR Mohamed INNOV/NET
> > > > <mohamed.boucadair@orange.com> Cc=C2=A0: netconf@ietf.org;
> > > > mjethanandani@gmail.com; kent@watsen.net;
> > > zahed.sarker.ietf@gmail.com
> > > > Objet=C2=A0: [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, mohamed.boucadair@orange.com
> > > 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=C2=A0: Kent Watsen <kent@watsen.net> Envoy=C3=A9=C2=A0: jeud=
i 26
> > > septembre
> > > > > > 2024 16:37 =C3=80=C2=A0: BOUCADAIR Mohamed INNOV/NET
> > > > > > <mohamed.boucadair@orange.com> Cc=C2=A0: netconf@ietf.org
> > > > Objet
> > > > > > : Re: [netconf] I-D Action: draft-boucadair-netconf-port-
> > > > > > numbers-00.txt
> > > > > >
> > > > > >
> > > > > > Hi Med,
> > > > > >
> > > > > > Thank you for initiating this effort.  Honestly, I didn=E2=80=
=99t
> > > know
> > > > that
> > > > > > those unnecessary allocations existed.  It is goodness to
> > > > release
> > > > > > unneeded allocations.
> > > > > >
> > > > > > Kent / contributor
> > > > > >
> > > > > >
> > > > > > > On Sep 26, 2024, at 8:50=E2=80=AFAM, mohamed.boucadair@orange=
.com
> > > > > > 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 : internet-drafts@ietf.org <internet-drafts@ietf.org>
> > > > Envoy=C3=A9
> > > > > > :
> > > > > > > jeudi 26 septembre 2024 14:40 =C3=80 : i-d-announce@ietf.org
> > > > 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 (netconf@ietf.org) which is
> > > > > > archived at
> > > > > > >
> > > > > >
> > > >
> > > https://eur03.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2
> > > > > >
> > > >
> > > Fmailarchive.ietf.org%2Farch%2Fbrowse%2Fnetconf%2F&data=3D05%7C02%7
> > > > > >
> > > >
> > > Cmohamed.boucadair%40orange.com%7C4bee2c4bc314482efabb08dcde3c1e7
> > > > > >
> > > >
> > > e%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638629597012519675
> > > > > >
> > > >
> > > %7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> > > > > >
> > > >
> > > TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=3DqhP3oGAev4J%2B3tO5n
> > > > > > dYLqxkcOfG%2BuIxk1Tf9yvmwrU8%3D&reserved=3D0.
> > > > > > >
> > > > > > > Source for this draft and an issue tracker can be found
> > > at
> > > > > > >
> > > > > >
> > > >
> > > https://eur03.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2
> > > > > > Fgithub.com%2Fboucadair%2Fnetconf-port-
> > > > > >
> > > >
> > > numbers&data=3D05%7C02%7Cmohamed.boucadair%40orange.com%7C4bee2c4bc
> > > > > >
> > > >
> > > 314482efabb08dcde3c1e7e%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C
> > > > > >
> > > >
> > > 0%7C638629597012538950%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD
> > > > > >
> > > >
> > > AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sda
> > > > > >
> > > >
> > > ta=3Do3reMdiuYBR7FP0xYQhAs%2FJiFWurDLml4T8BAbimf%2FA%3D&reserved=3D0.
> > > > > > >
> > > > > > > The IETF datatracker status page for this Internet-Draft
> > > is:
> > > > > > >
> > > > > >
> > > >
> > > https://eur03.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2
> > > > > > Fdata
> > > > > > > tracker.ietf.org%2Fdoc%2Fdraft-boucadair-netconf-port-
> > > > > > numbers%2F&data=3D
> > > > > > >
> > > > > >
> > > >
> > > 05%7C02%7Cmohamed.boucadair%40orange.com%7C4bee2c4bc314482efabb08
> > > > > > dcde3
> > > > > > >
> > > > > >
> > > >
> > > c1e7e%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C63862959701254
> > > > > > 9473%
> > > > > > >
> > > > > >
> > > >
> > > 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
> > > > > > iI6Ik
> > > > > > >
> > > > > >
> > > >
> > > 1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=3DbJ4deuMbNsKReFAjnJZGP%2BQ
> > > > > > 9WM%2
> > > > > > > FQCaSws%2Bq4Wyyov8c%3D&reserved=3D0
> > > > > > >
> > > > > > > There is also an HTML version available at:
> > > > > > >
> > > > > >
> > > >
> > > https://eur03.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2
> > > > > > Fwww.
> > > > > > > ietf.org%2Farchive%2Fid%2Fdraft-boucadair-netconf-port-
> > > > numbers-
> > > > > > 00.html
> > > > > > >
> > > > > >
> > > >
> > > &data=3D05%7C02%7Cmohamed.boucadair%40orange.com%7C4bee2c4bc314482e
> > > > > > fabb0
> > > > > > >
> > > > > >
> > > >
> > > 8dcde3c1e7e%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C63862959
> > > > > > 70125
> > > > > > >
> > > > > >
> > > >
> > > 60132%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzI
> > > > > > iLCJB
> > > > > > >
> > > > > >
> > > >
> > > TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=3DfK95LJd24FT65DoSn9P
> > > > > > hH8i5
> > > > > > > x1KVWope%2Fberxg7ihXg%3D&reserved=3D0
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > I-D-Announce mailing list -- i-d-announce@ietf.org To
> > > > > > unsubscribe send
> > > > > > > an email to i-d-announce-leave@ietf.org
> > > > > > >
> > > > > >
> > > >
> > > _________________________________________________________________
> > > > > > _____
> > > > > > > ______________________________________
> > > > > > > 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 -- netconf@ietf.org To unsubscribe
> > > send
> > > > an
> > > > > > email
> > > > > > > to netconf-leave@ietf.org
> > > > >
> > > > >
> > > >
> > > _________________________________________________________________
> > > _
> > > > ____
> > > > > ______________________________________
> > > > > 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.