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

Add security considerations text and a small suggestion for suspiciou… #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add security considerations text and a small suggestion for suspiciou… #1

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion draft-ghedini-dprive-early-data.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,13 +77,18 @@ them.
Not all types of DNS queries are safe to be sent as early data. Clients MUST
NOT use early data to send DNS Updates ({{?RFC2136}}) or Zone Transfers
({{?RFC5936}}) messages. Servers receiving any of those messages MUST reply with
a "FormErr" response code.
a "FormErr" response code. Servers MAY log those suspicious messages
including their sender's address.

[[TODO: forbid other types? use a different status code? should we define a
whitelist instead of a blacklist?]]

# Security Considerations

This whole document discusses the security implications of using
TLS 1.3 early data extension with DNS. It also offers different
solutions for each aspect.

## Information Exposure

By replaying DNS queries that were captured when transmitted over early data,
Expand Down