Here are two images by the two authors representing different views of the naming issues:

2/n

QUIC is defined in four RFCs spanning a few hundred pages, so making sense of that for textbook length coverage is no small task. But that's what we're willing to do for the devoted readers of our books.

There's a disconcerting (for old school types) lack of packet headers in the QUIC specs, where textual representation of packet headers has been used. We decided to make some packet header pictures anyway.

We hope the person who gave us a one-star review entitled "Wall of Text" appreciates the effort.

https://www.amazon.com/gp/customer-reviews/R1IVEX207N7WY8/ref=cm_cr_arp_d_rvw_ttl?ie=UTF8&ASIN=B004VF6216

(For comparison, here is the same header as described in the spec:

Long Header Packet {
Header Form (1) = 1,
Fixed Bit (1) = 1,
Long Packet Type (2),
Type-Specific Bits (4),
Version (32),
Destination Connection ID Length (8),
Destination Connection ID Length (8),
Destination Connection ID (0..160),
Source Connection ID Length (8),
Source Connection ID (0..160),
Type-Specific Payload (..),
}
3/n

Front cover in more detail:

Cover photo by Ziggy Stone on unsplash https://unsplash.com/@pacnw