IETF Logo Mail Archive

Re: EXTENSION frame

Martin Thomson <martin.thomson@gmail.com> Thu, 25 January 2018 04:02 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 2662F12E042 for <quic@ietfa.amsl.com>; Wed, 24 Jan 2018 20:02:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 JVHvFdq3w824 for <quic@ietfa.amsl.com>; Wed, 24 Jan 2018 20:02:40 -0800 (PST)
Received: from mail-ot0-x231.google.com (mail-ot0-x231.google.com [IPv6:2607:f8b0:4003:c0f::231]) (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 11D6A12D95B for <quic@ietf.org>; Wed, 24 Jan 2018 20:02:40 -0800 (PST)
Received: by mail-ot0-x231.google.com with SMTP id f100so5596954otf.3 for <quic@ietf.org>; Wed, 24 Jan 2018 20:02:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=a7ilJYM47STQ3RC8tqHy88i+zly7yDASgHqrw3JHqgU=; b=E1vYz1203ovmN+Y6oyqaUldiRUkhwil101ziAhFG0UF/2XNll1CoULLZsaRwf6tyts s9EWE7G6lW+qdrmfXsU44FE3hcgasYu80deOnunzYM+vP5opsWBXGpngcEmp+JUpb94o AKzh1bkA2BlEE9N/NWQO2xS2VGLgR4lU4R+kt3Lgh/dTvUiz9F8F0unQMPzSUnx39Bm9 rfvgjHsqOhUCnGr6/K8ORTDIxv1iJQ4u2vOUF7yhsPLw9XNZ8TPUyLmYEGhvT+DP8bPw rwH3Bow3d9SRrg2ZEHZ1NZeUDmeZrZGz6PfKAB7cb8otiS6jKFNzCsqlMlO6DmbygZOw PIEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=a7ilJYM47STQ3RC8tqHy88i+zly7yDASgHqrw3JHqgU=; b=HV9ninHl1DXHslNKvInnlbTjy7FXVuM5bTrUPrucQqD/r1pQClXsDcWC0jrh4L7Ej3 nrHE3qf9CL9YbXy+nP3k8CJy3lDQku6NQA9pdZpnmmXmw3CawD5k+Gb7715WAS2rz/2X UvhsFWprTKEm5iKLmUGtOSGTvHdON9Q8tmzzYUpNskihroEVas4KnQnVhZwt+0bvACbN uF3WhLAnD+N/qIhICzhH8YYrjVB8//ILf89RSWpIvd9+CEIs0zybMWKPJIaH6lifml4p maNSgSR+c8K1zHcg5R69cJe7A8dG1wR8dkvfYmFeTWgh62sWZsGJtRdeXFGfYxehMtgj Q8Pg==
X-Gm-Message-State: AKwxytdDEitm4zLgvlvY1axhCYhH/QoUK7PXlQVVSI9ow4RDO/t3ljKM q+kZcZwPOfKlWx6NHiZdV4gkH3DFHGIVUooGbeU=
X-Google-Smtp-Source: AH8x226TFKSRotEik8c/eWV6AW5cVRiNDQc0VkCPRGemSthps5bbZ3nGAXgsvfyeYhNsPMHhk7xHwFyN5UkQ0Enzxqc=
X-Received: by 10.157.0.102 with SMTP id 93mr10509761ota.175.1516852959282; Wed, 24 Jan 2018 20:02:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.8.46 with HTTP; Wed, 24 Jan 2018 20:02:38 -0800 (PST)
In-Reply-To: <CAAZdMad6Suk_LTxHzbFKG_h2Rbna0LuGVuUf2AnD1KoYb3_x6A@mail.gmail.com>
References: <CABkgnnWxGu3z6DG1cE4MmMwvcZQrJ3QQ3j7k=R_77_1PYUjHmg@mail.gmail.com> <CAAZdMad6Suk_LTxHzbFKG_h2Rbna0LuGVuUf2AnD1KoYb3_x6A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 25 Jan 2018 15:02:38 +1100
Message-ID: <CABkgnnUkW==kUqM07RoBijir+RoW2OJVoPOBFpwAKjMM5vpSuA@mail.gmail.com>
Subject: Re: EXTENSION frame
To: Victor Vasiliev <vasilvv@google.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/himm-N09UIb_rdnMhzT6hF4_82I>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
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, 25 Jan 2018 04:02:42 -0000

Creating reasons to tear down connections doesn't seem like a goal.

If you are concerned about the need to send things that the other side
doesn't support, then by all means negotiate the use of an extension
before sending it.  This only makes it *possible* to send something
without first negotiating support.

On Thu, Jan 25, 2018 at 2:09 PM, Victor Vasiliev <vasilvv@google.com> wrote:
> Is there a reason we can't go with TLS-style extension negotiation in the
> handshake?  This would allow fatal errors on unknown extension frames, and
> would save the peers the effort of sending things that are not supported.
>
> On Wed, Jan 24, 2018 at 8:05 PM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>>
>> This came up several times, and I think that having a pressure relief
>> valve is a nice thing.  We found this extremely valuable in h2 and the
>> obvious design is pretty simple.
>>
>> I expect that people will want to talk about the IANA policy that I've
>> proposed.
>>
>> https://github.com/quicwg/base-drafts/pull/1068
>>
>

v2.23.0 | Report a Bug | By Email