RE: [Sip] Open Issue #7: CANCEL for non-INVITE

> My proposal was that we should deprecate CANCEL for 
> non-INVITE. The benefit
> is not even quantifiable, at best, and the cost seems high. 
> Of course, for
> backwards compatibility, a server should not complain if it 
> gets a CANCEL
> for a non-invite, just respond 200 OK (or even 405 is OK) and 
> thats it. It
> should have responded to the request anyway. 

The proposal sounds good to me.

If the request was not important, just 
quit sending retries for the request and 
mark the delivery status as unknown/who-cares.

If the request was important, the UAC 
would have had to indefinitely continue 
to send the request or an alternative 
query to find out if the CANCEL actually 
worked.  

If the success or cancellation status of 
a request is deemed important enough, 
how about a new DISCARDORNOTIFY method 
to ensure that the request will be 
discarded if received or a notification 
sent if positively acknowledged? :)

_______________________________________________
Sip mailing list  http://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip