Make it clear that it is cleartext packets that have an FNV hash #683
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
martinthomson
added
-tls
editorial
mikkelfj
reviewed
Jul 15, 2017
draft-ietf-quic-tls.md
Outdated
|
|
||
| Unprotected packets all use the long form of the QUIC header and so will include | ||
| a version number. For this version of QUIC, the integrity check uses the 64-bit | ||
| QUIC adds an integrity check to all cleartext packets. Cleartext packetare not |
mikkelfj
reviewed
Jul 15, 2017
draft-ietf-quic-tls.md
Outdated
| protected by the negotiated AEAD (see {{packet-protection}}), but instead | ||
| include an integrity check. This check does not prevent the packet from being | ||
| altered, it exists for added resilience against data corruption and to provided | ||
| added assurance that the sender intends to use QUIC. |
seanturner
approved these changes
Jul 20, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the hackathon it came out that several people believed that Version Negotiation had integrity protection. This was understandable. The transport doc only said that integrity was for cleartext and said nothing about version neogitation, which isn't great. What was worse was that the TLS doc said that it was for all unprotected packets, which is not the case.