Re: [Editorial Errata Reported] RFC4960 (2592)
Gorry Fairhurst <gorry@erg.abdn.ac.uk> Fri, 29 October 2010 15:39 UTC
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4717C3A6A28 for <tsvwg@core3.amsl.com>; Fri, 29 Oct 2010 08:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.995
X-Spam-Level:
X-Spam-Status: No, score=-101.995 tagged_above=-999 required=5 tests=[AWL=-0.296, BAYES_00=-2.599, J_CHICKENPOX_52=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LBQY-+Jtxd4V for <tsvwg@core3.amsl.com>; Fri, 29 Oct 2010 08:39:31 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 093B23A68AE for <tsvwg@ietf.org>; Fri, 29 Oct 2010 08:39:29 -0700 (PDT)
Received: from Gorry-Fairhursts-MacBook-Pro.local (ra-gorry.erg.abdn.ac.uk [139.133.204.42]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id o9TFepvN009084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 29 Oct 2010 16:40:52 +0100 (BST)
Message-ID: <4CCAEB04.9040507@erg.abdn.ac.uk>
Date: Fri, 29 Oct 2010 16:40:52 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Michael Tüxen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Editorial Errata Reported] RFC4960 (2592)
References: <20101029133521.A1E38E06EF@rfc-editor.org> <021B5259-1A6E-4C0C-BD83-674D00F3EB4B@lakerest.net> <49FD141B-D7CE-4CB1-891E-78A7BA2DDC9F@lurchi.franken.de>
In-Reply-To: <49FD141B-D7CE-4CB1-891E-78A7BA2DDC9F@lurchi.franken.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
Cc: James Polk <jmpolk@cisco.com>, tsvwg list <tsvwg@ietf.org>, Randy Stewart <randall@lakerest.net>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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 Oct 2010 15:39:33 -0000
Michael, These seem to be straightforward corrections. Please propose some corrections in the form below, and we can make sure the RFC-Ed notes these. --- OLD: xxx NEW: xxx --- Gorry On 29/10/2010 16:19, Michael Tüxen wrote: > Dear all, > > we should possibly fix the wording also in > http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-chunk-flags-02 > during AUTH48. > > TSVWG chairs: Is that possible? > > Best regards > Michael > > On Oct 29, 2010, at 4:10 PM, Randy Stewart wrote: > >> Dear RFC Editor: >> >> The Errata is correct.. Tom and I discussed this on the list >> and I agree with it. We obviously made a cut-and paste typo.. since >> chunk types are different than parameter types ;-) >> >> Best Wishes >> >> Randall Stewart >> On Oct 29, 2010, at 6:35 AM, RFC Errata System wrote: >> >>> >>> The following errata report has been submitted for RFC4960, >>> "Stream Control Transmission Protocol". >>> >>> -------------------------------------- >>> You may review the report below and at: >>> http://www.rfc-editor.org/errata_search.php?rfc=4960&eid=2592 >>> >>> -------------------------------------- >>> Type: Editorial >>> Reported by: tom petch<ietfc@btconnect.com> >>> >>> Section: 14.1 >>> >>> Original Text >>> ------------- >>> 14.1. IETF-Defined Chunk Extension >>> >>> The assignment of new chunk parameter type codes is done through an >>> IETF Consensus action, as defined in [RFC2434]. Documentation of the >>> chunk parameter MUST contain the following information: >>> >>> >>> Corrected Text >>> -------------- >>> 14.1. IETF-Defined Chunk Extension >>> >>> The assignment of new chunk type codes is done through an >>> IETF Consensus action, as defined in [RFC2434]. Documentation of the >>> chunk type MUST contain the following information: >>> >>> >>> Notes >>> ----- >>> The OLD text relates to parameter types, and not chunk types, and already appears, correctly, in section 14.2. Section 14.1 is about chunk types,as the NEW text says. >>> >>> 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. >>> >>> -------------------------------------- >>> RFC4960 (draft-ietf-tsvwg-2960bis-05) >>> -------------------------------------- >>> Title : Stream Control Transmission Protocol >>> Publication Date : September 2007 >>> Author(s) : R. Stewart, Ed. >>> Category : PROPOSED STANDARD >>> Source : Transport Area Working Group >>> Area : Transport >>> Stream : IETF >>> Verifying Party : IESG >>> >> >> ----- >> Randall Stewart >> randall@lakerest.net >> >> >> >> >> > > >
- [Editorial Errata Reported] RFC4960 (2592) RFC Errata System
- Re: [Editorial Errata Reported] RFC4960 (2592) Randy Stewart
- Re: [Editorial Errata Reported] RFC4960 (2592) Michael Tüxen
- Re: [Editorial Errata Reported] RFC4960 (2592) Gorry Fairhurst
- Re: [Editorial Errata Reported] RFC4960 (2592) Michael Tüxen
- Re: [Editorial Errata Reported] RFC4960 (2592) Chris Benson