Hi,
I'd like to start discussion on ACH configuration so that we can produce
something by IETF 74. By ACH configuration I mean a mechanism to enable setting
things such as to which number/URI the proxy should forward the incoming call
when the user is busy.
I've studied the case a bit and it appears to be that a good starting point
would be to use SIMPLE HTTP (call it REST if you like) mechanism to create,
read, write and delete a ruleset that looks awfully lot like CPL. In fact, I
think we should just take CPL as a starting point and perhaps just cut some
unnecessary features out of it. The main things to figure out would be just
where to locate the resource(s). There could be more than one of them if we
want to enable things like multiple profiles. I assume each profile would have
its own ruleset. And hey, why not borrow the URI structure from XCAP AUID, that
would save us from re-inventing that wheel. We could also borrow the
extensibility model from XCAP, i.e. using XML namespaces and discovering which
of them are supported by the server.
I believe this would be an approach where we could complete something in a
reasonable time. Is there any reason why that approach would not work?
I've also looked at other approaches, such as using REST by breaking the
dataset into a bunch of resources. One resource could be for instance the
target for call forwarding on busy. That approach would work easily for the
basic use cases too, but I believe it has two major shortcomings:
* It is hard to build rules that have multiple conditions (e.g. take UA
response ("busy")and time-of-day into account. That requires some kind of a
rule language, such as CPL, where you can combine and order conditions and
actions.
* The extensibility model is undefined.
Markus
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
