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

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 27 January 2011 18:24 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 4EDF13A67BD for <sipcore@core3.amsl.com>; Thu, 27 Jan 2011 10:24:49 -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 sXA+SA8SkinC for <sipcore@core3.amsl.com>; Thu, 27 Jan 2011 10:24:45 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 491DB28C155 for <sipcore@ietf.org>; Thu, 27 Jan 2011 10:24:44 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-0d-4d41b9233c91
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 0A.79.13987.329B14D4; Thu, 27 Jan 2011 19:27:47 +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 19:27:47 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Date: Thu, 27 Jan 2011 19:27:46 +0100
Thread-Topic: [sipcore] Draft new version: draft-holmberg-sipcore-proxy-feature
Thread-Index: Acu+S6z+7IT2P/hITp6kkGSzkC1krwAAqXeI
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585194414F720@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> <580BEA5E3B99744AB1F5BFF5E9A3C67DFA9550FF@HE111648.emea1.cds.t-internal.com> <4D405B30.8020503@cisco.com> <580BEA5E3B99744AB1F5BFF5E9A3C67DFAAEA1E2@HE111648.emea1.cds.t-internal.com> <4D419056.8080502@nostrum.com> <4D4199EB.5050705@cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585194427B1AA@ESESSCMS0356.eemea.ericsson.se> <4D41AA37.1060009@cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585194427B1D3@ESESSCMS0356.eemea.ericsson.se>, <4D41B20C.5030506@cisco.com>
In-Reply-To: <4D41B20C.5030506@cisco.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>, "R.Jesske@telekom.de" <R.Jesske@telekom.de>
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 18:24:49 -0000

Hi,

In my opinion the big difference (a little simplified) from when we had the service-id discussion is the following:

- The service-id is used by the sender to REQUEST the receiver to do something. If the receiver doesn't do it (e.g. because it doesn't understand the service-id) the sender might not get the assumed result in the particular dialog.

- The feature tag is used by the sender to INFORM the receiver about a feature that it supports. It's up to the receiver to determine whether it wants to use that information for anything. And, if it doesn't (or, it doesn't even understand the meaning of the feature tag), nothing will go wrong in the particular dialog, because the sender didn't assume the receiver to do anything.

sip.instance is a very good example of informing. The sender doesn't really expect the receiver to do anything with the information (unless there is an associated option-tag), but the receiver MAY use it e.g. to later do a call transfer.
 
So, in my opinion, THAT is the separation we need to do, rather than arguing about terminology. 

(We know that people have changed "service" to "feature" in their drafts simply because of "political reasons", so I think it's really worthless trying to categorize)

Regards,

Christer






________________________________________
From: Paul Kyzivat [pkyzivat@cisco.com]
Sent: Thursday, January 27, 2011 7:57 PM
To: Christer Holmberg
Cc: Adam Roach; sipcore@ietf.org; R.Jesske@telekom.de
Subject: Re: [sipcore]  Draft   new     version:        draft-holmberg-sipcore-proxy-feature

On 1/27/2011 12:26 PM, Christer Holmberg wrote:
>
> Hi,
>
>> IMO the key differences are:
>>
>> - the definition must be publicly available
>> - capabilities/feature-tags should be orthogonal
>>
>> (And of course it is impossible to verify orthogonality
>> without the definitions being available.)
>
> As far as I know, all 3GPP specifications are publicly available.

I wasn't trying to imply that they are not, just putting a stake in the
ground generally.

The orthogonality also ties into the quote Adam cited. I had forgotten
exactly how that was stated. It goes further.

        Thanks,
        Paul