RFC 6933 on Entity MIB (Version 4)

rfc-editor@rfc-editor.org Fri, 24 May 2013 20:10 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 32E0721F8F1E; Fri, 24 May 2013 13:10:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.121
X-Spam-Level:
X-Spam-Status: No, score=-102.121 tagged_above=-999 required=5 tests=[AWL=-0.121, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QsQsZLV7unX; Fri, 24 May 2013 13:10:29 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id C936211E80FC; Fri, 24 May 2013 13:10:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5DBCE6210B; Fri, 24 May 2013 13:09:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6933 on Entity MIB (Version 4)
From: rfc-editor@rfc-editor.org
Message-Id: <20130524200948.5DBCE6210B@rfc-editor.org>
Date: Fri, 24 May 2013 13:09:48 -0700
Cc: eman@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 24 May 2013 20:10:30 -0000

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

        
        RFC 6933

        Title:      Entity MIB (Version 4) 
        Author:     A. Bierman, D. Romascanu,
                    J. Quittek, M. Chandramouli
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2013
        Mailbox:    andy@yumaworks.com, 
                    dromasca@avaya.com, 
                    quittek@neclab.eu,
                    moulchan@cisco.com
        Pages:      76
        Characters: 165278
        Obsoletes:  RFC 4133

        I-D Tag:    draft-ietf-eman-rfc4133bis-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6933.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 managed objects used for managing
multiple logical and physical entities managed by a single Simple
Network Management Protocol (SNMP) agent.  This document specifies
version 4 of the Entity MIB.  This memo obsoletes version 3 of the
Entity MIB module published as RFC 4133.

This document is a product of the Energy Management Working Group of the IETF.

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