[AVTCORE] [Errata Rejected] RFC4103 (5032)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 07 November 2023 09:22 UTC

To: gunnar.hellstrom@omnitor.se, gunnar.hellstrom@omnitor.se, paulej@packetizer.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: francesca.palombini@ericsson.com, iesg@ietf.org, avt@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20231107092142.7E79AAB208@rfcpa.amsl.com>
Date: Tue, 07 Nov 2023 01:21:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/l96wOnHMOoy9TGRUb_l3FgTmvcs>
Subject: [AVTCORE] [Errata Rejected] RFC4103 (5032)
Precedence: list

The following errata report has been rejected for RFC4103,
"RTP Payload for Text Conversation".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid5032

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
Date Reported: 2017-06-07
Rejected by: Francesca Palombini (IESG)

Section: 5.2

Original Text
-------------
After an idle period, the transmitter SHOULD set the M-bit to one in
the first packet with new text.

Corrected Text
--------------
After an idle period, the transmitter SHOULD set the M-bit to one in
the first packet with new text.

A number of approaches can be taken for how to compose the initial
packets in the session, and the packets sent at resumption after an
idle period. In order to harmonize transmitter behavior, and fulfill
requirements in RFC 2198[3] and RFC 4102[9], transmitters SHOULD
apply the following mechanism: Initially in the session and at
resumption of transmission after an idle period, when redundancy is
used, the packets to send SHOULD contain the same level of redundancy
as specified for the session. If redundant data for the specified
number of generations is not available for transmission, empty
T140blocks SHOULD be inserted in the packet for transmission to make
it contain the specified level of redundancy.

Notes
-----
RFC 4103 does not exactly specify how to compose the first packets in the session and the packets after an idle period, when redundancy is used in the session.

Even if receivers should be prepared to decode any valid packet composition, it eases interoperability when transmitters behave consistently.

RFC 2198 requires that the redundant format must carry at least the primary and one redundant level. RFC 4102 requires that if different compositions of the payloads in the packet is to be used, then each combination needs to be assigned its own payload type number. Assuming that that includes use of varying levels of redundancy with the same payload in the redundant data, these requirements lead to the recommendation to use the approach documented in the corrected text.
--VERIFIER NOTES--
Your comment is not in scope for errata reports, which are meant to collect errors in the documents, things that were actual errors at publication and that would have been fixed at that time had the working group or document authors noticed them -- they were just missed. What you've reported goes beyond what can be done in errata. The change, therefore, if it is to be applied needs to be achieved through a consensus document.

--------------------------------------
RFC4103 (draft-ietf-avt-rfc2793bis-09)
--------------------------------------
Title : RTP Payload for Text Conversation
Publication Date : June 2005
Author(s) : G. Hellstrom, P. Jones
Category : PROPOSED STANDARD
Source : Audio/Video Transport
Area : Real-time Applications and Infrastructure
Stream : IETF
Verifying Party : IESG

[AVTCORE] [Errata Rejected] RFC4103 (5032) RFC Errata System