Re: [dispatch] Next steps on SIP-CLF

Cullen Jennings <fluffy@cisco.com> Fri, 01 May 2009 20:14 UTC

Return-Path: <fluffy@cisco.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 6A6243A6C26 for <dispatch@core3.amsl.com>; Fri, 1 May 2009 13:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level:
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, 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 4+Wyy0idqnGW for <dispatch@core3.amsl.com>; Fri, 1 May 2009 13:14:36 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 8BD943A6B7A for <dispatch@ietf.org>; Fri, 1 May 2009 13:14:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,280,1238976000"; d="scan'208";a="179754362"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 01 May 2009 20:15:59 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n41KFxrP001132; Fri, 1 May 2009 13:15:59 -0700
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n41KFwqN002865; Fri, 1 May 2009 20:15:58 GMT
From: Cullen Jennings <fluffy@cisco.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
In-Reply-To: <49FB54C1.30206@alcatel-lucent.com>
Impp: xmpp:cullenfluffyjennings@jabber.org
References: <49FB54C1.30206@alcatel-lucent.com>
Message-Id: <91F97501-F0C9-45DC-A48F-38F0EE362FF0@cisco.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 01 May 2009 14:15:57 -0600
X-Mailer: Apple Mail (2.930.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1205; t=1241208959; x=1242072959; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20Next=20steps=20on=20SIP-CLF |Sender:=20; bh=dPWA8VTcuCBQrZqymguYZrDg9h21T5hmXc0YRuHsEp8=; b=ZVdSIBrQXu+1AH/CklpgLVXDzIkuxrtiZgbqR/lLGxnnBaql+NA5y6Zz6z /K0Lf1Hn6cxd66e31gjPvD1MIguk8GDtioiSY3LU2bVV0VbxIUhMGTRjTl18 jMihsQcxQg;
Authentication-Results: sj-dkim-4; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
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 20:14:37 -0000

On May 1, 2009, at 2:00 PM, Vijay K. Gurbani wrote:

> Given that there is enough interest in the topic of SIP-CLF
> and enough passionate people to support both sides of the
> argument on binary vs. ASCII, we might as well start thinking
> of a place to get the work done.
>
> Following dispatch's role, maybe we should think how to form
> a place to get this work done, i.e., forming a BoF or EG or
> directing the work to an existing WG.  To that extent, if
> anyone wants to help put a concrete proposal together for
> SIP CLF work, I will be more than happy to work with them to
> define problem statement and proposal for new work.  We could
> do that part in dispatch, I believe.

Sound great - I'd be happy to see this happening.


>
>
> Regarding dealing with the technical aspects of the work, we
> could start a new IETF mailing list so that the technical
> discussions happen on that list and the process discussions
> can continue on dispatch.

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. I'll work with you to get the list set up.

Cullen <in my AD role>