IETF Logo Mail Archive

Re: [quicwg/base-drafts] Allow stream-related frames in 0-RTT (#2355)

Kazuho Oku <notifications@github.com> Tue, 22 January 2019 00:43 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 7F2C0130E3F for <quic-issues@ietfa.amsl.com>; Mon, 21 Jan 2019 16:43:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.552
X-Spam-Level:
X-Spam-Status: No, score=-12.552 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_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 8XKzNQaZDSHV for <quic-issues@ietfa.amsl.com>; Mon, 21 Jan 2019 16:43:40 -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 807D8130E2E for <quic-issues@ietf.org>; Mon, 21 Jan 2019 16:43:40 -0800 (PST)
Date: Mon, 21 Jan 2019 16:43:39 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548117819; bh=z3kYpDbqJCRMLzFDZpimmFKcEmqBU4DW4ysCNLVi1YE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bktYvc4RZxMDZ6uEnkpnC38UHO602w2vv/O+GIF9yyzyPPltHI3Sk5YVPha0TLDA7 jkGYIvNjoVt75Yb3iwekjhOQ0Slr8UBAvoCyWSdjvysmt4S71DDrYqwI0vogs6fuyu 8GRNUJ4fZvCuDcbgl8AHIFEca23f89u7WSorHrRI=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1b13116c09d754d73fcfdcfb3a2e5245fb81c9dd92cf00000001185e293b92a169ce17e9c1c4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2355/review/194800021@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2355@github.com>
References: <quicwg/base-drafts/pull/2355@github.com>
Subject: Re: [quicwg/base-drafts] Allow stream-related frames in 0-RTT (#2355)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c46673b50331_7b883fb05d8d45bc839122"; 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/Zwd7fUcCk__qFuvPuXcMGOV2EOQ>
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: Tue, 22 Jan 2019 00:43:42 -0000

kazuho commented on this pull request.

As stated in 
https://github.com/quicwg/base-drafts/issues/2344#issuecomment-456233537, my preference goes to naming the frames that are necessary for 0-RTT to work rather than allowing any frames to be used (with the only exceptions being CRYPTO and ACK).

Besides, now that we have a section for Replay Attacks using 0-RTT, it might make sense to recommend servers _not_ sending MAX_DATA, MAX_STREAM_DATA, MAX_STREAMS frames until the handshake is complete. This works as a replacement of max_early_data_size that we have in TLS 1.3.



-- 
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/2355#pullrequestreview-194800021

v2.23.0 | Report a Bug | By Email