Skip to content

Try to hack around limitations in aasvg #1406

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

Open
martinthomson wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Try to hack around limitations in aasvg #1406

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7b7d353
Try to hack around limitations in aasvg
martinthomson Feb 12, 2026
94452d3
Avoid symbols
martinthomson Feb 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 22 additions & 23 deletions draft-ietf-tls-rfc8446bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -685,38 +685,37 @@ TLS supports three basic key exchange modes:
Client Server

Key ^ ClientHello
Exch | + key_share*
| + signature_algorithms*
| + psk_key_exchange_modes*
v + pre_shared_key* -------->
Exch | - key_share*
| - signature_algorithms*
| - psk_key_exchange_modes*
v - pre_shared_key* -------->
ServerHello ^ Key
+ key_share* | Exch
+ pre_shared_key* v
{EncryptedExtensions} ^ Server
{CertificateRequest*} v Params
- key_share* | Exch
- pre_shared_key* v
{EncryptedExtensions} ⎤ Server
{CertificateRequest*} ⎦ Params
{Certificate*} ^
{CertificateVerify*} | Auth
{Finished} v
<-------- [Application Data*]
^ {Certificate*}
Auth | {CertificateVerify*}
^ {Certificate＊}
Auth | {CertificateVerify＊}
v {Finished} -------->
[Application Data] <-------> [Application Data]

+ Indicates noteworthy extensions sent in the
previously noted message.

* Indicates optional or situation-dependent
messages/extensions that are not always sent.

{} Indicates messages protected using keys
derived from a [sender]_handshake_traffic_secret.

[] Indicates messages protected using keys
derived from [sender]_application_traffic_secret_N.
[Application Data] <=======> [Application Data]
~~~
{: #tls-full title="Message Flow for Full TLS Handshake"}

The annotations in {{tls-full}} are as follows:

* "-" Indicates noteworthy extensions sent in the
previously noted message.
* "*" indicates optional or situation-dependent
messages/extensions that are not always sent.
* "{...}" Indicates messages protected using keys
derived from a \[sender]_handshake_traffic_secret.
* "[...]" Indicates messages protected using keys
derived from \[sender]_application_traffic_secret_N.

The handshake can be thought of as having three phases (indicated
in the diagram above):

Expand Down