Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update to Figure 12 #191

Merged
merged 1 commit into from Dec 26, 2020
Merged

Update to Figure 12 #191

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
24 changes: 13 additions & 11 deletions draft-ietf-tls-dtls13.md
View file
Open in desktop
Expand Up @@ -1648,16 +1648,17 @@ The traffic key calculation is described in Section 7.3 of {{!TLS13}}.
Client Server
------ ------

Record 0
ClientHello
(epoch=0)
-------->

Record 0
<-------- HelloRetryRequest
(epoch=0)

Record 1
ClientHello -------->
(epoch=0)

Record 1
<-------- ServerHello
(epoch=0)
{EncryptedExtensions}
Expand All @@ -1668,37 +1669,38 @@ Client Server
(epoch=2)
{Finished}
(epoch=2)

Record 2
{Certificate} -------->
(epoch=2)
{CertificateVerify}
(epoch=2)
{Finished}
(epoch=2)

Record 2
<-------- [ACK]
(epoch=3)

Record 3
[Application Data] -------->
(epoch=3)

Record 3
<-------- [Application Data]
(epoch=3)

Some time later ...
(Post-Handshake Message Exchange)

Record 4
<-------- [NewSessionTicket]
(epoch=3)

Record 4
[ACK] -------->
(epoch=3)

Some time later ...
(Rekeying)

Record 5
<-------- [Application Data]
(epoch=4)
Record 5
[Application Data] -------->
(epoch=4)
~~~
Expand Down Expand Up @@ -1861,7 +1863,7 @@ low-power mesh networks, the use of ACKs is recommended.

The use of the ACK for the second case is mandatory for the proper functioning of the
protocol. For instance, the ACK message sent by the client in Figure 12,
acknowledges receipt and processing of record 2 (containing the NewSessionTicket
acknowledges receipt and processing of record 4 (containing the NewSessionTicket
message) and if it is not sent the server will continue retransmission
of the NewSessionTicket indefinitely until its transmission cap is reached.

Expand Down