Skip to content

Commit

Permalink
Padding with invalid packets is OK
Browse files Browse the repository at this point in the history
Closes #4738.
  • Loading branch information
martinthomson committed Jan 13, 2021
1 parent 25e5429 commit 2000306
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions draft-ietf-quic-transport.md
Expand Up @@ -4215,9 +4215,10 @@ meet size constraints; the endpoint MAY however discard such datagrams.
A client MUST expand the payload of all UDP datagrams carrying Initial packets
to at least the smallest allowed maximum datagram size of 1200 bytes by adding
PADDING frames to the Initial packet or by coalescing the Initial packet; see
{{packet-coalesce}}. Similarly, a server MUST expand the payload of all UDP
datagrams carrying ack-eliciting Initial packets to at least the smallest
allowed maximum datagram size of 1200 bytes.
{{packet-coalesce}}. Initial packets can even be coalesced with invalid
packets, which an receiver has to discard. Similarly, a server MUST expand the
payload of all UDP datagrams carrying ack-eliciting Initial packets to at least
the smallest allowed maximum datagram size of 1200 bytes.

Sending UDP datagrams of this size ensures that the network path supports a
reasonable Path Maximum Transmission Unit (PMTU), in both directions.
Expand Down

1 comment on commit 2000306

@nibanks
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fyi @martinthomson , I'd recommend an receiver -> a receiver

Please sign in to comment.