[IPFIX] RFC 6313 on Export of Structured Data in IP Flow Information Export (IPFIX)
rfc-editor@rfc-editor.org Wed, 20 July 2011 22:59 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 E0B0221F8AF0; Wed, 20 Jul 2011 15:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.165
X-Spam-Level:
X-Spam-Status: No, score=-102.165 tagged_above=-999 required=5 tests=[AWL=-0.165, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, 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 laMfTPSVX9+K; Wed, 20 Jul 2011 15:59:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id B9E0121F8AED; Wed, 20 Jul 2011 15:59:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EB7E098C4F4; Wed, 20 Jul 2011 15:59:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110720225923.EB7E098C4F4@rfc-editor.org>
Date: Wed, 20 Jul 2011 15:59:22 -0700
Cc: ipfix@ietf.org, rfc-editor@rfc-editor.org
Subject: [IPFIX] RFC 6313 on Export of Structured Data in IP Flow Information Export (IPFIX)
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: Wed, 20 Jul 2011 22:59:29 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6313 Title: Export of Structured Data in IP Flow Information Export (IPFIX) Author: B. Claise, G. Dhandapani, P. Aitken, S. Yates Status: Standards Track Stream: IETF Date: July 2011 Mailbox: bclaise@cisco.com, gowri@cisco.com, paitken@cisco.com, syates@cisco.com Pages: 71 Characters: 163360 Updates: RFC5102 I-D Tag: draft-ietf-ipfix-structured-data-06.txt URL: http://www.rfc-editor.org/rfc/rfc6313.txt This document specifies an extension to the IP Flow Information Export (IPFIX) protocol specification in RFC 5101 and the IPFIX information model specified in RFC 5102 to support hierarchical structured data and lists (sequences) of Information Elements in data records. This extension allows definition of complex data structures such as variable-length lists and specification of hierarchical containment relationships between Templates. Finally, the semantics are provided in order to express the relationship among multiple list elements in a structured data record. [STANDARDS-TRACK] This document is a product of the IP Flow Information Export Working Group of the IETF. This is now a Proposed Standard Protocol. 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/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