Found 2 records.

Status: Verified (1)

RFC 5651, "Layered Coding Transport (LCT) Building Block", October 2009

Errata ID: 3843
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Eric Turcotte
Date Reported: 2013-12-16
Verifier Name: Martin Stiemerling
Date Verified: 2015-12-16

Section 5.2.1 says:

There are two formats for Header Extension fields, as depicted in
Figure 2. The first format is used for variable-length extensions,
with Header Extension Type (HET) values between 0 and 127. The
second format is used for fixed-length (one 32-bit word) extensions,
using HET values from 127 to 255.

It should say:

There are two formats for Header Extension fields, as depicted in
Figure 2. The first format is used for variable-length extensions,
with Header Extension Type (HET) values between 0 and 127. The
second format is used for fixed-length (one 32-bit word) extensions,
using HET values from 128 to 255.

Notes:

the correct range for one 32-bit word extension HET values starts from 128, and not from 127.

Status: Reported (1)

RFC 5651, "Layered Coding Transport (LCT) Building Block", October 2009

Errata ID: 7638
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Sam Hurst
Date Reported: 2023-09-11

Section 2 says:

   Beyond support for congestion control, LCT provides a number of
   fields and supports functionality commonly required by many
   protocols.  For example, LCT provides a Transmission Session ID that
   can be used to identify to which session each received packet
   belongs.  This is important because a receiver may be joined to many
   sessions concurrently, and thus it is very useful to be able to
   demultiplex packets as they arrive according to the session to which
   they belong.  As another example, there are optional fields within
   the LCT packet header for identifying the object about which
   information is carried in the packet payload.

It should say:

   Beyond support for congestion control, LCT provides a number of 
   fields and supports functionality commonly required by many 
   protocols.  For example, LCT provides a Transport Session ID that 
   can be used to identify to which session each received packet 
   belongs.  This is important because a receiver may be joined to many 
   sessions concurrently, and thus it is very useful to be able to 
   demultiplex packets as they arrive according to the session to which 
   they belong.  As another example, there are optional fields within 
   the LCT packet header for identifying the object about which 
   information is carried in the packet payload.

Notes:

There is an inconsistency in the definition of the TSI acronym. There are 6 instances of TransPORT session identifier/ID, and 2 instances of TransMISSION session identifier/ID. The other instance is in section 3, paragraph 3 ("One of the required fields is the TransMISSION Session ID (TSI).")

Report New Errata