Re: [tsvwg] [Editorial Errata Reported] RFC7605 (5592)

Joe Touch <touch@strayalpha.com> Mon, 07 January 2019 04:23 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0359129A87 for <tsvwg@ietfa.amsl.com>; Sun, 6 Jan 2019 20:23:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.769
X-Spam-Level:
X-Spam-Status: No, score=0.769 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pnP-Hu8BlcQc for <tsvwg@ietfa.amsl.com>; Sun, 6 Jan 2019 20:23:54 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B11F61292F1 for <tsvwg@ietf.org>; Sun, 6 Jan 2019 20:23:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=JqeNU6KSm1IR4HgNbgw+VJ+hstnkxNhsXWIn12nSz5w=; b=63NmK0oLMF90pEE70LMl/Cv0K V78Rz2Hq5Hz+8bnxN45TRFdCPG4HRvaRqUupI5a+wOtp3KcSr05XVSWxQnenaXPZQ9+3fKqckiuJt dXJyCdy/VwZYroEc24KxH00f64pJ/UyUhaAQVHb/IgrYPMZ4iBj7tcvfREzBSo0+HRgvQGR3GfSz5 HpF+cNdccHY95xdfX3ZgHTseKKyqb7xqopOwZRQuycBiR4hCcZHQdyWB9sMvczOd8LscjG/amsgSz 4EnRBw7w9n++GhFBtP87i6eWUX4+m7HBbFRLa08MGf8yj9EA2hJFXrzxrCDsqwZlRGx1YDYd/6fQ1 zwlmP5Rzg==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:58960 helo=[192.168.1.77]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <touch@strayalpha.com>) id 1ggMS3-0020Cq-Lv; Sun, 06 Jan 2019 23:23:50 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_182BAE7E-6819-4C47-9AF9-BFCBA1C98805"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <CACL_3VH1Nt=nrbg10gM_YADL1NfOJ4s2trg8fLEGPN0C9bB5pw@mail.gmail.com>
Date: Sun, 06 Jan 2019 20:23:46 -0800
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg <tsvwg@ietf.org>, "Dr. Joe Touch" <touch@isi.edu>, david.black@emc.com, "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <3F0AF6F6-D52E-4D37-B9D5-A3A8D117EA6F@strayalpha.com>
References: <20190105223012.8117BB81F77@rfc-editor.org> <4279D66E-AFA3-4D1E-ABB8-1F7DF8FE0F01@strayalpha.com> <06ed0c8d-4a20-708c-bad3-fa6844a80797@strayalpha.com> <5C324F4A.1080402@erg.abdn.ac.uk> <2644B517-FD04-4666-B6F3-D9677ADCC5E7@strayalpha.com> <CACL_3VH1Nt=nrbg10gM_YADL1NfOJ4s2trg8fLEGPN0C9bB5pw@mail.gmail.com>
To: "C. M. Heard" <heard@pobox.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/o_NqHAHxeK8A-o7krrMPT4rpvts>
Subject: Re: [tsvwg] [Editorial Errata Reported] RFC7605 (5592)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2019 04:23:58 -0000

Not sure what you’re seeing, but one minor update below on the provenance and some notes on search terms I used.

Joe

> On Jan 6, 2019, at 7:20 PM, C. M. Heard <heard@pobox.com> wrote:
> 
> OK, I looked on the wayback machine to see what I could find.
> 
> Snapshots of the repository referenced in RFC 1700 (ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers <ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers>) indicate that it moved to http://www.iana.org/assignments/port-numbers <http://www.iana.org/assignments/port-numbers> on or before 2001-05-11. The earliest snapshot of that page was from 2001-06-04:
> 
> https://web.archive.org/web/20010604223215/http://www.iana.org:80/assignments/port-numbers <https://web.archive.org/web/20010604223215/http://www.iana.org:80/assignments/port-numbers>

2001-05-19 is earlier with the same results:
https://web.archive.org/web/20010519080902/http://www.iana.org:80/assignments/port-numbers <https://web.archive.org/web/20010519080902/http://www.iana.org:80/assignments/port-numbers>

> 
> I also found an earlier snapshot from 2000-08-15 that was archived from www.isi.edu <http://www.isi.edu/>:
> 
> https://web.archive.org/web/20000815053440/http://www.isi.edu:80/in-notes/iana/assignments/port-numbers <https://web.archive.org/web/20000815053440/http://www.isi.edu:80/in-notes/iana/assignments/port-numbers>
> 
> Both of them say:
> The port numbers are divided into three ranges: the Well Known Ports,
> the Registered Ports, and the Dynamic and/or Private Ports.
> 
> The Well Known Ports are those from 0 through 1023.
> 
> The Registered Ports are those from 1024 through 49151
> 
> The Dynamic and/or Private Ports are those from 49152 through 65535
> 
> So the current range for registered ports was in effect for more than a decade prior to the publication of RFC 6335.

