Hi, I'm thinking about a custom usage of PUBLISH method. The idea is to send a 
PUBLISH with body and "Expires: 0" but no "SIP-If-Match" header, so it would 
generate a NOTIFY for current subscribers, but since "Expires" is 0 future 
subscriptions would not receive such notification (this is what I want to 
achieve).

Is it a legal usage of PUBLISH method? In RFC 3903 I read that "Expires: 0" is 
used, in conjunction with "SIP-If-Match" header, to terminate an existing 
publication:

-----------------------------------------------
   To request the immediate removal of event state, an EPA MUST create a
   PUBLISH request with an Expires value of "0", and set the SIP-If-
   Match header field to contain the entity-tag of the event state
   publication to be removed.

      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.

   Similar to an event state refresh, the removal of event state only
   affects the expiry of the event state.  Therefore, a PUBLISH request
   that removes event state MUST NOT contain a body.
-----------------------------------------------


In my case the PUBLISH has body and "Expires: 0" but no "SIP-If-Match" so I 
expect is a legal usage. Opinions? Thanks.


-- 
Iñaki Baz Castillo <[email protected]>

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to