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

receivers cannot enforce datagram padding (though they may drop) #4254

Merged
merged 8 commits into from Oct 20, 2020
Merged

receivers cannot enforce datagram padding (though they may drop) #4254

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
6d59f18
endpoint MAY discard, MUST NOT close when receiving a datagram that d…
kazuho Oct 20, 2020
a364f7d
add ref
kazuho Oct 20, 2020
3fce52c
Update draft-ietf-quic-transport.md
kazuho Oct 20, 2020
49585a1
Update draft-ietf-quic-transport.md
kazuho Oct 20, 2020
db00657
Update draft-ietf-quic-transport.md
kazuho Oct 20, 2020
353747d
drop reference to packet coalescing, as suggested by @martinthomson
kazuho Oct 20, 2020
f4e391a
minimumumum
martinthomson Oct 20, 2020
bbb245b
Update draft-ietf-quic-transport.md
janaiyengar Oct 20, 2020
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: 3 additions & 5 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -4086,11 +4086,9 @@ UDP datagrams MUST NOT be fragmented at the IP layer. In IPv4
fragmentation on the path.

Datagrams are required to be padded under some conditions. However, the
martinthomson marked this conversation as resolved.
Show resolved Hide resolved
size of the datagram is not authenticated, and endpoints might send coalesced
packets after the handshake is confirmed; see {{packet-coalesce}}. Therefore,
an endpoint MUST NOT close a connection when it receives a datagram that does
not meet size constraints, though the endpoint MAY discard such
datagrams.
size of the datagram is not authenticated. Therefore, an endpoint MUST NOT
close a connection when it receives a datagram that does not meet size
constraints, though the endpoint MAY discard such datagrams.


## Initial Datagram Size {#initial-size}
Expand Down