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 44294129A87
 for <quic-issues@ietfa.amsl.com>; Sat, 12 Jan 2019 02:42:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.149
X-Spam-Level: 
X-Spam-Status: No, score=-11.149 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404,
 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 bVSc3icSN2gH for <quic-issues@ietfa.amsl.com>;
 Sat, 12 Jan 2019 02:42:55 -0800 (PST)
Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 686CD12785F
 for <quic-issues@ietf.org>; Sat, 12 Jan 2019 02:42:55 -0800 (PST)
Date: Sat, 12 Jan 2019 02:42:54 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1547289774;
 bh=5PSENidlzHnrqidGW7ml8et/YMx8ilGINHsERe0zcuY=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=lu04psvSD+ZPfnsbF2PleE9a47RQRijgVmyfCjCuK4/K+8aYUmeN8ySbLojszVrNG
 7+/gi91Nw833jBecL1SGgZS+7fAODBozF/o9BTL2hAwuxTbvF6+9sjeq+GN5xZhfGj
 0GSuNxIXi4mxQjURNa4Er8QDhdgiv/BTnOCzPb8s=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abb27a6e9dfb8b64059fe5043442bb68d7ed246d1f92cf00000001185186ae92a169ce17c1011d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2331/453737469@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2331@github.com>
References: <quicwg/base-drafts/issues/2331@github.com>
Subject: Re: [quicwg/base-drafts] What should the receiver do when the peer
 closes a unidirectional stream before providing the stream type? (#2331)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c39c4ae81f46_719f3fbc654d45c013712d0";
 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/fOFmtUyVP3lsIIJsljyCboF2WKo>
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: Sat, 12 Jan 2019 10:42:57 -0000


----==_mimepart_5c39c4ae81f46_719f3fbc654d45c013712d0
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Nice spot @kazuho, I prefer your second option.

I do wonder how likely this is to happen in practice. An endpoint opens the stream with a STREAM frame, and it would probably be wise for them to include the type byte in that initial frame.

If I understand what Mikkel said, the endpoint sends and empty stream frame and then closes the stream. What is advantage in that style of opening?

-- 
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/2331#issuecomment-453737469
----==_mimepart_5c39c4ae81f46_719f3fbc654d45c013712d0
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Nice spot <a class=3D"user-mention" data-hovercard-type=3D"user" data-=
hovercard-url=3D"/hovercards?user_id=3D41567" data-octo-click=3D"hovercar=
d-link-click" data-octo-dimensions=3D"link_type:self" href=3D"https://git=
hub.com/kazuho">@kazuho</a>, I prefer your second option.</p>
<p>I do wonder how likely this is to happen in practice. An endpoint open=
s the stream with a STREAM frame, and it would probably be wise for them =
to include the type byte in that initial frame.</p>
<p>If I understand what Mikkel said, the endpoint sends and empty stream =
frame and then closes the stream. What is advantage in that style of open=
ing?</p>

<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/2331#issuecomment-453737469">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkqyyc=
JlaE9rDVynFvXJnOKXwy9_sRks5vCbwugaJpZM4Z8gYm">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkqwRJobyAZkNXsHvQL28To8MF=
A4Krks5vCbwugaJpZM4Z8gYm.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 #2331: Nice spot @kazuho, I prefer your second option.\r\n\r\n=
I do wonder how likely this is to happen in practice. An endpoint opens t=
he stream with a STREAM frame, and it would probably be wise for them to =
include the type byte in that initial frame.\r\n\r\nIf I understand what =
Mikkel said, the endpoint sends and empty stream frame and then closes th=
e stream. What is advantage in that style of opening?"}],"action":{"name"=
:"View Issue","url":"https://github.com/quicwg/base-drafts/issues/2331#is=
suecomment-453737469"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2331#issuecomment=
-453737469",
"url": "https://github.com/quicwg/base-drafts/issues/2331#issuecomment-45=
3737469",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c39c4ae81f46_719f3fbc654d45c013712d0--

