Re: [dispatch] Next steps on SIP-CLF

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Fri, 01 May 2009 21:23 UTC

Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8EC0528C241 for <dispatch@core3.amsl.com>; Fri, 1 May 2009 14:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.394
X-Spam-Level:
X-Spam-Status: No, score=-5.394 tagged_above=-999 required=5 tests=[AWL=0.855, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 zdlnxeeuYflx for <dispatch@core3.amsl.com>; Fri, 1 May 2009 14:23:32 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 79A3228C250 for <dispatch@ietf.org>; Fri, 1 May 2009 14:23:32 -0700 (PDT)
X-AuditID: c1b4fb3e-b7b7aae000004a86-76-49fb68a617bc
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 58.D7.19078.6A86BF94; Fri, 1 May 2009 23:24:55 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 1 May 2009 23:24:54 +0200
Received: from [131.160.126.150] ([131.160.126.150]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 1 May 2009 23:24:54 +0200
Message-ID: <49FB68A6.1040103@ericsson.com>
Date: Sat, 02 May 2009 00:24:54 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
References: <49FB54C1.30206@alcatel-lucent.com> <91F97501-F0C9-45DC-A48F-38F0EE362FF0@cisco.com>
In-Reply-To: <91F97501-F0C9-45DC-A48F-38F0EE362FF0@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 May 2009 21:24:54.0448 (UTC) FILETIME=[45187300:01C9CAA3]
X-Brightmail-Tracker: AAAAAA==
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Subject: Re: [dispatch] Next steps on SIP-CLF
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 May 2009 21:23:33 -0000

Hi,

> Sounds like a reasonable plan. I'm not sure we want to do this for all 
> things but I think it sounds like a good experiment to try for this one. 

yes, setting up a dedicated mailing list for discussing technical issues 
is a good option for relatively big work items. For smaller ones, we may 
want to use a generic mailing list for technical discussions on 
different smaller topics. This would avoid the overhead of creating and 
following too many mailing lists.

In any case, we would like to limit discussions in the DISPTACH list to 
discussions on whether or not we should work on a particular issue. 
High-level technical discussions that may help clarify whether or not it 
is appropriate to adopt some work are relevant but more detailed 
technical discussions fall outside our charter.

Cheers,

Gonzalo