Re: HTTP/2 has been approved

ned+ietf@mauve.mrochek.com Thu, 19 February 2015 23:31 UTC

Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33D311A1A37 for <ietf@ietfa.amsl.com>; Thu, 19 Feb 2015 15:31:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gPkVnUbtErNC for <ietf@ietfa.amsl.com>; Thu, 19 Feb 2015 15:31:54 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8F3E41A1A2D for <ietf@ietf.org>; Thu, 19 Feb 2015 15:31:54 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PIPK8DQZXC005PNK@mauve.mrochek.com> for ietf@ietf.org; Thu, 19 Feb 2015 15:27:05 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 8bit
Content-type: TEXT/PLAIN; charset="windows-1252"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PIPGXFQU0G000090@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 19 Feb 2015 15:26:47 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01PIPK8BUPF2000090@mauve.mrochek.com>
Date: Thu, 19 Feb 2015 15:22:50 -0800
Subject: Re: HTTP/2 has been approved
In-reply-to: "Your message dated Thu, 19 Feb 2015 10:32:28 -0800" <B4CBAF0A-409B-4B45-B92E-CF148BF833B8@vpnc.org>
References: <96332FA9-9C09-4AD8-A76E-41593AA2652B@piuha.net> <20423.1424358980@sandelman.ca> <D4E24112-71EA-498F-BCF1-A202E97B677C@ieca.com> <B4CBAF0A-409B-4B45-B92E-CF148BF833B8@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/m2DbgiX2AhumI7CEJrjxJGmDOqY>
Cc: IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2015 23:31:56 -0000

> On Feb 19, 2015, at 10:09 AM, Sean Turner <turners@ieca.com> wrote:
> >
> > On Feb 19, 2015, at 10:16, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> >
> >> I propose that this document skip PS, and go straight to Internet Standard to
> >> accurately reflect the status of this document.
> >
> > Six months after it gets an RFC# I’d completely support this.

> Good god, no. HTTP/2 is quite complex, and it is likely that at least some parts will turn out to be non-optimal. Please give the HTTPBIS WG at least a year to shake out the protocol after wide deployment and constant use. Rushing the WG just so we can feel good about slapping a near-meaningless feel-good label on the spec is not a good process.

> Counter-proposal: we let the people closest to the protocol, the WG that created it, decide when to ask for STD status.

+1.

More generally, this all an attempt to solve a nonproblem. Essential documents
that have huge amounts of industry backing and where there's value seen in
progressing don't have any problem moving up the standards track. And HTTP/2 is
definitely such a document.

The problem is with smaller, arguably less essential documents, documents which
are important to their constituencies but which don't have the broad backing of
something like HTTP/2. That's where the road has proved to be too difficult to
travel.

				Ned