Re: [splices] SIP INVOKE method v1

"Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com> Sat, 18 June 2011 13:23 UTC

Return-Path: <rifatyu@avaya.com>
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 B626B21F860C for <splices@ietfa.amsl.com>; Sat, 18 Jun 2011 06:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.13
X-Spam-Level:
X-Spam-Status: No, score=-3.13 tagged_above=-999 required=5 tests=[AWL=0.470, BAYES_00=-2.599, 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 6v6tMMGnp8yZ for <splices@ietfa.amsl.com>; Sat, 18 Jun 2011 06:23:55 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 835F221F8608 for <splices@ietf.org>; Sat, 18 Jun 2011 06:23:55 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvUAAJ+l/E3GmAcF/2dsb2JhbABSl1WPCneIc6NdApsBhioElluLIA
X-IronPort-AV: E=Sophos;i="4.65,385,1304308800"; d="scan'208";a="252035943"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 18 Jun 2011 09:23:53 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 18 Jun 2011 09:23:41 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.192]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Sat, 18 Jun 2011 09:23:52 -0400
From: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
To: "R.Jesske@telekom.de" <R.Jesske@telekom.de>, "Worley, Dale R (Dale)" <dworley@avaya.com>, "andrew.hutton@siemens-enterprise.com" <andrew.hutton@siemens-enterprise.com>, "pkyzivat@cisco.com" <pkyzivat@cisco.com>, "splices@ietf.org" <splices@ietf.org>
Date: Sat, 18 Jun 2011 09:23:52 -0400
Thread-Topic: [splices] SIP INVOKE method v1
Thread-Index: AcwnpwHyWdPZ0GtcQdet0Lc+UVQPIgCJvnyQADiYGNAAANdDQAABWEfrAAFc1lAAANTSAwBPvZmgADtjeYA=
Message-ID: <4CA2C4386DB56F4589D436E1C3C86F752230509C39@DC-US1MBEX4.global.avaya.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> <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADCD25EA@HE111648.emea1.cds.t-internal.com>
In-Reply-To: <580BEA5E3B99744AB1F5BFF5E9A3C67D08ADCD25EA@HE111648.emea1.cds.t-internal.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
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: Sat, 18 Jun 2011 13:23:56 -0000

Hi Roland,

I browsed through the CSTA documents. This seems to go way beyond what we had in mind for the actions with the INVOKE method.
I will shortly send a separate email to start a discussion around the scope of the actions with the INVOKE method.

Regards,
 Rifaat


> -----Original Message-----
> From: R.Jesske@telekom.de [mailto:R.Jesske@telekom.de]
> Sent: Thursday, June 16, 2011 4:51 AM
> To: Worley, Dale R (Dale); andrew.hutton@siemens-enterprise.com; Shekh-Yusef,
> Rifaat (Rifaat); pkyzivat@cisco.com; splices@ietf.org
> Subject: AW: [splices] SIP INVOKE method v1
> 
> 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
> >