IETF Logo Mail Archive

Re: [sipcore] Feature-Caps: Feature indications in 18x and 200

Andrew Allen <aallen@rim.com> Thu, 03 November 2011 18:20 UTC

Return-Path: <aallen@rim.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B60C1F0C40 for <sipcore@ietfa.amsl.com>; Thu, 3 Nov 2011 11:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.319
X-Spam-Level:
X-Spam-Status: No, score=-5.319 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n5n4rGXX8+TK for <sipcore@ietfa.amsl.com>; Thu, 3 Nov 2011 11:20:53 -0700 (PDT)
Received: from mhs061cnc.rim.net (mhs061cnc.rim.net [208.65.73.35]) by ietfa.amsl.com (Postfix) with ESMTP id E955A1F0CA3 for <sipcore@ietf.org>; Thu, 3 Nov 2011 11:20:52 -0700 (PDT)
X-AuditID: 0a412830-b7b29ae000000f33-2b-4eb2db8360d3
Received: from XHT107CNC.rim.net (xht107cnc.rim.net [10.65.12.217]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mhs061cnc.rim.net (SBG) with SMTP id 7B.33.03891.38BD2BE4; Thu, 3 Nov 2011 18:20:52 +0000 (GMT)
Received: from XCT104ADS.rim.net (10.67.111.45) by XHT107CNC.rim.net (10.65.12.217) with Microsoft SMTP Server (TLS) id 8.3.159.2; Thu, 3 Nov 2011 14:20:52 -0400
Received: from XMB105ADS.rim.net ([fe80::c47b:e609:558:1b44]) by XCT104ADS.rim.net ([fe80::90f9:3b89:1d94:aa9b%22]) with mapi id 14.01.0289.001; Thu, 3 Nov 2011 13:20:50 -0500
From: Andrew Allen <aallen@rim.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "<sipcore@ietf.org>" <sipcore@ietf.org>
Thread-Topic: Feature-Caps: Feature indications in 18x and 200
Thread-Index: AcyaKaDr9sNrpIJ9RlKSWi2LDONmIgAK6xkQ
Date: Thu, 03 Nov 2011 18:20:50 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD23067A5B@XMB105ADS.rim.net>
References: <7F2072F1E0DE894DA4B517B93C6A05852235962788@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852235962788@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.110.254]
Content-Type: multipart/alternative; boundary="_000_BBF5DDFE515C3946BC18D733B20DAD23067A5BXMB105ADSrimnet_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNKsWRmVeSWpSXmKPExsXC5chzU7fl9iY/g9MHGS0uzDzMaPH1xyY2 ByaPX1+vsnksWfKTKYApqoHRJjEvL78ksSRVISW1ONlWySc1PTFHIaAosywxuVLBJbM4OScx Mze1SEkhM8VWyURJoSAnMTk1NzWvxFYpsaAgNS9FyY5LAQPYAJVl5imk5iXnp2TmpdsqeQb7 61pYmFrqGirZ6SKBhH/cGdOX97MVnGhmrHjZt5algfFVeRcjJ4eEgInEz5fXmCBsMYkL99az dTFycQgJ9DJJTPm0mRHCWcoo8fniNmYIZzOjxJW/D8Fa2ASUJZb/nsEIYosIJEos2/SLHcQW FrCVOPfxKBtE3E7i8qKZLBC2kcTiey/B6lkEVCSe3JwENIeDg1fATWLDxxSQsJBAuMSsXW1g 5ZwCERKb/h5kBbEZga77fmoN2FpmAXGJW0/mQ10tILFkz3lmCFtU4uXjf6wgIyUEFCVen66D KM+VmLj1I9g1vAKCEidnPmGBWCUtsePkGsYJjGKzkEydhaRlFpIWiLiOxILdn9ggbG2JZQtf M8PYZw48ZkIWX8DIvopRMDej2MDMMDkvWa8oM1cvL7VkEyM44WgY7GCcsFfrEKMAB6MSD2/e jU1+QqyJZcWVuYcYJTiYlUR43U8AhXhTEiurUovy44tKc1KLDzG6AsNtIrMUd3I+MBnmlcQb Gxjg5iiJ88pcyvATEkgHJr3s1NSC1CKYOUwcnFINjEwP7zRb6Ibp2U7e0WYd8qq+5brO36Qy JSGPB3t176e6SBnObwlbcTrtputU/dYQGXOm2q4/p7//eLXA+4TthascCxjnLX3SY5bywDC9 a+HyfVFl+ubyMybaad0wW1PweFblv2jtgsjHN3bXpr865prdssl20U7T1EiFtcsNP/h+bq9Y UrvRTYmlOCPRUIu5qDgRADWsW0VeAwAA
Subject: Re: [sipcore] Feature-Caps: Feature indications in 18x and 200
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 18:20:59 -0000

Agree

From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: Thursday, November 03, 2011 8:08 AM
To: <sipcore@ietf.org>
Subject: [sipcore] Feature-Caps: Feature indications in 18x and 200


Hi,

The Feature-Caps draft currently allows sending of feature indications in reliable 18x and 200 responses.

I've received an off-line question, asking whether the indicated features must be identical, if included both in 18x and 200 for the same request.

My suggestion would be that we take the same approach that we did for Info Packages.

Section 5.2.3 of RFC 6086 says:

                "As with SDP answers, the receiver can include the same Recv-Info
                 header field value in multiple responses (18x/2xx) for the same
                 INVITE/re-INVITE transaction, but the receiver MUST use the same
                 Recv-Info header field value (if included) in all responses for the
                 same transaction."

...so, for Feature-Caps it could say something like:

                "An entity can include the same Feature-Caps
                 header field value in multiple responses (18x/2xx) for the same
                 INVITE/re-INVITE transaction, but the entity MUST use the same
                 Feature-Caps header field value (if included) in all responses for the
                 same transaction."

Regards,

Christer




---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

v2.23.0 | Report a Bug | By Email