Document Action: 'IPFIX Applicability' to Informational RFC
The IESG <iesg-secretary@ietf.org> Thu, 12 July 2007 20:18 UTC
Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I957P-00017y-3P; Thu, 12 Jul 2007 16:18:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I957M-00012b-VE; Thu, 12 Jul 2007 16:18:28 -0400
Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I957J-0004AK-Mh; Thu, 12 Jul 2007 16:18:28 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id A481B329CC; Thu, 12 Jul 2007 20:18:25 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I957J-00072G-IG; Thu, 12 Jul 2007 16:18:25 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1I957J-00072G-IG@stiedprstage1.ietf.org>
Date: Thu, 12 Jul 2007 16:18:25 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Internet Architecture Board <iab@iab.org>, ipfix chair <ipfix-chairs@tools.ietf.org>, ipfix mailing list <ipfix@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Document Action: 'IPFIX Applicability' to Informational RFC
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
The IESG has approved the following document: - 'IPFIX Applicability ' <draft-ietf-ipfix-as-12.txt> as an Informational RFC This document is the product of the IP Flow Information Export Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipfix-as-12.txt Technical Summary This document describes the applicability of the IP Flow Information Export (IPFIX) protocol for a variety of applications. It shows how applications can use IPFIX, describes the relevant information elements (IEs) and shows opportunities and limitations of the protocol. The document furthermore describes relations of the IPFIX framework to other architectures and frameworks. Working Group Summary The document has met strong consensus withing the IPFIX Working Group. Protocol Quality The document was reviewed by the WG co-chairs, by representatives from RMON, IPPM, AAA and secdir and for the IESG by Dan Romascanu. Note to RFC Editor RFC Editor, please make the following changes: 1. In Section 2.1 OLD: In order to realize usage-based accounting with IPFIX the flow definition has to be chosen in accordance to the accounting purpose. NEW: In order to realize usage-based accounting with IPFIX the flow definition has to be chosen in accordance to the accounting purpose, such as trend analysis, capacity planning, auditing, or billing and cost allocation where some loss of data can be tolerated (see section 4.2). 2. In Section 2.1.1 OLD: Let's suppose someone has a Service Level Agreement (SLA) in a DiffServ network requiring accounting based on traffic volume. NEW: Let's suppose someone needs to monitor the individual flows in a DiffServ network in order to compare traffic amount trend with the terms outlined in a Service Level Agreement (SLA). _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce