Draft: draft-ietf-quic-transport

Commentary: We did n't really need to use a new " term " for the concept of including multiple frames in a packet . The use of " bundle " implied more than what was really happening . Using plain words is probably better . 
 What does “ bundling ” refer to ? I think I might now understand coalescing , but I do n’t understand if bundling is subtly different ? 
 Several instances I see in the draft refer to the situation where an endpoint is required to send a packet containing certain frames . The endpoint might opportunistically add other frames , not mandated to be sent , as long as it 's doing the work of generating and sending a packet anyway . These opportunistically frames are " bundled " with the mandatory frames . More generally , the term refers to selecting a collection of frames waiting to be sent when generating an outgoing packet . 
 (  coalescing , which is putting more than one packet in a single UDP datagram . ) 
 tbh , I think the text reads a lot better with bundling . Thanks !  is better .
Paragraph (version A):
A sender can minimize per-packet bandwidth and computational costs by
bundling as many frames as possible within a QUIC packet.  A sender
MAY wait for a short period of time to bundle multiple frames before
sending a packet that is not maximally packed, to avoid sending out
large numbers of small packets.  An implementation MAY use knowledge
about application sending behavior or heuristics to determine whether
and for how long to wait.  This waiting period is an implementation
decision, and an implementation should be careful to delay
conservatively, since any delay is likely to increase application-
visible latency.
Paragraph (version B):
A sender can minimize per-packet bandwidth and computational costs by
including as many frames as possible in each QUIC packet.  A sender
MAY wait for a short period of time to collect multiple frames before
sending a packet that is not maximally packed, to avoid sending out
large numbers of small packets.  An implementation MAY use knowledge
about application sending behavior or heuristics to determine whether
and for how long to wait.  This waiting period is an implementation
decision, and an implementation should be careful to delay
conservatively, since any delay is likely to increase application-
visible latency.
Paragraph (version A):
One of the benefits of QUIC is avoidance of head-of-line blocking
across multiple streams.  When a packet loss occurs, only streams
with data in that packet are blocked waiting for a retransmission to
be received, while other streams can continue making progress.  Note
that when data from multiple streams is bundled into a single QUIC
packet, loss of that packet blocks all those streams from making
progress.  Implementations are advised to bundle as few streams as
necessary in outgoing packets without losing transmission efficiency
to underfilled packets.
Paragraph (version B):
One of the benefits of QUIC is avoidance of head-of-line blocking
across multiple streams.  When a packet loss occurs, only streams
with data in that packet are blocked waiting for a retransmission to
be received, while other streams can continue making progress.  Note
that when data from multiple streams is included in a single QUIC
packet, loss of that packet blocks all those streams from making
progress.  Implementations are advised to include as few streams as
necessary in outgoing packets without losing transmission efficiency
to underfilled packets.