IETF Logo Mail Archive

RE: Clarification of transport and HTTP version compatibility

Mike Bishop <mbishop@evequefou.be> Wed, 09 May 2018 17:18 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 C875712D955 for <quic@ietfa.amsl.com>; Wed, 9 May 2018 10:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level:
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] 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 Qr80jmeJ0F3a for <quic@ietfa.amsl.com>; Wed, 9 May 2018 10:18:13 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0111.outbound.protection.outlook.com [104.47.40.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D86F912D950 for <quic@ietf.org>; Wed, 9 May 2018 10:18:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ECeXl1ihEfwtf7v5XwBoJtEIhAuXOpNhAhPqnefyGTg=; b=mHGpVost28TFaIIB3zlR3qVjFC4FEVHJEiKU6LMGIYU1+LbazY7jVndEM/5jxc+CuEjvuWrIzvYrKTH8UvEj9a+ZrjbQJJFs6ArNKFo7E+2BWEUJ5Yr1JmSX+CvogVnzkXP9TLsSK67558WNQtO4cUeiv81LEfq/N4yEs0NZVsQ=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1709.namprd08.prod.outlook.com (10.162.133.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.755.16; Wed, 9 May 2018 17:18:10 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0735.018; Wed, 9 May 2018 17:18:10 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Samuel Hurst <samuelh@rd.bbc.co.uk>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility
Thread-Topic: Clarification of transport and HTTP version compatibility
Thread-Index: AQHT56+xI3vQwOQ++kOo1AZLBRUIXaQno4FA
Date: Wed, 09 May 2018 17:18:10 +0000
Message-ID: <SN1PR08MB1854826DACF0454471CB162DDA990@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>
In-Reply-To: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>
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: [2603:3023:123:2900:2da8:81e8:86dc:e86e]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1709; 7:wVkmYAnrqYHkIqmfrxOITdqAsFb3F8JMTv3REDyxj4wdXmsE+1qos952ZlCj1ZkouT6fBphr04ndhtpqPJwJwLMaqUu7D9uVZMYJDJz1e3Jf3ll64mGOsQw0R7YIE5pTpfx1nJWbgmBrMdpIpwgE1jKYZGB/OrTjp89CkPop4UtwbPwUuHLUpsVsqQ/CZrFwUh6GS2mZhj32xQ3zV97YjFzSJGDRHxjY2sbEYLSJdx8Dh4AnQeDILpKP4NNtVYIa
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(5600026)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1709;
x-ms-traffictypediagnostic: SN1PR08MB1709:
x-microsoft-antispam-prvs: <SN1PR08MB1709D5BB5C43B3EAE5A60889DA990@SN1PR08MB1709.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3231254)(944501410)(52105095)(3002001)(93006095)(93001095)(10201501046)(149027)(150027)(6041310)(2016111802025)(20161123562045)(20161123558120)(20161123564045)(20161123560045)(6043046)(6072148)(201708071742011); SRVR:SN1PR08MB1709; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1709;
x-forefront-prvs: 0667289FF8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(39380400002)(346002)(366004)(396003)(39830400003)(189003)(199004)(13464003)(53754006)(6116002)(486006)(46003)(2906002)(97736004)(478600001)(2900100001)(446003)(81156014)(81166006)(8676002)(3280700002)(74316002)(3660700001)(86362001)(5660300001)(55016002)(53936002)(476003)(11346002)(7736002)(229853002)(305945005)(9686003)(6246003)(74482002)(106356001)(6436002)(33656002)(102836004)(99286004)(6506007)(53546011)(5250100002)(105586002)(110136005)(186003)(8936002)(25786009)(14454004)(76176011)(7696005)(316002)(68736007); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1709; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: D3DWFXJ+q8XS8R4T68v8QU9rF5VoxGqZ6md4fvQo4IgXbqxQCbKCDAOrynIXeWIgLyRbR/LbAO+Wb6Iaee9xmiN8fKkL1fGsUDnmaUfkf0hjImicdSKAIWQ4DTkCRL6yI643buC5kZbdxmZrMB2JpbL2DsSyHDdpvYqz91m6kx9w1AkkZh6N/bsgcU3C2Ge9
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 6ae4c620-5c1b-470e-e66b-08d5b5d0d6a6
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 6ae4c620-5c1b-470e-e66b-08d5b5d0d6a6
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 May 2018 17:18:10.0786 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1709
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/k0kjoM9G2DfBEfcmEfE-zWpTK6k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 09 May 2018 17:18:16 -0000

There's no firm restriction, no.  While I find it likely that draft deployments will choose to keep matching versions, the only restriction that the HTTP draft currently imposes is that it be a version of QUIC which uses TLS as the handshake protocol.

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Samuel Hurst
Sent: Wednesday, May 9, 2018 9:05 AM
To: IETF QUIC WG <quic@ietf.org>
Subject: Clarification of transport and HTTP version compatibility

Hi all,

Does the quic-transport version and the HTTP mapping version have to match? For example, could you negotiate QUIC draft-11, but the HTTP side is still using an older version (such as draft-09 to avoid the requirement of QPACK)?

As far as I understand it, the QUIC transport version is negotiated as part of the TransportParams in the appropriate TLS extension, and the HTTP mapping version is negotiated by ALPN. So in the example above, would it be acceptable to negotiate 0xff00000a as the transport protocol version, and then have an ALPN string of "hq-09"?

I'm then assuming that a valid Alt-Svc header for my example could be as
follows:

Alt-Svc: hq-09=":4443";quic="ff00000a"

The quic-tls draft mentions in Section 9.1 "The application-layer protocol MAY restrict the QUIC version that it can operate over", but none of the quic-http drafts that I've read list any such restriction.
Therefore, I'm then further assuming that it's safe to run whatever version of the HTTP mapping I like, unless there's a compatibility matrix between the various specs that I'm missing?

Best Regards,
Sam

v2.23.0 | Report a Bug | By Email