IETF Logo Mail Archive

RE: ALT_SVC HTTP/3 Frame?

Mike Bishop <mbishop@evequefou.be> Thu, 26 September 2019 18:15 UTC

Return-Path: <mbishop@evequefou.be>
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 71FEB120103 for <quic@ietfa.amsl.com>; Thu, 26 Sep 2019 11:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.com
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 x9zKy8HGXTX0 for <quic@ietfa.amsl.com>; Thu, 26 Sep 2019 11:15:19 -0700 (PDT)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-eopbgr820093.outbound.protection.outlook.com [40.107.82.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74C021200F9 for <quic@ietf.org>; Thu, 26 Sep 2019 11:15:14 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cextnJHraMrSk2V9syWKz5zuEPf1zOWwzd2gcSTH0zUGQ8jfTk0cZ08ZFPjK1ueJAgsT9Ybrw38mV/CCme0q7sLXskI/ixk2prYt2ymOyzTli8m2YNdzUrod8nDzD2eFEkxLJu9Jn/aD23ulBRRFns/nFHdoiGf2bam8Bfn1maAf17Zy4oxOQjEFzElAdc2fIb3D1eZljwZxXjEec3d+GxavzZZMImmnPAR1bgm+ilOskLB52cBCS1Ee/32F+sWcwuJR8jAcPXuHuUTDGd0neMJi64o6QUnO2qMfSsvm0SLDrnS55d0M5c7gcfAYrSBDdwwF+Yxv1+zKm+oF3b9Txg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VIkFSDKgPGRd/JLBICM93iWOGnZm4xfPQhWfeoes6d0=; b=iVIVylSOr+q3imRnSuNtupU2zpKfNwsNJ7prMeQzjRBe746eVfqBhIoUjJMNtcwC072OZCBxY5fE4da4qHi9eI0AdKp/Lvg51R1XLqZELsgq66B/2Fdirc/xdfEA0iUURCW64BsN7rlowNQr73a1uhp601eScE0tGsRxS+q64qogcQfUeE3buokk1HMqRLPCW8RMoGXaee/YOMPc7vAgzlvGbeYZQG0lNr2Nd4Qkrfe8debajYFhEC65tlEsaNtmyembzX0imv080uNyi+qEuIqqr3dLrSW9foH44Cm9+fIKma2/HtcP3XShbeZSjS5TBPkWVBnxA0VLjvfONw574A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=evequefou.be; dmarc=pass action=none header.from=evequefou.be; dkim=pass header.d=evequefou.be; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector2-evequefou-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VIkFSDKgPGRd/JLBICM93iWOGnZm4xfPQhWfeoes6d0=; b=PnK5QitUyYNWpsbJvzsb/v5iG4JxJDAFAUwlBZInOy4DzeXfJKidjaRlSxwK5rybX89hXJl6EbR9CIfc9v+QdHI3+hP7dqN8OmYVX6EXfeLdfSKcnxGTKfLLwEhEc/Aae72nclR9k4zsNSjmeLkI9YJkhlaiOGN2pW4ILTphZzI=
Received: from BN6PR2201MB1202.namprd22.prod.outlook.com (10.174.80.146) by BN6PR2201MB1537.namprd22.prod.outlook.com (10.174.85.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2284.22; Thu, 26 Sep 2019 18:15:12 +0000
Received: from BN6PR2201MB1202.namprd22.prod.outlook.com ([fe80::288b:d6ec:1e00:c3c]) by BN6PR2201MB1202.namprd22.prod.outlook.com ([fe80::288b:d6ec:1e00:c3c%12]) with mapi id 15.20.2284.028; Thu, 26 Sep 2019 18:15:12 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>, Ryan Hamilton <rch@google.com>
CC: QUIC WG <quic@ietf.org>
Subject: RE: ALT_SVC HTTP/3 Frame?
Thread-Topic: ALT_SVC HTTP/3 Frame?
Thread-Index: AQHVblwVPtjrnt/nkkad/ZHdgoD1O6cx4H8AgAAZJgCAAAi7gIAMTN/Q
Date: Thu, 26 Sep 2019 18:15:11 +0000
Message-ID: <BN6PR2201MB120231AF466A48BD40367665DA860@BN6PR2201MB1202.namprd22.prod.outlook.com>
References: <CAJ_4DfQxHg2Lcu4a0bNWoX35XxJS+CFm8b1r_360oJ4nCnpdjQ@mail.gmail.com> <CALGR9obKuxm4Ap=Dc9vpj7QBsfiuQ7JvWqYvQDcBjiauF+=Qag@mail.gmail.com> <CAJ_4DfSQ7AmZosRsk4cdCjzO_zMW5XgOFT6WRrV-UGDpcUMcqw@mail.gmail.com> <CALGR9oZf2TX8_1yPnOrR3=Dc_Sf5CD5LrEJMg120zu4nxLD-zg@mail.gmail.com>
In-Reply-To: <CALGR9oZf2TX8_1yPnOrR3=Dc_Sf5CD5LrEJMg120zu4nxLD-zg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be;
x-originating-ip: [2600:2b00:931f:a301:ad10:cc00:8cc7:f6a6]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 74226176-74e7-496f-377a-08d742ad78ea
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(5600167)(711020)(4605104)(1401327)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(2017052603328)(7193020); SRVR:BN6PR2201MB1537;
x-ms-traffictypediagnostic: BN6PR2201MB1537:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BN6PR2201MB153756568F6F15DA6C3CC326DA860@BN6PR2201MB1537.namprd22.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0172F0EF77
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(396003)(39830400003)(136003)(366004)(376002)(189003)(199004)(64756008)(25786009)(66446008)(2906002)(7736002)(6246003)(790700001)(6116002)(606006)(9686003)(99286004)(81166006)(54896002)(7696005)(81156014)(236005)(14444005)(6306002)(53546011)(86362001)(256004)(8936002)(102836004)(8676002)(55016002)(71200400001)(476003)(71190400001)(46003)(11346002)(446003)(486006)(186003)(74316002)(14454004)(76176011)(229853002)(6506007)(6436002)(33656002)(508600001)(966005)(316002)(66946007)(4326008)(110136005)(76116006)(5660300002)(66476007)(66556008)(52536014); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR2201MB1537; H:BN6PR2201MB1202.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: TmIZuVpjTOeiYxkZpLrpL+X49ObFq+bNBnIxyhz78wE5GVAYkhK2KwhdHLeSgO/k/IqxR3HLE6uq5+1vw+5IuNwbGIvGGrMFQ9dMggoWJEUv9LVncLcWpfPHqeq+T1dHx4qRSiEK43AJvOYyJ7XjdncGWhITEZ3Nd8Zz82PArYAVQgkUjBntQP2ppJwmikt5rKE8jd9pGTr2uwwxo6dYJIjlMa/ZrqiPUYhXHi94XyJLfZQ4BUh/rO+e+QD5UqnitEUw75fwmAuPrOX/IuFVlAgT5cLOvQ4L9re2kU5vcgwbfYKdcktzeK9wGvGs3t8v8ZFyfaAtLpq0G9QZUZDMzcQAx0eC2QY3pCpMRpfEc/JjuWS0KtG/x+ItS5ED4FJWz8zuTx/89Lz5b3+MqCW0jXHNBQTUGQCSRxiRbtRSXFx351OQR7p4OjQoEJ1hVorGt3X9BVWgvUUZmtgs9DbTzQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BN6PR2201MB120231AF466A48BD40367665DA860BN6PR2201MB1202_"
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 74226176-74e7-496f-377a-08d742ad78ea
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Sep 2019 18:15:11.9226 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 2m8I1mgUz7ta7AhZohJqimMBGcIIuzYgS4QesH9bl+vOfcZI9EeWLZSQE5N0QnprfRq75eWP1JUs5CxmvUk/GQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR2201MB1537
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nYgb4BjNKnGOdWZDH6bJFiBlYW8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 26 Sep 2019 18:15:23 -0000

The language in A.2.3 is talking about what is involved in porting an HTTP/2 extension to HTTP/3.  In A.2.4 it says, “Frame types defined by extensions to HTTP/2 need to be separately registered for HTTP/3 if still applicable.”  Perhaps that sentence should be in A.2.3 instead.

From: QUIC <quic-bounces@ietf.org> On Behalf Of Lucas Pardue
Sent: Wednesday, September 18, 2019 6:22 PM
To: Ryan Hamilton <rch@google.com>
Cc: QUIC WG <quic@ietf.org>
Subject: Re: ALT_SVC HTTP/3 Frame?

I think in the last 2 years we've gained a better understanding of what HTTP/3 is, how it varies from HTTP/2 and can tighten up the language. I'll let Mike answer for his own doc though.

Lucas

On Wed, 18 Sep 2019, 22:51 Ryan Hamilton, <rch@google.com<mailto:rch@google.com>> wrote:
Howdy,

Ah, great! That helps. That being said, I think I'm not clear on what the language in A.2.3 means. Is it saying:
1) "Hey, when you get around to specifying an HTTP/3-specific version of an HTTP/2 frame type extension is should be pretty easy"
2) Or, "HTTP/2 extensions are translated to HTTP/3 like this."

