IETF Logo Mail Archive

Re: [tsvwg] [Errata Held for Document Update] RFC6335 (4999)

Joseph Touch <touch@strayalpha.com> Wed, 04 March 2020 14:52 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 864393A1041; Wed, 4 Mar 2020 06:52:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.319
X-Spam-Level:
X-Spam-Status: No, score=-1.319 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] 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 PACY5ehX4-1E; Wed, 4 Mar 2020 06:52:27 -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 7FFAD3A103E; Wed, 4 Mar 2020 06:52:27 -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: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To: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=x/PexfejaLfpILeSGPkQHqtxNV+DpPkrbi+gwMyYZGA=; b=cGQEbjxrIAXn8eFq7N4+gAmK7 F+WgSYlhxoPGqzBBHcoVPbHWcydPenL+dZ+iH3uYInjv1o1Jh59BVg3zoZYeqEIofacg9N59Re2LH Jn66GqBoKOGgWi44g8OGQJrEAWMkSlG0Elv9lTAQKY71N2NGXhoNXhSjyMQuDFD/IEJTgzwdrZXrm WylPV6hv0qOmSp3UyzgvNHCzvrw2wm8syqDAhV5gSr92RJezREsG75PjR4OHBzwyQYBElU1lHrTwR b47yGVruasVdVyp7uUv+OGwT1iMinGDF/mww/3/hWakPjUP18FfD5bpBAcc4oQk120i/2KDap30Kj XDoBHYrmw==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:54094 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1j9VNg-001zt6-HB; Wed, 04 Mar 2020 09:52:21 -0500
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <20200304113026.A855CF40725@rfc-editor.org>
Date: Wed, 04 Mar 2020 06:52:15 -0800
Cc: Mark Nottingham <mnot@mnot.net>, michelle.cotton@icann.org, lars.eggert@nokia.com, "Dr. Joe Touch" <touch@isi.edu>, magnus.westerlund@ericsson.com, cheshire@apple.com, ietf@kuehlewind.net, iesg@ietf.org, tsvwg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9FDCD0E5-730B-4B19-83A5-C2A710344AD8@strayalpha.com>
References: <20200304113026.A855CF40725@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-0.2
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/eKQ8OUUJS1EHzs7ZRknFqadzNFk>
Subject: Re: [tsvwg] [Errata Held for Document Update] RFC6335 (4999)
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: Wed, 04 Mar 2020 14:52:30 -0000

Hi, all,

I disagree; Sec 8.4 allows for IANA-initiated deassignment. The deassignment procedures there and in Sec 8.3 make it clear that there’s not much point in focusing on cases when the assignee can’t be contacted (for whatever reason). 

Further, sec 7.9 of RFC 7605 underscores a point made throughout RFC 6335 - that port assignments aren’t intended to be changed. So the lack of such a contact isn’t really an issue except in very rare cases (for which the exception processes in RFC 6335 are already sufficient).

Joe

> On Mar 4, 2020, at 3:30 AM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been held for document update 
> for RFC6335, "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry". 
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid4999
> 
> --------------------------------------
> Status: Held for Document Update
> Type: Technical
> 
> Reported by: Mark Nottingham <mnot@mnot.net>
> Date Reported: 2017-04-19
> Held by: Mirja Kühlewind (IESG)
> 
> Section: GLOBAL
> 
> Original Text
> -------------
> 
> 
> Corrected Text
> --------------
> 
> 
> Notes
> -----
> Many port number assignments are to individuals, but the document does not
> contemplate how they should be handled when the assignee is dead or
> otherwise can't be contacted. 
> 
> The most obvious procedure to follow is a transfer (8.5), but that requires 
> de-assignment (8.2), and that doesn't cover the case above.
> 
> --------------------------------------
> RFC6335 (draft-ietf-tsvwg-iana-ports-10)
> --------------------------------------
> Title               : Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry
> Publication Date    : August 2011
> Author(s)           : M. Cotton, L. Eggert, J. Touch, M. Westerlund, S. Cheshire
> Category            : BEST CURRENT PRACTICE
> Source              : Transport Area Working Group
> Area                : Transport
> Stream              : IETF
> Verifying Party     : IESG
>

v2.23.0 | Report a Bug | By Email