Re: [quicwg/base-drafts] Define a safe algorithm for changing CID in response to a change in CID (#1795)

Martin Thomson <> Tue, 25 September 2018 17:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D21F0126F72 for <>; Tue, 25 Sep 2018 10:16:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.455
X-Spam-Status: No, score=-8.455 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 MWALEHbppXRi for <>; Tue, 25 Sep 2018 10:16:58 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 65236127133 for <>; Tue, 25 Sep 2018 10:16:57 -0700 (PDT)
Date: Tue, 25 Sep 2018 10:16:56 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1537895816; bh=Ctkwa1J2cgO+m7DvS524jBhrDEjzMnJAlmgfktY99Qo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JQajkMMde9JvlXJBU5Gt+ecyFGD95fWsIcrPvwFlbsVZCxe2ccAVPG3n7s1pYjsZp bn6WDzIi/a6ZhvcyUjdlrYgj4zBSPt4nFfHPTkSBbxkp0GgIq7Rw2HlomSaUmcLY1R NRCh/kQg5qvjMTVZvDm936Drs49LdctVPgWq9t94=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/1795/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Define a safe algorithm for changing CID in response to a change in CID (#1795)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5baa6d886dcdf_76253fb97f2d45c417613f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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, 25 Sep 2018 17:17:00 -0000

@kazuho, you need a small tweak there to deal with the possibility that a peer changes >1 times before you send anything yourself.  But that seems workable.

@mikkelfj the nice thing there is that bad behaviour leads to connections closing, which seems like a good outcome.  When the only thing at stake is the continued existence of the connection, there is no need for further defenses.

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