On Mon, Oct 27, 2008 at 3:51 PM, Jonathan Rosenberg <[EMAIL PROTECTED]> wrote: > As a follow up from Dublin, I worked with a colleague of mine to put > together a brief document which describes REST a bit and presents some > examples of how it can be used for the kinds of configuration problems we > have in ACH. The draft is here: > > http://www.ietf.org/internet-drafts/draft-griffin-bliss-rest-00.txt > > comments welcome.
Jonathan, The biggest issue with using REST is for notifications of changes to resources in a scalable way that works behind NAT. There are a number of choices: HTTP polling (perhaps COMET), XMPP, or in the case of BLISS, a SIP event package. However, this is a far more generic problem than just this domain - think RSS and twitter, and the huge amount of resource wasted every day from polling over HTTP for changes - although none the less something i'm interested in helping solve. So while i've not explicitly tackled the notification part of it yet, I have documented an initial framework that can be used for providing simple configuration/data API services in a RESTful manner: http://dev.voip.co.uk/~theo/ietf/draft-zourzouvillys-bliss-rest-for-sip-00.txt The idea is that "profiles" then sit on top of this framework running within the network, e.g: - ACH configuration - Phone book - Recent/missed calls - Voicemail access/configuration I'd also appreciate any comments! Kind regards, ~ Theo -- Theo Zourzouvillys Chief Technical Officer VoIP.co.uk - Commerce House, Telford Road, Bicester, OX26 4LD Tel: +44 1908 764 196 _______________________________________________ BLISS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bliss
