As you say: A CANCEL request SHOULD NOT be sent to cancel a request other than INVITE.
So, there is no CANCEL for non-INVITE. (In other words, there is only CANCEL for INVITE) Since the above is true, the "10. Generate CANCELs" section can be ignored for non-INVITEs. Regards, Attila -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rockson Li (zhengyli) Sent: 21 August 2008 08:25 To: [email protected] Subject: [Sip-implementors] Does proxy need cancel forked non-INVITE req ? Hi folks, Suppose a proxy which forks OPTIONS to two endpoints, endpoint A responds with 200 promptly, endpoint B responds with 100. so does proxy need to send to CANCEL to endpoint B? from RFC3261, 16.7 Response Processing 10. Generate CANCELs If the forwarded response was a final response, the proxy MUST generate a CANCEL request for all pending client transactions associated with this response context. it looks proxy MUST do it. However, I wonder if it's really true. since sec 9.1 Client Behavior A CANCEL request SHOULD NOT be sent to cancel a request other than INVITE. so why proxy MUST cancel forked non-INVITE req here? thanks -Rockson _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
