[quicwg/base-drafts] Does the connection id need to be in a consistent location? (#293)

ianswett <notifications@github.com> Sun, 12 February 2017 17:19 UTC

Date: Sun, 12 Feb 2017 09:19:51 -0800
From: ianswett <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/293@github.com>
Subject: [quicwg/base-drafts] Does the connection id need to be in a consistent location? (#293)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58a09937d6c12_2e4e3f9e435cf14037194"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/GoPzdVU7OFih0X96rcbSImRCE_M>
Cc: Subscribed <subscribed@noreply.github.com>
Reply-To: quic@ietf.org

@martinthomson created a header proposal that provides a fixed 8 byte connection id in a fixed location.  

We need to decide if this is a requirement or a nice to have.

I haven't found any environments it needed to be in a fixed location for all packets, as long as it's easy to determine where it will be from the first byte of the packet.

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

[quicwg/base-drafts] Does the connection id need … ianswett
Re: [quicwg/base-drafts] Does the connection id n… Martin Thomson
Re: [quicwg/base-drafts] Does the connection id n… ianswett
Re: [quicwg/base-drafts] Does the connection id n… Mike Bishop
Re: [quicwg/base-drafts] Does the connection id n… Mike Bishop