Re: [splices] SIP INVOKE method v1

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
> >