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

Kazuho Oku <notifications@github.com> Mon, 07 January 2019 00:26 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 AC8D21310C7 for <quic-issues@ietfa.amsl.com>; Sun, 6 Jan 2019 16:26:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.065
X-Spam-Level:
X-Spam-Status: No, score=-8.065 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_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 TcGqJOlZrC5O for <quic-issues@ietfa.amsl.com>; Sun, 6 Jan 2019 16:26:36 -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 18FD5129AB8 for <quic-issues@ietf.org>; Sun, 6 Jan 2019 16:26:36 -0800 (PST)
Date: Sun, 06 Jan 2019 16:26:34 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546820794; bh=0IWo3rqsEyqxKswULWz0M8b7L0R4j8L8LcH47qimy1c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VZPB6+Lj8z36+8nbXMDK6+/I2TooRcwcA0CKQCI7s5XU2jZ4k4fvbwIFR7NJsxKtx S2xzusG2rcvModp01S4mKAaLDkbxPFZ+zofH0emCxl646obthhePc0baJzEpG3Jz7l 57mJaA4cvWuvSFWHcbV1w8Uq37e8ei6gburtF55E=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab797faa995818dbb19264eb1d9ba1e5b65f747a4f92cf00000001184a5eba92a169ce179bec73@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/189652498@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_5c329cbac3e38_476e3f80ab8d45bc379448"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/76eoPC7VLDS6iSzNBpL1bQD9mmQ>
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: Mon, 07 Jan 2019 00:26:38 -0000

kazuho commented on this pull request.

@DavidSchinazi Thank you for working on this.

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

The PR seems to assume that:
* IPv4 and IPv6 are the only two types of underlying protocols that we care, while the current draft provides extensibility (i.e. we can add new types to the ipVersion enumeration).
* All the addresses share the same port number.

Are we fine with that?

If the intent here is to add support for IPv6 address:port without having any impact on other aspects, I believe that the struct should look like:

```
struct {
    enum { IPv4(4), IPv6(6), (15) } ipVersion;
    struct {
        select (ipVersion) {
        case IPv4:
            struct {
                opaque address[4];
                uint16 port;
            };
        case IPv6:
            struct {
                opaque address[16];
                uint16 port;
            };
        }
    } <0..2^8-1>;
} AddressPort;

struct {
    AddressPort address<0..2^8-1>;
    uint16 port;
    opaque connectionId<0..18>;
    opaque statelessResetToken[16];
} PreferredAddress;

-- 
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-189652498