From bclaise@cisco.com Tue Dec 10 03:08:25 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD3B1AD7C0; Tue, 10 Dec 2013 03:08:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -11.501 X-Spam-Level: X-Spam-Status: No, score=-11.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 GXNhdlNCV9vj; Tue, 10 Dec 2013 03:08:23 -0800 (PST) Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id D6C591A1F54; Tue, 10 Dec 2013 03:08:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4236; q=dns/txt; s=iport; t=1386673698; x=1387883298; h=message-id:date:from:mime-version:to:cc:subject; bh=JxVsZnlOpS40WGGYjjBK+FdoZJZ3uJuZrR0gd4oeLIc=; b=ThEzzANpd9zGbG9gJJtmN5GBa7HwxZoIgv1tWevIAxKz4QhqfZITrtHM zLE5KYHTLqwTIMf4CJPpyLLjrvoR1rG1sBfNmjllGiCYMvddl9m+k0T4L npaMbUOEjJP4fj/E6Coc5gAuWkVmWgj10MZJ14S6Hl38UoCLjFMfNQujd g=; X-IronPort-AV: E=Sophos;i="4.93,865,1378857600"; d="scan'208,217";a="1344512" Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 10 Dec 2013 11:08:17 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rBAB8C2J032554; Tue, 10 Dec 2013 11:08:13 GMT Message-ID: <52A6F61C.7020504@cisco.com> Date: Tue, 10 Dec 2013 12:08:12 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: "MIB Doctors (E-mail)" Content-Type: multipart/alternative; boundary="------------030408090104070401090208" Cc: eman mailing list Subject: [eman] DEFINITIONS and MODULE-IDENTITY X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2013 11:08:25 -0000 This is a multi-part message in MIME format. --------------030408090104070401090208 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit MIB doctors, One question regarding DEFINITIONS and MODULE-IDENTITY Looking at https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib/, I see ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, mib-2, Integer32 FROM SNMPv2-SMI TEXTUAL-CONVENTION, MacAddress, TruthValue FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF SnmpAdminString FROM SNMP-FRAMEWORK-MIB InetAddressType, InetAddress FROM INET-ADDRESS-MIB entPhysicalIndex FROM ENTITY-MIB UUIDorZero FROM UUID-TC-MIB IANAEnergyRelationship FROM IANA-ENERGY-RELATION-MIB; energyAwareMIBMODULE-IDENTITY LAST-UPDATED "201311290000Z" I guess that ENERGY-OBJECT-CONTEXT-MIB and energyAwareMIB, being different, would be flagged as a problem by the MIB doctors, correct? The closest piece of information is from RFC 4181: - The descriptor associated with the MODULE-IDENTITY invocation should be of the form xxxMIB, xxxMib, or xxxMibModule, where xxx is a mixed-case version of XXX starting with a lowercase letter and without any hyphens. For example, the OPT-IF-MIB uses the prefix optIf, and the descriptor associated with its MODULE-IDENTITY invocation is optIfMibModule. Regards, Benoit --------------030408090104070401090208 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit MIB doctors,

One question regarding DEFINITIONS and MODULE-IDENTITY

Looking at https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib/, I see 

       ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::= BEGIN 
         
        IMPORTS 
            MODULE-IDENTITY, 
            OBJECT-TYPE, 
            mib-2, 
            Integer32 
                FROM SNMPv2-SMI  
            TEXTUAL-CONVENTION, MacAddress, TruthValue 
                FROM SNMPv2-TC 
            MODULE-COMPLIANCE, 
            OBJECT-GROUP      
                FROM SNMPv2-CONF 
            SnmpAdminString 
                FROM SNMP-FRAMEWORK-MIB  
            InetAddressType, InetAddress 
               FROM INET-ADDRESS-MIB                  
            entPhysicalIndex 
               FROM ENTITY-MIB     
            UUIDorZero 
               FROM UUID-TC-MIB 
            IANAEnergyRelationship 
               FROM IANA-ENERGY-RELATION-MIB;   
         
        energyAwareMIB MODULE-IDENTITY 
            LAST-UPDATED    "201311290000Z"
I guess that ENERGY-OBJECT-CONTEXT-MIB and energyAwareMIB, being different, would be flagged as a problem by the MIB doctors, correct?

The closest piece of information is from RFC 4181:
 
   - The descriptor associated with the MODULE-IDENTITY invocation
     should be of the form xxxMIB, xxxMib, or xxxMibModule, where xxx is
     a mixed-case version of XXX starting with a lowercase letter and
     without any hyphens.  For example, the OPT-IF-MIB uses the prefix
     optIf, and the descriptor associated with its MODULE-IDENTITY
     invocation is optIfMibModule.
Regards, Benoit
--------------030408090104070401090208-- From tnadeau@lucidvision.com Tue Dec 10 04:50:47 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A82461AE06D; Tue, 10 Dec 2013 04:50:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.9 X-Spam-Level: X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001] 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 zA_-pMwAFAcn; Tue, 10 Dec 2013 04:50:46 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id B643E1AE069; Tue, 10 Dec 2013 04:50:45 -0800 (PST) Received: from [192.168.1.104] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 56038267E5A2; Tue, 10 Dec 2013 07:50:40 -0500 (EST) Content-Type: multipart/signed; boundary="Apple-Mail=_6FB722C4-F529-4327-877C-7F7CE1B673DB"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) From: Thomas Nadeau In-Reply-To: <52A6F61C.7020504@cisco.com> Date: Tue, 10 Dec 2013 07:50:36 -0500 Message-Id: <7AFD34CB-EFF6-4752-82FA-3B55BF8F5DD5@lucidvision.com> References: <52A6F61C.7020504@cisco.com> To: Benoit Claise X-Mailer: Apple Mail (2.1822) Cc: "MIB Doctors \(E-mail\)" , eman mailing list Subject: Re: [eman] [MIB-DOCTORS] DEFINITIONS and MODULE-IDENTITY X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2013 12:50:47 -0000 --Apple-Mail=_6FB722C4-F529-4327-877C-7F7CE1B673DB Content-Type: multipart/alternative; boundary="Apple-Mail=_3BED4C8C-6A8E-44EA-B43A-871876843D53" --Apple-Mail=_3BED4C8C-6A8E-44EA-B43A-871876843D53 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I believe that is the convention that I have always used (and = witnessed). --Tom > MIB doctors, >=20 > One question regarding DEFINITIONS and MODULE-IDENTITY >=20 > Looking at = https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib/, I = see=20 >=20 > ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::=3D BEGIN=20 > =20 > IMPORTS=20 > MODULE-IDENTITY,=20 > OBJECT-TYPE,=20 > mib-2,=20 > Integer32=20 > FROM SNMPv2-SMI =20 > TEXTUAL-CONVENTION, MacAddress, TruthValue=20 > FROM SNMPv2-TC=20 > MODULE-COMPLIANCE,=20 > OBJECT-GROUP =20 > FROM SNMPv2-CONF=20 > SnmpAdminString=20 > FROM SNMP-FRAMEWORK-MIB =20 > InetAddressType, InetAddress=20 > FROM INET-ADDRESS-MIB =20 > entPhysicalIndex=20 > FROM ENTITY-MIB =20 > UUIDorZero=20 > FROM UUID-TC-MIB=20 > IANAEnergyRelationship=20 > FROM IANA-ENERGY-RELATION-MIB; =20 > =20 > energyAwareMIB MODULE-IDENTITY=20 > LAST-UPDATED "201311290000Z"=20 > I guess that ENERGY-OBJECT-CONTEXT-MIB and energyAwareMIB, being = different, would be flagged as a problem by the MIB doctors, correct? >=20 > The closest piece of information is from RFC 4181: > - The descriptor associated with the MODULE-IDENTITY invocation > should be of the form xxxMIB, xxxMib, or xxxMibModule, where xxx = is > a mixed-case version of XXX starting with a lowercase letter and > without any hyphens. For example, the OPT-IF-MIB uses the prefix > optIf, and the descriptor associated with its MODULE-IDENTITY > invocation is optIfMibModule. > Regards, Benoit > _______________________________________________ > MIB-DOCTORS mailing list > MIB-DOCTORS@ietf.org > https://www.ietf.org/mailman/listinfo/mib-doctors --Apple-Mail=_3BED4C8C-6A8E-44EA-B43A-871876843D53 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=iso-8859-1

I believe that is the convention that I have always used (and witnessed).

--Tom


MIB doctors,

One question regarding DEFINITIONS and MODULE-IDENTITY

Looking at https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib/, I see 

       ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::= BEGIN 
         
        IMPORTS 
            MODULE-IDENTITY, 
            OBJECT-TYPE, 
            mib-2, 
            Integer32 
                FROM SNMPv2-SMI  
            TEXTUAL-CONVENTION, MacAddress, TruthValue 
                FROM SNMPv2-TC 
            MODULE-COMPLIANCE, 
            OBJECT-GROUP      
                FROM SNMPv2-CONF 
            SnmpAdminString 
                FROM SNMP-FRAMEWORK-MIB  
            InetAddressType, InetAddress 
               FROM INET-ADDRESS-MIB                  
            entPhysicalIndex 
               FROM ENTITY-MIB     
            UUIDorZero 
               FROM UUID-TC-MIB 
            IANAEnergyRelationship 
               FROM IANA-ENERGY-RELATION-MIB;   
         
        energyAwareMIB MODULE-IDENTITY 
            LAST-UPDATED    "201311290000Z"
I guess that ENERGY-OBJECT-CONTEXT-MIB and energyAwareMIB, being different, would be flagged as a problem by the MIB doctors, correct?

The closest piece of information is from RFC 4181:
 
   - The descriptor associated with the MODULE-IDENTITY invocation
     should be of the form xxxMIB, xxxMib, or xxxMibModule, where xxx is
     a mixed-case version of XXX starting with a lowercase letter and
     without any hyphens.  For example, the OPT-IF-MIB uses the prefix
     optIf, and the descriptor associated with its MODULE-IDENTITY
     invocation is optIfMibModule.
Regards, Benoit
_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/mib-doctors

--Apple-Mail=_3BED4C8C-6A8E-44EA-B43A-871876843D53-- --Apple-Mail=_6FB722C4-F529-4327-877C-7F7CE1B673DB Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJSpw4eAAoJEPcO+I7eiUJZUPoQAJE4S1lk79zFglypIOlxb/GD EIgqwjBhkr3bxWTuJanNHFyJQwgmZ2nz/eVsEgV+0JOGCCcIvs/oCoo9SQmq+jq/ yFA/Y232R728B+4oZIoTAlUqnjTyAA2tQ0/z8pV2cmNfCsHx8tQCnIn6iY6FM5Pr Rj2CL7W0lhzWOd/NI6ibBKtif7bxgXELpwFgYX75tAGNc1bkY+sGeV/GlikSMVJ6 anMJ/1E9PqTjjMjsP7AAX22ep31Cj8c1GilCzcHuVSh5AW826ynPaiIPs/SWoSJP QYIx98FEHqykRDVOOROmn1qT0RSbhMJCtU3gKJNDI+di4YAH3qy+XUaQeTqc1HXI IdkEnQHRwLhbKP0JX6C1qotZMcV33fPXonQoVKv9NJqDfdvpkZN1qHzACRPIeJi6 KFmppikvOAqI9+AigF+817xZXdibcLOC84RHMcy+Zj1kRvSVOScUNYh/OeKTPXpO phYP8FRMfLDI7tegcmUtfmJYOZy8dX4ckSbrndmGAPj9xejstM2amJHA6yW/Vijh aqFst1gqFuxTX6GikpTvN4sgqBqOn/rZlfiVCbT+1dCJjDE7t9/l/POp337bxUIS IpSVyJQvjg5cw7pBqC1IyZveTstcB8AqPnMDtdrbsYFaD6lPbybyVCQYazng0/0n WzKQPSJGLeJTTkKCkCBx =xHur -----END PGP SIGNATURE----- --Apple-Mail=_6FB722C4-F529-4327-877C-7F7CE1B673DB-- From randy_presuhn@mindspring.com Tue Dec 10 11:24:02 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A59751AE067; Tue, 10 Dec 2013 11:24:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4 X-Spam-Level: X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, RCVD_IN_DNSWL_NONE=-0.0001] 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 Mf4J1neAt4GV; Tue, 10 Dec 2013 11:24:00 -0800 (PST) Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 8E51F1AE04B; Tue, 10 Dec 2013 11:24:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=XhQgQKVxxgxvkj7/NUVE5+b6YvKRfVBmFgJBb10Rv5cJCQ//dpabLzf1hR08AZ7D; h=Message-ID:Date:From:Reply-To:To:Subject:Cc:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP; Received: from [209.86.224.36] (helo=elwamui-hybrid.atl.sa.earthlink.net) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1VqSuQ-0001zf-Cu; Tue, 10 Dec 2013 14:23:54 -0500 Received: from 76.254.54.123 by webmail.earthlink.net with HTTP; Tue, 10 Dec 2013 14:23:54 -0500 Message-ID: <1724639.1386703434383.JavaMail.root@elwamui-hybrid.atl.sa.earthlink.net> Date: Tue, 10 Dec 2013 11:23:54 -0800 (GMT-08:00) From: Randy Presuhn To: Benoit Claise , "MIB Doctors (E-mail)" Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailer: EarthLink Zoo Mail 1.0 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8889e105617274a0edb7a740d7ebde1177aa68930385ec65608350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 209.86.224.36 X-Mailman-Approved-At: Tue, 10 Dec 2013 11:25:23 -0800 Cc: eman mailing list Subject: Re: [eman] [MIB-DOCTORS] DEFINITIONS and MODULE-IDENTITY X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Randy Presuhn List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2013 19:24:02 -0000 Hi - >From: Benoit Claise >Sent: Dec 10, 2013 3:08 AM >To: "MIB Doctors (E-mail)" >Cc: eman mailing list , "Mouli Chandramouli (moulchan)" >Subject: [MIB-DOCTORS] DEFINITIONS and MODULE-IDENTITY > >MIB doctors, > >One question regarding DEFINITIONS and MODULE-IDENTITY > >Looking at >https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib/, I see > > ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::= BEGIN > > IMPORTS > MODULE-IDENTITY, > OBJECT-TYPE, > mib-2, > Integer32 > FROM SNMPv2-SMI > TEXTUAL-CONVENTION, MacAddress, TruthValue > FROM SNMPv2-TC > MODULE-COMPLIANCE, > OBJECT-GROUP > FROM SNMPv2-CONF > SnmpAdminString > FROM SNMP-FRAMEWORK-MIB > InetAddressType, InetAddress > FROM INET-ADDRESS-MIB > entPhysicalIndex > FROM ENTITY-MIB > UUIDorZero > FROM UUID-TC-MIB > IANAEnergyRelationship > FROM IANA-ENERGY-RELATION-MIB; > > energyAwareMIBMODULE-IDENTITY > LAST-UPDATED "201311290000Z" > >I guess that ENERGY-OBJECT-CONTEXT-MIB and energyAwareMIB, being >different, would be flagged as a problem by the MIB doctors, correct? > >The closest piece of information is from RFC 4181: > > - The descriptor associated with the MODULE-IDENTITY invocation > should be of the form xxxMIB, xxxMib, or xxxMibModule, where xxx is > a mixed-case version of XXX starting with a lowercase letter and > without any hyphens. For example, the OPT-IF-MIB uses the prefix > optIf, and the descriptor associated with its MODULE-IDENTITY > invocation is optIfMibModule. Abiding by the RFC 4181 *recommendation*, one would expect ENERGY-AWARE-MIB -> energyAwareMib (or variant) or ENERGY-OBJECT-CONTEXT-MIB -> energyObjectContextMib (or variant) The normative language is only a "should", but that implies that they should have a really good reason for disregarding the recommendation. I can't think of a plausible good reason, but they might be able to. Randy From internet-drafts@ietf.org Fri Dec 13 02:56:28 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1A861AE284; Fri, 13 Dec 2013 02:56:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 xHKK6LXQdMe4; Fri, 13 Dec 2013 02:56:27 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 342AD1AE20B; Fri, 13 Dec 2013 02:56:27 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131213105626.29195.82314.idtracker@ietfa.amsl.com> Date: Fri, 13 Dec 2013 02:56:26 -0800 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-energy-aware-mib-12.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2013 10:56:28 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Energy Object Context MIB Author(s) : John Parello Benoit Claise Mouli Chandramouli Filename : draft-ietf-eman-energy-aware-mib-12.txt Pages : 32 Date : 2013-12-13 Abstract: 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 relationships between reporting devices, remote devices, and monitoring devices. = The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-energy-aware-mib-12 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-energy-aware-mib-12 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Fri Dec 13 07:50:05 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA5D01AE2C0; Fri, 13 Dec 2013 07:50:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 mY11wD8f9u6T; Fri, 13 Dec 2013 07:50:04 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A45341AE2FE; Fri, 13 Dec 2013 07:50:03 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131213155003.3496.88993.idtracker@ietfa.amsl.com> Date: Fri, 13 Dec 2013 07:50:03 -0800 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-energy-monitoring-mib-08.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2013 15:50:05 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Power and Energy Monitoring MIB Author(s) : Mouli Chandramouli Benoit Claise Brad Schoening Juergen Quittek Thomas Dietz Filename : draft-ietf-eman-energy-monitoring-mib-08.txt Pages : 77 Date : 2013-12-13 Abstract: This document defines a subset of the Management Information Base (MIB) for power and energy monitoring of devices. = The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-energy-monitoring-mib-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-energy-monitoring-mib-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Fri Dec 13 09:52:58 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA6F21AE02E; Fri, 13 Dec 2013 09:52:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 PGUNTGJFPnde; Fri, 13 Dec 2013 09:52:57 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 91D2E1ACB4E; Fri, 13 Dec 2013 09:52:57 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131213175257.17557.1996.idtracker@ietfa.amsl.com> Date: Fri, 13 Dec 2013 09:52:57 -0800 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-energy-aware-mib-13.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2013 17:52:59 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Energy Object Context MIB Author(s) : John Parello Benoit Claise Mouli Chandramouli Filename : draft-ietf-eman-energy-aware-mib-13.txt Pages : 32 Date : 2013-12-13 Abstract: 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 relationships between reporting devices, remote devices, and monitoring devices. = The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-energy-aware-mib-13 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-energy-aware-mib-13 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From bclaise@cisco.com Fri Dec 13 14:31:36 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 248CB1ADFD6 for ; Fri, 13 Dec 2013 14:31:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.502 X-Spam-Level: X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 uf5QxfYoU3OH for ; Fri, 13 Dec 2013 14:31:34 -0800 (PST) Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id E67261AD694 for ; Fri, 13 Dec 2013 14:31:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=962; q=dns/txt; s=iport; t=1386973888; x=1388183488; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=9hRTiSGBfngD/1asHww6IfKdbLyI3J/QEyobuD6AU2Y=; b=B++qQN579vegZcdP+gRS1pvUHx0QzkhK9rXguCzo3FS1n4w9JYk7+R6M vIj0P2qDlRdwgKlpBCk1PXA2XuyQElGkgve80vBerTTNQYzSSDj+oddmu Deo4qTjFkayVHUZ3s5cRSfQjkdGTa0xD33Aa8koPXcgUC0lU3G4qAz5b1 U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhAFAGaJq1KQ/khL/2dsb2JhbABQCYMKuxIWdIJkQD0WGAMCAQIBSwEMCAEBiADLFReOLQ2FGAEDmBaGRYtPgWyBPzs X-IronPort-AV: E=Sophos;i="4.95,482,1384300800"; d="scan'208";a="1618208" Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-2.cisco.com with ESMTP; 13 Dec 2013 22:31:27 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rBDMVNoQ010529; Fri, 13 Dec 2013 22:31:23 GMT Message-ID: <52AB8ABB.2080901@cisco.com> Date: Fri, 13 Dec 2013 23:31:23 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: eman mailing list , draft-ietf-eman-battery-mib@tools.ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [eman] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2013 22:31:36 -0000 Dear all, During the last IETF meeting, there was an agreement to go for a single energyMIB OID under mib-2. energyObjectContextMIB MODULE-IDENTITY (draft-ietf-eman-energy-aware-mib) is under energyMIB.1 ianaEnergyRelationMIB MODULE-IDENTITY (draft-ietf-eman-energy-aware-mib) is under energyMIB.2 energyObjectMIB MODULE-IDENTITY (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.3 powerAttributesMIB MODULE-IDENTITY (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.4 For draft-ietf-eman-battery-mib, you can start with energyMIB.5 Note that draft-ietf-eman-energy-aware-mib requests: Descriptor OBJECT IDENTIFIER value ---------- ----------------------- energyMIB { mib-2 XXX } Btw, both draft-ietf-eman-energy-aware-mib and draft-ietf-eman-energy-monitoring-mib are ready for WGLC. Regards, Benoit From j.schoenwaelder@jacobs-university.de Sat Dec 14 00:39:54 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D12131AE518 for ; Sat, 14 Dec 2013 00:39:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.251 X-Spam-Level: X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] 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 quH61pgUVOIA for ; Sat, 14 Dec 2013 00:39:44 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 950011AE245 for ; Sat, 14 Dec 2013 00:39:44 -0800 (PST) Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 7B62C20082; Sat, 14 Dec 2013 09:39:37 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id pSKWWKbbPZs4; Sat, 14 Dec 2013 09:39:37 +0100 (CET) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id ADCEF20081; Sat, 14 Dec 2013 09:39:36 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id 33B6B29FFB1D; Sat, 14 Dec 2013 09:39:30 +0100 (CET) Date: Sat, 14 Dec 2013 09:39:30 +0100 From: Juergen Schoenwaelder To: Benoit Claise Message-ID: <20131214083930.GA86143@elstar.local> Mail-Followup-To: Benoit Claise , eman mailing list , draft-ietf-eman-battery-mib@tools.ietf.org References: <52AB8ABB.2080901@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52AB8ABB.2080901@cisco.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: eman mailing list , draft-ietf-eman-battery-mib@tools.ietf.org Subject: Re: [eman] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2013 08:39:54 -0000 Hi, in the past such registration spaces led to problems (I think RMON was the case) and I think because of that we moved pretty much all registrations below mib-2 and transmission. Bert Wijnen might recall the details. If we change our strategy, we should probably have strong reasons and understand the longer term implications. There is the relvant quote from RFC 4181: - The value assigned to the MODULE-IDENTITY descriptor MUST be unique and (for IETF standards-track MIB modules) SHOULD reside under the mgmt subtree [RFC2578]. Most often it will be an IANA-assigned value directly under mib-2 [RFC2578], although for media-specific MIB modules that extend the IF-MIB [RFC2863] it is customary to use an IANA-assigned value under transmission [RFC2578]. In the past, some IETF working groups have made their own assignments from subtrees delegated to them by IANA, but that practice has proven problematic and is NOT RECOMMENDED. /js On Fri, Dec 13, 2013 at 11:31:23PM +0100, Benoit Claise wrote: > Dear all, > > During the last IETF meeting, there was an agreement to go for a > single energyMIB OID under mib-2. > > energyObjectContextMIB MODULE-IDENTITY > (draft-ietf-eman-energy-aware-mib) is under energyMIB.1 > ianaEnergyRelationMIB MODULE-IDENTITY > (draft-ietf-eman-energy-aware-mib) is under energyMIB.2 > energyObjectMIB MODULE-IDENTITY > (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.3 > powerAttributesMIB MODULE-IDENTITY > (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.4 > > For draft-ietf-eman-battery-mib, you can start with energyMIB.5 > Note that draft-ietf-eman-energy-aware-mib requests: > > Descriptor OBJECT IDENTIFIER value > ---------- ----------------------- > > energyMIB { mib-2 XXX } > > > Btw, both draft-ietf-eman-energy-aware-mib and > draft-ietf-eman-energy-monitoring-mib are ready for WGLC. > > Regards, Benoit > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From bclaise@cisco.com Sat Dec 14 01:14:41 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BEB01ADF84; Sat, 14 Dec 2013 01:14:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.502 X-Spam-Level: X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 Fm-mNhevlDke; Sat, 14 Dec 2013 01:14:35 -0800 (PST) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id AADA91ADF8B; Sat, 14 Dec 2013 01:13:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3084; q=dns/txt; s=iport; t=1387012387; x=1388221987; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=MBwjy88wCqKto077c7MfsfGKnyWUEmR+xnm4ARWEELg=; b=HNexhW8Nvix4Z3pqNtR/CL+b5QJzeBuu9KoRn1mgVC+oRQWiH7LiNHRY 4Xy30kk5DUBUJLrppT1tafPhqK454SnyaK3Yq44MUAbyIi0TxiQWCvbG7 sr9Hfm46dEezhQMwAJetyBdALOMURnUr86v5gYHomClCJGNPDAsiMVD2B 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhYFAFsgrFKQ/khR/2dsb2JhbABQCYMKOLk2gR4WdIIlAQEBAwEBAQEvAQU2CgYLCxgJFgQLCQMCAQIBFTAGAQwGAgEBBYdzCA3KHReOMQYHCQIBVoQ2AQOYFoZFi0+BbIE/Ow X-IronPort-AV: E=Sophos;i="4.95,484,1384300800"; d="scan'208";a="2246301" Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-1.cisco.com with ESMTP; 14 Dec 2013 09:13:06 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rBE9D6Ho011263; Sat, 14 Dec 2013 09:13:06 GMT Message-ID: <52AC2122.4000204@cisco.com> Date: Sat, 14 Dec 2013 10:13:06 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: eman mailing list , draft-ietf-eman-battery-mib@tools.ietf.org, "MIB Doctors (E-mail)" References: <52AB8ABB.2080901@cisco.com> <20131214083930.GA86143@elstar.local> In-Reply-To: <20131214083930.GA86143@elstar.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [eman] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2013 09:14:41 -0000 Hi Jürgen, MIB doctors, Jürgen, I wish you had reacted when this email was posted: http://www.ietf.org/mail-archive/web/eman/current/msg02064.html, or during the WG meeting where it was discussed (too bad that the meeting minutes didn't cover that level of details). While I understand that assigning a MODULE-IDENTITY descriptor could be problematic, here it's different: this unique MODULE-IDENTITY descriptor is for related MIB modules, and this happens to be a WG in this case. We have 3 MIB documents containing 5 MIB modules, all related to Energy: 2 are for Textual Conventions 3 are interconnected: the second and third ones require some objects to be implemented in the first one. MIB doctors, Let us know your advice Regards, Benoit > Hi, > > in the past such registration spaces led to problems (I think RMON was > the case) and I think because of that we moved pretty much all > registrations below mib-2 and transmission. Bert Wijnen might recall > the details. If we change our strategy, we should probably have strong > reasons and understand the longer term implications. There is the relvant > quote from RFC 4181: > > - The value assigned to the MODULE-IDENTITY descriptor MUST be unique > and (for IETF standards-track MIB modules) SHOULD reside under the > mgmt subtree [RFC2578]. Most often it will be an IANA-assigned > value directly under mib-2 [RFC2578], although for media-specific > MIB modules that extend the IF-MIB [RFC2863] it is customary to use > an IANA-assigned value under transmission [RFC2578]. In the past, > some IETF working groups have made their own assignments from > subtrees delegated to them by IANA, but that practice has proven > problematic and is NOT RECOMMENDED. > > /js > > On Fri, Dec 13, 2013 at 11:31:23PM +0100, Benoit Claise wrote: >> Dear all, >> >> During the last IETF meeting, there was an agreement to go for a >> single energyMIB OID under mib-2. >> >> energyObjectContextMIB MODULE-IDENTITY >> (draft-ietf-eman-energy-aware-mib) is under energyMIB.1 >> ianaEnergyRelationMIB MODULE-IDENTITY >> (draft-ietf-eman-energy-aware-mib) is under energyMIB.2 >> energyObjectMIB MODULE-IDENTITY >> (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.3 >> powerAttributesMIB MODULE-IDENTITY >> (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.4 >> >> For draft-ietf-eman-battery-mib, you can start with energyMIB.5 >> Note that draft-ietf-eman-energy-aware-mib requests: >> >> Descriptor OBJECT IDENTIFIER value >> ---------- ----------------------- >> >> energyMIB { mib-2 XXX } >> >> >> Btw, both draft-ietf-eman-energy-aware-mib and >> draft-ietf-eman-energy-monitoring-mib are ready for WGLC. >> >> Regards, Benoit >> >> >> _______________________________________________ >> eman mailing list >> eman@ietf.org >> https://www.ietf.org/mailman/listinfo/eman From tnadeau@lucidvision.com Sat Dec 14 06:06:17 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FCA61AD84D for ; Sat, 14 Dec 2013 06:06:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 A2jaqEb11x_6 for ; Sat, 14 Dec 2013 06:05:35 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 4CEBC1AE04A for ; Sat, 14 Dec 2013 06:05:22 -0800 (PST) Received: from [192.168.1.102] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id F37672687C39; Sat, 14 Dec 2013 09:05:15 -0500 (EST) References: <52AB8ABB.2080901@cisco.com> <20131214083930.GA86143@elstar.local> Mime-Version: 1.0 (1.0) In-Reply-To: <20131214083930.GA86143@elstar.local> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPad Mail (11B554a) From: Thomas D Nadeau Date: Sat, 14 Dec 2013 09:05:14 -0500 To: Juergen Schoenwaelder Cc: eman mailing list , "draft-ietf-eman-battery-mib@tools.ietf.org" Subject: Re: [eman] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2013 14:06:17 -0000 FYI we followed a single OID model with the MPLS, CCAMP, and PWE3 MIBs and o= ver time have had no issues around the OID. It was actually convenient to h= ave the grouped that way. --Tom > On Dec 14, 2013, at 3:39 AM, Juergen Schoenwaelder wrote: >=20 > Hi, >=20 > in the past such registration spaces led to problems (I think RMON was > the case) and I think because of that we moved pretty much all > registrations below mib-2 and transmission. Bert Wijnen might recall > the details. If we change our strategy, we should probably have strong > reasons and understand the longer term implications. There is the relvant > quote from RFC 4181: >=20 > - The value assigned to the MODULE-IDENTITY descriptor MUST be unique > and (for IETF standards-track MIB modules) SHOULD reside under the > mgmt subtree [RFC2578]. Most often it will be an IANA-assigned > value directly under mib-2 [RFC2578], although for media-specific > MIB modules that extend the IF-MIB [RFC2863] it is customary to use > an IANA-assigned value under transmission [RFC2578]. In the past, > some IETF working groups have made their own assignments from > subtrees delegated to them by IANA, but that practice has proven > problematic and is NOT RECOMMENDED. >=20 > /js >=20 >> On Fri, Dec 13, 2013 at 11:31:23PM +0100, Benoit Claise wrote: >> Dear all, >>=20 >> During the last IETF meeting, there was an agreement to go for a >> single energyMIB OID under mib-2. >>=20 >> energyObjectContextMIB MODULE-IDENTITY >> (draft-ietf-eman-energy-aware-mib) is under energyMIB.1 >> ianaEnergyRelationMIB MODULE-IDENTITY >> (draft-ietf-eman-energy-aware-mib) is under energyMIB.2 >> energyObjectMIB MODULE-IDENTITY >> (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.3 >> powerAttributesMIB MODULE-IDENTITY >> (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.4 >>=20 >> For draft-ietf-eman-battery-mib, you can start with energyMIB.5 >> Note that draft-ietf-eman-energy-aware-mib requests: >>=20 >> Descriptor OBJECT IDENTIFIER value >> ---------- ----------------------- >>=20 >> energyMIB { mib-2 XXX } >>=20 >>=20 >> Btw, both draft-ietf-eman-energy-aware-mib and >> draft-ietf-eman-energy-monitoring-mib are ready for WGLC. >>=20 >> Regards, Benoit >>=20 >>=20 >> _______________________________________________ >> eman mailing list >> eman@ietf.org >> https://www.ietf.org/mailman/listinfo/eman >=20 > --=20 > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany > Fax: +49 421 200 3103 > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman >=20 From j.schoenwaelder@jacobs-university.de Sat Dec 14 07:27:25 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 636BD1ADBD1; Sat, 14 Dec 2013 07:27:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.251 X-Spam-Level: X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] 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 f0c_sh27G9MF; Sat, 14 Dec 2013 07:27:20 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 8E17D1AE1B5; Sat, 14 Dec 2013 07:27:20 -0800 (PST) Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 589092006A; Sat, 14 Dec 2013 16:27:13 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id JJwQXTOnq_19; Sat, 14 Dec 2013 16:27:13 +0100 (CET) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id E2C6320062; Sat, 14 Dec 2013 16:27:12 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id B4AE129FFFF6; Sat, 14 Dec 2013 16:27:07 +0100 (CET) Date: Sat, 14 Dec 2013 16:27:07 +0100 From: Juergen Schoenwaelder To: Benoit Claise Message-ID: <20131214152706.GA86891@elstar.local> Mail-Followup-To: Benoit Claise , eman mailing list , draft-ietf-eman-battery-mib@tools.ietf.org, "MIB Doctors (E-mail)" References: <52AB8ABB.2080901@cisco.com> <20131214083930.GA86143@elstar.local> <52AC2122.4000204@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52AC2122.4000204@cisco.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "MIB Doctors \(E-mail\)" , eman mailing list , draft-ietf-eman-battery-mib@tools.ietf.org Subject: Re: [eman] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2013 15:27:25 -0000 On Sat, Dec 14, 2013 at 10:13:06AM +0100, Benoit Claise wrote: > While I understand that assigning a MODULE-IDENTITY descriptor could > be problematic, here it's different: this unique MODULE-IDENTITY > descriptor is for related MIB modules, and this happens to be a WG > in this case. > We have 3 MIB documents containing 5 MIB modules, all related to Energy: > 2 are for Textual Conventions > 3 are interconnected: the second and third ones require some > objects to be implemented in the first one. I think bad experience was made with RMON but I am not 100% sure. Things may start in one WG but later get out of control. For stuff below mib-2 and transmission, there is a defined registry. What do you gain by a single OID? The single walk argument? Well, even the IF-MIB is in two branches. And who knows what other stuff might be put under the common OID root in the future. Decent management applications likely don't walk arbitrary subtrees (but if OID based MIB browsers is all we have, well then there might be some value). /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From andy@yumaworks.com Sat Dec 14 09:02:51 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD7501AE232 for ; Sat, 14 Dec 2013 09:02:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable 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 07g7KcTOnzgy for ; Sat, 14 Dec 2013 09:02:49 -0800 (PST) Received: from mail-qc0-f178.google.com (mail-qc0-f178.google.com [209.85.216.178]) by ietfa.amsl.com (Postfix) with ESMTP id 3E1271AE252 for ; Sat, 14 Dec 2013 08:48:30 -0800 (PST) Received: by mail-qc0-f178.google.com with SMTP id i17so2493891qcy.23 for ; Sat, 14 Dec 2013 08:48:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=jaRGUE7FN/HsP5wz+lC2vhC5MBLXVPLzn0J7Si+Mh9U=; b=MetfyYM43WIJoGqe0LBQ2HXPWaXjmag3sbTHedlpHUd33lHAFdFHZWOFM42Hqz873Q mGameDmVAXQd6mlQnMeZnr3A+99f+fkeb6Q9PaoHX2AOmhDPWuysMRCO619wo6s+A9Kh ZuVxfQ5zWQrrWgJ2b49ocS2ztWZ+kZxJoxREZjb1cMjVJro7lnHaxc7enKl8DNWKkN91 9NkMNewCzU/EBm26/Kv5EvIPy1lUG/wP1/iBqwVI0GsvDozA6oYHCXwa/I8oKkcU0rh6 FpnSIezsPB2N/2pQKR0P598n4mO4o+1dYqTOU/f4oEDlIOjfWBIEOoAVixm4mBPk4zaw JF1g== X-Gm-Message-State: ALoCoQlLgq11wGpojVHk6rI8NPXQcSNAlauH20z9sK8Za5LszCgjj1eg+rFoDpHaQqXfffvMOoNO MIME-Version: 1.0 X-Received: by 10.224.60.69 with SMTP id o5mr16316876qah.92.1387039703295; Sat, 14 Dec 2013 08:48:23 -0800 (PST) Received: by 10.140.48.75 with HTTP; Sat, 14 Dec 2013 08:48:23 -0800 (PST) In-Reply-To: <20131214152706.GA86891@elstar.local> References: <52AB8ABB.2080901@cisco.com> <20131214083930.GA86143@elstar.local> <52AC2122.4000204@cisco.com> <20131214152706.GA86891@elstar.local> Date: Sat, 14 Dec 2013 08:48:23 -0800 Message-ID: From: Andy Bierman To: Juergen Schoenwaelder , Benoit Claise , eman mailing list , draft-ietf-eman-battery-mib@tools.ietf.org, "MIB Doctors (E-mail)" Content-Type: multipart/alternative; boundary=001a11c3e488cdfee104ed81587d Subject: Re: [eman] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2013 17:02:52 -0000 --001a11c3e488cdfee104ed81587d Content-Type: text/plain; charset=ISO-8859-1 Hi, I was RMONMIB WG chair and I do remember there was concern after RMON had done this about 8 times. I think a CLR was created to prevent any attempt at data organization done by WGs. I think the reason was that the WG assigned a real OID in an I-D. People thought it was better to have XXX instead of a real number. If the I-D did not get published as an I-D, then an OID number was wasted. Only IANA can assign XXX to make sure only published RFCs get real OIDs. Andy On Sat, Dec 14, 2013 at 7:27 AM, Juergen Schoenwaelder < j.schoenwaelder@jacobs-university.de> wrote: > On Sat, Dec 14, 2013 at 10:13:06AM +0100, Benoit Claise wrote: > > > While I understand that assigning a MODULE-IDENTITY descriptor could > > be problematic, here it's different: this unique MODULE-IDENTITY > > descriptor is for related MIB modules, and this happens to be a WG > > in this case. > > We have 3 MIB documents containing 5 MIB modules, all related to Energy: > > 2 are for Textual Conventions > > 3 are interconnected: the second and third ones require some > > objects to be implemented in the first one. > > I think bad experience was made with RMON but I am not 100% > sure. Things may start in one WG but later get out of control. For > stuff below mib-2 and transmission, there is a defined registry. > > What do you gain by a single OID? The single walk argument? Well, even > the IF-MIB is in two branches. And who knows what other stuff might be > put under the common OID root in the future. Decent management > applications likely don't walk arbitrary subtrees (but if OID based > MIB browsers is all we have, well then there might be some value). > > /js > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany > Fax: +49 421 200 3103 > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > --001a11c3e488cdfee104ed81587d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I was RMONMIB WG chair and I do rem= ember there was concern
after RMON had done this about 8 times. I= think a CLR was created
to prevent any attempt at data organizat= ion done by WGs.
I think the reason was that the WG assigned a real OID in an I-D.
People thought it was better to have XXX instead of a
real = number. =A0If the I-D did not get published as an I-D, then
an OI= D number was wasted. Only IANA can assign XXX to
make sure only published RFCs get real OIDs.


<= div class=3D"gmail_extra">Andy



On Sat, Dec 14, 2013 at 7:27 AM, Juergen Schoenw= aelder <j.schoenwaelder@jacobs-university.de> wrote:
On Sat, Dec 14, 2013 at 10:13:06AM +0100, Be= noit Claise wrote:

> While I understand that assigning a MODULE-IDENTITY descriptor could > be problematic, here it's different: this unique MODULE-IDENTITY > descriptor is for related MIB modules, and this happens to be a WG
> in this case.
> We have 3 MIB documents containing 5 MIB modules, all related to Energ= y:
> =A0 =A0 2 are for Textual Conventions
> =A0 =A0 3 are interconnected: the second and third ones require some > objects to be implemented in the first one.

I think bad experience was made with RMON but I am not 100%
sure. Things may start in one WG but later get out of control. For
stuff below mib-2 and transmission, there is a defined registry.

What do you gain by a single OID? The single walk argument? Well, even
the IF-MIB is in two branches. And who knows what other stuff might be
put under the common OID root in the future. Decent management
applications likely don't walk arbitrary subtrees (but if OID based
MIB browsers is all we have, well then there might be some value).

/js

--
Juergen Schoenwaelder =A0 =A0 =A0 =A0 =A0 Jacobs University Bremen gGmbH Phone: +49 421 200 3587 =A0 =A0 =A0 =A0 Campus Ring 1, 28759 Bremen, German= y
Fax: =A0 +49 421 200 3103 =A0 =A0 =A0 =A0 <http://www.jacobs-university.de/><= br> _______________________________________________
eman mailing list
eman@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/eman

--001a11c3e488cdfee104ed81587d-- From randy_presuhn@mindspring.com Sat Dec 14 11:23:18 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9273D1AE27F; Sat, 14 Dec 2013 11:23:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] 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 pcWKRAvCrz8j; Sat, 14 Dec 2013 11:23:15 -0800 (PST) Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 62C7B1ADFF7; Sat, 14 Dec 2013 11:23:14 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=dnxrgNCHjRtHotnrL6PuUEze/8L31KnPMhsPoUY0lVU3e0BgR/mOHrj5HllP+6QM; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP; Received: from [209.86.224.35] (helo=elwamui-huard.atl.sa.earthlink.net) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1Vruna-00046c-Ce; Sat, 14 Dec 2013 14:22:50 -0500 Received: from 76.254.54.154 by webmail.earthlink.net with HTTP; Sat, 14 Dec 2013 14:22:50 -0500 Message-ID: <32654121.1387048970369.JavaMail.root@elwamui-huard.atl.sa.earthlink.net> Date: Sat, 14 Dec 2013 11:22:50 -0800 (GMT-08:00) From: Randy Presuhn To: Benoit Claise , eman mailing list , draft-ietf-eman-battery-mib@tools.ietf.org, "MIB Doctors (E-mail)" Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailer: EarthLink Zoo Mail 1.0 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8889e105617274a0edb4ba15379da6d40bdc55b79e56e2e1da1350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 209.86.224.35 X-Mailman-Approved-At: Sun, 15 Dec 2013 08:11:36 -0800 Subject: Re: [eman] [MIB-DOCTORS] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Randy Presuhn List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2013 19:23:21 -0000 Hi - >From: Benoit Claise >Sent: Dec 14, 2013 1:13 AM >To: eman mailing list , draft-ietf-eman-battery-mib@tools.i= etf.org, "MIB Doctors (E-mail)" >Subject: Re: [MIB-DOCTORS] [eman] A single OID for energy and the 3 EMAN M= IBs (message to draft-ietf-eman-battery-mib authors) > >Hi J=C3=BCrgen, MIB doctors, > >J=C3=BCrgen, >I wish you had reacted when this email was posted:=20 >http://www.ietf.org/mail-archive/web/eman/current/msg02064.html, or=20 >during the WG meeting where it was discussed (too bad that the meeting=20 >minutes didn't cover that level of details). > >While I understand that assigning a MODULE-IDENTITY descriptor could be=20 >problematic, here it's different: this unique MODULE-IDENTITY descriptor= =20 >is for related MIB modules, and this happens to be a WG in this case. >We have 3 MIB documents containing 5 MIB modules, all related to Energy: > 2 are for Textual Conventions > 3 are interconnected: the second and third ones require some=20 >objects to be implemented in the first one. ... It's not forbidden, it's just not recommended, due to bad experiences in the past. So the question becomes one of figuring out what would be sufficient reason to disregard the recommendation. So what *does* such a registration accomplish? It means that the "related" MIB modules have one more leading subidentifier in common than if they had been registered conventionally, and that this subidentifier can be used to distinguish them as a group from other MIB modules. But what does *that* accomplish? I can only think of two possible benefits. 1) IFF all these MIB modules are implemented in a single process by a single logical subagent, then only one SMUX or AgentX registration request, rather than three, would be needed. In the implementations with which I am most familiar, the cost of slightly longer OID operations would be a wash when compared to the increased number of subtrees known to the master agent. In the subagent itself, the one-time savings in a smaller number of registrations would be eaten up over time by the slightly longer OID operations in SMUX, less so in Agentx. (However, for purposes of maintaining sysORTable, the subagent would probably still register all three subtrees, thus resulting in a net increase in processing cost due to the longer OIDs.) (Also, the subagent code generation tools with which I am most familiar do not generate code to support registrations "above" a compiled MIB module.) 2) Similar to the subagent question, the proposed registration structure could, for each distinct access control policy specifically concerned with these MIB modules, reduce the number of entries in the vacmViewTreeFamilyTable by as much as two, though the vacmViewTreeFamilySubtree and vacmViewTreeFamilyMask would be correspondingly longer. Of course, whether one's management tools would know to "merge" the policies for "lexicographically related" MIB modules is a question for the management tool vendors. I suspect that the tools probably *don't* know how to do this kind of optimization, and that there are too few cases where it happens to make such an optimization worthwhile. In short, I find both of these lines of reasoning entirely unconvincing as arguments for disregarding registration conventions. Perhaps the working group could explain what they thought they would gain by doing such a registration. Randy From tnadeau@lucidvision.com Mon Dec 16 07:56:04 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FED11AE362 for ; Mon, 16 Dec 2013 07:56:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.438 X-Spam-Level: X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] 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 16UZq0laGT-T for ; Mon, 16 Dec 2013 07:56:03 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 2137B1AE02D for ; Mon, 16 Dec 2013 07:56:03 -0800 (PST) Received: from [192.168.1.112] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 4EB3C268A20C; Mon, 16 Dec 2013 10:56:02 -0500 (EST) Content-Type: multipart/signed; boundary="Apple-Mail=_440782C9-2B61-43AF-99C2-CA3B5D685E6F"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) From: Thomas Nadeau In-Reply-To: <52AB8777.9060704@cisco.com> Date: Mon, 16 Dec 2013 10:56:01 -0500 Message-Id: <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> To: eman mailing list X-Mailer: Apple Mail (2.1822) Subject: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 15:56:04 -0000 --Apple-Mail=_440782C9-2B61-43AF-99C2-CA3B5D685E6F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 As agreed at the last WG meeting, with the EMAN Framework = completing its WG LC the chairs would like to initiate a WG LC on = draft-ietf-eman-energy-monitoring-mib-08 and = draft-ietf-eman-energy-aware-mib-13. The WG LC will end on Dec 30 at = 8AM EDT.=20 Thank you, Nevil and Tom --Apple-Mail=_440782C9-2B61-43AF-99C2-CA3B5D685E6F Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJSryKRAAoJEPcO+I7eiUJZoIIQAIvzUX/MAsEzczQOwDV2Jtka TkbGt+esoif29pBJxSY8hVOeMlTbIBbnBBIkoMSM/NzpqFNUmywvI962W9xw5DoD lSvdjRI/PDvS4E+zabXtEs+Va66Q7tcG796Wd62bAlgHI0/IKMCw/iTKZ9XMkdd1 YKbucYl82dYFX3wBQUaLN3MIHxDUoWqalNVfEMCeDWdEBiby5EOYaAVjE3n6oLgP AITD86JhoR4zyTk2PbNWV6MEC/8jBz3oZqVU5/rTZj2MmA3ZA5awOvUp92rNOSJ2 /0rH+ewulceK5X+w+cWiWuhkRtoCb3ixZ8i7lPhT9VubfnDGXLH+G4oE4xjjrEa5 VtuJHVnmb3aDeg8RXB4AOcDzfBa8GMLbFAghHj4SjDwDnfoyjCn7w7YAJDetvfhU pJqCtjn+FIu56gnz0q5llEqpE8rdatDnOEJpDpvTr8HOqTr5ukoPQcorImza0AcO ddgUNx/yYQU6GwwF22nzUyhQ314VAIHUutzdWvjWNH2nfUDLNjwehJl2IcDDwI+W lmyikOFJmCoAipzyFtBx3t3zvW/MUU1mkkHE3MXYZ5oDA7GK5PhulgGs7mqqsVSG 7K1tZ0IsINlpnX66AJcxApXlMhQ/BMBuhq2te8w9ZWv1VWGKLTPmMXcdcUVB+2Jo SBrxZOsqLxMAlnGwop86 =vqgD -----END PGP SIGNATURE----- --Apple-Mail=_440782C9-2B61-43AF-99C2-CA3B5D685E6F-- From tnadeau@lucidvision.com Mon Dec 16 08:06:08 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7D311AE317 for ; Mon, 16 Dec 2013 08:06:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.438 X-Spam-Level: X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] 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 QjO_7wxPQtf7 for ; Mon, 16 Dec 2013 08:06:06 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id B268E1AE046 for ; Mon, 16 Dec 2013 08:06:06 -0800 (PST) Received: from [192.168.1.112] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 9C188268A291; Mon, 16 Dec 2013 11:06:05 -0500 (EST) From: Thomas Nadeau Content-Type: multipart/signed; boundary="Apple-Mail=_315BA7D5-0EF8-4D78-85CC-1BA9FF7688D3"; protocol="application/pgp-signature"; micalg=pgp-sha512 Date: Mon, 16 Dec 2013 11:06:04 -0500 Message-Id: To: eman mailing list Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) X-Mailer: Apple Mail (2.1822) Cc: draft-ietf-eman-framework@tools.ietf.org, eman-chairs@tools.ietf.org Subject: [eman] IPR Poll: draft-ietf-eman-framework X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 16:06:08 -0000 --Apple-Mail=_315BA7D5-0EF8-4D78-85CC-1BA9FF7688D3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii =09 This mail starts the IPR poll on draft-ietf-eman-framework. Are you aware of any IPR that applies to draft-ietf-eman-framework? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to this email explicitly regardless of whether or not you are aware of any = relevant IPR. *The response needs to be sent to the EMAN wg mailing list.* The document will not advance to the next stage until a response has been received from each author and contributor. If you are on the EMAN WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thank you, Nevil and Tom, EMAN WG Chairs --Apple-Mail=_315BA7D5-0EF8-4D78-85CC-1BA9FF7688D3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJSryTsAAoJEPcO+I7eiUJZ7WAP/j2AEoEe4Do/rc/i/Rddeb7+ H8DMvrrRW4Uy8lqZgyFv2nzzjdbKArug8YtVp7VFlAx/q8uY3M+xgJINO/Ud3SFL mdglNZiyydVbILBjNl/bn/AOM3toMUeEqpfcznao7mQbQF5VM/sj8Sh6PfAEtol5 KaIgqykmASNmF7Kv/k6agGgu0xZ4I2dsPNv0rEu7yDpT6pnyHWTIKTtZoGrZEmK+ XY1690EbncRpZZlNtpi+uO8xO8R4bGY+uPtxiemAD/X2/wOFNSW39OupPOUZZdyy q51Rq6mKJjnat+Qai0kPRpyWmYZ7MENAQlcpnbS/lfPobgWweXtyeJ48DlT2O/8K 7Vd47XD1C1xmTDK7cs17nmzpmeOPwQ8bwcDkTZMWjp5XIHRwYRCt/COc4SOna54Q zd1U/y2LXjkIriZAUTGIIycSwmU9yborGA2R/Z9ZG4M9OsjQmpSh8PVpfGlnm+S0 9S5lQGvg8imNu7ZOY8UEuZKHkQgMwth6GpFz0lGj1PjX5DoCZBpWHtcZUaTwLfCC AvmaQRC7jA3yzQ/sg4UK/tpjQxR9QNghyjur/CiTplwW+g2qyQMPeUWIpcG3lc6h cekQJC9uSin5S8mfuOEBsBtUokaJmha3KOj6yoXFLT66GdXqq9Q1UAVpb7hgcoJa 1puaeihPG3jHvnEmP0hM =9HMx -----END PGP SIGNATURE----- --Apple-Mail=_315BA7D5-0EF8-4D78-85CC-1BA9FF7688D3-- From tnadeau@lucidvision.com Mon Dec 16 08:06:11 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9B61AE354 for ; Mon, 16 Dec 2013 08:06:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.438 X-Spam-Level: X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] 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 XFPS6FupeDUF for ; Mon, 16 Dec 2013 08:06:10 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 23C481AE317 for ; Mon, 16 Dec 2013 08:06:09 -0800 (PST) Received: from [192.168.1.112] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 63836268A296; Mon, 16 Dec 2013 11:06:08 -0500 (EST) From: Thomas Nadeau Content-Type: multipart/signed; boundary="Apple-Mail=_DCC83585-BA77-4543-8B05-678D6AA55E35"; protocol="application/pgp-signature"; micalg=pgp-sha512 Date: Mon, 16 Dec 2013 11:06:08 -0500 Message-Id: <36DA8D84-C6D5-4A55-8B4A-2D155B449928@lucidvision.com> To: eman mailing list Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) X-Mailer: Apple Mail (2.1822) Cc: draft-ietf-eman-energy-monitoring-mib@tools.ietf.org, eman-chairs@tools.ietf.org Subject: [eman] IPR Poll: draft-ietf-eman-energy-monitoring-mib-08 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 16:06:11 -0000 --Apple-Mail=_DCC83585-BA77-4543-8B05-678D6AA55E35 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii =09 This mail starts the IPR poll on draft-ietf-eman-energy-monitoring-mib. Are you aware of any IPR that applies to = draft-ietf-eman-energy-monitoring-mib? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to this email explicitly regardless of whether or not you are aware of any = relevant IPR. *The response needs to be sent to the EMAN wg mailing list.* The document will not advance to the next stage until a response has been received from each author and contributor. If you are on the EMAN WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thank you, Nevil and Tom, EMAN WG Chairs --Apple-Mail=_DCC83585-BA77-4543-8B05-678D6AA55E35 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJSryTwAAoJEPcO+I7eiUJZ8zwQAIncTJa7aYusOMM5yl/FOHKj uZTKcmWfrTzLYZ7xBIjgj+egxlrjqSeZQYrvxsWb8Wbd9y7/htCrCD1uk5PsXavM JUSXn2h3s4ep8vr9Ov4SmRbOvMzx4Q5c2KemeFVeCgYn2/HNnYIBNuNhV9GyWiLL Uvyi85COT4/uw+Imqf7M1M6vjooKGZiJReA6KCnV+luK6cr5TcsuTf0N05QaTAxw pK/zMwT/ML5szvW6TF0HkPOFN/TnXhcnSOAnnp26OMJkVSTmVKw+PJRBuJhcdu4H oBBLNRvgusggFkGjVYHHRZK2UiSi9oIbAlYCoHIJMoUh3yz+0tfhJamvgnlNbdni eyFmORuIlDTLMiSkMKuvZMAiDALaRRAEoBJV+99KMGFOXWcbsx8i10Rdgg0Khrz6 h+N1+gNx1SAN7YYhRN5olDPplFwyXHA7XIoUr0wX8zg9D+93cpTwvbSo+5R2OQQZ pdYK5a/nHvhHkrZdOdoKge5fW/yNxEA5DTKaK1RS80MO9XAk2+g1cqZPN6CxAf8T xZ8f9dHSm81+Ijgy7yEWIaY5e4mBaHI/eFEdatKkaUqSIZMq5ZJXRlgPBNYhlyo6 VA5Od11g40h8Gbi6DB9rm9Pcd2Z99wjbgk+QOat7Z+6JcJDDzGXtLYQqhoyLwRm3 PBHO0Uy+HbkmJNh7Z64+ =ftiQ -----END PGP SIGNATURE----- --Apple-Mail=_DCC83585-BA77-4543-8B05-678D6AA55E35-- From tnadeau@lucidvision.com Mon Dec 16 08:06:16 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2588B1AE317 for ; Mon, 16 Dec 2013 08:06:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.438 X-Spam-Level: X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] 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 bfTnSQjHI9wb for ; Mon, 16 Dec 2013 08:06:15 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id BD4A91A9313 for ; Mon, 16 Dec 2013 08:06:14 -0800 (PST) Received: from [192.168.1.112] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 0DFDE268A2A5; Mon, 16 Dec 2013 11:06:14 -0500 (EST) From: Thomas Nadeau Content-Type: multipart/signed; boundary="Apple-Mail=_EDFA2558-4910-455D-B9B1-639C516F7E6E"; protocol="application/pgp-signature"; micalg=pgp-sha512 Date: Mon, 16 Dec 2013 11:06:13 -0500 Message-Id: To: eman mailing list Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) X-Mailer: Apple Mail (2.1822) Cc: draft-ietf-eman-energy-aware-mib@tools.ietf.org, eman-chairs@tools.ietf.org Subject: [eman] IPR Poll: draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 16:06:16 -0000 --Apple-Mail=_EDFA2558-4910-455D-B9B1-639C516F7E6E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii =09 This mail starts the IPR poll on draft-ietf-eman-energy-aware-mib. Are you aware of any IPR that applies to = draft-ietf-eman-energy-aware-mib? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to this email explicitly regardless of whether or not you are aware of any = relevant IPR. *The response needs to be sent to the EMAN wg mailing list.* The document will not advance to the next stage until a response has been received from each author and contributor. If you are on the EMAN WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thank you, Nevil and Tom, EMAN WG Chairs --Apple-Mail=_EDFA2558-4910-455D-B9B1-639C516F7E6E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJSryT1AAoJEPcO+I7eiUJZ9a0P/RboW46i8Z0RcwfTb20ZRvQR 2MPXATIx1ity6nbpqeJzz8E44Zo9gLdp0z8W1/za3tKUAAGe3vSQxTNE+Z4UMsFc ueAJg3YzxXiThzZTtY2h6neLy9YU61IsA1ICcQjB4hMXKyuFvCWAxbUmABflyilI ANSpO9NIGptm07lq+VpSQKhJ7bmgTTanoYQzz149kAp4v+JSHtMBNbZFIY54whLr Tm51JySknKlQ5qwyjazTBd+TTbLm9CzZxvf0DCDV3AWuHeJy3Im1C4dtsDj55GwT Uzic305dsgan2ljDYjOxZG/FrikBWNOyQqRF547oZIi59WWJPfItkJcV9QQML5Ss yI7vitVKe2aPmfQlS6xMCvts2QO+9kcwLUPuCgWPtUj4e7XLQ0WYT184h1zvwCj5 VJZksx7lHInPqy1q93874Ag7ozsn41tciJQk4CQDIS5TD+ClpkoDRkyRntIgrPdD nAENzgnKSX0EMB37mCIjco+6X+bhujG4ix39xaAEtLYUpholheA5V0JDcE6v4OUN +akgc5AwSb3nUWWEZIpyY8qUFN+R2nawYIcAw8i3y0tXDRwWF7y3TtFjQVHG4bqE wvTIbg6ZDv8uCOaVXEBFL6iiNFhOhTzHdRr8F4XjXt1eGOyJsjQy3qeJ/H83avaR dYt3045kZ1jM3yJoNLgg =8vrA -----END PGP SIGNATURE----- --Apple-Mail=_EDFA2558-4910-455D-B9B1-639C516F7E6E-- From bclaise@cisco.com Mon Dec 16 08:55:55 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E6B11AE359 for ; Mon, 16 Dec 2013 08:55:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.039 X-Spam-Level: X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 JW6ih40uLPas for ; Mon, 16 Dec 2013 08:55:53 -0800 (PST) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8F27D1AE355 for ; Mon, 16 Dec 2013 08:55:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1113; q=dns/txt; s=iport; t=1387212953; x=1388422553; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=eSwhx6Er5bki0pBepKXq5h9XZX0REn2GQ4rGYfObNng=; b=TzfoAUlbt69n2MYzyjjurI56zfeY2+DcbJYb0lgpliYIYPLS9zFdmdxk xAM0Q7+7xMPgVRgsZNW62TQxu+Z3g1orYS/3iilSXz3uchqePdpaD3A8k IWrRph4SHt76UJR9n26vq1aCWkI6wINQDD73LTrbrI0QmlVy9xXqfSvh5 s=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ag0FAKkur1KQ/khM/2dsb2JhbABZgwo4uUeBJRZ0giYBAQQ4NgYEARALDhMWDwkDAgECAUUGAQwBBwEBiAANyCATBI43EAIBTweENgEDmBaGRYtPgys7 X-IronPort-AV: E=Sophos;i="4.95,496,1384300800"; d="scan'208";a="2323184" Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 16 Dec 2013 16:55:52 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rBGGtprQ007301; Mon, 16 Dec 2013 16:55:52 GMT Message-ID: <52AF3097.3020905@cisco.com> Date: Mon, 16 Dec 2013 17:55:51 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Thomas Nadeau , eman mailing list References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: draft-ietf-eman-framework@tools.ietf.org, eman-chairs@tools.ietf.org Subject: Re: [eman] IPR Poll: draft-ietf-eman-framework X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 16:55:55 -0000 Tom, As an author, the IPR I know about has already been declared some time ago. https://datatracker.ietf.org/ipr/search/?option=document_search&id=draft-ietf-eman-framework Regards, Benoit > > This mail starts the IPR poll on draft-ietf-eman-framework. > > Are you aware of any IPR that applies to draft-ietf-eman-framework? > > If so, has this IPR been disclosed in compliance with IETF IPR rules > (see RFCs 3979, 4879, 3669 and 5378 for more details). > > If you are listed as a document author or contributor please respond to > this email explicitly regardless of whether or not you are aware of any relevant > IPR. *The response needs to be sent to the EMAN wg mailing list.* The > document will not advance to the next stage until a response > has been received from each author and contributor. > > If you are on the EMAN WG email list but are not listed as an author or > contributor, then please explicitly respond only if you are aware of any > IPR that has not yet been disclosed in conformance with IETF rules. > > Thank you, > > Nevil and Tom, EMAN WG Chairs > > From tnadeau@lucidvision.com Mon Dec 16 09:38:37 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 819491AE027 for ; Mon, 16 Dec 2013 09:38:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.438 X-Spam-Level: X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] 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 FSBozeALyDSd for ; Mon, 16 Dec 2013 09:38:36 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id EB3D61ADF83 for ; Mon, 16 Dec 2013 09:38:35 -0800 (PST) Received: from [192.168.1.112] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id CE92F268A5DA; Mon, 16 Dec 2013 12:38:34 -0500 (EST) Content-Type: multipart/signed; boundary="Apple-Mail=_442521FB-3849-4A5A-B15C-2E4D3B827690"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) From: Thomas Nadeau In-Reply-To: <52AF3097.3020905@cisco.com> Date: Mon, 16 Dec 2013 12:38:33 -0500 Message-Id: <275682ED-D962-4AAB-8CD2-5BEEBCCC941E@lucidvision.com> References: <52AF3097.3020905@cisco.com> To: Benoit Claise X-Mailer: Apple Mail (2.1822) Cc: draft-ietf-eman-framework@tools.ietf.org, eman mailing list , eman-chairs@tools.ietf.org Subject: Re: [eman] IPR Poll: draft-ietf-eman-framework X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 17:38:37 -0000 --Apple-Mail=_442521FB-3849-4A5A-B15C-2E4D3B827690 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 That was on version -08. I believe I need to ask for the = last/latest version. --Tom On Dec 16, 2013:11:55 AM, at 11:55 AM, Benoit Claise = wrote: > Tom, >=20 > As an author, the IPR I know about has already been declared some time = ago. > = https://datatracker.ietf.org/ipr/search/?option=3Ddocument_search&id=3Ddra= ft-ietf-eman-framework >=20 > Regards, Benoit >> =09 >> This mail starts the IPR poll on draft-ietf-eman-framework. >>=20 >> Are you aware of any IPR that applies to draft-ietf-eman-framework? >>=20 >> If so, has this IPR been disclosed in compliance with IETF IPR rules >> (see RFCs 3979, 4879, 3669 and 5378 for more details). >>=20 >> If you are listed as a document author or contributor please respond = to >> this email explicitly regardless of whether or not you are aware of = any relevant >> IPR. *The response needs to be sent to the EMAN wg mailing list.* The >> document will not advance to the next stage until a response >> has been received from each author and contributor. >>=20 >> If you are on the EMAN WG email list but are not listed as an author = or >> contributor, then please explicitly respond only if you are aware of = any >> IPR that has not yet been disclosed in conformance with IETF rules. >>=20 >> Thank you, >>=20 >> Nevil and Tom, EMAN WG Chairs >>=20 >>=20 >=20 >=20 --Apple-Mail=_442521FB-3849-4A5A-B15C-2E4D3B827690 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJSrzqZAAoJEPcO+I7eiUJZ8kIP/juPkpYkb6Nt+vPC9FBJYNDK d9V5YHpclJiYDVXvgR5s+kR4zdmCmrCZmJ039VRgZ524Io22pRbAmymelWtwgJcR ftgFEhCSA+wJQ6kYz9I47LAC1YqBZn0sSnDmaPO7ko81v/85H63BaqpSLxZBRvTW cgYwbRMUjn8obsiL9JMPPqD/5BR92/oyPkM734TWxtdsyjHS/qGEn6uASsnr0/l7 cck/qrumpHGqZHyNk8+t5ehDqPuyjnJMeGwKZFkLNqNnrknNdswOD2bhMXDqFlOy AO7XACEDm7JKiRhTtvJw4xdTe+ChKH2GrEN6ibbDKBpmua5gijtcV/P6RJZmrXJY 2M/D9JW+62b7a02nJ1ykiln0W6tsUs6aeQk9ZTQLO9PkDCQcNR/utVbhatSXkEyt mh/UBS8Cgjj2xXrafDqlKAYhY7u0HyonZxkr45U6XEDx0+EHJEMwZucvNFQ0PFz2 yZWtNDzA+rrF2KhawRgqYZjg4ztZAx6qusGQdaHIOvjQXQR8/6lX2ZCIA6qSqU2/ 0nIRux5qt65tMJ+2JFP+9faggtpesrSxSZBojfJs571JM+Yb397EBMpaz/e/rbpl /7voSQzY6qKz7Vxk12/Onc65uLnNmJJRz9s1HOOpOJ/M+rf+8P1lsnR1fImWTqDK GQzQ4UYkSdT8CaeYF+nB =0hxu -----END PGP SIGNATURE----- --Apple-Mail=_442521FB-3849-4A5A-B15C-2E4D3B827690-- From jparello@cisco.com Mon Dec 16 09:54:44 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1F961AE031 for ; Mon, 16 Dec 2013 09:54:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.038 X-Spam-Level: X-Spam-Status: No, score=-10.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 msLFid7Yo61z for ; Mon, 16 Dec 2013 09:54:42 -0800 (PST) Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 9E65F1ADF9B for ; Mon, 16 Dec 2013 09:54:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3932; q=dns/txt; s=iport; t=1387216482; x=1388426082; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=XZ66DnYJqT3NT8Ojf2ppb03Kade4C/cqYLD4M9gA7qw=; b=O0z+kkLd6vvEWMUmQRR1VFMmOpFAoPP2EbE/BQnVYX4nT6dJgDVHD9K8 kecTjMnPF0IEpgAsO/0tIKI4q9rtKX+2n0HL8U4kwdXtGXKKsU0QVcIGz pVBKxKtVtVIYHwzwfGC8/yQj7rn9zP0+Cd1ZZzunRMleVZLGMZp4jYJDf Q=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgsFADQ+r1KtJV2Z/2dsb2JhbABZgwq5f4ElFnSCJgEBBG4GBRACAQgEOwcyFBECBA4Fh3ADEcg2F40GgTEQAgFPBgGDI4ETBJgWkhSDKg X-IronPort-AV: E=Sophos;i="4.95,496,1384300800"; d="scan'208,217";a="7127210" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-6.cisco.com with ESMTP; 16 Dec 2013 17:54:23 +0000 Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rBGHsNOQ004378 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 16 Dec 2013 17:54:23 GMT Received: from xmb-aln-x04.cisco.com ([169.254.9.103]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0123.003; Mon, 16 Dec 2013 11:54:23 -0600 From: "John Parello (jparello)" To: Brad Schoening Thread-Topic: IPR Poll: draft-ietf-eman-framework Thread-Index: AQHO+oP3ilqU0Z7Hk0So31LWfDkSI5pXGqtZ Date: Mon, 16 Dec 2013 17:54:22 +0000 Message-ID: References: , <52AF377A.9000107@verizon.net> In-Reply-To: <52AF377A.9000107@verizon.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_FB36AFCD658B470090C28606E03BC642ciscocom_" MIME-Version: 1.0 Cc: "draft-ietf-eman-framework@tools.ietf.org" , eman mailing list , "eman-chairs@tools.ietf.org" Subject: Re: [eman] IPR Poll: draft-ietf-eman-framework X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 17:54:45 -0000 --_000_FB36AFCD658B470090C28606E03BC642ciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Same for me. As author and author I have added any IPR for the document already, and it = is reflected in the tool. I don't know of any other IPR related to the doc. Jp Sent from my iPad (expect ridiculous spelling mistakes) On Dec 16, 2013, at 9:26 AM, "Brad Schoening" > wrote: As an author, I am not aware of any IPR disclosures beyond the one Benoit h= as mentioned (ID #2161) Regards, Brad Schoening On 12/16/2013 11:06 AM, Thomas Nadeau wrote: This mail starts the IPR poll on draft-ietf-eman-framework. Are you aware of any IPR that applies to draft-ietf-eman-framework? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to this email explicitly regardless of whether or not you are aware of any rel= evant IPR. *The response needs to be sent to the EMAN wg mailing list.* The document will not advance to the next stage until a response has been received from each author and contributor. If you are on the EMAN WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thank you, Nevil and Tom, EMAN WG Chairs -- Brad Schoening Email: --_000_FB36AFCD658B470090C28606E03BC642ciscocom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Same for me.

As author and author I have added any IPR for the document alread= y, and it is reflected in the tool. I don't know of any other IPR related t= o the doc.


Jp

Sent from my iPad 
(expect ridiculous spelling mistakes) 

On Dec 16, 2013, at 9:26 AM, "Brad Schoening" <brad.schoening@verizon.net> wrote:

As an author, I am not aware of any IPR disclosures beyond the one Benoit h= as mentioned (ID #2161)

Regards,

Brad Schoening

On 12/16/2013 11:06 AM, Thomas Nadeau wrote:
=09
This mail starts the IPR poll on draft-ietf-eman-framework.

Are you aware of any IPR that applies to draft-ietf-eman-framework?

If so, has this IPR been disclosed in compliance with IETF IPR rules
(see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as a document author or contributor please respond to
this email explicitly regardless of whether or not you are aware of any rel=
evant
IPR. *The response needs to be sent to the EMAN wg mailing list.* The
document will not advance to the next stage until a response
has been received from each author and contributor.

If you are on the EMAN WG email list but are not listed as an author or
contributor, then please explicitly respond only if you are aware of any
IPR that has not yet been disclosed in conformance with IETF rules.

	Thank you,

	Nevil and Tom, EMAN WG Chairs


--
Brad Schoening
Email:
--_000_FB36AFCD658B470090C28606E03BC642ciscocom_-- From bnordman@lbl.gov Mon Dec 16 12:05:41 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9C6A1AC862 for ; Mon, 16 Dec 2013 12:05:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.115 X-Spam-Level: X-Spam-Status: No, score=-4.115 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538] 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 8KhMFOydIzsf for ; Mon, 16 Dec 2013 12:05:34 -0800 (PST) Received: from fe1.lbl.gov (fe1.lbl.gov [128.3.41.133]) by ietfa.amsl.com (Postfix) with ESMTP id 39DAA1A1F4C for ; Mon, 16 Dec 2013 12:05:34 -0800 (PST) X-Ironport-SBRS: 4.8 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ai4EAKNcr1JKfVKzlGdsb2JhbABWA4JGfFWwGohXgSAIFg4BAQEBBwsLCRIqgiUBAQEDAQEBAWsGBRALBAcDOCIFDQEFARwGE4d8CAUIpBakAheONxACAT8MBAcRhCUEiUOOU4EwjncYKYR3Gw X-IronPort-AV: E=Sophos;i="4.95,496,1384329600"; d="scan'208";a="35813461" Received: from mail-we0-f179.google.com ([74.125.82.179]) by fe1.lbl.gov with ESMTP; 16 Dec 2013 12:05:32 -0800 Received: by mail-we0-f179.google.com with SMTP id q59so5200304wes.10 for ; Mon, 16 Dec 2013 12:05:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pjqKYgXXqpf/OQSlHZdlqCl5Z9fa3YwNJhm/3paDZtU=; b=TXs0a18AWRg73wThwZ8+urKYGMnx1m5WH6bJ1YyMiO2kfrjUIta67GampMeGYEWHhy cowKGaek74W9SRvJW10E8A9N5X880pp8tuzoztyT5KE733pmvnkzaQNgHptpvEyl+lSz rNjdah77gs9ag6LvZQ0TabWDwEsMGyUFdBo5LufZS500UPLSN+JuxlOeI/vAJn7QUB7S oPJEs+zkJ20PXwx+WeRGokhkSUEzrA4WD9n4RgWQ6MoIy5kzMGqOVemjSsFhShYqY339 1i3vmFUn2eFV+h9U4g7j/mbTtp8zNZj7dE+xqeeraTGF77K5LASR6vZlM74y2zG9HFux N7EQ== X-Gm-Message-State: ALoCoQnV1j9nKy2cHfJXwHkYOixftP1Anh9Vus0mf5sHqshpwXen+PSwnpWILcMO10dKMDkYc6X8QM3woO9gsajcXsQm+ZVi2vJVW53GaiCY7cppNHIqX+o64QHHXiUzGg425Kivny9v X-Received: by 10.180.96.106 with SMTP id dr10mr14778762wib.27.1387224332188; Mon, 16 Dec 2013 12:05:32 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.96.106 with SMTP id dr10mr14778757wib.27.1387224332076; Mon, 16 Dec 2013 12:05:32 -0800 (PST) Received: by 10.180.90.38 with HTTP; Mon, 16 Dec 2013 12:05:31 -0800 (PST) In-Reply-To: References: Date: Mon, 16 Dec 2013 12:05:31 -0800 Message-ID: From: Bruce Nordman To: Thomas Nadeau Content-Type: multipart/alternative; boundary=f46d0418270289931d04edac55e7 Cc: "draft-ietf-eman-framework@tools.ietf.org" , eman mailing list , "eman-chairs@tools.ietf.org" Subject: Re: [eman] IPR Poll: draft-ietf-eman-framework X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 20:05:44 -0000 --f46d0418270289931d04edac55e7 Content-Type: text/plain; charset=ISO-8859-1 I am not currently an author on draft-ietf-eman-framework but earlier did contribute some concepts and text. I am not aware of any relevant IPR. Thank you, --Bruce On Mon, Dec 16, 2013 at 8:06 AM, Thomas Nadeau wrote: > > This mail starts the IPR poll on draft-ietf-eman-framework. > > Are you aware of any IPR that applies to draft-ietf-eman-framework? > > If so, has this IPR been disclosed in compliance with IETF IPR rules > (see RFCs 3979, 4879, 3669 and 5378 for more details). > > If you are listed as a document author or contributor please respond to > this email explicitly regardless of whether or not you are aware of any > relevant > IPR. *The response needs to be sent to the EMAN wg mailing list.* The > document will not advance to the next stage until a response > has been received from each author and contributor. > > If you are on the EMAN WG email list but are not listed as an author or > contributor, then please explicitly respond only if you are aware of any > IPR that has not yet been disclosed in conformance with IETF rules. > > Thank you, > > Nevil and Tom, EMAN WG Chairs > > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > > -- *Bruce Nordman* Lawrence Berkeley National Laboratory *nordman.lbl.gov * BNordman@LBL.gov 510-486-7089 m: 510-501-7943 --f46d0418270289931d04edac55e7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I am not currently an author on draft-ietf-eman-frame= work
but earlier did contribute some concepts and text.
I am n= ot aware of any relevant IPR.
Thank you,
--Bruce


On Mon, Dec 16, 2013 at 8:06 AM, Thomas = Nadeau <tnadeau@lucidvision.com> wrote:

This mail starts the IPR poll on draft-ietf-eman-framework.

Are you aware of any IPR that applies to draft-ietf-eman-framework?

If so, has this IPR been disclosed in compliance with IETF IPR rules
(see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as a document author or contributor please respond to
this email explicitly regardless of whether or not you are aware of any rel= evant
IPR. *The response needs to be sent to the EMAN wg mailing list.* The
document will not advance to the next stage until a response
has been received from each author and contributor.

If you are on the EMAN WG email list but are not listed as an author or
contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules.

=A0 =A0 =A0 =A0 Thank you,

=A0 =A0 =A0 =A0 Nevil and Tom, EMAN WG Chairs



_______________________________________________
eman mailing list
eman@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/eman




--
Bruce Nordman
Lawrence Be= rkeley National Laboratory
= nordman.lbl.gov
BNordman@LBL.gov
510-486-7089
m: 510-501-7943
--f46d0418270289931d04edac55e7-- From Quittek@neclab.eu Tue Dec 17 01:30:03 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E3291AE0D9 for ; Tue, 17 Dec 2013 01:30:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.14 X-Spam-Level: X-Spam-Status: No, score=-3.14 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 sgEL1xYS4dz0 for ; Tue, 17 Dec 2013 01:30:01 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 02BDE1ADF7C for ; Tue, 17 Dec 2013 01:30:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 468D01065C1; Tue, 17 Dec 2013 10:20:39 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YL31+g+NyRnU; Tue, 17 Dec 2013 10:20:39 +0100 (CET) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 1C0DF1065C4; Tue, 17 Dec 2013 10:20:19 +0100 (CET) Received: from PALLENE.office.hd ([169.254.1.239]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Tue, 17 Dec 2013 10:29:39 +0100 From: Juergen Quittek To: Thomas Nadeau , eman mailing list Thread-Topic: [eman] IPR Poll: draft-ietf-eman-framework Thread-Index: AQHO+njJRkZvF1J66U20tqErwxaMsppYH9HA Date: Tue, 17 Dec 2013 09:29:38 +0000 Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E86887BC4E@PALLENE.office.hd> References: In-Reply-To: Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.2.165] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "draft-ietf-eman-framework@tools.ietf.org" , "eman-chairs@tools.ietf.org" Subject: Re: [eman] IPR Poll: draft-ietf-eman-framework X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 09:30:03 -0000 Dear Tom, As an author I am not aware of any IPR that applies to draft-ietf-eman-fram= ework that has not yet been filed for this draft. Juergen > -----Original Message----- > From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau > Sent: Montag, 16. Dezember 2013 17:06 > To: eman mailing list > Cc: draft-ietf-eman-framework@tools.ietf.org; eman-chairs@tools.ietf.org > Subject: [eman] IPR Poll: draft-ietf-eman-framework >=20 >=20 > This mail starts the IPR poll on draft-ietf-eman-framework. >=20 > Are you aware of any IPR that applies to draft-ietf-eman-framework? >=20 > If so, has this IPR been disclosed in compliance with IETF IPR rules (see= RFCs > 3979, 4879, 3669 and 5378 for more details). >=20 > If you are listed as a document author or contributor please respond to t= his > email explicitly regardless of whether or not you are aware of any releva= nt IPR. > *The response needs to be sent to the EMAN wg mailing list.* The document > will not advance to the next stage until a response has been received fro= m each > author and contributor. >=20 > If you are on the EMAN WG email list but are not listed as an author or > contributor, then please explicitly respond only if you are aware of any = IPR that > has not yet been disclosed in conformance with IETF rules. >=20 > Thank you, >=20 > Nevil and Tom, EMAN WG Chairs >=20 From Quittek@neclab.eu Tue Dec 17 01:31:35 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADCFE1AE0CA for ; Tue, 17 Dec 2013 01:31:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.14 X-Spam-Level: X-Spam-Status: No, score=-3.14 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 sioeXZGrLOy6 for ; Tue, 17 Dec 2013 01:31:34 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 672F61AE026 for ; Tue, 17 Dec 2013 01:31:34 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 3D8581065C0; Tue, 17 Dec 2013 10:22:13 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ah4O0OkCI3r; Tue, 17 Dec 2013 10:22:13 +0100 (CET) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 223F0106599; Tue, 17 Dec 2013 10:22:03 +0100 (CET) Received: from PALLENE.office.hd ([169.254.1.239]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Tue, 17 Dec 2013 10:31:23 +0100 From: Juergen Quittek To: Thomas Nadeau , eman mailing list Thread-Topic: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 Thread-Index: AQHO+ndiYJGZWdpqpE2anb88yvyKyppYH7RA Date: Tue, 17 Dec 2013 09:31:23 +0000 Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E86887BC8D@PALLENE.office.hd> References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> In-Reply-To: <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.2.165] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 09:31:35 -0000 Dear Tom, As an author I am not aware of any IPR that applies to draft-ietf-eman-ener= gy-monitoring-mib and that has not yet been filed for this draft. Juergen > -----Original Message----- > From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau > Sent: Montag, 16. Dezember 2013 16:56 > To: eman mailing list > Subject: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 > and draft-ietf-eman-energy-aware-mib-13 >=20 >=20 > As agreed at the last WG meeting, with the EMAN Framework > completing its WG LC the chairs would like to initiate a WG LC on draft-i= etf- > eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13. > The WG LC will end on Dec 30 at 8AM EDT. >=20 > Thank you, >=20 > Nevil and Tom >=20 From bclaise@cisco.com Tue Dec 17 06:36:56 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F29311ADFCA for ; Tue, 17 Dec 2013 06:36:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.039 X-Spam-Level: X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 XNAvCxUdP1I8 for ; Tue, 17 Dec 2013 06:36:54 -0800 (PST) Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE611ADEBA for ; Tue, 17 Dec 2013 06:36:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1171; q=dns/txt; s=iport; t=1387291014; x=1388500614; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=8go38O2cpoqMGDfNspNLuGyZSOLnV3fT4Mpjy8Yly/U=; b=X+yOSxKX4j/JEbco4hZjB/wLGeTiqxNJqffU3J1w6fvTfFJ112iXxQ7+ XHliaS6oRT8ERZS0b9v5A29FA/JHUJxZKrP8ghT1MwR52ejqwBBpzRL8l gfRrZVcD6qLFeatve7uIkKMEm5nnUJD09lKfSajHbbTL6puxetpt4GWDg Q=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjoFAM1gsFKQ/khM/2dsb2JhbABZgwq5dYEeFnSCJgEBBB0bQAEQCw4TFgQLCQMCAQIBRQYBDAEHAQGIAMkUF48SB4Q2AQOYFoZFi0+BbYE/Ow X-IronPort-AV: E=Sophos;i="4.95,501,1384300800"; d="scan'208";a="1753587" Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 17 Dec 2013 14:36:53 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rBHEaqXr024098; Tue, 17 Dec 2013 14:36:52 GMT Message-ID: <52B06184.3060509@cisco.com> Date: Tue, 17 Dec 2013 15:36:52 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Thomas Nadeau , eman mailing list References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> In-Reply-To: <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 14:36:56 -0000 Dear all, Feedback regarding draft-ietf-eman-energy-monitoring-mib. EMAN should start at 768 and not 1024, according to the IANAPowerStateSet TC. eman(1024), -- indicates EMAN set emanmechoff(1025), emansoftoff(1026), emanhibernate(1027), emansleep(1028), emanstandby(1029), emanready(1030), emanlowMinus(1031), emanlow(1032), emanmediumMinus(1033), emanmedium(1034), emanhighMinus(1035), emanhigh(1036) I should have probably spotted that one earlier. Sorry. Regards, Benoit > As agreed at the last WG meeting, with the EMAN Framework completing its WG LC the chairs would like to initiate a WG LC on draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13. The WG LC will end on Dec 30 at 8AM EDT. > > Thank you, > > Nevil and Tom > > From bclaise@cisco.com Tue Dec 17 06:44:07 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B29A01AE1B8 for ; Tue, 17 Dec 2013 06:44:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.038 X-Spam-Level: X-Spam-Status: No, score=-10.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 bTh8-a8yxXIe for ; Tue, 17 Dec 2013 06:44:06 -0800 (PST) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id D37061AE1B6 for ; Tue, 17 Dec 2013 06:44:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3478; q=dns/txt; s=iport; t=1387291445; x=1388501045; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=XEHdrSYlgVfcgZi8x4isXVBlTKRfaqbB271b2hD6mJ4=; b=esM7EMXVAbOpdNMCPFEQrK0GsMAKwi7DIP0b2XKms1sRMIsqi5S7FJNS NQBWMQt8kqI8mqPlAgKKekHbSDhEDD0U87+9H+wX9sJ1gyCyJf65YUmIN 8wPeFTZXmh1brs/G3K8f0fSXlf0HyNkV6XdR2KaDkmvCOGQOjrB069wbd o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjwFADFisFKQ/khR/2dsb2JhbABZgwo4uT2BHhZ0giYBAQQBAQFrBgQBEAsEChMWDwkDAgECARUwBgEMAQUCAQGIAA3JCRMEjjAQAgFPB4Q2BJgWhkWLT4MsOw X-IronPort-AV: E=Sophos;i="4.95,501,1384300800"; d="scan'208,217";a="2366614" Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-1.cisco.com with ESMTP; 17 Dec 2013 14:44:04 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rBHEi26a018751; Tue, 17 Dec 2013 14:44:03 GMT Message-ID: <52B06332.7080107@cisco.com> Date: Tue, 17 Dec 2013 15:44:02 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Thomas Nadeau , eman mailing list References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------080300090702010606070500" Cc: draft-ietf-eman-energy-aware-mib@tools.ietf.org, eman-chairs@tools.ietf.org Subject: Re: [eman] IPR Poll: draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 14:44:07 -0000 This is a multi-part message in MIME format. --------------080300090702010606070500 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Tom, As a document author, I'm not aware of any other IPRs related to draft-ietf-eman-energy-aware-mib, next to the one already disclosed. Regards, Benoit > > This mail starts the IPR poll on draft-ietf-eman-energy-aware-mib. > > Are you aware of any IPR that applies to draft-ietf-eman-energy-aware-mib? > > If so, has this IPR been disclosed in compliance with IETF IPR rules > (see RFCs 3979, 4879, 3669 and 5378 for more details). > > If you are listed as a document author or contributor please respond to > this email explicitly regardless of whether or not you are aware of any relevant > IPR. *The response needs to be sent to the EMAN wg mailing list.* The > document will not advance to the next stage until a response > has been received from each author and contributor. > > If you are on the EMAN WG email list but are not listed as an author or > contributor, then please explicitly respond only if you are aware of any > IPR that has not yet been disclosed in conformance with IETF rules. > > Thank you, > > Nevil and Tom, EMAN WG Chairs > > > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman --------------080300090702010606070500 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hi Tom,

As a document author, I'm not aware of any other IPRs related to draft-ietf-eman-energy-aware-mib, next to the one already disclosed.

Regards, Benoit
	
This mail starts the IPR poll on draft-ietf-eman-energy-aware-mib.

Are you aware of any IPR that applies to draft-ietf-eman-energy-aware-mib?

If so, has this IPR been disclosed in compliance with IETF IPR rules
(see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as a document author or contributor please respond to
this email explicitly regardless of whether or not you are aware of any relevant
IPR. *The response needs to be sent to the EMAN wg mailing list.* The
document will not advance to the next stage until a response
has been received from each author and contributor.

If you are on the EMAN WG email list but are not listed as an author or
contributor, then please explicitly respond only if you are aware of any
IPR that has not yet been disclosed in conformance with IETF rules.

	Thank you,

	Nevil and Tom, EMAN WG Chairs





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

--------------080300090702010606070500-- From bclaise@cisco.com Tue Dec 17 06:44:44 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29E7F1AE1E4 for ; Tue, 17 Dec 2013 06:44:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.038 X-Spam-Level: X-Spam-Status: No, score=-10.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 cuQieAz6dQLB for ; Tue, 17 Dec 2013 06:44:42 -0800 (PST) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id C8EAD1AE1B6 for ; Tue, 17 Dec 2013 06:44:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3488; q=dns/txt; s=iport; t=1387291481; x=1388501081; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=z6IS2/nF1h6cTNovrgaftMhfac4vrZ8ZARdk3Z4tw3Y=; b=S23pftQUAXwumy6vRo013PU68fkZ9GTkSfOv23dlU0aIvzBYRKwdo68S 1mCY0ae+XggYmL0sP7ldCZNKYusHIX15v1WB0UvQAcv8Ww7uJFDnsfiLb ZCwCzX/TrynEoPtVwopatpQUDDhuECof/gm4X6Yw5xCrrFmUcbFS1BaPo o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjwFADFisFKQ/khN/2dsb2JhbABZgwo4uT2BHhZ0giYBAQQBAQFrBgQBEAsEChMWDwkDAgECARUwBgEMAQUCAQGIAA3JCRMEjjAQAgFPB4Q2BJgWhkWLT4MsOw X-IronPort-AV: E=Sophos;i="4.95,501,1384300800"; d="scan'208,217";a="2366632" Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-1.cisco.com with ESMTP; 17 Dec 2013 14:44:40 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rBHEidYw030090; Tue, 17 Dec 2013 14:44:39 GMT Message-ID: <52B06357.7070605@cisco.com> Date: Tue, 17 Dec 2013 15:44:39 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Thomas Nadeau , eman mailing list References: <36DA8D84-C6D5-4A55-8B4A-2D155B449928@lucidvision.com> In-Reply-To: <36DA8D84-C6D5-4A55-8B4A-2D155B449928@lucidvision.com> Content-Type: multipart/alternative; boundary="------------080601080308090808000704" Cc: draft-ietf-eman-energy-monitoring-mib@tools.ietf.org, eman-chairs@tools.ietf.org Subject: Re: [eman] IPR Poll: draft-ietf-eman-energy-monitoring-mib-08 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 14:44:44 -0000 This is a multi-part message in MIME format. --------------080601080308090808000704 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Tom, As a document author, I'm not aware of any other IPRs related to draft-ietf-eman-energy-monitoring-mib, next to the one already disclosed. Regards, Benoit > > This mail starts the IPR poll on draft-ietf-eman-energy-monitoring-mib. > > Are you aware of any IPR that applies to draft-ietf-eman-energy-monitoring-mib? > > If so, has this IPR been disclosed in compliance with IETF IPR rules > (see RFCs 3979, 4879, 3669 and 5378 for more details). > > If you are listed as a document author or contributor please respond to > this email explicitly regardless of whether or not you are aware of any relevant > IPR. *The response needs to be sent to the EMAN wg mailing list.* The > document will not advance to the next stage until a response > has been received from each author and contributor. > > If you are on the EMAN WG email list but are not listed as an author or > contributor, then please explicitly respond only if you are aware of any > IPR that has not yet been disclosed in conformance with IETF rules. > > Thank you, > > Nevil and Tom, EMAN WG Chairs > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman --------------080601080308090808000704 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hi Tom,

As a document author, I'm not aware of any other IPRs related to draft-ietf-eman-energy-monitoring-mib, next to the one already disclosed.

Regards, Benoit
	
This mail starts the IPR poll on draft-ietf-eman-energy-monitoring-mib.

Are you aware of any IPR that applies to draft-ietf-eman-energy-monitoring-mib?

If so, has this IPR been disclosed in compliance with IETF IPR rules
(see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as a document author or contributor please respond to
this email explicitly regardless of whether or not you are aware of any relevant
IPR. *The response needs to be sent to the EMAN wg mailing list.* The
document will not advance to the next stage until a response
has been received from each author and contributor.

If you are on the EMAN WG email list but are not listed as an author or
contributor, then please explicitly respond only if you are aware of any
IPR that has not yet been disclosed in conformance with IETF rules.

	Thank you,

	Nevil and Tom, EMAN WG Chairs



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

--------------080601080308090808000704-- From jparello@cisco.com Tue Dec 17 07:55:30 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6380D1ADF73 for ; Tue, 17 Dec 2013 07:55:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.038 X-Spam-Level: X-Spam-Status: No, score=-15.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 Tqmf9LDJgxU5 for ; Tue, 17 Dec 2013 07:55:29 -0800 (PST) Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id D41791AE047 for ; Tue, 17 Dec 2013 07:55:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4526; q=dns/txt; s=iport; t=1387295728; x=1388505328; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=dWDAy9p3JOtXv8lm8UYE2NIC6K6+ITRDkxTjxImppXQ=; b=FmmLywv5kl/Z4BhOUQANhIr/clrq6ArWei6gUNoVuNzd4BOyuVCz/3l6 BpeT6+v1LF0zZATGNBhaFHxy88vdLTa4RVOBH66RSjT7iEF1Uq/7SuzUK BClY9fgsuLYbbYs8pBK2FMnup152HTomAaqguCd16EC8picN7YsNXyMus k=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjwFAN1ysFKtJXG+/2dsb2JhbABZgwo4Sbh0gR8WdIImAQEEAQEBawYFEAIBCAQ7BycLFBECBA4FiAQNyRkTBI4wEAIBSwQHgyOBEwSYFpIUgys X-IronPort-AV: E=Sophos;i="4.95,502,1384300800"; d="scan'208,217";a="292072741" Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-2.cisco.com with ESMTP; 17 Dec 2013 15:55:27 +0000 Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rBHFtRqi012531 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 17 Dec 2013 15:55:27 GMT Received: from xmb-aln-x04.cisco.com ([169.254.9.103]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Tue, 17 Dec 2013 09:55:27 -0600 From: "John Parello (jparello)" To: "Benoit Claise (bclaise)" Thread-Topic: [eman] IPR Poll: draft-ietf-eman-energy-aware-mib-13 Thread-Index: AQHO+njCY+ybwGJosEmHIfm0mchfI5pY3H4A//+vXaw= Date: Tue, 17 Dec 2013 15:55:25 +0000 Message-ID: References: , <52B06332.7080107@cisco.com> In-Reply-To: <52B06332.7080107@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_BD7576817D1A45EEB00F628B2225845Eciscocom_" MIME-Version: 1.0 Cc: "draft-ietf-eman-energy-aware-mib@tools.ietf.org" , eman mailing list , "eman-chairs@tools.ietf.org" Subject: Re: [eman] IPR Poll: draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 15:55:30 -0000 --_000_BD7576817D1A45EEB00F628B2225845Eciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Same for me. I don't know of any other IPR. Jp Sent from my iPad (expect ridiculous spelling mistakes) On Dec 17, 2013, at 6:44 AM, "Benoit Claise (bclaise)" > wrote: Hi Tom, As a document author, I'm not aware of any other IPRs related to draft-ietf= -eman-energy-aware-mib, next to the one already disclosed. Regards, Benoit This mail starts the IPR poll on draft-ietf-eman-energy-aware-mib. Are you aware of any IPR that applies to draft-ietf-eman-energy-aware-mib? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to this email explicitly regardless of whether or not you are aware of any rel= evant IPR. *The response needs to be sent to the EMAN wg mailing list.* The document will not advance to the next stage until a response has been received from each author and contributor. If you are on the EMAN WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thank you, Nevil and Tom, EMAN WG Chairs _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman --_000_BD7576817D1A45EEB00F628B2225845Eciscocom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Same for me. I don't know of any other IPR.

Jp


Sent from my iPad 
(expect ridiculous spelling mistakes) 

On Dec 17, 2013, at 6:44 AM, "Benoit Claise (bclaise)" <bclaise@cisco.com> wrote:

Hi Tom,

As a document author, I'm not aware of any other IPRs related to draft-ietf= -eman-energy-aware-mib, next to the one already disclosed.

Regards, Benoit
=09
This mail starts the IPR poll on draft-ietf-eman-energy-aware-mib.

Are you aware of any IPR that applies to draft-ietf-eman-energy-aware-mib?

If so, has this IPR been disclosed in compliance with IETF IPR rules
(see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as a document author or contributor please respond to
this email explicitly regardless of whether or not you are aware of any rel=
evant
IPR. *The response needs to be sent to the EMAN wg mailing list.* The
document will not advance to the next stage until a response
has been received from each author and contributor.

If you are on the EMAN WG email list but are not listed as an author or
contributor, then please explicitly respond only if you are aware of any
IPR that has not yet been disclosed in conformance with IETF rules.

	Thank you,

	Nevil and Tom, EMAN WG Chairs





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

_______________________________________________
eman mailing list
eman@ietf.org
https://www.ie= tf.org/mailman/listinfo/eman
--_000_BD7576817D1A45EEB00F628B2225845Eciscocom_-- From Thomas.Dietz@neclab.eu Thu Dec 19 04:15:04 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5142C1A1F1B for ; Thu, 19 Dec 2013 04:15:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.14 X-Spam-Level: X-Spam-Status: No, score=-3.14 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 QotpdBNr2sEr for ; Thu, 19 Dec 2013 04:15:00 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 51AD11A1F33 for ; Thu, 19 Dec 2013 04:15:00 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 2E638106648; Thu, 19 Dec 2013 13:05:28 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PHteBtj9W4Qg; Thu, 19 Dec 2013 13:05:28 +0100 (CET) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 0F4B9106647; Thu, 19 Dec 2013 13:05:08 +0100 (CET) Received: from DAPHNIS.office.hd ([169.254.2.18]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0323.003; Thu, 19 Dec 2013 13:14:38 +0100 From: Thomas Dietz To: Thomas Nadeau , eman mailing list Thread-Topic: [eman] IPR Poll: draft-ietf-eman-energy-monitoring-mib-08 Thread-Index: AQHO+njLGAX4UuwpVk+qjvyukEpe9ZpbcpPg Date: Thu, 19 Dec 2013 12:14:37 +0000 Message-ID: <75581E268A48F849916117B977D76D376880BD42@DAPHNIS.office.hd> References: <36DA8D84-C6D5-4A55-8B4A-2D155B449928@lucidvision.com> In-Reply-To: <36DA8D84-C6D5-4A55-8B4A-2D155B449928@lucidvision.com> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.1.2.117] Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0147_01CEFCBC.440E4480" MIME-Version: 1.0 Cc: "draft-ietf-eman-energy-monitoring-mib@tools.ietf.org" , "eman-chairs@tools.ietf.org" Subject: Re: [eman] IPR Poll: draft-ietf-eman-energy-monitoring-mib-08 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Dec 2013 12:15:04 -0000 ------=_NextPart_000_0147_01CEFCBC.440E4480 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Tom, As an author I am not aware of any IPR that applies to draft-ietf-eman-energy-monitoring-mib and that has not yet been filed = for this draft. Best Regards, Thomas --=20 Thomas Dietz NEC Europe Ltd., NEC Laboratories, Network Research Division, 69115 Heidelberg, Germany NEC Europe Limited, Registered in England 2832014 Registered Office: Athene, Odyssey Business Park, West End =A0Road, = London, HA4 6QE, GB > -----Original Message----- > From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau > Sent: Monday, December 16, 2013 5:06 PM > To: eman mailing list > Cc: draft-ietf-eman-energy-monitoring-mib@tools.ietf.org; eman- > chairs@tools.ietf.org > Subject: [eman] IPR Poll: draft-ietf-eman-energy-monitoring-mib-08 >=20 >=20 > This mail starts the IPR poll on = draft-ietf-eman-energy-monitoring-mib. >=20 > Are you aware of any IPR that applies to draft-ietf-eman-energy- > monitoring-mib? >=20 > If so, has this IPR been disclosed in compliance with IETF IPR rules > (see RFCs 3979, 4879, 3669 and 5378 for more details). >=20 > If you are listed as a document author or contributor please respond = to > this email explicitly regardless of whether or not you are aware of = any > relevant > IPR. *The response needs to be sent to the EMAN wg mailing list.* The > document will not advance to the next stage until a response > has been received from each author and contributor. >=20 > If you are on the EMAN WG email list but are not listed as an author = or > contributor, then please explicitly respond only if you are aware of = any > IPR that has not yet been disclosed in conformance with IETF rules. >=20 > Thank you, >=20 > Nevil and Tom, EMAN WG Chairs ------=_NextPart_000_0147_01CEFCBC.440E4480 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIISXDCCA58w ggKHoAMCAQICASYwDQYJKoZIhvcNAQEFBQAwcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRz Y2hlIFRlbGVrb20gQUcxHzAdBgNVBAsTFlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMT GkRldXRzY2hlIFRlbGVrb20gUm9vdCBDQSAyMB4XDTk5MDcwOTEyMTEwMFoXDTE5MDcwOTIzNTkw MFowcTELMAkGA1UEBhMCREUxHDAaBgNVBAoTE0RldXRzY2hlIFRlbGVrb20gQUcxHzAdBgNVBAsT FlQtVGVsZVNlYyBUcnVzdCBDZW50ZXIxIzAhBgNVBAMTGkRldXRzY2hlIFRlbGVrb20gUm9vdCBD QSAyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqwujNeCLKRSxFIWvPBDkOW81XUqu 3ephjZVJ9G9koxpgZqSpQCKE2dSl5XiTDmgBrblNXDrO07ioQkDfz6O6gllqkhusHJraCCslJ/lp I0fx4Ossepv1EwLQfjR8wp48AFmr9doM9TI8K6xQ2tbD3oOUyqgMmTIOCEhWW2r72uFYWAFJX3JB PBUGAY5draq4k7TNnuun6GotUjTbOu9cdVHa2/Mx+e5xmDLEVBVEDPmbVe2t3xgIoKOGiknuUwWP GUzV3lh5m9JqHEKrxdWnz2gPluThYZh2YciRfNY+AOKRUIfhnQrmrZfSHcY6fcu82gM01Y5bAfVq B7cWtm5KfwIDAQABo0IwQDAdBgNVHQ4EFgQUMcN5G7r1U9cX4Il6LRdsCrMrnTMwDwYDVR0TBAgw BgEB/wIBBTAOBgNVHQ8BAf8EBAMCAQYwDQYJKoZIhvcNAQEFBQADggEBAJRkWa05ZOcp6xP+WsOL E1fIBCTwdHfAYONn++mJpoO/loJ8btTDPe+egG67KbSYerE7VOs5F0d+Go4L/B8xWTEEss4X8yzH YjZV4iLYiVW0mEiqZPrWHDbYRHhaWiM6V5f1ejBPrp9qTEsrjqAD4z7gqdTSe9KzqOJyPK2e/4BZ 5JtFtPY7sM05GZgy5eohYZDkMSGONLH3LzVKhRDa54o3Ib5ZY+DyhYgxU9RUFIVwefQuBncndS8f uIr5/sW62Dbkg+znZbe/Y1rzRq+BlDfUQYzWI9Yez/VoG0Rjolq6pzVZoeVwBZsOI1eZlAptujlj KIaS8xiE2PvRzwVWZFcwggQhMIIDCaADAgECAgIAxzANBgkqhkiG9w0BAQUFADBxMQswCQYDVQQG EwJERTEcMBoGA1UEChMTRGV1dHNjaGUgVGVsZWtvbSBBRzEfMB0GA1UECxMWVC1UZWxlU2VjIFRy dXN0IENlbnRlcjEjMCEGA1UEAxMaRGV1dHNjaGUgVGVsZWtvbSBSb290IENBIDIwHhcNMDYxMjE5 MTAyOTAwWhcNMTkwNjMwMjM1OTAwWjBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVp bjEQMA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAx MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6ZvDZ4X5Da71jVTDllA1PWLpbkztlNcA W5UidNQg6zSP1uzAMQQLmYHiphTSUqAoI4SLdIkEXlvg4njBeMsWyyg1OXstkEXQ7aAAeny/Sg4b AMOG6VwrMRF7DPOCJEOMHDiLamgAmu7cT3ir0sYTm3at7t4m6O8Br3QPwQmi9mvOvdPNFDBP9eXj pMhim4IaAycwDQJlYE3t0QkjKpY1WCfTdsZxtpAdxO3/NYZ9bzOz2w/FEcKKg6GUXUFr2NIQ9Uz9 ylGs2b3vkoO72uuLFlZWQ8/h1RM9ph8nMM1JVNvJEzSacXXFbOqnC5j5IZ0nrz6jOTlIaoytyZn7 wxLyvQIDAQABo4HZMIHWMHAGA1UdHwRpMGcwZaBjoGGGX2h0dHA6Ly9wa2kudGVsZXNlYy5kZS9j Z2ktYmluL3NlcnZpY2UvYWZfRG93bmxvYWRBUkwuY3JsPy1jcmxfZm9ybWF0PVhfNTA5Ji1pc3N1 ZXI9RFRfUk9PVF9DQV8yMB0GA1UdDgQWBBRJt8bP6D0ff+pEexMp9/EKcD7eZDAfBgNVHSMEGDAW gBQxw3kbuvVT1xfgiXotF2wKsyudMzAOBgNVHQ8BAf8EBAMCAQYwEgYDVR0TAQH/BAgwBgEB/wIB AjANBgkqhkiG9w0BAQUFAAOCAQEAO+Fad8BIF9ypGOyBr1qJ8L0okqbKWRgScOwo8ueuf5Ys5/Jd GTH2Eyt0vb2Asrn3Z8k5onk74RER7mt4kTN+O18mJ3VTZY4zY+7Pc8OwkiNJIVB1I6EfGOKUhT0/ M+l3II2iveahhSlA9j9zMlgNCWum2oVswD+7jWZkViROrg0/MjUBW+mMgtlyWU+xhoXxdIVW5cP4 XPON7kezUwVw5+VNimmDKOETCYaeXsjqWB4MH/mk1FoEaP0oPosCtli19qEsN1cAZ6sjaI1jpe+Z a1z9S1b2q0CHNNQRkmzsh8UKCwczcrRvDB1ULNhRx8y/MNNDcvEyv4zOSWOoAPfyHDCCBS8wggQX oAMCAQICBA0hCkcwDQYJKoZIhvcNAQEFBQAwWjELMAkGA1UEBhMCREUxEzARBgNVBAoTCkRGTi1W ZXJlaW4xEDAOBgNVBAsTB0RGTi1QS0kxJDAiBgNVBAMTG0RGTi1WZXJlaW4gUENBIEdsb2JhbCAt IEcwMTAeFw0wODEwMjQwODUyMDhaFw0xOTA2MzAwMDAwMDBaMIGQMQswCQYDVQQGEwJERTEYMBYG A1UEChMPTkVDIEV1cm9wZSBMdGQuMSAwHgYDVQQLExdORUMgTGFib3JhdG9yaWVzIEV1cm9wZTES MBAGA1UEAxMJTkVDTEFCLUNBMTEwLwYJKoZIhvcNAQkBFiJ6ZXJ0aWZpemllcnVuZ3NzdGVsbGVA bncubmVjbGFiLmV1MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnvIVsbURqjIOcbnf ruYkRceWOZpyvM2ebnYpbd1cP+zdWm6yR7HSO9ppOe1ZZFIasArqQpedPEFvcncSG94FRuW3ND4r Rcq08mbpUTmpWmXfdYlJpQezbsOHCWR74NXoEEbK6TPZIMFpJr6dzQDAxnRc7UOgO6JQ1V42Z39B PhIbPIWz64t8svafxbORmxulJn7F5zDLDcR1AEGyn+L9b645AGwapoKNh7cSQFTqdb6kGyPQjLWf tv09dvmBDKesrcyLZXuDWJ1LMeizSjUEygdSszNXD3gePgJaVaZDS3o923W5gAyPCTSxpAFj8XJ+ /7Ap5jJwYhjJgJ8khFR7JQIDAQABo4IBxDCCAcAwEgYDVR0TAQH/BAgwBgEB/wIBATALBgNVHQ8E BAMCAQYwHQYDVR0OBBYEFE8ch3od4C+Z9r4VqtE1nQ5K5ro2MB8GA1UdIwQYMBaAFEm3xs/oPR9/ 6kR7Eyn38QpwPt5kMC0GA1UdEQQmMCSBInplcnRpZml6aWVydW5nc3N0ZWxsZUBudy5uZWNsYWIu ZXUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290 LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2Jh bC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGiBggrBgEFBQcBAQSBlTCBkjBHBggrBgEFBQcw AoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2Vy dC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2Ev cHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQBsMQ+dD0mmi48dgDU4R6Q/ eXcY0zQcHNp1Vu1s3kwO0WahWB0tiqVBodvfTAWG44xuw0I7NXSTwQ68FU5P0GIQnvRFZyVJlDjr SNlLYxjqfmgb+KVm67o383cZIuDakEE0f29kULIEn2fg/HsDiBAXTsb4I19XaN0TXLI+PMhU+GDp sGCJrydeugEV7qi15q8yymjSAsYgnrc2wJuXpyQ9r3qCtP6aedAPSHqOT8ga1dLT2YRZFs3vNm7T HSr5JJymWMbfpD6OcbRTnNAjSMDHwJxgRBAflA6WzDVm7fk4jiWyLvJwWTMk19t8QLiKG7D0nYvj cEUYyiOSE+SFUTEdMIIFXTCCBEWgAwIBAgIHFXEjuSzkIzANBgkqhkiG9w0BAQUFADCBkDELMAkG A1UEBhMCREUxGDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVDIExhYm9yYXRv cmllcyBFdXJvcGUxEjAQBgNVBAMTCU5FQ0xBQi1DQTExMC8GCSqGSIb3DQEJARYiemVydGlmaXpp ZXJ1bmdzc3RlbGxlQG53Lm5lY2xhYi5ldTAeFw0xMzAzMjYxMzQ0MDlaFw0xNjAzMjUxMzQ0MDla MGAxCzAJBgNVBAYTAkRFMRgwFgYDVQQKEw9ORUMgRXVyb3BlIEx0ZC4xIDAeBgNVBAsTF05FQyBM YWJvcmF0b3JpZXMgRXVyb3BlMRUwEwYDVQQDEwxUaG9tYXMgRGlldHowggEiMA0GCSqGSIb3DQEB AQUAA4IBDwAwggEKAoIBAQCpjbFMyLnXM7ssr9eAuoFSJd2fNyleLDl+BbAd4uaSuD6IacC4Cq/d e3tXtiuM1o5HefxvXMcgRArYdmhICR+Il4jJwHOcZyfKzlBbqtQrzUgbixiuqhDNCmhxoLMRTJtY aDIuoRqVXzqDjU1gWB+BAKIA2B7KzCCZtGnmd2QSAmZkSPL3X+FMQ64+5cTPijzOJ5dgX5mAdHX2 /OUWZ12NdrspIoxoKx3twk9tRVv9K30ehOFN7BV1aJfjEiEWCOGT5aE6dxle+ujn+U/TG8GIyfE6 uXCituRUM168X6CfzoSM8rE8bjXzTiy92bPtQmXIgW9Jn5sE+/hn7yV5BNIpAgMBAAGjggHpMIIB 5TAvBgNVHSAEKDAmMBEGDysGAQQBga0hgiwBAQQDADARBg8rBgEEAYGtIYIsAgEEAwAwCQYDVR0T BAIwADALBgNVHQ8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQW BBSfxN6vdKpCh8VajmMo3lQw21coTDAfBgNVHSMEGDAWgBRPHId6HeAvmfa+FarRNZ0OSua6NjAh BgNVHREEGjAYgRZUaG9tYXMuRGlldHpAbmVjbGFiLmV1MH0GA1UdHwR2MHQwOKA2oDSGMmh0dHA6 Ly9jZHAxLnBjYS5kZm4uZGUvbmVjbGFiLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMDigNqA0hjJodHRw Oi8vY2RwMi5wY2EuZGZuLmRlL25lY2xhYi1jYS9wdWIvY3JsL2NhY3JsLmNybDCBmAYIKwYBBQUH AQEEgYswgYgwQgYIKwYBBQUHMAKGNmh0dHA6Ly9jZHAxLnBjYS5kZm4uZGUvbmVjbGFiLWNhL3B1 Yi9jYWNlcnQvY2FjZXJ0LmNydDBCBggrBgEFBQcwAoY2aHR0cDovL2NkcDIucGNhLmRmbi5kZS9u ZWNsYWItY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQBeQruB47uM aISTpyfmtUw9p5FwiQJ6voD76MjHdSP5eR2Li/h/N1HQKi417Wztz55iI2H5Jywi38aIoYKDkByw NHZPgOgPcEBUG6p7vrbMaxFZrZvOWAm471kFgHnL+CeX80xujmfuxT2GnULYmq1KQaGzqWvXAgms mopuKE4D+O4tIhlPr9mmdBClrJ2vfwGfR0wf94LoA1SRYatmrpp7yrpWSQHYYcZ2dVF6HBVIGp14 rZW/tw9jKxoX39yoGOxRR60kew/58wPmS+O8BzvG0n9mAOwCmd8ZhiKrW18GZpJ0+TNi9zc+MJcv TFQS3SzT4qpe1BdI9bB+BoU8q7irMYIENTCCBDECAQEwgZwwgZAxCzAJBgNVBAYTAkRFMRgwFgYD VQQKEw9ORUMgRXVyb3BlIEx0ZC4xIDAeBgNVBAsTF05FQyBMYWJvcmF0b3JpZXMgRXVyb3BlMRIw EAYDVQQDEwlORUNMQUItQ0ExMTAvBgkqhkiG9w0BCQEWInplcnRpZml6aWVydW5nc3N0ZWxsZUBu dy5uZWNsYWIuZXUCBxVxI7ks5CMwCQYFKw4DAhoFAKCCAm0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3 DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMxMjE5MTIxNDM2WjAjBgkqhkiG9w0BCQQxFgQUFVwN21iH ZV09mlykl8S7etDLFo4wgasGCSqGSIb3DQEJDzGBnTCBmjALBglghkgBZQMEASowCwYJYIZIAWUD BAEWMAoGCCqGSIb3DQMHMAsGCWCGSAFlAwQBAjAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYI KoZIhvcNAwICAUAwDQYIKoZIhvcNAwICASgwBwYFKw4DAhowCwYJYIZIAWUDBAIDMAsGCWCGSAFl AwQCAjALBglghkgBZQMEAgEwga0GCSsGAQQBgjcQBDGBnzCBnDCBkDELMAkGA1UEBhMCREUxGDAW BgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVDIExhYm9yYXRvcmllcyBFdXJvcGUx EjAQBgNVBAMTCU5FQ0xBQi1DQTExMC8GCSqGSIb3DQEJARYiemVydGlmaXppZXJ1bmdzc3RlbGxl QG53Lm5lY2xhYi5ldQIHFXEjuSzkIzCBrwYLKoZIhvcNAQkQAgsxgZ+ggZwwgZAxCzAJBgNVBAYT AkRFMRgwFgYDVQQKEw9ORUMgRXVyb3BlIEx0ZC4xIDAeBgNVBAsTF05FQyBMYWJvcmF0b3JpZXMg RXVyb3BlMRIwEAYDVQQDEwlORUNMQUItQ0ExMTAvBgkqhkiG9w0BCQEWInplcnRpZml6aWVydW5n c3N0ZWxsZUBudy5uZWNsYWIuZXUCBxVxI7ks5CMwDQYJKoZIhvcNAQEBBQAEggEAOl0E+VXOWpHT xGKcop6I+6HeWcbZev8xYoBN1v1sAvqYoPjhbdX90UmCmrmoFI9SxEBkuLR72jOejMqwYeJlwEJM DdxuIQjeOIw4RNIWbd+j6hFPGu1C3gigD/0ObxyYfDDpKqfidW9PzKazTuHJUZZbU+YoHZqCgngC I160o6OO9UgS4ZywOWPLEhHk1AixfvZb1jrNlrBs1tmQdgkG7tBbkgTpAvZgJphfpozV2JuKTlIG Ap1F/FlyK3LNaTwDNUFhexgS9U29ZyJqYbfFUUDc/Fze12odqdfgiwEhpyTlQTcivFshEmMNPhcv FkXwQQAKwh3rC38lHWU1b6s5YgAAAAAAAA== ------=_NextPart_000_0147_01CEFCBC.440E4480-- From Quittek@neclab.eu Thu Dec 19 08:31:44 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 903411AD10A; Thu, 19 Dec 2013 08:31:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.14 X-Spam-Level: X-Spam-Status: No, score=-3.14 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 oIWg_cGJ6zV1; Thu, 19 Dec 2013 08:31:41 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 051821ACCEC; Thu, 19 Dec 2013 08:31:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id D54AD10664D; Thu, 19 Dec 2013 17:22:07 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tAruD3RXI5i4; Thu, 19 Dec 2013 17:22:07 +0100 (CET) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id BA5241065F6; Thu, 19 Dec 2013 17:21:47 +0100 (CET) Received: from DAPHNIS.office.hd ([169.254.2.18]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Thu, 19 Dec 2013 17:31:18 +0100 From: Juergen Quittek To: Benoit Claise , eman mailing list , "draft-ietf-eman-battery-mib@tools.ietf.org" , "MIB Doctors (E-mail)" Thread-Topic: [eman] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) Thread-Index: AQHO+FMf76TAmnRYTkadaz6w6T55dJpTTpgAgAAJZACACGQoMA== Date: Thu, 19 Dec 2013 16:31:17 +0000 Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E86889143C@DAPHNIS.office.hd> References: <52AB8ABB.2080901@cisco.com> <20131214083930.GA86143@elstar.local> <52AC2122.4000204@cisco.com> In-Reply-To: <52AC2122.4000204@cisco.com> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.2.165] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Dec 2013 16:31:44 -0000 Hi Benoit, I don't think it is a big issue to revise this decision in order to be in l= ine with IETF recommendations. It was anyway only a question of style.=20 There was no technical reason to use one OID for all. As a workaround we can ask IANA for consecutive OIDs for these drafts. I did not understand a comment you made: > We have 3 MIB documents containing 5 MIB modules, all related to Energy: > 2 are for Textual Conventions > 3 are interconnected: the second and third ones require some objects= to be I assume the third of the 3 'interconnected' modules is the BATTERY MIB. Ho= w is it connected to the others? I do not see any dependency of the BATTERY= MIB on the other two modules. Cheers, Juergen > -----Original Message----- > From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Benoit Claise > Sent: Samstag, 14. Dezember 2013 10:13 > To: eman mailing list; draft-ietf-eman-battery-mib@tools.ietf.org; MIB Do= ctors > (E-mail) > Subject: Re: [eman] A single OID for energy and the 3 EMAN MIBs (message = to > draft-ietf-eman-battery-mib authors) >=20 > Hi J=FCrgen, MIB doctors, >=20 > J=FCrgen, > I wish you had reacted when this email was posted: > http://www.ietf.org/mail-archive/web/eman/current/msg02064.html, or > during the WG meeting where it was discussed (too bad that the meeting > minutes didn't cover that level of details). >=20 > While I understand that assigning a MODULE-IDENTITY descriptor could be > problematic, here it's different: this unique MODULE-IDENTITY descriptor = is for > related MIB modules, and this happens to be a WG in this case. > We have 3 MIB documents containing 5 MIB modules, all related to Energy: > 2 are for Textual Conventions > 3 are interconnected: the second and third ones require some objects= to be > implemented in the first one. >=20 > MIB doctors, > Let us know your advice >=20 > Regards, Benoit >=20 > > Hi, > > > > in the past such registration spaces led to problems (I think RMON was > > the case) and I think because of that we moved pretty much all > > registrations below mib-2 and transmission. Bert Wijnen might recall > > the details. If we change our strategy, we should probably have strong > > reasons and understand the longer term implications. There is the > > relvant quote from RFC 4181: > > > > - The value assigned to the MODULE-IDENTITY descriptor MUST be uniq= ue > > and (for IETF standards-track MIB modules) SHOULD reside under th= e > > mgmt subtree [RFC2578]. Most often it will be an IANA-assigned > > value directly under mib-2 [RFC2578], although for media-specific > > MIB modules that extend the IF-MIB [RFC2863] it is customary to u= se > > an IANA-assigned value under transmission [RFC2578]. In the past= , > > some IETF working groups have made their own assignments from > > subtrees delegated to them by IANA, but that practice has proven > > problematic and is NOT RECOMMENDED. > > > > /js > > > > On Fri, Dec 13, 2013 at 11:31:23PM +0100, Benoit Claise wrote: > >> Dear all, > >> > >> During the last IETF meeting, there was an agreement to go for a > >> single energyMIB OID under mib-2. > >> > >> energyObjectContextMIB MODULE-IDENTITY > >> (draft-ietf-eman-energy-aware-mib) is under energyMIB.1 > >> ianaEnergyRelationMIB MODULE-IDENTITY > >> (draft-ietf-eman-energy-aware-mib) is under energyMIB.2 > >> energyObjectMIB MODULE-IDENTITY > >> (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.3 > >> powerAttributesMIB MODULE-IDENTITY > >> (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.4 > >> > >> For draft-ietf-eman-battery-mib, you can start with energyMIB.5 Note > >> that draft-ietf-eman-energy-aware-mib requests: > >> > >> Descriptor OBJECT IDENTIFIER value > >> ---------- ----------------------- > >> > >> energyMIB { mib-2 XXX } > >> > >> > >> Btw, both draft-ietf-eman-energy-aware-mib and > >> draft-ietf-eman-energy-monitoring-mib are ready for WGLC. > >> > >> Regards, Benoit > >> > >> > >> _______________________________________________ > >> eman mailing list > >> eman@ietf.org > >> https://www.ietf.org/mailman/listinfo/eman >=20 > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman From bclaise@cisco.com Fri Dec 20 02:45:13 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2AC81AC441; Fri, 20 Dec 2013 02:45:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.038 X-Spam-Level: X-Spam-Status: No, score=-10.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 juD34n1bJtqx; Fri, 20 Dec 2013 02:45:11 -0800 (PST) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0DBF31AE1BA; Fri, 20 Dec 2013 02:45:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13474; q=dns/txt; s=iport; t=1387536308; x=1388745908; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=SBjp4bJ9CtEgCT3QjrFAkuYWfXCXjo7q50g+Vcsm41o=; b=TmasuGhZz83wYPcyWfpOyr4vcejGhGDbnosz2Q33jHOnmrRj89/ezNRj EcYt+7Ie8Li7gKz0xJBAcDPPjzVMEOlYorF8b751ujJIPQ7RWMvWhUmip yr/2RPAcWiaud3WNHNFgB86T6o5aKR7iBbJdwWp8Yh3Dl8fg0y9yzDE+A o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgcFAMketFKQ/khN/2dsb2JhbABQCYMLOIk1sFWBGBZ0giUBAQEEAQEBaxcECxEEAQEBCRoEBw8CFh8JCAYBDAYCAQEFh3sNylgXjioGBwkCAVYGhDAElDODY4ZFi0+BbYE/Ow X-IronPort-AV: E=Sophos;i="4.95,520,1384300800"; d="scan'208,217";a="2571032" Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-1.cisco.com with ESMTP; 20 Dec 2013 10:45:06 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rBKAj6jP010149; Fri, 20 Dec 2013 10:45:06 GMT Message-ID: <52B41FB2.30105@cisco.com> Date: Fri, 20 Dec 2013 11:45:06 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Juergen Quittek , eman mailing list , "draft-ietf-eman-battery-mib@tools.ietf.org" , "MIB Doctors (E-mail)" References: <52AB8ABB.2080901@cisco.com> <20131214083930.GA86143@elstar.local> <52AC2122.4000204@cisco.com> <9AB93E4127C26F4BA7829DEFDCE5A6E86889143C@DAPHNIS.office.hd> In-Reply-To: <9AB93E4127C26F4BA7829DEFDCE5A6E86889143C@DAPHNIS.office.hd> Content-Type: multipart/alternative; boundary="------------080008040907000809090503" Subject: Re: [eman] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Dec 2013 10:45:14 -0000 This is a multi-part message in MIME format. --------------080008040907000809090503 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hi Jürgen, > Hi Benoit, > > I don't think it is a big issue to revise this decision in order to be in line with IETF recommendations. As an author, I will follow whatever advice/consensus the MIB doctors will come up with. At this point, I'm not sure about the outcome. Practically, I believe that Tom Nadeau, as the MIB doctor for these EMAN documents (and EMAN co-chair) should be providing guidance here. > It was anyway only a question of style. > There was no technical reason to use one OID for all. > As a workaround we can ask IANA for consecutive OIDs for these drafts. > > I did not understand a comment you made: >> We have 3 MIB documents containing 5 MIB modules, all related to Energy: >> 2 are for Textual Conventions >> 3 are interconnected: the second and third ones require some objects to be > I assume the third of the 3 'interconnected' modules is the BATTERY MIB. How is it connected to the others? I do not see any dependency of the BATTERY MIB on the other two modules. No direct dependency, correct. However, the battery MIB shares the index (entPhysicalIndex) and minimum entity4CRCompliance with draft-ietf-eman-energy-aware-mib Batteries are indexed by the entPhysicalIndex of the entPhysicalTable defined in the ENTITY-MIB module [RFC6933]. An implementation of the ENTITY-MIB module complying with the entity4CRCompliance MODULE- COMPLIANCE statement is required for compliant implementations of the BATTERY-MIB module. Practically, we know that there are two cases: 1. the battery is completely independent and the NMS only wants to monitor the battery: only the battery MIB is implemented 2. the battery is part of a device, and the NMS also needs to understand the inventory and energy information from that device: both energy aware and battery MIBs will be implemented. I have the feeling that #2>> #1 Regards, Benoit > > Cheers, > Juergen > > >> -----Original Message----- >> From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Benoit Claise >> Sent: Samstag, 14. Dezember 2013 10:13 >> To: eman mailing list; draft-ietf-eman-battery-mib@tools.ietf.org; MIB Doctors >> (E-mail) >> Subject: Re: [eman] A single OID for energy and the 3 EMAN MIBs (message to >> draft-ietf-eman-battery-mib authors) >> >> Hi Jürgen, MIB doctors, >> >> Jürgen, >> I wish you had reacted when this email was posted: >> http://www.ietf.org/mail-archive/web/eman/current/msg02064.html, or >> during the WG meeting where it was discussed (too bad that the meeting >> minutes didn't cover that level of details). >> >> While I understand that assigning a MODULE-IDENTITY descriptor could be >> problematic, here it's different: this unique MODULE-IDENTITY descriptor is for >> related MIB modules, and this happens to be a WG in this case. >> We have 3 MIB documents containing 5 MIB modules, all related to Energy: >> 2 are for Textual Conventions >> 3 are interconnected: the second and third ones require some objects to be >> implemented in the first one. >> >> MIB doctors, >> Let us know your advice >> >> Regards, Benoit >> >>> Hi, >>> >>> in the past such registration spaces led to problems (I think RMON was >>> the case) and I think because of that we moved pretty much all >>> registrations below mib-2 and transmission. Bert Wijnen might recall >>> the details. If we change our strategy, we should probably have strong >>> reasons and understand the longer term implications. There is the >>> relvant quote from RFC 4181: >>> >>> - The value assigned to the MODULE-IDENTITY descriptor MUST be unique >>> and (for IETF standards-track MIB modules) SHOULD reside under the >>> mgmt subtree [RFC2578]. Most often it will be an IANA-assigned >>> value directly under mib-2 [RFC2578], although for media-specific >>> MIB modules that extend the IF-MIB [RFC2863] it is customary to use >>> an IANA-assigned value under transmission [RFC2578]. In the past, >>> some IETF working groups have made their own assignments from >>> subtrees delegated to them by IANA, but that practice has proven >>> problematic and is NOT RECOMMENDED. >>> >>> /js >>> >>> On Fri, Dec 13, 2013 at 11:31:23PM +0100, Benoit Claise wrote: >>>> Dear all, >>>> >>>> During the last IETF meeting, there was an agreement to go for a >>>> single energyMIB OID under mib-2. >>>> >>>> energyObjectContextMIB MODULE-IDENTITY >>>> (draft-ietf-eman-energy-aware-mib) is under energyMIB.1 >>>> ianaEnergyRelationMIB MODULE-IDENTITY >>>> (draft-ietf-eman-energy-aware-mib) is under energyMIB.2 >>>> energyObjectMIB MODULE-IDENTITY >>>> (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.3 >>>> powerAttributesMIB MODULE-IDENTITY >>>> (draft-ietf-eman-energy-monitoring-mib) is under energyMIB.4 >>>> >>>> For draft-ietf-eman-battery-mib, you can start with energyMIB.5 Note >>>> that draft-ietf-eman-energy-aware-mib requests: >>>> >>>> Descriptor OBJECT IDENTIFIER value >>>> ---------- ----------------------- >>>> >>>> energyMIB { mib-2 XXX } >>>> >>>> >>>> Btw, both draft-ietf-eman-energy-aware-mib and >>>> draft-ietf-eman-energy-monitoring-mib are ready for WGLC. >>>> >>>> Regards, Benoit >>>> >>>> >>>> _______________________________________________ >>>> eman mailing list >>>> eman@ietf.org >>>> https://www.ietf.org/mailman/listinfo/eman >> _______________________________________________ >> eman mailing list >> eman@ietf.org >> https://www.ietf.org/mailman/listinfo/eman > . > --------------080008040907000809090503 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hi Jürgen,
Hi Benoit,

I don't think it is a big issue to revise this decision in order to be in line with IETF recommendations.
As an author, I will follow whatever advice/consensus the MIB doctors will come up with. At this point, I'm not sure about the outcome. Practically, I believe that Tom Nadeau, as the MIB doctor for these EMAN documents (and EMAN co-chair) should be providing guidance here.
It was anyway only a question of style. 
There was no technical reason to use one OID for all.
As a workaround we can ask IANA for consecutive OIDs for these drafts.

I did not understand a comment you made:

We have 3 MIB documents containing 5 MIB modules, all related to Energy:
     2 are for Textual Conventions
     3 are interconnected: the second and third ones require some objects to be

I assume the third of the 3 'interconnected' modules is the BATTERY MIB. How is it connected to the others? I do not see any dependency of the BATTERY MIB on the other two modules.
No direct dependency, correct.
However, the battery MIB shares the index (entPhysicalIndex) and minimum entity4CRCompliance with draft-ietf-eman-energy-aware-mib 
   Batteries are indexed by the entPhysicalIndex of the entPhysicalTable
   defined in the ENTITY-MIB module [RFC6933].  An implementation of the
   ENTITY-MIB module complying with the entity4CRCompliance MODULE-
   COMPLIANCE statement is required for compliant implementations of the
   BATTERY-MIB module.
Practically, we know that there are two cases:
1. the battery is completely independent and the NMS only wants to monitor the battery: only the battery MIB is implemented
2. the battery is part of a device, and the NMS also needs to understand the inventory and energy information from that device: both energy aware and battery MIBs will be implemented.

I have the feeling that #2>> #1

Regards, Benoit

Cheers,
    Juergen



-----Original Message-----
From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Benoit Claise
Sent: Samstag, 14. Dezember 2013 10:13
To: eman mailing list; draft-ietf-eman-battery-mib@tools.ietf.org; MIB Doctors
(E-mail)
Subject: Re: [eman] A single OID for energy and the 3 EMAN MIBs (message to
draft-ietf-eman-battery-mib authors)

Hi Jürgen, MIB doctors,

Jürgen,
I wish you had reacted when this email was posted:
http://www.ietf.org/mail-archive/web/eman/current/msg02064.html, or
during the WG meeting where it was discussed (too bad that the meeting
minutes didn't cover that level of details).

While I understand that assigning a MODULE-IDENTITY descriptor could be
problematic, here it's different: this unique MODULE-IDENTITY descriptor is for
related MIB modules, and this happens to be a WG in this case.
We have 3 MIB documents containing 5 MIB modules, all related to Energy:
     2 are for Textual Conventions
     3 are interconnected: the second and third ones require some objects to be
implemented in the first one.

MIB doctors,
Let us know your advice

Regards, Benoit


Hi,

in the past such registration spaces led to problems (I think RMON was
the case) and I think because of that we moved pretty much all
registrations below mib-2 and transmission. Bert Wijnen might recall
the details. If we change our strategy, we should probably have strong
reasons and understand the longer term implications. There is the
relvant quote from RFC 4181:

    - The value assigned to the MODULE-IDENTITY descriptor MUST be unique
      and (for IETF standards-track MIB modules) SHOULD reside under the
      mgmt subtree [RFC2578].  Most often it will be an IANA-assigned
      value directly under mib-2 [RFC2578], although for media-specific
      MIB modules that extend the IF-MIB [RFC2863] it is customary to use
      an IANA-assigned value under transmission [RFC2578].  In the past,
      some IETF working groups have made their own assignments from
      subtrees delegated to them by IANA, but that practice has proven
      problematic and is NOT RECOMMENDED.

/js

On Fri, Dec 13, 2013 at 11:31:23PM +0100, Benoit Claise wrote:

Dear all,

During the last IETF meeting, there was an agreement to go for a
single energyMIB OID under mib-2.

energyObjectContextMIB MODULE-IDENTITY
(draft-ietf-eman-energy-aware-mib) is under energyMIB.1
ianaEnergyRelationMIB MODULE-IDENTITY
(draft-ietf-eman-energy-aware-mib) is under energyMIB.2
energyObjectMIB MODULE-IDENTITY
(draft-ietf-eman-energy-monitoring-mib) is under energyMIB.3
powerAttributesMIB MODULE-IDENTITY
(draft-ietf-eman-energy-monitoring-mib) is under energyMIB.4

For draft-ietf-eman-battery-mib, you can start with energyMIB.5 Note
that draft-ietf-eman-energy-aware-mib requests:

            Descriptor                      OBJECT IDENTIFIER value
            ----------                      -----------------------

            energyMIB                         { mib-2 XXX }


Btw, both draft-ietf-eman-energy-aware-mib and
draft-ietf-eman-energy-monitoring-mib are ready for WGLC.

Regards, Benoit


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

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

.

--------------080008040907000809090503-- From j.schoenwaelder@jacobs-university.de Fri Dec 20 03:02:51 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF1961AE1EF; Fri, 20 Dec 2013 03:02:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.788 X-Spam-Level: X-Spam-Status: No, score=-2.788 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] 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 pKnFb0LwF3DI; Fri, 20 Dec 2013 03:02:49 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 843601AE1E2; Fri, 20 Dec 2013 03:02:49 -0800 (PST) Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id DD2952002D; Fri, 20 Dec 2013 12:02:46 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id W1LuTlrKAwj9; Fri, 20 Dec 2013 12:02:46 +0100 (CET) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 286C420013; Fri, 20 Dec 2013 12:02:46 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id D4E122A0E24C; Fri, 20 Dec 2013 12:02:41 +0100 (CET) Date: Fri, 20 Dec 2013 12:02:41 +0100 From: Juergen Schoenwaelder To: Benoit Claise Message-ID: <20131220110241.GA7974@elstar.local> Mail-Followup-To: Benoit Claise , Juergen Quittek , eman mailing list , "draft-ietf-eman-battery-mib@tools.ietf.org" , "MIB Doctors (E-mail)" References: <52AB8ABB.2080901@cisco.com> <20131214083930.GA86143@elstar.local> <52AC2122.4000204@cisco.com> <9AB93E4127C26F4BA7829DEFDCE5A6E86889143C@DAPHNIS.office.hd> <52B41FB2.30105@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52B41FB2.30105@cisco.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "MIB Doctors \(E-mail\)" , eman mailing list , "draft-ietf-eman-battery-mib@tools.ietf.org" Subject: Re: [eman] [MIB-DOCTORS] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Dec 2013 11:02:51 -0000 On Fri, Dec 20, 2013 at 11:45:06AM +0100, Benoit Claise wrote: > > I assume the third of the 3 'interconnected' modules is the > > BATTERY MIB. How is it connected to the others? I do not see any > > dependency of the BATTERY MIB on the other two modules. > No direct dependency, correct. > However, the battery MIB shares the index (entPhysicalIndex) and > minimum entity4CRCompliance with draft-ietf-eman-energy-aware-mib > > > Batteries are indexed by the entPhysicalIndex of the entPhysicalTable > defined in the ENTITY-MIB module [RFC6933]. An implementation of the > ENTITY-MIB module complying with the entity4CRCompliance MODULE- > COMPLIANCE statement is required for compliant implementations of the > BATTERY-MIB module. > > Practically, we know that there are two cases: > 1. the battery is completely independent and the NMS only wants to > monitor the battery: only the battery MIB is implemented > 2. the battery is part of a device, and the NMS also needs to > understand the inventory and energy information from that device: > both energy aware and battery MIBs will be implemented. > > I have the feeling that #2>> #1 So the point is being made that the battery MIB should be rooted under the ENTITY-MIB? Perhaps this example makes it clear that attempts to find a proper logical nesting do not scale up. Are we optimizing for applications that do blind MIB walks in order to find information for managing certain functions or do we expect sligthly more advanced applications? /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From bclaise@cisco.com Mon Dec 23 03:30:28 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76F3F1ADF73; Mon, 23 Dec 2013 03:30:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.039 X-Spam-Level: X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 yJzlPNa7wRRY; Mon, 23 Dec 2013 03:30:27 -0800 (PST) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 905291AD72A; Mon, 23 Dec 2013 03:30:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1752; q=dns/txt; s=iport; t=1387798223; x=1389007823; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=0tSEJuPVstflC/eWLh2YpzlxvhHNLV8A/x7INs31Vv4=; b=iZCXTcnmgcYO1DlHVnp9uBwsSxv8Phz7gtVkVEsU5ISEbM7yp6YR2WpG RXxcKhrArAlfFNyX0UtvtFE1iCOLAV3UtgfWG/ZFR85LIluu81jCN9r+e mtR5jRqXZZxteSBGMqVvDFUI/VitT9q/43CE0/Vb9zeqRqyf+dD2gVyNu Q=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuwKAEwduFKQ/khL/2dsb2JhbABZgws4snWHIIEaFnSCJQEBAQQ4QBELGAkWBAsJAwIBAgFFBgEMCAEBiAANylYTBI49b4Q2AQOUM4NkhkWLT4FvgT87 X-IronPort-AV: E=Sophos;i="4.95,536,1384300800"; d="scan'208";a="2675795" Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 23 Dec 2013 11:30:22 +0000 Received: from [10.60.67.83] (ams-bclaise-8912.cisco.com [10.60.67.83]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rBNBUMbF030348; Mon, 23 Dec 2013 11:30:22 GMT Message-ID: <52B81ECE.3070507@cisco.com> Date: Mon, 23 Dec 2013 12:30:22 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Juergen Quittek , eman mailing list , "draft-ietf-eman-battery-mib@tools.ietf.org" , "MIB Doctors (E-mail)" References: <52AB8ABB.2080901@cisco.com> <20131214083930.GA86143@elstar.local> <52AC2122.4000204@cisco.com> <9AB93E4127C26F4BA7829DEFDCE5A6E86889143C@DAPHNIS.office.hd> <52B41FB2.30105@cisco.com> <20131220110241.GA7974@elstar.local> In-Reply-To: <20131220110241.GA7974@elstar.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [eman] [MIB-DOCTORS] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Dec 2013 11:30:28 -0000 On 20/12/2013 12:02, Juergen Schoenwaelder wrote: > On Fri, Dec 20, 2013 at 11:45:06AM +0100, Benoit Claise wrote: > >>> I assume the third of the 3 'interconnected' modules is the >>> BATTERY MIB. How is it connected to the others? I do not see any >>> dependency of the BATTERY MIB on the other two modules. >> No direct dependency, correct. >> However, the battery MIB shares the index (entPhysicalIndex) and >> minimum entity4CRCompliance with draft-ietf-eman-energy-aware-mib >> >> >> Batteries are indexed by the entPhysicalIndex of the entPhysicalTable >> defined in the ENTITY-MIB module [RFC6933]. An implementation of the >> ENTITY-MIB module complying with the entity4CRCompliance MODULE- >> COMPLIANCE statement is required for compliant implementations of the >> BATTERY-MIB module. >> >> Practically, we know that there are two cases: >> 1. the battery is completely independent and the NMS only wants to >> monitor the battery: only the battery MIB is implemented >> 2. the battery is part of a device, and the NMS also needs to >> understand the inventory and energy information from that device: >> both energy aware and battery MIBs will be implemented. >> >> I have the feeling that #2>> #1 > So the point is being made that the battery MIB should be rooted under > the ENTITY-MIB? Not quite. Regards, Benoit > Perhaps this example makes it clear that attempts to > find a proper logical nesting do not scale up. > > Are we optimizing for applications that do blind MIB walks in order to > find information for managing certain functions or do we expect > sligthly more advanced applications? > > /js > From Quittek@neclab.eu Thu Dec 26 07:46:33 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81DBB1AE22B; Thu, 26 Dec 2013 07:46:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.44 X-Spam-Level: X-Spam-Status: No, score=-0.44 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 CAmztZ5HLRcO; Thu, 26 Dec 2013 07:46:31 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id B505F1ADF60; Thu, 26 Dec 2013 07:46:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 120ED10671A; Thu, 26 Dec 2013 16:36:23 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d3WBOJb6ctdz; Thu, 26 Dec 2013 16:36:22 +0100 (CET) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id EA29C106714; Thu, 26 Dec 2013 16:35:57 +0100 (CET) Received: from DAPHNIS.office.hd ([169.254.2.18]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Thu, 26 Dec 2013 16:46:00 +0100 From: Juergen Quittek To: Juergen Schoenwaelder , Benoit Claise Thread-Topic: [MIB-DOCTORS] [eman] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) Thread-Index: AQHO+FMf76TAmnRYTkadaz6w6T55dJpTTpgAgAAJZACACGQoMIABI4kAgAAE6oCACcrI0A== Date: Thu, 26 Dec 2013 15:45:59 +0000 Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E8688AFEFC@DAPHNIS.office.hd> References: <52AB8ABB.2080901@cisco.com> <20131214083930.GA86143@elstar.local> <52AC2122.4000204@cisco.com> <9AB93E4127C26F4BA7829DEFDCE5A6E86889143C@DAPHNIS.office.hd> <52B41FB2.30105@cisco.com> <20131220110241.GA7974@elstar.local> In-Reply-To: <20131220110241.GA7974@elstar.local> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.0.199] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "MIB Doctors \(E-mail\)" , eman mailing list , "draft-ietf-eman-battery-mib@tools.ietf.org" Subject: Re: [eman] [MIB-DOCTORS] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 15:46:33 -0000 So, we found there is no dependency of the BATTERY-MIB on other eman MIB mo= dules (except for using the ENTITY MIB which has its own OID already). Henc= e, we do not have a technical reason to use a common OID prefix for the cur= rent eman MIB modules. Rather we are creating a common OID prefix for MIB m= odules developed by the eman WG. This is a matter of style. Do we want to i= ntroduce WG-owned OID prefixes at the IETF? Juergen Q.=20 > -----Original Message----- > From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] > Sent: Freitag, 20. Dezember 2013 12:03 > To: Benoit Claise > Cc: Juergen Quittek; eman mailing list; draft-ietf-eman-battery- > mib@tools.ietf.org; MIB Doctors (E-mail) > Subject: Re: [MIB-DOCTORS] [eman] A single OID for energy and the 3 EMAN > MIBs (message to draft-ietf-eman-battery-mib authors) >=20 > On Fri, Dec 20, 2013 at 11:45:06AM +0100, Benoit Claise wrote: >=20 > > > I assume the third of the 3 'interconnected' modules is the BATTERY > > > MIB. How is it connected to the others? I do not see any dependency > > > of the BATTERY MIB on the other two modules. >=20 > > No direct dependency, correct. > > However, the battery MIB shares the index (entPhysicalIndex) and > > minimum entity4CRCompliance with draft-ietf-eman-energy-aware-mib > > > > > > Batteries are indexed by the entPhysicalIndex of the entPhysicalTabl= e > > defined in the ENTITY-MIB module [RFC6933]. An implementation of th= e > > ENTITY-MIB module complying with the entity4CRCompliance MODULE- > > COMPLIANCE statement is required for compliant implementations of th= e > > BATTERY-MIB module. > > > > Practically, we know that there are two cases: > > 1. the battery is completely independent and the NMS only wants to > > monitor the battery: only the battery MIB is implemented 2. the > > battery is part of a device, and the NMS also needs to understand the > > inventory and energy information from that device: > > both energy aware and battery MIBs will be implemented. > > > > I have the feeling that #2>> #1 >=20 > So the point is being made that the battery MIB should be rooted under th= e > ENTITY-MIB? Perhaps this example makes it clear that attempts to find a > proper logical nesting do not scale up. >=20 > Are we optimizing for applications that do blind MIB walks in order to fi= nd > information for managing certain functions or do we expect sligthly more > advanced applications? >=20 > /js >=20 > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany > Fax: +49 421 200 3103 From randy_presuhn@mindspring.com Thu Dec 26 10:51:09 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 078121AE005; Thu, 26 Dec 2013 10:51:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.7 X-Spam-Level: X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] 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 nAd0AjWOZH3O; Thu, 26 Dec 2013 10:51:07 -0800 (PST) Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 3992C1ADFF6; Thu, 26 Dec 2013 10:51:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=TR4MN5rgRCGBu5yHbA4z8n/+v78B0njQ94rMtwoekJS97vgvHKO66hnjSl8s0bAD; h=Message-ID:Date:From:Reply-To:To:Subject:Cc:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP; Received: from [209.86.224.52] (helo=mswamui-valley.atl.sa.earthlink.net) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1VwG1D-0002v4-2b; Thu, 26 Dec 2013 13:50:51 -0500 Received: from 99.187.237.254 by webmail.earthlink.net with HTTP; Thu, 26 Dec 2013 13:50:50 -0500 Message-ID: <18241430.1388083851066.JavaMail.root@mswamui-valley.atl.sa.earthlink.net> Date: Thu, 26 Dec 2013 10:50:50 -0800 (GMT-08:00) From: Randy Presuhn To: Juergen Quittek , Juergen Schoenwaelder , Benoit Claise Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailer: EarthLink Zoo Mail 1.0 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8889e105617274a0edbda66e139513d0a727957537984f18c7f350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 209.86.224.52 Cc: "MIB Doctors \(E-mail\)" , eman mailing list , "draft-ietf-eman-battery-mib@tools.ietf.org" Subject: Re: [eman] [MIB-DOCTORS] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Randy Presuhn List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 18:51:09 -0000 Hi - >From: Juergen Quittek >Sent: Dec 26, 2013 7:45 AM >To: Juergen Schoenwaelder , Benoit Claise >Cc: "MIB Doctors (E-mail)" , eman mailing list , "draft-ietf-eman-battery-mib@tools.ietf.org" >Subject: Re: [MIB-DOCTORS] [eman] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) > >So, we found there is no dependency of the BATTERY-MIB >on other eman MIB modules (except for using the ENTITY >MIB which has its own OID already). Hence, we do not >have a technical reason to use a common OID prefix for >the current eman MIB modules. Rather we are creating a >common OID prefix for MIB modules developed by the eman >WG. This is a matter of style. Do we want to introduce >WG-owned OID prefixes at the IETF? 1) Doing so would increase the likelihood of implementations using WG-issued OIDs escaping into the wild prior to publication of the RFC. It's not merely a matter of the WG maintaining the discipline of not making the assignments until, say, AUTH-48. Because the subidentifier values would be easily guessed, folks will very likely implement using anticipated values. 2) There is a dimly-remembered incident in the past of WGs giving the same subid to two different modules. I don't think anyone wants a replay of that. 3) WGs are (we hope) relatively short-lived entities. After a WG is dead and buried, what would be the criteria for locating new work within the defunct WG's tree? After all, by giving a WG a tree to play with, we'd be assuming there must be something meaningful or useful reason for doing so. Consequently, for me the answer to Juergen Q.'s question is "no." Randy From andy@yumaworks.com Thu Dec 26 11:42:07 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 374031AE27E for ; Thu, 26 Dec 2013 11:42:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 0jaQbkbzU1yy for ; Thu, 26 Dec 2013 11:42:05 -0800 (PST) Received: from mail-qe0-f46.google.com (mail-qe0-f46.google.com [209.85.128.46]) by ietfa.amsl.com (Postfix) with ESMTP id 096611AE02F for ; Thu, 26 Dec 2013 11:42:04 -0800 (PST) Received: by mail-qe0-f46.google.com with SMTP id a11so8091738qen.5 for ; Thu, 26 Dec 2013 11:42:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=P+JZPSuQfXsWW8khA34VBsoSVEODNPYuwutKJmTKlss=; b=GWLS2BIyuWMSSkVsnHMZEsxyIdoKz1Fve2VuUNdTKahcbBZgoYcKlPfXrgguaP20kh teNYKgX1iIeB+JjiijuU+IZlZbPP9/4MANjIjjNYQLGuAb52DLHA9ukUNAX0grGPAMib zRTSP87bINZeCX9IQI7VE84bUwNAtiIq1fLkBn8jRGEZnB2cbfjcSen8jB8Z2Kyl3Ri6 GNHlAHgao065hNPOXXKIuaOaGVUP9g8y5mzEIa9bfGm5n5mQW0hLhyoRfW9dQEr8LMZd 5Kue8Z0edxlbNwdfBd8224KFs5iIdbGKUeBfDSZgirLFor1RWAOnUeGm+f99YdzJuDp2 nfHA== X-Gm-Message-State: ALoCoQm+lscNFG8bmgQXoS4zqlzUctiwWua+TwHbrg3QTyvi1wAmpmsOBQ5XGdUT55V0h1c9q7WP MIME-Version: 1.0 X-Received: by 10.224.26.71 with SMTP id d7mr40250968qac.99.1388086920366; Thu, 26 Dec 2013 11:42:00 -0800 (PST) Received: by 10.140.48.75 with HTTP; Thu, 26 Dec 2013 11:42:00 -0800 (PST) In-Reply-To: <18241430.1388083851066.JavaMail.root@mswamui-valley.atl.sa.earthlink.net> References: <18241430.1388083851066.JavaMail.root@mswamui-valley.atl.sa.earthlink.net> Date: Thu, 26 Dec 2013 11:42:00 -0800 Message-ID: From: Andy Bierman To: Randy Presuhn Content-Type: multipart/alternative; boundary=089e0149c510ce63d804ee752b74 Cc: "MIB Doctors \(E-mail\)" , "draft-ietf-eman-battery-mib@tools.ietf.org" , eman mailing list Subject: Re: [eman] [MIB-DOCTORS] A single OID for energy and the 3 EMAN MIBs (message to draft-ietf-eman-battery-mib authors) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 19:42:07 -0000 --089e0149c510ce63d804ee752b74 Content-Type: text/plain; charset=ISO-8859-1 Hi, responses inline On Thu, Dec 26, 2013 at 10:50 AM, Randy Presuhn < randy_presuhn@mindspring.com> wrote: > Hi - > > >From: Juergen Quittek > >Sent: Dec 26, 2013 7:45 AM > >To: Juergen Schoenwaelder , Benoit > Claise > >Cc: "MIB Doctors (E-mail)" , eman mailing list < > eman@ietf.org>, "draft-ietf-eman-battery-mib@tools.ietf.org" < > draft-ietf-eman-battery-mib@tools.ietf.org> > >Subject: Re: [MIB-DOCTORS] [eman] A single OID for energy and the 3 EMAN > MIBs (message to draft-ietf-eman-battery-mib authors) > > > >So, we found there is no dependency of the BATTERY-MIB > >on other eman MIB modules (except for using the ENTITY > >MIB which has its own OID already). Hence, we do not > >have a technical reason to use a common OID prefix for > >the current eman MIB modules. Rather we are creating a > >common OID prefix for MIB modules developed by the eman > >WG. This is a matter of style. Do we want to introduce > >WG-owned OID prefixes at the IETF? > > 1) Doing so would increase the likelihood of implementations > using WG-issued OIDs escaping into the wild prior to > publication of the RFC. It's not merely a matter of the > WG maintaining the discipline of not making the assignments > until, say, AUTH-48. Because the subidentifier values > would be easily guessed, folks will very likely implement > using anticipated values. > Some people call that "escaping into the wild" early implementation experience. We should be doing all we can to encourage early implementation experience. This has always been a problem in SNMP. First you have to pick a tool-dependent MIB file suffix . Then you have to edit the file and change XXX in the root OID to something else. The IETF just punted the problem to the vendor with the XXX approach. We never developed any guidelines on how vendors should re-root I-D MIB modules in their enterprise OID space. NETCONF gets around this problem by advertising module revision dates in the . > 2) There is a dimly-remembered incident in the past of > WGs giving the same subid to two different modules. I > don't think anyone wants a replay of that. > > That would be my bad in RMONMIB WG, right? ;-) It took awhile before a cut-and-paste error from 1 RMON draft to another was caught. > 3) WGs are (we hope) relatively short-lived entities. > After a WG is dead and buried, what would be the criteria > for locating new work within the defunct WG's tree? > After all, by giving a WG a tree to play with, we'd > be assuming there must be something meaningful or > useful reason for doing so. > > There is the risk that the I-D will not get published as an RFC. Since the OID does not really matter, it should be possible to have IANA assign a temporary OID, under a different OID root (ala /tmp directory :-) IANA could assign a real OID and replace the temporary OID when the RFC is published. My experience several times over is that reviewing a technical spec and writing code to do what the spec says are much different tasks. It is usually very easy for an developer to identify where the spec is silent or just plain wrong. This helps the WG fix the bugs and identify the interoperability limits. > Consequently, for me the answer to Juergen Q.'s question > is "no." > > Randy Andy --089e0149c510ce63d804ee752b74 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

responses inline


On Thu, Dec 26, 2013 at 10:5= 0 AM, Randy Presuhn <randy_presuhn@mindspring.com> wrote:
Hi -

>From: Juergen Quittek <Quittek@= neclab.eu>
>Sent: Dec 26, 2013 7:45 AM
>To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Benoit Claise = <bclaise@cisco.com>
>Cc: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, eman mailing list <eman@ietf.org>, "draft-ietf-eman-battery-mib@tools.ietf.= org" <draft-ietf-eman-battery-mib@tools.ietf.org>
>Subject: Re: [MIB-DOCTORS] [eman] A single OID for energy and the 3 EMA= N MIBs (message to draft-ietf-eman-battery-mib authors)
>
>So, we found there is no dependency of the BATTERY-MIB
>on other eman MIB modules (except for using the ENTITY
>MIB which has its own OID already). Hence, we do not
>have a technical reason to use a common OID prefix for
>the current eman MIB modules. Rather we are creating a
>common OID prefix for MIB modules developed by the eman
>WG. This is a matter of style. Do we want to introduce
>WG-owned OID prefixes at the IETF?

1) Doing so would increase the likelihood of implementations
using WG-issued OIDs escaping into the wild prior to
publication of the RFC. =A0It's not merely a matter of the
WG maintaining the discipline of not making the assignments
until, say, AUTH-48. =A0Because the subidentifier values
would be easily guessed, folks will very likely implement
using anticipated values.

Some people c= all that "escaping into the wild" early implementation experience= .
We should be doing all we can to encourage early implementation= experience.

This has always been a problem in SNMP.
First= you have to pick a tool-dependent MIB file suffix .
Then you hav= e to edit the file and change XXX in the root OID to something else.
The IETF just punted the problem to the vendor with the XXX approach.<= /div>
We never developed any guidelines on how vendors should re-root I= -D MIB modules
in their enterprise OID space.

NETCONF gets around this problem by advertising module revision dates = in the <hello>.



2) There is a dimly-remembered incident in the past of
WGs giving the same subid to two different modules. =A0I
don't think anyone wants a replay of that.



That would be my bad in= RMONMIB WG, right? ;-)
It took awhile before a cut-and-paste err= or from 1 RMON draft to another was caught.

=A0
3) WGs are (we hope) relatively short-lived entities.
After a WG is dead and buried, what would be the criteria
for locating new work within the defunct WG's tree?
After all, by giving a WG a tree to play with, we'd
be assuming there must be something meaningful or
useful reason for doing so.


There is the risk that the I-D will no= t get published as an RFC.
Since the OID does not really matter, = it should be possible to
have IANA assign a temporary OID, under = a
different OID root (ala /tmp directory :-) =A0IANA could assign
<= div>a real OID and replace the temporary OID when the RFC is published.

My experience several times over is that reviewing a = technical spec
and writing code to do what the spec says are much different tasks.
It is usually very easy for an developer to identify where the spec=
is silent or just plain wrong. =A0This helps the WG fix the bugs= and
identify the interoperability limits.

=A0
Consequently, for me the answer to Juergen Q.'s question
is "no."

Randy

=A0
Andy

--089e0149c510ce63d804ee752b74-- From blueroofmusic@gmail.com Fri Dec 27 13:48:28 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC63B1AE687 for ; Fri, 27 Dec 2013 13:48:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.299 X-Spam-Level: X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 kQoMwOdifsWW for ; Fri, 27 Dec 2013 13:48:24 -0800 (PST) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 805531AE674 for ; Fri, 27 Dec 2013 13:48:24 -0800 (PST) Received: by mail-ig0-f172.google.com with SMTP id hl1so30845573igb.5 for ; Fri, 27 Dec 2013 13:48:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=VjqKrdtu8f0/DPI5GbUQ/6tlz5LVsEBzv+Ex2z87t68=; b=weogHqAkHfJWBrYTg/0+evGeoSNz5YswlfhhC/ixXpRpGmCvTLbqO91IVTGHjUlM3h JQWr6hHAbHQVO44tRtG94YHt/bXICuYwvWWGl13o7Bn/BZC3M71fOcD8p5eEFCSG1PX5 N4/+EaAzA6cbFPh9vogHfzeyM0dIwjcig+ziojkDE/q3qNEt2RE6Rp6prWP33j5aMNMD BWAuUKmvVoR+4iPmpqmUf9XaOf8KpbIhGqJ3dWOzOv1EeNla4gkFs0aDFeeLVZV4ahz5 RI11DEga2pHmIJtYCukUM63qlN3tjP9fdZmIpIXzuXFmjZctoifcTPG2oHZI/jvHH3Ux jyAQ== X-Received: by 10.50.79.170 with SMTP id k10mr42315228igx.14.1388180899576; Fri, 27 Dec 2013 13:48:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.203.38 with HTTP; Fri, 27 Dec 2013 13:47:59 -0800 (PST) From: Ira McDonald Date: Fri, 27 Dec 2013 16:47:59 -0500 Message-ID: To: eman mailing list , Ira McDonald Content-Type: multipart/alternative; boundary=089e011827d66743a404ee8b0d3c Subject: [eman] Ira's comments on draft-ietf-eman-energy-monitoring-mib-08 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Dec 2013 21:48:28 -0000 --089e011827d66743a404ee8b0d3c Content-Type: text/plain; charset=ISO-8859-1 Hi Benoit et al, Friday (27 December 2013) Here are my comments on draft-ietf-eman-energy-monitoring-mib-08: (0) Global (missing series comma) - please always use an explicit comma between the penultimate and ultimate words/phrases of a list - this can avoid ambiguity and is always clearer writing - the explicit series comma is omitted throughout the current draft (0) Global (missing trailing comma) - please always wrap "i.e." and "e.g." with leading and trailing commas - the trailing comma is incorrectly omitted throughout the current draft (0) Global (misuse of explicit numeric values of enumerations) - please remove all explicit numeric values of enumerations in preface and body text of MIB modules - these values are frequently wrong and they create hard-to-find documentation errors (1) Page 6 (readability) - please add subsection 5.1 ENERGY-OBJECT-MIB before "The ENERGY-OBJECT-MIB MIB module ..." (2) Page 6 (grammar) - parenthetic clauses cannot be normative in standard English - please change "This compliance requires that the following 3 MIB objects from ENTITY-MIB [RFC6933] (entPhysicalIndex, entPhysicalName and entPhysicalUUID) MUST be implemented." to "This compliance requires that the following 3 MIB objects from ENTITY-MIB [RFC6933] MUST be implemented: entPhysicalIndex, entPhysicalName, entPhysicalUUID." (3) Page 7 (missing word) - please change "provide the log the" to "provide the log of the" (4) Page 7 (missing legend info) - please add a sentence explaining each of "rwn" for object trees (read, write, notify). (5) Page 8 (inconsistent usage) - please change "The powerAttributesMIB consists ..." to "The POWER-ATTRIBUTES-MIB consists ..." (6) Page 8 (readability) - please add subsection 5.2 POWER-ATTRIBUTES-MIB before "The POWER-ATTRIBUTES-MIB consists ..." (7) Page 9 (cardinality) - please change "A UML representation of ... are presented." to "A UML representation of ... is presented below." (8) Page 11 (grammar) - please change "In this table, the context ... are specified." to "In this table, the contexts ... are specified." (9) Page 13 (grammar) - please change "The difference between ... can be attributed that" to "The difference between ... indicate that" (10) Page 14 (poor wording) - please "There are currently three Power State Sets advocated:" to "There are currently three Power State Sets defined:" (11) Page 14 (readability) - please change "raised to the power of the scale." to "raised to the power of the unit multiplier." (12) Page 15 (poor wording) - please change "adheres closely to" to "is technically aligned with" (13) Page 15 (grammar) - please change "It is relevant to measure energy and demand only" to "It is only relevant to measure energy and demand" (14) Page 18 (poor wording) - explicit numeric values should not appear in informative text - please change "active (value 1)" to "active" (15) Page 19 (missing comma) - please change "eoEnergyParametersIndex which" to "eoEnergyParametersIndex, which" (16) Page 19 (grammar) - please change "period, i.e. a month," to "period, e.g., a month," (17) Page 20 (extra comma) - please change "value(s) of ,eoPowerStateIndex," to "value(s) of eoPowerStateIndex," (18) Page 20 (poor wording) - please change "It is foreseen that most" to "It is probable that most" (19) Page 20 (extra space, extra comma, missing word) - please change "Energy Object ( entPhysicalIndex), by the" to "Energy Object (entPhysicalIndex) and by the" (20) Page 20 (cardinality) - please change "which have their own" to "which has its own" (21) Page 20 (poor wording) - please change "must be discovered thanks to the" to "must be discovered via the" (22) Page 20 (poor wording) - please change "monitor the power attributes thanks to the" to "monitor the power attributes via the" (23) Page 21 (poor wording) - please change "this MIB proposes a customized power scale" to "this MIB supports a customized power scale" (24) Page 22 (poor wording) - please change "doing the proxy between" to "implementing the proxy between" (25) Page 22 (poor wording) - please change "thanks to PhysicalIndexOrZero" to "via the PhysicalIndexOrZero" (26) Page 22 (ambiguity) - please change "The RFC introduces" to "RFC 3621 introduces" (27) Page 23 (poor wording) - please change "doing the proxy between" to "implementing the proxy between" (28) Page 23 (poor wording) - please change "thanks to new PethPsePortIndexOrZero" to "via the new PethPsePortIndexOrZero" (29) Page 24 (poor wording) - please change "is copied over in" to "is copied over into" (30) Page 25 (missing capital letter) - please change "[EMAN-AWARE-MIB]. while the PC" to ""[EMAN-AWARE-MIB]. While the PC" (31) Page 25 (extra space) - please change "UUID 1000:57 ". to "UUID 1000:57". (32) Pages 26 and 27 (page break across figure) - please insert a page break before Figure 6 (to avoid widowed lines) (33) Page 27 (cardinality) - please change "The notion of identity" to "The notions of identity" (34) Page 27 (grammar) - parenthetic clauses cannot be normative in standard English - please change "should be supported which requires 3 MIB objects (entPhysicalIndex, entPhysicalName and entPhysicalUUID ) MUST be implemented." to "should be supported which requires 3 MIB objects MUST be implemented: entPhysicalIndex, entPhysicalName and entPhysicalUUID." (35) Page 30 (ambiguity) - in DESCRIPTION clause, please change "This table sparse extension of the eoTable" to "The eoMeterCapabilitiesTable is a sparse extension of the eoTable" (36) Page 32 (cardinality) - please change "This object use a BITS syntax and indicate" to "This object uses a BITS syntax and indicates" (37) Page 33 (extra period) - please change "fixed number of AC cycles. ." to "fixed number of AC cycles." (38) Page 34 (ambiguity) - please change "The eoPowerNameplate is widely used" to "The nameplate power is widely used" (39) Page 35 (misuse of, misnamed, and incorrect explicit values) - please change "actual(2), estimated(3) or presumed (4)." to "actual, estimated, or static." - please change "is not presumed(4) or estimated(3)" to "is not estimated or static" (40) Page 36 (misuse of, misnamed, and incorrect explicit values) - please change "alternating current AC(1)," to "alternating current 'ac', - please change "direct current DC(1)," to "direct current 'dc'," - please change "unknown(3)." to "unknown." (41) Page 36 (poor object naming) - "eoPowerOrigin" is a really a boolean - it would be better named "eoPowerOriginRemote" with a default value of 'false' (i.e., self or local) (42) Page 36 (misuse of explicit values) - see above comment about "eoPowerOrigin" name - below may not apply - please change "self(1)" to "self" - please change "remote(2)" to "remote" (43) Page 37 (missing period) - please change "transition Alternatively, this" to "transition. Alternatively, this" (44) Page 38 (poor wording) - please change "this table extends to return" to "this table also includes" (45) Page 39 (ambiguous special value) - this is a signed 32-bit object (Integer32) - please change "0xFFFF" (16-bits) to "0xFFFFFFFF" (maximum negative 32-bits) (46) Pages 39 and 40 (cardinality) - please change "hundredth of second" to "hundredths of seconds" (47) Page 40 (missing word and grammar) - please change "only sense for Energy Objects that" to "only makes sense for Energy Objects with" (48) Page 41 (grammar - comma should be semi-colon) - please change "measurement is applied, the same index" to "measurement is applied; the same index" (49) Page 41 (cardinality) - please change "depending on the capability of" to "depending on the capabilities of" (50) Page 41 (cardinality) - please change "hundredth of seconds" to "hundredths of seconds" (51) Page 41 (missing rationale for default value) - please explain why "90000" (15 minutes) is the default value of eoEnergyParametersIntervalLength (52) Page 42 (missing aging/pruning algorithm rationale) - please explain (perhaps more in preface before MIB?) the exception to aging of old entries described in eoEnergyParametersIntervalNumber (I couldn't understand this) (53) Page 43 (cardinality) - please change "hundredth of seconds" to "hundredths of seconds" (54) Page 43 (missing default value rationale) - please explain the default value of "1000" (1 second) for eoEnergyParametersSampleRate (55) Page 43 (underspecified RowStatus usage) - please explain why 'notReady' or 'createAndWait' in eoEnergyParametersStatus should delete usage data (this is not obvious to me) (56) Page 45 (extra space) - please change "eoEnergyMaxProduced ." to "eoEnergyMaxProduced." (in eoEnergyUnitMultiplier) (57) Page 46 (ambiguity) - please change "indicates a percentage value," to "indicates an accuracy," (in eoEnergyAccuracy) (58) Page 47 (poor wording) - please change "This variable indicates" to "This object controls" (in eoPowerEnableStatusNotification) (59) Pages 48 and 49 (grammar - five occurrences) - parenthetic clauses cannot be normative in standard English - please change "of 3 MIB objects (entPhysicalIndex, entPhysicalName and entPhysicalUUID)." to "of 3 MIB objects: entPhysicalIndex, entPhysicalName, and entPhysicalUUID." (in energyObjectMIBFullCompliance, energyObjectMIBEnergyTableGroup, energyObjectMIBEnergyParametersTableGroup, energyObjectMIBMeterCapabilitiesTableGroup, and energyObjectMIBReadOnlyCompliance) (60) Page 49 (ambiguity) - please explain why only 'read-create' and 'read-only' are described, but 'read-write' is not described (useful for statically allocated tables, using 'notInService' for a toggle) (61) Page 54 (inconsistent wording) - a requirement has to be paired with MUST (capitalized) - a recommandation has to be paired with SHOULD (capitalized) - please change "As a requirement ... should be implemented." to "As a requirement ... MUST be implemented." (in DESCRIPTION clause) (62) Page 54 (grammar) - parenthetic clauses cannot be normative in standard English - please change "of 3 MIB objects (entPhysicalIndex, entPhysicalName and entPhysicalUUID)." to "of 3 MIB objects: entPhysicalIndex, entPhysicalName, and entPhysicalUUID." (in DESCRIPTION clause) (63) Page 54 (grammar) - please change "This table defines power attributes" to "This table contains power attributes" (in eoACPwrAttributesTable) (64) Page 56 (spelling error) - please change "Ampheres" to "amperes" (lowercase) (in eoACPwrAttributesAvgCurrent) (65) Page 57 (extra space) - please change " watts" to "watts" (in eoACPwrAttributesTotalActivePower) (66) Page 57 (spelling error) - please change "A mesured value" to "A measured value" (in eoACPwrAttributesTotalReactivePower) (67) Page 60 (spelling error) - please change "Ampheres" to "amperes" (lowercase) (in eoACPwrAttributesPhaseAvgCurrent) (68) Pages 64 and 65 (grammar) - parenthetic clauses cannot be normative in standard English - please change "of 3 MIB objects (entPhysicalIndex, entPhysicalName and entPhysicalUUID)." to "of 3 MIB objects: entPhysicalIndex, entPhysicalName, and entPhysicalUUID." (in powerAttributesMIBFullCompliance) (69) Page 72 (unsafe allocation of new MIB objects) - please explain why Expert Review (rather than a new RFC) is allowed for defining new MIB objects - seems inherently unsafe (in section 13 IANA Considerations) (70) Page 72 (garbled sentence) - please rewrite sentence containing "and will, as a consequence" (in section 13.1 IANA Registration of new Power State Set) Cheers, - Ira Ira McDonald (Musician / Software Architect) Co-Chair - TCG Trusted Mobility Solutions WG Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG IETF Designated Expert - IPP & Printer MIB Blue Roof Music / High North Inc http://sites.google.com/site/blueroofmusic 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 --089e011827d66743a404ee8b0d3c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Benoit et al,=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Friday (27 December 2013)

Here = are my comments on draft-ietf-eman-energy-monitoring-mib-08:

(0) Glo= bal (missing series comma)
- please always use an explicit comma between= the penultimate and
=A0 ultimate words/phrases of a list - this can avoid ambiguity and
=A0 = is always clearer writing - the explicit series comma is omitted
=A0 thr= oughout the current draft

(0) Global (missing trailing comma)
- p= lease always wrap "i.e." and "e.g." with leading and tr= ailing
=A0 commas - the trailing comma is incorrectly omitted throughout
=A0 th= e current draft

(0) Global (misuse of explicit numeric values of enu= merations)
- please remove all explicit numeric values of enumerations i= n
=A0 preface and body text of MIB modules - these values are frequently
= =A0 wrong and they create hard-to-find documentation errors

(1) Page= 6 (readability)
- please add subsection 5.1 ENERGY-OBJECT-MIB
=A0 be= fore "The ENERGY-OBJECT-MIB MIB module ..."

(2) Page 6 (grammar)
- parenthetic clauses cannot be normative in st= andard English
- please change
"This compliance requires that th= e
following 3 MIB objects from ENTITY-MIB [RFC6933]
(entPhysicalIndex= , entPhysicalName and entPhysicalUUID) MUST be
implemented."
=A0 to
"This compliance requires that the
= following 3 MIB objects from ENTITY-MIB [RFC6933] MUST be
implemented:= =A0 entPhysicalIndex, entPhysicalName, entPhysicalUUID."

(3) Pa= ge 7 (missing word)
- please change "provide the log the" to "provide the log of= the"

(4) Page 7 (missing legend info)
- please add a senten= ce explaining each of "rwn" for object trees
=A0 (read, write,= notify).

(5) Page 8 (inconsistent usage)
- please change "The powerAttri= butesMIB consists ..."
=A0 to "The POWER-ATTRIBUTES-MIB consis= ts ..."

(6) Page 8 (readability)
- please add subsection 5.2= POWER-ATTRIBUTES-MIB
=A0 before "The POWER-ATTRIBUTES-MIB consists ..."

(7) Pag= e 9 (cardinality)
- please change "A UML representation of ... are = presented."
=A0 to "A UML representation of ... is presented b= elow."

(8) Page 11 (grammar)
- please change "In this table, the conte= xt ... are specified."
=A0 to "In this table, the contexts ...= are specified."

(9) Page 13 (grammar)
- please change "= ;The difference between ... can be attributed that"
=A0 to "The difference between ... indicate that"

(10) Pag= e 14 (poor wording)
- please "There are currently three Power State= Sets advocated:"
=A0 to "There are currently three Power Stat= e Sets defined:"

(11) Page 14 (readability)
- please change "raised to the power= of the scale."
=A0 to "raised to the power of the unit multip= lier."

(12) Page 15 (poor wording)
- please change "adh= eres closely to"
=A0 to "is technically aligned with"

(13) Page 15 (grammar= )
- please change "It is relevant to measure energy and demand only= "
=A0 to "It is only relevant to measure energy and demand&quo= t;

(14) Page 18 (poor wording)
- explicit numeric values should not app= ear in informative text
- please change "active (value 1)" to = "active"

(15) Page 19 (missing comma)
- please change &= quot;eoEnergyParametersIndex which"
=A0 to "eoEnergyParametersIndex, which"

(16) Page 19 (gram= mar)
- please change "period, i.e. a month,"
=A0 to "p= eriod, e.g., a month,"

(17) Page 20 (extra comma)
- please c= hange "value(s) of ,eoPowerStateIndex,"
=A0 to "value(s) of eoPowerStateIndex,"

(18) Page 20 (poor= wording)
- please change "It is foreseen that most"
=A0 to= "It is probable that most"

(19) Page 20 (extra space, ext= ra comma, missing word)
- please change "Energy Object ( entPhysicalIndex), by the"
= =A0 to "Energy Object (entPhysicalIndex) and by the"

(20) = Page 20 (cardinality)
- please change "which have their own" =A0 to "which has its own"

(21) Page 20 (poor wording)
= - please change "must be discovered thanks to the"
=A0 to &quo= t;must be discovered via the"

(22) Page 20 (poor wording)
- = please change "monitor the power attributes thanks to the"
=A0 to "monitor the power attributes via the"

(23) Page 21= (poor wording)
- please change "this MIB proposes a customized pow= er scale"
=A0 to "this MIB supports a customized power scale&q= uot;

(24) Page 22 (poor wording)
- please change "doing the proxy be= tween"
=A0 to "implementing the proxy between"

(25= ) Page 22 (poor wording)
- please change "thanks to PhysicalIndexOr= Zero"
=A0 to "via the PhysicalIndexOrZero"

(26) Page 22 (ambigui= ty)
- please change "The RFC introduces"
=A0 to "RFC 3= 621 introduces"

(27) Page 23 (poor wording)
- please change = "doing the proxy between"
=A0 to "implementing the proxy between"

(28) Page 23 (poor= wording)
- please change "thanks to new PethPsePortIndexOrZero&quo= t;
=A0 to "via the new PethPsePortIndexOrZero"

(29) Pag= e 24 (poor wording)
- please change "is copied over in"
=A0 to "is copied ove= r into"

(30) Page 25 (missing capital letter)
- please chang= e "[EMAN-AWARE-MIB]. while the PC"
=A0 to ""[EMAN-AW= ARE-MIB]. While the PC"

(31) Page 25 (extra space)
- please change "UUID 1000:57 "= .
=A0 to "UUID 1000:57".

(32) Pages 26 and 27 (page bre= ak across figure)
- please insert a page break before Figure 6 (to avoid= widowed
=A0 lines)

(33) Page 27 (cardinality)
- please change "The n= otion of identity"
=A0 to "The notions of identity"
(34) Page 27 (grammar)
- parenthetic clauses cannot be normative in st= andard English
- please change
"should be supported which requires 3 MIB objects(entPhysicalIndex, entPhysicalName and entPhysicalUUID ) MUST be
imple= mented."
=A0 to
"should be supported which requires 3 MIB o= bjects MUST be
implemented: entPhysicalIndex, entPhysicalName and entPhysicalUUID."
(35) Page 30 (ambiguity)
- in DESCRIPTION clause, please change"This table sparse extension of the eoTable"
=A0 to
"= The eoMeterCapabilitiesTable is a sparse extension of the eoTable"

(36) Page 32 (cardinality)
- please change "This object use a B= ITS syntax=A0 and indicate"
=A0 to "This object uses a BITS sy= ntax and indicates"

(37) Page 33 (extra period)
- please cha= nge "fixed number of AC cycles.=A0 ."
=A0 to "fixed number of AC cycles."

(38) Page 34 (ambiguit= y)
- please change "The eoPowerNameplate is widely used"
= =A0 to "The nameplate power is widely used"

(39) Page 35 (= misuse of, misnamed, and incorrect explicit values)
- please change "actual(2), estimated(3) or presumed (4)."
=A0= to "actual, estimated, or static."
- please change "is n= ot presumed(4) or estimated(3)"
=A0 to "is not estimated or st= atic"

(40) Page 36 (misuse of, misnamed, and incorrect explicit values)
- = please change "alternating current AC(1),"
=A0 to "altern= ating current 'ac',
- please change "direct current DC(1),&= quot;
=A0 to "direct current 'dc',"
- please change "un= known(3)."
=A0 to "unknown."

(41) Page 36 (poor ob= ject naming)
- "eoPowerOrigin" is a really a boolean
- it w= ould be better named "eoPowerOriginRemote" with a default
=A0 value of 'false' (i.e., self or local)

(42) Page 36 (mis= use of explicit values)
- see above comment about "eoPowerOrigin&qu= ot; name - below may not apply
- please change "self(1)"
=A0 to "self"
- please change "remote(2)"
=A0 to = "remote"

(43) Page 37 (missing period)
- please change = "transition Alternatively, this"
=A0 to "transition.=A0 A= lternatively, this"

(44) Page 38 (poor wording)
- please change "this table extends= to return"
=A0 to "this table also includes"

(45)= Page 39 (ambiguous special value)
- this is a signed 32-bit object (Int= eger32)
- please change "0xFFFF" (16-bits)
=A0 to "0xFFFFFFFF&quo= t; (maximum negative 32-bits)

(46) Pages 39 and 40 (cardinality)
= - please change "hundredth of second"
=A0 to "hundredths = of seconds"

(47) Page 40 (missing word and grammar)
- please change "only s= ense for Energy Objects that"
=A0 to "only makes sense for Ene= rgy Objects with"

(48) Page 41 (grammar - comma should be semi-= colon)
- please change "measurement is applied, the same index"
=A0 t= o "measurement is applied; the same index"

(49) Page 41 (c= ardinality)
- please change "depending on the capability of" =A0 to "depending on the capabilities of"

(50) Page 41 (ca= rdinality)
- please change "hundredth of seconds"
=A0 to &q= uot;hundredths of seconds"

(51) Page 41 (missing rationale for = default value)
- please explain why "90000" (15 minutes) is the default value of=
=A0 eoEnergyParametersIntervalLength

(52) Page 42 (missing aging= /pruning algorithm rationale)
- please explain (perhaps more in preface = before MIB?)
=A0 the exception to aging of old entries described in
=A0 eoEnergyParam= etersIntervalNumber (I couldn't understand this)

(53) Page 43 (c= ardinality)
- please change "hundredth of seconds"
=A0 to &= quot;hundredths of seconds"

(54) Page 43 (missing default value rationale)
- please explain the = default value of "1000" (1 second)
=A0 for eoEnergyParametersS= ampleRate

(55) Page 43 (underspecified RowStatus usage)
- please = explain why 'notReady' or 'createAndWait'
=A0 in eoEnergyParametersStatus should delete usage data
=A0 (this is no= t obvious to me)

(56) Page 45 (extra space)
- please change "= ;eoEnergyMaxProduced ."
=A0 to "eoEnergyMaxProduced." (in= eoEnergyUnitMultiplier)

(57) Page 46 (ambiguity)
- please change "indicates a percentag= e value,"
=A0 to "indicates an accuracy," (in eoEnergyAcc= uracy)

(58) Page 47 (poor wording)
- please change "This var= iable indicates"
=A0 to "This object controls" (in eoPowerEnableStatusNotification= )

(59) Pages 48 and 49 (grammar - five occurrences)
- parenthetic= clauses cannot be normative in standard English
- please change
&quo= t;of 3 MIB objects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)."
=A0 to
"of 3 MIB obj= ects: entPhysicalIndex,
entPhysicalName, and entPhysicalUUID."
= =A0 (in energyObjectMIBFullCompliance, energyObjectMIBEnergyTableGroup,
=A0 energyObjectMIBEnergyParametersTableGroup,
=A0 energyObjectMIBMeterCapabilitiesTableGroup, and
=A0 energyObjectMIBR= eadOnlyCompliance)

(60) Page 49 (ambiguity)
- please explain why = only 'read-create' and 'read-only' are
=A0 described, bu= t 'read-write' is not described (useful for
=A0 statically allocated tables, using 'notInService' for a toggle)=

(61) Page 54 (inconsistent wording)
- a requirement has to be pa= ired with MUST (capitalized)
- a recommandation has to be paired with SH= OULD (capitalized)
- please change "As a requirement ... should be implemented."
= =A0 to "As a requirement ... MUST be implemented."
=A0 (in DES= CRIPTION clause)

(62) Page 54 (grammar)
- parenthetic clauses can= not be normative in standard English
- please change
"of 3 MIB objects (entPhysicalIndex,
entPhysical= Name and entPhysicalUUID)."
=A0 to
"of 3 MIB objects: entPh= ysicalIndex,
entPhysicalName, and entPhysicalUUID."
=A0 (in DESC= RIPTION clause)

(63) Page 54 (grammar)
- please change "This table defines powe= r attributes"
=A0 to "This table contains power attributes&quo= t;
=A0 (in eoACPwrAttributesTable)

(64) Page 56 (spelling error)<= br> - please change "Ampheres"
=A0 to "amperes" (lowerca= se)
=A0 (in eoACPwrAttributesAvgCurrent)

(65) Page 57 (extra spac= e)
- please change " watts"
=A0 to "watts"
=A0= (in eoACPwrAttributesTotalActivePower)

(66) Page 57 (spelling error)
- please change "A mesured value&= quot;
=A0 to "A measured value"
=A0 (in eoACPwrAttributesTo= talReactivePower)

(67) Page 60 (spelling error)
- please change &= quot;Ampheres"
=A0 to "amperes" (lowercase)
=A0 (in eoACPwrAttributesPhaseAvg= Current)

(68) Pages 64 and 65 (grammar)
- parenthetic clauses can= not be normative in standard English
- please change
"of 3 MIB o= bjects (entPhysicalIndex,
entPhysicalName and entPhysicalUUID)."
=A0 to
"of 3 MIB obj= ects: entPhysicalIndex,
entPhysicalName, and entPhysicalUUID."
= =A0 (in powerAttributesMIBFullCompliance)

(69) Page 72 (unsafe alloc= ation of new MIB objects)
- please explain why Expert Review (rather than a new RFC)
=A0 is allowe= d for defining new MIB objects - seems inherently unsafe
=A0 (in section= 13 IANA Considerations)

(70) Page 72 (garbled sentence)
- please= rewrite sentence containing "and will, as a consequence"
=A0 (in section 13.1 IANA Registration of new Power State Set)


C= heers,
- Ira

Ira McDonald (Mu= sician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions W= G
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer = Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
= IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High No= rth Inc
http://sites.google.com/site/blueroofmusic=
http://sites.google.com/site/highnorthinc
mailto: bluero= ofmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0= 734-944-0094
Summer=A0 PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-= 2434

--089e011827d66743a404ee8b0d3c-- From Quittek@neclab.eu Mon Dec 30 04:05:25 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFB941ADFFA for ; Mon, 30 Dec 2013 04:05:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.44 X-Spam-Level: X-Spam-Status: No, score=-0.44 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 h5TbE02YlLfO for ; Mon, 30 Dec 2013 04:05:22 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id C2BDB1ADF7E for ; Mon, 30 Dec 2013 04:05:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 781F0106728 for ; Mon, 30 Dec 2013 12:54:51 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dHcWNzd0Ht4D for ; Mon, 30 Dec 2013 12:54:51 +0100 (CET) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 5345F106726 for ; Mon, 30 Dec 2013 12:54:46 +0100 (CET) Received: from DAPHNIS.office.hd ([169.254.2.18]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Mon, 30 Dec 2013 13:05:06 +0100 From: Juergen Quittek To: eman mailing list Thread-Topic: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 Thread-Index: AQHO+ndiYJGZWdpqpE2anb88yvyKyppsem/g Date: Mon, 30 Dec 2013 12:05:06 +0000 Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E8688B2E6C@DAPHNIS.office.hd> References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> In-Reply-To: <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.0.209] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Dec 2013 12:05:25 -0000 Dear all, Below please find my comments on draft-ietf-eman-energy-aware-mib-13 titled= "Energy Object Context MIB". I will send comments on draft-ietf-eman-energ= y-monitoring-mib-08 in a separate message. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Technical comments: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1) Section 5.1, 3rd paragraph: Since you are already very precise about thi= s MUST, I would add that the name MUST NOT have length zero. 2) Section 5.1, one but last paragraph: "Each Energy Object MUST belong to = a single Energy Management Domain or in other words, an Energy Object canno= t belong to more than one Energy Management Domain." This is more strict th= an in the framework where we say an EO "should" not belong to more than one= domain. However, as we have discussed several times, there are management = systems that use more than one domain (different to EnergyWise). I do not s= ee a good reason to declare that their model is wrong. Thus, we can recomme= nd "make it as EnergWise from Cisco does it" with the "should" clause that = we have in the framework, but we should not fully exclude other solutions w= ith a "must" clause. See also comment 7). 3) Section 5.3, 2nd and 3rd paragraph: Both paragraphs need more explanation and you need to make them consistent = with the text in the MIB modules. For LLDP you say "If the LLDP MIB is impl= emented". Why don't you have a similar statement for the PoE MIB? You talk = about "the" Energy Object SNMP agent. However, EOs may not have SNMP agents= , for example, if they are just a power interface. And it is not specified = which of the potentially numerous instances of lldpLocPortNum objects of a = device should be reported. 4) Section 5.4, 4th paragraph: "Since the communication between the Energy Objects may not be=20 SNMP and is left to the choice of the device manufacturer, an=20 Energy Object can have additional MIB objects that can be used=20 for easier identification by the EnMS." Two comments on this sentence: A) It is not very obvious if SNMP is not available, it makes sense to use M= IB objects. Please clarify this. B) Please note that the choice is not only with the manufacturer. Even if t= he manufacturer builds in SNMP, the operator may choose to disable it ;-) 5) Section 6, DESCRIPTION clause of object eoEthPortIndex: What "attached device" are you talking about? Why is it relevant for the specification of this object, if that a certain = MIB module "should" be implemented on that device? Does it make any differe= nt for the DESCRIPTION of this object whether or not this MIB module is imp= lemented on the attached device? I do not see why and thus recommend removi= ng the statement "PoE MIB should be instantiated on the device." 6) Section 6, DESCRIPTION clause of object eoMgmtDNSName: There may be more than one DNS name associated to a single IP address: "the DNS name" -> "a DNS name" 7) Section 6, DESCRIPTION clause of object eoDomainName: Please insert as second sentence: "If the energy object has been assigned t= o multiple domains, then they are represented in this object as comma-separ= ated list.", see comment 2). 8) Section 6, SYNTAX clause of object eoPowerCategory: Some devices match more than one category, for example a UPS is a store and= a distributor at the same time, and to be precise, also a consumer. A PoE = Switch is a consumer and a distributor, some devices switch between consume= r and producer, etc. We can support all of this if we change the syntax fro= m INTEGER to BITS. 9) Section 6, DESCRIPTION clause of object eoAlternateKey: There is a contradiction between having this object with MAX-ACCESS read-wr= ite and stating " This object specifies a manufacturer defined string". If = the manufacturer defines the string, there is no need to write it. I sugges= t allowing the operator to set the value of this document. 10) Section 6, DESCRIPTION clause of object eoRelationID: I recommend adding a sentence to the DESCRIPTION clause, that preferable th= e value of an entPhysicalUUID from the Entity MIB should be used for values= of this object. 11) Section 6, Conformance of ENERGY-OBJECT-CONTEXT-MIB module:=20 The dependence of compliance with entity4CRCompliance is stated in the GROU= P DESCRIPTION clauses. In our case, this is not the right place. There is a= dependency on entity4CRCompliance independent of which group is implement= ed. Hence, these statements need to be moved from the GROUP DESCRIPTION cla= uses to the module compliance DESCRIPTION clauses of energyObjectContextMIB= FullCompliance and energyObjectContextMIBReadOnlyCompliance. 12) Section 6, Conformance of ENERGY-OBJECT-CONTEXT-MIB module: We state in other places that implementation of the Entity MIB compliant wi= th entity4CRCompliance is a must. But in the conformance section of the ENE= RGY-OBJECT-CONTEXT-MIB the dependency on entity4CRCompliance is stated as "= should". This need to be changed to a "must" or "required." 13) Section 6, DESCRIPTION clause of TC IANAEnergyRelationship: For interoperability, the description need to be clear. As this TC is state= d, there are two points unclear to me: A) " The enumeration 'poweredBy' is applicable if the =20 Energy Object A is poweredBy Energy Object B.=20 The enumeration 'powering' is applicable if the =20 Energy Object A is powering Energy Object B." If the TC is used, how do I know which object is A and which is B? Is it th= at the DESCRIPTION clauses of objects of this type must refer to object A a= nd object B? B) "if the Energy Object A is aggregating Energy Object B" There is no place in this document where there is explained what aggregatin= g means. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Editorial comments: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 14) Abstract, last two lines: "relationships between reporting devices, remote devices, and monitoring de= vices.": The enumeration of "reporting devices", "monitoring devices", and = "remote devices" is inappropriate because it does not reflect the list of r= elationships discussed by the draft: poweredBy, meteredBy, aggregatedBy. 15) Section 1. Introduction, 2nd paragraph, last two lines: "Identification" -> "identification" "Context" -> "context" "Relationships" -> "relationships" 16) Section 1.1, 3rd paragraph, line 1: "A second MIB module required by the [EMAN-FMWK]": There is no MIB module r= equired by the EMAN framework. It seems you wanted to say: "A second MIB mo= dule meeting EMAN requirements given by [RFC6988]". 17) Entire Section 3 This section is completely redundant. It mainly repeats sentences of sectio= n 1.1. Remove this section and merge sentences you want to keep into sectio= n 1.1 18) Section 5, 3rd paragraph, first sentence: The sentence is not grammatically correct, please fix. Also semantic correc= tion seems to be needed. You don't mention "identification" as focus of the= first table. 19) Section 5, sentence before Figure 1: "The following UML diagram illustrates the relationship of the=20 MIB objects in the eoTable, eoRelationTable that describe the=20 identity, context and relationship of an Energy Object." You should mention that you UML diagram furthermore contains objects from t= he Entity MIB. 20) Section 5, figure 1: There is a dotted line at the lower left that goes nowhere. Please cut it. 21) Section 5, grouping of MIB objects is inconsistent. In Figure 1 you have three groups: "Context", "Identification", "Relationsh= ips", where "Identifications" has three subgroups. The sentence below the f= igure emphasizes this grouping. However, the following subsections 5.1-5.4 = are grouped differently. 5.1 is titled "Identification" but covers only a t= hird of the objects under "Identification" in Figure 1. Section 5.2 is cons= istently with Figure 1 covering context information. Section 5.3 covers PoE= and LLDP identification. Sections 5.4 is called "Relationships" but covers= not just the objects under "Relationships" in Figure 1, but also objects f= rom under "Identification" in Figure 1. Here is a clean-up needed. Please s= plit the last sentence from section 5.4. It firs much better in section 5.3= . 22) Section 5, enumeration under Figure 1: Please note that subsection 5.5 is not another group of MIB objects but ref= ers to objects in subsection 5.1. The sentence above the enumeration implie= s that each numbered item would be a group of objects. 23) Section 5.1, 2nd paragraph, line 7: What is "primary Energy Object information"?=20 24) Section 5.4, 2nd paragraph, last sentence: "It is important to notice, that it is possible that" -> "Obviously," "not have an" -> "not have any" 25) Section 5.4, 4th paragraph The entire paragraph is in the wrong subsection. It rather belongs to subse= ction 5.1 or 5.3. 26) Section 6, DESCRIPTION clause of object eoEthPortGrpIndex: See comment 5). There is a full stop missing at the end of the second sente= nce. 27) Section 6, OBJECTS clause of GROUP energyObjectRelationTableGroup: The comment "Note that object eoRelationIndex is not included since it is n= ot-accessible" is not really needed. Almost every Conformance section has s= uch objects and usually this comment is omitted. Cheers, Juergen > -----Original Message----- > From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau > Sent: Montag, 16. Dezember 2013 16:56 > To: eman mailing list > Subject: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 > and draft-ietf-eman-energy-aware-mib-13 >=20 >=20 > As agreed at the last WG meeting, with the EMAN Framework > completing its WG LC the chairs would like to initiate a WG LC on draft-i= etf- > eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13. > The WG LC will end on Dec 30 at 8AM EDT. >=20 > Thank you, >=20 > Nevil and Tom >=20 From tnadeau@lucidvision.com Mon Dec 30 05:44:04 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43C6D1AE0B4 for ; Mon, 30 Dec 2013 05:44:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.438 X-Spam-Level: X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] 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 ZJ5IxLmjdvGs for ; Mon, 30 Dec 2013 05:44:02 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id BAADF1AE08F for ; Mon, 30 Dec 2013 05:44:02 -0800 (PST) Received: from [192.168.1.101] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 68F0F269BCED for ; Mon, 30 Dec 2013 08:43:56 -0500 (EST) From: Thomas Nadeau Content-Type: multipart/signed; boundary="Apple-Mail=_9AC69A16-7F7F-448F-9914-7BDB7D942C11"; protocol="application/pgp-signature"; micalg=pgp-sha512 Message-Id: <5339BC8D-660B-4659-96DC-C0170E124134@lucidvision.com> Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Date: Mon, 30 Dec 2013 08:43:55 -0500 References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> To: eman mailing list In-Reply-To: <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> X-Mailer: Apple Mail (2.1827) Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Dec 2013 13:44:04 -0000 --Apple-Mail=_9AC69A16-7F7F-448F-9914-7BDB7D942C11 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 WG, This concludes the WG LC on the MIBs. We have received just one = set of comments from the WG and one set of comments regarding the OID = numbering. Would the document editors please address these and republish = the drafts ASAP so that we can proceed with progressing the drafts? Cheers and Happy Holidays, Tom >=20 > As agreed at the last WG meeting, with the EMAN Framework = completing its WG LC the chairs would like to initiate a WG LC on = draft-ietf-eman-energy-monitoring-mib-08 and = draft-ietf-eman-energy-aware-mib-13. The WG LC will end on Dec 30 at = 8AM EDT.=20 >=20 > Thank you, >=20 > Nevil and Tom >=20 >=20 > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman --Apple-Mail=_9AC69A16-7F7F-448F-9914-7BDB7D942C11 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJSwXibAAoJEPcO+I7eiUJZGkMP/1axk695lmsW3QlKnHCX9E43 cuK0WI+S3MVNlUKhE9x1GNUBl1fkz4IgHhofIw1cIUgurJXQGhmVTMamwrki4BHY dbACgmEmdukiGTK/xwXT0Z19cuss1ucBALg1iGb6WqEg2Q20l3J+6MaT9iX0jIEe FNwIKHFSyxgpBnSMo0kyKRXiCWh0Ch9daKj0+OHQ5HoF8uuXWgtuRRIGTNFktm3J tM6QuDNiKFLAp2Cd1mrrxReKFeTdCK3Gz59bbW8gcLd4VyXii7NmSYnNYpS8WoN8 uzUwNcqyVQdBC72EHux8+QncFY/PBtdZi9m3I+0TC3ys2hhvU9WMT3IvGU1MGW90 U4Np59TfnBMGNClmvzKj5MF/xwNcTcTTnSmeC6QN1nBc+rfn/W7ZR+j39rc08GeO pP+Mzha7x2jl4qITM+u11Y0t2qUMTcLwm8gvYr3aDPzGVvTAPQvz0lsTso7NbAeW 1cWXpuYUhf+HnJgRA3gLb0GI81Q+PS9rAkU4AQZfkITEL+CXT2/UCPC+nkpMMdTH jGQSvafUx8eBwAbOsPJxva+mZcKsEqE69MoD4S+V7jX2EnlpzfahQvkCDGqWq7kW gYvWsz71bQ71SuiZxUi9M/0FLm2RYk1ipyv/4fj970ZlFzx7s62OI/B6PIEujznY mBaTlHVWdfgZkxa8MuL9 =JMZ4 -----END PGP SIGNATURE----- --Apple-Mail=_9AC69A16-7F7F-448F-9914-7BDB7D942C11-- From blueroofmusic@gmail.com Mon Dec 30 06:59:04 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7E421AE143 for ; Mon, 30 Dec 2013 06:59:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.711 X-Spam-Level: X-Spam-Status: No, score=0.711 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_FREEMAIL_DOC_PDF=0.01] 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 NQSnS_c02CQG for ; Mon, 30 Dec 2013 06:59:02 -0800 (PST) Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 68D331ADFA6 for ; Mon, 30 Dec 2013 06:59:02 -0800 (PST) Received: by mail-ie0-f170.google.com with SMTP id qd12so12082708ieb.1 for ; Mon, 30 Dec 2013 06:58:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=LNUiBaP/4v9ZXAvKlqArHgOsyla9E3wJ6nY03hrABGg=; b=zmzPGn6HR550VVuv4doioOX03bSS0Jui3NSrpVaWywuRFls+yY6p1KGThhRTfft03R Racq6LS8CZKFDUAKpcmpLukkmAn1WwGzIxaOmok+A9o9l1jVidC3iFMCG74Z1BAoKdhY h2cgFj2bgEyRlA4nGDsteeJnSFX34k+uMGlqPBKKPvdLCbRqGVAFAFK4paC4Z/l7P6d+ sEV98O3IfOkrFQc40hgcvydZOd4SQ9+gFGThx/ZhUDlkxlwVzUrCWj43+rTd65BD0XND 2I/gSFH31C04y+GFZVrcWw0bpv3fqPwHKuwlcWSmILIsPJE+73Nt44RvScXx6f3+Uxyk iqtg== X-Received: by 10.50.14.202 with SMTP id r10mr40010963igc.18.1388415536420; Mon, 30 Dec 2013 06:58:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.203.38 with HTTP; Mon, 30 Dec 2013 06:58:36 -0800 (PST) In-Reply-To: <5339BC8D-660B-4659-96DC-C0170E124134@lucidvision.com> References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> <5339BC8D-660B-4659-96DC-C0170E124134@lucidvision.com> From: Ira McDonald Date: Mon, 30 Dec 2013 09:58:36 -0500 Message-ID: To: Thomas Nadeau , Ira McDonald Content-Type: multipart/mixed; boundary=14dae93a1007d9763804eec1ae25 Cc: eman mailing list Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Dec 2013 14:59:05 -0000 --14dae93a1007d9763804eec1ae25 Content-Type: multipart/alternative; boundary=14dae93a1007d9763004eec1ae23 --14dae93a1007d9763004eec1ae23 Content-Type: text/plain; charset=ISO-8859-1 Hi Thomas, Ahem - I did send the attached extensive comments on the Energy Monitoring MIB three days ago to the EMAN mailing list. Cheers, - Ira Ira McDonald (Musician / Software Architect) Co-Chair - TCG Trusted Mobility Solutions WG Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG IETF Designated Expert - IPP & Printer MIB Blue Roof Music / High North Inc http://sites.google.com/site/blueroofmusic 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, Dec 30, 2013 at 8:43 AM, Thomas Nadeau wrote: > > WG, > > This concludes the WG LC on the MIBs. We have received just one > set of comments from the WG and one set of comments regarding the OID > numbering. Would the document editors please address these and republish > the drafts ASAP so that we can proceed with progressing the drafts? > > Cheers and Happy Holidays, > > Tom > > > > > > As agreed at the last WG meeting, with the EMAN Framework > completing its WG LC the chairs would like to initiate a WG LC on > draft-ietf-eman-energy-monitoring-mib-08 and > draft-ietf-eman-energy-aware-mib-13. The WG LC will end on Dec 30 at 8AM > EDT. > > > > Thank you, > > > > Nevil and Tom > > > > > > _______________________________________________ > > eman mailing list > > eman@ietf.org > > https://www.ietf.org/mailman/listinfo/eman > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > > --14dae93a1007d9763004eec1ae23 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Thomas,

Ahem - I did send t= he attached extensive comments on the Energy Monitoring MIB
three days a= go to the EMAN mailing list.

Cheers,
- Ira


Ira McDo= nald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Sol= utions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-= ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated E= xpert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthincmailto: blue= roofmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0 734-944-0094
Summer= =A0 PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-2434



On Mon, Dec 30, 2013 at 8:43 AM, Thomas = Nadeau <tnadeau@lucidvision.com> wrote:

=A0 =A0 =A0 =A0 WG,

=A0 =A0 =A0 =A0 This concludes the WG LC on the MIBs. We have received just= one set of comments from the WG and one set of comments regarding the OID = numbering. Would the document editors please address these and republish th= e drafts ASAP so that we can proceed with progressing the drafts?

=A0 =A0 =A0 =A0 Cheers and Happy Holidays,

=A0 =A0 =A0 =A0 Tom


>
> =A0 =A0 =A0 As agreed at the last WG meeting, with the EMAN Framework = completing its WG LC the chairs would like to initiate a WG LC on draft-iet= f-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13. = =A0The WG LC will end on Dec 30 at 8AM EDT.
>
> =A0 =A0 =A0 Thank you,
>
> =A0 =A0 =A0 Nevil and Tom
>
>
> ________________________= _______________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman


_______________________________________________
eman mailing list
eman@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/eman


--14dae93a1007d9763004eec1ae23-- --14dae93a1007d9763804eec1ae25 Content-Type: application/pdf; name="ira-comments-on-draft-ietf-eman-energy-monitoring-mib-08.pdf" Content-Disposition: attachment; filename="ira-comments-on-draft-ietf-eman-energy-monitoring-mib-08.pdf" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hptuqvtq1 JVBERi0xLjUKJeLjz9MKNiAwIG9iago8PCAKICAgL1R5cGUgL1hPYmplY3QKICAgL1N1YnR5cGUg L0ltYWdlCiAgIC9CaXRzUGVyQ29tcG9uZW50IDgKICAgL1dpZHRoIDE0MwogICAvSGVpZ2h0IDU5 CiAgIC9Db2xvclNwYWNlIC9EZXZpY2VSR0IKICAgL0ZpbHRlciAvRmxhdGVEZWNvZGUKICAgL0xl bmd0aCAzNjA2Cj4+CnN0cmVhbQp42u2cW2wU1xnHaZ/6UikSbdS3PlWtFKrmqVXVp0oVqiJF6VNb qa14qEKqKlITqBTaqpCmKgiaSjgQsCHUAWODSSxhGzuAagSxtzHYa3xZgw1WML6Bsd0YbC5rfOlv 9m9/HM5ebOzdxTJ79MmanTkzc+b7ne9yzpzxzEzayvT09INodGx8/Ivbt03u3Iuyc2pqaiZXlkHp Gx4/3tKfX9e9qbz9N8WtP9nb6Ap72L/t9FUqhK4OUhl8OaVluWAvMALEd9+t/8qfz31p439WvV6F sOEKh5BvvBOiGiJ8AjczmaOW8XI3Ogkm1A4CMXr+req1Ww7/cnvpPwpK8oorJUVFRZs/rGLnD7d+ QgUhc4UrcB3cZk6lGSpt3bcwDcP0wqaPNuQVl5aWnjlzNtIQuhJp6bp6tTtW2EDam8Mcgh3UQGa2 ZpYIsupwFx2AkJdTbxr9Hu4LVwYptI3m0X95RXlTfR1QhoaGsBHqTDycdIU9pBkDA/1wPFR2Aisz bzm78erHSH7VZ5PR+zleaSlkBQpPIoVB4fEaamvABAugpD6dbDBIFG/dCDc2vpp/UpgM1osbC4E+ 8sX/ngVY07GSBVLKJSCFW8PpYU3zYvKQRcfv4CGJZatfPyqbghTRDbsD+srGNDH1MDJ0paijUsJ2 2qmBg8TbSOH90C2RaCEGlbBf4e6G+68H/nBdiUhxNcxqEVdbhqkXWS5ZE5GdXNdjQZiA0ZsX3kV+ fe4vbN8bDfon3sZEPxfdACV+coAEGrwfNgWppfQKYh82hYWSmYj7CnCAkKJX2wCTrAk34j6XB+uf FfnDNwdUwTAZssXlfro1sCBFRkFqh/dbyowEFsSDkFGcOnVa3m9lhCpsypsNIKC77oInNVgvVf4e WEO9gx6sRVuWQpVIyQESqrwGLKIocpFs0K/obCsmqZALsr7N39CFizxpvGVhVh6sNN7dzKoxVLv0 NIDmwUuJ/QobgWqiQELSi424Q35ZFqSQb5f9LI2wuItrVuTYRCvMigw8N5BJWDAiYgQaI3fSCDTe DZpZpReWeWCZFckAd7eAmCsJY7EGksTiUCiYKPCcPD8VrdILCzdFwiZYWDRmtXbL4ab6OtcD50pC XqiIYQhGhAuKT90FC1JphMVl9bLDfCB2Teb27PjA6biSlsiSCVhuxi5YG/KKu7u7V/w7RFQXWMdY H3J3qMEVTCb1bDOHMKi+4XEJubRXGYsDlkilEZaXBwJr84dVw/3Xswbrxsnq/oP7E0pPQZ5Jx3vv mXRv/Svy+eY/Sq68ud7k8m9/gbT9/CWk6ac/kqA611GgNABN3Cyf7vlXMuEoUQlkKQbFeCQ5JcaS k9H7WYCl2XX3jVUAK4vZBVCkfE8A1NtxeejxcvPxMjDQj/T09nYePRb+wXck9d/6OlL7tS+bkANw rpHCdqY71yMz3X+SGCPbM9X2ChWomfBlt+XP6uSM+iHraixDsGwy8GnBAorLyOxFcrs5PC+s1KSQ 0tJSgFpCBQJYSK5/thFpqtmBaFscrQIRId6+8IEurLziSnxRxmFNRhPDevzWmYblAfKcG37SXZaD oAqTeUkhRUVF6NzuCF+ghKveKD+2K5CKcjJwSfDOrmaHkZpqWENNopKnjXhYXDPTsOhm9kLEYDEe z2aC4cFyA5AJde6NBhmyJ3B0MSUkVf7cKg8WTox0l1Ft6MJFhkhYqHUDtptaOyOhfSKFDNW93N4c 9ozrqVgWRLAsLXHRq0ZgMSrnEbIGi4TB5UIIi08YEDgSF7xgl5AU+0kqhCkhrGBIG1tEx9/4eTC4 BG/D614WLAR2KP+JLIsKmmhKe4Jhc1yC9cKmj+hyXnqTNVgEKaC4mJTaSTiqs4hu8a6PDUih/9Sw ZuZ7hxtY2aVts7Bqn8MTEvLc3ksF8kB5pISWlSFYpJ0uLHlC0hu9LMtCQe0uGuGAF6ZkjCwJR3B9 HIo3KDY4V0tBqGakEsJKNjTWnDMZoAurteKV+Kk/g4Xe4qN8hmAxKBYmFxZhC3UtxRNOpSy4Ght1 AstIGSxNlnLIxeQlEm6EYicnKpDh3AQrhWV5L3HIDzXsCtJ4pYIxTBJgtUauuCM1WOAAbe1W1mDp vt6yseffqo60tS3OE9IttWrXE4IjoqW8CHW08tO1INfRee7Ow+SRomsZKYOV2rJ4umDAxfDK6DiA XAEWWUc8LC1tTZg/ZwgWbUaB3NFgqQHsfNK5XFoIAvkHb2W1xWLNFZPD1Ifb9Crcc3ceLCoo5UuI CeEskRImZQ7zWlZ0rO8RprksXWhGT35VYtvJYNkqu6zBwg8QtpRa2EJotlHsE+WEGBTmAylcKEL7 TWxVvL2GZpSq1wqcSMByfZ0LS0GEasbLS8txm4yUNfVtpPh58sffT2ZZmmsSKRv/kvudLnltdth1 bBfNA5CxWz6wKOQSdmuX1xMZF8+ClrQut6m+ThJpCDGcsVl9DeXINtlpSwcNlhydwZpdfxjTf2/H ZZJGD1aQPUZayNM0myFqCBuCZeLCCsx5bmYJUmR6okOTMHZiE49AHGf/8oSFK8S4dF8XFibA/gV+ U+Dq1vo5Plaz+ra8TUMD9yU4OnejkmDFk1JKTwUbTGl/55lPtYqbkY6QpYAVrDFwEgmIcAhMHLVh l9YhBNlgclh0CR7n6cCKpcrqKh4vgsu8Se88ExS9vZoltuwFWO2xzE0VcGVu8gAUIxXMJp35tPPo MZqnnByZHYvFOsPwzQGOIlpsT1O5HdSSwZJZWcqHTUEKxXreXrAseCWEpcXhKWDZy6y0w8J8cAKY 0qOlznO8UDU6WcrQQC9fZi03tobQg+UmD4AIFkTNgSBa8dPN9Cw22SQhQDEx0ldDlgyWzbcrTpVX lAM3XocLgSXLksTDooJZ1jcL16YXVhB2x+8wFnaXplvPgRfddSnjOHe5uweLdM7N8TRtq7l0d+iU EJNNxcslNoZqhSwhrMfm2xvWDJ5ec+rUaW8eyWCBciGWlQKWWVbaYcmf4224L/r0kMkfBt/ELQqW a7Cr1pXEw3LTBmChebk+LyE3TN4bE/etFoJiE8LSmyyb8SMeRUL7+oYTfDJGXDNSKWCZopLBAlOG YMkZclPxikeGzhnVPukHccCCji4YXPNXB17cWOjC0jyeCQYCLxLU1KZkmGAk0ZdipC5cIZkbDKZl nPEU5kPz3HmkYLDwOKnlCyvmAbhvXnGlffrhIcNXM/Jd+PpPWdbspdaVzAsL03DNJwUX+4jPEzxh MlgMBskAXRDwChZdxFZiBIli53rt//zj1SYJU3eDxd+nBUsjJoI7/nztlsOzGo7ziiBjFAY13EjC hQrs1NfiwbSMQyo1LBQLLOOSjAg4kgmWFbpwMRksuiKnE6082/H2AIgx8ryweCI92lOEpYfidqiU ZsiJqWHx6Yd96K3v9G32j50yKJ24+neFMIL+hrziQ2Un3Else52hOQfLw1OgcT+c8SQUqkNSDIrR M0P1i0e/5/EyTBzS62ODxR6u7LlB1BL0PXrgupIUsCQZhTWbb5A/91/n2fWZsBt6DJz3092DI+UU +1Scx2+oraEDYDLu0MabdCXfOPOH15YoLikPFvfF5HmocNUbUHDdnTCVlpYyiqE+DhObwsSQ9tjI zn3XzBPR9yR0P2/VCmQBpBW5SHZWOGvdKchoLY6RFmIa6J8WAsITfcVPBaPDKU31dfpUnNa6swR2 CwITqkNFRRkrNIOo5/ZDWkKTuC+NFCC1FhcKJn0xzSlQ09t/OphrWUFkvzmATrgC4wV9wOuyoAKn y9JVIS3/qcB9Z5oQvWZTNfUHNc3+0QCewtaZsI1gOKDhqNwXoQcQWl3MFZL1K45SzU0b0l7QW/wC Y32uziHVoQH6sF1NtTlkdTBvgbT7D3bsW/gUFeyy6V2kmvqo5s3c+W3lbMqrreVqfPbX9NrLzYWr RQ+lMrOiy8TERFdXV0tLS2NjY3t7+/37S1q20dfXt23r1vPnz8/kSroLDqSsrAxGWFZ/f/8n1dU7 d+4cGRlZCvq/v/MO9HO6TW+5e/fu7t27e3p6Hk1+TE5evnSJv6Z56nju6F6sJIuY1AfWtWvXrHI0 FmgePnzIBn9zak9Wbty4gaUkO1pTU3Po4MFkRzG387FSXFyMcwveTUSj/GxubiYdOX78+IMHD9h5 69atpqamE5WVBz74gI3R0VFgqQPgV8PhMJbLWVSjG/TOrX/OlfhCgrRj+/ZkR/fv34+SEx4ihKFk bdfW1qJ/bIQ9jXNfpv/7wAEgYkeFhYWEubGxMYUqgFIZ71obK9RsbW2lDdScN/nJwUJRmE9BQQHb WBk9v6OjQwaFLaBwL+JIn9SXqimwQP9YE5caHBw0u/vb22//NxTatWuX9mBrjHQEC0vM37sXQ4tE IsASqVxZCCy0je+CFPo8e/Ysf5WtsY3C79yZXaHBBoaDpeC7CvLzXaODSGVFhZs5YDv8hDt/IcIe 7A5HJ7LAIhrCN4dgcbAwFnTLX/ZgX0oGZHeWUVBgikVgMhxSbsDpwCLoQBDbMcvCi7IBPqDs37dP HhLiwMIACYhs6EbPwggoLQmGfCCFbfk3t8MPDw/jr/bs2YOtBXPjXV38vNLZKUsBDXkdagdNMLE5 MgKUc+fOCZBl+C50dhK8YA3oI0eOsJ/hAPRzeeDikkNRc2cM8FrgAMHAwEDUmdJh8MUhN+Kgc4Zj XIHoNhN8JDWAt9S5WB9ZB7xIRbAvTUFgYvSBJQ60n82CpeAP0zivBSCLYhDZ8/778nu5stwKsLBT nKR+YkQkIbnkfDnPVhGYiFYgIzDlUvRcyZVcyUL5P2nfhwgKZW5kc3RyZWFtCmVuZG9iagozIDAg b2JqCjw8IAogICAvVHlwZSAvUGFnZQogICAvUGFyZW50IDIgMCBSCiAgIC9SZXNvdXJjZXMgPDwg CiAgIC9Qcm9jU2V0IFsvUERGIC9UZXh0IF0KICAgL1hPYmplY3QgPDwgCiAgIC9JbWcxIDYgMCBS Cj4+CiAgIC9Gb250IDw8IAogICAvRjEgNyAwIFIKICAgL0YyIDEwIDAgUgogICAvRjMgMTMgMCBS Cj4+Cj4+CiAgIC9NZWRpYUJveCBbMCAwIDYxMiA3OTJdCiAgIC9Db250ZW50cyA0IDAgUgo+Pgpl bmRvYmoKNCAwIG9iago8PCAKICAgL0ZpbHRlciAvRmxhdGVEZWNvZGUKICAgL0xlbmd0aCAzMDg1 Cj4+CnN0cmVhbQp4XuVaWXPcxhF+31+B0oO9SBkQbmBVOWRFtkNXyVfocqVMP1DL5ZGQXGqXVMJ/ n+mvjxlgwRUJy6lUUraWA8xMn1/39Mzg3ezdrGwi939dZVFbZNFmNfvpd7PrWR7Rf5sz6m7rJrqa 1S23LtEqqVHK3/PZ6ex7RypLi7arov4fR6MqombRpU0FMpk+XNpDTlRkVP4EijkJVhVp1S4WISF9 0aaFEuamp9tVbRT+OqJ1s0iLbq+obdp09KAj5XkvWWHvBl4NqMjDgzI+rHvdpeKUTB8u7SHrhKC2 H0kx60JrekL6okk7oyztR9lzj7DOEoE55fGD1sS4qz4JtPdI6N61We2oRHnWplkVVVWa104vRfw7 h/nM/ZdHfujyakajnWzUozOo7XqeH1yd5dHrtSNPDF4dzp5/6YImI7Mdns4yjHMSK9myadOqclFW pi5qDq9mP88P4ryZb+Jufuz+RXFS5vM3S9d8HbvWOs7r+TX9UO8lDT2hJzeunf8+TvJ8/paeL+Ny Mb+j1sqN27iOmufi5zROimp+Fdc1j9m6MRc0g/i8ROcZvceIY3Q6RqCZQiAat7YRf4x/iQ6/nn1x 2NO5JMXGdCZPtF26MH2ToiYRi9zxKuafxkXpJEpUq6V7twbXK/dYy+/Kvb3G29s4adz4gkYXpGCS V9TlfvnNCdrKIIH+ucxL6OcCw4gi3qEXHfSK2fE8olr6LuZPLSZ+hu5794whPJNF55nMCEzWeMHz +DUPOfMseD53vvWvM0e/27V4sQdlZPGmTuuCLZ4zsFrHwZmaALKFzcnTZ+7fatSfe6m7hFBU6k8H E0bcsTJ6A0w9iGI3QVD8JLUkaEPmGgKgmjt01w1HwBqI7Qj6QFLVUqeD/gWNW74k9mdxWbBNGPOu A1QE8zQdE0fwvtf6VUZpx4nJMn5JvDawCHh8BvKw0+u4deI6KZYc+IVj2bp/n1Gnf5XREPJiaSmC JL71oyr3+IIeK6EA8t+9eaLkzrPFIm0lUg/jvKxgxRde5BWsApuVFBLO4JG3cWDIlhvXZPUzlche bwPh2YkrNTfRAN2XcUnUmCfGszdTapJYG0ldnXMRkQjMdkBN7t9BpROeDL8WBRSVrQNlWfRkCoFl qbWoeOqH4dWNGAXCT8ZWzdDKUJDASX8htqAOHV/FTryVWnCtnG/7DgweVffAdtF/V5Pj50L9QwLf c8+RBQw/I9mQfsuVhTa5EI6LgnDqXDS5ARROR/EUD9Rd1fcAGDI4Voq3Y8OLvYJI91EfA/gxn7Fv tpGCXEOM1O8CSJ/SKx6cjARJMoynmpYTA0e7COBMSL1PnmaHos3TRdEzBJRbK3mS6bYfqZoQGnBM MB7vyEksHVJdF1PKeZI44pYmM2mO5kIQPqYmjPgV/VzGLBbxRR6jF+iWWTAcacArJbWg1JlhbQvz XSjitvx2uTbgme0nIqzyMZ6o+I7DjYq7irlk3Oqizv2ywubzf7oM1nC0MJg4QYUj+wmcev4Vt8Si 84l6OcwfIW5l6cR7DTT43DEvGWEry7LMBd3nuk4HOq0UppDz0nOFAH7JuTVhLcigxMkkK5eNWTlI PKgjLhXAoQCin5edzQyMU3xun4tGnVOyXQTxurXCiyfK8qFZzuw4ukQmQ+MZNgV3bAbH0FN7Tz6y FeAkNJhkRmdNokOgvrNlBDzuPRlQnWbcohozLkQ3URSrDi7AKuJNlLrU6EIm9fkq8hDbXAyAEtYb Y4Yz4DDcnYluVAoSbMk5qQ2Lq8eHeuTl8Anccsmtz9hEZ5pN82LMpkz1nHRH6XunSfZcy4A7WVtU KbVI7S2yxBg28SZcj3QOFiBZe0BiggJV1/2nUjQk9wHoC3weG9alg8V4etqu2uYjp23BOb25seHP 4oLVSBXKaDxzHI2gZveT/iwZXObQvjetFe4G1nOft3uxeKLmtMXc4hl2tWTDuFQfSL4RH/hgnWLn ZjS3iB/DmGQrJh5eFisNL077wNKOqfnQCmhx31MPoze+DlzeMrxdv2TZIEmUmstslfHe8x4JNiF3 CmN0SKDXE0Oz/lBuGaYKr9U1c/24qaL4TVIFRN+aKn4bF6nNH7csSLHiUo6dq2xsLA95ryDsn05s Q8ZKrl//2J5gIzWHYsq2BNuJCSqflqCwIFiF/57qxJHshR+vjxhSKI/Xk6pzE+jsdwtLjNljR5jE MRi4ECYaWNKCW6o63V85D/ajdopZs9F8dGN8V+ptEmAZmk7rYx/pBGQSDfvd+yD6zaYBDAcwenOA PzgHgAjmM6IPuKqXg/pxJD3KDjHYMMDp7IWWKQVOsBKNH099OqWX7yxXhclCAXM/xeLlYjRbyXK5 VjbDxakZzagklWzLvdBj2w0sG8fmVaKV3JofktMQRuFCeCIuXfaR7tPmQ2FuiJa6zO+mt5Os1uzk VDpYDHPqd7GECZ8NiwKNWe1oHpqIcUV/CbX9GguK3U/LU2U9LU+pRGb5LWBHwm35qHXXynLzUMda GdmJ+Rdki28I6mj9EMuS8zcKBRbrW3pGuH2NMX8mwodxU0q/BeQUI1SjWUW32qcGvCDyUOQd0pnZ YJe9o4t7J8o4NCbf+rzRU6Rrh4qYL97glPWVpBnZbXKawf65DNcIVJqpbz6bZJBi54CneDJ8qcMv Bv2qn99PhGy258jGE+/HvaUfW5R4yePN73HcBec2XDcsLZNd8+bOslQPHMz7WsvCjakY4P+95qFI mfucs7W0ZFkzzHtWOAMrViD72n57PsWGxWJa2C8lMeti+sC91iMECA40sS/yoRTW90tdVbG83vQ0 t23Q0kwbroSyCpO1N8ECqmhofIky7JimUOvXSZ8wpFqTWxBeNEe2Ov7Caaeu0Ir77xrmkliDqiIo AmyPM8xFMC/yCFqci/im5sAyK0/6mZ4pBeNGAOmJwnoR88VYSZr8MslEu8fG/SBFToEL7uWGx4rR Aw0zDhEsMSjRgmu+lQYRE0NttUPoG+J2bGdKBp1h3dIvHNzEQDg7CVnqxpRc/CPxww8silsSnzHJ t+j8K9E5lK8LylwSyRRzBkfXJMxVbzu10qBhNRxjX2KRitMXh2L8MFfLsykUi/+1ZJD/fyUDAwET eQDnuH2YYs0s+xVAf+G9uhPWD2aJnXQjdza72ebR6QGWt0qIZgd3wYPUJbTqXcF6SaaUu9jpsZwH 56iSkuW29gOFnr8NPpr7C8btNjxvlKEMdGDe7+amlX55cBz568uWXinvjxDs4IXvwgOlB3t2ng23 rMU+vWGyLQD5IK2sfyPG5e4RjUlSiyRTbF7trNrVx4aIuu6Mc8TOCYLPkqdqwYkAKqZf9/a2u8fW tfW5x5KBpaLgBMpyiN772kE9Jo4sBCoLozdSzQP/YrHccICBn79iCDatkTV31o7eeucXTCyRk+yb j9YGgpvBmQ8ZM0iodtMoJxqDFGlbLNvBAQv3R3E6RdLgWEukq+PHoLozhx75nZxVJnhihG8HUAj2 jnw0HpKehuYumwTmR2TDnYMNXnBJRf3mwNL552Sn2yGMYAPCm78RBap2jzdC49V94wV1zUc51whO 5QJ0auXaBUGlBgguY4AHPr75iXr98U4idljUPA8/P/g6Asr+aJUXJqI8Gj3xkZuvAZRarVn3GyKL 2i5PC2xH84YM0tln1zBSucdINLlM5bPEr4jzFZ1LHccJHTkSx0uOx9wfZeekZFHaSY/T71M3tMLX zxE+71viC2mQuqIDuxV/p4rz9bwJBq6J0LVUrDndbgWEE8p8Oie5kOBKKB84PKJLv7xKukDwa3+G uOJnlF/0sdsZNe8xE+PX13yDxVCmomVzIbmnou83jBBGc9dbklE+qup/P1zyt9rijwW+8X+aP4yC OeWcLVAu2Aw3ZDv+avQ5eYa/iuk5jRZXxkpOV9F0eriGJpfeguhbUou9BFqjrmcGfyLr3Xlb/YFk KcgQn8S413Yj/0Hd6Mjh/1Pq7uCmPKsLOACj33NpYMLw3Thm3kDTT+iHv1zHgGP/oS9kPmdOVTYP nAWVUqBoZHnYHwRFKjkiB7zXp5yFXLPtkaqLlj7+zqKuSita++jp0c6V2Z5ZAbOXGf4UWV6C5QL7 l7rBw+cxbbG8DN/P/g2RNBJaCmVuZHN0cmVhbQplbmRvYmoKMTYgMCBvYmoKPDwgCiAgIC9UeXBl IC9QYWdlCiAgIC9QYXJlbnQgMiAwIFIKICAgL1Jlc291cmNlcyA8PCAKICAgL1Byb2NTZXQgWy9Q REYgL1RleHQgXQogICAvRm9udCA8PCAKICAgL0YyIDEwIDAgUgogICAvRjMgMTMgMCBSCj4+Cj4+ CiAgIC9NZWRpYUJveCBbMCAwIDYxMiA3OTJdCiAgIC9Db250ZW50cyAxNyAwIFIKPj4KZW5kb2Jq CjE3IDAgb2JqCjw8IAogICAvRmlsdGVyIC9GbGF0ZURlY29kZQogICAvTGVuZ3RoIDIzMzEKPj4K c3RyZWFtCnhevVptb9tGDP7uX2Hsw2YNsau308kFhqEFtmHDir00Qz+s+5AqcZIttjPLSZd/vyN5 5FGy4shKXbR2JN3pjnz4kEfe+d/Rv6OsGLv/Jo/HNo3Hm4vRu69Hq1Eyhn+bS2i2phgvR8bS1Q1e ZXCR+b9Xo8XoNzfU69PRi+/TcRLP4nJ8uhjFY/jnBknwIhmbeFaWY5vZWeo6LEd/Tt5PommaT4qo nLyP8HIcTe3k18hdnbmHl+5z4T74tKSLLHGvbbAzNEG3c//3g/tcR67DDXxdR3ayhRcf3Nh/jU9/ Gn13epCgqRFBpyycG/c2ylI3g5Xp6yjNWEzXzhKds+D1XWQMCldfwLvVFvuhpGv3dAXN2NO4uxk2 pvwyYvELPnsXJWbyHdz/Dq+STK+iuZmcQgt+YcuP2P019PwjsnNqwRffwhe9+IZ7DYEmyQQaUhpl /eDNtcBHoNomwPJFlCYkyVVkCoUXa2idgtNSK7ijmwXVbG/NxGQVWEigrhH5mqyAxqNeMxh7Fi6/ GAJNUc7b9La96D1X9K6glTh+zpxeAWrw3JPbfZEGA+ldWDuI3tUVCeJ6IZpKCbbyq4A8WunNz9KO hLgV7S70+KjhVnwIfVc7SeHHWBPF7CNmC16o2IdaqTkvmAw4C9wB0M8we2G6PGIrAo9p6Gn6KDpW yXfL0tcaGMu4ZMkuMJZx4bkVJLPwFKJijVfaCg6cumUCfHguALJv3/C8H6Pn+UmetP0EAvzTfpIA ZonI9R5bSQ/ou4xyS1/BhwY6SDo/loNQgAqWI8SvQLNgH/YEN84HBJ5mPAkcR0roaGonlVBCiP0f gLF9ihcBLRmrvvWSV0i2BdPnE3hLYvt6CwZ8XiEbOlMUV085BUCKeqiaQ/fGyvLAvYILEmAHrMw7 qYIL7T8ALzPP2s4Cy0UfZyknmch5PF8xZXIsX9lJGaxfEy0xcsG2U7EMjVqFgT7AQ7glGnyMpgkN JzFvj2fgYhxyNA6EgQnbQLANiIWz3elIqpJB5eohmA8jRTHv60SMoWljyG69EEE3AkklfVnlIeiF 3EVmrILiMsUnhCU3bV8BL4gj8BfC6XFfycWw79Gh1/6zCY5G6oeHOkEjAg90oSwb5EINJzENT/CK dYT2Cum5CU9DGISpHkJSHOJt6CzDIJCUDDAnFFKYkrfyuSA3tl7w8zq40zkofA9RCUauGq8C2C+f wY00GeYyKti3Yj+WFljgkebBf2hUXIweGhwHLBWMTMgWjgolWd1aTqMhzBKfNpxHUoTRcr3i2InA PgO9fL5TuUsydphrdZXvPs0BiT9RhZOXwwr4HotSWEMpC2FudtFJhbYwCgeXHYO3ipvgfuFdFBf9 gpRwcj4jt8htZy3f5ROstZsQ01QhlZJ1LWJ2iU5quzec3tn8EL0tragryfy2Qdal98GCmLNl5t9G ulqm6OR6Ds9b83ynuAdqw2bN0w5gBIXPvrbk2dFqfXbgZqj04RyDI4wPKtHmFy4vLYYNs0Xau+Le qRRAxAolDnzyDpWpkJ2ReoFCoL8Kp6VYLZsLKT1th+kU7xTFnMEfxq9j5flZeeSaeBtCgFhNb4xI bXfP6oRdnM4ohGqLVHcQhVu50AUPciHggHgqBzpjs4vJeZFdNqSQZiksiUqDuJDZw2pkFQ/DHkJL EBpn8yiQxQFAchZDraHsaqGIYvQDkJqHgWV2CmTOOZ52HH2w8JkDc5Z3180IJ25GqDXMpe0hyFA/ nB5tIebBErRCqcW0OMAdW4eoUWP8A5Uwe8UuYh60BrQpVsFAt/7DPNgoVw2VoGSdC6YQoSbGlhX6 PrKSz2YqOPt9mCGIHm/XDt6qlOi5T76YOzgbasS52V0z6aNEGV32UV/Wk7jGezbrMLeIO2thE/Vx C30ggRkWBeQ6GPuSu+NOml9lXEdEcZhDpPNhVXAP88EtyInHRSFUYZQSFFqLJvQQUlJbHXYkOYgh W1WcQM9CNwQh8W6Q+dKyd7naVs7sU86BtGT4+mjnGK22UindCVuw1fB8JzUdFWXpz4MP4eex8p00 P1oJyWGUxJPjHEBdbfHj85lfE8rmHrSEniVvlqh9B6w3T/x0QzTPepeFosm1z/RbOqgK9ZJ1UHw6 E1y0Hkbl0s9RI+6s2OyTDIOaLlYMU6vS1Cqudce/oflAMj9aofZIMuBBwfH0eYKvx9lIJ0JBaOja r3q7ZWNKSFHHXB3BZJA9k7J31bejsPEK13v03KchvvTYhhzHzaK5KpyQOEM0LTprQTokPYS5nzml TfKjJWD7SsTWb05wbwo+ISvluOjGFpa24k69HW6u7BOUa+FIHt7Ac6SzqGwc/zZUaZyWYMuSf+mC 6G6f4WhJZ0U1P5h+ewMnHjFjygvdGmuGjxWkgspcPFtUxPVuftJCoZWumpCudlF/INnjo517tjI5 HLy1L4E/mgJy/M3FfKWo4K0mYU0lB2g5pM9DrTe/bGcYc1bwEVNBDNPuHGtA/0FsK3sfZXZl7/vQ YEJ5NMI+RQMJd/9QE2nwwNdb75FUnx3gLJJ9CyFmBy6GZh0ETLFTwLF/HeaFjV+UZSmX6CYskM8/ bzFHK92krCoaZRX/IExietd2ghATFVQLoF/dXS2zAk9omiceWyi+xqlNZ0kBqpfy61iEI9sDB7yc zQqC4geYdhmVEKSmIAVIdkPETBJBKoHlzanFkS4xk69cV8jMUJ0EdtPdwzUOtYwKgDCBDWwMrQ6e 0HENA618UZrAto4aeAr5Dr8zvfbRdgqriIMCm6beVaalEnwF2KqWFdXHTgTnhDmcGcOb2H+Nbdfe Bm7U9YZu8PllGAh7X3u/cTLS07hsmCJzK1Gesz3mJaB+mD1kBDHKFSHgREMYbgE7Ohl9AZZ5gZcN o8GpJDycgaVQ4fUaNbkJCGJbBVdkpRe0FnWYnib4FtC7C1h9A7KkAMSXcIWz/gPN2JCg/RfQXKKZ ktikaADsfU/hS4Qhn8E3b1HTL+Grdk8NdUCOEStQ5iuaKY8nylio0gxZNNuNCfudIJ3lhHaK9F4v aOVyl7YxlEntzKTuhTKf5ZB5wF1v4/q3ZbIkRdizGP+kcZLhlPOXcGsKvHnlgsgbJcNvo/8Bt8Tr fwplbmRzdHJlYW0KZW5kb2JqCjE4IDAgb2JqCjw8IAogICAvVHlwZSAvUGFnZQogICAvUGFyZW50 IDIgMCBSCiAgIC9SZXNvdXJjZXMgPDwgCiAgIC9Qcm9jU2V0IFsvUERGIC9UZXh0IF0KICAgL0Zv bnQgPDwgCiAgIC9GMiAxMCAwIFIKICAgL0YzIDEzIDAgUgo+Pgo+PgogICAvTWVkaWFCb3ggWzAg MCA2MTIgNzkyXQogICAvQ29udGVudHMgMTkgMCBSCj4+CmVuZG9iagoxOSAwIG9iago8PCAKICAg L0ZpbHRlciAvRmxhdGVEZWNvZGUKICAgL0xlbmd0aCAyMDIwCj4+CnN0cmVhbQp4XtVabW/bNhD+ 7l8h9EMnDrArinrzgGFot3Zoga5rkaHAmn5o7Tju4tiu5GTNfv14d+SRktVUYec0Q2uHIo/He3l4 vKP8cfRxpIpI/8+zJCrTJKpPRq+/H61HMoJ/9SkMl3kRnY/yklorbCloKPN3OVqMXmpWj45GD56k kUwmSRUdLUZJBP80E4kNGeXJpKqiUpWTVBOcj97EkRgrCd9lvMPmRlT0eE+M0/hvMZZFvBR5Hn8Q enSGTZq0FOU0fqfJG3pGgh1MNR3AihisRV5ohm+jo2ejx0c3klUqlvU41iJlcarZSv05FrTM70J3 ghyn+nNixQeqhB40zXG81e2N+dTIB8lIPtc51y1UZA2KnuIyQXInkuUe2+U0261QabwSJQqKxhOp slIbAxd6QFOxBG70nkhlfA4zLsD4zc55732LcA4MPuhlmhlQg36XIqNVSVFoIRVNQL+ZtSvy11nT B4ud8z2wCHJqUU2HAvAcpL4AcRoUkcg9ZUvjspIsOWurSlpaq1yKUiLpu642mv8JGCNMnSLvw2gq 7jhGi1wdFKMbQ1GgzdF9Hc06YLLLV17oQDfSAIiyc9Nq4ApIQHjgABA3UcexBGi9xFnjYX0P0FqR cEBn8kaA3qBINqg6srq7GbtWURiS1fTLZtGU1i660xkG9wYu+4552/W+xgKy7NsDSgzZA5Iluf09 kOSH2gMeBFFSsv9zXOQpNB8JbzmtGGhn1W+cxzhYzS5gpYbhi5sMWf9jA97c0vZsImfMZgY8V8IA I8jh+VQNhbyDF4dpmvH8Kf6xdtBjCNmtZ4eaGLYsAeb3zz+yhYX1t7BFMe0DfyaGgD9lpW4d/Hle Hgr8c6OFFbNAona4KZwhtqwbTPoELrxyOLHH/c4Z48R04fphTsvyoQBGJXC3bX2snFukrfkAAoAb bXtSq3Y0r52quJSnpaboqqnhHqZmKvuwmYu7js1keihstnIDm6L0Z7toGqS8aqgA4mhBsQvnzs0a nyC/fIH99Z9C5l6sAY5B/sumg4u1vaN9L7m5kU7aMqSU5voCJpIme4qFps1Z2VvaFTdGJhDgXnwv qBIAajwgOO+8CgNhVhysijsCM7aD4CvN8Al0/yysmymeaE1MbudMPhcm8Z3B/CbMA9ngOuwViNQS Tn8r4y7K4TjguZhvpAZWRt7cyAv2CpM57S22ykGoUR5qbjmeZfJgxdbdP2uzZHB99H8+a1XZWwRV 4o5jUxW3UQR96axdW7eRmp69GI/IB7uwPsKWMweS2CNM+9Ady587wYJPZZUPrn4Gnspr+xSgPfF7 ykY8pOJpb6kzFUMgnolvB3F5sFKnU9TiDeTWig20XIjCiLubJHIXtMP8kdysijFXYHwrTILagpnj 6PWS7qwyQSKn1V5FArEvGQSh3IOQu/9omr2zr6S0lh1BFuFMFyms33fOZKhvGMTS4mAVyxtsPgar PH8I379BfKNFHoKbXgs1jXEEEzWkHHevmt4ilwk8E+/u2x0rZCtIte5m0TGYAYa5Ph9czODXG3gk tY2urPvn1UZK/2rpLXCZuOVei3Hl3ctxjkES9aUQX6u22qt0APHDXmL5iOegvnNBnU+VZmvwhRl2 IIbTgxU8f4Db8Itc84urI7B2gP1vPz9gN2hetkAxCdIpGVzlfE7GEn3VkbBkAcNlk9VeNQPIuPbV UcPQKKzwMMwnP02joogDumGOfuzATFHSX1vXnjHLmSsT0N/m8FjAeKvOdq8Uw2Any7DiyGUGmBGZ RIjlt0wqT2W2yJ7OyhY/mmTB4Kjdalj+4pKkuLa3VZy5skuMwfmopGFY65LeACl6QcvJAQVj2wVT XFkyDzJq0Vt0gTndaYmACnSa2qt2ALvDXvmUbJJjOqhtumfMgk7l09o7wQNvcmR6sBKn5yYHTQsu 3DmYwiP2RxYSC+cUcru5cfOuTnzFg69MpBxcrFhduoWJ0YUEZU28rNfoYzMLlNuWIe2SHRtXQYpU e7UHgG3YaxYfcKeMN746xC+HwzCQldfUGI63MUnOmQYZmw00Q5lnK1syXnB8o8g/42hvYKbS2At8 7R+CsPdq1tBDFqf4DEKHUHrP2DpZOvuUVsCkizNvt12bZYgJ/9ObiID1vboeN0SztFsZD7qVH7Hb lm7oZzl55/2lOwUokLtor1PXpb2knmGLGHlnykdhzhmgqR0E3F3R3itUWBQE+8tmtbOdEc+3RhKV UIVFaZlOZAFWqfinZ2gpdY2lYLKaFGSlX2Gdc1EBVMZQa8FiK4oEUrITJdxPaAPZbafDzHeaNNNy oSoSalLduUFW56IA7+rnNWW7svAIN8AIB+h57jMeQxyyc8Ykzgn07qBWwKGxMfC48gRfw7sbb2RN W0OLUJ/SFSnMRPrNmq50xhibNddN/cFstgySImaE1DT0HmSk3qRquULp6Jxl1h/TCqx+M38wB3bK kiygpmSGLdiOcuoH4JkH2Gw5DfIC6JyAp1DhzQY1WTkL4tgMWuQl5NXrelrgJ7DehbPVjyBLCoa4 LzDV0ZRnMIwDEv2/gOEK3SSTPEUHIPUlFfssDCVHOHOLmt6Hr0b35kSAGCNUzKjgw5WyJPachSpN EEU9+fv1myCdZGRthfDeLOg01M2yxSpPy0me6glVNsngNIanwc41s3kxmaLZVYJ/0kTS6lMqSAp8 eCjgdyZOhpejfwGqKPEDCmVuZHN0cmVhbQplbmRvYmoKMjAgMCBvYmoKPDwgCiAgIC9UeXBlIC9Q YWdlCiAgIC9QYXJlbnQgMiAwIFIKICAgL1Jlc291cmNlcyA8PCAKICAgL1Byb2NTZXQgWy9QREYg L1RleHQgXQogICAvRm9udCA8PCAKICAgL0YyIDEwIDAgUgogICAvRjMgMTMgMCBSCj4+Cj4+CiAg IC9NZWRpYUJveCBbMCAwIDYxMiA3OTJdCiAgIC9Db250ZW50cyAyMSAwIFIKPj4KZW5kb2JqCjIx IDAgb2JqCjw8IAogICAvRmlsdGVyIC9GbGF0ZURlY29kZQogICAvTGVuZ3RoIDI0MTYKPj4Kc3Ry ZWFtCnhe7VpLc9vIEb7zV6D2sCZSJo3XAOBWpVK73k1qU2Xvw9rKIcqBpl4bW6RMUM7y32f665me BghREGTmlJJEgYOZnn5+3T3Ap8mnSV5G9tcUSVRlSbS9nPzjT5P1JI3oZ3tNtytTRrcTU/HVR1zl dJG7/zeTq8kvltR3Z5NXf82iNJkndXR2NUki+rFEUlykkUnmdR1VeTXP7ITbyT+n59N4lhXTy7ie rmNjprt4Vk1/ju3QTWzK6b75Pc7T6Wpp73+kqx/jmf1c070LO3YZ59n0j7iopi9xI6LljljpiN3E 1eKQ0FvabUnLb+MsxxosXvrFF35E82YXKuZooaVbTVd0xaSr6W+0Hz5+pOXfx8yX/TyPISyovvmN SL4jYmdxanjwPUT6V3T298kPZ09SaWZEpcTQLankzstKEoiUa+KMRaGvJOac9v5q1L5pLvtGwQJM fjOKYpIKxa+suqYNdL2xbN4T56RhMQ3rq3ZbNyTiPc0myemPVm2h8523pKz9j12zmMI5YEJcMaGt 80nrHJ+wryVJc7ZEoMHqXHZ9wy75XewtS5sSY//2ql+xOpoT2L2sF8+w+ze0dyRDaoZ3ctMbgZUO wFrir01rQDC/pQ2XYLKolCGPx2B1jLtW8NnviL45Lkc5eFmaLlaR6Y39O4+joCti4DoWb2QHSUSi 8yAm2ZpMRbPvvfdBrL3FhzEsmhCDMw8wdk9oBmqMBId+IF7fvabLX8WYP4szss5+osG3IRxW0Owy dpHQkIzK3HcUJxSWNE6zGgWotBzGB9SCG1bTGEGLDjSA5xuOThdg9t/Ow/j7WMWBgog7xyeHeSMm E18WsAC/7GIb/1Vi/KqLd+CkRY2mWSbzQvFTMbCM88Zs8YXhtkyrh3R6IMmbAIsBR7avY9Y23MCL ST4N1UN3u+CPQNCuSlom0qaE0zjLidX6DZYrDENO3jiHM46AM5n3WtgYGNJnsTRx7CnXHmUxs8j7 8KOMh+BHJko5Z4hjj70grkjENdcw9YGqRyKJqdNeJHlahBstSE64m6UPhGpvqvQWAjg2gc7Sqwap lqEKZN9J6m32oe5beueIAkmXWExILB4keahVywWnGmf58misuv1bMWeCcnQZwXoHX7tAKGAxz1+K orx+qrZ6iPJe5fi2gg5zLnuYnX5EM8041RS9SbWKhwRFqLzOO4jN0SFucudW8rCA+AV2GcV23p9o v0B4XAXo+8PXQmIImAXmlgIiyCW+orDtW1Le69B3rNCprCT3NPPgRjxjfAdgsnSom195r3IiWk4u RA3QTI+QkRB6SEDrmPuVJJHmGcVesThoTMnb6kF+WSi/PF2xV9TmVD54JPNDarrgpgmmY/c7LOG5 +6h4r4AUAimMVpZQyk2VtPG0aB85aDMMbXRznCmro41pP/oKn5JYO1I51OxI5TtNlqkTmsNFLp8r crHo895FPMR7jfjCObeMnImYrbYrSSyqIxe1ZC2OJq0niaQaBk41LrFEAfmwcoWe3Xfg7YqA4b5K xce4+VOFD5j5TEaTsujee3QzMuLUadUXjrilyHfPc1mqcxR+7rCo01c3oQqA2Leck1uhhgwHq+oD p3AWIk4btNwAnFoGwyznRwVoPQdZ1fnUI+HYUooqbzsHfE1LCc7gWgdWJWpJR/omlEA7H6Uob54j Y3qy8gAgQqt4DIGy8bz7XWp3PhWSaHCG4rgzDFJox6nG6SgZXC3oPgFosRF+nsLzQ9bXcxlGRgmU VwclA+k6iYeAbilW/j/odtRanqzMER6Dn2zXHn53LcXweoi3gkSsIYRZOI1k2qEkdW6QwgVejseT 3AwuYR6QybQBTk7fRCKjjd6V6AWQ+MXLUbwXJztJ4G40T6f97rpCJnOGUrJJ2wvhv7csOGOxnUKu HWer4wdz2laP8S8PMdrOVmr2X1zANHZC/hym05NVNhAANz+4ZGUnc/OA761MMr75zJPBZQW8HXt/ IGnAWyja8fUZuT9TJ2cqDbBvMWfD0oDvJToZ6+hBmaAXUmBA9et47ElHps6utGfAtpfxYVPY6nvw /ECdulx7j4eWYY2IMSlXJ71OISEqBNTwse/Me68UJc0/J7kxApv+UPBZzquaRaU94eHYOCRUPrSQ I2t/hrELPgklidU6PaaUK1DRMTX/BApbf7IQTP6r1wSIhorJPXKYZS05VA5XTz9Fxf753pUMyxPY 3SglF73RelA5SCOeHxz8vMC1b5QaiMUwCFIu9CDXXBQOfFF1E9psbKYe4XQCjsgDtFbSlY2LpKwX GLjBewowDK0PIxH7f160ZUk/agirgV3akyPYqvhz++kvMuAmdo+uJTp8DqwOSDi/VHI9GkAKp7pB ZBjlHgpS0NfS4RnRpVNz2Abzbv2J+b7VvJlu80ZT+J0Ffyg0Rv/p4mT5vBsyrbJpVMZM68Gpu7v5 uP2qk3XnIWVp1GWKLuY53scxXg5umdV7K7c+iISTcZsfvqpF8MXF22PwVYmaWvDVtCsUTP/iz2rS 7GQNJGt+y7WG8e8HqM5x4+9ANDSGnDOdJVjItWyklgoUcs1DCK4Sl0rVOBEaZ9Ljr2xpfwLH4aka FCLSck8pss4Dmmmx80f77H6Ru4/py3AGNkrq+uBsnPy4GOTHtfLjB+rzUBf6R/Q6oYwvxKuTIbr3 JaOeyHsv8KlVv5nBe/W8HkOi6sXiQgEWsUD1tC7LjtBHOThpeMcx087hKW4ECVVWl0Ko2Yiu1BlZ qJF8YdzjjklUUSsYZVU2T0uSp5Z3aiFjfkRGWpzPS5bvb7TdbVwTXzPyJmLnI0dGmoo7pPQSl2XD h2lqqCDOC8scZEipoLKDG5C6jUvyk5RaYVgyLdXEDXfG/EpASp2NIjyjAtOvmf3ugnpG1rVdPW7N nMVntWJ8TRGt7qw53i0L22u63GMl5m/W3MCymSzVzZa/YPw6EMJsvvWeeOTRpG6ZIrdAVxTeHoua tP40ewgFMcoNayBfsBruSHffgI9XZJlXuGwZjVoJGpyTpSDwZgNJPgYN4t6KrthKoNVret7gL6S9 +6CrPxMvGSni6xhtnZ35gW7jRgr7X9HtGmZKE5PBAJj9mTOzMMNQhpV3kPRr+mjsqOEJ8DH2CvB8 wzsVyVQZCyLN4UXzw0A/HgTZvGBtF3DvzRUHr72sWqRMVs1NZhfUxbygxEbfBhvXrZbN0gxqzxP8 y5I0x5YLvCRrSnz51sLFG8XDL5P/Ao9ZAf0KZW5kc3RyZWFtCmVuZG9iagoyMiAwIG9iago8PCAK ICAgL1R5cGUgL1BhZ2UKICAgL1BhcmVudCAyIDAgUgogICAvUmVzb3VyY2VzIDw8IAogICAvUHJv Y1NldCBbL1BERiAvVGV4dCBdCiAgIC9Gb250IDw8IAogICAvRjIgMTAgMCBSCiAgIC9GMyAxMyAw IFIKPj4KPj4KICAgL01lZGlhQm94IFswIDAgNjEyIDc5Ml0KICAgL0NvbnRlbnRzIDIzIDAgUgo+ PgplbmRvYmoKMjMgMCBvYmoKPDwgCiAgIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlCiAgIC9MZW5ndGgg MjQxOQo+PgpzdHJlYW0KeF7NWm2P28YR/q5fQfhDThtYMt8ppSiCBEgKB700ca/Ih7ofZJ505+Z0 uoiym/v33ZnZmVm+nEStc4Fhyya5y+HOM8+87JC/TX6bZGVk/xZ5HFVpHO3Xk1++nNxPkgj+7G9g uCrKaDspKjq6w6MMDjL3/+1kM/nZivr2avLq+zRK4nm8iK42kziCP1ZIggdJVMTzxSKqsmqe2gnb yb+nb6dmlubT3Cymhf29NZGZZcn0J2MvruyFG/tb25+9XE0ze7CkEzvnLU7YmryavrMH702Fsz+Y ajnd4UFRThua25g0mz44WfV7Yy/BzXf2HpT8EaTQFTuEd65xOeY/0dUPk++uztIvLUS/GapHizjA k25BNi7ALU2OaQHeelmje1pOlk6vZQJAkdrfjFVH4TS2g6lw/b/2OioM0g44hs9xoL/GK/eAFw2u PcD3/IRADJJsEIMHWNudWxfoi5quRa8a8VnBLKt24dvfjr4waTKN7envYK/vTVJ0/8EZzA98bgKy SoAKTwkvsgYAHahenIh6kQJ7cPg7vr6wTzy+3JMqbAGeFYqoEjQ0Eh4ZikeRGpHNB9MPyi3kdsuH 0kE0qlAwymrQn0tzxJ+brkMT+5HqynIQE4P9WhatGZM9nl6zDvdEHefE4hSPgVqVw178BzAYZ3yA QdF3D1OuxXC3YE/25sV0o87diEPvCK8Cb3sRpGKRjWXxLTwIWYdUuxb0vXW74EamdctmmbTsnW9i xC1s3elyiHCVOZVAiE+aQLYUZgHWRil0w9P/Z2ZJiZoo0wapSnGaJklScq5reUADgTRMqueioVgD /eXR8YvF4Egj0G2EFHua+B0gjKIxXYB8J+IfMJ/yT0ZJpabwQsPKFA1UYTSIi7H0FV8RVSsNrb+y ylwsrB1qqr+9umFW79kKlWBQjsSA8aU5RC8vGaGTBUFRLJIhj1iYMR6RiI5vh3nsaiNP8ZkeolP7 hHeSG9TGFWIOeHGXd8ZnIwGuzkjS6x1TXKwX5kJFuXwuF9rSHXYG3o8BUuPiljMv3u5VaJ2a78H9 JG9xUH2pt7DXFGq7ZuU/w5MsWQGuY+0RRqqiGutfsgqGoaCMttVoIlUm3gVaPgmA8xjQ4C/d546H oPQgqAJDTJFlQ34FNct5flX79YqlC+iPZvLqFYkDgRVLkSbPxXNGkrdQAu9A1pS00rZaqeDUbHP4 X0rQTtUWOZrZVW3Cc0QRL8dyuK+jK3ScrUBFKUUlJPWVlDkdNZ3Vu8YWujd/jMb5ouhSFnbWUPZ8 fpTNq2fbJj5Dkd2EGaQcvVf8rKrsvN+mKRxFziPSiSpby40DZQZ1L287p9YdKsTYdwkLuAnbQHft xojr8jhqfWKXJ3+iy3OKupKTZSJMUlxQH1saZksi6KPHacg7ceeHxMGbpOEBvTSJQpgdyXetNFRa uz0NW9KrSIYitodv5eDlfYOX1HtdtMLTm6gaAnQyuEsFySCzU4MjBFiIA+w/efuvVqmgEOybwT7Y vq3M342X+G7OUyON85YSzonPkkFQZIvexhdcktp0p1wyNaNdku/XahLOXim/CVGNru2JIuMOO5hZ 6rlrd7vDTayBOOAV/ivfqcL8NavCNtKj/NUZg0uHvWxv4Qq51ZbTyV5ld6Q8GD/ei6/VYkbeNnmb cRV2STz+FgjwdThM5ZFNdbv4FmRwgQ9mMICTjAPH7MgFaAslEWy4tPJyMZz6m0c0Ce/PaVl73jN5 m2uOWA2mcY97jKGKc1YIAWu4gfbnhqYfJa4jxd6dp0gaV/Oypcha18Xh4rXqVrsdfalGQQ+98PIA xwXdhO6bgxpeRjxuILMoIAXytt8ThNCYmTGhMZPF/Dllb/Z8Tb3PpuzNxnfnPquyN+230oBI+dlE OpFjnyqpOhVrpW8qP/BLHhrbr8Skfsj1iLo2oVkgDWyZSUo4liyHcskno9GhMvoCVMInS+UegxwD A4Eb7pn1uufdFOF30YVenByyVBtpB04wNNj8kydvCXbP9G/gQEmyDtKn3wADbzj9rr7rDe2QRDmh /UJ+o1Rmv0dJb5jctClChQ9ME1INueD6J/ighlvRvKZAawZ21Ea5QX+Pd4GDO7byG3xARr1lgOPx QrnueHRRa6SU0hlOvhFiwZ2/GPsoWQOBdhGEyHA/Teq46Ej9M0zuduXT53bP1JAFtM5rbgkzC5OE DKEOU01cQosoHCdhyhOpQa99OFchQCXLwUDgfMjLxNoJlz040wS18uoqwBTK14+0pXdMIMJHGlkl uUrQCGN/Ug36/tH3+uL7hVHfF3dAONXwFHq5Q1p/wkrLMD8dUU8d4/KlaIJvGBAM0g7uuGbb1PxQ rXnnoHlQeZLkoxvax3LM5YptMrhqy8uaVzxXMNig0k7ScPfUg/4F07RHQOu87LaPcKz3CmwfyIZ0 sAM+7vOA0ihvJTj1vi/71I9Lkuf7PEpsc+0WLZ/LaPDrfm6Gj9XAi6bn/XXVx+mJPt9Lt4gQPMZ/ T6VZlBTM3IsWTzvNDiujbQjXTKnpJS0eP4LbvhTRkRehW8k6cz2Ho5t6zLgIdk0vQCU64MVApvS/ rQIuj3uxXxnlMjjXzv28xvnQJy7tZl7Ysp/v46kr+EbuVgKKy5eyNfA6PXAKntt5f3CKQPbZYTve 8V9TsQ6F6qDZ/amvNnWD66XRHevXHGewFmVIFy2nvW6PMruHHFdimWwouHj6kT+3PVAJU9EurAur q1bOQhW6JEXqw4qc6BAyjirYsUdplc6TEsQt5CtmfER25BFwczYvSfrfYI1bs4BAMQNmwMLvQJvI JInw2B6+1p7iCkx5YafaepVsbMdruLhDUVtTAsET2PxgBZSU3sQdCLp3LfAE6k5P8Ax2tHzP7L2j 5wwgtYbDoZkr/mcLb+H34AveyD3V13YJNiXbw0e8E+fv7qmUBNEodbenE7x+o4JwNg29gzXS1XjR MkVms1qesz2WC0D9PHuIBDHKLSGQLQmGB8DuK1zHK7AMvZNoGQ1escPFOVgKFd7tUJM7RRDHajgi K72icnnA9PSArwG9D4rVX2EtKQDxhcFvuOzMX2EYBxK0/waGF2imJC5SNADO/kiNIVkMxWC88wE1 /QL+aezVgiYgx1xqhvNbelIeTz1joUpzZNG872fHnSCd54R2gfTebSiD2sOqJapI0SPjaJHPc6hi 4Gy0cd3d8rAkRdizGP9L4yTDRy6/gtOixJNvbEC59Nbw8+T/BNBebgplbmRzdHJlYW0KZW5kb2Jq CjI0IDAgb2JqCjw8IAogICAvVHlwZSAvUGFnZQogICAvUGFyZW50IDIgMCBSCiAgIC9SZXNvdXJj ZXMgPDwgCiAgIC9Qcm9jU2V0IFsvUERGIC9UZXh0IF0KICAgL0ZvbnQgPDwgCiAgIC9GMiAxMCAw IFIKICAgL0YzIDEzIDAgUgo+Pgo+PgogICAvTWVkaWFCb3ggWzAgMCA2MTIgNzkyXQogICAvQ29u dGVudHMgMjUgMCBSCj4+CmVuZG9iagoyNSAwIG9iago8PCAKICAgL0ZpbHRlciAvRmxhdGVEZWNv ZGUKICAgL0xlbmd0aCAyMjUxCj4+CnN0cmVhbQp4Xu1aWW/bRhB+168Q8hBri4jhcnkpQFE4Z1M0 V+OiD3UfFPmQW9uyRTmN8+u7881epGhHpOMmSIvEMrnH7Mw3x86MfD44H6h8qP9naTwskni43B/8 9t3gdCCH9G95SNNFlg9PBlnBT8d4UvSgzO/54GDwRpN6uDO4/zQZyjiKy+HOwSAe0j9NROJBDrM4 Kkt9ThYlesHJ4PfR7kiMk3SUiXI00T+7YijGSo5eCz041QOH+mdf/1R6vBil+qnUP3ih6VOR5aM9 HtHbUpBRiXk1xA9pZIlH2nMi0kJ/JApvS1465l8HRPhIFKP3opA4mMcX+mlGW2YXIssMseU+c5CN ZmBxV4g/hjs/DZ7sdEJDKofGGHT5yDPiGhxi0J21Ihbn9ERDK8vwDJjMjoXeSrvAZ+Whmzm48LEg 6ischOl3Bmc+GweRzEuANeWD9MQRkX9PY/tWDXQ4SOKtWq2pxsuw51XzhBSMJaRhcA3a1bwXhrG8 GsNjwdwSHxXp0Ms5mxMHU1oFkdnaejCQlxPHwB3NAMCDMfFByqL1Atw9p8eHwvFJq0kDfxIExN4M MFbWjPctnhh+PRfFZHRZATDoFfg9t6pj2GnPB7Lie70EKgonUHi69U0Ad0loVrA+604E9ktiz3ma M5QWf2XKevUaZSgKlJ18v9JCfLCkj2lwV0R4udNLyNwHoqH3hZXRSR+KmboNO3jgmavHgRCxWzWH VH5Gc7jnAWkaRQcBjT3olYAR5nATY0gmbcZg7hCcbcNcaLn0sDTXTDm6fGWDaU2F+vEF6/qpkJmO zXojQQM5HgmjeeBzZlA7soEch84asO2bkJVvdv66vdn4mzUJ7Aip+J58Z4GmFc9oJy8jVi+6IayK JJrkNYjPIFAnKkZPsmjTk7PKhjxkia+wrAMqrVReT1vyCHMHG6rLbgIlUkZpWpOoauJfBPAz8pq7 /uDFrRHvs4D3wuUpK0uTST2ypkxss2QayCNr/7B0m150kklOJtEkqQlFp3bB0EFgXC3TgagTD4xr NlG3husvdppYpDD5ykR2E0Qu2wIIwCSpOgmTyKQpjQ8//dLbLPc+b2JpronF4ppkH9hxLm8zhV3v cgQZyXYITWoQ6AXIXfZkMfP+1yV7pKcPDLlZOAVryt8UxehvvXQy4ozNX/KYh5YusWpLH6u4oLBa Hs984m8ScOZk66qbc6u+AUQah/E5zuDthj6gpa2RxKYaleEeaNjigiaDS+ydVWBQh7QBAUIaR5mP lk7XQMJLw8XD0Oc8zQLnk4yFtz0ChNP2AahcOBSx8sDpsmPQN/Cp1oBRrZxufWUXJlOBzdSGUKDW zMTJ5EnWbvQq0AQXizbldqUQa8TAae85BCaMvRXG2hhRlMyO4YZ+Ari8+Qbs0Qzq9EPhI3ZPd45b I44Un4o41IRIhY84jIW2z5nzIs5BKwdykAdbb5e5sQqueMOAcNhbpnTSHqKmvqK2vqwHzoW540gC +JLLVZoMo5GA2NZQBl6DrkDhbm9H1NdxLHZwkSPe8dwL5OlvdyjxDX3MmfWZobnyRq3YkD7aJsxe f+DKrANwM75FNWOu7+FC7NQHlCPrcUFBMLdVjglCkGbhEELK468Oj2XAQBk2SCykRdDwAXzwuh/p Fbk+0P1Z731sQhNMd+aBdToJoNUfH61F3ADb4prOVeeui529IxI52iYhq0ak8Did094NLZxLwsg/ YrSa2xYXYh9wcRGz3gwDXLXarPU8jybO6lWDprlsuxUaXonGgkOosACRJTE4RqiGcbVwPGxiE/nR Nb+tBQPCvZ5u8hFQtK1NfWF0Q1jSLqU5HAGVHFwF2TFyaO6IIPZDKtxknEy/NPEKHdSCbZOTgP73 ULre5qZ7KBFd7yGaXGtfp2EG15PB/zvPQUDs13lOv3TnWX1rnWf1X+g8q8/eeVbfaOdZffudZ9Wp 8/y1XG8qbr3elPharrdkcmvpKfCdc/6pZC3ln4pGnc1z1hHMF8xWpfaWtGyRG3LHiGaCUnnlw8PS tS4ujLGakyBHLwtMyo3zTit65kW/ssVg8CS2TLWUBUs9CkyEMkkjvww7pi6ErzzKjR7ORS0Hr/ph kHfxwn3D7LbzQRi76VJhC6bqeiuaPS+we8VXLj2tPm11y1Rs4pa58G5ZnZlZMOS+knKZkwuZLO3S Nz16Mq5uzV2hCdQmJNO8/rXdDSwm2dhrXGSzoAZns9eOk5q9uaaejQbuqydcQzeI20n8pex8mwBA Ck86AjE47rJWZxhH7iecLFutPxObWH8hvPXTBHr7QbiZ2sWVbd/c4HsReXvNE35kFTXujn6GLjdv S9ROVSZa9zy1U9X/OQ2VA7JveU+tTkCBM+PaH4nhqI5pe6Kr7zKtSdm8+XpaVnvfIe/sA//2DSCv 60fczCW2faXjaoGKgw89+roQKrX1w4W9KfrZb7yx17SxN2UWNQdhf9jsem8T5GMTRbP+fJZfnZvV vvG27qZc+6eTjORmKg+FNM66nmj2s9q81dvIj673Nvst+Jfytux2na1DuhUPC6o/hkmRRDInxkv3 d8gQRl0jDG1WUc6CPBPwoJJ8Y0wVxhhQjqnml9LJKalYpq+ZzbWuK5otvTTVskIQSUWLHlyA1InI CQD9fsoJgcyDhQsihAl+3wsJj6ngs3vGR8b0x2TwOqnD1NigMi4Dxk8pCgUzp2z4moXlIT1eYifW LzB3ZC5bTXWx5JdTTrQcIazmqXfEI4/GZU0VSntLmlp9TEpCvZs+HAWnlDkjoCYMwxlhx22l+6SZ +ybsBUqj77RpMCJNQeDFApIcewQxN6Mn1hJotaqeD/iB//DOYfU98ZIQEHcFvmjTK/+iaUxI6P+A pkuoScZZAgVg9XvuETpmOJJg5xkkvUsflR7NeAFszOTv9D7nk9J4FCgLIkWwomjdo693giRKGe0c 5r0A63gsaqSypIiyRG8o0yilK5feNlau2e0OkwlgVzF+JbFUOHLyAOkEs7ItqOfoeXgz+AdyfE0p CmVuZHN0cmVhbQplbmRvYmoKMSAwIG9iago8PCAKICAgL1R5cGUgL0NhdGFsb2cKICAgL1BhZ2Vz IDIgMCBSCiAgIC9QYWdlTGF5b3V0IC9PbmVDb2x1bW4KICAgL1BhZ2VNb2RlIC9Vc2VOb25lCj4+ CmVuZG9iagoyIDAgb2JqCjw8IAogICAvVHlwZSAvUGFnZXMKICAgL0tpZHMgWzMgMCBSIDE2IDAg UiAxOCAwIFIgMjAgMCBSIDIyIDAgUiAyNCAwIFIgMjYgMCBSIF0KICAgL0NvdW50IDcKPj4KZW5k b2JqCjI2IDAgb2JqCjw8IAogICAvVHlwZSAvUGFnZQogICAvUGFyZW50IDIgMCBSCiAgIC9SZXNv dXJjZXMgPDwgCiAgIC9Qcm9jU2V0IFsvUERGIC9UZXh0IF0KICAgL0ZvbnQgPDwgCiAgIC9GMiAx MCAwIFIKICAgL0YzIDEzIDAgUgo+Pgo+PgogICAvTWVkaWFCb3ggWzAgMCA2MTIgNzkyXQogICAv Q29udGVudHMgMjcgMCBSCj4+CmVuZG9iagoyNyAwIG9iago8PCAKICAgL0ZpbHRlciAvRmxhdGVE ZWNvZGUKICAgL0xlbmd0aCAyMjQ1Cj4+CnN0cmVhbQp4Xs1a23IbRRB911eoeAgaKlL2viuqKIid EEIRErCpPBAeFGFLJraUaJWA/57p09Pds7Ki4DVUkcTyzs5MT/fp67TybvBukFdD/68skmGdJcPN 2eDlF4PVIB3S382CpuuyGl4NypqfLvGU00Mefi8H54OfPKmj08GDb7NhmkySZnh6PkiG9NcTSfGQ Dstk0jTDOq8nmV9wNfh1NHTjPKXPerTF49o1PPzMjbPRzI+uXFGP3vqHM/+z8W8LPLUuy3kRlr8a YebSBRp/empTvzDPwp450Wpp5yvnfhuefj94fHorrrNyH9fh3As6d+XKKszROcTGQ+cnj2nyBT15 rtIqMISprUm+uXD16LXf897V0/AOgmLn0pUl4IDcZ0L6g6vT0cKPjv1mbGTigtOtBM2ybFJnHUkh EvPSE7YkVWIBq8qz20APjBXkI9EWQcktkKVlhVgDTYOX3/mN30bzJemXh4H4wjSuxnNFkNFo00+G qpmqDGOQ5iPf0lmzjlWuSE1QKhRGrzAi3c4hyRwmOoOe/YrWBJ6rkPhYE/WtWdrrgA6fjYPIwjYQ ccYH+QlY4gd6dybg0eFim/Wo3d4A1GT43QB9TGrBEtILuAbtdtkLw7r+OIaXjrnt2DfPz5fEwYxW QWS2kT4MVGbVCBsE3jlBwQflgtYzcPeUHo+c8kmrSQN/uOCWc8DYivGdCZ54/WJJrnjdAjDoFfg9 FdUx7LTnL3Lg+70EKnMVKD5dPArAXROaLaxPnIDA/pHYU/9QQ9njZUxZA1JEGYoCZZXvF1qID5b0 kUPcmGDwWS8hi/RQruhDMZv+F3bwpTHXjQMxYv+pOaT1v2gO9w2QXaO4hYDBHvxKwAhzuIsxJLdJ wVQyhErA51wUD5Jy/SxY39hGTrwsEzTrA067awLfurTkVRCPoDuWgkPLlBApxZtuJWeW5pOqI+dc wmG/1FU2e9Pv1B1IvwC19g+ZkyjwiqUGuu1MHMai9EyiuNZf85CROPusXYgi5kSRy60kVbKqenhf T3CqA3n9QE5iR4W6w0Ja1LG/OhSgnAeihPqXVbNaqERJ/mcRDBn8QkYKDHRh5Y1UGsG+RQYJkFo0 RtjPRMMr2RYTx/kw82OO3b1wLfcW+GQIXOlogLgMtmE+qkHmXBW+YRoSIs+ZloDNxY0Xb6H6ubs9 8eyYf6n26Qe1JN7wpDGiBd8mjo8Q0n9cgwvxorLjRX0gLm4TClsY2zwqENkhxVZTP8oVPoCEUIm8 8NDgOo62liOO9qKWzU4Jqif0dc7sRuSimJS420YumrQCl7R9KdpWY2vjjKkJrhrN7xB5k37BZRMM 1wcP3AiVoZuM5iFPGatMAjlD1bRVt4+dRtxkIZT1vo3Xigy70IWEdnzcN4ODABJY9OowNxsR4d65 kF/VOcBwrzqgmO6NL3c0fi5MUhGci7ObbkAxumbcF8BUblQ7UTk+qYzCTSfv1dORqRvEYdM7ZYuF 9RMrYPQg0ztmz+R9P7MtKnM76ikshUfjpO1VnxbFfn94GmPXh27UrWCdCTE1x2fzRx21a/qxa86r kCDeq9GiSIYStQCGCh6YwZ2IrjhXbc1fLN6o58J+QitqqT4YeXGw0J5qS/OO2oirMcL1UiTGeZEt xUo41Yz/xMzz1FV52IDOUivMRoGTUUOr4nXwBusU8PrrLlaX0qjamyuw9qUbN56RPjAke6x3FhgL dUTI6j84C4ihqEdtBg5QARFXlrC5T6ItmRuBxA+f01bpVJrFvDDN24FaGmPdwoy1v/B51KY6YZMy G9xKtOZX110TkHCHEtU+xlY0QX+nzoep5+YAH5MsWMlGJPK71nr0GwvQmnyesOMGxCsPYh/5oxZT Dx+AmJ8EwNvFc3MRAPCSXj4xVORa3+niblZSbkfV/h78qti+uiBFq9eiUVy12K2YKPAGP30QrHZj 6WOVGi7BBzyS+kkD5cJpaFUP6cSJ3buPGMPWsBxHaoCoL6zwvKfJ9wBkkck9Y+6PeoEQ9dWOAOt7 UR04+Fk83yJ/FAo5UmqHhdl5YFJ+R/PgnDBbWvBAkQEvkbubXtkACRd5hwWapGXVDPVXs0e4qJ+2 NOi2Erm+NH450bUSybnQaLlKWkD8nJtn3B7m+QkthEGiHxJoiJkomQf95UjrbFJWHUG0pldFbbr6 AS+YDB2qTxxf0Fl74Yuah/9j+PbwL7DtChCbYslBy0I1DgzLwi37E9B9xKWi3qR+GYOTL61OWDN+ 5CiHpUuqqvLi5f7PrpRNPkmKznH/2DbkPjv/hgIdEvIeVll/QUN9kIhae8j0B4IYokrpx3SjpY4d B8CZNY7eWEiULtT8zEoJzJ5ob86OokOiDm+IlkN7Q9+70Vd0KU73+yvXKNHe2smKzJtmDAFJRncv Oo9z7TSMCjqVX9GVPwkQFH1Az6YW0U8QoKFZbXZHBUGU1iXN16Mj+KpUh36e2gsZ4OliHcqY3Vs0 QYzSSyrRdgf8GPZpgD6PlX4X0Kt6UnUgmBLXBGilqMvB0EMWHvIbeCfDmvrJw8wHk7QiBhr9HwNg Kj+gC9pM3W3w8MTB9RoyWnjBGB4GUdNU67KUkl8mt5AZeebnfqm/gzIyKcVyKtVB6oouLGc0XpGu ts7fxGzhmgitghJTuvxFhMcUDmTP+CK44piqLF+8YmocaulxEzG+ou9ropkV25RnYbOgx2vsxPr1 ilu6nDCoJN7wAO8XRgireeo18Ri8oOmoIvcXvqIQfUwbQv12+lAKqpQlI5BPGYa3hN2NjNZRGt32 xgiLKWURv329hiSXhiDm5vTEWgKtvarnA77mL1kUq6+Il4yAuOfQivIr39A0JlLo/5ymG6gpTcoM CsDqD5w7lRm+nmPnW0h6jz5a/7bkBbCxcE2n8ZJPKpJRpCyINIEVTW565mEnoBDIsQ/mvT7nMtE/ 1h1SZVZPysxvaIpJ4XWb0ugfKzfs1sPSDLDnCX5lSZrjyCkSrq8LaPDQURFrPPw0+BsZ8aAbCmVu ZHN0cmVhbQplbmRvYmoKNSAwIG9iago8PCAKICAgL1Byb2R1Y2VyIDxGRUZGMDA2NDAwNkYwMDUw MDA0NDAwNDYwMDIwMDA1NjAwNjUwMDcyMDAyMDAwMzcwMDJFMDAzMzAwMjAwMDQyMDA3NTAwNjkw MDZDMDA2NDAwMjAwMDMzMDAzOTAwMzQwMDIwMDAyODAwNTcwMDY5MDA2RTAwNjQwMDZGMDA3NzAw NzMwMDIwMDAzNzAwMjAwMDQyMDA3NTAwNzMwMDY5MDA2RTAwNjUwMDczMDA3MzAwMjAwMDQ1MDA2 NDAwNjkwMDc0MDA2OTAwNkYwMDZFMDAyMDAwMjgwMDUzMDA1MDAwMjAwMDMxMDAyOTAwMjAwMDJE MDAyMDAwNTYwMDY1MDA3MjAwNzMwMDY5MDA2RjAwNkUwMDNBMDAyMDAwMzYwMDJFMDAzMTAwMkUw MDM3MDAzNjAwMzAwMDMxMDAyMDAwMjgwMDc4MDAzNjAwMzQwMDI5MDAyOT4KICAgL0NyZWF0aW9u RGF0ZSAoRDoyMDEzMTIzMDA5NTcwNC0wNScwMCcpCj4+CmVuZG9iago3IDAgb2JqCjw8IAogICAv VHlwZSAvRm9udAogICAvU3VidHlwZSAvVHJ1ZVR5cGUKICAgL0ZvbnREZXNjcmlwdG9yIDggMCBS CiAgIC9CYXNlRm9udCAvQXJpYWwtQm9sZE1UCiAgIC9GaXJzdENoYXIgMAogICAvTGFzdENoYXIg MjU1CiAgIC9XaWR0aHMgOSAwIFIKICAgL0VuY29kaW5nIC9XaW5BbnNpRW5jb2RpbmcKPj4KZW5k b2JqCjggMCBvYmoKPDwgCiAgIC9UeXBlIC9Gb250RGVzY3JpcHRvcgogICAvRm9udE5hbWUgL0Fy aWFsLUJvbGRNVAogICAvQXNjZW50IDcyOAogICAvQ2FwSGVpZ2h0IDcxNgogICAvRGVzY2VudCAt MjEwCiAgIC9GbGFncyAyNjIxNzYKICAgL0ZvbnRCQm94IFstNjI4IC0zNzYgMjAwMCAxMDE4XQog ICAvSXRhbGljQW5nbGUgMAogICAvU3RlbVYgMTY1CiAgIC9YSGVpZ2h0IDUxOQo+PgplbmRvYmoK OSAwIG9iagpbNzUwIDc1MCA3NTAgNzUwIDc1MCA3NTAgNzUwIDc1MCA3NTAgNzUwIDc1MCA3NTAg NzUwIDc1MCA3NTAgNzUwIDc1MCA3NTAgNzUwIDc1MCA3NTAgNzUwIDc1MCA3NTAgNzUwIDc1MCA3 NTAgNzUwIDc1MCA3NTAgNzUwIDc1MCAyNzggMzMzIDQ3NCA1NTYgNTU2IDg4OSA3MjIgMjM4IDMz MyAzMzMgMzg5IDU4NCAyNzggMzMzIDI3OCAyNzggNTU2IDU1NiA1NTYgNTU2IDU1NiA1NTYgNTU2 IDU1NiA1NTYgNTU2IDMzMyAzMzMgNTg0IDU4NCA1ODQgNjExIDk3NSA3MjIgNzIyIDcyMiA3MjIg NjY3IDYxMSA3NzggNzIyIDI3OCA1NTYgNzIyIDYxMSA4MzMgNzIyIDc3OCA2NjcgNzc4IDcyMiA2 NjcgNjExIDcyMiA2NjcgOTQ0IDY2NyA2NjcgNjExIDMzMyAyNzggMzMzIDU4NCA1NTYgMzMzIDU1 NiA2MTEgNTU2IDYxMSA1NTYgMzMzIDYxMSA2MTEgMjc4IDI3OCA1NTYgMjc4IDg4OSA2MTEgNjEx IDYxMSA2MTEgMzg5IDU1NiAzMzMgNjExIDU1NiA3NzggNTU2IDU1NiA1MDAgMzg5IDI4MCAzODkg NTg0IDM1MCA1NTYgMzUwIDI3OCA1NTYgNTAwIDEwMDAgNTU2IDU1NiAzMzMgMTAwMCA2NjcgMzMz IDEwMDAgMzUwIDYxMSAzNTAgMzUwIDI3OCAyNzggNTAwIDUwMCAzNTAgNTU2IDEwMDAgMzMzIDEw MDAgNTU2IDMzMyA5NDQgMzUwIDUwMCA2NjcgMjc4IDMzMyA1NTYgNTU2IDU1NiA1NTYgMjgwIDU1 NiAzMzMgNzM3IDM3MCA1NTYgNTg0IDMzMyA3MzcgNTUyIDQwMCA1NDkgMzMzIDMzMyAzMzMgNTc2 IDU1NiAzMzMgMzMzIDMzMyAzNjUgNTU2IDgzNCA4MzQgODM0IDYxMSA3MjIgNzIyIDcyMiA3MjIg NzIyIDcyMiAxMDAwIDcyMiA2NjcgNjY3IDY2NyA2NjcgMjc4IDI3OCAyNzggMjc4IDcyMiA3MjIg Nzc4IDc3OCA3NzggNzc4IDc3OCA1ODQgNzc4IDcyMiA3MjIgNzIyIDcyMiA2NjcgNjY3IDYxMSA1 NTYgNTU2IDU1NiA1NTYgNTU2IDU1NiA4ODkgNTU2IDU1NiA1NTYgNTU2IDU1NiAyNzggMjc4IDI3 OCAyNzggNjExIDYxMSA2MTEgNjExIDYxMSA2MTEgNjExIDU0OSA2MTEgNjExIDYxMSA2MTEgNjEx IDU1NiA2MTEgNTU2IF0KZW5kb2JqCjEwIDAgb2JqCjw8IAogICAvVHlwZSAvRm9udAogICAvU3Vi dHlwZSAvVHJ1ZVR5cGUKICAgL0ZvbnREZXNjcmlwdG9yIDExIDAgUgogICAvQmFzZUZvbnQgL0Fy aWFsTVQKICAgL0ZpcnN0Q2hhciAwCiAgIC9MYXN0Q2hhciAyNTUKICAgL1dpZHRocyAxMiAwIFIK ICAgL0VuY29kaW5nIC9XaW5BbnNpRW5jb2RpbmcKPj4KZW5kb2JqCjExIDAgb2JqCjw8IAogICAv VHlwZSAvRm9udERlc2NyaXB0b3IKICAgL0ZvbnROYW1lIC9BcmlhbE1UCiAgIC9Bc2NlbnQgNzI4 CiAgIC9DYXBIZWlnaHQgNzE2CiAgIC9EZXNjZW50IC0yMTAKICAgL0ZsYWdzIDMyCiAgIC9Gb250 QkJveCBbLTY2NSAtMzI1IDIwMDAgMTAwNl0KICAgL0l0YWxpY0FuZ2xlIDAKICAgL1N0ZW1WIDg3 CiAgIC9YSGVpZ2h0IDUxOQo+PgplbmRvYmoKMTIgMCBvYmoKWzc1MCA3NTAgNzUwIDc1MCA3NTAg NzUwIDc1MCA3NTAgNzUwIDc1MCA3NTAgNzUwIDc1MCA3NTAgNzUwIDc1MCA3NTAgNzUwIDc1MCA3 NTAgNzUwIDc1MCA3NTAgNzUwIDc1MCA3NTAgNzUwIDc1MCA3NTAgNzUwIDc1MCA3NTAgMjc4IDI3 OCAzNTUgNTU2IDU1NiA4ODkgNjY3IDE5MSAzMzMgMzMzIDM4OSA1ODQgMjc4IDMzMyAyNzggMjc4 IDU1NiA1NTYgNTU2IDU1NiA1NTYgNTU2IDU1NiA1NTYgNTU2IDU1NiAyNzggMjc4IDU4NCA1ODQg NTg0IDU1NiAxMDE1IDY2NyA2NjcgNzIyIDcyMiA2NjcgNjExIDc3OCA3MjIgMjc4IDUwMCA2Njcg NTU2IDgzMyA3MjIgNzc4IDY2NyA3NzggNzIyIDY2NyA2MTEgNzIyIDY2NyA5NDQgNjY3IDY2NyA2 MTEgMjc4IDI3OCAyNzggNDY5IDU1NiAzMzMgNTU2IDU1NiA1MDAgNTU2IDU1NiAyNzggNTU2IDU1 NiAyMjIgMjIyIDUwMCAyMjIgODMzIDU1NiA1NTYgNTU2IDU1NiAzMzMgNTAwIDI3OCA1NTYgNTAw IDcyMiA1MDAgNTAwIDUwMCAzMzQgMjYwIDMzNCA1ODQgMzUwIDU1NiAzNTAgMjIyIDU1NiAzMzMg MTAwMCA1NTYgNTU2IDMzMyAxMDAwIDY2NyAzMzMgMTAwMCAzNTAgNjExIDM1MCAzNTAgMjIyIDIy MiAzMzMgMzMzIDM1MCA1NTYgMTAwMCAzMzMgMTAwMCA1MDAgMzMzIDk0NCAzNTAgNTAwIDY2NyAy NzggMzMzIDU1NiA1NTYgNTU2IDU1NiAyNjAgNTU2IDMzMyA3MzcgMzcwIDU1NiA1ODQgMzMzIDcz NyA1NTIgNDAwIDU0OSAzMzMgMzMzIDMzMyA1NzYgNTM3IDMzMyAzMzMgMzMzIDM2NSA1NTYgODM0 IDgzNCA4MzQgNjExIDY2NyA2NjcgNjY3IDY2NyA2NjcgNjY3IDEwMDAgNzIyIDY2NyA2NjcgNjY3 IDY2NyAyNzggMjc4IDI3OCAyNzggNzIyIDcyMiA3NzggNzc4IDc3OCA3NzggNzc4IDU4NCA3Nzgg NzIyIDcyMiA3MjIgNzIyIDY2NyA2NjcgNjExIDU1NiA1NTYgNTU2IDU1NiA1NTYgNTU2IDg4OSA1 MDAgNTU2IDU1NiA1NTYgNTU2IDI3OCAyNzggMjc4IDI3OCA1NTYgNTU2IDU1NiA1NTYgNTU2IDU1 NiA1NTYgNTQ5IDYxMSA1NTYgNTU2IDU1NiA1NTYgNTAwIDU1NiA1MDAgXQplbmRvYmoKMTMgMCBv YmoKPDwgCiAgIC9UeXBlIC9Gb250CiAgIC9TdWJ0eXBlIC9UcnVlVHlwZQogICAvRm9udERlc2Ny aXB0b3IgMTQgMCBSCiAgIC9CYXNlRm9udCAvVGltZXNOZXdSb21hblBTTVQKICAgL0ZpcnN0Q2hh ciAwCiAgIC9MYXN0Q2hhciAyNTUKICAgL1dpZHRocyAxNSAwIFIKICAgL0VuY29kaW5nIC9XaW5B bnNpRW5jb2RpbmcKPj4KZW5kb2JqCjE0IDAgb2JqCjw8IAogICAvVHlwZSAvRm9udERlc2NyaXB0 b3IKICAgL0ZvbnROYW1lIC9UaW1lc05ld1JvbWFuUFNNVAogICAvQXNjZW50IDY5MwogICAvQ2Fw SGVpZ2h0IDY2MgogICAvRGVzY2VudCAtMjE2CiAgIC9GbGFncyAzMgogICAvRm9udEJCb3ggWy01 NjggLTMwNyAyMDAwIDEwMDddCiAgIC9JdGFsaWNBbmdsZSAwCiAgIC9TdGVtViA4NwogICAvWEhl aWdodCA0NDcKPj4KZW5kb2JqCjE1IDAgb2JqCls3NzggNzc4IDc3OCA3NzggNzc4IDc3OCA3Nzgg Nzc4IDc3OCA3NzggNzc4IDc3OCA3NzggNzc4IDc3OCA3NzggNzc4IDc3OCA3NzggNzc4IDc3OCA3 NzggNzc4IDc3OCA3NzggNzc4IDc3OCA3NzggNzc4IDc3OCA3NzggNzc4IDI1MCAzMzMgNDA4IDUw MCA1MDAgODMzIDc3OCAxODAgMzMzIDMzMyA1MDAgNTY0IDI1MCAzMzMgMjUwIDI3OCA1MDAgNTAw IDUwMCA1MDAgNTAwIDUwMCA1MDAgNTAwIDUwMCA1MDAgMjc4IDI3OCA1NjQgNTY0IDU2NCA0NDQg OTIxIDcyMiA2NjcgNjY3IDcyMiA2MTEgNTU2IDcyMiA3MjIgMzMzIDM4OSA3MjIgNjExIDg4OSA3 MjIgNzIyIDU1NiA3MjIgNjY3IDU1NiA2MTEgNzIyIDcyMiA5NDQgNzIyIDcyMiA2MTEgMzMzIDI3 OCAzMzMgNDY5IDUwMCAzMzMgNDQ0IDUwMCA0NDQgNTAwIDQ0NCAzMzMgNTAwIDUwMCAyNzggMjc4 IDUwMCAyNzggNzc4IDUwMCA1MDAgNTAwIDUwMCAzMzMgMzg5IDI3OCA1MDAgNTAwIDcyMiA1MDAg NTAwIDQ0NCA0ODAgMjAwIDQ4MCA1NDEgMzUwIDUwMCAzNTAgMzMzIDUwMCA0NDQgMTAwMCA1MDAg NTAwIDMzMyAxMDAwIDU1NiAzMzMgODg5IDM1MCA2MTEgMzUwIDM1MCAzMzMgMzMzIDQ0NCA0NDQg MzUwIDUwMCAxMDAwIDMzMyA5ODAgMzg5IDMzMyA3MjIgMzUwIDQ0NCA3MjIgMjUwIDMzMyA1MDAg NTAwIDUwMCA1MDAgMjAwIDUwMCAzMzMgNzYwIDI3NiA1MDAgNTY0IDMzMyA3NjAgNTAwIDQwMCA1 NDkgMzAwIDMwMCAzMzMgNTc2IDQ1MyAzMzMgMzMzIDMwMCAzMTAgNTAwIDc1MCA3NTAgNzUwIDQ0 NCA3MjIgNzIyIDcyMiA3MjIgNzIyIDcyMiA4ODkgNjY3IDYxMSA2MTEgNjExIDYxMSAzMzMgMzMz IDMzMyAzMzMgNzIyIDcyMiA3MjIgNzIyIDcyMiA3MjIgNzIyIDU2NCA3MjIgNzIyIDcyMiA3MjIg NzIyIDcyMiA1NTYgNTAwIDQ0NCA0NDQgNDQ0IDQ0NCA0NDQgNDQ0IDY2NyA0NDQgNDQ0IDQ0NCA0 NDQgNDQ0IDI3OCAyNzggMjc4IDI3OCA1MDAgNTAwIDUwMCA1MDAgNTAwIDUwMCA1MDAgNTQ5IDUw MCA1MDAgNTAwIDUwMCA1MDAgNTAwIDUwMCA1MDAgXQplbmRvYmoKeHJlZgowIDI4IAowMDAwMDAw MDAwIDY1NTM1IGYgCjAwMDAwMjAwMjUgMDAwMDAgbiAKMDAwMDAyMDEyOSAwMDAwMCBuIAowMDAw MDAzODE1IDAwMDAwIG4gCjAwMDAwMDQwNTMgMDAwMDAgbiAKMDAwMDAyMjc1OCAwMDAwMCBuIAow MDAwMDAwMDE1IDAwMDAwIG4gCjAwMDAwMjMxODMgMDAwMDAgbiAKMDAwMDAyMzM3NCAwMDAwMCBu IAowMDAwMDIzNTk4IDAwMDAwIG4gCjAwMDAwMjQ2NDYgMDAwMDAgbiAKMDAwMDAyNDgzNSAwMDAw MCBuIAowMDAwMDI1MDUwIDAwMDAwIG4gCjAwMDAwMjYxMDAgMDAwMDAgbiAKMDAwMDAyNjI5OSAw MDAwMCBuIAowMDAwMDI2NTI0IDAwMDAwIG4gCjAwMDAwMDcyMTggMDAwMDAgbiAKMDAwMDAwNzQx MSAwMDAwMCBuIAowMDAwMDA5ODIzIDAwMDAwIG4gCjAwMDAwMTAwMTYgMDAwMDAgbiAKMDAwMDAx MjExNyAwMDAwMCBuIAowMDAwMDEyMzEwIDAwMDAwIG4gCjAwMDAwMTQ4MDcgMDAwMDAgbiAKMDAw MDAxNTAwMCAwMDAwMCBuIAowMDAwMDE3NTAwIDAwMDAwIG4gCjAwMDAwMTc2OTMgMDAwMDAgbiAK MDAwMDAyMDIzOSAwMDAwMCBuIAowMDAwMDIwNDMyIDAwMDAwIG4gCnRyYWlsZXIKPDwgCiAgIC9S b290IDEgMCBSCiAgIC9JbmZvIDUgMCBSCiAgIC9TaXplIDI4Cj4+CnN0YXJ0eHJlZgoyNzU3MAol JUVPRgo= --14dae93a1007d9763804eec1ae25-- From blueroofmusic@gmail.com Mon Dec 30 07:02:26 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB0EA1AE1B3 for ; Mon, 30 Dec 2013 07:02:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 Bm6Wk0JdLD9Z for ; Mon, 30 Dec 2013 07:02:24 -0800 (PST) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id C5D0A1AE18B for ; Mon, 30 Dec 2013 07:02:24 -0800 (PST) Received: by mail-ie0-f173.google.com with SMTP id to1so12010221ieb.4 for ; Mon, 30 Dec 2013 07:02:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7mc/Z+hhkcYVRMvn/4Z/y2nUfFX3apsc9o1TbVd3IR4=; b=eMfjoA1yLkywPZ9Bp99mcSsdDAJ9i0mlAfOEhU/3U7/kGGk58/fmw34EyvhDklE3EU litmJJ5zQ43dTLm4J6qbi4tOVF/qzMQAi49oH2JKiQQ+nKQUHgqX98Cm2ajyoBiW7eRR AVMMN6D6FyVS6QKQLJIgnxQ//Cey4GvUhssuSfxkxjbRHGk9c/OXlvXidLHj8aQXUJOf ZckSq3zHGZbCEoScvIzxGZTC0WxgbJ3zjwELZSQDinjDtvRemZ/idUWUaPev7QzD1A+U OgZfciPCS6BPXy/yTOQ2BdW8bh8wYVzaP4mjeWS20v4q6LlLV6J/7bG2qJRBKwcwabcL h9kg== X-Received: by 10.50.25.129 with SMTP id c1mr56148971igg.23.1388415738843; Mon, 30 Dec 2013 07:02:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.203.38 with HTTP; Mon, 30 Dec 2013 07:01:58 -0800 (PST) In-Reply-To: References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> <5339BC8D-660B-4659-96DC-C0170E124134@lucidvision.com> From: Ira McDonald Date: Mon, 30 Dec 2013 10:01:58 -0500 Message-ID: To: Thomas Nadeau , Ira McDonald Content-Type: multipart/alternative; boundary=047d7bdc10ecea38ce04eec1bae0 Cc: eman mailing list Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Dec 2013 15:02:27 -0000 --047d7bdc10ecea38ce04eec1bae0 Content-Type: text/plain; charset=ISO-8859-1 Hi Thomas, This is the link in the EMAN mailing list archive to those comments that I sent three days ago on the Energy Monitoring MIB. http://www.ietf.org/mail-archive/web/eman/current/msg02118.html Cheers, - Ira Ira McDonald (Musician / Software Architect) Co-Chair - TCG Trusted Mobility Solutions WG Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG IETF Designated Expert - IPP & Printer MIB Blue Roof Music / High North Inc http://sites.google.com/site/blueroofmusic 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, Dec 30, 2013 at 9:58 AM, Ira McDonald wrote: > Hi Thomas, > > Ahem - I did send the attached extensive comments on the Energy Monitoring > MIB > three days ago to the EMAN mailing list. > > Cheers, > - Ira > > > Ira McDonald (Musician / Software Architect) > Co-Chair - TCG Trusted Mobility Solutions WG > Chair - Linux Foundation Open Printing WG > Secretary - IEEE-ISTO Printer Working Group > Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG > IETF Designated Expert - IPP & Printer MIB > Blue Roof Music / High North Inc > http://sites.google.com/site/blueroofmusic > 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, Dec 30, 2013 at 8:43 AM, Thomas Nadeau wrote: > >> >> WG, >> >> This concludes the WG LC on the MIBs. We have received just one >> set of comments from the WG and one set of comments regarding the OID >> numbering. Would the document editors please address these and republish >> the drafts ASAP so that we can proceed with progressing the drafts? >> >> Cheers and Happy Holidays, >> >> Tom >> >> >> > >> > As agreed at the last WG meeting, with the EMAN Framework >> completing its WG LC the chairs would like to initiate a WG LC on >> draft-ietf-eman-energy-monitoring-mib-08 and >> draft-ietf-eman-energy-aware-mib-13. The WG LC will end on Dec 30 at 8AM >> EDT. >> > >> > Thank you, >> > >> > Nevil and Tom >> > >> > >> > _______________________________________________ >> > eman mailing list >> > eman@ietf.org >> > https://www.ietf.org/mailman/listinfo/eman >> >> >> _______________________________________________ >> eman mailing list >> eman@ietf.org >> https://www.ietf.org/mailman/listinfo/eman >> >> > --047d7bdc10ecea38ce04eec1bae0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Thomas,

This is the li= nk in the EMAN mailing list archive to those comments
that I sent = three days ago on the Energy Monitoring MIB.

http://www.ietf.org/ma= il-archive/web/eman/current/msg02118.html

Cheers,
- Ira

Ira McDonald (Musician / Software Arc= hitect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Fo= undation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Int= ernet Printing Protocol WG
IETF Designated Expert - IPP & Printer MI= B
Blue Roof Music / High North Inc
http:= //sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthincmailto: blue= roofmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0 734-944-0094
Summer= =A0 PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-2434



On Mon, Dec 30, 2013 at 9:58 AM, Ira McD= onald <blueroofmusic@gmail.com> wrote:
Hi Thomas,

Ahem - I did send t= he attached extensive comments on the Energy Monitoring MIB
three days a= go to the EMAN mailing list.

Cheers,
- Ira


Ira McDo= nald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Sol= utions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-= ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated E= xpert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthincmailto: blue= roofmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0 734-944-0094
Summer=A0= PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-2434



On Mon, Dec 30, 2013 at 8:43 AM, Thomas = Nadeau <tnadeau@lucidvision.com> wrote:

=A0 =A0 =A0 =A0 WG,

=A0 =A0 =A0 =A0 This concludes the WG LC on the MIBs. We have received just= one set of comments from the WG and one set of comments regarding the OID = numbering. Would the document editors please address these and republish th= e drafts ASAP so that we can proceed with progressing the drafts?

=A0 =A0 =A0 =A0 Cheers and Happy Holidays,

=A0 =A0 =A0 =A0 Tom


>
> =A0 =A0 =A0 As agreed at the last WG meeting, with the EMAN Framework = completing its WG LC the chairs would like to initiate a WG LC on draft-iet= f-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13. = =A0The WG LC will end on Dec 30 at 8AM EDT.
>
> =A0 =A0 =A0 Thank you,
>
> =A0 =A0 =A0 Nevil and Tom
>
>
> _______________________________________________
> eman mailing list
> eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman


_______________________________________________
eman mailing list
eman@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/eman



--047d7bdc10ecea38ce04eec1bae0-- From tnadeau@lucidvision.com Mon Dec 30 09:22:27 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E15D81AE195 for ; Mon, 30 Dec 2013 09:22:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.437 X-Spam-Level: X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538] 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 rB4hVXeisJFB for ; Mon, 30 Dec 2013 09:22:25 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 555CC1AE227 for ; Mon, 30 Dec 2013 09:22:25 -0800 (PST) Received: from [10.78.188.188] (mobile-198-228-204-195.mycingular.net [198.228.204.195]) by lucidvision.com (Postfix) with ESMTP id 9D107269C30B; Mon, 30 Dec 2013 12:22:18 -0500 (EST) References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> <5339BC8D-660B-4659-96DC-C0170E124134@lucidvision.com> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: multipart/alternative; boundary=Apple-Mail-76F66941-603C-4815-9ABA-1D9FCD559B0D Content-Transfer-Encoding: 7bit Message-Id: <19FBC5F9-3600-400C-B996-992FD3BE9715@lucidvision.com> X-Mailer: iPhone Mail (11B554a) From: "Thomas D. Nadeau" Date: Mon, 30 Dec 2013 12:22:16 -0500 To: Ira McDonald Cc: eman mailing list Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Dec 2013 17:22:28 -0000 --Apple-Mail-76F66941-603C-4815-9ABA-1D9FCD559B0D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable ok cool. I must have missed the email over the holiday. thanks Tom > On Dec 30, 2013, at 9:58 AM, Ira McDonald wrote:= >=20 > Hi Thomas, >=20 > Ahem - I did send the attached extensive comments on the Energy Monitoring= MIB > three days ago to the EMAN mailing list. >=20 > Cheers, > - Ira >=20 >=20 > Ira McDonald (Musician / Software Architect) > Co-Chair - TCG Trusted Mobility Solutions WG > Chair - Linux Foundation Open Printing WG > Secretary - IEEE-ISTO Printer Working Group > Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG > IETF Designated Expert - IPP & Printer MIB > Blue Roof Music / High North Inc > http://sites.google.com/site/blueroofmusic > 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 >=20 >=20 >=20 >> On Mon, Dec 30, 2013 at 8:43 AM, Thomas Nadeau w= rote: >>=20 >> WG, >>=20 >> This concludes the WG LC on the MIBs. We have received just one s= et of comments from the WG and one set of comments regarding the OID numberi= ng. Would the document editors please address these and republish the drafts= ASAP so that we can proceed with progressing the drafts? >>=20 >> Cheers and Happy Holidays, >>=20 >> Tom >>=20 >>=20 >> > >> > As agreed at the last WG meeting, with the EMAN Framework complet= ing its WG LC the chairs would like to initiate a WG LC on draft-ietf-eman-e= nergy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13. The WG LC w= ill end on Dec 30 at 8AM EDT. >> > >> > Thank you, >> > >> > Nevil and Tom >> > >> > >> > _______________________________________________ >> > eman mailing list >> > eman@ietf.org >> > https://www.ietf.org/mailman/listinfo/eman >>=20 >>=20 >> _______________________________________________ >> eman mailing list >> eman@ietf.org >> https://www.ietf.org/mailman/listinfo/eman >=20 > --Apple-Mail-76F66941-603C-4815-9ABA-1D9FCD559B0D Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
ok cool. I must have missed the email over the holiday.

thanks

Tom

On Dec 30, 2013, at 9:58 AM, Ira McDonald <blueroofmusic@gmail.com> wrote:

Hi Thomas,

Ahem - I did send the attached extensive comments on the Energy Monitoring MIB
three days ago to the EMAN mailing list.

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
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, Dec 30, 2013 at 8:43 AM, Thomas Nadeau <tnadeau@lucidvision.com> wrote:

        WG,

        This concludes the WG LC on the MIBs. We have received just one set of comments from the WG and one set of comments regarding the OID numbering. Would the document editors please address these and republish the drafts ASAP so that we can proceed with progressing the drafts?

        Cheers and Happy Holidays,

        Tom


>
>       As agreed at the last WG meeting, with the EMAN Framework completing its WG LC the chairs would like to initiate a WG LC on draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13.  The WG LC will end on Dec 30 at 8AM EDT.
>
>       Thank you,
>
>       Nevil and Tom
>
>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman


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


<ira-comments-on-draft-ietf-eman-energy-monitoring-mib-08.pdf>
--Apple-Mail-76F66941-603C-4815-9ABA-1D9FCD559B0D-- From Quittek@neclab.eu Mon Dec 30 10:46:44 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA9A11AE547 for ; Mon, 30 Dec 2013 10:46:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.14 X-Spam-Level: X-Spam-Status: No, score=-3.14 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 U83VmHZE_ScA for ; Mon, 30 Dec 2013 10:46:42 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 755A81AE545 for ; Mon, 30 Dec 2013 10:46:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 9043F1066FB; Mon, 30 Dec 2013 19:36:14 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8D7WbZfUuTXe; Mon, 30 Dec 2013 19:36:14 +0100 (CET) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 72C7F1066F1; Mon, 30 Dec 2013 19:36:04 +0100 (CET) Received: from DAPHNIS.office.hd ([169.254.2.18]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Mon, 30 Dec 2013 19:46:06 +0100 From: Juergen Quittek To: Thomas Nadeau , eman mailing list Thread-Topic: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 Thread-Index: AQHPBWW+e+FcyZl6xU2iDkmSboVCg5ptEzlg Date: Mon, 30 Dec 2013 18:46:05 +0000 Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E8688B32A5@DAPHNIS.office.hd> References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> <5339BC8D-660B-4659-96DC-C0170E124134@lucidvision.com> In-Reply-To: <5339BC8D-660B-4659-96DC-C0170E124134@lucidvision.com> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.0.197] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Dec 2013 18:46:45 -0000 Hi Tom, I missed the fact that the deadline is already in the morning of today. I t= hought I had the full day today for sending them. There are still some comm= ents that I planned to send this evening. I will send them asap and hope th= ey will be OK even if a few hours late. Thanks, Juergen > -----Original Message----- > From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau > Sent: Montag, 30. Dezember 2013 14:44 > To: eman mailing list > Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mi= b- > 08 and draft-ietf-eman-energy-aware-mib-13 >=20 >=20 > WG, >=20 > This concludes the WG LC on the MIBs. We have received just one set > of comments from the WG and one set of comments regarding the OID > numbering. Would the document editors please address these and republish > the drafts ASAP so that we can proceed with progressing the drafts? >=20 > Cheers and Happy Holidays, >=20 > Tom >=20 >=20 > > > > As agreed at the last WG meeting, with the EMAN Framework > completing its WG LC the chairs would like to initiate a WG LC on draft-i= etf- > eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13. > The WG LC will end on Dec 30 at 8AM EDT. > > > > Thank you, > > > > Nevil and Tom > > > > > > _______________________________________________ > > eman mailing list > > eman@ietf.org > > https://www.ietf.org/mailman/listinfo/eman From luchuk@snmp.com Mon Dec 30 10:54:07 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA3CA1AE293 for ; Mon, 30 Dec 2013 10:54:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.26 X-Spam-Level: X-Spam-Status: No, score=0.26 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 gBe4_-6RGt0K for ; Mon, 30 Dec 2013 10:54:05 -0800 (PST) Received: from mailbox.snmp.com (mailbox.snmp.com [192.147.142.80]) by ietfa.amsl.com (Postfix) with ESMTP id 88BBF1AE2D7 for ; Mon, 30 Dec 2013 10:54:04 -0800 (PST) Received: from adminfs.snmp.com (adminfs.snmp.com [192.147.142.39]) by mailbox.snmp.com (8.9.3p2-20030922/m.0080228) with ESMTP id NAA11789; Mon, 30 Dec 2013 13:53:15 -0500 (EST) Received: (from luchuk@localhost) by adminfs.snmp.com (8.9.3p2-20030922/snmpclient.mc-990525) id NAA03279; Mon, 30 Dec 2013 13:53:14 -0500 (EST) Date: Mon, 30 Dec 2013 13:53:14 -0500 (EST) From: Alan Luchuk Message-Id: <201312301853.NAA03279@adminfs.snmp.com> To: eman@ietf.org Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Dec 2013 18:54:08 -0000 Hello, Here are comments about draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13. Due to the holidays, I was unable to get these sent to the WG E-mail list sooner. Regarding draft-ietf-eman-energy-aware-mib-13: ---------------------------------------------- Section 5, Page 6: The UML on Page 6 _looks_ incorrect. It _looks_ like the eoRelationTable is subordinate to, or a child of, the eoEntry. I'm not sure how the actual relationship specified in the MIB is _supposed_ to be represented in UML. Page 22: The eoRelationID in the eoRelationTable is "read-only". In many cases, I do not see how an energy object can determine the eoRelationID to the Energy Objects to which it is connected, so I _think_ the eoRelationID must be configured by the EnMS. I _think_ the eoRelationID should be a read-write object like the eoRelationship object. As an example, consider a manageable, metering power distribution unit (PDU), I don't see how it can autodiscover and populate the eoRelationID of the energy objects to which it is connected. The useful- ness of the eoRelationID MIB object is reduced if it is only populated in devices where it can be autodiscovered. Regarding draft-ietf-eman-energy-monitoring-mib-08: --------------------------------------------------- Section 5, 3rd paragraph, Page 6: "entity4CRCompliance. This compliance requires that the following 3 MIB objects from ENTITY-MIB [RFC6933] (entPhysicalIndex, entPhysicalName and entPhysicalUUID) MUST be implemented." I think entPhysicalClass should be included in this list. There are other references to the entity4CRCompliance in this draft that need the same update. Section 5, Page 7: | +-- r-n INTEGER eoMeasurementCaliber(5) I think the above should be eoPowerMeasurementCaliber(5). | +-- r-n Interger32 eoPowerStateMaxPower(2) Change "Interger32" to Integer. | +-- r-n Integer32 eoEnergyParametersIntervalMode(5) I think the type of "eoEnergyParametersIntervalMode" should be INTEGER. Section 5, Page 8: I suggest changing "powerAttributesMIB" to "POWER-ATTRIBUTES-MIB" for for consistency with previous text that references the ENERGY-OBJECT-MIB and POWER-ATTRIBUTES-MIB. A quick summary of the function of each of the tables in the POWER- ATTRIBUTES-MIB, similar to the quick summary of each of the tables in the ENERGY-OBJECT-MIB (on Page 6) might be helpful and consisent. | +-- r-n Interger32 eoACPwrAttributesAvgVoltage(2) | +-- r-n Interger32 | eoACPwrAttributesTotalActivePower(7) Change "Interger32" to Integer. In the diagram for the eoACPwrAttributesEntry, after eoACPwrAttributes- ThdAmpheres, the eoACPwrAttributesThdVoltage object is missing. Also, here, and several places in the document, "Ampheres" is referenced. Not sure if "Ampheres" is intentional, but "Amperes" might be preferable. It might be good to do a case-insensitive search for "ampheres". Section 5, Page 9: +-- eoACPwrAttributesDelPhaseEntry(1) | | [entPhysicalIndex, eoPhaseIndex] | | | +-- r-n Integer32 | | eoACPwrAttributesDelPhaseToNextPhaseVoltage(1) | +-- r-n Integer32 | | eoACPwrAttributesDelThdPhaseToNextPhaseVoltage(2) | +-- r-n Integer32 eoACPwrAttributesDelThdCurrent(3) I think the column numbers 1, 2, and 3, are incorrect. The actual column numbers in the MIB are 2, 3, and 4. Perhaps the MIB table should be fixed so the column numbers are 1, 2, and 3. Section 5, Page 12. At the very top, in the diagram for the eoACPwrAttributesEntry, after eoACPwrAttributesThdAmpheres, the eoACPwrAttributesThdVoltage object is missing. Section 5.4, Page 15: I suggest changing "powerAttributesMIB" to "POWER-ATTRIBUTES-MIB" for for consistency with previous text that references the ENERGY-OBJECT-MIB and POWER-ATTRIBUTES-MIB. Section 6, Page 20: This section references the EMAN-MON-MIB. I think this should be ENERGY-OBJECT-MIB. Section 9, Page 27: This section references the "energyObjectMIBObject". Not sure what this is. In the MIBs, adding eye-catching comments between the tables would ease visually identifying where each MIB table begins. Page 37, "eoPowerOperState" MIB object: The second paragraph of the DESCRIPTION clause reads: "Possible values of eoPowerAdminState...". I think "eoPowerAdminState" should be changed to "eoPowerOperState." Page 38, "eoPowerStateTable": The text reads: This table has an expansion-dependent relationship on the eoPowerTable, containing rows describing each Power State for the corresponding Energy Object. For every Energy Object in the eoPowerTable, there is a corresponding entry in this table." Not sure I correctly understand this table, but should the second sentence read something like: "For every Energy Object in the eoPowerTable, there is a corresponding set of entries in this table, one entry for each power state supported by the Energy Object." Page 38, "eoPowerStateEntry": In the DESCRIPTION clause, the state numbers and state names do not match any documented enumerations for the IANAPowerStateSet textual convention. Should the existing values be replaced with: eman(1024), -- indicates EMAN set emanmechoff(1025), emansoftoff(1026), emanhibernate(1027), emansleep(1028), emanstandby(1029), emanready(1030), emanlowMinus(1031), emanlow(1032), emanmediumMinus(1033), emanmedium(1034), emanhighMinus(1035), emanhigh(1036) Page 45, "eoEnergyStored": The first sentence of the DESCRIPTION clause reads: "This object indicates the resultant of the energy consumed..." Perhaps the following text would be clearer: "This object indicates the difference of the energy consumed..." ^^^^^^^^^^ Page 46, "eoEnergyMaxConsumed": The DESCRIPTION text reads: "This object is the maximum energy ever observed in eoEnergyConsumed since the monitoring started. This value is specified in the common billing units of watt-hours with the magnitude of watt-hours (kW-Hr, MW-Hr, etc.) indicated separately in eoEnergyUnitMultiplier." Does this mean that the eoEnergyMaxConsumed value must be retained across reboots, and thus must be stored in non-volatile memory? Page 48/49/54, where "entity4CRCompliance" is listed: I believe the "entPhysicalClass" object must be added to the lists of MIB objects (entPhysicalIndex, entPhysicalName and entPhysicalUUID). Page 56, "eoACPwrAttributesAvgCurrent": It might be niced to expand the DESCRIPTION clause so that it more precisely specifies the significance of this, perhaps similar to the DESCRIPTION clause for "eoACPwrAttributesAvgVoltage". Page 56, "eoACPwrAttributesFrequency": The UNITS clause does not match the comment after the SYNTAX clause. eoACPwrAttributesFrequency OBJECT-TYPE SYNTAX Integer32 (4500..6500) -- UNITS 0.01 Hertz UNITS "hertz" Would it be useful or helpful to have UnitsMultiplier companion objects for the following objects? Page 58, "eoACPwrAttributesThdAmpheres": Page 60, "eoACPwrAttributesPhaseAvgCurrent": Page 62, "eoACPwrAttributesDelPhaseToNextPhaseVoltage": Page 63, "eoACPwrAttributesWyePhaseToNeutralVoltage": Page 64, "eoACPwrAttributesWyePhaseCurrent": Page 59, "eoACPwrAttributesPhaseEntry": Under the DESCRIPTION clause, it might be helpful to add a comment that indicates the phase-to-phase voltages are in separate tables. When I first encountered the "eoACPwrAttributesPhaseEntry", I wondered about the voltages until I read further in the MIB and found the eoACPwrAttributesDelPhaseTable and the eoACPwrAttributesWyePhaseTable. Page 60, "eoACPwrAttributesPhaseActivePower", "eoACPwrAttributesPhaseReactivePower", "eoACPwrAttributesPhaseApparentPower": Expanding the DESCRIPTION clauses to note these are scaled by the eoACPwrAttributesPowerUnitMultiplier might be helpful, but the DESCRIPTION clause for the "eoACPwrAttributesPowerUnitMultiplier" does note this scaling relationship. Page 61, "eoACPwrAttributesPhaseImpedance": Are the UNITS of "volt-amperes" correct? Page 62/63, "eoACPwrAttributesDelPhaseToNextPhaseVoltage", "eoACPwrAttributesDelThdPhaseToNextPhaseVoltage", "eoACPwrAttributesDelThdCurrent": The last SID values for these objects are 2, 3, and 4, which distinctly does NOT match the values shown in the figure on Page 9, which shows the last SID values as 1, 2, and 3. Page 74, Section 13: [EMAN-AWARE-MIB] J. Parello, B. Claise and M. Chandramoili, "draft-ietf-eman-energy-aware-mib-11 ", work in progress, November 2013. Does it matter, or should this reference draft 13, draft-ietf-eman-energy-aware-mib-13? Regards, --Alan ------------------------------------------------------------------------------ Alan Luchuk SNMP Research, Inc. Voice: +1 865 573 1434 Senior Software Engineer 3001 Kimberlin Heights Road FAX: +1 865 573 9197 luchuk at snmp.com Knoxville, TN 37920-9716 http://www.snmp.com/ ------------------------------------------------------------------------------ From Quittek@neclab.eu Mon Dec 30 11:05:04 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82FFE1AE51F for ; Mon, 30 Dec 2013 11:05:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.14 X-Spam-Level: X-Spam-Status: No, score=-3.14 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 3BOc9PcVZpfM for ; Mon, 30 Dec 2013 11:05:02 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 124211AE293 for ; Mon, 30 Dec 2013 11:05:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 1AE871066AE for ; Mon, 30 Dec 2013 19:54:34 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aJTw6b4w+cGb for ; Mon, 30 Dec 2013 19:54:34 +0100 (CET) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id E80B710664B for ; Mon, 30 Dec 2013 19:54:28 +0100 (CET) Received: from DAPHNIS.office.hd ([169.254.2.18]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Mon, 30 Dec 2013 20:04:29 +0100 From: Juergen Quittek To: Juergen Quittek , eman mailing list Thread-Topic: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 Thread-Index: AQHO+ndiYJGZWdpqpE2anb88yvyKyppsem/ggACvdJA= Date: Mon, 30 Dec 2013 19:04:29 +0000 Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E8688B330D@DAPHNIS.office.hd> References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> <9AB93E4127C26F4BA7829DEFDCE5A6E8688B2E6C@DAPHNIS.office.hd> In-Reply-To: <9AB93E4127C26F4BA7829DEFDCE5A6E8688B2E6C@DAPHNIS.office.hd> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.0.197] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Dec 2013 19:05:04 -0000 Dear all, There are two more comments on draft-ietf-eman-energy-aware-mib-13 that I m= issed to include in my previous email. One is editorial and one is technical: Editorial: MIB modules description It is just once mentioned that there are two MIB modules in this draft (Sec= tion 1.1, first sentence. The draft starts discussing the ENERGY-OBJECT-CON= TEXT-MIB module and sometimes uses "this MIB modules" to refer to it. When = the discussion of the other MIB module starts in the middle of section 5.4 = it would be helpful adding a statement reminding the reader that this modul= e is included in the draft as well. For example by changing in section 5.4,= 3rd paragraph OLD The IANA Energy Relationship MIB module specifies the first=20 version of the IANA-maintained definitions of relationships NEW The IANA Energy Relationship MIB module in Section 6 below specifie= s the first=20 version of the IANA-maintained definitions of relationships Technical: object eoPowerInterfaceType I wonder why object eoPowerInterfaceType is included in the ENERGY-OBJECT-C= ONTEXT-MIB and not in the ENERGY-OBJECT-MIB itself. This object does not pr= ovide context, identity, or relationship information, but rather a technica= l property of a power interface, such as the nominal voltage or the number = of AC phases. Why is it in this MIB module. Wouldn't it fit much better in = the other one? Cheers, Juergen > -----Original Message----- > From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Juergen Quittek > Sent: Montag, 30. Dezember 2013 13:05 > To: eman mailing list > Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mi= b- > 08 and draft-ietf-eman-energy-aware-mib-13 >=20 > Dear all, >=20 > Below please find my comments on draft-ietf-eman-energy-aware-mib-13 > titled "Energy Object Context MIB". I will send comments on draft-ietf-em= an- > energy-monitoring-mib-08 in a separate message. >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Technical comments: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > 1) Section 5.1, 3rd paragraph: Since you are already very precise about t= his > MUST, I would add that the name MUST NOT have length zero. >=20 > 2) Section 5.1, one but last paragraph: "Each Energy Object MUST belong t= o a > single Energy Management Domain or in other words, an Energy Object canno= t > belong to more than one Energy Management Domain." This is more strict > than in the framework where we say an EO "should" not belong to more than > one domain. However, as we have discussed several times, there are > management systems that use more than one domain (different to > EnergyWise). I do not see a good reason to declare that their model is wr= ong. > Thus, we can recommend "make it as EnergWise from Cisco does it" with the > "should" clause that we have in the framework, but we should not fully ex= clude > other solutions with a "must" clause. See also comment 7). >=20 > 3) Section 5.3, 2nd and 3rd paragraph: > Both paragraphs need more explanation and you need to make them consisten= t > with the text in the MIB modules. For LLDP you say "If the LLDP MIB is > implemented". Why don't you have a similar statement for the PoE MIB? You > talk about "the" Energy Object SNMP agent. However, EOs may not have SNMP > agents, for example, if they are just a power interface. And it is not sp= ecified > which of the potentially numerous instances of lldpLocPortNum objects of = a > device should be reported. >=20 > 4) Section 5.4, 4th paragraph: > "Since the communication between the Energy Objects may not be SNMP and i= s > left to the choice of the device manufacturer, an Energy Object can have > additional MIB objects that can be used for easier identification by the = EnMS." > Two comments on this sentence: > A) It is not very obvious if SNMP is not available, it makes sense to use= MIB > objects. Please clarify this. > B) Please note that the choice is not only with the manufacturer. Even if= the > manufacturer builds in SNMP, the operator may choose to disable it ;-) >=20 > 5) Section 6, DESCRIPTION clause of object eoEthPortIndex: > What "attached device" are you talking about? > Why is it relevant for the specification of this object, if that a certai= n MIB > module "should" be implemented on that device? Does it make any different > for the DESCRIPTION of this object whether or not this MIB module is > implemented on the attached device? I do not see why and thus recommend > removing the statement "PoE MIB should be instantiated on the device." >=20 > 6) Section 6, DESCRIPTION clause of object eoMgmtDNSName: > There may be more than one DNS name associated to a single IP address: > "the DNS name" -> "a DNS name" >=20 > 7) Section 6, DESCRIPTION clause of object eoDomainName: > Please insert as second sentence: "If the energy object has been assigned= to > multiple domains, then they are represented in this object as comma-separ= ated > list.", see comment 2). >=20 > 8) Section 6, SYNTAX clause of object eoPowerCategory: > Some devices match more than one category, for example a UPS is a store a= nd > a distributor at the same time, and to be precise, also a consumer. A PoE > Switch is a consumer and a distributor, some devices switch between consu= mer > and producer, etc. We can support all of this if we change the syntax fro= m > INTEGER to BITS. >=20 > 9) Section 6, DESCRIPTION clause of object eoAlternateKey: > There is a contradiction between having this object with MAX-ACCESS read- > write and stating " This object specifies a manufacturer defined string".= If the > manufacturer defines the string, there is no need to write it. I suggest = allowing > the operator to set the value of this document. >=20 > 10) Section 6, DESCRIPTION clause of object eoRelationID: > I recommend adding a sentence to the DESCRIPTION clause, that preferable > the value of an entPhysicalUUID from the Entity MIB should be used for va= lues > of this object. >=20 > 11) Section 6, Conformance of ENERGY-OBJECT-CONTEXT-MIB module: > The dependence of compliance with entity4CRCompliance is stated in the > GROUP DESCRIPTION clauses. In our case, this is not the right place. Ther= e is a > dependency on entity4CRCompliance independent of which group is > implemented. Hence, these statements need to be moved from the GROUP > DESCRIPTION clauses to the module compliance DESCRIPTION clauses of > energyObjectContextMIBFullCompliance and > energyObjectContextMIBReadOnlyCompliance. >=20 > 12) Section 6, Conformance of ENERGY-OBJECT-CONTEXT-MIB module: > We state in other places that implementation of the Entity MIB compliant = with > entity4CRCompliance is a must. But in the conformance section of the ENER= GY- > OBJECT-CONTEXT-MIB the dependency on entity4CRCompliance is stated as > "should". This need to be changed to a "must" or "required." >=20 > 13) Section 6, DESCRIPTION clause of TC IANAEnergyRelationship: > For interoperability, the description need to be clear. As this TC is sta= ted, there > are two points unclear to me: > A) " The enumeration 'poweredBy' is applicable if the > Energy Object A is poweredBy Energy Object B. > The enumeration 'powering' is applicable if the > Energy Object A is powering Energy Object B." > If the TC is used, how do I know which object is A and which is B? Is it = that the > DESCRIPTION clauses of objects of this type must refer to object A and ob= ject > B? > B) "if the Energy Object A is aggregating Energy Object B" > There is no place in this document where there is explained what aggregat= ing > means. >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Editorial comments: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > 14) Abstract, last two lines: > "relationships between reporting devices, remote devices, and monitoring > devices.": The enumeration of "reporting devices", "monitoring devices", = and > "remote devices" is inappropriate because it does not reflect the list of > relationships discussed by the draft: poweredBy, meteredBy, aggregatedBy. >=20 > 15) Section 1. Introduction, 2nd paragraph, last two lines: > "Identification" -> "identification" > "Context" -> "context" > "Relationships" -> "relationships" >=20 > 16) Section 1.1, 3rd paragraph, line 1: > "A second MIB module required by the [EMAN-FMWK]": There is no MIB > module required by the EMAN framework. It seems you wanted to say: "A > second MIB module meeting EMAN requirements given by [RFC6988]". >=20 > 17) Entire Section 3 > This section is completely redundant. It mainly repeats sentences of sect= ion 1.1. > Remove this section and merge sentences you want to keep into section 1.1 >=20 > 18) Section 5, 3rd paragraph, first sentence: > The sentence is not grammatically correct, please fix. Also semantic corr= ection > seems to be needed. You don't mention "identification" as focus of the fi= rst > table. >=20 > 19) Section 5, sentence before Figure 1: > "The following UML diagram illustrates the relationship of the MIB object= s in > the eoTable, eoRelationTable that describe the identity, context and > relationship of an Energy Object." > You should mention that you UML diagram furthermore contains objects from > the Entity MIB. >=20 > 20) Section 5, figure 1: > There is a dotted line at the lower left that goes nowhere. Please cut it= . >=20 > 21) Section 5, grouping of MIB objects is inconsistent. > In Figure 1 you have three groups: "Context", "Identification", "Relation= ships", > where "Identifications" has three subgroups. The sentence below the figur= e > emphasizes this grouping. However, the following subsections 5.1-5.4 are > grouped differently. 5.1 is titled "Identification" but covers only a thi= rd of the > objects under "Identification" in Figure 1. Section 5.2 is consistently w= ith Figure > 1 covering context information. Section 5.3 covers PoE and LLDP identific= ation. > Sections 5.4 is called "Relationships" but covers not just the objects un= der > "Relationships" in Figure 1, but also objects from under "Identification"= in > Figure 1. Here is a clean-up needed. Please split the last sentence from = section > 5.4. It firs much better in section 5.3. >=20 > 22) Section 5, enumeration under Figure 1: > Please note that subsection 5.5 is not another group of MIB objects but r= efers > to objects in subsection 5.1. The sentence above the enumeration implies = that > each numbered item would be a group of objects. >=20 > 23) Section 5.1, 2nd paragraph, line 7: > What is "primary Energy Object information"? >=20 > 24) Section 5.4, 2nd paragraph, last sentence: > "It is important to notice, that it is possible that" -> "Obviously," > "not have an" -> "not have any" >=20 > 25) Section 5.4, 4th paragraph > The entire paragraph is in the wrong subsection. It rather belongs to sub= section > 5.1 or 5.3. >=20 > 26) Section 6, DESCRIPTION clause of object eoEthPortGrpIndex: > See comment 5). There is a full stop missing at the end of the second sen= tence. >=20 > 27) Section 6, OBJECTS clause of GROUP energyObjectRelationTableGroup: > The comment "Note that object eoRelationIndex is not included since it is= not- > accessible" is not really needed. Almost every Conformance section has su= ch > objects and usually this comment is omitted. >=20 > Cheers, > Juergen >=20 >=20 > > -----Original Message----- > > From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau > > Sent: Montag, 16. Dezember 2013 16:56 > > To: eman mailing list > > Subject: [eman] WG Last Call for > > draft-ietf-eman-energy-monitoring-mib-08 > > and draft-ietf-eman-energy-aware-mib-13 > > > > > > As agreed at the last WG meeting, with the EMAN Framework > completing > > its WG LC the chairs would like to initiate a WG LC on draft-ietf- > > eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13. > > The WG LC will end on Dec 30 at 8AM EDT. > > > > Thank you, > > > > Nevil and Tom > > >=20 > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman From Quittek@neclab.eu Mon Dec 30 11:33:39 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECC9E1AE2D7 for ; Mon, 30 Dec 2013 11:33:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.14 X-Spam-Level: X-Spam-Status: No, score=-3.14 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 Qp2XLxUSOKI6 for ; Mon, 30 Dec 2013 11:33:36 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id F2AED1AE21E for ; Mon, 30 Dec 2013 11:33:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id E6FF31066AE for ; Mon, 30 Dec 2013 20:23:07 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id odNw1Ne+cKAC for ; Mon, 30 Dec 2013 20:23:07 +0100 (CET) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id C898B10664B for ; Mon, 30 Dec 2013 20:23:02 +0100 (CET) Received: from DAPHNIS.office.hd ([169.254.2.18]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Mon, 30 Dec 2013 20:33:03 +0100 From: Juergen Quittek To: eman mailing list Thread-Topic: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 Thread-Index: AQHO+ndiYJGZWdpqpE2anb88yvyKypptNC8w Date: Mon, 30 Dec 2013 19:33:02 +0000 Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E8688B333E@DAPHNIS.office.hd> References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> In-Reply-To: <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.0.197] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Dec 2013 19:33:39 -0000 Dear all, Here are my last two comments for this WGLC. Both concerns the conformance = section of the ENERGY-OBJECT-MIB module in draft-ietf-eman-energy-monitorin= g-mib-08: 1. I may have missed a point here: Why is the Entity MIB not mandatory anym= ore to implement? It is just two additional objects, since entPhysicalIndex= from this MIB is needed anyway. Particularly, we considered the UUID provi= ded by this MIB essential for our framework. 2. Why is the module compliance dependency on the Entity MIB repeated in th= e DESCRIPTION clauses of all optional groups within a MODULE-COMPLIANCE dec= laration? I think It is fully sufficient to have it stated in the top DESCR= IPTION clause of the MODULE-COMPLIANCE declaration. Does it make any sense = to repeat it for optional groups? Cheers, Juergen > -----Original Message----- > From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau > Sent: Montag, 16. Dezember 2013 16:56 > To: eman mailing list > Subject: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 > and draft-ietf-eman-energy-aware-mib-13 >=20 >=20 > As agreed at the last WG meeting, with the EMAN Framework > completing its WG LC the chairs would like to initiate a WG LC on draft-i= etf- > eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13. > The WG LC will end on Dec 30 at 8AM EDT. >=20 > Thank you, >=20 > Nevil and Tom >=20 From tnadeau@lucidvision.com Mon Dec 30 11:52:44 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28A331AE30A for ; Mon, 30 Dec 2013 11:52:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.438 X-Spam-Level: X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] 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 NSM5HI0SAxrh for ; Mon, 30 Dec 2013 11:52:42 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 6F04C1AE1DE for ; Mon, 30 Dec 2013 11:52:42 -0800 (PST) Received: from [192.168.1.101] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 3F033269C5FB; Mon, 30 Dec 2013 14:52:36 -0500 (EST) Content-Type: multipart/signed; boundary="Apple-Mail=_7DDFD106-1888-45E9-A8A5-3901A3B919D4"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Nadeau In-Reply-To: <9AB93E4127C26F4BA7829DEFDCE5A6E8688B32A5@DAPHNIS.office.hd> Date: Mon, 30 Dec 2013 14:52:36 -0500 Message-Id: References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> <5339BC8D-660B-4659-96DC-C0170E124134@lucidvision.com> <9AB93E4127C26F4BA7829DEFDCE5A6E8688B32A5@DAPHNIS.office.hd> To: Juergen Quittek X-Mailer: Apple Mail (2.1827) Cc: eman mailing list Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Dec 2013 19:52:44 -0000 --Apple-Mail=_7DDFD106-1888-45E9-A8A5-3901A3B919D4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii The note said 8AM EDT. *) Anyways, send over your comments ASAP. --Tom On Dec 30, 2013:1:46 PM, at 1:46 PM, Juergen Quittek = wrote: > Hi Tom, > I missed the fact that the deadline is already in the morning of = today. I thought I had the full day today for sending them. There are = still some comments that I planned to send this evening. I will send = them asap and hope they will be OK even if a few hours late. > Thanks, > Juergen >=20 >> -----Original Message----- >> From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau >> Sent: Montag, 30. Dezember 2013 14:44 >> To: eman mailing list >> Subject: Re: [eman] WG Last Call for = draft-ietf-eman-energy-monitoring-mib- >> 08 and draft-ietf-eman-energy-aware-mib-13 >>=20 >>=20 >> WG, >>=20 >> This concludes the WG LC on the MIBs. We have received just one = set >> of comments from the WG and one set of comments regarding the OID >> numbering. Would the document editors please address these and = republish >> the drafts ASAP so that we can proceed with progressing the drafts? >>=20 >> Cheers and Happy Holidays, >>=20 >> Tom >>=20 >>=20 >>>=20 >>> As agreed at the last WG meeting, with the EMAN Framework >> completing its WG LC the chairs would like to initiate a WG LC on = draft-ietf- >> eman-energy-monitoring-mib-08 and = draft-ietf-eman-energy-aware-mib-13. >> The WG LC will end on Dec 30 at 8AM EDT. >>>=20 >>> Thank you, >>>=20 >>> Nevil and Tom >>>=20 >>>=20 >>> _______________________________________________ >>> eman mailing list >>> eman@ietf.org >>> https://www.ietf.org/mailman/listinfo/eman >=20 >=20 --Apple-Mail=_7DDFD106-1888-45E9-A8A5-3901A3B919D4 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJSwc8EAAoJEPcO+I7eiUJZyTQP/2lBGQJbuPaw6bRSvrAQ4FEK jlm3XiwCHo25cSYmLgYWgFKnB4fUtTI1fLgd9di/Mc0wW5KeUhVvzb45zH/4qn+0 Wy+yJPn35BGbHKjF96W+F3U7E1h9vO3dUQwMatLHidR5yeV4tDo4E2xrh+cj9Pmg EDDN6tZJIw9saYt7G21hj38Vi+Yvo+d9ImrMLmkCfa25EsEClGA1VEWZhLYD90rS W0ChxMM6enHUFfaRvWhBxDwyWjrWOgLJV7N1nedthFwxoZCOlkyt53qsjrscGr+t s3t7Vv8tpGNjFhmFnU9eqn+oX+j4O31VLTZHK6hYGU0lcvMrnvoN4VJgqWncls3M Y5p6xTTSeWTRTLLGsL0Hd2qr2atmiV4Dn1wggQWcY/T3ABhmjKifAg3BOvzMqpH2 kJ4WdZZJ3fE2vZ8ASS9zpTSdaXpgoFA1lRR7hOYWMSE7ZNt46/kLjHIba0MSwP6q 3toyejzmCqCqVdJagP/hEWAELdWZPmZ9vEaLf/L7z4VeT9LSV4a/xlE5VauqbQL8 c6S+yAVvJEmtyWVZm+9QC6gQRSH4dxSq5dm8y6dXiieHCjy5n8isGZUj8+5n5wKv gh3InH51a75US35N69O6pN8TJTl8QzJyW/+geQLwuD1L3Kn/g+ys3Ov2+Odz3wEi 6Mt0LWIa8pOe9h93AD5u =Po0a -----END PGP SIGNATURE----- --Apple-Mail=_7DDFD106-1888-45E9-A8A5-3901A3B919D4-- From karagian@cs.utwente.nl Tue Dec 31 02:17:19 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D8DC1AE0AB for ; Tue, 31 Dec 2013 02:17:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 H6TiQZUuxkVf for ; Tue, 31 Dec 2013 02:17:16 -0800 (PST) Received: from out47-ams.mf.surf.net (out47-ams.mf.surf.net [145.0.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id D94C61ADEA7 for ; Tue, 31 Dec 2013 02:17:15 -0800 (PST) Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by outgoing2-ams.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id rBVAH6tV017017; Tue, 31 Dec 2013 11:17:07 +0100 Received: from EXHUB01.ad.utwente.nl (130.89.4.228) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 31 Dec 2013 11:17:10 +0100 Received: from EXMBX23.ad.utwente.nl ([169.254.3.41]) by EXHUB01.ad.utwente.nl ([130.89.4.228]) with mapi id 14.02.0328.009; Tue, 31 Dec 2013 11:17:06 +0100 From: To: Thread-Topic: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 Thread-Index: AQHPBZi1GAOTTyzl30yr0sj36UfzaZpuFzVJgAAAhLQ= Date: Tue, 31 Dec 2013 10:17:05 +0000 Message-ID: References: <5298B7FA.1010509@cisco.com> <52A5A9FA.80101@cisco.com> <52A5C2A6.9000501@cisco.com> <52AB8777.9060704@cisco.com> <653A4764-315C-4671-B0DA-389553CB3E29@lucidvision.com> <5339BC8D-660B-4659-96DC-C0170E124134@lucidvision.com> <9AB93E4127C26F4BA7829DEFDCE5A6E8688B32A5@DAPHNIS.office.hd>, In-Reply-To: Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-mimectl: Produced By Microsoft Exchange V14.2.247.1 x-originating-ip: [86.91.134.3] Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F4141DAEXMBX23adutwent_" MIME-Version: 1.0 X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN) X-CanIt-Geo: ip=130.89.5.49; country=NL; region=15; city=Enschede; latitude=52.2195; longitude=6.8912; http://maps.google.com/maps?q=52.2195,6.8912&z=6 X-CanItPRO-Stream: utwente-out:default (inherits from utwente:default, base:default) X-Canit-Stats-ID: 0vL8ah7zc - 9500fa20802b - 20131231 (trained as not-spam) X-Scanned-By: CanIt (www . roaringpenguin . com) Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Dec 2013 10:17:19 -0000 --_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F4141DAEXMBX23adutwent_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi all, Sorry for the delay on providing comments on time for the WGLC of draft-iet= f-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13. Here are my comments! Many of the comments that I wanted to send are similar to the ones sent by = Juergen Quittek. Therefore, I will send only the ones that are different! =3D> Regarding: draft-ietf-eman-energy-aware-mib-13: Comment_1: Section 5, page 6 shows the entries/attributes (MIB objects) of= the eaTable and eoRelationTable. In Figure 1 the UML diagram illustrates t= he relationship of the MIB objects in the eatable and eoRelationTable. Howe= ver not all entries (MIB objects) depicted in eaTable and eoRelationTable (= page 6) are shown in the UML diagrams. Please elaborate on this in the text= . Comment_2: In section 5.2, page 20 is mentioned: =93The Energy Object can b= e classified as consuming power or supplying power to other devices or that= Energy Object can perform both of those functions, ..=94. However, in the = formal MIB definition on page 20, eoPowerCategory can get the values: consu= mer (0), producer(1), meter(2), distributor(3) or store(4). From what I can= see no value is provided for the situation that the energy object can perf= orm both functions consumer and producer. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D =3D> Regarding draft-ietf-eman-energy-monitoring-mib-08: Comment_1:Section 5: It is not clear what is the relation between the ENERG= Y-OBJECT-MIB MIB module tables, the associated UML diagram given in Figure = 1 and the text other subsections (5.1, 5.2, 5.3, 5.4, 5.5 and 5.6.).. Pleas= e make this relation clear. Comment_2: The same holds for the powerAttributeMIB MIB module tables, UML = diagram given in Figure 2 and subsections (5.1, 5.2, 5.3, 5.4, 5.5 and 5.6.= ). Comment_3: The description of the powerAttributeMIB MIB module tables on pa= ge 8 is too short. A similar description as the one described for the ENERG= Y-OBJECT-MIB MIB module tables in page 6 could be also provided, Comment_4: Some parts of the UML diagram given in Figure 2 as representing = the relations in the powerAttributeMIB are (probabl) part of the ENERGY-OB= JECT-MIB. These are the Energy ParametersTable and EnergyTable. Comment_5: not all entries (MIB objects) depicted in the ENERGY-OBJECT-MIB = MIB module tables are shown in the UML diagram depicted in Fgure 1.Please e= laborate. Comment_6: the same holds for powerAttributeMIB MIB module tables and the = UML diagram depicted in Figure 2. Comment_7: Maybe the title of Section 5.1 should be: Enetgy Object Identity= , instead of Energy Object Information? Comment_8: The description of the vertical axis used in Figure 3 is not cle= ar to me. Are both horizontal axis and vertical axis representing time. Reg= arding the vertical axis you might want to say that the vertical axis repre= sents the amount of measured power ? Comment_9: The description of Figure 4 is not clear to me. You might includ= e at the right sde of the figure and for each window the term S+L, so (S1+L= , S2+L, S3+L and S4+L). You can then explain that the value of the EoEnergy= Consumed is obtained at these time intervals (Sx+L).. Comment_10: Section 6 is very important and its importance should be emphas= ized more clearly in the Introduction. Comment_11: In Section 6 the term EMAN-MON-MIB is used for the first time. = I considered that it referes to this document. Please emphasize that in the= text. Comment_12: Section 8 provides an example for the implementation of the Ene= rgy Object, including the Energy Object relationships. Is it possible to pr= ovide an example of the IANAEnergyRelationship (in particular regaring aggr= egation) defined in [ENERGY-AWARE-MIB]. Comment_13: Are the MIB objects defined in this draft complying with the me= chanisms defined by SMIv2 [RFC2578, RFC2579, RFC2580? If yes, please emphas= ize this in the document! Best regards, Georgios Karagiannis ________________________________ Van: eman [eman-bounces@ietf.org] namens Thomas Nadeau [tnadeau@lucidvision= .com] Verzonden: maandag 30 december 2013 20:52 To: Juergen Quittek Cc: eman mailing list Onderwerp: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mi= b-08 and draft-ietf-eman-energy-aware-mib-13 The note said 8AM EDT. *) Anyways, send over your comments ASAP. --Tom On Dec 30, 2013:1:46 PM, at 1:46 PM, Juergen Quittek wr= ote: > Hi Tom, > I missed the fact that the deadline is already in the morning of today. I= thought I had the full day today for sending them. There are still some co= mments that I planned to send this evening. I will send them asap and hope = they will be OK even if a few hours late. > Thanks, > Juergen > >> -----Original Message----- >> From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau >> Sent: Montag, 30. Dezember 2013 14:44 >> To: eman mailing list >> Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-m= ib- >> 08 and draft-ietf-eman-energy-aware-mib-13 >> >> >> WG, >> >> This concludes the WG LC on the MIBs. We have received just one se= t >> of comments from the WG and one set of comments regarding the OID >> numbering. Would the document editors please address these and republish >> the drafts ASAP so that we can proceed with progressing the drafts? >> >> Cheers and Happy Holidays, >> >> Tom >> >> >>> >>> As agreed at the last WG meeting, with the EMAN Framework >> completing its WG LC the chairs would like to initiate a WG LC on draft-= ietf- >> eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13. >> The WG LC will end on Dec 30 at 8AM EDT. >>> >>> Thank you, >>> >>> Nevil and Tom >>> >>> >>> _______________________________________________ >>> eman mailing list >>> eman@ietf.org >>> https://www.ietf.org/mailman/listinfo/eman > > --_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F4141DAEXMBX23adutwent_ Content-Type: text/html; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable

Hi all,

 

Sorry for the delay on providing comments on time for the WGLC of = draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib-13.

 

Here are my comments!

Many of the comments that I wanted to send are similar to the ones= sent by Juergen Quittek. Therefore, I will send only the ones that are different!

 

=3D> Regarding: draft-ietf-eman-energy-aware-mib-13:=

 

Comment_1: Section 5, page 6 shows the entries/attributes  (MIB objects) of the eaTable= and eoRelationTable. In Figure 1 the UML diagram illustrates the relations= hip of the MIB objects in the eatable and eoRelationTable. However not all = entries (MIB objects) depicted in eaTable and eoRelationTable (page 6) are shown in the UML diagrams. Please elabora= te on this in the text.

 

Comment_2: In section 5.2, page 20 is mentioned: =93The Energy Obj= ect can be classified as consuming power or supplying power to other devices or that Energy Object can perform both of those fun= ctions, ..=94. However, in the formal MIB definition on page 20, eoPowerCat= egory can get the values: consumer (0), producer(1), meter(2), distributor(= 3) or store(4). From what I can see no value is provided for the situation that the energy object can perform = both functions consumer and producer.

 

 

=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D

 

=3D> Regarding draft-ietf-eman-energy-monitoring-mib-08:

 

Comment_1:Section 5: It is not clear what is the relation between = the ENERGY-OBJECT-MIB MIB module tables, the associated UML diagram given in Figure 1 and the text other subsections (5= .1, 5.2, 5.3, 5.4, 5.5 and 5.6.).. Please make this relation clear.

 

Comment_2: The same holds for the powerAttributeMIB MIB module tab= les, UML diagram given in Figure 2 and subsections (5.1, 5.2, 5.3, 5.4, 5.5 and 5.6.).

 

Comment_3: The description of the powerAttributeMIB MIB module tab= les on page 8 is too short. A similar description as the one described for the ENERGY-OBJECT-MIB MIB module tables in page 6= could be also provided,

 

Comment_4: Some parts of the UML diagram given in Figure 2 as repr= esenting the relations in the powerAttributeMIB are (probabl)  part of the E= NERGY-OBJECT-MIB. These are the Energy ParametersTable and EnergyTable.

 

Comment_5: not all entries (MIB objects) depicted in the ENERGY-OB= JECT-MIB MIB module tables are shown in the UML diagram depicted in Fgure 1.Please elaborate.=

 

Comment_6: the same holds for powerAttributeMIB MIB module tables  and the UML diagram depicted= in Figure 2.

 

Comment_7: Maybe the title of Section 5.1 should be: Enetgy Object= Identity, instead of Energy Object Information?

 

Comment_8: The description of the vertical axis used in Figure 3 i= s not clear to me. Are both horizontal axis and vertical axis representing time. Regarding the vertical axis you might= want to say that the vertical axis represents the amount of measured power= ?

 

Comment_9: The description of Figure 4 is not clear to me. You mig= ht include at the right sde of the figure and for each window the term S+L, so (S1+L, S2+L, S3+L and S4&= #43;L). You can then explain that the value of the EoEnergyConsumed is obta= ined at these time intervals (Sx+L)..

 

Comment_10: Section 6 is very important and its importance should = be emphasized more clearly in the Introduction.

 

Comment_11: In Section 6 the term EMAN-MON-MIB is used for the fir= st time. I considered that it referes to this document. Please emphasize that in the text.

 

Comment_12: Section 8 provides an example for the implementation o= f the Energy Object, including the Energy Object relationships. Is it possible to provide an example of the IANAEnergyRelat= ionship (in particular regaring aggregation) defined in [ENERGY-AWARE-MIB].=

 

Comment_13: Are the MIB objects defined in this draft complying wi= th the mechanisms defined by SMIv2 [RFC2578, RFC2579, RFC2580? If yes, please emphasize this in the document!

 

Best regards,

Georgios Karagiannis

 

 

 

Van: eman [eman-bounces@ietf.org] namens Thomas Nadeau [tnadeau@= lucidvision.com]
Verzonden: maandag 30 december 2013 20:52
To: Juergen Quittek
Cc: eman mailing list
Onderwerp: Re: [eman] WG Last Call for draft-ietf-eman-energy-monito= ring-mib-08 and draft-ietf-eman-energy-aware-mib-13


        The note said 8AM EDT. *)

        Anyways, send over your comments= ASAP.

        --Tom


On Dec 30, 2013:1:46 PM, at 1:46 PM, Juergen Quittek <Quittek@neclab.eu&= gt; wrote:

> Hi Tom,
> I missed the fact that the deadline is already in the morning of today= . I thought I had the full day today for sending them. There are still some= comments that I planned to send this evening. I will send them asap and ho= pe they will be OK even if a few hours late.
> Thanks,
>    Juergen
>
>> -----Original Message-----
>> From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau
>> Sent: Montag, 30. Dezember 2013 14:44
>> To: eman mailing list
>> Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monito= ring-mib-
>> 08 and draft-ietf-eman-energy-aware-mib-13
>>
>>
>>       WG,
>>
>>       This concludes the WG LC on th= e MIBs. We have received just one set
>> of comments from the WG and one set of comments regarding the OID<= br> >> numbering. Would the document editors please address these and rep= ublish
>> the drafts ASAP so that we can proceed with progressing the drafts= ?
>>
>>       Cheers and Happy Holidays,
>>
>>       Tom
>>
>>
>>>
>>>      As agreed at the last WG meeting= , with the EMAN Framework
>> completing its WG LC the chairs would like to initiate a WG LC on = draft-ietf-
>> eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-aware-mib= -13.
>> The WG LC will end on Dec 30 at 8AM EDT.
>>>
>>>      Thank you,
>>>
>>>      Nevil and Tom
>>>
>>>
>>> _______________________________________________
>>> eman mailing list
>>> eman@ietf.org
>>> https://www.ietf.org/mailman/listinfo/eman
>
>

--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F4141DAEXMBX23adutwent_--