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

Robert Sparks <rjsparks@nostrum.com> Thu, 20 August 2009 22:36 UTC

Return-Path: <rjsparks@nostrum.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 228A23A6B41 for <sip-clf@core3.amsl.com>; Thu, 20 Aug 2009 15:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.138
X-Spam-Level:
X-Spam-Status: No, score=-2.138 tagged_above=-999 required=5 tests=[AWL=-0.408, BAYES_00=-2.599, SARE_MLH_Stock1=0.87, SPF_PASS=-0.001]
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 IPMQklM85oYD for <sip-clf@core3.amsl.com>; Thu, 20 Aug 2009 15:36:10 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id CA6283A69F0 for <sip-clf@ietf.org>; Thu, 20 Aug 2009 15:36:09 -0700 (PDT)
Received: from dn3-232.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id n7KMaA0Q085379 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Aug 2009 17:36:10 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-Id: <0CF4A43B-EE03-4220-A972-777138DCDC20@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
In-Reply-To: <4A8DC962.3090200@alcatel-lucent.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 20 Aug 2009 17:36:10 -0500
References: <3D468AF5-7257-42D8-8F20-B619E04D648F@nostrum.com> <4A8DC962.3090200@alcatel-lucent.com>
X-Mailer: Apple Mail (2.936)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
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: Thu, 20 Aug 2009 22:36:11 -0000

Thanks for looking at this Vijay.

Your suggestion negates exactly what the text was trying to say though.

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".

RjS

On Aug 20, 2009, at 5:08 PM, Vijay K. Gurbani wrote:

> Robert Sparks wrote:
>> Please review and comment on the text at
>> http://svn.resiprocate.org/viewsvn/ietf-drafts/clf/clf-draft-charter.txt?revision=3692&view=markup
>
> Robert: Overall, the writeup looks great.  I especially
> think that the operational guidelines and security
> guidance are advantageous outcomes of the hallway
> conversation we had with various folks in Stockholm.
>
> I do have one suggestion:
>
> OLD:
> * the need to search, merge, and summarize the log records
>  from diverse elements.
>
> NEW:
> * the need to search, merge, and summarize the log records
>  from a log file produced by the corresponding SIP element.
>
> Rationale: I believe that what you are trying to say is
> that search, merge, and summarization is being performed
> by the administrator or user responsible for a specific
> SIP element.  That is, a user may well summarize all the
> sessions he or she established during the day, while a
> system administrator will be more interested in a summary
> of all the sessions set up through the proxy.  Each
> principal -- user or the administrator -- is looking at
> the log records produced by the specific SIP element they
> have access to; respectively, UA and proxy.
>
> Thanks for getting this out.
>
> - 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/