[quicwg/base-drafts] TLS Early Data is impossible (#3039)

martinduke <notifications@github.com> Mon, 16 September 2019 23:15 UTC

Date: Mon, 16 Sep 2019 16:15:40 -0700
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK35JFK4YNSNGIZLW5F3RVMCZEVBNHHB25V4CU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3039@github.com>
Subject: [quicwg/base-drafts] TLS Early Data is impossible (#3039)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d80179c97d0b_113e3fce4f6cd95c1789d0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/LJ7Xb6yVu017GxuktPDcIpmU1Xs>

Section 4.5 of quic-tls:

Early data within the TLS connection MUST NOT be used.  As it is for
   other TLS application data, a server MUST treat receiving early data
   on the TLS connection as a connection error of type
   PROTOCOL_VIOLATION.

As there is no way to express TLS application data (no record headers!) I believe there is no way for the proposed error condition to occur. I propose we strike the paragraph, though we might mention that this condition is impossible for clarity.

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

[quicwg/base-drafts] TLS Early Data is impossible… martinduke
Re: [quicwg/base-drafts] TLS Early Data is imposs… martinduke