RFC 7270 on Cisco-Specific Information Elements Reused in IP Flow Information Export (IPFIX)

rfc-editor@rfc-editor.org Tue, 24 June 2014 22:34 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 204271B293B for <ietf-announce@ietfa.amsl.com>; Tue, 24 Jun 2014 15:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level:
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 bskyrNz-VeIw for <ietf-announce@ietfa.amsl.com>; Tue, 24 Jun 2014 15:34:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id A93E51B2929 for <ietf-announce@ietf.org>; Tue, 24 Jun 2014 15:34:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DD6EC1801C2; Tue, 24 Jun 2014 15:33:01 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7270 on Cisco-Specific Information Elements Reused in IP Flow Information Export (IPFIX)
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140624223301.DD6EC1801C2@rfc-editor.org>
Date: Tue, 24 Jun 2014 15:33:01 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/P6j-MMEKynx_sISdtr2_T84EJ2E
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2014 22:34:38 -0000

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

        
        RFC 7270

        Title:      Cisco-Specific Information Elements Reused in 
                    IP Flow Information Export (IPFIX) 
        Author:     A. Yourtchenko,
                    P. Aitken,
                    B. Claise
        Status:     Informational
        Stream:     IETF
        Date:       June 2014
        Mailbox:    ayourtch@cisco.com, 
                    paitken@cisco.com, 
                    bclaise@cisco.com
        Pages:      21
        Characters: 33990
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-yourtchenko-cisco-ies-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7270.txt

This document describes some additional IP Flow Information Export
(IPFIX) Information Elements in the range of 1-127, which is the
range compatible with field types used by NetFlow version 9 in RFC
3954, as specified in the IPFIX Information Model in RFC 7012.


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/search
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