Given Mike's draft, I'm guessing it's 2? If so it might make sense to clarify A.2.3?

Cheers,

Ryan

On Wed, Sep 18, 2019 at 1:21 PM Lucas Pardue <lucaspardue.24.7@gmail.com<mailto:lucaspardue.24.7@gmail.com>> wrote:
Hi Ryan,

Mike actually has an expired draft for this [1] dating back to 2017. The code point (0xA) is the same, we've been careful to avoid the H3 frames colliding.
Maybe time to dust the ID off..

Lucas

[1] - https://tools.ietf.org/html/draft-bishop-httpbis-altsvc-quic-00

On Wed, Sep 18, 2019 at 9:03 PM Ryan Hamilton <rch=40google.com@dmarc.ietf.org<mailto:40google.com@dmarc.ietf.org>> wrote:
Howdy Folks,

I'm trying to understand the state of the ALT_SVC frame in HTTP/3. It is not explicitly defined in the HTTP/3 draft, as far as I can tell. However, A.2.3 says

... frame type HTTP/2 extensions are typically portable to QUIC simply by replacing Stream 0 in HTTP/2 with a control stream in HTTP/3.

Does this mean that I can send an HTTP/3 frame with type 0xa<https://tools.ietf.org/html/rfc7838#section-4> on the HTTP/3 control stream with the payload:

    +-------------------------------+-------------------------------+
    |         Origin-Len (16)       | Origin? (*)                 ...
    +-------------------------------+-------------------------------+
    |                   Alt-Svc-Field-Value (*)                   ....
    +---------------------------------------------------------------+

Do I have that right?

Cheers,

Ryan

v2.23.0 | Report a Bug | By Email