IETF Logo Mail Archive

Re: [quicwg/base-drafts] New connection IDs are mandatory for intentional migration (#2414)

MikkelFJ <notifications@github.com> Tue, 12 February 2019 06:47 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 5FE3B129A87 for <quic-issues@ietfa.amsl.com>; Mon, 11 Feb 2019 22:47:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-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, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PeMhhSK74cRN for <quic-issues@ietfa.amsl.com>; Mon, 11 Feb 2019 22:47:00 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD1BA1274D0 for <quic-issues@ietf.org>; Mon, 11 Feb 2019 22:46:59 -0800 (PST)
Date: Mon, 11 Feb 2019 22:46:58 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549954018; bh=eqfVgmwarHUvsT834QChk2kdUKOChQyCVsCWWmzZ4Pg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k6QyFs8ziQ2LACQc15cSmML9DaMY7bKp4Y45fK5ufZxWWdNqD5MEvfa3Hf7Ct6PAg v8jO8p+o7KUfhS4rKV/AVlvZMc/7arezBEMWLpj0RrqtxS+Dv2xVU4torrSB172M6z DQ5p8N0sCJEsUNWZ82maW0bUCOHCQrwXdnBFgKbY=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5372282acd52a20b754a330789b2bcf33bee698192cf00000001187a2de292a169ce183ba47d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2414/review/202505210@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2414@github.com>
References: <quicwg/base-drafts/pull/2414@github.com>
Subject: Re: [quicwg/base-drafts] New connection IDs are mandatory for intentional migration (#2414)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c626be23344b_30ed3ff233ed45bc584586"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/vUDEgLDGAjitH0jRwez1maelPEs>
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: Tue, 12 Feb 2019 06:47:01 -0000

mikkelfj commented on this pull request.



> @@ -2091,7 +2091,8 @@ different local addresses, as discussed in {{connection-id}}.  For this to be
 effective endpoints need to ensure that connections IDs they provide cannot be
 linked by any other entity.
 
-Endpoints MAY move to a new connection ID at any time.
+At any time, endpoints MAY change the Destination Connection ID they send to a
+value that has not been used on another path.

If there is point to changing CID's on same path, then reordering can send packets with the old CID. I'm not sure there is, but it might have relevance to keep up with changes to router state. But I suppose a router will need to be able to track a CID forever if it keeps seeing it periodically.

-- 
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/2414#discussion_r255820990

v2.23.0 | Report a Bug | By Email