RE: [Sip-implementors] rfc3261 & rfc2543 compatibility

ranjit.avasarala Mon, 12 Jan 2004 04:29:50 -0800

Title: Message

Hi Vijay

As per RFC 2543, Via header is not part of matching mechanism. Actually RFC 2543 compliant SIP entities must incorporate this feature as RFC 3261 bseletes RFC 2543.

Ranjit
Ph: 8520408/16 extn: 2173

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vijay Kamath (WT01 - TELECOM & INTER-NETWORKING SOLUTIONS)
Sent: Monday, January 12, 2004 10:41 AM
To: [EMAIL PROTECTED]
Subject: [Sip-implementors] rfc3261 & rfc2543 compatibility

Hi,

I need a clarification regarding matching CANCEL requests to INVITE transaction wrt 3261 & 2543.

According to rfc3261, sec 17.2.3 :-

    a request is matched to a transaction
    if the Request-URI, To tag, From tag, Call-ID, CSeq (including the
    method), and top Via header field match those of the request that
    created the transaction. Matching is done based on the matching rules defined for each of those header fields.

    When     a non-INVITE request matches an existing transaction, it is a retransmission of
    the request that created that transaction.

But rfc2543 says, sec 4.2.5

    The CANCEL request cancels a pending request with the same Call-ID,
    To, From and CSeq (sequence number only) header field values, but
    does not affect a completed request.

The top via header is not part of the matching process. In fact, I did not find VIA as a part of transaction matching anywhere in rfc2543.

So my question is this - is VIA matching a part of the transaction matching process in rfc2543 ? If it is, could someone show me where in 2543 it says that ? And, if it isn't, isn't this a backward compatibility issue ??

Regards...Vijay
Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments.

Confidentiality Notice


The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately
and destroy all copies of this message and any attachments.

_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

RE: [Sip-implementors] rfc3261 & rfc2543 compatibility

Reply via email to