IETF Logo Mail Archive

Re: [quicwg/base-drafts] Stream0 dt output ready (#1377)

ekr <notifications@github.com> Wed, 06 June 2018 16:15 UTC

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 3E5D9130F78 for <quic-issues@ietfa.amsl.com>; Wed, 6 Jun 2018 09:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-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 0gQ_7KrNj-6B for <quic-issues@ietfa.amsl.com>; Wed, 6 Jun 2018 09:15:19 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B1AA130F72 for <quic-issues@ietf.org>; Wed, 6 Jun 2018 09:15:19 -0700 (PDT)
Date: Wed, 06 Jun 2018 09:15:18 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528301718; bh=9ZZLXqJ/4xN14ZhLYipUsrKnns2qWnhJghflSvJOLzI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=auLjztqG9BM/prr3CwiKrRkA2rPnO/kNBS4o2hwsljPiOhp6GCW0s1h7ZA+IhELpE wvAEiwzh63d8D0cmqGl4JXUXyhaMq3IFtxjglKwAbyx4+smVBwb/Pz/jT03Ov/NKAj ShNdUVo5WuEO2qzQVSYXMwST9qNZ8GrCLjvuv7Is=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab398809758ce4ec4233fe593bf0d0b580e179f53892cf00000001172fca9692a169ce1366fdac@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1377/review/126449987@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1377@github.com>
References: <quicwg/base-drafts/pull/1377@github.com>
Subject: Re: [quicwg/base-drafts] Stream0 dt output ready (#1377)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b18089655467_e653ffcfed8af78122772"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/1ZoLqLeVk8QrFXha6h0IgRwpfiw>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 06 Jun 2018 16:15:23 -0000

ekr commented on this pull request.



> +In general, the rules for which data can appear in packets of which
+encryption level are the same in QUIC as in TLS over TCP:
+
+- CRYPTO_HS frames MAY appear in packets of any encryption level.
+- CONNECTION_CLOSE and CRYPTO_CLOSE MAY appear in packets of any
+  encryption level other than 0-RTT.
+- PADDING and PING frames MAY appear in packets of any encryption level.
+- ACK frames MAY appear in packets of any encryption level, but
+  MUST only acknowledge packets which appeared in that encryption
+  level.
+- STREAM frames MUST ONLY appear in the 0-RTT and 1-RTT levels.
+- All other frame types MUST only appear at the 1-RTT levels.
+
+Because packets may be reordered on the wire, QUIC uses the packet
+type to indicate which level a given packet was encrypted
+under [TODO: Table needed here?]. When multiple packets of

Done.

-- 
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/1377#discussion_r193470927

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