Re: [apps-discuss] process and editing questions: RFC errata
Erik Wilde <dret@berkeley.edu> Thu, 21 February 2013 14:59 UTC
Return-Path: <dret@berkeley.edu>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6178A21F873C for <apps-discuss@ietfa.amsl.com>; Thu, 21 Feb 2013 06:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0KDP4ZoswwZP for <apps-discuss@ietfa.amsl.com>; Thu, 21 Feb 2013 06:59:18 -0800 (PST)
Received: from cm04fe.IST.Berkeley.EDU (cm04fe.IST.Berkeley.EDU [169.229.218.145]) by ietfa.amsl.com (Postfix) with ESMTP id 2869721F85C0 for <apps-discuss@ietf.org>; Thu, 21 Feb 2013 06:59:18 -0800 (PST)
Received: from 46-126-158-51.dynamic.hispeed.ch ([46.126.158.51] helo=dretair.local) by cm04fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1U8Xc5-0002Gy-Ds; Thu, 21 Feb 2013 06:59:16 -0800
Message-ID: <51263634.7040906@berkeley.edu>
Date: Thu, 21 Feb 2013 15:59:00 +0100
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "t.petch" <ietfc@btconnect.com>, apps-discuss@ietf.org
References: <5124D91C.1000703@berkeley.edu> <000901ce1023$3c4b7140$4001a8c0@gateway.2wire.net>
In-Reply-To: <000901ce1023$3c4b7140$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: REST Discuss <rest-discuss@yahoogroups.com>
Subject: Re: [apps-discuss] process and editing questions: RFC errata
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Feb 2013 14:59:19 -0000
hello tom. thanks a lot for your response! it was very useful to get a menu of options how to proceed. On 2013-02-21 12:04 , t.petch wrote: >> - how to best sync draft development, and the submitted errata. there >> seems to be no way to predict when and how errata are processed, in >> particular for RFC 5261 because the author seems to be unreachable. > > Indeed! Bear in mind that the text of an RFC is available for further > processing within the IETF so while it is desirable that the original > author is involved in any updates thereto, that is not a requirement > thereof so if you cannot get any response from them, then submitting an > RFC5261-bis yourself is quite in order; but quite a lot of work. > > A simpler approach is to include the relevant changes in > draft-wilde-xml-patch > and state that this is an update to the relevant sections of RFC5261. > These should give more context than the errata do but need not be much > longer. > > Or you can include sections that clarify the issues you have identified > in RFC5261 and state in your I-D that your I-D is based on this > interpretation ie you are not updating RFC5261 for the world at large > but are modifiying the content thereof for the purposes of your I-D. > > Or you can make normative references to errata by URL once they are > approved. I think this the most fraught approach and so the least > desirable. after thinking about these options for a while, i decided to go with the second option. http://tools.ietf.org/html/draft-wilde-xml-patch-04 is the updated draft and now officially updates RFC 5261. http://tools.ietf.org/html/draft-wilde-xml-patch-04#appendix-A lists all the changes to that RFC, and i have based this appendix mostly on the errata i had filed before. this approach seems to be much less work than republishing RFC 5261, and since the changes are rather small, the updates aren't that hard to read and apply, when you have to read them in addition to RFC 5261. thanks again and kind regards, dret. -- erik wilde | mailto:dret@berkeley.edu - tel:+1-510-2061079 | | UC Berkeley - School of Information (ISchool) | | http://dret.net/netdret http://twitter.com/dret |
- [apps-discuss] process and editing questions: RFC… Erik Wilde
- Re: [apps-discuss] process and editing questions:… t.petch
- Re: [apps-discuss] process and editing questions:… Erik Wilde
- Re: [apps-discuss] process and editing questions:… t.petch
- Re: [apps-discuss] process and editing questions:… Erik Wilde
- Re: [apps-discuss] process and editing questions:… t.petch
- [apps-discuss] draft-wilde-xml-patch and updates … Erik Wilde
- Re: [apps-discuss] draft-wilde-xml-patch and upda… t.petch
- Re: [apps-discuss] draft-wilde-xml-patch and upda… Barry Leiba
- Re: [apps-discuss] draft-wilde-xml-patch and upda… Robert Sparks