[AVTCORE] [Technical Errata Reported] RFC4867 (4349)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 27 April 2015 15:58 UTC

To: Johan.Sjoberg@ericsson.com, Magnus.Westerlund@ericsson.com, ari.lakaniemi@nokia.com, Qiaobing.Xie@motorola.com, ben@nostrum.com, alissa@cooperw.in, keith.drage@alcatel-lucent.com, roni.even@mail01.huawei.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150427155709.23479180092@rfc-editor.org>
Date: Mon, 27 Apr 2015 08:57:09 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/5pf1HvjAlEguo48fOXNFoeml7LM>
Cc: Thomas.Belling@nokia.com, avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVTCORE] [Technical Errata Reported] RFC4867 (4349)
Precedence: list

The following errata report has been submitted for RFC4867,
"RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4867&eid=4349

--------------------------------------
Type: Technical
Reported by: Thomas Belling <Thomas.Belling@nokia.com>

Section: 8.1

Original Text
-------------
mode-set: Restricts the active codec mode set to a subset of all
modes, for example, to be able to support transport
channels such as GSM networks in gateway use cases.
Possible values are a comma separated list of modes from
the set: 0,...,7 (see Table 1a [2]). The SID frame type
8 and NO_DATA (frame type 15) are never included in the
mode set, but can always be used. If mode-set is
specified, it MUST be abided, and frames encoded with
modes outside of the subset MUST NOT be sent in any RTP
payload or used in codec mode requests. If not present,
all codec modes are allowed for the payload type.

Corrected Text
--------------
mode-set: Restricts the active codec mode set to a subset of all
modes, for example, to be able to support transport
channels such as GSM networks in gateway use cases.
Possible values are a comma separated list of modes from
the set: 0,...,7 (see Table 1a [2]). The SID frame type
8 and NO_DATA (frame type 15) are never included in the
mode set, but can always be used. If mode-set is
specified, it MUST be abided, i.e. frames encoded with
modes outside of the subset MUST NOT be sent in any RTP
payload and codec mode requests MUST only use modes
within the mode-set or CMR=15. If the mode-set parameter
is not present, then all codec modes are allowed for the
payload type.

Notes
-----
The existing text rules out that CMR=15 is used when a mode-set has been negotiated. However, this contradicts a statement in .clause 4.3.1 that if a terminal has no preference in which mode to receive, it SHOULD set CMR=15 in all its outbound payloads.

This erratum has been discussed and endorsed by the 3GPP SA4 group before submission to IETF.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC4867 (draft-ietf-avt-rtp-amr-bis-06)
--------------------------------------
Title : RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs
Publication Date : April 2007
Author(s) : J. Sjoberg, M. Westerlund, A. Lakaniemi, Q. Xie
Category : PROPOSED STANDARD
Source : Audio/Video Transport
Area : Real-time Applications and Infrastructure
Stream : IETF
Verifying Party : IESG

[AVTCORE] [Technical Errata Reported] RFC4867 (43… RFC Errata System
Re: [AVTCORE] [Technical Errata Reported] RFC4867… Magnus Westerlund
Re: [AVTCORE] [Technical Errata Reported] RFC4867… Magnus Westerlund
[AVTCORE] [Errata Verified] RFC4867 (4349) RFC Errata System