Hi Folks, I'm trying to use PUBLISH method to present the config changes (updated by the SIP endpoints) to Config Agent (PA) which'd inturn update/notify the storage servers and provisioning server databases (which acts as watchers) with this new config updates.
Going through the sip-publish draft "draft-ietf-sip-publish-00.txt" I have the following questions.
1) What is the intention and scope of the Entity Tags (ETags) header in the PUBLISH method ? I understand the ETags/If-Match enables the PresenceAgent (PA) to identify the soft-state changes in subsequent updates from the same Presentity (PUA), but why would the PA need to generate this token when it could've used the from-tag/to-tag and callID to uniquely identify it ?
2) Also each PUBLISH transaction from the same Presentity keeps changing the from/to tags. Why is that so ?
3) The section 5 of the draft mentions that the PUBLISH request does not establish a dialog. But isn't it doing the same with these ETags/If-Match headers to update the event states within the same publication. I dont understand why the publication is not referred to as dialog.
Thanks in advance, Arun
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
