Hello, I had a query regarding Entity tag. Suppose a Client has sent a stop-publish request to stop it's publication, using Expires Header with value '0'. Presence server replies back with a 200 OK indicating that the publication has been successfully terminated. Should this 200 OK contain an Entity tag?
There is no section in PUBLISH RFC (3903) that explcitely mandates E-tag in such 200 OK. *Section 4.3: Refreshing Event State* *Like the 2xx response to an initial PUBLISH request, the 2xx response to a refresh PUBLISH request will contain a SIP-ETag header field with an entity-tag.* ** *Section 4.5: Removing Event State* *Note that removing event state is effectively a publication refresh suggesting an infinitesimal expiration interval.Consequently, the refreshed event state expires immediately after being refreshed.* Can we conclude from this that the remove(stop) response will also be constructed on the same lines as a refresh response (i.e, having an E-Tag) ?? But if we see other sections in the same RFC.. *Section 8.2: Client Usage* *"Each successful publication will get assigned an entity-tag which is then delivered to the EPA in the response to the PUBLISH request."* ** *Section 8.3: Server Usage* *"An entity-tag is generated and stored for each successful event state publication, and returned to the EPA in a 200 (OK) response."* It says that E-tags are generated for each successful publication, however when we send a stop publish request, we are actually deleting this Publication context, so ideally we don't need a new E-tag now at the Client side. Can anyone throw some light on this... Thanks, Pankaj _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
