Re: [quicwg/base-drafts] CID change still required in response to migration? (#2778)

Tatsuhiro Tsujikawa <> Wed, 03 July 2019 08:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BB2EC12069D for <>; Wed, 3 Jul 2019 01:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id S-ZcQ_gf-DvU for <>; Wed, 3 Jul 2019 01:09:24 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9B9FF120682 for <>; Wed, 3 Jul 2019 01:09:24 -0700 (PDT)
Date: Wed, 03 Jul 2019 01:09:23 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1562141363; bh=k3UjtssjL6JqaUEUtBQG6uoYKrmYzJuMdjQW111fbMk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GnCu3l//IrAvKlTjexp/zEtHgON4kBOXXFdWV6ZYRsqgHybRQhOdsoswU+0Oi9g9M DUxXHwNz3IWKeYctTV+Th9brtKvXE8WrTKzlVKLtAY0tK2Y/vxgUQ2zkkGOBMQ162j lpeHWCBptTtcT0JDmJ4gQu55fjuxKOkaO9cPwuaY=
From: Tatsuhiro Tsujikawa <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2778/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] CID change still required in response to migration? (#2778)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d1c62b3326ea_4a603f9c146cd9601853c1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: tatsuhiro-t
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 03 Jul 2019 08:09:27 -0000

Client don't change CID in indirect migration because it does not aware of it.
Regardless of direct or indirect migration, server knows the packet is coming from new path (new remote address and/or port). 
So the question is server MAY/SHOULD/MUST change CID when sending a packet to new path.

Current draft says that it is MUST to change CID on direct migration:

> An endpoint MUST use a new connection ID if it initiates connection migration.

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