Re: [sip-clf] Last Call: <draft-ietf-sipclf-problem-statement-11.txt> (The Common Log Format (CLF) for the Session Initiation Protocol (SIP): Framework and Data Model) to Proposed Standard
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 25 December 2012 10:35 UTC
Return-Path: <dromasca@avaya.com>
X-Original-To: sip-clf@ietfa.amsl.com
Delivered-To: sip-clf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 184E521F86BA for <sip-clf@ietfa.amsl.com>; Tue, 25 Dec 2012 02:35:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.924
X-Spam-Level:
X-Spam-Status: No, score=-102.924 tagged_above=-999 required=5 tests=[AWL=-0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1yLg-rci-Acu for <sip-clf@ietfa.amsl.com>; Tue, 25 Dec 2012 02:35:15 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id A3AB721F8614 for <sip-clf@ietf.org>; Tue, 25 Dec 2012 02:35:15 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAAEvoFDGmAcF/2dsb2JhbABEgmzAaYEIgh4BAQEBAgESKD8FBwQCAQgNBAQBAQEKFAUEBzIUCQgCBA4FCBqHYgYBCp4mjGSPHYwVhWlhA5wJijaCb4FkFx4
X-IronPort-AV: E=Sophos;i="4.80,759,1344225600"; d="scan'208";a="41957569"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 25 Dec 2012 05:25:11 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 25 Dec 2012 05:31:43 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.02.0318.004; Tue, 25 Dec 2012 05:35:15 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Thread-Topic: [sip-clf] Last Call: <draft-ietf-sipclf-problem-statement-11.txt> (The Common Log Format (CLF) for the Session Initiation Protocol (SIP): Framework and Data Model) to Proposed Standard
Thread-Index: AQHN4glSBsjFEtLFIUC61GjkDxUW+JgpUpzw
Date: Tue, 25 Dec 2012 10:35:14 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA051F66@AZ-FFEXMB04.global.avaya.com>
References: <20121203204501.12217.39525.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA042028@AZ-FFEXMB04.global.avaya.com> <50D8A750.2020005@bell-labs.com>
In-Reply-To: <50D8A750.2020005@bell-labs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
Subject: Re: [sip-clf] Last Call: <draft-ietf-sipclf-problem-statement-11.txt> (The Common Log Format (CLF) for the Session Initiation Protocol (SIP): Framework and Data Model) to Proposed Standard
X-BeenThere: sip-clf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Common Log File format discussion list <sip-clf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 25 Dec 2012 10:35:20 -0000
Hi Vijay, Thank you for addressing my comments. The proposed clarifications are very good and address my concerns and unclarities. Regards, Dan > -----Original Message----- > From: Vijay K. Gurbani [mailto:vkg@bell-labs.com] > Sent: Monday, December 24, 2012 9:05 PM > To: Romascanu, Dan (Dan) > Cc: ietf@ietf.org; sip-clf@ietf.org > Subject: Re: [sip-clf] Last Call: <draft-ietf-sipclf-problem-statement- > 11.txt> (The Common Log Format (CLF) for the Session Initiation Protocol > (SIP): Framework and Data Model) to Proposed Standard > > Dan: Thank you for your review of the SIP CLF problem statement draft. > I appreciate your time and resulting comments. > > Please see inline on resolution of your comments. I will be releasing > an updated version of the draft shortly with the resolutions contained > herein. > > On 12/17/2012 10:02 AM, Romascanu, Dan (Dan) wrote: > > Hi, > > > > I believe that this is a good document and I support its approval. > > > > I do have a number of issues which I suggest to take into > consideration before approval and publication: > > > > 1. In Section 4: > > > > The SIP CLF is amenable to easy parsing and lends itself well to > > creating other innovative tools. > > > > I am not sure what this sentence really says. What does 'easy parsing' > mean? The previous paragraph referred to 'quick parsing (i.e., well- > delimited fields)' - quick parsing is a relative notion but at least > there was an example. Here, I do not know. > > > > What does 'other innovative tools' means escapes me totally. Why > 'other'? 'other' than what? And what 'innovative tools' means? > > I have changed the text to address your comment. The change is as > follows: > > OLD: > > The SIP CLF is amenable to easy parsing and lends itself well to > creating other innovative tools. > > NEW: > > Due to the structure imposed by delimited fields, the SIP CLF is > amenable to easy parsing and lends itself well to creating other > innovative tools such as logfile parsers and trend analytic engines. > > > 2. In Section 11 > > > > SIP CLF log files will take up substantive amount of disk space > > depending on traffic volume at a processing entity and the amount > of > > information being logged. As such, any organization using SIP CLF > > should establish operational procedures for file rollovers as > > appropriate to the needs of the organization. > > > > Procedures for file rollovers is not enough - actually there need to > be in place procedures for periodic retrieval of logs before rollover. > > Added the phrase "periodic retrieval of logs before rollover" in S11. > > > 3. [RFC3261] needs to be a Normative Reference. All this document > speaks about logs for SIP, refers to SIP entities, messages, fields in > the SIP messages - on short it cannot be understood and the SIP-CLF > cannot be implemented without a good reading and understanding of > [RFC3261]. > > I think it is a reasonable position that understanding rfc3261 is a pre- > requsite for implementing SIP CLF. I have made rfc3261 normative as you > suggest. > > Once again, thank you for your time and review of this work. > > - vijay > -- > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent > 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) > Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com > Web: http://ect.bell-labs.com/who/vkg/
- [sip-clf] Last Call: <draft-ietf-sipclf-problem-s… The IESG
- Re: [sip-clf] Last Call: <draft-ietf-sipclf-probl… Romascanu, Dan (Dan)
- Re: [sip-clf] Last Call: <draft-ietf-sipclf-probl… Vijay K. Gurbani
- Re: [sip-clf] Last Call: <draft-ietf-sipclf-probl… Romascanu, Dan (Dan)