Re: [sipcore] Call for consensus: draft-ietf-sipcore-presence-scaling-requirements

Adam Roach - SIPCORE Chair <adam@nostrum.com> Mon, 25 October 2010 20:53 UTC

Return-Path: <adam@nostrum.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 3E2D73A67B3 for <sipcore@core3.amsl.com>; Mon, 25 Oct 2010 13:53:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.629
X-Spam-Level:
X-Spam-Status: No, score=-102.629 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, 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 3PNkIAlKfwDO for <sipcore@core3.amsl.com>; Mon, 25 Oct 2010 13:53:03 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id F23C63A6407 for <sipcore@ietf.org>; Mon, 25 Oct 2010 13:53:00 -0700 (PDT)
Received: from dn3-228.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o9PKsjvj010701 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 25 Oct 2010 15:54:45 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4CC5EE94.4090700@nostrum.com>
Date: Mon, 25 Oct 2010 15:54:44 -0500
From: Adam Roach - SIPCORE Chair <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5
MIME-Version: 1.0
To: SIPCORE <sipcore@ietf.org>
References: <4CAB453D.5020601@nostrum.com>
In-Reply-To: <4CAB453D.5020601@nostrum.com>
Content-Type: multipart/alternative; boundary="------------010900060203000305080307"
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: simple-chairs@tools.ietf.org, "sipcore-chairs@tools.ietf.org" <sipcore-chairs@tools.ietf.org>
Subject: Re: [sipcore] Call for consensus: draft-ietf-sipcore-presence-scaling-requirements
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: SIPCORE Chairs <sipcore-chairs@tools.ietf.org>
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: Mon, 25 Oct 2010 20:53:04 -0000

[as chair]

It has been nearly three weeks, and there is been no expression of 
interest in continuing this work. We will ask the area directors to 
remove it from our charter and to mark the draft as "dead."

/a

On 10/5/10 10:33 AM, Adam Roach wrote:
> [as chair]
>
> As you can see below, the SIMPLE working group has decided to remove 
> draft-ietf-simple-interdomain-scaling-analysis from its chartered 
> milestones.
>
> SIPCORE has a closely related work item: 
> draft-ietf-sipcore-presence-scaling-requirements.
> It has been evaluated by the IESG, but has not been approved for 
> publication. The issue that is blocking its publication involves some 
> security related issues, which were to be addressed in the 
> interdomain-scaling-analysis. Further, the actual description of the 
> driving factors for the presence-scaling-requirements work are present 
> only in the interdomain-scaling-analysis work.
>
> With the interdomain-scaling-analysis work abandoned, the only path 
> for publishing presence-scaling-requirements would be to bring it back 
> to the working group, add the context that had been provided by the 
> interdomain-scaling-analysis draft, and address the IESG concerns that 
> have been raised around security and scaling.
>
> Given that the community of interest -- or disinterest, as the case 
> may be -- for the abandoned interdomain-scaling-analysis document is 
> almost certainly identical to that for the 
> presence-scaling-requirements document, it is a safe assumption that 
> SIPCORE can similarly remove the presence-scaling-requirements 
> milestone from its charter.
>
> So, I am posing the same question as the SIMPLE chairs: with the 
> interdomain-scaling-analysis work abandoned, is the 
> presence-scaling-requirements work still relevant? Are people still 
> interested in working on it? By that, I mean willing to spend time 
> doing focused reviews, offering feedback and maybe even text?
>
> Silence will be interpreted in the negative.
>
> /a
>
>
> -------- Original Message --------
> Subject: 	Re: [Simple] draft-ietf-simple-interdomain-scaling-analysis
> Date: 	Mon, 27 Sep 2010 14:55:48 -0500
> From: 	Ben Campbell <ben@nostrum.com>
> To: 	Simple WG <simple@ietf.org>
>
>
>
> Hi,
>
> We've had no expression of interest in continuing this effort. We will 
> ask our ADs to remove the milestone.
>
> Thanks!
>
> Ben.
>
> On Sep 24, 2010, at 9:24 AM, Ben Campbell wrote:
>
>> It's been almost a week, and no one has responded. If we don't hear 
>> otherwise from people who want to invest their time to work on this 
>> draft by Monday, we will ask the ADs to remove this milestone from 
>> the SIMPLE charter.
>>
>> Thanks!
>>
>> Ben.
>>
>> On Sep 19, 2010, at 9:09 AM, Ben Campbell wrote:
>>
>>> (as chair)
>>>
>>> draft-ietf-simple-interdomain-scaling-analysis has been stalled for 
>>> a while now. We handed it over to the IESG some time ago, but 
>>> received AD feedback indicating it needed significant work.   It has 
>>> been cycle starved since then. The author may be in a position to 
>>> start working on it again.
>>> *
>>> *
>>> *My question to the working group is, is this work still relevant? 
>>> Are people still interested in working on it? By that, I mean 
>>> willing to spend time doing focused reviews, offering feedback and 
>>> maybe even text?*
>>> *
>>> *
>>> *Silence will be interpreted in the negative. *
>>> *
>>> *
>>> *Thanks,*
>>> *
>>> *
>>> *Ben.*
>>> _______________________________________________
>>> Simple mailing list
>>> Simple@ietf.org <mailto:Simple@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/simple
>>
>> _______________________________________________
>> Simple mailing list
>> Simple@ietf.org <mailto:Simple@ietf.org>
>> https://www.ietf.org/mailman/listinfo/simple
>
>