Re: [eman] EMAN-REQ: the notion of importance

"Mouli Chandramouli (moulchan)" <moulchan@cisco.com> Tue, 28 February 2012 05:57 UTC

Return-Path: <moulchan@cisco.com>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6E0A21F86A3 for <eman@ietfa.amsl.com>; Mon, 27 Feb 2012 21:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.037
X-Spam-Level:
X-Spam-Status: No, score=-9.037 tagged_above=-999 required=5 tests=[AWL=0.561, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 wHKSUqAdfV2M for <eman@ietfa.amsl.com>; Mon, 27 Feb 2012 21:57:36 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id D2D8321F869D for <eman@ietf.org>; Mon, 27 Feb 2012 21:57:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=moulchan@cisco.com; l=28824; q=dns/txt; s=iport; t=1330408656; x=1331618256; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=JaRZiTsZT9xihfYLBv+209QwHSlJaGMJ9sIiHO9ORCM=; b=llPDa3yO9IbbIP9wHxzRmD9wKh6MrroI49M0mMzbL6VSKw3h6p+jSAlc 4dPRceVUHz4tE3mYHYnCGxPXpN5jSqirvDmEsUTKmJpxbZvv4cxqP4DFJ Vo+8g98t4GPw+3LoavUhzOEISkmEyQkC5exPkXJ1tT37wqcVqn/zau25g w=;
X-Files: image001.png : 2050
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAIVsTE+tJXG9/2dsb2JhbAA/A4JRgmilKgGIJ3mBB4FzAQEBBAEBAQIBDAEJBwIIAQI7AwsQAgEGAgcKAwEBAQYBAQECBhcBAgICAQEFEAEJBQEfCQgBAQQBEQEGAhMHh2QLoHEBjGWKQYkPb4JzCAULAQcDAgFMGIRZDggKBwYBRwEFCAEGBAYEAQUECAQJgg0zYwSIT4cekGeHdoE2
X-IronPort-AV: E=Sophos; i="4.73,494,1325462400"; d="png'150?scan'150,208,217,150"; a="62268207"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-1.cisco.com with ESMTP; 28 Feb 2012 05:57:25 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id q1S5vPlw018517; Tue, 28 Feb 2012 05:57:25 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 27 Feb 2012 23:57:25 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/related; type="multipart/alternative"; boundary="----_=_NextPart_001_01CCF5DD.D8449251"
Date: Mon, 27 Feb 2012 23:57:21 -0600
Message-ID: <E9B25823FA871E4AA9EDA7B163E5D8A9079F9740@XMB-RCD-106.cisco.com>
In-Reply-To: <CAN40gSv6HDcFD6Sa+nj1JMXodYRmp4qYTOuz7WUV4iFFrR7vxg@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [eman] EMAN-REQ: the notion of importance
Thread-Index: Acz1d4FT0+CobvM1QvWC78mg3uU1nwAZa3LA
References: <4F4B6644.2030503@cisco.com><CB71229C.206B9%brads@coraid.com> <CAN40gSv6HDcFD6Sa+nj1JMXodYRmp4qYTOuz7WUV4iFFrR7vxg@mail.gmail.com>
From: "Mouli Chandramouli (moulchan)" <moulchan@cisco.com>
To: Ira McDonald <blueroofmusic@gmail.com>, Brad Schoening <brads@coraid.com>
X-OriginalArrivalTime: 28 Feb 2012 05:57:25.0521 (UTC) FILETIME=[D877D010:01CCF5DD]
Cc: eman mailing list <eman@ietf.org>
Subject: Re: [eman] EMAN-REQ: the notion of importance
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2012 05:57:38 -0000

Given the precedence of use of priority in other IETF MIBs, I think the value of importance is clearly illustrated. 

 

Regarding Role, it is not intended to be an IANA registry.  This concept is already used by deployments.  Should not be dismissed as not useful. 

 

If the question is – clearer description of these terms, in the requirements draft, it is possible to provide some text and also how these concepts can be useful. 

 

Thanks

Mouli

 

From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of Ira McDonald
Sent: Monday, February 27, 2012 11:15 PM
To: Brad Schoening; Ira McDonald
Cc: eman mailing list
Subject: Re: [eman] EMAN-REQ: the notion of importance

 

Hi,

Brad - good precedent - because it makes the "importance"
machine readable (and therefore useful).

But since EMAN (and many other IETF WGs) have consistently
backed away from any standard definition of "role" (w/ behavior
semantics that are predictable), a text string of "role" is useless
(except in a vendor- or site-specific manner - out-of-scope IMHO).

And I suggest that the "universe of things" is too diverse to lend
itself to an IANA registry of standard "role" keywords.

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic <http://sites.google.com/site/blueroofmusic> 
http://sites.google.com/site/highnorthinc <http://sites.google.com/site/highnorthinc> 
mailto:blueroofmusic@gmail.com
Winter  579 Park Place  Saline, MI  48176  734-944-0094
Summer  PO Box 221  Grand Marais, MI 49839  906-494-2434





On Mon, Feb 27, 2012 at 12:10 PM, Brad Schoening <brads@coraid.com> wrote:

Benoit,

 

There is a precedence for doing this on the device in the PoE MIB, rfc3621 which defines pethPsePortPowerPriority:

   pethPsePortPowerPriority OBJECT-TYPE
    SYNTAX INTEGER   {
               critical(1),
               high(2),
               low(3)
     }
    MAX-ACCESS read-write
    STATUS current
    DESCRIPTION
        "This object controls the priority of the port from the point
         of view of a power management algorithm.  The priority that
         is set by this variable could be used by a control mechanism
         that prevents over current situations by disconnecting first
         ports with lower power priority.  Ports that connect devices
         critical to the operation of the network - like the E911
         telephones ports - should be set to higher priority."
    ::= { pethPsePortEntry 7 }
 
 
 
 

Brad Schoening
e: brads@coraid.com ⟐ m: 917-304-7190

 

  <http://www.coraid.com/>  Redefining Storage Economics

 

 

From: Benoit Claise <bclaise@cisco.com>
Date: Mon, 27 Feb 2012 05:17:24 -0600
To: eman mailing list <eman@ietf.org>
Subject: [eman] EMAN-REQ: the notion of importance

 

Dear all, 

There is a discussion amongst the "EMAN requirements" authors right now about the notion of importance.
We're trying to evaluate the requirements related to the "importance".

The current draft version <http://tools.ietf.org/html/draft-ietf-eman-requirements-05>  only mentions:


5.1.2.  Context information on powered entities

   The energy management standard must provide means for retrieving and
   reporting context information on powered entities, for example, tags
   associated with a powered entity that indicate the powered entity's
   role, or importance.


So there are no justifications why the importance is required. 
The people who want this, please provide some more text/justifications

Some extra questions: 
- Is this importance specific to EMAN or is this generic also for non Energy Objects?
- Importance is important related to ...?

Regards, Benoit (as a contributor for the EMAN-REQ)





_______________________________________________
eman mailing list
eman@ietf.org
https://www.ietf.org/mailman/listinfo/eman