RFC Errata
Found 3 records.
Status: Verified (3)
RFC 4326, "Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS)", December 2005
Source of RFC: ipdvb (int)
Errata ID: 124
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Gorry Fairhurst
Date Reported: 2006-08-02
Section 7.2 says:
When in the Reassembly State, the Receiver reads a 2-byte SNDU Length field from the TS Packet payload. If the value is less than or equal to 4, or equal to 0xFFFF, the Receiver discards the Current SNDU and
It should say:
When in the Reassembly State, the Receiver reads the first two bytes from the TS Packet payload. This value forms the first 2 bytes of the SNDU base header, which is a combination of the D-bit and the SNDU-Length. If the combined value is less than or equal to 4, or equal to 0xFFFF (i.e. D=1 and SNDU Length = 32768), the Receiver MUST discard the Current SNDU and
Notes:
- Usage of last byte in a TS-Packet.
Source: Bernhard Collini-Nocker & Gorry Fairhurst, 15th February 2006
Errata ID: 726
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Gorry Fairhurst
Date Reported: 2006-08-02
Section 4.1 says:
The most significant bit of the Length field carries the value of the Destination Address Absent Field, the D-bit
It should say:
The most significant bit of the first byte of the SNDU base header carries the value of the Destination Address Absent Field, the D-bit
Notes:
- Length field description refers to a 16-bit value.
Source: Bernhard Collini-Nocker, 15th February 2006
Errata ID: 727
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Gorry Fairhurst
Date Reported: 2006-08-02
In Example A.2, it says:
| HDR | 0x00 | 0x00 | 0xB1 | ... | C180 | 0x00 | 0x65 |
It should say:
| HDR | 0x00 | 0x00 | 0xB1 | ... | C180 | 0x00 | 0xB5 |
Notes:
- Misrepresentation of hex byte in example, Change /0x65/0xB5/
Source: Karsten Siebert, 26th February 2006