Re: [quicwg/base-drafts] Remove the explicit packet number gap in favor of one computed (#496)

ekr <notifications@github.com> Wed, 03 May 2017 22:28 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 AA0E2129490 for <quic-issues@ietfa.amsl.com>; Wed, 3 May 2017 15:28:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.497
X-Spam-Level:
X-Spam-Status: No, score=-6.497 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.8, 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 A8RxsXu7ABfk for <quic-issues@ietfa.amsl.com>; Wed, 3 May 2017 15:28:08 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8397B129AF4 for <quic-issues@ietf.org>; Wed, 3 May 2017 15:26:23 -0700 (PDT)
Date: Wed, 03 May 2017 15:26:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1493850382; bh=KCJx+3EX8iVvkVzuN2kLGLxQFhUGyNUx+LnnxBiv2Pc=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SziNm9LCHE5EqcQnAGmZOVXv4gcXqprU0IsXUdSoLgd0vLrL29FHKFOrXeuk0B84d YLYlGer3IYkv2GGp2AdVS03Z9g7FEnqG6Bcb/6n4ew1Ufa8ygYOakbL2ArFJpuDmGM rfVvJDci5MLq3AS6SylXGWrYR4NT4LuJJAW4bf0I=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab24bcea125de1d79499e59cc8cf10698acf0236e192cf0000000115221b0e92a169ce0d7957f1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/496/review/36154106@github.com>
In-Reply-To: <quicwg/base-drafts/pull/496@github.com>
References: <quicwg/base-drafts/pull/496@github.com>
Subject: Re: [quicwg/base-drafts] Remove the explicit packet number gap in favor of one computed (#496)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_590a590ed8aa3_6f3d3f9a04573c348949d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/CpdkMdnqvM31gJGmTlVEBWisnRs>
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: Wed, 03 May 2017 22:28:10 -0000

ekr commented on this pull request.



>  between two points of network attachment.
 
-The NEW_CONNECTION_ID message includes a connection ID that the client can use
-for packets on the current connection.  This message also includes packet number
-gap, which is the number of packet numbers that the client skips when using the
-new connection ID.  Without this, the packet number field in the header might be
-used to link activity across networks.  A server MUST provide a 32-bit value for
-the packet number gap field that is indistinguishable from random to a passive
-observer.
+A client which wishes to break linkability upon changing networks MUST
+use the NEW_CONNECTION_ID as well as incrementing the packet sequence

Well I think my claim is that if you want it unlinkable you have to


-- 
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/496#discussion_r114667708