[Sip] Re: Question on RFC3840/3841

Paul Kyzivat <pkyzivat@cisco.com> Wed, 09 January 2008 14:21 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 1JCboO-00085I-Uf; Wed, 09 Jan 2008 09:21:44 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JCboO-00085C-Ab for sip-confirm+ok@megatron.ietf.org; Wed, 09 Jan 2008 09:21:44 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCboN-00082q-V9 for sip@ietf.org; Wed, 09 Jan 2008 09:21:44 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCboN-0003nV-Mi for sip@ietf.org; Wed, 09 Jan 2008 09:21:43 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 09 Jan 2008 09:21:43 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m09ELh26031361; Wed, 9 Jan 2008 09:21:43 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m09ELc6p002808; Wed, 9 Jan 2008 14:21:43 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 Jan 2008 09:21:39 -0500
Received: from [161.44.174.128] ([161.44.174.128]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 Jan 2008 09:21:39 -0500
Message-ID: <4784D875.7080508@cisco.com>
Date: Wed, 09 Jan 2008 09:21:41 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <CA9998CD4A020D418654FCDEF4E707DF03F7A681@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF03F7A681@esealmw113.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jan 2008 14:21:39.0369 (UTC) FILETIME=[F2FE6990:01C852CA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=973; t=1199888503; x=1200752503; 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=20Question=20on=20RFC3840/3841 |Sender:=20 |To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>; bh=QbLVTARsIx4h0PQJSB03szTo0EIym5JMC+Q/Tg9j6xg=; b=xqeGhf05CCK1gcbKe4FxftZg2qR0ythCSU4yAARaH01eIVNpwL168pvQmV Hn+IsurD6QIrZx/SYVwB3AHl5WUZFVyfcMMv2yS3ipSAt0aEyD3UOdI9VKRY U3srJCmd66;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: sip@ietf.org
Subject: [Sip] Re: Question on RFC3840/3841
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


Christer Holmberg wrote:
> 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

The above isn't syntactically correct. I presume you meant to write:

Accept-Contact: *;myTag;myTag

And yes, that isn't allowed.

> 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?

Yes.

	Thanks,
	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