Re: [quicwg/base-drafts] Full (mostly) editorial pass (#1665)

Mike Bishop <notifications@github.com> Thu, 16 August 2018 18:09 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 CA8D9130E40 for <quic-issues@ietfa.amsl.com>; Thu, 16 Aug 2018 11:09:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 RYMLe1cqz6wg for <quic-issues@ietfa.amsl.com>; Thu, 16 Aug 2018 11:09:54 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 293B2130F17 for <quic-issues@ietf.org>; Thu, 16 Aug 2018 11:09:53 -0700 (PDT)
Date: Thu, 16 Aug 2018 11:09:52 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1534442992; bh=uGqxf/s7cStW/qa7EwqaXIDYsYNLHJOJ5zfnsFE/bHM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SXdEjpJl317it0DOc0RUxpsO9uqEy/R01hZge2bhHOKOer3PLT5e7snnKAGtEkh+u 4gCvYEhVM+epXW1+ylLf1fldqqFEv8oRru5S+Bjbve5JMYW/ItqimNXYhh15kn4eXz MyKcdWwJkZHKcSwVJd/uu/qvqNSwUsv5RNXklvHk=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abab94f9aa5ef212f608595a5e91f404d82c3d68db92cf00000001178d7ff092a169ce14e9e22c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1665/review/146961669@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1665@github.com>
References: <quicwg/base-drafts/pull/1665@github.com>
Subject: Re: [quicwg/base-drafts] Full (mostly) editorial pass (#1665)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b75bdf052a62_776b3fde4d6d45b425685"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/9T4nrQN9G4d-rtsWgPfi03_nOI4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Thu, 16 Aug 2018 18:09:56 -0000

MikeBishop commented on this pull request.



> @@ -2560,11 +2594,16 @@ properly continue the connection.  An endpoint that wishes to communicate a
 fatal connection error MUST use a closing frame if it has sufficient state to do
 so.
 
-To support this process, a token is sent by endpoints.  The token is carried in
-the NEW_CONNECTION_ID frame sent by either peer, and servers can specify the
-stateless_reset_token transport parameter during the handshake (clients cannot
-because their transport parameters don't have confidentiality protection).  This
-value is protected by encryption, so only client and server know this value.
+To support this process, a token is sent by the endpoints that can be recovered
+or regenerated by the endpoint based on the information available in each packet
+even if the connection state was lost. This provides a protect mechanism to
+identify Stateless Reset packets from an attacker.

That works.

-- 
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/1665#discussion_r210691284