[quicwg/base-drafts] 449d63: Allow stream-related frames in 0-RTT
Martin Thomson <martin.thomson@gmail.com> Mon, 21 January 2019 05:07 UTC
Return-Path: <bounce+565321.40f-quic-issues=ietf.org@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 F3A65130DE9 for <quic-issues@ietfa.amsl.com>; Sun, 20 Jan 2019 21:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level:
X-Spam-Status: No, score=-0.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 qT1EMhgh45Xv for <quic-issues@ietfa.amsl.com>; Sun, 20 Jan 2019 21:07:21 -0800 (PST)
Received: from m71-131.mailgun.net (m71-131.mailgun.net [166.78.71.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E48EA12D4F2 for <quic-issues@ietf.org>; Sun, 20 Jan 2019 21:07:20 -0800 (PST)
DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1548047240; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=Sp8NHYxtaBbuEs2hzC22xFLyzxjqqOUNMfewvKT9pd4=; b=PzyFF0NzSA4M1zz/oJRT11IRhhRoedzBfLeCbBJkgdUNaLRzTA5X+Bn8igADMpIK0Tkxg27v v6PgZ5UiTdMWJz/7Hzuqm/nFuI3b4Ed4FgDMtP5XZV211Bio+2RVlpNFnduZ6dDs0puMSIy8 KETpQ3IQz09Ae7y4w3pcKKQlmI0=
X-Mailgun-Sending-Ip: 166.78.71.131
X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ==
Sender: martin.thomson=gmail.com@github.com
Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5c455387.7fd5a16dae40-smtp-out-n02; Mon, 21 Jan 2019 05:07:19 -0000 (UTC)
Date: Sun, 20 Jan 2019 21:07:19 -0800
From: Martin Thomson <martin.thomson@gmail.com>
Reply-To: Martin Thomson <martin.thomson@gmail.com>
To: quic-issues@ietf.org
Message-ID: <5c455387af18b_263d2aab1ce0e588230e4@hookshot-fe-d252ca1.cp1-iad.github.net.mail>
Subject: [quicwg/base-drafts] 449d63: Allow stream-related frames in 0-RTT
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="--==_mimepart_5c455387aedd9_263d2aab1ce0e588229e4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/WZbOrexcDV318VO3Wb6KVIDYrQQ>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Mon, 21 Jan 2019 05:07:23 -0000
Branch: refs/heads/0rtt-reset Home: https://github.com/quicwg/base-drafts Commit: 449d636415a868bd503ac6334257dcb1f9bb93af https://github.com/quicwg/base-drafts/commit/449d636415a868bd503ac6334257dcb1f9bb93af Author: Martin Thomson <martin.thomson@gmail.com> Date: 2019-01-21 (Mon, 21 Jan 2019) Changed paths: M draft-ietf-quic-tls.md Log Message: ----------- Allow stream-related frames in 0-RTT In #2344, @kazuho suggests that we could allow RESET_STREAM in 0-RTT. That seems slightly wrong, because why would someone send something then give up without receiving anything in return, but that is actually possible in the presence of packet loss. And changing your mind is perfectly acceptable. But RESET_STREAM doesn't really cover it. Streams can get blocked, requests can go out with additional flow control credits, and maybe even STOP_SENDING makes sense. So this changes it so that any stream-related frame (those that exist to convey application state or manage it), can be sent in 0-RTT. That seems more principled than just adding RESET_STREAM. Closes #2344. **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019.
- [quicwg/base-drafts] 449d63: Allow stream-related… Martin Thomson