[rfc-dist] RFC 8038 on Exporting MIB Variables Using the IP Flow Information Export (IPFIX) Protocol

rfc-editor@rfc-editor.org Wed, 03 May 2017 01:35 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01BE5129C60 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 2 May 2017 18:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kVdmbPh-n1Np for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 2 May 2017 18:35:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54FEA12EB05 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 2 May 2017 18:33:15 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id EBCFBB8139C; Tue, 2 May 2017 18:33:09 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 4D758B8139B; Tue, 2 May 2017 18:33:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170503013309.4D758B8139B@rfc-editor.org>
Date: Tue, 02 May 2017 18:33:09 -0700
Subject: [rfc-dist] RFC 8038 on Exporting MIB Variables Using the IP Flow Information Export (IPFIX) Protocol
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8038

        Title:      Exporting MIB Variables Using the 
                    IP Flow Information Export (IPFIX) Protocol 
        Author:     P. Aitken, Ed.,
                    B. Claise, 
                    S. B S,
                    C. McDowall,
                    J. Schoenwaelder
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2017
        Mailbox:    paitken@brocade.com, 
                    bclaise@cisco.com, 
                    srikarbs@gmail.com,
                    cmcdowal@brocade.com, 
                    j.schoenwaelder@jacobs-university.de
        Pages:      85
        Characters: 188626
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipfix-mib-variable-export-10.txt

        URL:        https://www.rfc-editor.org/info/rfc8038

        DOI:        10.17487/RFC8038

This document specifies a way to complement IP Flow Information
Export (IPFIX) Data Records with Management Information Base (MIB)
objects, avoiding the need to define new IPFIX Information Elements
for existing MIB objects that are already fully specified.

Two IPFIX Options Templates, as well as a method for creating IPFIX
Options Templates that are used to export the extra data required to
fully describe Simple Network Management Protocol (SNMP) MIB objects
in IPFIX, are specified herein.

This is now a Proposed 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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org