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

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 27 January 2011 13:52 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 CD72D3A6826 for <sipcore@core3.amsl.com>; Thu, 27 Jan 2011 05:52:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.465
X-Spam-Level:
X-Spam-Status: No, score=-6.465 tagged_above=-999 required=5 tests=[AWL=0.134, 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 fEj5Eu+iMHDU for <sipcore@core3.amsl.com>; Thu, 27 Jan 2011 05:52:27 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id A5C883A6803 for <sipcore@ietf.org>; Thu, 27 Jan 2011 05:52:26 -0800 (PST)
X-AuditID: c1b4fb39-b7cfbae000005c8e-78-4d41794f44ed
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id F6.B1.23694.F49714D4; Thu, 27 Jan 2011 14:55:28 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.59]) by esessmw0247.eemea.ericsson.se ([10.2.3.116]) with mapi; Thu, 27 Jan 2011 14:55:26 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Adam Roach <adam@nostrum.com>
Date: Thu, 27 Jan 2011 14:55:25 +0100
Thread-Topic: [sipcore] Draft new version: draft-holmberg-sipcore-proxy-feature
Thread-Index: Acu8xZUNBn4ESCXXRAm4BnYzPds59gBTZHMw
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585194427B044@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>
In-Reply-To: <4D3F2365.2070504@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 13:52:28 -0000

Hi,

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". 

I think there could be usages for SIP-PBXs, but I don't have any specific requirement/use-case to put on the table.

Regarding the WG and IESG, we have specified mechanisms for 3GPP before, e.g based on RFC 4083, and my understanding is that there is some kind of agreement between 3GPP and IETF. I do realize that we are not talking about a P- header in this case, but that should not change the fundamental agreement.

But, if you now are saying that, unless there is a non-IMS use-case, IETF (or, at least SIPCORE) is no more going to accept doing any work for 3GPP, I really think 3GPP should be informed about that.

BTW, there is an *I* in IMS also :)

Regards,

Christer

 

> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com] 
> Sent: 25. tammikuuta 2011 21:24
> To: Christer Holmberg
> Cc: Paul Kyzivat; sipcore@ietf.org
> Subject: Re: [sipcore] Draft new version: 
> draft-holmberg-sipcore-proxy-feature
> 
> [as individual]
> 
> On 1/25/11 10:33, Jan 25, Christer Holmberg wrote:
> > I'll try to put something together.
> > But, just for my understanding: what happens if there are 
> no non-IMS use cases?
> 
> Then we need to try to figure out whether the inapplicability 
> of the problem is due to the fact that it is being stated in 
> overly-narrow terms (i.e., is there a more general problem 
> here that does have applicability to the Internet?), or 
> whether it is due to the fact that it only arises because of 
> a specific architecture.
> 
> If it's the first case, we'll probably need to generalize the 
> problem to include the Internet (you know, the "I" in 
> "IETF"). Then, you'll have a much easier time getting the WG 
> to adopt it and the IESG to approve it.
> 
> If the problem only exists because of certain walled-garden 
> architectures, then things get trickier -- both in the WG and 
> in the IESG.
> 
> /a
>