RFC 6727 on Definitions of Managed Objects for Packet Sampling

rfc-editor@rfc-editor.org Tue, 02 October 2012 23:29 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5951021F85C0; Tue, 2 Oct 2012 16:29:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.004
X-Spam-Level:
X-Spam-Status: No, score=-102.004 tagged_above=-999 required=5 tests=[AWL=-0.004, 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 kK4w3R6XpYmb; Tue, 2 Oct 2012 16:29:19 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id F0B2321F85B8; Tue, 2 Oct 2012 16:29:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 183F0B1E003; Tue, 2 Oct 2012 16:24:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6727 on Definitions of Managed Objects for Packet Sampling
From: rfc-editor@rfc-editor.org
Message-Id: <20121002232455.183F0B1E003@rfc-editor.org>
Date: Tue, 02 Oct 2012 16:24:55 -0700
Cc: ipfix@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 02 Oct 2012 23:29:19 -0000

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

        
        RFC 6727

        Title:      Definitions of Managed Objects for 
                    Packet Sampling 
        Author:     T. Dietz, Ed.,
                    B. Claise, J. Quittek
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2012
        Mailbox:    dietz@neclab.eu, 
                    bclaise@cisco.com, 
                    quittek@neclab.eu
        Pages:      28
        Characters: 55441
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipfix-psamp-mib-06.txt

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

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes extensions to the IPFIX-SELECTOR-MIB
module.  For IP Flow Information eXport (IPFIX) implementations that
use Packet Sampling (PSAMP) techniques, this memo defines the PSAMP-
MIB module containing managed objects for providing information on
applied packet selection functions and their parameters.  
[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