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

Martin Thomson <> Sun, 02 February 2020 16:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D9B15120127 for <>; Sun, 2 Feb 2020 08:53:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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_32=0.001, 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 ewaV5Ix21P8G for <>; Sun, 2 Feb 2020 08:53:32 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C725C12008D for <>; Sun, 2 Feb 2020 08:53:32 -0800 (PST)
Date: Sun, 02 Feb 2020 08:53:31 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1580662411; bh=plAatX+/hyDk/fNxUkCL2cUE5uJyKzMIjgInupO2Ac0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=klHMZ1BZH1jPZtNpZwzoMAzT0UDk7yy9zxfG1/Bq/+um1U1SUVYgJgGGg+ke6OTNE GbHQJohEIbU38DGgRBKCZNi2msE81PmTjKgkSCxdwefEV+ZosrnPsJ8B4wY9VuHOlz 1hVeKIIU/PM8QKZJHygz8B411lxRcogQRcARkwY4=
From: Martin Thomson <>
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_5e36fe8bc3f54_51d73f8d380cd9605720ef"; 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: Sun, 02 Feb 2020 16:53:35 -0000

@erickinnear made me realize the nature of the hazard here.

It seems fairly natural for an server to bind connection IDs to the current socket address.  That is part of why we have new connection IDs attached to the preferred address and the forced retirement.  After all, if the server uses a different target address, the hash at a load balancer could change and cause packets to be badly routed.  Not including the target address in the hash would work, but it would force connection IDs to be bigger.

But this all assumes that you never expect the server to migrate.  If the server ever wanted to migrate, then the client is stuck with a bunch of unusable connection IDs for its own migrations.

We decided that only clients can initiate migration in this version, which might mean that we don't need to worry about this case.  We decided not to allow server migration primarily to avoid having to deal with the complex problems that ICE handles.  But it was only the lack of mechanisms, not a structural constraint.  Now it seems like we have a structural constraint that would prevent server migration.

At a minimum, it seems like we should probably acknowledge this constraint somehow.

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