Skip to content

Commit

Permalink
Christian's suggested coalescing tweak, fixes #1702
Browse files Browse the repository at this point in the history
  • Loading branch information
@martinthomson
martinthomson committed Aug 27, 2018
1 parent 39d9d29 commit 4600624
Showing 1 changed file with 4 additions and 5 deletions.
9 changes: 4 additions & 5 deletions draft-ietf-quic-transport.md
View file
Expand Up @@ -919,11 +919,10 @@ packets, though failing to do so will require sending a significantly
larger number of datagrams during the handshake. Receivers MUST
be able to process coalesced packets.

Senders SHOULD coalesce packets in order of increasing encryption levels
(Initial, Handshake, 0-RTT, 1-RTT), as this makes it more likely the receiver
will be able to process all the packets in a single pass. A packet with a short
header does not include a length, so it will always be the last packet included
in a UDP datagram.
Coalescing packets in order of increasing encryption levels (Initial, 0-RTT,
Handshake, 1-RTT) makes it more likely the receiver will be able to process all
the packets in a single pass. A packet with a short header does not include a
length, so it will always be the last packet included in a UDP datagram.

Senders MUST NOT coalesce QUIC packets with different Destination Connection
IDs into a single UDP datagram. Receivers SHOULD ignore any subsequent packets
Expand Down

1 comment on commit 4600624

@huitema
Copy link
Contributor

@huitema huitema commented on 4600624 Aug 27, 2018 •
edited

Choose a reason for hiding this comment

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

Yes, I recognize that I could have written a PR myself. Thanks for doing it.

Please sign in to comment.