Re: [quicwg/base-drafts] Move stateless reset token to the end (#842)

janaiyengar <notifications@github.com> Tue, 10 October 2017 22:54 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 C40FD1346B4 for <quic-issues@ietfa.amsl.com>; Tue, 10 Oct 2017 15:54:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 P7qubu_DMZ5x for <quic-issues@ietfa.amsl.com>; Tue, 10 Oct 2017 15:54:16 -0700 (PDT)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 9BF721346B9 for <quic-issues@ietf.org>; Tue, 10 Oct 2017 15:53:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=jpTtcR5cxKEIHIq27mj/xox1ej0=; b=rSg10jr8mgmTD4RV Lgk1TT9YnJyM8nC6+GrLCWfvHdyWKoqNJ0UnqPbK9Zllyar4BK7iGfECQQndUkbi scr58kN3+ox62hVtpi6Qg6wJjJpCd6uDm7Sz1EOmnG0nyqALApMQlSE9rSqsnBRf e/tmUsI7BSnEY5QCrQV61l4GMOA=
Received: by filter0114p1iad2.sendgrid.net with SMTP id filter0114p1iad2-27400-59DD4F81-4 2017-10-10 22:53:53.378904307 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0011p1iad2.sendgrid.net (SG) with ESMTP id 1EufUa10SNWzcYjLw0r7Kw for <quic-issues@ietf.org>; Tue, 10 Oct 2017 22:53:53.435 +0000 (UTC)
Date: Tue, 10 Oct 2017 22:53:53 +0000
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abcb5ae80616f95e3f326a3af354b98886fa0d757692cf0000000115f5118192a169ce0fb8c6e7@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/842/review/68450033@github.com>
In-Reply-To: <quicwg/base-drafts/pull/842@github.com>
References: <quicwg/base-drafts/pull/842@github.com>
Subject: Re: [quicwg/base-drafts] Move stateless reset token to the end (#842)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59dd4f8157385_603c3ff807014f3424384"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3FH4QqYJwSE2B6zJUHdTt+zqSh7hvkezu950 XSI7QXo6A/d4gB6DjBzC6+1P5B15Da3RhC46u4Y8wBuKLaiEH6FOHi5tdcd2EgKJp+SYJzOpDtvSv8 Y9eWckqdAIGzNTfaNzplxz1n8ckpXkBdjmYBqeEpJBpkZCWdH1tiinh2H5pIo7e7Kf30LNQVV0dZs5 I=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/8npp2ENAb9QC2gYMbAFAzKcGPG4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 10 Oct 2017 22:54:18 -0000

janaiyengar commented on this pull request.

Couple of comments.

>  A server copies the connection ID field from the packet that triggers the
 stateless reset.  A server omits the connection ID if explicitly configured to
 do so, or if the client packet did not include a connection ID.
 
+The Packet Number field is set to a randomized value.  The server SHOULD send a
+packet with a short header and a type of 0x01.  This produces the shortest
+possible packet number encoding, which minimizes the perceived gap between the
+last packet that the server sent and this packet.  A server MAY use a different
+short header type, indicating a different packet number length, but this allows
+for the message to be identified as a stateless reset more easily using

nit: "this allows for" - I think you mean to say that using a 1-byte packet number makes life easier, but "this" is ambiguous here. Maybe something like: "A server MAY use a different short header type, indicating a different packet number length, but using 0x01 allows for the message to be identified as a stateless reset more easily using heuristics."

> @@ -1595,11 +1600,11 @@ CONNECTION_CLOSE or APPLICATION_CLOSE frame if it has sufficient state to do so.
 #### Detecting a Stateless Reset
 
 A client detects a potential stateless reset when a packet with a short header
-cannot be decrypted.  The client then performs a constant-time comparison of the
-16 octets that follow the Connection ID with the Stateless Reset Token provided
-by the server in its transport parameters.  If this comparison is successful,
-the connection MUST be terminated immediately.  Otherwise, the packet can be
-discarded.
+either cannot be decrypted or is marked as a potential duplicate.  The client
+then performs a constant-time comparison of the last 16 octets of the packet
+with the Stateless Reset Token provided by the server in its transport
+parameters.  If this comparison is successful, the connection MUST be terminated

Perhaps "all connection state MUST be discarded."

-- 
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/842#pullrequestreview-68450033