Comments inline... Thanks & Regards, Nataraju A.B.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fortinsky Michael Sent: Tuesday, November 08, 2005 6:34 PM To: [email protected] Subject: [Sip-implementors] Clarification relating to entity-tags and PUBLISH Can someone please clarify the following sentence in RFC3903 relating to entity-tags: >From section 6 (Processing PUBLISH Requests), point #6 (on page 13): The response MUST also contain a SIP-ETag header field that contains a single entity-tag identifying the publication. The ESC MUST generate a new entity-tag for each successful publication, replacing any previous entity-tag associated with that event state. Based on the above, which of the following is correct: (1) The ESC creates a new entity-tag for EVERY successful PUBLISH (including refreshes) [ABN] YES... (2) The ESC creates a new entity-tag only for successful publications of event state (which is defined as initial and modify PUBLISH operations only, but not refreshes because referesh operations do not contain event state in the PUBLISH message and do not change event state) [ABN] No... [ABN] for every successful response for PUBLISH, ESC generates a new entity-tag. The EPA will overwrite the earlier tag with this new one upon every successful response to PUBLISH request.....(initial, refresh and modify publications....) Thanks in advance. Mike [EMAIL PROTECTED] _______________________________________________ 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
