Draft: draft-ietf-quic-invariants

Commentary: Looks like all leftovers from renamed elements .
Paragraph (version A):
The next byte contains the length in bytes of the two Connection IDs
(see connection-id) that follow.  Each length is encoded as a 4-bit
unsigned integer.  The length of the Destination Connection ID (DCIL)
occupies the high bits of the byte and the length of the Source
Connection ID (SCIL) occupies the low bits of the byte.  An encoded
length of 0 indicates that the connection ID is also 0 bytes in
length.  Non-zero encoded lengths are increased by 3 to get the full
length of the connection ID; the final value is therefore either 0 or
between 4 and 18 bytes in length (inclusive).  For example, an byte
with the value 0xe0 describes a 17 byte Destination Connection ID and
a zero byte Source Connection ID.
Paragraph (version B):
The next byte contains the length in bytes of the two Connection IDs
(see connection-id) that follow.  Each length is encoded as a 4-bit
unsigned integer.  The length of the Destination Connection ID (DCIL)
occupies the high bits of the byte and the length of the Source
Connection ID (SCIL) occupies the low bits of the byte.  An encoded
length of 0 indicates that the connection ID is also 0 bytes in
length.  Non-zero encoded lengths are increased by 3 to get the full
length of the connection ID; the final value is therefore either 0 or
between 4 and 18 bytes in length (inclusive).  For example, a byte
with the value 0xe0 describes a 17 byte Destination Connection ID and
a zero byte Source Connection ID.
Paragraph (version A):
Once the handshake completes, if an endpoint is unable to buffer all
data in a CRYPTO frame, it MAY discard that CRYPTO frame and all
CRYPTO frames received in the future, or it MAY close the connection
with an CRYPTO_BUFFER_EXCEEDED error code.  Packets containing
discarded CRYPTO frames MUST be acknowledged because the packet has
been received and processed by the transport even though the CRYPTO
frame was discarded.
Paragraph (version B):
Once the handshake completes, if an endpoint is unable to buffer all
data in a CRYPTO frame, it MAY discard that CRYPTO frame and all
CRYPTO frames received in the future, or it MAY close the connection
with a CRYPTO_BUFFER_EXCEEDED error code.  Packets containing
discarded CRYPTO frames MUST be acknowledged because the packet has
been received and processed by the transport even though the CRYPTO
frame was discarded.
Paragraph (version A):
An immediate close can be used after an application protocol has
arranged to close a connection.  This might be after the application
protocols negotiates a graceful shutdown.  The application protocol
exchanges whatever messages that are needed to cause both endpoints
to agree to close the connection, after which the application
requests that the connection be closed.  The application protocol can
use an CONNECTION_CLOSE frame with an appropriate error code to
signal closure.
Paragraph (version B):
An immediate close can be used after an application protocol has
arranged to close a connection.  This might be after the application
protocols negotiates a graceful shutdown.  The application protocol
exchanges whatever messages that are needed to cause both endpoints
to agree to close the connection, after which the application
requests that the connection be closed.  The application protocol can
use a CONNECTION_CLOSE frame with an appropriate error code to signal
closure.
Paragraph (version A):
The byte following the version contains the lengths of the two
connection ID fields that follow it.  These lengths are encoded as
two 4-bit unsigned integers.  The Destination Connection ID Length
(DCIL) field occupies the 4 high bits of the byte and the Source
Connection ID Length (SCIL) field occupies the 4 low bits of the
byte.  An encoded length of 0 indicates that the connection ID is
also 0 bytes in length.  Non-zero encoded lengths are increased by
3 to get the full length of the connection ID, producing a length
between 4 and 18 bytes inclusive.  For example, an byte with the
value 0x50 describes an 8-byte Destination Connection ID and a
zero-length Source Connection ID.
Paragraph (version B):
The byte following the version contains the lengths of the two
connection ID fields that follow it.  These lengths are encoded as
two 4-bit unsigned integers.  The Destination Connection ID Length
(DCIL) field occupies the 4 high bits of the byte and the Source
Connection ID Length (SCIL) field occupies the 4 low bits of the
byte.  An encoded length of 0 indicates that the connection ID is
also 0 bytes in length.  Non-zero encoded lengths are increased by
3 to get the full length of the connection ID, producing a length
between 4 and 18 bytes inclusive.  For example, a byte with the
value 0x50 describes an 8-byte Destination Connection ID and a
zero-length Source Connection ID.