On Sun, Apr 19, 2020 at 03:41:49PM -0700, Eric Rescorla wrote:
> I don't think we should make this change. In the context of this draft, if
> the client wants that behavior, it should send {1, 1}.
That precludes clients from soliciting 0 *only* from servers that
support some future specification,
I don't think we should make this change. In the context of this draft, if
the client wants that behavior, it should send {1, 1}.
-Ekr
On Sun, Apr 19, 2020 at 3:23 PM Viktor Dukhovni
wrote:
> I uploaded a small pull request for the ticket request draft:
>
> https://github.com/tlswg/draft-i
I uploaded a small pull request for the ticket request draft:
https://github.com/tlswg/draft-ietf-tls-ticketrequest/pull/20
it stipulates that servers SHOULD send at least one ticket unless *both*
counters are zero. A client willing to accept tickets for either of the
two handshake types is
I have posted a PR to clarify this:
https://github.com/tlswg/dtls13-spec/pull/142
On Tue, Apr 14, 2020 at 1:13 AM Hanno Becker wrote:
> Hi all,
>
> On ACK protection, DTLS 1.3 Draft 37 says in Section 7:
>
>ACK records MUST be sent with an epoch that is equal to or higher
>than the recor
Issues
--
* tlswg/draft-ietf-tls-esni (+5/-0/💬11)
5 issues created:
- two type codes needed for interop (by sftcd)
https://github.com/tlswg/draft-ietf-tls-esni/issues/220
- cardinality of ECHOConfig vs. HTTPSSVC (by sftcd)
https://github.com/tlswg/draft-ietf-tls-esni/issues/219
