Re: Straw-man charter for http-bis

Keith Moore <moore@cs.utk.edu> Fri, 01 June 2007 19:45 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 1HuD3f-0003Hu-5w; Fri, 01 Jun 2007 15:45:11 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HuD3e-0003DX-8o for discuss-confirm+ok@megatron.ietf.org; Fri, 01 Jun 2007 15:45:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HuD3d-0003Co-US for discuss@apps.ietf.org; Fri, 01 Jun 2007 15:45:09 -0400
Received: from shu.cs.utk.edu ([160.36.56.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HuD3c-0002Nt-Na for discuss@apps.ietf.org; Fri, 01 Jun 2007 15:45:09 -0400
Received: from localhost (localhost [127.0.0.1]) by shu.cs.utk.edu (Postfix) with ESMTP id 032E01EE188; Fri, 1 Jun 2007 15:45:04 -0400 (EDT)
X-Virus-Scanned: by amavisd-new with ClamAV and SpamAssasin at cs.utk.edu
Received: from shu.cs.utk.edu ([127.0.0.1]) by localhost (bes.cs.utk.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q3UPrWDC96Yz; Fri, 1 Jun 2007 15:44:19 -0400 (EDT)
Received: from lust.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182]) by shu.cs.utk.edu (Postfix) with ESMTP id C45441EE1E1; Fri, 1 Jun 2007 15:44:09 -0400 (EDT)
Message-ID: <46607708.4020603@cs.utk.edu>
Date: Fri, 01 Jun 2007 15:44:08 -0400
From: Keith Moore <moore@cs.utk.edu>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Straw-man charter for http-bis
References: <BA772834-227A-4C1B-9534-070C50DF05B3@mnot.net> <392C98BA-E7B8-44ED-964B-82FC48162924@mnot.net> <46605C9B.3080804@gmx.de> <46606B50.6030308@cs.utk.edu> <46606E4B.9040201@gmx.de> <46606FAE.2000907@cs.utk.edu> <46607205.3010000@gmx.de>
In-Reply-To: <46607205.3010000@gmx.de>
X-Enigmail-Version: 0.95.0
OpenPGP: id=E1473978
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Apps Discuss <discuss@apps.ietf.org>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
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

> I guess that depends on who's doing the editing. Speaking for myself,
> I have tried to make sure that changes are kept as minimal as
> possible, and that each and every change is linked to the issue it's
> supposed to resolve.
Maybe I should clarify.  If the working group sees itself as updating
2616, the working group can get into a rathole discussing changes to the
text even if the people participating in that discussion can't actually
change the text and submit a revised internet-draft for that text. But
if it's clear up front that the WG is not chartered to actually change
the document text, the participants are more likely to confine their
discussion to descriptions of specific problems and fixes.

(there's a reason we describe the job of being a WG chair (and for that
matter, an AD) as "herding cats".)

Keith