RFC 5153 on IPFIX Implementation Guidelines

rfc-editor@rfc-editor.org Fri, 18 April 2008 23:03 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA9ED3A6820; Fri, 18 Apr 2008 16:03:04 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E8D13A6804; Fri, 18 Apr 2008 16:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
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 OhMjp0KrPXN2; Fri, 18 Apr 2008 16:03:03 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id F3C983A68EE; Fri, 18 Apr 2008 16:03:02 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 52B83124F63; Fri, 18 Apr 2008 16:03:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5153 on IPFIX Implementation Guidelines
From: rfc-editor@rfc-editor.org
Message-Id: <20080418230304.52B83124F63@bosco.isi.edu>
Date: Fri, 18 Apr 2008 16:03:04 -0700
Cc: ipfix@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

        
        RFC 5153

        Title:      IPFIX Implementation Guidelines 
        Author:     E. Boschi, L. Mark,
                    J. Quittek, M. Stiemerling, P. Aitken
        Status:     Informational
        Date:       April 2008
        Mailbox:    elisa.boschi@hitachi-eu.com, 
                    lutz.mark@fokus.fraunhofer.de, 
                    quittek@nw.neclab.eu,
                    stiemerling@nw.neclab.eu, 
                    paitken@cisco.com
        Pages:      35
        Characters: 82845
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipfix-implementation-guidelines-08.txt

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

The IP Flow Information Export (IPFIX) protocol defines how IP Flow
information can be exported from routers, measurement probes, or
other devices.  This document provides guidelines for the
implementation and use of the IPFIX protocol.  Several sets of
guidelines address Template management, transport-specific issues,
implementation of Exporting and Collecting Processes, and IPFIX
implementation on middleboxes (such as firewalls, network address
translators, tunnel endpoints, packet classifiers, etc.).  This memo provides information for the Internet community.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce