Re: [sip-clf] Changes to proposed charter based on discussion in Stockholm

Vijay Gurbani <vkg@alcatel-lucent.com> Fri, 21 August 2009 00:38 UTC

Return-Path: <vkg@alcatel-lucent.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 BE0C33A6C74 for <sip-clf@core3.amsl.com>; Thu, 20 Aug 2009 17:38:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level:
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[AWL=-0.317, BAYES_00=-2.599, SARE_MLH_Stock1=0.87]
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 BPA7F03+Sjma for <sip-clf@core3.amsl.com>; Thu, 20 Aug 2009 17:38:46 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id C3CE13A6A4D for <sip-clf@ietf.org>; Thu, 20 Aug 2009 17:38:46 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id n7L0cpWp010733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Aug 2009 19:38:51 -0500 (CDT)
Received: from shoonya.ih.lucent.com (guard.research.bell-labs.com [135.104.2.9]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n7L0cnAM003902; Thu, 20 Aug 2009 19:38:50 -0500 (CDT)
Message-ID: <4A8DECCE.2060201@alcatel-lucent.com>
Date: Thu, 20 Aug 2009 19:39:42 -0500
From: Vijay Gurbani <vkg@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
References: <3D468AF5-7257-42D8-8F20-B619E04D648F@nostrum.com> <4A8DC962.3090200@alcatel-lucent.com> <0CF4A43B-EE03-4220-A972-777138DCDC20@nostrum.com>
In-Reply-To: <0CF4A43B-EE03-4220-A972-777138DCDC20@nostrum.com>
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, theo zourzouvillys <theo@voip.co.uk>
Subject: Re: [sip-clf] Changes to proposed charter based on discussion in Stockholm
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: Fri, 21 Aug 2009 00:38:47 -0000

Robert Sparks wrote:
> Thanks for looking at this Vijay.
> 
> Your suggestion negates exactly what the text was trying to say though.

Robert: Then I am confused.  More inline.

> The word "diverse" was there on purpose. I've heard an expectation from
> the conversation so far to be able to merge records from several different
> elements on the path of a request (multiple proxies, and potentially both
> (even several) endpoints, and do something sensible, like answer "what
> happened with this request".

Sure, but that is what the *second* bullet item is covering, is it not?
Namely,

   * the need to correlate messages from multiple elements
     related to a given request (that may fork) or a
     given dialog.

This is what allows folks to correlate a request across multiple
elements using something akin to Hadriel's session-id draft.

The first bullet covers cases where a proxy may want to create
a search tree of forked requests, or where a proxy's administrator
wants to do some trend analysis on a the proxy's log file.  The
first bullet also covers the case where a user wants to do some
analysis on his or her UA's local log file.

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}
WWW:   http://ect.bell-labs.com/who/vkg