Re: Straw-man charter for http-bis -- call for errata/clarifications to 2617

Mark Nottingham <mnot@mnot.net> Thu, 31 May 2007 04:23 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 1HtcBx-0004qo-G5; Thu, 31 May 2007 00:23:17 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HtcBv-0004n4-JV for discuss-confirm+ok@megatron.ietf.org; Thu, 31 May 2007 00:23:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HtcBv-0004kt-7v for discuss@apps.ietf.org; Thu, 31 May 2007 00:23:15 -0400
Received: from mxout-03.mxes.net ([216.86.168.178]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HtcBs-00065l-Vf for discuss@apps.ietf.org; Thu, 31 May 2007 00:23:15 -0400
Received: from [127.0.0.1] (unknown [216.145.54.7]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 5C90A5197D; Thu, 31 May 2007 00:23:10 -0400 (EDT)
In-Reply-To: <000c01c7a318$7bc243e0$7346cba0$@org>
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> <000c01c7a318$7bc243e0$7346cba0$@org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E21FCD3A-D51A-4C06-B46D-3EA3ED54592B@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 -- call for errata/clarifications to 2617
Date: Thu, 31 May 2007 14:23:06 +1000
To: Larry Masinter <LMM@acm.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 'Paul Hoffman' <phoffman@imc.org>, 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 31/05/2007, at 10:13 AM, Larry Masinter wrote:

> I'm sympathetic to the desire to keep the charter narrow, but I wonder
> if it is feasible to update 2616 without updating 2617. I thought
> that it was more of a convenience and that the split between
> the two was (to some degree) artificial.
>
> If you really want to limit scope, what do you think about
> issuing an informational RFC on 'what changes are needed to 2617'
> (starting with the Sayre draft, I'd think)? Then 2616bis
> could be published and the group rechartered to do the
> 2617 update (and, if needed, yet another turn of the crank
> on 2616bisbis.)

Robert's draft is orthogonal to a 2617 update; the idea of that is to  
address the need for MTI security.

It would be interesting to compile issues for 2617 as well, to see  
what the scope of work would be. If we can keep the scope to errata  
and clarifications (i.e., not introducing new schemes), it might be  
doable.

Anybody?

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