[quicwg/base-drafts] Connection ID should be treated as a 32-bit field and not as a uint (#786)

janaiyengar <notifications@github.com> Thu, 21 September 2017 17:20 UTC

Date: Thu, 21 Sep 2017 10:20:29 -0700
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba8f0c0cfef294feda5da86f492fdb2cada04e9ae92cf0000000115dbb6dd92a169ce0f78bdb5@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/786@github.com>
Subject: [quicwg/base-drafts] Connection ID should be treated as a 32-bit field and not as a uint (#786)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59c3f4dd7325d_4cb33f8b5b008f7c34688"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/uifZ74o0ENsHGmb8DHxXyNHwo0I>

It should be obvious, but we should make it clear since endianness matters, especially when we feed connection ID into the en/decrypters.

Also, version number should be treated as a uint. We should be explicit about this as well.

-- 
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/786

[quicwg/base-drafts] Connection ID should be trea… janaiyengar
Re: [quicwg/base-drafts] Connection ID should be … Ryan Hamilton
Re: [quicwg/base-drafts] Clarify Connection ID an… janaiyengar
Re: [quicwg/base-drafts] Clarify Connection ID an… janaiyengar
Re: [quicwg/base-drafts] Clarify Connection ID an… Subodh Iyengar
Re: [quicwg/base-drafts] Clarify Connection ID an… Martin Thomson