ALT_SVC HTTP/3 Frame?
Ryan Hamilton <rch@google.com> Wed, 18 September 2019 20:02 UTC
Return-Path: <rch@google.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 944BB120CDC for <quic@ietfa.amsl.com>; Wed, 18 Sep 2019 13:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Level:
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 3ICml8s4BCI2 for <quic@ietfa.amsl.com>; Wed, 18 Sep 2019 13:02:46 -0700 (PDT)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (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 5590F120CAD for <quic@ietf.org>; Wed, 18 Sep 2019 13:02:38 -0700 (PDT)
Received: by mail-wm1-x330.google.com with SMTP id x2so1562824wmj.2 for <quic@ietf.org>; Wed, 18 Sep 2019 13:02:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=9Ss7yuCWLoRaqJz3spO8pdWeYJQKTsfdnbVbmXqQQyE=; b=v4VRGtXC1j/6CTitAYIxW8GvbSDDlDkF0kVt4Z2Ygcir6ghfTJvyrG7AhvZpWKp044 /M/MQgEZrpPfRXhwBfv55jGpsg7tKWSzu5QU5yz3+Q7yAQyj//MNJaXRP7S6cGxTwqTM tFUPa56Ps3ZnC7A4BgCqT58QnBgMUfCnRI4zSwyCj3nYLkwNv/Hs6tWrRo6LlZ6NDr9h zR3Md53XBZNGiE2FYcGQGse4XHryiS9Z0qOoHb1HocI0RPH1MmlZhx6D8q9ht1YRpZNE 51ta7repBl74VBcLPM9gfLtOG4tzAhGBS5GJ7N81k9Lohflwd+7woMp2cm4oHPyG4miL vPKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=9Ss7yuCWLoRaqJz3spO8pdWeYJQKTsfdnbVbmXqQQyE=; b=BsUbC8SVt6yPGugZvQDyNM9aX3SER7l4XOSnF9Q8fqeo7BO8CZQflUlgskQkkxdW6m lx5NOGkZCqyEZQVl/DYL1IsGqvFElSbZdrS1/qNUabV8Be7gJyFOPIzmDx+K8s1Gfu42 TCxEzDyB/6kY9JAvbQqI0cNKG6EaWOreeEy5FBFrRn3Nx8Ocmbo+WSJ8v7u7UqHFbSL3 it1zwK8+zBpf3dMeD/8qJc2FBpd2IPp3DMk0nURU4cfl5We2hXhJSgddnj9NlQmgT1bz Qj5z38oQFTf8wP1ldoHjTcgqxq9ZMroZPGYXp473iHimNO8DACIEJSL/kn1VFL4axLba ymwA==
X-Gm-Message-State: APjAAAW6aRxIRrYPkne5cdKuFcaxxkbUKplBh2K2WVq1BPyVnv5GvF3i zFpEV7f6IwX7f7Ag/I2wts2/YG+IPFtWwjVDNnmxIAjEMrAMRA==
X-Google-Smtp-Source: APXvYqzL/UWIz8VKaWjH4QhRl+d6p84FvGf6CuEh2fWIcB7o8pk92rBTLcv+PXlx7roF4xBJ746ORGopdKrpT0OYbUg=
X-Received: by 2002:a1c:cf05:: with SMTP id f5mr4239109wmg.131.1568836955654; Wed, 18 Sep 2019 13:02:35 -0700 (PDT)
MIME-Version: 1.0
From: Ryan Hamilton <rch@google.com>
Date: Wed, 18 Sep 2019 13:02:21 -0700
Message-ID: <CAJ_4DfQxHg2Lcu4a0bNWoX35XxJS+CFm8b1r_360oJ4nCnpdjQ@mail.gmail.com>
Subject: ALT_SVC HTTP/3 Frame?
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007422150592d951cb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/09cYCCh3PlHZouvhNnA9k6bwClw>
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: Wed, 18 Sep 2019 20:02:50 -0000
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
- ALT_SVC HTTP/3 Frame? Ryan Hamilton
- Re: ALT_SVC HTTP/3 Frame? Lucas Pardue
- Re: ALT_SVC HTTP/3 Frame? Ryan Hamilton
- Re: ALT_SVC HTTP/3 Frame? Lucas Pardue
- RE: ALT_SVC HTTP/3 Frame? Mike Bishop
- Re: ALT_SVC HTTP/3 Frame? Martin Thomson
- Re: ALT_SVC HTTP/3 Frame? Ryan Hamilton