That’s what I thought - though I was hoping to find something that points to the actual change.  I wasn’t able to find any RFC citing the change, searching on:
	49151
	49152
	ephemeral port
	dynamic port
	private port

> 
> On that basis, the "corrected text" that I proposed is incomplete. Maybe the following would be better:
> 
> OLD:
>                                       [RFC1340 <https://tools.ietf.org/html/rfc1340>] also establishes the
>    Registered range of 1024-59151, though it notes that it is not
>    controlled by the IANA (at that point).  The list provided by
>    [RFC1700 <https://tools.ietf.org/html/rfc1700>] in 1994 remained the standard until it was declared
>    replaced by an online version, as of [RFC3232 <https://tools.ietf.org/html/rfc3232>] in 2002.
> 
> NEW:
>                                       [RFC1340 <https://tools.ietf.org/html/rfc1340>] also established the
>    Registered range of 1024-65535, though it noted that it was not
>    controlled by the IANA (at that point).  The list provided by
>    [RFC1700 <https://tools.ietf.org/html/rfc1700>] in 1994 remained the standard until it was declared
>    replaced by an online version, as of [RFC3232 <https://tools.ietf.org/html/rfc3232>] in 2002.  At some
>    time prior to that, the Registered range was changed to 1024-49151
>    and the Dynamic/Private range of 49152-65535 was established.
> 
> Sigh ... this all started because I saw 59151 and thought it was just a typo that should have been 49151.

> 
> Mike Heard
> 
> On Sun, Jan 6, 2019 at 2:29 PM Joe Touch <touch@strayalpha.com <mailto:touch@strayalpha.com>> wrote:
> Yes, as does RFC 1700. However, it was long before 6335 that the range was reduced to 48K, down from 64K. The only place to check, AFAICT, will be the Internet archive pages of IANA, other than RFCs...
> Joe
> 
> > On Jan 6, 2019, at 10:56 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>> wrote:
> > 
> > The point I saw was that RFC 1340 states this range on p23:
> > 
> > "
> > The Registered Ports are in the range 1024-65535.
> > "
> > 
> > Gorry
> > 
> > On 06/01/2019, 04:26, Joe Touch wrote:
> >> PS - ephemeral ports were known before RFC 6335. RFC 6056 refers to them
> >> at least; I'm digging to see if there's an earlier reference.
> >> Joe
> >> 
> >> On 1/5/2019 3:17 PM, Joe Touch wrote:
> >>> Good catch, though IANA did *register* ports in the range 1024-63353. I’m not sure what it meant to “control” ports; in both the system and registered ranges, all IANA could ever do was register assignees.
> >>> 
> >>> Joe
> >>> 
> >>>> On Jan 5, 2019, at 2:30 PM, RFC Errata System<rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>>  wrote:
> >>>> 
> >>>> The following errata report has been submitted for RFC7605,
> >>>> "Recommendations on Using Assigned Transport Port Numbers".
> >>>> 
> >>>> --------------------------------------
> >>>> You may review the report below and at:
> >>>> http://www.rfc-editor.org/errata/eid5592 <http://www.rfc-editor.org/errata/eid5592>
> >>>> 
> >>>> --------------------------------------
> >>>> Type: Editorial
> >>>> Reported by: C. M. Heard<heard@pobox.com <mailto:heard@pobox.com>>
> >>>> 
> >>>> Section: 3
> >>>> 
> >>>> Original Text
> >>>> -------------
> >>>>                                      [RFC1340] also establishes the
> >>>>   Registered range of 1024-59151, though it notes that it is not
> >>>>   controlled by the IANA (at that point).
> >>>> 
> >>>> Corrected Text
> >>>> --------------
> >>>>                                      [RFC1340] also established the
> >>>>   Registered range of 1024-65535, though it noted that it was not
> >>>>   controlled by the IANA (at that point).
> >>>> 
> >>>> Notes
> >>>> -----
> >>>> RFC 1340 (and RFC 1700, the subsequent and final Assigned Numbers RFC) listed the upper end of the Registered port range as 65535. It was subsequently changed to 49151 by RFC 6335.
> >>>> 
> >>>> Instructions:
> >>>> -------------
> >>>> This erratum is currently posted as "Reported". If necessary, please
> >>>> use "Reply All" to discuss whether it should be verified or
> >>>> rejected. When a decision is reached, the verifying party
> >>>> can log in to change the status and edit the report, if necessary.
> >>>> 
> >>>> --------------------------------------
> >>>> RFC7605 (draft-ietf-tsvwg-port-use-11)
> >>>> --------------------------------------
> >>>> Title               : Recommendations on Using Assigned Transport Port Numbers
> >>>> Publication Date    : August 2015
> >>>> Author(s)           : J. Touch
> >>>> Category            : BEST CURRENT PRACTICE
> >>>> Source              : Transport Area Working Group
> >>>> Area                : Transport
> >>>> Stream              : IETF
> >>>> Verifying Party     : IESG
> > 
>