Return-Path: <noreply@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 8A92B130EE7
 for <quic-issues@ietfa.amsl.com>; Thu,  3 Jan 2019 18:27:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.064
X-Spam-Level: 
X-Spam-Status: No, score=-8.064 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001,
 HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5,
 SPF_PASS=-0.001] 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 pbON98BgVsV4 for <quic-issues@ietfa.amsl.com>;
 Thu,  3 Jan 2019 18:27:01 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 4AC1A130ED0
 for <quic-issues@ietf.org>; Thu,  3 Jan 2019 18:27:01 -0800 (PST)
Date: Thu, 03 Jan 2019 18:27:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1546568820;
 bh=okaj6rEuUx9mpkcyvoS+OP5hlNbqFQlLRIIhosb4BJs=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=syA4gUsr+G2YKVAqBSAoWrHsjt/f9EpOaECKMvoNdzRWUFmzTGSbisk1pVwLjjrT7
 Ko4WKDy7Qf5NLsrh1LGhk3Qh8QO+89xkOX8/RP9BqJMe92WnyZWFZezIcEkopO0OWr
 iAaiGO3hs27gOO31wUvqnkHbJ1Y+YOXRT0oGOyQo=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab8e303000aca569102b9f59bc5d06c9ba083937d892cf000000011846867492a169ce1797273c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2291/451338208@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2291@github.com>
References: <quicwg/base-drafts/issues/2291@github.com>
Subject: Re: [quicwg/base-drafts] Allow extra data after self-terminating h3
 frames (#2291)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c2ec47451ebc_24c63fbb126d45b898383";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/FFNGH7wmEB1PwzYgX_pF_cLyS9c>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 04 Jan 2019 02:27:03 -0000


----==_mimepart_5c2ec47451ebc_24c63fbb126d45b898383
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Ah ok, understood. I guess the reaction  is that there are so few applicable core H3 frames that are likely to be sent through the course of a typical connection* that the merits of this flexibility might be hard to realise. 

Also, by invoking Postel, I fear the wrath of https://tools.ietf.org/html/draft-iab-protocol-maintenance-01 :)

* of the 7 frames, 4 of them relate to Server push. SETTINGS can't be sent multiple times. PRIORITY, the H3 style might change this up compared to H3, it's also one-way. GOAWAY is one-way too.

-- 
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/issues/2291#issuecomment-451338208
----==_mimepart_5c2ec47451ebc_24c63fbb126d45b898383
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Ah ok, understood. I guess the reaction  is that there are so few appl=
icable core H3 frames that are likely to be sent through the course of a =
typical connection* that the merits of this flexibility might be hard to =
realise.</p>
<p>Also, by invoking Postel, I fear the wrath of <a href=3D"https://tools=
.ietf.org/html/draft-iab-protocol-maintenance-01" rel=3D"nofollow">https:=
//tools.ietf.org/html/draft-iab-protocol-maintenance-01</a> :)</p>
<ul>
<li>of the 7 frames, 4 of them relate to Server push. SETTINGS can't be s=
ent multiple times. PRIORITY, the H3 style might change this up compared =
to H3, it's also one-way. GOAWAY is one-way too.</li>
</ul>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/issues/2291#issuecomment-451338208">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq6ae=
n6oiCA_5rQvkaNjnANACmPZ6ks5u_rv0gaJpZM4ZpBt0">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkqwapyjEqVEG1-n6sIr29IO3l=
XO6oks5u_rv0gaJpZM4ZpBt0.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://github.githubassets.com/images/email/message_cards/header.png","avata=
r_image_url":"https://github.githubassets.com/images/email/message_cards/=
avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/q=
uicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@=
LPardue in #2291: Ah ok, understood. I guess the reaction  is that there =
are so few applicable core H3 frames that are likely to be sent through t=
he course of a typical connection* that the merits of this flexibility mi=
ght be hard to realise. \r\n\r\nAlso, by invoking Postel, I fear the wrat=
h of https://tools.ietf.org/html/draft-iab-protocol-maintenance-01 :)\r\n=
\r\n* of the 7 frames, 4 of them relate to Server push. SETTINGS can't be=
 sent multiple times. PRIORITY, the H3 style might change this up compare=
d to H3, it's also one-way. GOAWAY is one-way too."}],"action":{"name":"V=
iew Issue","url":"https://github.com/quicwg/base-drafts/issues/2291#issue=
comment-451338208"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2291#issuecomment=
-451338208",
"url": "https://github.com/quicwg/base-drafts/issues/2291#issuecomment-45=
1338208",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c2ec47451ebc_24c63fbb126d45b898383--

