This open issue relates to the Request-URI used by UAs to publish dialog
event information to the Appearance Agent which acts as a state agent
and event state compositor for the dialog package for the AOR.
Currently, the draft says the Request-URI must be provisioned or
constructed by some convention (e.g. sip:[EMAIL PROTECTED]).
Comments in the room were strongly in favor of instead just using the
shared appearance AOR. This simplifies operations and does not require
any provisioning.
One consequence of this, pointed out by Dale Worley, is that the
Appearance Agent must be prepared to handle all SUBSCRIBEs and PUBLISHes
for the dialog events for this AOR, not just the ones used for
implementing shared appearances. Since the Appearance Agent is
essentially just a state agent that also inserts additional information
about appearances, this should not be a problem. We need to give this a
little more thought to make sure this is reasonable and does not cause
problems for proxy routing logic.
In addition, the draft needs to have some text clearly describing this
and Dale has volunteered to submit some.
Thanks,
Alan
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
