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 typos in transport draft #1689

Merged
merged 2 commits into from Aug 21, 2018
Merged

Fix typos in transport draft #1689

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3b171c6
Fix typos in transport draft
amirlivneh Aug 21, 2018
cf66c74
Fix grammar
amirlivneh Aug 21, 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
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -3833,7 +3833,7 @@ The details of loss detection and congestion control are described in
The QUIC packet size includes the QUIC header and integrity check, but not the
UDP or IP header.

Clients MUST ensure that the first Initial packet it sends is sent in a UDP
Clients MUST ensure that the first Initial packet they send is sent in a UDP
datagram that is at least 1200 octets. Padding the Initial packet or including a
0-RTT packet in the same datagram are ways to meet this requirement. Sending a
UDP datagram of this size ensures that the network path supports a reasonable
Expand Down Expand Up @@ -3874,7 +3874,7 @@ QUIC endpoints that implement any kind of PMTU discovery SHOULD maintain an
estimate for each combination of local and remote IP addresses. Each pairing of
local and remote addresses could have a different maximum MTU in the path.

QUIC depends on the network path supporting a MTU of at least 1280 octets. This
QUIC depends on the network path supporting an MTU of at least 1280 octets. This
is the IPv6 minimum MTU and therefore also supported by most modern IPv4
networks. An endpoint MUST NOT reduce its MTU below this number, even if it
receives signals that indicate a smaller limit might exist.
Expand Down