Re: [QUIC] Supporting HTTP/2 extension: frames and semantics

Ryan Hamilton <rch@google.com> Mon, 23 May 2016 04:38 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 2610E12D62D for <quic@ietfa.amsl.com>; Sun, 22 May 2016 21:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level:
X-Spam-Status: No, score=-4.126 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] 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 1MLjMe-cgr8u for <quic@ietfa.amsl.com>; Sun, 22 May 2016 21:38:37 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 4F54F12D62F for <quic@ietf.org>; Sun, 22 May 2016 21:38:34 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id n129so57444312wmn.1 for <quic@ietf.org>; Sun, 22 May 2016 21:38:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iSoeOqQOBuRGL+ZJTzCUmJSXmsSehvm6y3ithuina7I=; b=kB8xMQSP/ej5WVkXb/yMDNVPxcrSwhOCNG7YGl/3jhnlt3W9dXQOakzqUaDm1uP2Xk dCvF9VeVhXzJTerud+CKTdw98VCZxjWZj0NyTuRNFNiVKsZCwf+R2sa8JBHUCZEKF40A eOToyPkkHfodeyST4k8VNLTHqxADZ31vzjp6ZzVpE/r8dhJLeyr/L1lmOpp5T44hXBbW 9x+lkT+SVZ2fkhOY2RHzTy+icAr1rgoFfGu63B3Qi8zKOaf1a84kCbBy50OzcL+QPWvp OklKi0gvjT2U7KCjLspUpNXCm95Q+hFp7M+YOee65OuGmCfeQd8cDnZXMXacxKz2+6Ky E2VQ==
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=iSoeOqQOBuRGL+ZJTzCUmJSXmsSehvm6y3ithuina7I=; b=aPortGk9iMkmqqTK1Hk5+s3VEDRWLLyJSlJdkXRxqoVJz+FwwUeHZj6kZHhAZClAna ZLOEx1yKe/lu706KaX3qHmKen4f09OMoBrtthHHwY2AHC06QP9vc85vb3CsqFAQRE4IA +RUE9G+eKQhGt56YRt/0wP8jgmRPXZFASnnJ80pLpCYv/dpj+BWvLYUMT9nPbGWrEY3u wh1bycjCN9ccsv9FV9YyT2hlDC4qxyPCwu4ZOiu26RpKj+ktOZiODK9OROq7lpdGomLJ 0LPQujWMIwMhZ5+bn8tjJoVtlE108A1DZdOiorh7II2Xmb6zkyOEID2SIP83b5F/pGCB HKeg==
X-Gm-Message-State: AOPr4FWTrpRW1Q52ITMxmC04ThBYQbySdDTNV8BawWBgc/VdnDqzMc3EDc/mYPqpMEWfAKnkc/ufHNIIoqbdixM2
X-Received: by 10.194.205.105 with SMTP id lf9mr14116867wjc.25.1463978312672; Sun, 22 May 2016 21:38:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.46.151 with HTTP; Sun, 22 May 2016 21:38:31 -0700 (PDT)
In-Reply-To: <509EC821-B796-40A6-AE6D-C175D0F7F888@mnot.net>
References: <7CF7F94CB496BF4FAB1676F375F9666A2A80998D@bgb01xud1012> <509EC821-B796-40A6-AE6D-C175D0F7F888@mnot.net>
From: Ryan Hamilton <rch@google.com>
Date: Sun, 22 May 2016 21:38:31 -0700
Message-ID: <CAJ_4DfRV-7quudJV=hMqVBN34N2j+AEWZygDhPvP2afBHSu-Aw@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary="047d7b874c2449795005337b039e"
Archived-At: <http://mailarchive.ietf.org/arch/msg/quic/xrfIN7yZGJ_RCoGaMkRvdpvx8S8>
Cc: Lucas Pardue <Lucas.Pardue@bbc.co.uk>, "quic@ietf.org" <quic@ietf.org>
Subject: Re: [QUIC] Supporting HTTP/2 extension: frames and semantics
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: Mon, 23 May 2016 04:38:39 -0000

Agreed. Do you have any suggestions for language we could include in the
charter to ensure that this gets addressed satisfactorily?

On Sun, May 22, 2016 at 9:32 PM, Mark Nottingham <mnot@mnot.net> wrote:

> +1; I share this concern. There are a growing number of H2 extensions that
> are either in progress [1] or coming [2][3]; it would be good to avoid too
> much of a mess here.
>
> The same question arises for SETTINGSes.
>
> Cheers,
>
> 1. https://httpwg.github.io/http-extensions/origin-frame.html
> 2. https://tools.ietf.org/html/draft-bishop-httpbis-http2-additional-certs
> 3. https://datatracker.ietf.org/doc/draft-kazuho-h2-cache-digest
>
>
>
> > On 21 May 2016, at 1:22 AM, Lucas Pardue <Lucas.Pardue@bbc.co.uk> wrote:
> >
> > Hello,
> >
> > I would like to gain further clarification on the mapping of HTTP/2
> frames in QUIC, especially with regards to extension via new frame types.
> Is it anticipated that HTTP/2 extension frame types will be supported in
> QUIC and is there a feeling about how that would be defined?
> >
> > Previous QUIC documents have covered how to map HTTP/2 frame types such
> as HEADERS or DATA, however there was little explanation of how something
> like the ALTSVC frame [1] would be supported in QUIC (if at all). In the
> specific case of HTTP Alternative Services we can fallback on the header
> field crutch and use Alt-Svc to express the same service detail within a
> HEADERS frame. However, this does not hold true for other extensions such
> as the ORIGIN frame [2].
> >
> > I am also interested in understanding how QUIC might handle HTTP
> semantic extension such as proposed in the Peer-to-Peer Extension to HTTP/2
> [3].
> >
> > Lucas
> >
> > [1] https://tools.ietf.org/html/rfc7838
> > [2] https://datatracker.ietf.org/doc/draft-ietf-httpbis-origin-frame/
> > [3] https://tools.ietf.org/html/draft-benfield-http2-p2p
> >
> > _______________________________________________
> > QUIC mailing list
> > QUIC@ietf.org
> > https://www.ietf.org/mailman/listinfo/quic
>
> --
> Mark Nottingham   https://www.mnot.net/
>
> _______________________________________________
> QUIC mailing list
> QUIC@ietf.org
> https://www.ietf.org/mailman/listinfo/quic
>