IETF Logo Mail Archive

[QUIC] h2 mapping - extensions

Patrick McManus <patrick.ducksong@gmail.com> Thu, 03 November 2016 21:52 UTC

Return-Path: <patrick.ducksong@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 BC82512944A for <quic@ietfa.amsl.com>; Thu, 3 Nov 2016 14:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.63
X-Spam-Level:
X-Spam-Status: No, score=-0.63 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, HTML_IMAGE_ONLY_12=2.059, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] 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 czPUUqABlDav for <quic@ietfa.amsl.com>; Thu, 3 Nov 2016 14:52:49 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 725B0127A91 for <quic@ietf.org>; Thu, 3 Nov 2016 14:52:49 -0700 (PDT)
Received: by mail-oi0-x22b.google.com with SMTP id v84so113585436oie.3 for <quic@ietf.org>; Thu, 03 Nov 2016 14:52:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=uv0rv69etqTG9eI4GfE/QWLRTSvLDdAKvrfauP3PC74=; b=rEEqMBNC4LAuBN57CozQ8i9pyE3McsJ5A39zqZYCklAXzBMleuweNa7W/q+dDS3Vul Jt9mNOzQEHPjYELRi0mRNefaawibE6m22icGrWXwx92iDWYpLZltNn/5ujZViIjUBlRZ R4mPbIFyw5HztfS1x3C5DJx0lXyjBmwowRdq2HvtMPfgKmipEzgB5lH/Yf9KY874Akci ghtEa3HNCTLJjLAEkg+Wvl8vc8ppRi8MVYo0M5OMAhC0Jy4nD0Vqc8orl3eIBvLIcDoC VQpOBpWxgfpeyUA++Jh0svdAOl7sZZPBNjPG7+Zjzq5N1/zKfA2gRxmR1ezhskbr2JHu Wz7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=uv0rv69etqTG9eI4GfE/QWLRTSvLDdAKvrfauP3PC74=; b=f1AQM5LDG1ZwIjFUO525Kr8k/HAvaCwOOUedrG8zX7LaJaEnQ3ANB0RrxJt75Agthz wk14wzdK7bVMdFQoK/lxNIyBO4yPhdjIKwRNDGejQL7ZYdu+dK1M/lpk28M1byvocWx2 466QIfTOvzJWu5u8XpAJpVgotIz23vdSvXwGKQ90czpG12/R02B1RJMXIbY76dmJvAbq BzJAFCLgS6h7DQvGNHeliVChz9snaY7UcucFNGYXevjUgSmCMeT7xKZGkrvZvu/gKUt5 GC42xh6CAYkWWnxTdWvF3xyewuRienCVtLcF/lZq5dpU1bPTuu8mPVhqQT8vPp/yrBi1 BQmg==
X-Gm-Message-State: ABUngvd321T3LeP3q0p/Syp9b8SywDCX3Ji7nsQAxsC9SIECFH+WSd9VoQiMfQMP9vuEay1KoyCi6tk6nCltMw==
X-Received: by 10.107.57.135 with SMTP id g129mr2805742ioa.178.1478209968467; Thu, 03 Nov 2016 14:52:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.228.236 with HTTP; Thu, 3 Nov 2016 14:52:48 -0700 (PDT)
From: Patrick McManus <patrick.ducksong@gmail.com>
Date: Thu, 03 Nov 2016 17:52:48 -0400
Message-ID: <CAOdDvNoNvGRCRuLGZiHJvkakU+yH-+k0=KaUcF4Msz8q+0qnZA@mail.gmail.com>
To: quic@ietf.org
Content-Type: multipart/alternative; boundary="001a114ac3e213128005406c94bd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/dweFPb595kum0OooZ2gbSBqdI3U>
Subject: [QUIC] h2 mapping - extensions
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 03 Nov 2016 21:52:51 -0000

Hi Robbie, Mike, et al. Thanks for getting the ball rolling with
https://tools.ietf.org/html/draft-shade-quic-http2-mapping-00..

What is the thinking about rfc 7540 h2 extensions and the h2/quic mapping..
particularly the way it allows unspecified frame types which may or may not
require negotiation.

it seems some of these extensions may have stateful issues across streams,
ala hpack and some may not.

If the extension were only defined for h2-over-quic that would be for the
extension to sort out.. but it doesn't seem like we are limiting things to
be defined in quic vs tcp, or are we?

-Patrick

v2.23.0 | Report a Bug | By Email