Re: [Sip] Question on RFC3840/3841

Mahesh Anjanappa <mahesha@samsung.com> Wed, 09 January 2008 13:28 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCayR-0007aK-F2; Wed, 09 Jan 2008 08:28:03 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JCayP-0007Zq-Om for sip-confirm+ok@megatron.ietf.org; Wed, 09 Jan 2008 08:28:01 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCayP-0007Zb-Dj for sip@ietf.org; Wed, 09 Jan 2008 08:28:01 -0500
Received: from [203.254.224.24] (helo=mailout1.samsung.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCayO-0001hU-Te for sip@ietf.org; Wed, 09 Jan 2008 08:28:01 -0500
Received: from epmmp2 (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0JUD00HXFPEID5@mailout1.samsung.com> for sip@ietf.org; Wed, 09 Jan 2008 22:27:54 +0900 (KST)
Received: from mahesha ([107.108.74.189]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0JUD00FMLPEH2C@mmp2.samsung.com> for sip@ietf.org; Wed, 09 Jan 2008 22:27:54 +0900 (KST)
Date: Wed, 09 Jan 2008 19:00:36 +0530
From: Mahesh Anjanappa <mahesha@samsung.com>
Subject: Re: [Sip] Question on RFC3840/3841
To: Christer Holmberg <christer.holmberg@ericsson.com>, sip@ietf.org
Message-id: <038901c852c3$d222b750$bd4a6c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; reply-type=original; charset=iso-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <CA9998CD4A020D418654FCDEF4E707DF03F7A681@esealmw113.eemea.ericsson.se>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: Paul Kyzivat <pkyzivat@cisco.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

hi
That is my understanding as well. But if that is the case then it should 
apply to Contact header as well
when describing Capabilities using Feature parameters in Contact Header.
But i'm not sure if it applies the same way. I had posted this question long 
ago but didnt get any comments on it.

regards
Mahesh

----- Original Message ----- 
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <sip@ietf.org>
Cc: "Paul Kyzivat" <pkyzivat@cisco.com>
Sent: Wednesday, January 09, 2008 3:54 PM
Subject: [Sip] Question on RFC3840/3841



Hi,


Chapter 9 of RFC3840 says:

"There are additional constraints on the usage of feature-param that
cannot be represented in a BNF. There MUST only be one instance of any
feature tag in feature-param."


Chapter 10 of RFC3840 says:

"Furthermore, there can only be one instance of any feature tag in
feature-param."



So, this means that the following is NOT allowed:

Accept-Contact: *;myTag,myTag


However, since an Accept-Contact header can contain multiple ac-values,
each with its own sets of ac-parameters (including feature-params), the
following should be allowed:

Accept-Contact: *;myTag, *;myTag

...or:

Accept-Contact: *;myTag
Accept-Contact: *;myTag


Correct?


Regards,

Christer





_______________________________________________
Sip mailing list  https://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 



_______________________________________________
Sip mailing list  https://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