I have a minor comment on DTLS 1.3 draft 37.
On the topic of sending ACKs, the draft recommends:
```
ACKs SHOULD NOT be sent for other complete
flights because they are implicitly acknowledged by the receipt of
the next flight, which generally immediately follows the flight.
```
I wonder if the
Thanks. This seems like a good improvement. I have filed
https://github.com/tlswg/dtls13-spec/issues/128 to track it.
On Fri, Mar 27, 2020 at 8:29 AM Hanno Becker wrote:
> I have a minor comment on DTLS 1.3 draft 37.
>
> On the topic of sending ACKs, the draft recommends:
>
> ```
> ACKs SHOULD N
Another comment on DTLS 1.3 draft 37.
I believe there is a slight ambiguity in the description of what
shall happen after a peer sends the last flight in a handshake.
On the one hand, the spec says:
```
In the SENDING state, the implementation transmits the buffered
flight of messages. If
I know that this WGLC was supposed to focus on the diff between -34
and -37. I don't have any comments on that diff, but I do have some
comments on the draft following a re-read of the entire document.
# Minor
The term "deprotection" is used twice in document but never defined.
Section 5.11 aba
