IETF Logo Mail Archive

Re: ALT_SVC HTTP/3 Frame?

Lucas Pardue <lucaspardue.24.7@gmail.com> Wed, 18 September 2019 20:21 UTC

Return-Path: <lucaspardue.24.7@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 CFEA1120086 for <quic@ietfa.amsl.com>; Wed, 18 Sep 2019 13:21:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level:
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 9N1Up2XsaZjc for <quic@ietfa.amsl.com>; Wed, 18 Sep 2019 13:21:23 -0700 (PDT)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (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 493CB120046 for <quic@ietf.org>; Wed, 18 Sep 2019 13:21:23 -0700 (PDT)
Received: by mail-vs1-xe35.google.com with SMTP id w195so690421vsw.11 for <quic@ietf.org>; Wed, 18 Sep 2019 13:21:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WM+J5jtMrzinfksYU3H3TXglasPCBzBYUaTQEgt6Hzg=; b=W+LmxsZgAVz+hVyZU0pBWaxyv2z5VQ/tlk5OFgTRxGEfPwd3A2tf0Gm1bgdK+FDqsi ZwlRK4Xmr2vghco8FgLux7oV9/XfEp2gYDmGdHh/e2gLmIJ0D3iHXemE9JsjIo/dio+D 6rnxdiG+lMIDRBZfVfgeA2YD6JucWKIeEcKYEaveNuFw1wPlY8pJoTcSkfkobBAR6/i7 iijHm1T4UMCc6ITBuzYaJBLA/aBxJCwlHUDW+SBeQpktPGTevM5Ygn5xpEPursp+ZJ0U /BckCtdrgnf4zzb2OQADXb7bM85NXVo1qqkDhFk9/nZKid3z+5QfELzQ6KNa1Zlvkfdj YAdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WM+J5jtMrzinfksYU3H3TXglasPCBzBYUaTQEgt6Hzg=; b=C/y33R9bkhzcYZZGLp3Jxe3ctnJqn4vFcmg6jK+39UmMkE9LJDHgxByceDcKUyqCIR LxklRrk9ikEfh470/INx4x72v+5mBwyU8JoyUbyqoXur13Iqzuw3c8VBdxwGlUtmF7oO FojFWsRPMcTzYv9SHjqAUXnBM2Q4E4fvY2+JVXW8ZUJh9gT0fqXLHSUL4gfuRxS2m/iF dX/T1BpyDpvydtSzf2h5noyVheMBCRisVLr5Oaw7WOTthnazr03jw2obPe7Qwuyg/iKN IAlL0fgLXVzBNrU0neUSsBv512Ky7A44feUHpp0DXOIJiIp4a6zUrhXZEgCDHpeHpnn/ 3P8w==
X-Gm-Message-State: APjAAAVSBpCdAqwgut5bElr6rkv6qvlQIjO/0lwLOpLre3IT1kZYg3a+ T+jo+pCRP4DxJ/qsIJrBzpr0KdGsQLzMd7EiMXA=
X-Google-Smtp-Source: APXvYqzQnFffv1vspOp5Xz6blUlN4oI2YOGdHBbe3uv/tSHbuWnPkkZlM9dmsxG6wyYgqV3fA0KzeHDMF+NozVHI3fM=
X-Received: by 2002:a67:c392:: with SMTP id s18mr3513018vsj.15.1568838082345; Wed, 18 Sep 2019 13:21:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAJ_4DfQxHg2Lcu4a0bNWoX35XxJS+CFm8b1r_360oJ4nCnpdjQ@mail.gmail.com>
In-Reply-To: <CAJ_4DfQxHg2Lcu4a0bNWoX35XxJS+CFm8b1r_360oJ4nCnpdjQ@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 18 Sep 2019 21:21:10 +0100
Message-ID: <CALGR9obKuxm4Ap=Dc9vpj7QBsfiuQ7JvWqYvQDcBjiauF+=Qag@mail.gmail.com>
Subject: Re: ALT_SVC HTTP/3 Frame?
To: Ryan Hamilton <rch=40google.com@dmarc.ietf.org>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009bc2950592d99480"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/gVSikLcmoorF9MtDDpgdL9bJttU>
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:21:25 -0000

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> 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