[quicwg/base-drafts] Checking frame type encoding? (#2155)

ekr <notifications@github.com> Thu, 13 December 2018 20:56 UTC

Date: Thu, 13 Dec 2018 20:56:20 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe817b20ddd00e0a32e6d4e1c3c79ae5f86e358ff92cf00000001182a897492a169ce174bfecb@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2155@github.com>
Subject: [quicwg/base-drafts] Checking frame type encoding? (#2155)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12c774c5e74_7d633fd971ad45b4342852"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/jHIgeCqBcDmIXFNfObiWHhz8FPE>

```
encoded as a single byte with the value 0x07.  An endpoint MUST treat the
receipt of a frame type that uses a longer encoding than necessary as a
connection error of type PROTOCOL_VIOLATION.
```

Why does this requirement exist? It seems like an odd place to be
picky when we're generally allowing implementations to do unusual
things without requiring checking. To be clear, I'm fine with the
shortest encoding rule, but the must check seems unnecessary
and inconvenient.



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

[quicwg/base-drafts] Checking frame type encoding… ekr
Re: [quicwg/base-drafts] Checking frame type enco… MikkelFJ
Re: [quicwg/base-drafts] Checking frame type enco… ekr
Re: [quicwg/base-drafts] Checking frame type enco… Martin Thomson
Re: [quicwg/base-drafts] Checking frame type enco… ekr
Re: [quicwg/base-drafts] Checking frame type enco… Martin Thomson
Re: [quicwg/base-drafts] Checking frame type enco… Martin Thomson