Re: [sip-clf] draft CLF charter

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 22 July 2009 13:43 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: sip-clf@core3.amsl.com
Delivered-To: sip-clf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1745F3A6768 for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 06:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.164
X-Spam-Level:
X-Spam-Status: No, score=-2.164 tagged_above=-999 required=5 tests=[AWL=0.435, BAYES_00=-2.599]
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 oA-QU3XgMTnr for <sip-clf@core3.amsl.com>; Wed, 22 Jul 2009 06:43:00 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id E28C23A68E1 for <sip-clf@ietf.org>; Wed, 22 Jul 2009 06:42:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,247,1246852800"; d="scan'208";a="151883702"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 22 Jul 2009 09:38:18 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 22 Jul 2009 09:38:17 -0400
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: Wed, 22 Jul 2009 15:38:16 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040189300C@307622ANEX5.global.avaya.com>
In-Reply-To: <4A6715CA.4000709@lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sip-clf] draft CLF charter
thread-index: AcoK0WNUI4ePL3TgRiK7mZ2pF/N2tQAADwsw
References: <3B33A97D-7E19-4A08-A431-A085D53A2A6E@nostrum.com> <D5E606B8-0811-4D40-AA76-ED989B00FD02@nostrum.com> <EDC652A26FB23C4EB6384A4584434A0401892AF4@307622ANEX5.global.avaya.com> <4A664053.7070603@alcatel-lucent.com> <EDC652A26FB23C4EB6384A4584434A0401892EB9@307622ANEX5.global.avaya.com> <4A6715CA.4000709@lucent.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Cc: sip-clf@ietf.org
Subject: Re: [sip-clf] draft CLF charter
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-clf>
List-Post: <mailto:sip-clf@ietf.org>
List-Help: <mailto:sip-clf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-clf>, <mailto:sip-clf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2009 13:43:02 -0000

All these look good. 

Thanks,

Dan
 

> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@alcatel-lucent.com] 
> Sent: Wednesday, July 22, 2009 4:36 PM
> To: Romascanu, Dan (Dan)
> Cc: Robert Sparks; sip-clf@ietf.org
> Subject: Re: [sip-clf] draft CLF charter
> 
> Romascanu, Dan (Dan) wrote:
> > Thanks for the answers. Most clarifications are fine with 
> me, a couple 
> > of observations in line.
> 
> Dan: Thank you.  I am suggesting some changes to the charter 
> based on your comments.  Could the sip-clf list participants 
> and the AD please review and comment.
> 
> dromasca> Is it efficiency on storage, on transmission? etc.)
> vkg> More than storage costs or transmission overhead, efficiency is 
> vkg> measured in processing time at the clients and servers.
> dromasca> Some clarification in the text of the charter would 
> be welcome.
> 
> OLD:
> The format will anticipate being used both for off-line 
> analysis and on-line real-time processing applications. The 
> working group will consider the need for efficient processing 
> in its design of this format.
> 
> NEW:
> The format will anticipate being used both for off-line 
> analysis and on-line real-time processing applications. The 
> working group will consider the need for efficient processing 
> in its design of this format, where efficiency is measured in 
> processing time of the CLF at the clients and servers (i.e., 
> the generation of the CLF should not cause an unnecessarily 
> burden so as to slow the normal processing done by a server, 
> and the processing of the file should not take undue time by 
> a client.)
> 
> dromasca> - if the WG ends by doing both a bit-field oriented and a 
> dromasca> text-oriented format will these end being separate 
> deliverables?
> vkg> Possibly; or they could be different sections in the 
> same document.  
> vkg> The CLF fields will be the same, just the representation of them 
> vkg> will differ.
> dromasca> So, basically we are talking about fields 
> definition (one) and 
> dromasca> mapping of the fields to different formats (one or more). 
> dromasca> Again, clarifying this in text may help.
> 
> OLD:
> The working group is not pre-constrained to producing either 
> a bit-field oriented or text-oriented format, and may choose 
> to provide both.  If the group chooses to specify both, it 
> must be possible to mechanically translate between the 
> formats without loss of information.
> 
> NEW:
> The working group is not pre-constrained to producing either 
> a bit-field oriented or text-oriented format, and may choose 
> to provide both.  The nature of the CLF information contained 
> in a bit-field or text-oriented format will be the same, it 
> is the representation that will differ.  If the group chooses 
> to specify both, it must be possible to mechanically 
> translate between the formats without loss of information.
> 
> Thanks,
> 
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 
> Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
> Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
> Web:   http://ect.bell-labs.com/who/vkg/
>