From: Alan Johnston <[EMAIL PROTECTED]> The draft mentions a server mode of operation, where UAs do not need to publish normal dialog state information since the server (a call stateful proxy or B2BUA) already knows all the dialog information.
I haven't read the recent drafts, though I saw the presentation at IETF 73. From that, it appears to me that the only functional difference is that in server mode, the UAs need not send the PUBLISH requests. Of course, we could allow the server to respond 200 to the PUBLISHes but otherwise ignore them, but that seems a waste of network bandwidth. It seems that we want a way for the server to signal to the UAs to not bother sending the PUBLISHes. A simple way for the server to communicate this is to reject the PUBLISHes with an appropriate error code, giving a Retry-After header telling how long the UA should suppress PUBLISHes (for that AOR). (I suppose to allow changing modes of operation, we should specify that if the phone is restarted or reconfigured, it should resume PUBLISHes.) Dale _______________________________________________ BLISS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bliss
