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

Hannes Tschofenig <hannes.tschofenig@gmx.net> Sun, 30 January 2011 11:36 UTC

Return-Path: <hannes.tschofenig@gmx.net>
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 178E53A693B for <sipcore@core3.amsl.com>; Sun, 30 Jan 2011 03:36:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 1qF88ituEm6S for <sipcore@core3.amsl.com>; Sun, 30 Jan 2011 03:36:46 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id D4B833A691D for <sipcore@ietf.org>; Sun, 30 Jan 2011 03:36:45 -0800 (PST)
Received: (qmail invoked by alias); 30 Jan 2011 11:39:54 -0000
Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.1.3]) [88.115.222.204] by mail.gmx.net (mp010) with SMTP; 30 Jan 2011 12:39:54 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX181PVIg8aw1SX1B2exs/CTkYmFD7o04m4sxe6H+gq WxC4MlYcX3/DYG
Message-ID: <4D454DFC.9050901@gmx.net>
Date: Sun, 30 Jan 2011 13:39:40 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
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>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A0585194427B044@ESESSCMS0356.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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: Sun, 30 Jan 2011 11:36:47 -0000

On 1/27/2011 3:55 PM, Christer Holmberg wrote:
> Eventhough I would be happy to see usage outside of IMS for the mechanism, I don't see why 3GPP people should have to try to invent such use-cases "by force".

Christer,

the challenge is to figure out whether there are more generic usage 
patterns that can be identified. The idea of developing these more 
generic features is that you could re-use them in different usage 
environments. Standardizing point-solutions is quite expensive and the 
results often do not see deployment.

Specifically, there is the question about how much standardization is 
necessary to get the basic level of interoperability to let those 
players in the application eco-system extend their software in a way 
that it works with others. In general, it is fair to say that 
standardizing each application has not been very successful.

Does that make sense?

Ciao
Hannes