Updated examples in Section 5.6 #188
Conversation
| Remarks: | ||
|
|
||
| - The HelloRetryRequest shown in (1) is an optional message sent by the server. | ||
| - The ACK message is sent by a client in response to a NewSessionTicket message from the server (as noted in (3)) or sent by a server in response to receipt of flight (2). In those cases it represent a flight on its own. |
There was a problem hiding this comment.
I tend to think we should not think of an ACK as part of a flight. It's kind of outside this model.
| | (2) | x | | Certificate*, CertificateVerify*, Finished | | ||
| | | | x | ACK | | ||
| | (3) | | x | NewSessionTicket | | ||
| {: #tab-flights title="Flight Handshake Message Combinations."} |
There was a problem hiding this comment.
I don't quite see what the Note column is doing.
| | (1) | | x | HelloRetryRequest | | ||
| | | | x | ServerHello, EncryptedExtensions, CertificateRequest*, Certificate*, CertificateVerify*, Finished | | ||
| | (2) | x | | Certificate*, CertificateVerify*, Finished | | ||
| | | | x | ACK | |
There was a problem hiding this comment.
(A client will send ACK in response to post-handshake messages, just not during the initial handshake. I think this is okay as the table contents, but maybe we should ensure that the prose is clear this is just for the initial handshake.) Though, given ekr's comment below, perhaps it's going away anyway and becomes irrelevant.
There was a problem hiding this comment.
I actually left ACK in because it was more confusing not to.
| Note: The application data sent by the client is not included in the | ||
| timeout and retransmission calculation. | ||
|
|
||
| {: #dtls-post-handshake-ticket title="Message flights for the NewSessionTicket message"} |
There was a problem hiding this comment.
Do we also want to mention KeyUpdate/NewConnectionID/RequestConnectionID here? It seems overkill to have a separate figure showing the message and ACK for each of them...
There was a problem hiding this comment.
Yeah, I guess that would work.
|
@kaduk I merged this. Any chance you want to send a PR or do you want me to? |
I'm not in a great spot to make a PR at the moment; please go ahead. |
|
I just fixed this in the main branch. |
No description provided.