Re: Straw-man charter for http-bis

Mark Nottingham <mnot@mnot.net> Thu, 31 May 2007 10:53 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 1HtiHJ-0000qT-ND; Thu, 31 May 2007 06:53:13 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HtiHI-0000qO-VS for discuss-confirm+ok@megatron.ietf.org; Thu, 31 May 2007 06:53:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HtiHI-0000qE-L9 for discuss@apps.ietf.org; Thu, 31 May 2007 06:53:12 -0400
Received: from mxout-03.mxes.net ([216.86.168.178]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HtiHH-00031d-Dh for discuss@apps.ietf.org; Thu, 31 May 2007 06:53:12 -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 404F051981; Thu, 31 May 2007 06:53:06 -0400 (EDT)
In-Reply-To: <465E7B2F.8010304@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> <C1E6F3CB-49C6-4C0F-955A-3D69D26987C6@mnot.net> <Pine.LNX.4.64.0705310312560.7945@ubzre.j3.bet> <465E7B2F.8010304@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <35A8B74A-E78B-4A8B-85C1-7FCE72A7CE49@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 20:53:03 +1000
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: Yves Lafon <ylafon@w3.org>, 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

Considering the scope of 2616bis is errata, and explicitly not new  
features/mechanisms, I'm not sure I follow. Do you think that  
designing new auth mechanisms will expose new errata?

My initial thought is that it's much more likely that it'll require  
who new features, or no changes to HTTP at all.


On 31/05/2007, at 5:37 PM, Eliot Lear wrote:

> An authentication requirements document sits in "Last Call" right  
> now as we speak.  My concern is that we'll close 2616bis only to  
> discover that not only do we need a 2617bis but also a 2616bisbis.   
> The only real question is whether or not we can move fast enough on  
> the auth work so that you're not left twiddling your thumbs too long.


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