[IPFIX] STD 77, RFC 7011 on Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information
rfc-editor@rfc-editor.org Mon, 16 September 2013 05:05 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8D6D11E81E6; Sun, 15 Sep 2013 22:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.7
X-Spam-Level:
X-Spam-Status: No, score=-101.7 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qxzzGq74dTO1; Sun, 15 Sep 2013 22:05:30 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 186AE11E81C3; Sun, 15 Sep 2013 22:05:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 712758E01B; Sun, 15 Sep 2013 21:59:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130916045909.712758E01B@rfc-editor.org>
Date: Sun, 15 Sep 2013 21:59:07 -0700
Cc: drafts-update-ref@iana.org, ipfix@ietf.org, rfc-editor@rfc-editor.org
Subject: [IPFIX] STD 77, RFC 7011 on Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 16 Sep 2013 05:05:31 -0000
A new Request for Comments is now available in online RFC libraries.
STD 77
RFC 7011
Title: Specification of the IP Flow
Information Export (IPFIX) Protocol for the
Exchange of Flow Information
Author: B. Claise, Ed.,
B. Trammell, Ed.,
P. Aitken
Status: Standards Track
Stream: IETF
Date: September 2013
Mailbox: bclaise@cisco.com,
trammell@tik.ee.ethz.ch,
paitken@cisco.com
Pages: 76
Characters: 170852
Obsoletes: RFC 5101
See Also: STD 77
I-D Tag: draft-ietf-ipfix-protocol-rfc5101bis-10.txt
URL: http://www.rfc-editor.org/rfc/rfc7011.txt
This document specifies the IP Flow Information Export (IPFIX)
protocol, which serves as a means for transmitting Traffic Flow
information over the network. In order to transmit Traffic Flow
information from an Exporting Process to a Collecting Process, a
common representation of flow data and a standard means of
communicating them are required. This document describes how
the IPFIX Data and Template Records are carried over a number of
transport protocols from an IPFIX Exporting Process to an IPFIX
Collecting Process. This document obsoletes RFC 5101.
This document is a product of the IP Flow Information Export Working Group of the IETF.
This is now an Internet Standard.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. 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/search/rfc_search.php
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