IETF Logo Mail Archive

RE: PUSH_HEADERS frame

Lucas Pardue <Lucas.Pardue@bbc.co.uk> Thu, 21 June 2018 18:08 UTC

Return-Path: <Lucas.Pardue@bbc.co.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D86B412F1A6 for <quic@ietfa.amsl.com>; Thu, 21 Jun 2018 11:08:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Bocz3KGvOgVk for <quic@ietfa.amsl.com>; Thu, 21 Jun 2018 11:08:43 -0700 (PDT)
Received: from mailout1.cwwtf.bbc.co.uk (mailout1.cwwtf.bbc.co.uk [132.185.160.180]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 984E0124C04 for <quic@ietf.org>; Thu, 21 Jun 2018 11:08:42 -0700 (PDT)
Received: from BGB01XI1003.national.core.bbc.co.uk ([10.184.50.53]) by mailout1.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w5LI8X0Y019732; Thu, 21 Jun 2018 19:08:33 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1003.national.core.bbc.co.uk ([10.184.50.53]) with mapi id 14.03.0389.001; Thu, 21 Jun 2018 19:08:33 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Roberto Peon <fenix@fb.com>, Martin Thomson <martin.thomson@gmail.com>, Mike Bishop <mbishop@evequefou.be>
CC: QUIC WG <quic@ietf.org>
Subject: RE: PUSH_HEADERS frame
Thread-Topic: PUSH_HEADERS frame
Thread-Index: AdQItM9/wr2FRkmcSU6cCT2bnOJHwAACdGVFAAJIJNAACF8SAAAC5KUlACIVeAAAAyZcvA==
Date: Thu, 21 Jun 2018 18:08:33 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BB5B23B@bgb01xud1012>
References: <BYAPR08MB3944A37B3230FAAA5448E16EDA770@BYAPR08MB3944.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB58F3A@bgb01xud1012> <BYAPR08MB394439B73E6495D7DCD09ECFDA770@BYAPR08MB3944.namprd08.prod.outlook.com> <CABkgnnU12bHq_OOz26EVjyGnaf41+VGCqriOk6sO8zZJkA83Ug@mail.gmail.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB5B115@bgb01xud1012>, <B088118C-9290-40A8-AB29-2021E2FD8AEA@fb.com>
In-Reply-To: <B088118C-9290-40A8-AB29-2021E2FD8AEA@fb.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.161.212]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-12.5.0.1300-8.2.1013-23922.000
x-tm-as-result: No-8.986800-8.000000-10
x-tmase-matchedrid: cgbqQT5W8he7lpQUW6Uvz7iMC5wdwKqdwZLXS0hN8p1QKAQSutQYXMX+ rw9BJFvkwj/YNxEfqolzxvUqN7uOVOyt+a9Mtf+eoprTEHvewADjmgMQ17h562Ek/mdKoRi5D+A 3vN265hecs+AAiy/A+HohyeDbLUuCn/KiuQleQIW8coKUcaOOvVT5iq0BT4XZ2oLGTNKlb9dYpc rLTXioByu9v6J5hdMYgDLqnrRlXrboYnQQ+lY28ZRMZUCEHkRt
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
x-tmase-result: 10--8.986800-8.000000
x-tmase-version: SMEX-12.5.0.1300-8.2.1013-23922.000
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/aVwhcU95kTkHKHYQkXrdijCwJ80>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2018 18:08:45 -0000

I'm arguing against the middle ground we currently have. So either typed streams, or extensions as untyped streams with HTTP framing to support disambiguation.

The downside of mandatory framing is it prevents unexplored use cases.

P.s. Another place to unframed data is the CONNECT method, exchange STREAM frames rather than DATA.

Lucas
________________________________________
From: Roberto Peon [fenix@fb.com]
Sent: 21 June 2018 18:30
To: Lucas Pardue; Martin Thomson; Mike Bishop
Cc: QUIC WG
Subject: Re: PUSH_HEADERS frame

As Mike showed, typed frames and typed streams are very much not the same.
Lucas, are you arguing for typed *frames* or typed *streams*?
-=R


-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------

v2.23.0 | Report a Bug | By Email