Re: [quicwg/base-drafts] Allow servers to send a preferred address of each address family (#2296)

ianswett <notifications@github.com> Sun, 06 January 2019 21:15 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C30F8130E1F for <quic-issues@ietfa.amsl.com>; Sun, 6 Jan 2019 13:15:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.064
X-Spam-Level:
X-Spam-Status: No, score=-8.064 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RnISl2H88os0 for <quic-issues@ietfa.amsl.com>; Sun, 6 Jan 2019 13:15:31 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0263D130E43 for <quic-issues@ietf.org>; Sun, 6 Jan 2019 13:15:31 -0800 (PST)
Date: Sun, 06 Jan 2019 13:15:29 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546809329; bh=Z9Wp5z60V6QODUwEtgd6FJPo5Lgr6fiHy465kfOr+3c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l/ossVAF5DrPG4iCjimWSAyfw91cHujjn/1OO3z1aZMUBu4YIbqZr13EdXgYK+bzx 2yaQTWbS5D51wvhKQmzV8AT1Tlfwx9RQAzBztLQtTGdW0k/ithSNQcBckOj4NbJcM7 78SBksnROxcFbgWJluEBVniq+QfYpDUmE9FGKj6Y=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab64c84cdfd91e287bdff5bdd7b8f4e09c66e5675892cf00000001184a31f192a169ce179bec73@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2296/review/189644456@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2296@github.com>
References: <quicwg/base-drafts/pull/2296@github.com>
Subject: Re: [quicwg/base-drafts] Allow servers to send a preferred address of each address family (#2296)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c326ff1c0c3f_5c9a3ff7fd8d45c0768925"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/WbUKOCa8njs-Ft3XGJWUcVZxnLA>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2019 21:15:33 -0000

ianswett commented on this pull request.

I like this idea, one suggestion.

> @@ -2116,6 +2116,9 @@ packets.
 A server conveys a preferred address by including the preferred_address
 transport parameter in the TLS handshake.
 
+Servers MAY communicate a preferred address of each address family (IPv4 and

If you're speaking of "preferred" address, this is consistent with the rest of the text.  If you want to change the name, I'd suggest opening a separate issue.

I'm happy with preferred, since if it's just alternate, why would the client change?  Alternate implies no preference, when in fact the server does prefer the other address.

>  
 ~~~
    struct {
-     enum { IPv4(4), IPv6(6), (15) } ipVersion;
-     opaque ipAddress<4..2^8-1>;
+     opaque ipv4Address<0..2^8-1>;

Aren't these two fields now fixed sizes?  If so, any reason not to specify those?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2296#pullrequestreview-189644456