IETF Logo Mail Archive

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

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 27 January 2011 17:10 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 2579A28C13C for <sipcore@core3.amsl.com>; Thu, 27 Jan 2011 09:10:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.47
X-Spam-Level:
X-Spam-Status: No, score=-6.47 tagged_above=-999 required=5 tests=[AWL=0.129, 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 eG7ZRvRoItES for <sipcore@core3.amsl.com>; Thu, 27 Jan 2011 09:10:25 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 0F6EC28C125 for <sipcore@ietf.org>; Thu, 27 Jan 2011 09:10:24 -0800 (PST)
X-AuditID: c1b4fb39-b7cfbae000005c8e-84-4d41a7b7c312
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 92.F8.23694.7B7A14D4; Thu, 27 Jan 2011 18:13:28 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.59]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Thu, 27 Jan 2011 18:13:27 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Adam Roach <adam@nostrum.com>
Date: Thu, 27 Jan 2011 18:13:25 +0100
Thread-Topic: [sipcore] Draft new version: draft-holmberg-sipcore-proxy-feature
Thread-Index: Acu+RPrErK5doFYgS5eDC/63c4rqRgAACTbQ
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585194427B1CF@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> <4D41A072.9040202@nostrum.com> <7F2072F1E0DE894DA4B517B93C6A0585194427B1C9@ESESSCMS0356.eemea.ericsson.se> <4D41A6CA.1010609@nostrum.com>
In-Reply-To: <4D41A6CA.1010609@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>, "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 17:10:28 -0000

Hi, 

>>Having said that, if you think there is a better way of solving the 
>>use-cases in the draft, I am willing to hear about it.
> 
>Splendid. What are your requirements? Answer in internet-draft form, please.

I already indicated that I will do that.

What I am trying to figure out, based on the feedback I have got from you and Paul, is whether writing such a draft would be a waste of time, unless I can come up with non-IMS use-cases.

Regards,

Christer

v2.23.0 | Report a Bug | By Email