IETF Logo Mail Archive

Re: [QUIC] draft-shade-quic-http2-mapping comments

Martin Thomson <martin.thomson@gmail.com> Sat, 23 July 2016 08:46 UTC

Return-Path: <martin.thomson@gmail.com>
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 B326E12B056 for <quic@ietfa.amsl.com>; Sat, 23 Jul 2016 01:46:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 GE21x3FepGC3 for <quic@ietfa.amsl.com>; Sat, 23 Jul 2016 01:46:04 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (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 00E2912D5BF for <quic@ietf.org>; Sat, 23 Jul 2016 01:46:03 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id s63so120205005qkb.2 for <quic@ietf.org>; Sat, 23 Jul 2016 01:46:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4ObYXmtoV4gqfc1ffcInl9txJii/8f6MXwfN0aFkVDQ=; b=IAVFxP+Q1hl/MmBNBQE3JPw2uc5Ds40HWV0TXC7Jn+d0EfYz0tjZEek1xPGwtaoNLS e4HVTUwkInUMEpaVXJs4NgglTwGYqMuHCAPxT1uVl4NTIAFgBjcRj5sJQELWDewg2Wg0 HwTtESu6pUsYubFkG7FtmdeAvnnvAmLKvAsupAhPYG77JwvbM/dvDcY+r7055N3PlGeo CBCsyJuIY7iilsi1dNeHM0IDjX6rW6uR9mjRUaPBlS78AgPFFG4V97Od9eyUmPeE1CsH sIUzxgnYNsyzdgpYGWmAVHCM+vWYmvHFUVcOuz3lDR1Os4lEmDqFODa2jTRM/ucSkGTE OG9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4ObYXmtoV4gqfc1ffcInl9txJii/8f6MXwfN0aFkVDQ=; b=fpwZD53y3qlcRJaFeiU2V2h43Vef9lagH+PH9lYCAEdljwloK6F6ZKQWBfBQCYADbO LaH+NCo2LkreB72G6KsOW5TcaGtSuBk8q25hWE9ARszdXijAIbm5KNjaorfWR9ERm6aQ FeLQXmr9EAI+eakOwff/dmFYQ2ICcI2COXiHBIHjGMpCOWBPFDBF3rkvpJEqRU0AhZIf QkjqW66SFXjNF5i0XpUauJlyaD2HWv6A2X5zvcp64jkd+Gqljqwn3jHbN2MHrqtoTD37 MiHeWnsoZfwtO4PtoVJkm08HT2fqytxetTKtFJsUP1k1jVl6KFXTK+K8374wa5qGJkzH QzQw==
X-Gm-Message-State: AEkoouu/vYwjU2z7MgFFVU9bOYSP0x1fOEQwxAA27czrohTMFU+iYFmKSHzZ9BJCxKvWP3PKNSgu/qe7dg1TdQ==
X-Received: by 10.55.203.156 with SMTP id u28mr10189304qkl.116.1469263563147; Sat, 23 Jul 2016 01:46:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.22.146 with HTTP; Sat, 23 Jul 2016 01:46:02 -0700 (PDT)
In-Reply-To: <d8af823c-0877-8c65-347f-edc3966fc3dd@greenbytes.de>
References: <CAGD1bZYWgZDkXhsdSVz9k47DiPjiW+TJomfZ9A1yeA6mAEzZ1g@mail.gmail.com> <d8af823c-0877-8c65-347f-edc3966fc3dd@greenbytes.de>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Sat, 23 Jul 2016 10:46:02 +0200
Message-ID: <CABkgnnVZkPp+DN=ZqUaP_FekCJ6A3B3bszFFsOVaB3wB9Db8Ug@mail.gmail.com>
To: Julian Reschke <julian.reschke@greenbytes.de>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-CKW1102yjEavuqz87hAsAlgMu4>
Cc: Jana Iyengar <jri@google.com>, quic@ietf.org
Subject: Re: [QUIC] draft-shade-quic-http2-mapping comments
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list to discuss QUIC standardization <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: Sat, 23 Jul 2016 08:46:05 -0000

On 22 July 2016 at 14:54, Julian Reschke <julian.reschke@greenbytes.de> wrote:
>>    Alt-Svc: quic=":443"
>
>
> Well, you'd need to register an ALPN identifiers "quic" for that. The
> problem is that (AFAIU) APLN tokens in theory are used to negotiate
> protocols over TLS, which is not the case here. I know that there are
> precedents with that, but if we really want to turn ALPN identifiers into a
> generic protocol negotiation mechanism, we really should talk to the TLS WG
> and potentially revise RFC 7301. (Alternatively, we could revise Alt-Svc, in
> which case you should talk to the HTTPbis WG).

Since we plan to use TLS, and to use ALPN for performing the integrity
check on version negotiation, this is OK in my view.  I think that in
the short term we will want to have something more specific than just
"quic".  I believe that someone at the BoF pointed out that getting
version negotiation in place early is important, and I agree with
that.  The draft numbering stuff we did with HTTP/2 might be something
we can lean on a little (as you point out).

v2.23.0 | Report a Bug | By Email