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

fix wording that said only long header packets could be coalesced #1324

Merged
merged 2 commits into from Apr 25, 2018
Merged

fix wording that said only long header packets could be coalesced #1324

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
87422f0
fix wording that said only long header packets could be coalesced
mcmanus Apr 24, 2018
38d5b83
THE end
martinthomson Apr 25, 2018
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
8 changes: 4 additions & 4 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -372,10 +372,10 @@ The interpretation of the fields and the payload are specific to a version and
packet type. Type-specific semantics for this version are described in the
following sections.

End of the Payload field (which is also the end of the long header packet) is
determined by the value of the Payload Length field. Senders can coalesce
multiple long header packets into one UDP datagram. See {{packet-coalesce}} for
more details.
The end of the Payload field (which is also the end of the long header
packet) is determined by the value of the Payload Length field.
Senders can sometimes coalesce multiple packets into one UDP datagram.
See {{packet-coalesce}} for more details.


## Short Header
Expand Down