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
--
Dan York, CISSP, Director of Emerging Communication Technology
Office of the CTO Voxeo Corporation [EMAIL PROTECTED]
Phone: +1-407-455-5859 Skype: danyork http://www.voxeo.com
Blogs: http://blogs.voxeo.com http://www.disruptivetelephony.com
Build voice applications based on open standards.
Find out how at http://www.voxeo.com/free
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
