[quicwg/base-drafts] Don't change CID on peer CID change (#2145)

ekr <notifications@github.com> Thu, 13 December 2018 18:57 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 234ED130E12 for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 10:57:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.056
X-Spam-Status: No, score=-8.056 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id DyPjlvwILF8A for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 10:57:03 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D81BC130934 for <quic-issues@ietf.org>; Thu, 13 Dec 2018 10:57:02 -0800 (PST)
Date: Thu, 13 Dec 2018 10:57:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544727420; bh=w+ayZzlfgSjj080wecX/MIS5vk5V70W+/LUSUWFPNG8=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=E+Go5r9YpMHrlpg4t1ILH8F9T1EZQ8gLUSWSK3we5CIsOV7vsupmwtIostwY8zsDz M7e9wgONNLda7hsIgsYT24LPAjS2mmXvffHb6FIZy+v41ZvmLtwQCf2s9LIgrfvfNb +KjmWV55AiECEvKPlpmFuhylYQkxKUXBh8lIr3YM=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4a01d20ee3804b8ad051ab41a24195789e465d1b92cf00000001182a6d7c92a169ce174b5875@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2145@github.com>
Subject: [quicwg/base-drafts] Don't change CID on peer CID change (#2145)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12ab7cc77d2_76113f819b4d45c079255"; 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/S5TxLY6YWlKjcSgMG3rwuYmHJJU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Dec 2018 18:57:06 -0000

```Endpoints that use connection IDs with length greater than zero could have their
activity correlated if their peers keep using the same destination connection ID
after migration. Endpoints that receive packets with a previously unused
Destination Connection ID SHOULD change to sending packets with a connection ID
that has not been used on any other network path.  The goal here is to ensure
that packets sent on different paths cannot be correlated. To fulfill this
privacy requirement, endpoints that initiate migration and use connection IDs
with length greater than zero SHOULD provide their peers with new connection IDs
before migration.


: If both endpoints change connection ID in response to seeing a change in
  connection ID from their peer, then this can trigger an infinite sequence of

I don't remember this being what we agreed, and it's not necessary. You only need to change when you see a new path, not after a new CID. That's how we got rid of counting to infinity.

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