Re: Straw-man charter for http-bis

Mark Nottingham <mnot@mnot.net> Wed, 30 May 2007 22:58 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 1HtX7y-0007E5-8I; Wed, 30 May 2007 18:58:50 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HtX7w-0007Dz-L5 for discuss-confirm+ok@megatron.ietf.org; Wed, 30 May 2007 18:58:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HtX7w-0007Dr-BV for discuss@apps.ietf.org; Wed, 30 May 2007 18:58:48 -0400
Received: from mxout-03.mxes.net ([216.86.168.178]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HtX7v-0006rT-4C for discuss@apps.ietf.org; Wed, 30 May 2007 18:58:48 -0400
Received: from [192.168.1.102] (unknown [59.167.129.121]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id E73F65194C; Wed, 30 May 2007 18:58:44 -0400 (EDT)
In-Reply-To: <465D987F.5070906@cisco.com>
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>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C1E6F3CB-49C6-4C0F-955A-3D69D26987C6@mnot.net>
Content-Transfer-Encoding: 7bit
X-Image-Url: http://www.mnot.net/personal/MarkNottingham.jpg
From: Mark Nottingham <mnot@mnot.net>
Subject: Re: Straw-man charter for http-bis
Date: Thu, 31 May 2007 08:58:41 +1000
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: Paul Hoffman <phoffman@imc.org>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, 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 31/05/2007, at 1:30 AM, Eliot Lear wrote:

> The HTTP auth model needs a lot of work.

Agreed.

> 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.

To be fair, there are some small clarification/editorial-type issues  
(e.g., encoding of credentials) in 2617 that could be addressed by  
this style of charter. The concern that I have is that a) it would be  
difficult to keep the lid on and limit it to just those changes, and  
b) doing so would do a lot of good in the world, considering Kieth's  
point.

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)?

Cheers,


--
Mark Nottingham     http://www.mnot.net/