Re: [Sipping] Transcoding/Reconciling Device Capabilities

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Thu, 24 February 2005 04:24 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 XAA17586 for <sipping-web-archive@ietf.org>; Wed, 23 Feb 2005 23:24:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4Auw-0003Cq-QJ for sipping-web-archive@ietf.org; Wed, 23 Feb 2005 23:48:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3knJ-0006fJ-Qe; Tue, 22 Feb 2005 19:54:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3WMZ-0007dq-Sl for sipping@megatron.ietf.org; Tue, 22 Feb 2005 04:29:53 -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 EAA05306 for <sipping@ietf.org>; Tue, 22 Feb 2005 04:29:44 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3Wiq-0005v7-K2 for sipping@ietf.org; Tue, 22 Feb 2005 04:52:59 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120]) by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id j1M9TcO6028150 for <sipping@ietf.org>; Tue, 22 Feb 2005 10:29:38 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue, 22 Feb 2005 10:30:17 +0100
Received: from mail.lmf.ericsson.se (dossier.lmf.ericsson.se [131.160.11.13]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id FLYCHT20; Tue, 22 Feb 2005 10:33:07 +0100
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.37.196]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 7500F18A90; Tue, 22 Feb 2005 11:29:37 +0200 (EET)
Message-ID: <421AFBA8.5050000@ericsson.com>
Date: Tue, 22 Feb 2005 11:30:16 +0200
X-Sybari-Trust: 1f8fb62e b8ec86c7 6fd9df5c 00000139
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Roy, Radhika" <RoyR@saic-abingdon.com>
Subject: Re: [Sipping] Transcoding/Reconciling Device Capabilities
References: <37B2A14433611A4C93B9A22A082E8ED6D360D5@bh-exchange01.saic-abingdon.com>
In-Reply-To: <37B2A14433611A4C93B9A22A082E8ED6D360D5@bh-exchange01.saic-abingdon.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Feb 2005 09:30:17.0510 (UTC) FILETIME=[1ED72C60:01C518C1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit

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