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

Mike Bishop <> Fri, 18 January 2019 17:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A0C2913123E for <>; Fri, 18 Jan 2019 09:36:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.935
X-Spam-Status: No, score=-10.935 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id swIi5GcZXHrw for <>; Fri, 18 Jan 2019 09:36:37 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E63F7131236 for <>; Fri, 18 Jan 2019 09:36:36 -0800 (PST)
Date: Fri, 18 Jan 2019 09:36:35 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1547832995; bh=hJBaymeqkdDp2+K+KtsNav57i6eGc58PcoH8EC3xOMU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=skAWmzza7jGJtUt2pnQ+J6abQj/oqL9JLOP5sOtenCexizepTX32bqL5KYvJbgY1k n25sKeP5juBkBfkhlFMKh1RImiZhALr6uBfeILb6dfjaHEenMy2Ko6exC2gS7hIi9k pG07RWmYVnm3rvKWg7+iYEq5zFCOhglzP7em7h+k=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2344/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
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_5c420ea3acdff_b853fc77e6d45b83035ca"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 18 Jan 2019 17:36:39 -0000

I agree with loosening the restrictions.  As with TLS 1.3, it's up to the application layer to restrict what things can't be done in 0-RTT.  Those should generally be things which have effects outside the connection itself, and at the QUIC layer, nothing the client sends does.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: