Re: Straw-man charter for http-bis
Mark Nottingham <mnot@mnot.net> Fri, 01 June 2007 00: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 1HtvSs-00044A-6y; Thu, 31 May 2007 20:58:02 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43)
id 1HtvSr-000444-Lu for discuss-confirm+ok@megatron.ietf.org;
Thu, 31 May 2007 20:58:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1HtvSr-00043w-C2
for discuss@apps.ietf.org; Thu, 31 May 2007 20:58:01 -0400
Received: from mxout-03.mxes.net ([216.86.168.178])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HtvSo-0004PS-Rz
for discuss@apps.ietf.org; Thu, 31 May 2007 20:58: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 EE8C55193D;
Thu, 31 May 2007 20:57:56 -0400 (EDT)
In-Reply-To: <DAC34319-CB4D-48B6-A53F-66345790F0FA@gbiv.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>
<DAC34319-CB4D-48B6-A53F-66345790F0FA@gbiv.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <AC54FD4E-2691-484B-AF35-1310599A4DE3@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, 1 Jun 2007 10:57:53 +1000
To: "Roy T. Fielding" <fielding@gbiv.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: Apps Discuss <discuss@apps.ietf.org>,
"ietf-http-wg@w3.org Group" <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:59 AM, Roy T. Fielding wrote: > It is not "if I don't get my way". Who appointed you to be the > determinant of group consensus in the first place? I am not going > to support an IETF working group that says "nobody is allowed > to do a better job describing HTTP than what is in our charter." > If you don't allow people to produce drafts, and allow the working > group to evaluate those drafts on the basis of whether the contents > are better or not, then all you are doing is dictating the content > of the specification based upon some imagined position of authority. You spoke about forking the HTTP spec if the IETF decided to go in a direction that you didn't like. Working outside the process is very different to working within it, whether that be in the charter discussions or the WG. Don't try to make this about me. > So, you should decide whether your work item is to replace 2616 > or to produce a list of errata to be published in RFC form. If it > is the former, than I know a lot more about this subject than you > and I know for a fact that just making small changes around the > edges is not sufficient. That's a naked appeal to authority, and I'll give it as much credence as it deserves. > We already tried that twice. I believe the circumstances are different; time changes things. > If I make the real changes that are needed in draft form and submit > them to the WG, then I will expect them to be evaluated without bias > or the WG to be closed. If the answer is "that's too much > for me to review, so you aren't allowed to do that in the IETF" > then I won't. I will do it elsewhere and the IETF specification > will become irrelevant. > >> Also, on what do you base the accusation that this is being driven >> by "short-term corporate agendas?" > > On the basis that you presuppose every work item as being limited > to what you want to do, rather than a task that can be accomplished > if someone does it, and the continual reference to vendors and > "developers" that never actually show themselves on this list. Can you substantiate that? >> In any case, I don't think re-organising parts of the spec is off >> the table; indeed, it's already been discussed on a small scale. >> Re-writing the entire spec sentence-for-sentence is, in my opinion. > > In your opinion. You chose to ignore mine, in spite of the fact that > I have a bit of history on the subject, and that is why I have to make > comments on these proposals. I'm not ignoring you, Roy. However, you're making the same arguments repeatedly. If you make arguments that convince me, or if you can get other people to agree with you, I'm happy to reconsider my opinion. Neither has happened yet. >>> If an IETF HTTP WG is to be recreated, then its task items should be >>> to create what the working group believes to be the best documents >>> to replace 2616 and 2617. The charter does not need to constrain >>> that. >> >> That would be disruptive and unproductive. You may be willing to >> re-write HTTP from scratch, but the review requirements are much >> higher than required for what we're attempting (with step-by-step >> diffs, by the way). >> >> Somehow, HTTP has been implemented and become one of the most >> widely-deployed application protocols today, despite your claims >> that the spec needs to be re-written from scratch. I don't hear >> *anyone* else saying that this necessary, or a realistic option. > > I don't hear anyone else saying that 2616 needs to be revised before > 2617, yet you continue to take that as an assumption. 2616 doesn't > *need* to be revised at all. 2617 desperately does need to in order > to meet the IESG requirements. Why is that unclear? Have you been following the same discussion that I have? Later, you said to Larry: > I said that I would if it were given a chance to be reviewed. > I offered as much to Lisa before this effort started, and before > the revision was public, and again once people started working on it, > and each of those times I was rebuffed because the people organizing > this WG don't think a full revision should be in scope. I'm willing to do a reasonable amount of work to polish the spec, but at this point am unwilling to commit to start from scratch, both because I don't think it's likely to be successful, or that I'd be able to put the time in. My perception is that most people are in the same boat. If you're willing to put that kind of effort in, good for you, but it would be misleading to say that I'd have the time to see it through to the end. If you want to do that, go ahead and find other people who are willing to make it work; that's what I've trying to do for this effort. -- Mark Nottingham http://www.mnot.net/
- Straw-man charter for http-bis Mark Nottingham
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis Paul Hoffman
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis Eliot Lear
- Re: Straw-man charter for http-bis Paul Hoffman
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis Paul Hoffman
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis Mark Nottingham
- Re: Straw-man charter for http-bis Paul Hoffman
- Re: Straw-man charter for http-bis Mark Nottingham
- RE: Straw-man charter for http-bis Larry Masinter
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis -- call for er… Mark Nottingham
- Re: Straw-man charter for http-bis Eliot Lear
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis -- call for er… Julian Reschke
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis Eliot Lear
- Re: Straw-man charter for http-bis Mark Nottingham
- Re: Straw-man charter for http-bis Eliot Lear
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis Eliot Lear
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis -- call for er… Julian Reschke
- Re: Straw-man charter for http-bis -- call for er… Cyrus Daboo
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Mark Nottingham
- Re: Straw-man charter for http-bis -- call for er… Cyrus Daboo
- Re: Straw-man charter for http-bis Alexey Melnikov
- Re: Straw-man charter for http-bis Alexey Melnikov
- Re: Straw-man charter for http-bis Yves Lafon
- Re: Straw-man charter for http-bis -- call for er… Robert Sayre
- Re: Straw-man charter for http-bis Robert Sayre
- Re: Straw-man charter for http-bis -- call for er… Robert Sayre
- Re: Straw-man charter for http-bis -- call for er… Robert Sayre
- Re: Straw-man charter for http-bis Roy T. Fielding
- Re: Straw-man charter for http-bis -- call for er… Henrik Nordstrom
- Re: Straw-man charter for http-bis -- call for er… Henrik Nordstrom
- Re: Straw-man charter for http-bis Robert Sayre
- Re: Straw-man charter for http-bis -- call for er… Robert Sayre
- Re: Straw-man charter for http-bis Mark Nottingham
- Re: Straw-man charter for http-bis Mark Nottingham
- Re: Straw-man charter for http-bis Mark Nottingham
- Re: Straw-man charter for http-bis Mark Nottingham
- Re: Straw-man charter for http-bis Mark Nottingham
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Robert Sayre
- RE: Straw-man charter for http-bis -- call for er… Henrik Nordstrom
- Re: Straw-man charter for http-bis Henrik Nordstrom
- Re: Straw-man charter for http-bis Roy T. Fielding
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis John C Klensin
- Re: Straw-man charter for http-bis Eliot Lear
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Paul Hoffman
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Robert Sayre
- Re: Straw-man charter for http-bis Chris Newman
- Re: Straw-man charter for http-bis Julian Reschke
- Re: Straw-man charter for http-bis Alexey Melnikov
- Re: Straw-man charter for http-bis Paul Hoffman
- RFC2616 vs RFC2617, was: Straw-man charter for ht… Julian Reschke
- Re: Straw-man charter for http-bis Keith Moore
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Keith Moore
- Re: Straw-man charter for http-bis Julian Reschke
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Julian Reschke
- Re: Straw-man charter for http-bis Paul Hoffman
- Re: Straw-man charter for http-bis Eliot Lear
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Keith Moore
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Lisa Dusseault
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Stephane Bortzmeyer
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Joe Orton
- Re: Straw-man charter for http-bis Henrik Nordstrom
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… lists
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… lists
- Re: Straw-man charter for http-bis Eliot Lear
- Re: Straw-man charter for http-bis Chris Newman
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Chris Newman
- Re: Straw-man charter for http-bis Henrik Nordstrom
- Re: Straw-man charter for http-bis Lisa Dusseault
- Re: Straw-man charter for http-bis Martin Duerst
- Re: Straw-man charter for http-bis Henrik Nordstrom
- Re: Straw-man charter for http-bis Keith Moore
- Re: Straw-man charter for http-bis Julian Reschke
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Mark Nottingham
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Stephane Bortzmeyer
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Adrien de Croy
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Stephane Bortzmeyer
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… tom.petch
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Keith Moore
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… tom.petch
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Keith Moore
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Mark Nottingham
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Adrien de Croy
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… Chris Newman
- Re: Straw-man charter for http-bis Chris Newman
- Re: Straw-man charter for http-bis Henrik Nordstrom
- Re: Straw-man charter for http-bis der Mouse
- Re: Straw-man charter for http-bis Keith Moore
- Re: RFC2616 vs RFC2617, was: Straw-man charter fo… tom.petch
- Re: Straw-man charter for http-bis Mark Nottingham
- Character encodings in headers [i74][was: Straw-m… Mark Nottingham
- Re: Character encodings in headers [i74][was: Str… Keith Moore
- Re: Character encodings in headers [i74][was: Str… John C Klensin
- Re: Character encodings in headers [i74][was: Str… Clive D.W. Feather
- Re: Character encodings in headers [i74][was: Str… Martin Duerst
- Re: Character encodings in headers [i74][was: Str… Martin Duerst
- Re: Character encodings in headers [i74][was: Str… Mark Nottingham
- Re: Character encodings in headers [i74][was: Str… Martin Duerst
- Re: Character encodings in headers [i74][was: Str… Mark Nottingham
- Re: Character encodings in headers [i74][was: Str… Clive D.W. Feather
- Re: Character encodings in headers [i74][was: Str… Clive D.W. Feather
- Re: Character encodings in headers [i74][was: Str… Keith Moore
- Re: Character encodings in headers [i74][was: Str… der Mouse
- Re: Character encodings in headers [i74][was: Str… Keith Moore
- Re: Character encodings in headers [i74][was: Str… Stefanos Harhalakis
- Re: Character encodings in headers [i74][was: Str… Keith Moore