Re: [quicwg/base-drafts] Long and short packet type 00? (#487)

Martin Thomson <notifications@github.com> Thu, 04 May 2017 04:54 UTC

Date: Wed, 03 May 2017 21:54:18 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab9e0e45f46edaac2862e58c05e42eabb7ea3e219992cf00000001152275fa92a169ce0d6a4292@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/487/299096805@github.com>
In-Reply-To: <quicwg/base-drafts/issues/487@github.com>
References: <quicwg/base-drafts/issues/487@github.com>
Subject: Re: [quicwg/base-drafts] Long and short packet type 00? (#487)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_590ab3fad0768_44cc3f8ea88b7c2c3088f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/o-LDEdyeliaZBS-WgQkRG8Mt23Q>

I don't think that we want to reserve these.  Nor do I think that it needs special mention.  We just decided not to use them.

I hear that there are some deployments that route a packet containing a zero octet at the front to other places.  I don't think that we need to endorse that sort of behaviour, but avoiding `00` is cheap.

-- 
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/487#issuecomment-299096805

[quicwg/base-drafts] Long and short packet type 0… Lars Eggert
Re: [quicwg/base-drafts] Long and short packet ty… janaiyengar
Re: [quicwg/base-drafts] Long and short packet ty… Martin Thomson
Re: [quicwg/base-drafts] Long and short packet ty… Lars Eggert
Re: [quicwg/base-drafts] Long and short packet ty… Martin Thomson
Re: [quicwg/base-drafts] Long and short packet ty… janaiyengar
Re: [quicwg/base-drafts] Long and short packet ty… Martin Thomson
Re: [quicwg/base-drafts] Long and short packet ty… Martin Thomson