Re: [AVT] How is SDP a=fmtp used for RFC 2198?
Tim Melanchuk <timm@convedia.com> Fri, 02 April 2004 21:37 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 QAA02280 for <avt-archive@odin.ietf.org>; Fri, 2 Apr 2004 16:37:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9WLr-00065W-QO for avt-archive@odin.ietf.org; Fri, 02 Apr 2004 16:37:25 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i32LbNC4023377 for avt-archive@odin.ietf.org; Fri, 2 Apr 2004 16:37:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9WLd-0005nd-G6; Fri, 02 Apr 2004 16:37:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9Th5-0005t4-NS for avt@optimus.ietf.org; Fri, 02 Apr 2004 13:47:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22641 for <avt@ietf.org>; Fri, 2 Apr 2004 13:47:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B9Th3-0004NP-00 for avt@ietf.org; Fri, 02 Apr 2004 13:47:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B9TgB-0004Fx-00 for avt@ietf.org; Fri, 02 Apr 2004 13:46:11 -0500
Received: from cerbrus.convedia.com ([216.129.93.50]) by ietf-mx with esmtp (Exim 4.12) id 1B9TfX-00045H-00 for avt@ietf.org; Fri, 02 Apr 2004 13:45:32 -0500
Received: from ladon.convedia.com (ladon [192.168.208.15]) by cerbrus.convedia.com (8.12.9/8.12.9) with ESMTP id i32IYMAL025903; Fri, 2 Apr 2004 10:34:22 -0800 (PST)
Received: from convedia.com (dhcp-211.convedia.com [192.168.208.211]) by ladon.convedia.com (8.12.9/8.12.9) with ESMTP id i32IisXS005077; Fri, 2 Apr 2004 10:44:55 -0800 (PST)
Message-ID: <406DB4B7.2070909@convedia.com>
Date: Fri, 02 Apr 2004 10:45:11 -0800
From: Tim Melanchuk <timm@convedia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
CC: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>, magnus.westerlund@ericsson.com, paulej@packetizer.com, avt@ietf.org
Subject: Re: [AVT] How is SDP a=fmtp used for RFC 2198?
References: <20040329135920.088a0720.csp@csperkins.org> <BHEHLFPKIPMLPFNFAHJKCEICDPAA.gunnar.hellstrom@omnitor.se> <20040331163154.38cf8d5d.csp@csperkins.org>
In-Reply-To: <20040331163154.38cf8d5d.csp@csperkins.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
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=none 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
to clarify with respect to using rfc2198 redundancy with rfc2833 telephone events, the sdp for the example on page 10 of rfc2833, which shows 3 events in one packet, would have had: a=rtpmap:96 red/8000 a=rtpmap:97 telephone-event/8000 a=fmtp:96 97/97/97 as well, at most 3 telephone-events could occur in one packet. is this interpretation correct? thanks, timm Colin Perkins wrote: >> >>Therefore, I think, that I can specify a=fmtp: 100 98/98 and mean that >>PT 98 is used as primary, and PT 98 is used for any number of generations >>of secondary coded redundant data. No tertiary choice of coding is >>specified, meaning no third choice of coding. > > > No, this is not correct. The syntax "a=fmtp:100 98/98" means that payload > type 98 is used for the primary and secondary, and that there is no third > level of redundancy. > > _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Comments on draft-ietf-avt-rfc2793bis-03.txt Magnus Westerlund
- RE: [AVT] Comments on draft-ietf-avt-rfc2793bis-0… Gunnar Hellstrom
- [AVT] How is SDP a=fmtp used for RFC 2198? Magnus Westerlund
- RE: [AVT] How is SDP a=fmtp used for RFC 2198? Gunnar Hellstrom
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Magnus Westerlund
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Colin Perkins
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Colin Perkins
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Tim Melanchuk
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Colin Perkins
- RE: [AVT] How is SDP a=fmtp used for RFC 2198? Gunnar Hellstrom
- RE: [AVT] How is SDP a=fmtp used for RFC 2198? Gunnar Hellstrom
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Magnus Westerlund
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Randell Jesup
- RE: [AVT] -Bursty packet loss for text. - Was: Ho… Gunnar Hellstrom
- RE: [AVT] -Bursty packet loss for text. - Was: Ho… Alan Clark
- Re: [AVT] How is SDP a=fmtp used for RFC 2198? Colin Perkins