[PSAMP] RFC 5476 on Packet Sampling (PSAMP) Protocol Specifications

rfc-editor@rfc-editor.org Tue, 31 March 2009 23:57 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: psamp@core3.amsl.com
Delivered-To: psamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38D7928C1EA; Tue, 31 Mar 2009 16:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.937
X-Spam-Level:
X-Spam-Status: No, score=-16.937 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, 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 fBEV-wa7U8dG; Tue, 31 Mar 2009 16:57:40 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 6331328C1E8; Tue, 31 Mar 2009 16:57:38 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id EB25826B7C2; Tue, 31 Mar 2009 16:58:01 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090331235801.EB25826B7C2@bosco.isi.edu>
Date: Tue, 31 Mar 2009 16:58:01 -0700
Cc: psamp@ietf.org, rfc-editor@rfc-editor.org
Subject: [PSAMP] RFC 5476 on Packet Sampling (PSAMP) Protocol Specifications
X-BeenThere: psamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This mailing list is used for discussion within the IETF packet sampling \(PSAMP\) WG" <psamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/psamp>, <mailto:psamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/psamp>
List-Post: <mailto:psamp@ietf.org>
List-Help: <mailto:psamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/psamp>, <mailto:psamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2009 23:57:41 -0000

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

        
        RFC 5476

        Title:      Packet Sampling (PSAMP) Protocol Specifications 
        Author:     B. Claise, Ed.,
                    A. Johnson, J. Quittek
        Status:     Standards Track
        Date:       March 2009
        Mailbox:    bclaise@cisco.com, 
                    andrjohn@cisco.com, 
                    quittek@nw.neclab.eu
        Pages:      45
        Characters: 101620
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-psamp-protocol-09.txt

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

This document specifies the export of packet information from a
Packet SAMPling (PSAMP) Exporting Process to a PSAMP Collecting Process.  
For export of packet information, the IP Flow Information eXport (IPFIX)
protocol is used, as both the IPFIX and PSAMP architecture match
very well, and the means provided by the IPFIX protocol are
sufficient.  The document specifies in detail how the IPFIX protocol
is used for PSAMP export of packet information.  [STANDARDS TRACK]

This document is a product of the Packet Sampling 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
USC/Information Sciences Institute