Re: Straw-man charter for http-bis

Keith Moore <moore@cs.utk.edu> Fri, 01 June 2007 14:48 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 1Hu8Qy-0007nK-Us; Fri, 01 Jun 2007 10:48:56 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1Hu8Qx-0007n9-Li for discuss-confirm+ok@megatron.ietf.org; Fri, 01 Jun 2007 10:48:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hu8Qx-0007n1-C6 for discuss@apps.ietf.org; Fri, 01 Jun 2007 10:48:55 -0400
Received: from shu.cs.utk.edu ([160.36.56.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hu8Qw-0001r3-4t for discuss@apps.ietf.org; Fri, 01 Jun 2007 10:48:55 -0400
Received: from localhost (localhost [127.0.0.1]) by shu.cs.utk.edu (Postfix) with ESMTP id 1CB6F1EE152; Fri, 1 Jun 2007 10:48:52 -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 FCSh2iiq4YRI; Fri, 1 Jun 2007 10:48:41 -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 B416F1EE1A7; Fri, 1 Jun 2007 10:48:40 -0400 (EDT)
Message-ID: <466031C7.4050906@cs.utk.edu>
Date: Fri, 01 Jun 2007 10:48:39 -0400
From: Keith Moore <moore@cs.utk.edu>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: "Roy T. Fielding" <fielding@gbiv.com>
Subject: Re: Straw-man charter for http-bis
References: <BA772834-227A-4C1B-9534-070C50DF05B3@mnot.net> <392C98BA-E7B8-44ED-964B-82FC48162924@mnot.net> <1358AF2C-F967-46D6-B291-BC65126CCDF6@gbiv.com> <8FBD37BC-E635-485D-A368-22D9DE332498@mnot.net> <DAC34319-CB4D-48B6-A53F-66345790F0FA@gbiv.com>
In-Reply-To: <DAC34319-CB4D-48B6-A53F-66345790F0FA@gbiv.com>
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: 7655788c23eb79e336f5f8ba8bce7906
Cc: Apps Discuss <discuss@apps.ietf.org>, Mark Nottingham <mnot@mnot.net>, "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 am not going
> to support an IETF working group that says "nobody is allowed
> to do a better job describing HTTP than what is in our charter."
that's your choice, of course.  but the charter wording is up to the
IESG, and they have the authority to make decisions about what kinds of
activities are in scope and which kinds of activities are out of scope. 
(the draft charter being discussed is just someone's idea of a proposal
to be given to IESG and it's reasonable to debate it, or to suggest your
own draft charter to the applications ADs)

for better or worse, there's a lot of investment in the current prose. 
a drastic rewrite might remove some ambiguities but would certainly
create others - and also create questions about exactly what was
changed.  if HTTP is updated by making relatively minor tweaks where
possible, and major changes to text only when necessary, it's much
clearer what was changed than if there's a major restructuring/rewriting
of the document.  that, and rewriting would force a reset to Proposed
Standard and create an ambiguity over whether the Proposed or Draft
version were authoritative.

Keith