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

Include pictures for empty frames too #3744

Merged
merged 1 commit into from Jun 9, 2020
Merged

Include pictures for empty frames too #3744

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
36 changes: 29 additions & 7 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -5004,15 +5004,30 @@ to increase the size of a packet. Padding can be used to increase an initial
client packet to the minimum required size, or to provide protection against
traffic analysis for protected packets.

A PADDING frame has no content. That is, a PADDING frame consists of the single
byte that identifies the frame as a PADDING frame.
As shown in {{padding-format}}, a PADDING frame has no content. That is, a
PADDING frame consists of the single byte that identifies the frame as a PADDING
frame.

~~~
PADDING Frame {
Type (i) = 0x00,
}
~~~
{: #padding-format title="PADDING Frame Format"}


## PING Frame {#frame-ping}

Endpoints can use PING frames (type=0x01) to verify that their peers are still
alive or to check reachability to the peer. The PING frame contains no
additional fields.
alive or to check reachability to the peer. As shown in {{ping-format}} a PING
frame contains no content.

~~~
PING Frame {
Type (i) = 0x01,
}
~~~
{: #ping-format title="PING Frame Format"}

The receiver of a PING frame simply needs to acknowledge the packet containing
this frame.
Expand Down Expand Up @@ -5909,10 +5924,17 @@ APPLICATION_ERROR in an Initial or a Handshake packet.
## HANDSHAKE_DONE frame {#frame-handshake-done}

The server uses the HANDSHAKE_DONE frame (type=0x1e) to signal confirmation of
the handshake to the client. The HANDSHAKE_DONE frame contains no additional
fields.
the handshake to the client. As shown in {{handshake-done-format}}, a
HANDSHAKE_DONE frame has no content.

~~~
HANDSHAKE_DONE Frame {
Type (i) = 0x1e,
}
~~~
{: #handshake-done-format title="HANDSHAKE_DONE Frame Format"}

This frame can only be sent by the server. Servers MUST NOT send a
A HANDSHAKE_DONE frame can only be sent by the server. Servers MUST NOT send a
HANDSHAKE_DONE frame before completing the handshake. A server MUST treat
receipt of a HANDSHAKE_DONE frame as a connection error of type
PROTOCOL_VIOLATION.
Expand Down