Re: [sip-clf] Implementation - Code and Results

"Vijay K. Gurbani" <vkg@bell-labs.com> Wed, 27 October 2010 15:53 UTC

Return-Path: <vkg@bell-labs.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 7264C3A6853 for <sip-clf@core3.amsl.com>; Wed, 27 Oct 2010 08:53:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level:
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, 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 pULoM1I3zabh for <sip-clf@core3.amsl.com>; Wed, 27 Oct 2010 08:53:24 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 228B83A69A0 for <sip-clf@ietf.org>; Wed, 27 Oct 2010 08:53:19 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-63.lucent.com [135.3.40.63]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id o9RFt74o015515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Oct 2010 10:55:08 -0500 (CDT)
Received: from shoonya.ih.lucent.com (Knoppix-135185238233.ih.lucent.com [135.185.238.233]) by umail.lucent.com (8.13.8/TPES) with ESMTP id o9RFt7sX022361; Wed, 27 Oct 2010 10:55:07 -0500 (CDT)
Message-ID: <4CC84BCC.5060303@bell-labs.com>
Date: Wed, 27 Oct 2010 10:57:00 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.12) Gecko/20100907 Fedora/3.0.7-1.fc12 Thunderbird/3.0.7
MIME-Version: 1.0
To: Saverio Niccolini <Saverio.Niccolini@neclab.eu>
References: <AANLkTimO0vUhjRJBU9iSkLXkQ3xT36up635y+4__QoO1@mail.gmail.com> <4CC83820.2090103@bell-labs.com> <752EDF9B02C09847950620E262C45431841220@PALLENE.office.hd>
In-Reply-To: <752EDF9B02C09847950620E262C45431841220@PALLENE.office.hd>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Implementation - Code and Results
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, 27 Oct 2010 15:53:36 -0000

On 10/27/2010 10:35 AM, Saverio Niccolini wrote:
> Vijay,
>
>> Small devices (mobile phones running SIP) will not generate that
>> much traffic per day --- when compared to a SIP proxy --- to make
>> the space issue a deterrent.
>
> are we looking at log generated by small devices? there is not so
> much you can analyze from them (unless you merge them, which is
> outside the scope of the charter now), the interesting part is to
> look at the SIP proxy logs...

Saverio: Absolutely.  I was merely responding to Peter's
note that people coding on small devices may feel differently
about space.

That said, I will point out that the way we have defined the
data model for SIP CLF, any SIP entity can use it --- proxy,
user agent server, user agent clients and everything in between.
Thus, it is not inconceivable that implementers for resource
constrained devices be interested in saving local logs of
calls being made.

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/