Section 2.1 (comment 5)

[LPardue]

Section 2.1: Would clarifying actors and actions make the following clearer?

Current:
The Source Connection ID corresponds to the Destination Connection
ID the source would like to have on packets sent to it, and is
only present on long headers. On long header packets, the length
of the connection IDs is also present; on short header packets,
the length of the Destination Connection ID is implicit and need
to be known as such from the long header packets.

Perhaps (Making the first sentence more active ("The source adds", "the source indicates", "the destination uses"), and changing "need to be known as such" to "thus needs to be known" in the second sentence):
The source adds a Source Connection ID to long headers only. By
specifying a Source Connection ID, the source indicates what
the destination uses when constructing a Destination Connection
ID, which specifies where the source would like to have packets
sent. On long header packets, the length
of the connection IDs is also present; on short header packets,
the length of the Destination Connection ID is implicit and thus
needs to be known from the long header packets.

[mirjak]

Maybe this:

The Source Connection ID is
only present on long headers and indicates the Destination Connection
ID that the other endpoint should use when sending packets.
On long header packets, the length
of the connection IDs is also present; on short header packets,
the length of the Destination Connection ID is implicit and thus need
to be known as such from the long header packets.

[britram]

Minor edit:

The Source Connection ID is
only present on long headers and indicates the Destination Connection
ID that the other endpoint should use when sending packets.
On long header packets, the length
of the connection IDs is also present; on short header packets,
the length of the Destination Connection ID is implicit, as it is known
from preceding long header packets.