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

"DOLLY, MARTIN C (ATTSI)" <md3135@att.com> Thu, 27 January 2011 17:19 UTC

Return-Path: <md3135@att.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 6ABD73A681B for <sipcore@core3.amsl.com>; Thu, 27 Jan 2011 09:19:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.123
X-Spam-Level:
X-Spam-Status: No, score=-106.123 tagged_above=-999 required=5 tests=[AWL=0.476, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 MN7FKjiJ5SBI for <sipcore@core3.amsl.com>; Thu, 27 Jan 2011 09:19:41 -0800 (PST)
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.241.147]) by core3.amsl.com (Postfix) with ESMTP id 7763A3A67B3 for <sipcore@ietf.org>; Thu, 27 Jan 2011 09:19:41 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: md3135@att.com
X-Msg-Ref: server-10.tower-146.messagelabs.com!1296148962!24080388!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 6968 invoked from network); 27 Jan 2011 17:22:43 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-10.tower-146.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Jan 2011 17:22:43 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p0RHLnfG006976 for <sipcore@ietf.org>; Thu, 27 Jan 2011 12:21:49 -0500
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p0RHISwi003464 for <sipcore@ietf.org>; Thu, 27 Jan 2011 12:21:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 27 Jan 2011 12:20:20 -0500
Message-ID: <14C85D6CCBE92743AF33663BF5D24EBA08F56ABB@gaalpa1msgusr7e.ugd.att.com>
In-Reply-To: <4D419713.7030000@nostrum.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sipcore] Draft new version:draft-holmberg-sipcore-proxy-feature
Thread-Index: Acu+O67DYjwYaUD4Q5a3OOStZK/3TQACmegg
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>
From: "DOLLY, MARTIN C (ATTSI)" <md3135@att.com>
To: Adam Roach <adam@nostrum.com>, Christer Holmberg <christer.holmberg@ericsson.com>
Cc: 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 17:19:43 -0000

Adam,

Could you please consult with the AD and chairs on Christer's question?
It would be useful for 3GPP to understand the working relationship.

Regards,

Martin

-----Original Message-----
From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On
Behalf Of Adam Roach
Sent: Thursday, January 27, 2011 11:02 AM
To: Christer Holmberg
Cc: sipcore@ietf.org
Subject: Re: [sipcore] Draft new
version:draft-holmberg-sipcore-proxy-feature

[as an individual]

On 1/27/11 7:55 AM, Christer Holmberg wrote:
> 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.

Heh. If I were to make that kind of statement, it would be as a chair, 
and in coordination with the area directors. But that's not what I said,

or meant to imply. I said things would "get trickier," meaning you'll 
face opposition from the members of the working group that hold 
generality as a key SIP attribute.

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.

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.

/a
_______________________________________________
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore