Hi Arun, > -----Original Message----- > From: ext Arun Kumar [mailto:[EMAIL PROTECTED] > Sent: 06 October, 2003 20:43 > To: [EMAIL PROTECTED] > Subject: [Sip-implementors] Scope of the ETags/If-Match in PUBLISH > > > 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 ?
These won't work, since the PUBLISH request doesn't create a dialog. There is no requirement that the Call-ID (or the from-tag) stay the same in subsequent updates from the same PUA. > 2) Also each PUBLISH transaction from the same Presentity keeps > changing the from/to tags. Why is that so ? See above. The requests are not related in the sense of a SIP dialog. > 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. This was discussed in the SIMPLE WG some time ago, and there the conclusion was that a PUBLISH should *not* create a dialog. I didn't immediately find the corresponding thread in the SIMPLE email archives, but maybe someone who remembers these discussions better could point them out. Cheers, Aki > > Thanks in advance, > Arun > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
