[tsvwg] [Technical Errata Reported] RFC6335 (4999)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 19 April 2017 06:40 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 585E613150E for <tsvwg@ietfa.amsl.com>; Tue, 18 Apr 2017 23:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 nIr0Y5CMHuw0 for <tsvwg@ietfa.amsl.com>; Tue, 18 Apr 2017 23:40:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0411113151E for <tsvwg@ietf.org>; Tue, 18 Apr 2017 23:40:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 20762B80E78; Tue, 18 Apr 2017 23:40:22 -0700 (PDT)
To: michelle.cotton@icann.org, lars.eggert@nokia.com, touch@isi.edu, magnus.westerlund@ericsson.com, cheshire@apple.com, spencerdawkins.ietf@gmail.com, ietf@kuehlewind.net, david.black@emc.com, gorry@erg.abdn.ac.uk, wes@mti-systems.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: mnot@mnot.net, tsvwg@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20170419064022.20762B80E78@rfc-editor.org>
Date: Tue, 18 Apr 2017 23:40:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/VPki5H7JT2n0H-XiDH91p3prvSc>
Subject: [tsvwg] [Technical Errata Reported] RFC6335 (4999)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
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, 19 Apr 2017 06:40:37 -0000

The following errata report has been submitted 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:
http://www.rfc-editor.org/errata_search.php?rfc=6335&eid=4999

--------------------------------------
Type: Technical
Reported by: Mark Nottingham <mnot@mnot.net>

Section: GLOBAL

Original Text
-------------


Corrected Text
--------------


Notes
-----
HOLD FOR UPDATE

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.

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. 

--------------------------------------
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