Dan,
When you say, "RESTful interface to SIP" - what kind of functions do you
mean?
Do you mean, have a way to make first person calls with REST, as a
replacement for SIP? Or do you mean third party call control/CTI types
of things? Or do you mean presence? e.g., a RESTful method to fetch
someones presence state?
The piece BLISS is looking at, is RESTful configuration of feature
parameters. That one is a no-brainer for REST.
-Jonathan R.
Dan York wrote:
Sal,
On Oct 31, 2008, at 11:00 AM, Salvatore Loreto wrote:
I think that the intentions of both the draft is not to develop REST
interface for SIP,
but just to show how a service can be configured on a Server using REST.
DY> Ah... sorry, I guess I was reading more into it. (And admittedly
finding it an exciting idea.)
All what we need to define here is XML file format (if as I guess we
are going to use REST handling
state representations in XML format) for a service or a set of service
and showing how this XML document can be modified using REST (that is
what is showed in
the Theo draft).
So for this reason bliss seems, at least to me, the perfect wg where
define this stuff.
DY> Got it. Makes sense for that reason.
DY> Having said that, I would say that there *would* be value, IMHO, in
creating a standard RESTful interface to SIP that had broader
applicability.
Thanks,
Dan
--
Jonathan D. Rosenberg, Ph.D. 111 Wood Avenue South
Cisco Fellow Iselin, NJ 08830
Cisco, Voice Technology Group
[EMAIL PROTECTED]
http://www.jdrosen.net PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
