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

Padding non-HOWTO #4312

Merged
merged 1 commit into from Oct 29, 2020
Merged

Padding non-HOWTO #4312

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
12 changes: 12 additions & 0 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -6842,6 +6842,18 @@ decisions are made independently of client-selected values; a Source Connection
ID can be selected to route later packets to the same server.


## Traffic Analysis

The length of QUIC packets can reveal information about the length of the
content of those packets. The PADDING frame is provided so that endpoints have
some ability to obscure the length of packet content; see {{frame-padding}}.

Note however that defeating traffic analysis is challenging and the subject of
active research. Length is not the only way that information might leak.
Endpoints might also reveal sensitive information through other side channels,
such as the timing of packets.


## Overview of Security Properties {#security-properties}

A complete security analysis of QUIC is outside the scope of this document.
Expand Down