W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2014

Re: Our Schedule

From: Salvatore Loreto <loreto.salvatore@gmail.com>
Date: Mon, 26 May 2014 12:19:44 +0300
Cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <D03CC894-180A-4D5B-8BF9-2FBE78E7A5A3@gmail.com>
To: Greg Wilkins <gregw@intalio.com>

On May 24, 2014, at 12:43 PM, Greg Wilkins <gregw@intalio.com> wrote:

> I respect the IETF process and if all these issues have been raised before, discussed and put to consensus, then I'm put myself on mute and get on with implementing the protocol.   But the process does sometimes get it wrong and we really don't want to have a HTTP/2.1 any time soon.  So perhaps for a such an important protocol, rather than rush forward to LC and an RFC by the end of the year, perhaps pause, step back for a while, solicit some wider review and listen to some new voices and be prepared to re-evaluate if all the complexity is really justified?

Hi Greg

I don't think there is a rush here! 

On the contrary
due the fact that the protocol has been largely discussed in the mailing list and the f2f meetings and interims,
implemented and that people behind the implementations have had several chances to interop
issuing a Working Group Last Call with a deadline in mid-July is actually a reasonable thing to do

A WG LC period but sometime also only the awareness that the WG LC is approaching
is the best way to solicit comments from a larger audience:
people with a fresh eyes as well as people that have only recently re-engaged with this protocol design.
It is the right way to make sure that "no important concerns have been missed or misunderstood".

We have also be aware of the fact that there can be more then one WG LC.
I think that what Mark was describing in his mail, is only how the process will evolve if everything goes smoothly


Received on Monday, 26 May 2014 09:20:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:30 UTC