Re: [AVTCORE] Discuss on draft-ietf-avt-forward-shifted-red-06

Colin Perkins <> Thu, 19 May 2011 07:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BD340E0681 for <>; Thu, 19 May 2011 00:46:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.318
X-Spam-Status: No, score=-102.318 tagged_above=-999 required=5 tests=[AWL=-0.881, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RCVD_IN_DNSWL_LOW=-1, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BPdMUWpTiGWS for <>; Thu, 19 May 2011 00:46:02 -0700 (PDT)
Received: from (unknown []) by (Postfix) with ESMTP id AD950E067C for <>; Thu, 19 May 2011 00:46:02 -0700 (PDT)
Received: from ([] helo=[]) by with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1QMxvl-0000nN-bn; Thu, 19 May 2011 07:46:01 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Colin Perkins <>
In-Reply-To: <>
Date: Thu, 19 May 2011 08:45:59 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Magnus Westerlund <>
X-Mailer: Apple Mail (2.1084)
Cc: IETF AVTCore WG <>
Subject: Re: [AVTCORE] Discuss on draft-ietf-avt-forward-shifted-red-06
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 19 May 2011 07:46:03 -0000

On 19 May 2011, at 08:30, Magnus Westerlund wrote:

> WG,
> Peter Saint-Andre has one part of his discuss which I believe we need WG input on.
>> 1) It is not clear to me why this document is registering 2 new MIME types, instead of just registering a new optional parameter "forwardshift" for the already registered audio/red MIME type. Handling of these 2 new MIME types without the "forwardshift" parameter seems to be identical to the handling of audio/red.
> I have discussed this discuss with Peter and clarified that there is one actual difference between the two approaches.
> Where using new mime types results in that one handles this as two independent media formats. Thus requiring two different payload types and negotiating them independently. And these two payload types is in fact resulting to a doubling of the number of payload types required in relation to the combination of primary secondary. This as each payload type only can carry one specific combination of redundancy.
> Using a optional parameter in the existing types has the result that one uses only one payload type and in a negotiation context, like SDP offer/answer one will use forward redundancy if both peers acknowledge the optional parameter, and if the other doesn't understand one gets automatic downgrade to RFC 2198 behavior. If this is the desired behavior my small concern is how well the implementations handle new optional parameters. They should but I have no knowledge how well people implements that handling.
> So the question to the WG is what behavior is really desired here?

The problem with using an optional parameter is that the extension changes the semantics and is not backwards compatible. This would break older implementations that ignore the new parameter. A new payload type will not be understood by old implementations, but at least it won't be misinterpreted. Because of this, I think we want new media types.

Colin Perkins