[AVT] question: mapping dynamic RTP formats using SDP
"Hager, Todd" <THH@dolby.com> Sat, 01 March 2003 01:17 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19327 for <avt-archive@odin.ietf.org>; Fri, 28 Feb 2003 20:17:58 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h211Qi610276 for avt-archive@odin.ietf.org; Fri, 28 Feb 2003 20:26:44 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h211QFp10259; Fri, 28 Feb 2003 20:26:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h211PDp10231 for <avt@optimus.ietf.org>; Fri, 28 Feb 2003 20:25:13 -0500
Received: from scandium.dolby.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA19317 for <avt@ietf.org>; Fri, 28 Feb 2003 20:15:55 -0500 (EST)
Received: from platinum.dolby.net ([172.16.33.28]) by 192.168.16.253 with In terScan Messaging Security Suite; Fri, 28 Feb 2003 17:17:54 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=_Boundary_wqxsIPIkxS4FRVvhHiUH"
Date: Fri, 28 Feb 2003 17:17:54 -0800
Message-ID: <5FCCC03CAF7C5C4C8E2F995E3D72E1334BBB5C@platinum.dolby.net>
X-MS-TNEF-Correlator: <5FCCC03CAF7C5C4C8E2F995E3D72E1334BBB5C@platinum.dolby .net>
Thread-Topic: question: mapping dynamic RTP formats using SDP
Thread-Index: AcLfkGJ0WEnGW1vPT/qmoBrk7l3evQ==
From: "Hager, Todd" <THH@dolby.com>
To: avt@ietf.org
Subject: [AVT] question: mapping dynamic RTP formats using SDP
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>
--- Begin Message ---Hi all, What is the best method to define a valid encoding name for a new encoding format? Regarding <draft-flaks-avt-rtp-ac3-03.txt>, I'm trying to determine the best method of choosing a value for the payload type for AC-3 in the RTP header. I am proceeding under the assumption that the best course is to randomly choose a value from the dynamic range (96-127) described in <RTP Profile for Audio and Video Conferences with Minimal Control.txt> (RFC 1890), and use SDP to somehow map this value to the AC-3 encoding type. I have questions regarding the SDP mapping process. Pages 21 and 22 in the SDP specification (RFC 2327) indicate the following mechanism to map a dynamic format ID : m=<media> <port>/<number of ports> <transport> <fmt list> and a=rtpmap:<payload type> <encoding name>/<clock rate>[/<encoding parameters>] Therefore, an SDP description ought to be able to incorporate the following two lines: m=audio 49232 RTP/AVP 98 a=rtpmap:98 <AC3_ENCODING_NAME>/48000 How does the AVT group suggest I define <AC3_ENCODING_NAME>? Should I submit a new Internet Draft describing a full profile specifically for this format, or can I simply use the AC-3 RTP Payload document itself as the vehicle that registers a valid AV Profile encoding name? Alternatively, though the current AC-3 RTP Payload draft document does not currrently define an AV RTP Profile encoding name, it does define a MIME type description for AC-3. The SDP spec allows MIME types to describe media encodings, but the wording of the SDP spec (page 22) implies that this is only intended to be used for non-RTP streams. Which is the most appropriate course of action: 1) Define a new RTP profile, 2) Use the AC-3 RTP payload document to define a valid encoding name for the AC-3 format, or 3) Use the defined MIME type to map a dynamic AV Profile payload type to AC-3? Thanks in advance, Todd Hager Dolby Laboratories--- End Message ---
This message (including any attachments) may contain confidential information intended for a specific individual and purpose. If you are not the intended recipient, delete this message. If you are not the intended recipient, disclosing, copying, distributing, or taking any action based on this message is strictly prohibited.
- [AVT] question: mapping dynamic RTP formats using… Hager, Todd
- Re: [AVT] question: mapping dynamic RTP formats u… Colin Perkins