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

Martin Thomson <notifications@github.com> Mon, 09 April 2018 04:34 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 85A34126C2F for <quic-issues@ietfa.amsl.com>; Sun, 8 Apr 2018 21:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.392
X-Spam-Level:
X-Spam-Status: No, score=-0.392 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_24=1.618, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 EP_tKOD7H-nI for <quic-issues@ietfa.amsl.com>; Sun, 8 Apr 2018 21:34:32 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 759701252BA for <quic-issues@ietf.org>; Sun, 8 Apr 2018 21:34:32 -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=UJNR+DNxY0+luSosXC4DdDBr8l4=; b=JbETMhl4rosVZw+q /LgYoKhDyQ7jss48bPo8P4WQpjteNge9PH5bRVg80aAdhkpYrKd5NurEh7r5sNht Dn0lQSVNU8DZxLZdlJTNwjb+TBWnek0AY9odOqX10aZnJQl2vgDDC1j25FFCxMYB 5WRTPl5m1wNa4f4eEEHcP2YqPsk=
Received: by filter1237p1mdw1.sendgrid.net with SMTP id filter1237p1mdw1-27677-5ACAED56-13 2018-04-09 04:34:30.917461667 +0000 UTC
Received: from smtp.github.com (out-1.smtp.github.com [192.30.252.192]) by ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id V_JL-opIRY-HevUYRZ89fg for <quic-issues@ietf.org>; Mon, 09 Apr 2018 04:34:30.831 +0000 (UTC)
Date: Mon, 09 Apr 2018 04:34:31 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab40574de979d38ffda3f188d3020704a50048838092cf0000000116e2af5692a169ce115ea54e@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/c379628361@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_5acaed56b1a8a_48882b031bb06ec490773"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1/Wjw5cDu12HZ0mG3UG8gvQOM0Vhw5c+FSYJ CGDv6t1UsPCJJVQPnAiXnLUlQWrnYgULSlUI+CkJNytxZGcDbJ0QHbD3do6lrei6D/ivcXYnoNYInA MxkalLDdB7A4uS3daApdZ9Nmdx7avtW4y+t3vhCaVoeaAruPiQdyCUR7zEU0n4QHOqIflVBqJO6+Q2 M=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ZElzQ891K-2LWmrx_7mxlZLpTpo>
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 04:34:35 -0000

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.

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