Re: [tsvwg] [Technical Errata Reported] RFC6335 (3813)

gorry@erg.abdn.ac.uk Fri, 29 November 2013 18:56 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C9B11ADF4F for <tsvwg@ietfa.amsl.com>; Fri, 29 Nov 2013 10:56:56 -0800 (PST)
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_PASS=-0.001] autolearn=ham
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 pDxFnznu9efO for <tsvwg@ietfa.amsl.com>; Fri, 29 Nov 2013 10:56:54 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id D379D1AE03A for <tsvwg@ietf.org>; Fri, 29 Nov 2013 10:56:53 -0800 (PST)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id D1E1B2B44C8; Fri, 29 Nov 2013 18:56:51 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Fri, 29 Nov 2013 18:56:51 -0000
Message-ID: <897b067e38c3a6e990209b47e852a8b0.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <20131129184403.997A4726001@rfc-editor.org>
References: <20131129184403.997A4726001@rfc-editor.org>
Date: Fri, 29 Nov 2013 18:56:51 -0000
From: gorry@erg.abdn.ac.uk
To: RFC Errata System <rfc-editor@rfc-editor.org>
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: magnus.westerlund@ericsson.com, tsvwg@ietf.org, touch@isi.edu, gorry@erg.abdn.ac.uk, mls.ietf@gmail.com, lars.eggert@nokia.com, jmpolk@cisco.com, michelle.cotton@icann.org, rfc-editor@rfc-editor.org
Subject: Re: [tsvwg] [Technical Errata Reported] RFC6335 (3813)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 29 Nov 2013 18:56:56 -0000

Please disregard this Errata. It is was submitted by mistake. A corrected
entry has replaced this.

Gorry


> 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=3813
>
> --------------------------------------
> Type: Technical
> Reported by: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
>
> Section: 2.2
>
> Original Text
> -------------
> All standards assigned Service Codes, including
> all values assigned by IANA, are required to use a value that may be
> represented using a subset of the ASCII character set.
>
>
> Corrected Text
> --------------
> Requests for a Service Code in the IANA Considerations section of a
> Standards-Track specification are to be assigned from the
> Specifications-Required portion of the Service Code registry.
> These assignments are required to use a value that may be
> represented using a subset of the ASCII character set (see section 5).
>
>
> Notes
> -----
> RFC 5595 did not clearly specify the intended update to RFC 4340.
>
> Instructions:
> -------------
> This errata 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 (IESG)
> 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
>