Re: [AVT] How is SDP a=fmtp used for RFC 2198?

Colin Perkins <csp@csperkins.org> Fri, 09 April 2004 12:42 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25490 for <avt-archive@odin.ietf.org>; Fri, 9 Apr 2004 08:42:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBvKc-0007sv-Ud for avt-archive@odin.ietf.org; Fri, 09 Apr 2004 08:42:11 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i39Cg2ZF030289 for avt-archive@odin.ietf.org; Fri, 9 Apr 2004 08:42:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBvKc-0007pv-ED; Fri, 09 Apr 2004 08:42:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBrwf-0001Rp-M5 for avt@optimus.ietf.org; Fri, 09 Apr 2004 05:05:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18935 for <avt@ietf.org>; Fri, 9 Apr 2004 05:05:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBrwb-0003UH-00 for avt@ietf.org; Fri, 09 Apr 2004 05:05:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBrvZ-0003MV-00 for avt@ietf.org; Fri, 09 Apr 2004 05:03:58 -0400
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163]) by ietf-mx with esmtp (Exim 4.12) id 1BBruI-0003AC-00 for avt@ietf.org; Fri, 09 Apr 2004 05:02:38 -0400
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:63947 helo=[192.168.0.5]) by dundee.dcs.gla.ac.uk with asmtp (TLSv1:RC4-SHA:128) (Exim 4.04) id 1BBrtX-00064H-00; Fri, 09 Apr 2004 10:01:51 +0100
In-Reply-To: <A03FFB626FA02D4A9C68DBA5B228AF1E0958A7@gtmentos.telogy.design.ti.com>
References: <A03FFB626FA02D4A9C68DBA5B228AF1E0958A7@gtmentos.telogy.design.ti.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <A2D8CB68-8A04-11D8-9867-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
Cc: paulej@packetizer.com, Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>, Tim Melanchuk <timm@convedia.com>, magnus.westerlund@ericsson.com, avt@ietf.org
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] How is SDP a=fmtp used for RFC 2198?
Date: Fri, 09 Apr 2004 10:02:32 +0100
To: "Mundra, Satish" <smundra@telogy.com>
X-Mailer: Apple Mail (2.613)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

On 8 Apr 2004, at 22:32, Mundra, Satish wrote:
> Does this mean that if one wants to provide redundancy for different
> encoding methods on "m=" line, one can not do so using a single RED PT?

Correct. The "a=fmtp:" lines tell the sender how to encode particular 
data.

> See example below where redundancy is desired for both 97 and 98.
>
> m=audio 5678 RTP/AVP 0 97 98 99 100
> a=rtpmap:97 telephone-event/8000
> a=rtpmap:98 t140/8000
> a=rtpmap:99 red/8000
> a=rtpmap:100 red/8000
> a=fmtp:99 97/97/97/97/97
> a=fmtp:100 98/98/98

Sending this much redundancy is excessive, but the example is 
syntactically correct.

-- 
Colin Perkins
http://csperkins.org/


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt