RFC 7461 on Energy Object Context MIB

rfc-editor@rfc-editor.org Mon, 23 March 2015 19:04 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 113161B29B9; Mon, 23 Mar 2015 12:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 aTkjeudlvgoy; Mon, 23 Mar 2015 12:04:51 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id C4A061B29AA; Mon, 23 Mar 2015 12:04:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 488C6180470; Mon, 23 Mar 2015 12:03:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7461 on Energy Object Context MIB
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150323190322.488C6180470@rfc-editor.org>
Date: Mon, 23 Mar 2015 12:03:22 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/dFYrY3_hg3CNMToMe9t_q5AESTg>
Cc: drafts-update-ref@iana.org, eman@ietf.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: Mon, 23 Mar 2015 19:04:53 -0000

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

        
        RFC 7461

        Title:      Energy Object Context MIB 
        Author:     J. Parello, B. Claise,
                    M. Chandramouli
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2015
        Mailbox:    jparello@cisco.com, 
                    bclaise@cisco.com, 
                    moulchan@cisco.com
        Pages:      32
        Characters: 67077
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-eman-energy-aware-mib-17.txt

        URL:        https://www.rfc-editor.org/info/rfc7461

This document defines a subset of a Management Information Base
(MIB) for energy management of devices.  The module addresses
device identification, context information, and the energy
relationships between devices.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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