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 569C8120838
 for <quic-issues@ietfa.amsl.com>; Thu,  6 Feb 2020 01:07:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.754
X-Spam-Level: 
X-Spam-Status: No, score=-3.754 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546,
 HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3,
 SPF_HELO_NONE=0.001, 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 zrAEaGH93EVt for <quic-issues@ietfa.amsl.com>;
 Thu,  6 Feb 2020 01:07:24 -0800 (PST)
Received: from out-28.smtp.github.com (out-28.smtp.github.com [192.30.252.211])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 16E5A120255
 for <quic-issues@ietf.org>; Thu,  6 Feb 2020 01:07:24 -0800 (PST)
Date: Thu, 06 Feb 2020 01:07:23 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1580980043;
 bh=LX1y/K+OftO5Vn1FKFZcPYh93YVvdVpL5wqgysnwqNM=;
 h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post:
 List-Unsubscribe:From;
 b=lWYD6AYKM4C/NRm5mcNqxYaOXmk2Hpv/cvXN9LPY5gTCAEVJThEjf0P84QnWHs0Al
 sCOKV8ut7iq2dLZkHVCLJ8fsbf4572rq7bv9u+6UQN1BIiB3lcbAR/qxbq5WOHGA5b
 MdrgNX8Rx0P17zf/y1WDbFIn8JLpBAhwQn/J9Kc4=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJKZVTLNL3YAYVG54S5N4JEE4XEVBNHHCC3RXUI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3430@github.com>
Subject: [quicwg/base-drafts] It is unclear if some frames are forbidden in
 0-RTT (#3430)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5e3bd74b502f0_50363fabb00cd960173a4";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/liDAJtrQSer3-qzR1jyqMacyqvQ>
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: Thu, 06 Feb 2020 09:07:25 -0000


----==_mimepart_5e3bd74b502f0_50363fabb00cd960173a4
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

In TLS draft, we state that _all other frame types MUST only be sent in the 0-RTT and 1-RTT levels_, then state that it is impossible to send some of those frames in 0-RTT (HANDSHAKE_DONE, NEW_TOKEN, PATH_RESPONSE, RETIRE_CONNECTION_ID).

As it seems that we think use of these frames in 0-RTT to be forbidden, I think we should be clear about that.

-- 
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/3430
----==_mimepart_5e3bd74b502f0_50363fabb00cd960173a4
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>In TLS draft, we state that <em>all other frame types MUST only be sent in the 0-RTT and 1-RTT levels</em>, then state that it is impossible to send some of those frames in 0-RTT (HANDSHAKE_DONE, NEW_TOKEN, PATH_RESPONSE, RETIRE_CONNECTION_ID).</p>
<p>As it seems that we think use of these frames in 0-RTT to be forbidden, I think we should be clear about that.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/3430?email_source=notifications&amp;email_token=AFTOJK27H6EZS3IKJRO2CRLRBPHMXA5CNFSM4KQZCPY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ILOG6RA">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK2ZYTZFBOLQRXS5YXTRBPHMXANCNFSM4KQZCPYQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK754AD3WVQDNAGKYPDRBPHMXA5CNFSM4KQZCPY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ILOG6RA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/3430?email_source=notifications\u0026email_token=AFTOJK27H6EZS3IKJRO2CRLRBPHMXA5CNFSM4KQZCPY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ILOG6RA",
"url": "https://github.com/quicwg/base-drafts/issues/3430?email_source=notifications\u0026email_token=AFTOJK27H6EZS3IKJRO2CRLRBPHMXA5CNFSM4KQZCPY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ILOG6RA",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5e3bd74b502f0_50363fabb00cd960173a4--

