Re: Straw-man charter for http-bis

Julian Reschke <julian.reschke@gmx.de> Fri, 01 June 2007 17:51 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HuBHj-0003RK-Uy; Fri, 01 Jun 2007 13:51:35 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HuBHj-0003Nq-4l for discuss-confirm+ok@megatron.ietf.org; Fri, 01 Jun 2007 13:51:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HuBHi-0003MQ-Ql for discuss@apps.ietf.org; Fri, 01 Jun 2007 13:51:34 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HuBHh-0003xr-DD for discuss@apps.ietf.org; Fri, 01 Jun 2007 13:51:34 -0400
Received: (qmail invoked by alias); 01 Jun 2007 17:51:31 -0000
Received: from p508FA47F.dip0.t-ipconnect.de (EHLO [192.168.178.22]) [80.143.164.127] by mail.gmx.net (mp057) with SMTP; 01 Jun 2007 19:51:31 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/ECDlFHlvE6MaFt/iMdYxg3dZnU3DaWBK/yyi/OE IVmeNRIKl415tI
Message-ID: <46605C9B.3080804@gmx.de>
Date: Fri, 01 Jun 2007 19:51:23 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, Apps Discuss <discuss@apps.ietf.org>
Subject: Re: Straw-man charter for http-bis
References: <BA772834-227A-4C1B-9534-070C50DF05B3@mnot.net> <392C98BA-E7B8-44ED-964B-82FC48162924@mnot.net>
In-Reply-To: <392C98BA-E7B8-44ED-964B-82FC48162924@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc:
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

Hi,

I'd like to make one small comment with respect to the opinion that 
maintaining an errata list (and potentially handing that to the RFC 
Editor) would be sufficient.

1) Scott Lawrence' original errata list 
(<http://purl.org/NET/http-errata> is excellent, but it hasn't been 
maintained since 2004. So we needed to move somewhere else.

2) Just collecting errata sounds nice in theory, but my experience with 
spec writing is that you can't close a bug until you have applied the 
suggested fix to the spec text. Frequently, something that looks OK in 
isolation doesn't work in the specification context. Thus my preference 
is not only to collect errata and proposed resolutions, but to also have 
them applied to a copy of the original spec (and have that up for review 
for everybody).

3) Finally, looking at the amount of issues we have collected in the 
meantime, I'd be really amazed if the RFC Editor would be willing to 
take over the editorial work for updating the document. I bet the answer 
would be: please submit an Internet Draft.

Best regards, Julian