Re: [splices] SIP INVOKE method v1

<R.Jesske@telekom.de> Thu, 16 June 2011 08:52 UTC

Return-Path: <R.Jesske@telekom.de>
X-Original-To: splices@ietfa.amsl.com
Delivered-To: splices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB99211E818F for <splices@ietfa.amsl.com>; Thu, 16 Jun 2011 01:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QnmXxHE8MwwT for <splices@ietfa.amsl.com>; Thu, 16 Jun 2011 01:52:10 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id 6637611E8184 for <splices@ietf.org>; Thu, 16 Jun 2011 01:52:09 -0700 (PDT)
Received: from he111631.emea1.cds.t-internal.com ([10.134.93.23]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 16 Jun 2011 10:50:51 +0200
Received: from HE111648.emea1.cds.t-internal.com ([169.254.5.233]) by HE111631.emea1.cds.t-internal.com ([::1]) with mapi; Thu, 16 Jun 2011 10:50:51 +0200
From: <R.Jesske@telekom.de>
To: <dworley@avaya.com>, <andrew.hutton@siemens-enterprise.com>, <rifatyu@avaya.com>, <pkyzivat@cisco.com>, <splices@ietf.org>
Date: Thu, 16 Jun 2011 10:50:50 +0200
Thread-Topic: [splices] SIP INVOKE method v1
Thread-Index: AcwnpwHyWdPZ0GtcQdet0Lc+UVQPIgCJvnyQADiYGNAAANdDQAABWEfrAAFc1lAAANTSAwBPvZmg
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADCD25EA@HE111648.emea1.cds.t-internal.com>
References: <6369CB70BFD88942B9705AC1E639A33822CD81384C@DC-US1MBEX4.global.avaya.com> <4DF27461.8060204@cisco.com> <101C6067BEC68246B0C3F6843BCCC1E30C22977E6A@MCHP058A.global-ad.net> <6369CB70BFD88942B9705AC1E639A33822CDA812C4@DC-US1MBEX4.global.avaya.com>, <101C6067BEC68246B0C3F6843BCCC1E30C229785C2@MCHP058A.global-ad.net> <CD5674C3CD99574EBA7432465FC13C1B222907E9D3@DC-US1MBEX4.global.avaya.com>, <101C6067BEC68246B0C3F6843BCCC1E30C229785F5@MCHP058A.global-ad.net> <CD5674C3CD99574EBA7432465FC13C1B222907E9D7@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222907E9D7@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [splices] SIP INVOKE method v1
X-BeenThere: splices@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Loosely-coupled SIP Devices \(splices\) working group discussion list" <splices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/splices>, <mailto:splices-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/splices>
List-Post: <mailto:splices@ietf.org>
List-Help: <mailto:splices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/splices>, <mailto:splices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2011 08:52:16 -0000

Hi,
now I'm puzzled about the scope?

Is the scope of INVOKE to realise the Computer Supported Telecommunications Applications (CSTA)?

Best Regards
Roland




> -----Urspr√ľngliche Nachricht-----
> Von: splices-bounces@ietf.org
> [mailto:splices-bounces@ietf.org] Im Auftrag von Worley, Dale R (Dale)
> Gesendet: Dienstag, 14. Juni 2011 20:36
> An: Hutton, Andrew; Shekh-Yusef, Rifaat (Rifaat); Paul
> Kyzivat; splices@ietf.org
> Betreff: Re: [splices] SIP INVOKE method v1
>
> ________________________________________
> From: Hutton, Andrew [andrew.hutton@siemens-enterprise.com]
>
> I think the problem is that we don't have any specified
> requirements so we don't know what the boundaries are.
>
> What has been specified so far already looks like it is
> trying to do CTI type things and for that we know the list of
> possible services is endless. The most relevant standards
> would probably be ECMA-269 and ECMA-323
> (http://www.ecma-international.org/publications/standards/Ecma
> -323.htm) if you want to see the XML for this.
>
> I don't see how it is really possibly to limit this to a
> small set of actions as once the mechanism is implemented
> there will always be requirements to add more actions.
> ________________________________________
>
> Thanks for those references!
>
> Yes, there is a real scope-creep problem.  Looking at
> ECMA-323, I see 45 "Call control services and events", and
> that is not the majority of the defined operations.
>
> One possibility would be to define INVOKE as a carrier for
> ECMA-323 operations.  But even then, a lot of care needs to
> be taken to see how to embed the dataflow model of ECMA-323
> into the SIP request/response structure.  If we define our
> own CTI set, we have to create our own dataflow model.
>
> Dale
> _______________________________________________
> splices mailing list
> splices@ietf.org
> https://www.ietf.org/mailman/listinfo/splices
>