Re: HTTP/2 has been approved
Yoav Nir <ynir.ietf@gmail.com> Thu, 19 February 2015 15:36 UTC
Return-Path: <ynir.ietf@gmail.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 5DA101A9125 for <ietf@ietfa.amsl.com>; Thu, 19 Feb 2015 07:36:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 Eip1XBIXHwIj for <ietf@ietfa.amsl.com>; Thu, 19 Feb 2015 07:36:10 -0800 (PST)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F3EE1A9119 for <ietf@ietf.org>; Thu, 19 Feb 2015 07:36:02 -0800 (PST)
Received: by mail-wi0-f171.google.com with SMTP id hi2so48882075wib.4 for <ietf@ietf.org>; Thu, 19 Feb 2015 07:36:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Q66jKeSp9CMhwE3rhZAZIhFqPgXbe3AhjKQ3PDkYdbk=; b=W6PGBpuN2QYQBlNACCpx4bXXFx6wmsjxe+KCMWNx5yOZkSKyYI40DiNgWITSonV8p1 rFBhF10bPugvpC06eb6EM4tPLkctiGogqLWcANXr8GDaOv/keN4SkXiuhYZVGxZb6Fy7 8nZ04YB5f1buKXDZVrNr+2Rj4qLeo6gra/fMMmRZQOpbYAoWTn0P+XQyBBNAle2wdghS U6A/LcInLBokW/Tznu7am7a4yGG/MjMfPmWRXJTLTe8zGFtMgdygSBjj7cheBVL1J5v3 i6kO9qV7lbmpgud6D12xYjPlVWFtPDU8AV9yWnd+caX2gWDyaEs/2Ne6krYfJCqd+8Ip bnoQ==
X-Received: by 10.194.243.1 with SMTP id wu1mr10259998wjc.69.1424360161152; Thu, 19 Feb 2015 07:36:01 -0800 (PST)
Received: from [172.24.251.208] (dyn32-131.checkpoint.com. [194.29.32.131]) by mx.google.com with ESMTPSA id dj4sm37880232wjc.13.2015.02.19.07.36.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Feb 2015 07:36:00 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Re: HTTP/2 has been approved
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <20423.1424358980@sandelman.ca>
Date: Thu, 19 Feb 2015 17:35:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <006FB40B-1F60-4CC5-B000-1F17B2146FC6@gmail.com>
References: <96332FA9-9C09-4AD8-A76E-41593AA2652B@piuha.net> <20423.1424358980@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KJMr5uvnrqBTuRbRtEsV7ipyOks>
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 15:36:12 -0000
> On Feb 19, 2015, at 5:16 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote: > > > I'm very concerned about this part: > >> A key point in the protocol development process was the iteration the >> working group did between protocol updates, and implementations and >> testing. Certain draft protocol versions were labelled by the working group >> as "implementation drafts", and the participants -- many web browser and >> web server providers -- updated their implementations and tested out the >> protocol changes. Most of the interim meetings included part of a day spent >> on hands-on interoperability testing and discussion. The result is a >> thoroughly validated protocol that has been shown to interoperate and that >> meets the needs of many major stakeholders. > > It sure seems to me like those "implementation drafts" are what used to be > called proposed standards. Proposed standards also have to go through working group last call, AD review, IETF last call, IESG review, SecDir review, GenArt review, a six-week waiting period in the RFC editor’s queue, and AUTH48. I don’t think we can afford to do that for a single document every 4-6 months, like httpbis did for HTTP/2. > What I see is a new step in the standardization process, along with a view > that the step after internet-draft seems to include proven interoperability. Running code has always been part of the deal, at least as something we would like to have. Besides, the process continued even when some implementations did not interoperate. > I propose that this document skip PS, and go straight to Internet Standard to > accurately reflect the status of this document. There is currently pretty close to zero deployment in the real world. A bunch of lab implementations that managed to interoperate in a bake-off is not an indication of something ready for Internet Standard. But don’t you agree that publishing a document with the bunch of lab implementations is better than publishing it without them? Yoav
- HTTP/2 has been approved Jari Arkko
- Re: HTTP/2 has been approved Michael Richardson
- Re: HTTP/2 has been approved Yoav Nir
- Re: HTTP/2 has been approved Phillip Hallam-Baker
- HTTP/2 should be published at Internet Standard Michael Richardson
- Re: HTTP/2 should be published at Internet Standa… Yoav Nir
- Re: HTTP/2 has been approved Sean Turner
- Re: HTTP/2 has been approved Paul Hoffman
- Re: HTTP/2 has been approved Bjoern Hoehrmann
- Re: HTTP/2 has been approved Jari Arkko
- Re: HTTP/2 has been approved Eliot Lear
- Re: HTTP/2 has been approved David Morris
- Re: HTTP/2 has been approved ned+ietf
- Re: HTTP/2 should be published at Internet Standa… Larry Masinter
- Re: HTTP/2 has been approved Julian Reschke
- Re: HTTP/2 has been approved Julian Reschke