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

Tatsuhiro Tsujikawa <> Tue, 11 June 2019 08:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2063D1201E5 for <>; Tue, 11 Jun 2019 01:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.391
X-Spam-Status: No, score=-6.391 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 ptYLZCl9eDeU for <>; Tue, 11 Jun 2019 01:51:40 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E70A012013B for <>; Tue, 11 Jun 2019 01:51:39 -0700 (PDT)
Date: Tue, 11 Jun 2019 01:51:38 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1560243098; bh=cuBv1U/g4vd56ivak4+JSPz+LDRvQSsD9nuPmZAF1wY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=V6PeBH7M7AkBakNGSGthMlZSTi38wQcdhVC3cUibM6MXHI4UJClrevy3Rd+hg/Isj p78hlJFst1QlvUcjuzRi2X5HECVKuYG0lroHvAcC8pHUoLa8Yrqitx1q++ZuFK3FMG DDga6ETtgd+8rqRCUsqxwdXAekZSz7yE1Eb39A9s=
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_5cff6b9ac5e96_73063fd054ecd95c394558"; 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: Tue, 11 Jun 2019 08:51:49 -0000

Background context for this issue:
In NAT rebinding test, quic tracker does not send any NEW_CONNECTION_ID.
My server implementation refuses to use new path because there is no new CID left and cannot verify new path assuming that new CID is required for new path.
But they say that using NEW_CONNECTION_ID for new path is not written in draft as requirement, so server should follow the new path.
If using new CID for new path is a requirement, quic tracker should send NEW_CONNECTION_ID.
If it is just a recommendation, server probably should use new path with same CID.

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