Re: [quicwg/base-drafts] Preferred Address needs clarifications (#3432)

notonymous <> Wed, 12 February 2020 21:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7CC6A12004F for <>; Wed, 12 Feb 2020 13:44:51 -0800 (PST)
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 NEUHUg8g88tU for <>; Wed, 12 Feb 2020 13:44:49 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E453F12009C for <>; Wed, 12 Feb 2020 13:44:48 -0800 (PST)
Date: Wed, 12 Feb 2020 13:44:48 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1581543888; bh=yCZlhyEE/lub4RatHQpnEARV2mO3v9oQa8aHqeu8m+c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cCZNsM+BVMmYUovjdAx9IcjOWdYSd/m6F8wo5AlCFVtAtNlXB1saSdR42BK9i45ZT WKcfrk0g0qocjjTO7sqr/N3WNev2JFsh+1jEKZQGpHEB9GGqxZliP8PfZDdXgv21QI cxqaiRLC4/c/6nv9Juebj5AYOeyPZCY7cGBUmd7s=
From: notonymous <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3432/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Preferred Address needs clarifications (#3432)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e4471d0f524_14b33f83966cd96024273e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: notonymous
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, 12 Feb 2020 21:44:51 -0000

> If the server isn't willing at all to handle connections on its published IP address, then (naively) it shouldn't accept connections on that IP address and should publish the other one instead. 

I thought the use case in section 9.6 was pretty clear -- "This is particularly useful when clients initially connect to an address shared by multiple servers but [the server] would prefer to use a unicast address to ensure connection stability".

Migrating to a unicast address avoids having to perform connection-based routing through a load balancer.

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