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

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 03 November 2011 13:08 UTC

Return-Path: <christer.holmberg@ericsson.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 831BB11E811F for <sipcore@ietfa.amsl.com>; Thu, 3 Nov 2011 06:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.306
X-Spam-Level:
X-Spam-Status: No, score=-6.306 tagged_above=-999 required=5 tests=[AWL=0.292, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 W-KPuMFn+jTQ for <sipcore@ietfa.amsl.com>; Thu, 3 Nov 2011 06:08:11 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 8426711E8110 for <sipcore@ietf.org>; Thu, 3 Nov 2011 06:08:10 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-7d-4eb292399a9c
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 5A.AA.13753.93292BE4; Thu, 3 Nov 2011 14:08:09 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.57]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Thu, 3 Nov 2011 14:08:08 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "<sipcore@ietf.org>" <sipcore@ietf.org>
Date: Thu, 03 Nov 2011 14:08:07 +0100
Thread-Topic: Feature-Caps: Feature indications in 18x and 200
Thread-Index: AcyaKaDr9sNrpIJ9RlKSWi2LDONmIg==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852235962788@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7F2072F1E0DE894DA4B517B93C6A05852235962788ESESSCMS0356e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [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 13:08:11 -0000

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