IETF Logo Mail Archive

Re: [quicwg/base-drafts] RESET_STREAM should be allowed in 0-RTT packets (#2344)

MikkelFJ <notifications@github.com> Fri, 18 January 2019 18:26 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 6FF7A131290 for <quic-issues@ietfa.amsl.com>; Fri, 18 Jan 2019 10:26:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.553
X-Spam-Level:
X-Spam-Status: No, score=-12.553 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_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 CMzGxnaBWG63 for <quic-issues@ietfa.amsl.com>; Fri, 18 Jan 2019 10:26:27 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E56331312C0 for <quic-issues@ietf.org>; Fri, 18 Jan 2019 10:26:26 -0800 (PST)
Date: Fri, 18 Jan 2019 10:26:26 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547835986; bh=Xogztve+Ww68/jc0We+oz3gQHLRjqPEYcSOkBwt8ys4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nAQjguBa/D/riyXue0Qz4a3Q1RVxRSQhB+u/IgkatmWmrvlUkXB75fMZIq2ORSF0k l+yg6xSz8Kan+nmlBMULC7CV9QcLYFxPwpc/Qk4UOw5rlKkH28s8FucPbe9WtZRNtu xVlan6S8hLayYZKhvKLUYKXazgyptIDkcGOl6FD8=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab264a4b7bee49fcf6ee1509061abd4a4e01174e5992cf000000011859dc5292a169ce17e00219@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2344/455642017@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2344@github.com>
References: <quicwg/base-drafts/issues/2344@github.com>
Subject: Re: [quicwg/base-drafts] RESET_STREAM should be allowed in 0-RTT packets (#2344)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c421a5220bfa_59eb3f98226d45bc6618da"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/RWOw2pl7b8SXVaC9UcWbzrpWWAM>
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, 18 Jan 2019 18:26:30 -0000

I have been skimming through the QUIC transport and QUIC TLS draft a few times. It is really difficult to decipher which frames can be sent where. Some packet types mention permitted frames in transport, but does not do that for all packet types. QUIC TLS has a list of frames for different packet types, but it is not clear if that cover all frame types.

QUIC TLS does suggest that CRYPTO frames can be sent in 1-RTT by stating the only 0-RTT cannot contain crypto, but is not clear about how or why that would happen, although I suspect it has to do with client auth - which is explicitly not permitted post handshake without any explanation. It could also be rekeying, but I think that is derived locally from session key.

-- 
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/2344#issuecomment-455642017

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