RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 1 record.

Status: Reported (1)

RFC 5740, "NACK-Oriented Reliable Multicast (NORM) Transport Protocol", November 2009

Source of RFC: rmt (tsv)

Errata ID: 6405
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Ronald in 't Velt
Date Reported: 2021-01-21

Section 4.2.1 says:

For NORM_OBJECT_FILE and NORM_OBJECT_STREAM objects, the data segment length and offset can be calculated using the block partitioning algorithm described in the
FEC Building Block [RFC5052] document. For NORM_OBJECT_STREAM objects, the length and offset is obtained from the segment’s corresponding embedded "payload_len" and "payload_offset" fields.

It should say:

For NORM_OBJECT_FILE and NORM_OBJECT_DATA objects, the data segment length and offset can be calculated using the block partitioning algorithm described in the
FEC Building Block [RFC5052] document. For NORM_OBJECT_STREAM objects, the length and offset is obtained from the segment’s corresponding embedded "payload_len" and "payload_offset" fields.

Notes:

The partitioning algorithm specified in RFC 5052 and referenced here applies only to NORM_OBJECT_FILE and NORM_OBJECT_DATA objects, not to NORM_OBJECT_STREAM objects. In fact, these sentences at the very end of section 4.2.1 merely try to reiterate what has already been said earlier in the same section with reference to the header fields 'payload_len', 'payload_msg_start' and 'payload_offset': "For objects of types NORM_OBJECT_FILE and NORM_OBJECT_DATA, these fields are unnecessary since the receiver can calculate the payload length and offset information from the "fec_payload_id" using the REQUIRED block partitioning algorithm described in the FEC Building Block [RFC5052] document."

Report New Errata