Re: [Sip] Question on RFC3840/3841

Paul Kyzivat <pkyzivat@cisco.com> Wed, 09 January 2008 14:26 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 1JCbsh-0001Ih-1g; Wed, 09 Jan 2008 09:26:11 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JCbsf-0001Ic-GF for sip-confirm+ok@megatron.ietf.org; Wed, 09 Jan 2008 09:26:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCbsf-0001IU-6X for sip@ietf.org; Wed, 09 Jan 2008 09:26:09 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCbsd-0000Le-RW for sip@ietf.org; Wed, 09 Jan 2008 09:26:09 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 09 Jan 2008 09:26:07 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m09EQ7Lp001108; Wed, 9 Jan 2008 09:26:07 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m09EQ2pk007228; Wed, 9 Jan 2008 14:26:02 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 Jan 2008 09:25:45 -0500
Received: from [161.44.174.128] ([161.44.174.128]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 Jan 2008 09:25:44 -0500
Message-ID: <4784D96A.5010104@cisco.com>
Date: Wed, 09 Jan 2008 09:25:46 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Mahesh Anjanappa <mahesha@samsung.com>
Subject: Re: [Sip] Question on RFC3840/3841
References: <CA9998CD4A020D418654FCDEF4E707DF03F7A681@esealmw113.eemea.ericsson.se> <038901c852c3$d222b750$bd4a6c6b@sisodomain.com>
In-Reply-To: <038901c852c3$d222b750$bd4a6c6b@sisodomain.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jan 2008 14:25:44.0938 (UTC) FILETIME=[855D44A0:01C852CB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=562; t=1199888767; x=1200752767; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Sip]=20Question=20on=20RFC3840/3841 |Sender:=20 |To:=20Mahesh=20Anjanappa=20<mahesha@samsung.com>; bh=7h+fdhur1gPoPDfi1Wma91Sgv9+tDTpRFul9lJvjngk=; b=gBA9X4o3fIM9UJi8D7GvqwUhTl9CiARgkMmX2SqRS0qmh2gJsnr0WX4Uav wewxf4Rt/P2xQrJscLUz/SOGaT220HX1El7bViR1VeLJCjGS0pUo3Av8W8BD gqimpukQWr;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.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


Mahesh Anjanappa wrote:
> 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.

The rule forbidding multiple instances of a parameter applies to all 
headers, so it applies to Contact.  E.g. the following is illegal:

	Contact:sip:alice@atlanta.com;methods="INVITE";methods="CANCEL"

Paul


_______________________________________________
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