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

Colin Perkins <csp@csperkins.org> Sun, 11 April 2004 12:45 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 IAA22194 for <avt-archive@odin.ietf.org>; Sun, 11 Apr 2004 08:45:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCeKn-0006v2-WB for avt-archive@odin.ietf.org; Sun, 11 Apr 2004 08:45:15 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3BCjDXN026572 for avt-archive@odin.ietf.org; Sun, 11 Apr 2004 08:45:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCeKc-0006tt-J6; Sun, 11 Apr 2004 08:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCGNR-0000FZ-Ui for avt@optimus.ietf.org; Sat, 10 Apr 2004 07:10:35 -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 HAA02034 for <avt@ietf.org>; Sat, 10 Apr 2004 07:10:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BCGNK-0003iu-00 for avt@ietf.org; Sat, 10 Apr 2004 07:10:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BCGM6-0003Rp-00 for avt@ietf.org; Sat, 10 Apr 2004 07:08:59 -0400
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163]) by ietf-mx with esmtp (Exim 4.12) id 1BCGKx-0003Gh-00 for avt@ietf.org; Sat, 10 Apr 2004 07:07:47 -0400
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:61617 helo=[192.168.0.5]) by dundee.dcs.gla.ac.uk with asmtp (TLSv1:RC4-SHA:128) (Exim 4.04) id 1BCGKE-0000od-00; Sat, 10 Apr 2004 12:07:02 +0100
In-Reply-To: <A03FFB626FA02D4A9C68DBA5B228AF1E0958A9@gtmentos.telogy.design.ti.com>
References: <A03FFB626FA02D4A9C68DBA5B228AF1E0958A9@gtmentos.telogy.design.ti.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <4CC70CD1-8ADF-11D8-9065-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: Sat, 10 Apr 2004 12:07:47 +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 9 Apr 2004, at 19:17, Mundra, Satish wrote:
...
> Another question:
> -----------------
>
> The redundancy header fields "F" and "Block PT" enable a receiver to 
> decode the RED packet, the level of redundancy, the PTs used for 
> primary/secondary (and tertiary etc.).
>
> For e.g.,
>
> m=audio 5678 RTP/AVP 0 97 98 99
> a=rtpmap:97 telephone-event/8000
> a=rtpmap:98 t140/8000
> a=rtpmap:99 red/8000
> a=fmtp:99 97/98
>
> Any comination of 97 or 98 as primary/secondary/tertiary as payload 
> for RED can be  decoded using the redundancy header fields. The 
> largest possible RED packet size (maximum redundancy levels allowed) 
> can not be determined from above.
>
> Is "estimating the additional bandwidth" the motivation for specifying 
> the maximum redundancy levels for each primary and hence separate RED 
> PTs ?

No, the receiver can decode the data without this information. The 
"a=fmtp:" lines tell the sender what is required for the session. See 
RFC 2198 section 5.

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


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