When looking at stuff some more, I noticed that extension
status_request_v2, which is used by OCSP stapling and is not deprecated
[1].
Now, that extension uses additional handshake message type
(certificate_status), which is specified to go between Certificate
and SKE. Now, TLS 1.3 does not have S
I am looking at the specification of the key share extension, section 6.3.2.3
of the 1.3 draft. I think that the behavior is somewhat underspecified. The
spec says:
...Clients MAY omit this extension from the ClientHello, and in response to
this, servers MUST send a HelloRetryRequest requestin
On Friday, December 11, 2015 08:13:05 pm Christian Huitema wrote:
> I am looking at the specification of the key share extension, section 6.3.2.3
> of the 1.3 draft. I think that the behavior is somewhat underspecified. The
> spec says:
>
> ...Clients MAY omit this extension from the ClientHell
I think that the best way to deal with the status_request_v2 extension
is to make it a proper part of the TLS 1.3 messages, probably
Certificate or CertificateVerify. This is a fairly heavily important
extension.
On 12 December 2015 at 05:52, Ilari Liusvaara wrote:
> When looking at stuff some m
