[sipcore] Feature-Caps: Feature indication in target refresh request

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 04 November 2011 13:12 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 3372321F8C12 for <sipcore@ietfa.amsl.com>; Fri, 4 Nov 2011 06:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.308
X-Spam-Level:
X-Spam-Status: No, score=-6.308 tagged_above=-999 required=5 tests=[AWL=0.291, BAYES_00=-2.599, 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 R2mVN5YALtvZ for <sipcore@ietfa.amsl.com>; Fri, 4 Nov 2011 06:12:50 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 5F33221F8BDC for <sipcore@ietf.org>; Fri, 4 Nov 2011 06:12:50 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-61-4eb3e4d1c74a
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 33.91.13753.1D4E3BE4; Fri, 4 Nov 2011 14:12:49 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.57]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Fri, 4 Nov 2011 14:12:49 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Date: Fri, 4 Nov 2011 14:12:48 +0100
Thread-Topic: Feature-Caps: Feature indication in target refresh request
Thread-Index: AQHMmvNsFpgV19D5R028+3xjTusUUA==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A058522357173B5@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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [sipcore] Feature-Caps: Feature indication in target refresh request
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: Fri, 04 Nov 2011 13:12:51 -0000

Hi,

It has been indicated that it would be useful tobe able to re-indicate supported features within a dialog, as part of a target refresh request.

Based on that, I suggest the following modified section 6.2 text:


"6.2. SIP Dialog

The Feature-Caps header field can be used within an initial SIP
request for a dialog, within a target refresh SIP request, and within 
any 18x or 2xx response associated with such requests. If a feature 
tag is inserted in a Feature-Caps header field of such request or such 
response, the feature associated with the feature tag MUST be 
supported for the dialog, until the next time the dialog target
is refreshed, or the dialog is terminated."


Regards,

Christer