IETF Logo Mail Archive

Re: [quicwg/base-drafts] Extension frames (#1068)

ekr <notifications@github.com> Mon, 09 April 2018 11:54 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC9F124B17 for <quic-issues@ietfa.amsl.com>; Mon, 9 Apr 2018 04:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 yGE2FROsYPs8 for <quic-issues@ietfa.amsl.com>; Mon, 9 Apr 2018 04:54:51 -0700 (PDT)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 B5D551241F5 for <quic-issues@ietf.org>; Mon, 9 Apr 2018 04:54:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=/zlHrIN/urVd/lTWxWvGJOlkPRw=; b=nHjxCZ/Lru44sGvK aZfcXYDPnqfBNpxIs4CmrMi9bhZaML5+gyaT9k1TmhHBmMsVsWhEiPWeK7ahSll/ 4+2hWrJTSUW1ATYupVduFNDXjwKgl5OMg88VY6UCjumZiYkl+RJQ55Bg2PQrXlID 5f1hQjlYGj7gTgn9ykF4HqgIS7o=
Received: by filter0484p1las1.sendgrid.net with SMTP id filter0484p1las1-30534-5ACB5447-11 2018-04-09 11:53:43.618588162 +0000 UTC
Received: from smtp.github.com (out-3.smtp.github.com [192.30.252.194]) by ismtpd0009p1iad1.sendgrid.net (SG) with ESMTP id 1OGvBI8pTTSqdffdiKkt4Q for <quic-issues@ietf.org>; Mon, 09 Apr 2018 11:53:43.489 +0000 (UTC)
Date: Mon, 09 Apr 2018 11:53:43 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1102ea36a4dde9fffc874c23c64d8b08324b656592cf0000000116e3164792a169ce115ea54e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1068/c379725981@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1068@github.com>
References: <quicwg/base-drafts/pull/1068@github.com>
Subject: Re: [quicwg/base-drafts] Extension frames (#1068)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5acb544761a53_11562b1f7220cecc3829b3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1MLZj2TSugpjL7Tk8aPRr6Fjs+x7zPRM2Rpm gE343n+5kK5fF/d2REe3nzOacYsUj5MnvWt+BgSPgkBdpqTuymzK8Fvw7qi3rB8Pna4sboWqx6UirT 2qgn+gaU2pe2KRvUoC3avAFa1sntkaB4F34uBj3TJUghZdKmtCn/yJ/2Gw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/YgifXidWMdYcHESQCktqQ4geLc4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Apr 2018 11:54:52 -0000

On Sun, Apr 8, 2018 at 9:34 PM, Martin Thomson <notifications@github.com>
wrote:

> It would be technically possible to use transport parameters like TLS
> extensions, which can (and do) change the protocol from the handshake
> onwards.
>
> The coordination disaster arises from the fact that we don't have any way
> to manage collisions between different extensions that add the use of new
> frames.
>

I don't see why this is a problem, except for collisions of the frame type
IDs. And that can be solved by making that space very large. What am I
missing?


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/1068#issuecomment-379725981

v2.30.2 | Report a Bug | By Email | System Status