Re: Straw-man charter for http-bis

Mark Nottingham <mnot@mnot.net> Thu, 31 May 2007 22:33 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 1HttCZ-0005DU-UT; Thu, 31 May 2007 18:33:03 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HttCX-0005DP-Sz for discuss-confirm+ok@megatron.ietf.org; Thu, 31 May 2007 18:33:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HttCX-0005DH-JJ for discuss@apps.ietf.org; Thu, 31 May 2007 18:33:01 -0400
Received: from mxout-03.mxes.net ([216.86.168.178]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HttCW-0005os-B1 for discuss@apps.ietf.org; Thu, 31 May 2007 18:33:01 -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 2A4E451925; Thu, 31 May 2007 18:32:57 -0400 (EDT)
In-Reply-To: <76323E9F0A911944A4E9225FACFC55BA04AFFB6C@WIN-MSG-20.wingroup.windeploy.ntdev.microsoft.com>
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> <76323E9F0A911944A4E9225FACFC55BA04AFFB6C@WIN-MSG-20.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <6B1691C7-73AB-4C05-8BC7-4D331CC12E3A@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: Fri, 01 Jun 2007 08:32:53 +1000
To: Paul Leach <paulle@windows.microsoft.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: Apps Discuss <discuss@apps.ietf.org>, "Roy T.Fielding" <fielding@gbiv.com>, 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

On 01/06/2007, at 8:05 AM, Paul Leach wrote:

> Sometimes, the best is the enemy of the good. I think this is one of
> cases. As all good engineers should, I have great emotional  
> sympathy for
> Roy's approach of producing the best possible HTTP spec, but while a
> brand-new, easy-to-implement-from HTTP/1.1 spec would sure be  
> wonderful,
> if it isn't very likely to get done, then it isn't in reality better
> than a careful revision of the current one. (Another aspect of good
> engineering is dealing with tradeoffs.)
>
> Indeed, the above analysis also applies to the proposed charter:
> wouldn't an informational RFC "HTTP Implementors Guide" be nearly as
> good as the proposed RFC2616bis? And far less work, hence available  
> much
> sooner?

That's an interesting suggestion. My initial feeling is that it might  
be harder to settle on text if given a blank slate.

Also, much of the work for bis is done, or in train -- see the issues  
list and draft-lafon. For the apps-discuss people who may not have  
seen them;
   http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/issues/
   http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon- 
rfc2616bis-latest.txt

> (And hey, since it isn't us, who are these evil "short-term corporate
> interests"? Are they available to  take other heat off us, too? :-)

I'm sure someone could be found, for the right price...

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