Re: [sipcore] Draft new version: draft-holmberg-sipcore-proxy-feature

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 27 January 2011 16:12 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6AAA3A67D3 for <sipcore@core3.amsl.com>; Thu, 27 Jan 2011 08:12:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.468
X-Spam-Level:
X-Spam-Status: No, score=-6.468 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jjkAHbOctUqi for <sipcore@core3.amsl.com>; Thu, 27 Jan 2011 08:12:23 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 70B223A6917 for <sipcore@ietf.org>; Thu, 27 Jan 2011 08:12:22 -0800 (PST)
X-AuditID: c1b4fb39-b7cfbae000005c8e-97-4d419a1dc87a
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id F2.83.23694.D1A914D4; Thu, 27 Jan 2011 17:15:25 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.59]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Thu, 27 Jan 2011 17:15:25 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Adam Roach <adam@nostrum.com>
Date: Thu, 27 Jan 2011 17:15:23 +0100
Thread-Topic: [sipcore] Draft new version: draft-holmberg-sipcore-proxy-feature
Thread-Index: Acu+O5nBl5aHToRzQN6gM0EPa6zplAAAMMwA
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585194427B199@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A058502B84084@ESESSCMS0356.eemea.ericsson.se> <BDBFB6CE314EDF4CB80404CACAEFF5DE07C6C68C@XCH02DFW.rim.net>, <4D3A2C3D.10508@cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585194414F717@ESESSCMS0356.eemea.ericsson.se> <4D3EEC64.2080302@nostrum.com> <7F2072F1E0DE894DA4B517B93C6A05851944155A13@ESESSCMS0356.eemea.ericsson.se> <4D3F2365.2070504@nostrum.com> <7F2072F1E0DE894DA4B517B93C6A0585194427B044@ESESSCMS0356.eemea.ericsson.se> <4D419713.7030000@nostrum.com>
In-Reply-To: <4D419713.7030000@nostrum.com>
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==
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] Draft new version: draft-holmberg-sipcore-proxy-feature
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Jan 2011 16:12:23 -0000

Hi, 

>I'm pointing out, just as a participant, that you will have a 
>harder time drumming up interest for a niche mechanism than 
>you will for a general one.

I think a number of people have already shown interest for this.

>Another hurdle you're going to face is harmonizing your 
>proposal with RFC 5897. All three of your examples rely on 
>doing, just about as vigorously as possible, precisely what 
>RFC 5897 says not to do.

Feature tags indicate support of a capability. EVERY feature tag does that - even if inserted in a Contact header field by a UA - and the feature tag specification needs to define the meaning of that capability.

The important thing is that it cannot be assumed that other entities understand the meaning of the feature tag in order to progress a call (in such cases you will also need an option-tag, inserted in a Require/Proxy-Require header field).

Regards,

Christer