[quicwg/base-drafts] Byte order of IP addresses in PreferredAddress (#2951)

Masakazu Kitajo <notifications@github.com> Fri, 02 August 2019 07:42 UTC

Date: Fri, 02 Aug 2019 00:42:47 -0700
From: Masakazu Kitajo <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4O7S255GBX26FEGJF3KEN7PEVBNHHBYX6XRE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2951@github.com>
Subject: [quicwg/base-drafts] Byte order of IP addresses in PreferredAddress (#2951)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d43e977c502e_54373f85f6ecd964736d2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/jCBP8f7YxoCjnykRU_plVA2yYuo>

Byte order of IP addresses in PreferredAddress is not explicitly stated. In practice, most OSs keep them in network byte order, and the spec says integers are in network byte order, however the fields for ip addresses are defined as opaque data. The byte order should be stated on this spec.

```
    struct {
     opaque ipv4Address[4];
     uint16 ipv4Port;
     opaque ipv6Address[16];
     uint16 ipv6Port;
     opaque connectionId<0..20>;
     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/issues/2951

[quicwg/base-drafts] Byte order of IP addresses i… Masakazu Kitajo
Re: [quicwg/base-drafts] Byte order of IP address… Jana Iyengar