Re: CANCEL with/without 1xx To tag

Hi Del,

You are right as per section 9.1 recommendation the To
Header should be
be identical to initial INVITE. This can also be seen in
example section
of RFC-3665 Page 70

Section 12.2.1.1 recommendation in my opinion is applicable
for all
other requests with in a dialog ( early/confirmed ).

Regards,

Indresh K Singh

-----Original Message-----
From: sip-implementors-bouncescs.columbia.edu
[mailto:sip-implementors-bouncescs.columbia.edu] On Behalf
Of Del
Stevens
Sent: Monday, April 02, 2007 10:02 AM
To: sip-implementorscs.columbia.edu
Subject: [Sip-implementors] CANCEL with/without 1xx To tag

I have not seen anywhere confirmation one way or another on
this topic.


F1 A ----- INVITE -------> B
F2 A <----- 183 ------------ B
F3 A ----- CANCEL ----> B

F1 contains From tag.
F2 contains From tag and To tag

The question is: Is the F3 CANCEL required to send both From
and To
tags?

RFC 3261 Section 9.1 states...

The following procedures are used to construct a CANCEL
request. The
Request-URI, Call-ID, To, the numeric part of CSeq, and From
header
fields in the CANCEL request MUST be identical to those in
the
request being cancelled, including tags. 
Thanks.

Del Stevens
CopperCom
<www.coppercom.com>


_______________________________________________
Sip-implementors mailing list
Sip-implementorscs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors

_______________________________________________
Sip-implementors mailing list
Sip-implementorscs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors