[130150] in North American Network Operators' Group
Re: Randy in Nevis
daemon@ATHENA.MIT.EDU (Joe Abley)
Wed Sep 29 09:02:05 2010
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <79587.1285763116@localhost>
Date: Wed, 29 Sep 2010 12:59:40 +0000
To: Valdis.Kletnieks@vt.edu
X-SA-Exim-Mail-From: jabley@hopcount.ca
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 2010-09-29, at 12:25, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 29 Sep 2010 14:13:51 +0200, =3D?utf-8?Q?Bj=3DC3=3DB8rn_Mork?=3D =
said:
>> John Peach <john-nanog@johnpeach.com> writes:
>>=20
>>> It is on all Linux distros:
>>>=20
>>> ssmtp 465/tcp smtps # SMTP over SSL
>>=20
>> So file bug reports.
>=20
> bug-reports@iana.org seems to bounce.
I don't know the history of 465/tcp as an entry in the registry found at =
<<http://www.iana.org/assignments/port-numbers>, but assuming the =
current entry is there for a reason (and hence is not an error that =
might be corrected), I believe this is the workflow required to change =
it.
The port-number registry is maintained according to the directions in =
RFC 2780. To change an entry in the registry you need to write and =
submit an internet-draft <http://www.ietf.org/id-info/> which contains =
an IANA Considerations section specifying the change that is required. =
Those specifications will be executed (and the registry updated) if/when =
the I-D makes it through to that stage in the RFC publication process. =
RFC 2780 gives the following guidance for how such an I-D might reach =
that stage.
9.1 TCP Source and Destination Port fields
Both the Source and Destination Port fields use the same namespace.
Values in this namespace are assigned following a Specification
Required, Expert Review, IESG Approval, IETF Consensus, or Standards
Action process. Note that some assignments may involve non-
disclosure information.
Joe=
