[IPFIX] RFC 5982 on IP Flow Information Export (IPFIX) Mediation: Problem Statement
rfc-editor@rfc-editor.org Tue, 31 August 2010 17:47 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipfix@core3.amsl.com
Delivered-To: ipfix@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4DC803A68A7; Tue, 31 Aug 2010 10:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.347
X-Spam-Level:
X-Spam-Status: No, score=-102.347 tagged_above=-999 required=5 tests=[AWL=0.253, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 LDoGSDCy2yix; Tue, 31 Aug 2010 10:47:41 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 01A3B3A6842; Tue, 31 Aug 2010 10:47:41 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0C7E2E06D9; Tue, 31 Aug 2010 10:48:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100831174812.0C7E2E06D9@rfc-editor.org>
Date: Tue, 31 Aug 2010 10:48:12 -0700
Cc: ipfix@ietf.org, rfc-editor@rfc-editor.org
Subject: [IPFIX] RFC 5982 on IP Flow Information Export (IPFIX) Mediation: Problem Statement
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Aug 2010 17:47:42 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 5982
Title: IP Flow Information Export (IPFIX)
Mediation: Problem Statement
Author: A. Kobayashi, Ed.,
B. Claise, Ed.
Status: Informational
Stream: IETF
Date: August 2010
Mailbox: akoba@nttv6.net,
bclaise@cisco.com
Pages: 25
Characters: 56005
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ipfix-mediators-problem-statement-09.txt
URL: http://www.rfc-editor.org/rfc/rfc5982.txt
Flow-based measurement is a popular method for various network
monitoring usages. The sharing of flow-based information for
monitoring applications having different requirements raises some
open issues in terms of measurement system scalability, flow-based
measurement flexibility, and export reliability that IP Flow
Information Export (IPFIX) Mediation may help resolve. This
document describes some problems related to flow-based
measurement that network administrators have been facing,
and then it describes IPFIX Mediation applicability examples
along with the problems. This document is not an Internet
Standards Track specification; it is published for
informational purposes.
This document is a product of the IP Flow Information Export Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC