Re: [quicwg/base-drafts] Description of the use of Preferred Address is unclear (#3353)

Eric Kinnear <> Sun, 19 January 2020 18:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C1CE512002F for <>; Sun, 19 Jan 2020 10:30:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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_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 g9rtNiDyZbv7 for <>; Sun, 19 Jan 2020 10:29:57 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C291D12002E for <>; Sun, 19 Jan 2020 10:29:57 -0800 (PST)
Date: Sun, 19 Jan 2020 10:29:56 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1579458596; bh=8GPOiQfdHjAPCDLlH7LL4j1BGBAVrVze6NoXmhfDDoE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DSEJg06o+oKw4ThUZJI2vzl9r3iW3e0pzIU4uJW6nrNtFJRtZHFHX+m7tTiIY3UnS emM34WaX+9JypGYlHCMNmxCzAoQp0wW8wSeILMxWk3Q3gYoNejv9QQlTI7iEwtR4aW HC2kvnDFkiE7PCJsLB9EqvcZ01IP9WjDaGrPKgH0=
From: Eric Kinnear <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3353/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Description of the use of Preferred Address is unclear (#3353)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e24a0249bc5e_74a73f7f3d0cd96459729b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: erickinnear
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: Sun, 19 Jan 2020 18:30:01 -0000

> I think the piece we're missing is that when a client declares a migration unsuccessful, it MUST/SHOULD retire the CID it used to attempt the migration. That gives the server a clear signal, succeed or fail; it can then proceed to issue CIDs for the surviving server address.

I think this is only particularly relevant to SPA, since that's the only time that a server is expecting a migration. 

> such change would require every client to recognize TP.preferred_address

Definitely worth being clear about what to do if you also disable migration, but implementations that disable migration still need 99% of the rest of the machinery for other purposes, requiring them to immediately send retire for the TP.preferred_address seems _okay_, if slightly less convoluted than having some "ignore this if that" statement around the whole thing.

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