RE: [Sipping] Transcoding/Reconciling Device Capabilities
"Roy, Radhika" <RoyR@saic-abingdon.com> Thu, 24 February 2005 03:07 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19523 for <sipping-web-archive@ietf.org>; Wed, 23 Feb 2005 22:07:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D49iX-0003Yj-Tk for sipping-web-archive@ietf.org; Wed, 23 Feb 2005 22:31:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3knt-0006uw-8H; Tue, 22 Feb 2005 19:55:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3aNL-0007w0-IV for sipping@megatron.ietf.org; Tue, 22 Feb 2005 08:46:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01077 for <sipping@ietf.org>; Tue, 22 Feb 2005 08:46:34 -0500 (EST)
Received: from mail.saic-abingdon.com ([12.167.146.25]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3ajX-0005SN-5e for sipping@ietf.org; Tue, 22 Feb 2005 09:09:51 -0500
Received: from no.name.available by mail.saic-abingdon.com via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with ESMTP; Tue, 22 Feb 2005 08:49:13 -0500
Received: from bh-exchange01.saic-abingdon.com ([172.17.10.225]) by bh-exchangefe.saic-abingdon.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 22 Feb 2005 08:50:12 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Subject: RE: [Sipping] Transcoding/Reconciling Device Capabilities
Date: Tue, 22 Feb 2005 08:47:36 -0500
Message-ID: <37B2A14433611A4C93B9A22A082E8ED6D403A5@bh-exchange01.saic-abingdon.com>
Thread-Topic: [Sipping] Transcoding/Reconciling Device Capabilities
Thread-Index: AcUYwY3/YPrnQVajRdyisrIvmNgacAAI4N6n
From: "Roy, Radhika" <RoyR@saic-abingdon.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
X-OriginalArrivalTime: 22 Feb 2005 13:50:12.0135 (UTC) FILETIME=[6DF61B70:01C518E5]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c
Cc: sipping <sipping@ietf.org>, Henning Schulzrinne <hgs@cs.columbia.edu>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2031541082=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7698d1420ecbbce1995432e99bb6d1a1
Hi, Gonzalo: You are right (it is Henning - sorry for the mistake). It is great that you will take of this in the future draft. Best regards, Radhika ________________________________ From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] Sent: Tue 2/22/2005 4:30 AM To: Roy, Radhika Cc: Henning Schulzrinne; sipping Subject: Re: [Sipping] Transcoding/Reconciling Device Capabilities Hi Roy, inline: Roy wrote: > Hi, Gonzalo and Henry: I guess you meant "Henning", right? > I find that the following drafts of yours have some similarities so far > transcoding is concerned. I find that Henning's draft addresses more > generic way including mobility. Henning's draft deals with transcoding by using the 3pcc model documented in the 3pcc transcoding draft. There isn't any inconsistency as far as I can see between both drafts. Of course, Henning's draft covers ground that is outside the scope of the transcoding work. > http://www.ietf.org/internet-drafts/draft-shacham-sipping-session-mobili > ty-00.txt > > http://standards.ericsson.net/gonzalo/papers/draft-ietf-sipping-transc-f > ramework-00.txt > > http://www.ietf.org/internet-drafts/draft-ietf-sipping-transc-3pcc-02.tx > t > > http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-tra > nsc-b2bua-01.txt > > Let me suggest that all transcoding drafts be extended to make them more > generic, as Henning has done in Section 6 of his draft, titling as > "Reconciling Device Capability Differences" and use codec differences, > TTS, STT, bandwidth differences, QoS parameter differences, etc. as > separate examples. > > Is this suggestion acceptable? The transcoding drafts already state that the mechanisms described there are general and can be used to invoke simple transcoders or more complicated media servers. From the Introduction of the transcoding framework: So, the invocation mechanisms described in this document are generally applicable to any type of incompatibility related to how the information that needs to be communicated is encoded. Furthermore, although this framework focuses on transcoding, the mechanisms described are applicable to media manipulation in general. It would be possible to use them, for example, to invoke a server that simply increased the volume of an audio stream. In any event, in future revisions of this document we will try to stress (even more) this point, as you suggest. Thanks for the comments, Gonzalo
_______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- RE: [Sipping] Transcoding/Reconciling Device Capa… Roy, Radhika
- RE: [Sipping] Transcoding/Reconciling Device Capa… Roy, Radhika
- Re: [Sipping] Transcoding/Reconciling Device Capa… Gonzalo Camarillo