Re: Straw-man charter for http-bis

Yves Lafon <ylafon@w3.org> Thu, 31 May 2007 21:39 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 1HtsMf-0007Wu-Fr; Thu, 31 May 2007 17:39:25 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1Hteyv-0005aO-Hi for discuss-confirm+ok@megatron.ietf.org; Thu, 31 May 2007 03:22:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hteyq-0005TT-VP for discuss@apps.ietf.org; Thu, 31 May 2007 03:21:57 -0400
Received: from homer.w3.org ([128.30.52.30]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hteyn-00084R-GO for discuss@apps.ietf.org; Thu, 31 May 2007 03:21:56 -0400
Received: by homer.w3.org (Postfix, from userid 12961) id 564774F018; Thu, 31 May 2007 03:21:52 -0400 (EDT)
Date: Thu, 31 May 2007 03:21:52 -0400 (EDT)
From: Yves Lafon <ylafon@w3.org>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Straw-man charter for http-bis
In-Reply-To: <C1E6F3CB-49C6-4C0F-955A-3D69D26987C6@mnot.net>
Message-ID: <Pine.LNX.4.64.0705310312560.7945@ubzre.j3.bet>
References: <BA772834-227A-4C1B-9534-070C50DF05B3@mnot.net> <392C98BA-E7B8-44ED-964B-82FC48162924@mnot.net> <p06240843c2833f4d7f2f@[10.20.30.108]> <465D9142.9050506@gmx.de> <465D987F.5070906@cisco.com> <C1E6F3CB-49C6-4C0F-955A-3D69D26987C6@mnot.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
X-Mailman-Approved-At: Thu, 31 May 2007 17:39:23 -0400
Cc: Paul Hoffman <phoffman@imc.org>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, Eliot Lear <lear@cisco.com>, Apps Discuss <discuss@apps.ietf.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

On Thu, 31 May 2007, Mark Nottingham wrote:

>> Creating an update without addressing it seems to me pointless.
>
> Not to me. The scope of the two activities is vastly different; I've only 
> seen support for doing minor changes and clarifications to 2616, while 2617 
> needs wholesale revision or replacement in many eyes.

At worst, basic auth could be back in 2616, but fixing auth in general or 
even the issues with digest is way bigger than what planned in the 
proposed scope.

> Paul just noted that if the efforts are temporally linked, doing them 
> separately is a waste of resources. I'm wondering if they are; e.g., could a 
> WG do 2616bis, and then be re-chartered to do 2617bis (with a similar scope)?

If two groups are created, there will be overlap in membership, but not 
in the work done, so I don't see a big issue here. I would be against 
doing a 2617bis to fix only typos, much more is needed.


-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

         ~~Yves