Re: [sip-clf] FW: New Version Notification for draft-niccolini-sipclf-ipfix-02
"Vijay K. Gurbani" <vkg@bell-labs.com> Mon, 19 April 2010 22:21 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 CA13F3A6942 for <sip-clf@core3.amsl.com>; Mon, 19 Apr 2010 15:21:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.941
X-Spam-Level:
X-Spam-Status: No, score=-0.941 tagged_above=-999 required=5 tests=[AWL=-0.942, BAYES_50=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 nX5jeq0Lm0sa for <sip-clf@core3.amsl.com>; Mon, 19 Apr 2010 15:21:44 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 1A3253A6955 for <sip-clf@ietf.org>; Mon, 19 Apr 2010 15:21:33 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-63.lucent.com [135.3.40.63]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id o3JMLKeF024208 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Apr 2010 17:21:20 -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 o3JMLKQ5024901; Mon, 19 Apr 2010 17:21:20 -0500 (CDT)
Message-ID: <4BCCD7A5.9090903@bell-labs.com>
Date: Mon, 19 Apr 2010 17:22:29 -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.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Thunderbird/3.0.4
MIME-Version: 1.0
To: Saverio Niccolini <Saverio.Niccolini@nw.neclab.eu>
References: <547F018265F92642B577B986577D671C013819FF@VENUS.office>
In-Reply-To: <547F018265F92642B577B986577D671C013819FF@VENUS.office>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: SIP-CLF Mailing List <sip-clf@ietf.org>
Subject: Re: [sip-clf] FW: New Version Notification for draft-niccolini-sipclf-ipfix-02
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: Mon, 19 Apr 2010 22:21:47 -0000
On 04/19/2010 09:28 AM, Saverio Niccolini wrote: > Dear all, > > we just submitted a new version of the draft (now available at > http://www.ietf.org/id/draft-niccolini-sipclf-ipfix-02.txt). > > This version improves the example where we used a real private > enterprise (PEN) number 35566 (which is controlled by one of > the authors of the draft). > > We also added a list of open points that we think should be > addressed in future version of the draft. > > Before moving into addressing those, we would appreciate feedback > to the example that was explicitly requested by the WG and the AD. Saverio: Thanks for getting this out. I am not sure I understand the mechanics of ipfix completely, but the draft helps me conceptualize the approach a bit more. In any case, I had one comment on Section 5. The text presented in S5 is more of a data model than an information model. If I read rfc3444 correctly, a "data model" determines the structure of data elements (including legal values for the contents of these) and the relationship among the data elements. An "information model", on the other hand, is the modeling of entities in a system and their relationship (these are, fortunately, the most generally accepted definitions for the terms in the industry and academia.) The problem-statement draft already contains a data model [1] that I have been using for a long time [2]. In the next revision of the problem-statement draft I am working on now, I will present a more formal definition of the data model, including the relationship between the data elements (some of which is captured in the precursor draft [2].) I think it may be best to leave the data model in one place --- the problem-statement draft --- and have the individual solution drafts show the format of the sipclf record. I would love your feedback on the data model and its contents once I get the updated problem-statement draft out later this week. [1] http://tools.ietf.org/html/draft-ietf-sipclf-problem-statement-01 [2] http://tools.ietf.org/html/draft-gurbani-sipping-clf-01 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/
- [sip-clf] FW: New Version Notification for draft-… Saverio Niccolini
- Re: [sip-clf] FW: New Version Notification for dr… Vijay K. Gurbani
- Re: [sip-clf] FW: New Version Notification for dr… Saverio Niccolini
- Re: [sip-clf] FW: New Version Notification for dr… Vijay K. Gurbani
- Re: [sip-clf] FW: New Version Notification for dr… Saverio Niccolini
- Re: [sip-clf] FW: New Version Notification for dr… Vijay K. Gurbani
- Re: [sip-clf] FW: New Version Notification for dr… Saverio Niccolini
- Re: [sip-clf] FW: New Version Notification for dr… Vijay K. Gurbani