[SIP] Comment on draft-moyer-sip-appliances-framework-00.txt

[Henning Schulzrinne]

I don't see this as RPC in the classical sense. There are two aspects:

- action (MESSAGE) to affect lightbulb state;'

- events to obtain lightbulb state.

Thus, this is very similar to sending text (chat) messages and
subscribing to user status changes (events). Particularly in the event
case, the usual SIP advantages apply, including that the watcher may be
mobile (Speaking from personal plumbing accident experience, I want to
be notified when the home temperature drops below threshold regardless
of my location).

There are some nice secondary benefits to this: existing SIP message and
notification tools can be trivially extended to handle this. I can put
my washer in my address book and be notified when the wash is ready.

Also, existing tools such as sip-cgi and CPL are quite useful for this
space.

Since this doesn't require any SIP extensions, it seems (hopefully)
harmless.

Ben Campbell wrote:
> 
> I have a general comment on the "Networked Appliances" draft.
> 
> It seems to me that SIP is not an appropriate protocol for this purpose. It
> falls into the category of using SIP for an RPC mechanism. It is not clear
> to me how the primary features that distinguish SIP from something like HTTP
> (finding location, mobility, etc) are needed for a networked appliance
> protocol.
> 
> It is entirely possible I am missing something here. If so, please enlighten
> me.
> 
> Thanks!
> 
> Ben Campbell
> dynamicsoft
> 
> _______________________________________________
> SIP mailing list
> SIP@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/sip