Re: [tsvwg] [Editorial Errata Reported] RFC7605 (5592)
"C. M. Heard" <heard@pobox.com> Mon, 07 January 2019 03:20 UTC
Return-Path: <heard@pobox.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 40473130E3F for <tsvwg@ietfa.amsl.com>; Sun, 6 Jan 2019 19:20:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.711
X-Spam-Level:
X-Spam-Status: No, score=-0.711 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.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 vT-Xrnkv8jVe for <tsvwg@ietfa.amsl.com>; Sun, 6 Jan 2019 19:20:18 -0800 (PST)
Received: from pb-smtp21.pobox.com (pb-smtp21.pobox.com [173.228.157.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53D86130DD7 for <tsvwg@ietf.org>; Sun, 6 Jan 2019 19:20:17 -0800 (PST)
Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 879A03BA42 for <tsvwg@ietf.org>; Sun, 6 Jan 2019 22:20:15 -0500 (EST) (envelope-from heard@pobox.com)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; s=sasl; bh=vju1GDK9W5wb5xLIAiYdrrHaeLQ=; b=jenaeI DRvqo1AvYYoFBlQoF8iqf307APSULgzPLDJZspm3jxbxXV+lp24hY3abCc/GZitP H8xY0rlZSdphjUjTwIQCKobQ29WFY61iqE01t8vSdrQqvlJEbRTs7NdjWuOonLyi Wf4AbP/4mTpEB84jzLS3+1wnASFaRnRpTvDVk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; q=dns; s=sasl; b=HbhgyQlO53kWPMtjSckgzCQjpA2yPT4j zMy1qSauwVwVsCK5mvLkc5km1wVYae+IglQiPokmnyQAQqazwJ6/4fEUjJQFj8fG dll3NDZA8c1UhLttdElsb8GWMdyMj80tXx4MQ38hWO5qySM4Aj42BWXwmvFS2D/m 4ylJB3okIzo=
Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 8071F3BA41 for <tsvwg@ietf.org>; Sun, 6 Jan 2019 22:20:15 -0500 (EST) (envelope-from heard@pobox.com)
Received: from mail-it1-f176.google.com (unknown [209.85.166.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id 263683BA3D for <tsvwg@ietf.org>; Sun, 6 Jan 2019 22:20:13 -0500 (EST) (envelope-from heard@pobox.com)
Received: by mail-it1-f176.google.com with SMTP id x124so6264442itd.1 for <tsvwg@ietf.org>; Sun, 06 Jan 2019 19:20:13 -0800 (PST)
X-Gm-Message-State: AJcUukcUM79MqZJRc0+12mrfzblenb3AH6DymPecR3nTORdEy7OdYRNP OfdWZ59Zx6i8rzlofO6ljU719srUynoqt9XlON4=
X-Google-Smtp-Source: ALg8bN5Et9ixm6VUYM+gSDgglmQkQeALYKWwuejDXfRQTPbd0DTIbHWcw1yqOo4/rn7PHbhg2Dqhdiswwep8jZ9Qj+c=
X-Received: by 2002:a24:ee83:: with SMTP id b125mr6560068iti.151.1546831211907; Sun, 06 Jan 2019 19:20:11 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <2644B517-FD04-4666-B6F3-D9677ADCC5E7@strayalpha.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Sun, 06 Jan 2019 19:20:00 -0800
X-Gmail-Original-Message-ID: <CACL_3VH1Nt=nrbg10gM_YADL1NfOJ4s2trg8fLEGPN0C9bB5pw@mail.gmail.com>
Message-ID: <CACL_3VH1Nt=nrbg10gM_YADL1NfOJ4s2trg8fLEGPN0C9bB5pw@mail.gmail.com>
To: Joe Touch <touch@strayalpha.com>
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>
Content-Type: multipart/alternative; boundary="000000000000e9d455057ed5b4fa"
X-Pobox-Relay-ID: 2563BF9E-122B-11E9-AB6E-90A5DACCD188-06080547!pb-smtp21.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/OeAR6CpThPrccA2BxyzC5x7z_H4>
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 03:20:22 -0000
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) indicate that it moved to 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 I also found an earlier snapshot from 2000-08-15 that was archived from www.isi.edu: 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. 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> 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> > 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> 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 > >>>> > >>>> -------------------------------------- > >>>> Type: Editorial > >>>> Reported by: C. M. Heard<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 > > > >
- [tsvwg] [Editorial Errata Reported] RFC7605 (5592) RFC Errata System
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Joe Touch
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Joe Touch
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Gorry Fairhurst
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Joe Touch
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… C. M. Heard
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Joe Touch
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Mirja Kuehlewind
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Joe Touch
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Mirja Kuehlewind
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Gorry Fairhurst
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Joe Touch
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Mirja Kuehlewind
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Gorry Fairhurst
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Mirja Kuehlewind
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Joe Touch
- Re: [tsvwg] [Editorial Errata Reported] RFC7605 (… Gorry Fairhurst