Re: [splices] SIP INVOKE method

Hi Rifaat,

Overall this is clearly described and I can see the utility.

I agree with other comments that explicit subscriptions are evil.

If find the method name INVOKE very unfortunate - since my brain when
parsing the example actually skipped the INVOKE message thinking it was an
INVITE. Semantically this method is somewhat like HTTP POST - but I think
overloading that term might not be viewed favourably. Maybe ACTION?

Do you foresee having actions which accept parameters? For example there is
a special case of an action 'sendvm' that could be generalized to something
like 'redirect vm'. I could also see a case where terminate might wish to
specify the error code to be used to reject the call.

Will the gory details of what a UA must do for each action be something
which is added to the document?

Regards,

Peter Musgrave

On Tue, May 17, 2011 at 9:15 AM, Shekh-Yusef, Rifaat (Rifaat) <
rifatyu@avaya.com> wrote:

> Hi,
>
>
>
> As discussed in the last SPLICES WG meeting in Prague, the REFER method is
> overloaded and has limitations that prevents it from being the ideal method
> for action invocation.
>
> We have worked on the following new draft that defines a new SIP method to
> be used for invoking actions:
>
> https://datatracker.ietf.org/doc/draft-yusef-splices-invoke/
>
>
>
> We would appreciate it if people review the document and provide us with
> their feedback.
>
>
>
> Regards,
>
> Rifaat
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> splices mailing list
> splices@ietf.org
> https://www.ietf.org/mailman/listinfo/splices
>
>