From nobody Sat Mar 1 22:11:50 2014 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 A4C4C1A0B96 for ; Sat, 1 Mar 2014 22:11:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.152 X-Spam-Level: X-Spam-Status: No, score=0.152 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, 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 lxL_KxkcjtTZ for ; Sat, 1 Mar 2014 22:11:45 -0800 (PST) Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) by ietfa.amsl.com (Postfix) with ESMTP id 31F321A0B94 for ; Sat, 1 Mar 2014 22:11:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1393740703; x=1425276703; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=K0aP9wPkGIeKowrRba3k4vDIRaWMX2IwS7aIORheAIk=; b=Q5XdPer8zaPa1Vumf6HMS4gDznoj42j+lfO+I/1AzGC8h5WZN5M4z0o3 TRR2dgHtYwCSFuoOYc8Tqtg4SEXpMKq0UABuC788Ov8TNKccVdxs1rhLq Q95CIhCcH+t9DqSqrEVkiHag3lrqqx4q3NIloM5GYIzRs2y3+4bFli/hD M=; X-IronPort-AV: E=Sophos;i="4.97,571,1389697200"; d="scan'208";a="236678964" X-Ironport-HAT: None - $RELAY-AUTH X-Ironport-Source: 130.129.155.105 - Outgoing - Outgoing-SSL Received: from unknown (HELO [130.129.155.105]) ([130.129.155.105]) by mx2-int.auckland.ac.nz with ESMTP; 02 Mar 2014 19:11:39 +1300 Message-ID: <5312CB98.5040900@auckland.ac.nz> Date: Sun, 02 Mar 2014 19:11:36 +1300 From: Nevil Brownlee User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: eman@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/eman/ir8gmkCWSAEewjx6EXpe4rW8E4s Subject: [eman] EMAN Meeting Materials updated 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: Sun, 02 Mar 2014 06:11:49 -0000 Hi all: I've put the slides I've received so far up on the Meeting Materials page, thanks to the authors who've sent them to me. I'm still waiting for some of the slides ... Cheers, Nevil -- --------------------------------------------------------------------- Nevil Brownlee Computer Science Department | ITS Phone: +64 9 373 7599 x88941 The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand From nobody Sun Mar 2 09:51:22 2014 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 9C5481A0221; Sun, 2 Mar 2014 09:51:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.149 X-Spam-Level: X-Spam-Status: No, score=-3.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547, 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 JMraH67wEewC; Sun, 2 Mar 2014 09:51:19 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 8E4861A0202; Sun, 2 Mar 2014 09:51:19 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id BBBFC106E91; Sun, 2 Mar 2014 18:51:16 +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 6OtILefczyOv; Sun, 2 Mar 2014 18:51:16 +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 9B605106F0A; Sun, 2 Mar 2014 18:50:56 +0100 (CET) Received: from PALLENE.office.hd ([169.254.1.233]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Sun, 2 Mar 2014 18:50:56 +0100 From: Juergen Quittek To: Thomas Nadeau , "draft-ietf-eman-battery-mib@tools.ietf.org" Thread-Topic: [eman] MIB-Doctor Review of draft-ietf-eman-battery-mib-11 Thread-Index: AQHPGUrAPWHfU4CFBUe1IOKiozRfY5rJFwDg Date: Sun, 2 Mar 2014 17:50:55 +0000 Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E877A701F4@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.7.0.201] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/eman/3GPLxXzFbO9Wkt-V8v3HcD2LHY8 Cc: "MIB Doctors \(E-mail\)" , eman mailing list Subject: Re: [eman] MIB-Doctor Review of draft-ietf-eman-battery-mib-11 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: Sun, 02 Mar 2014 17:51:21 -0000 Hi Tom, Here is our reply to the issue of limiting notification rates, that you rai= sed: > -----Original Message----- > From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau > Sent: Freitag, 24. Januar 2014 22:24 > To: draft-ietf-eman-battery-mib@tools.ietf.org > Cc: MIB Doctors (E-mail); eman mailing list > Subject: [eman] MIB-Doctor Review of draft-ietf-eman-battery-mib-11 > [snip] >=20 > batteryTemperatureNotification NOTIFICATION-TYPE > OBJECTS { > batteryTemperature, > batteryCellIdentifier > } > STATUS current > DESCRIPTION > "This notification can be generated when the measured > temperature (batteryTemperature) rises above the threshold > defined by object batteryAlarmHighTemperature or falls > below the threshold defined by object > batteryAlarmLowTemperature. >=20 > If the low or high temperature has been detected for a > single cell or a set of cells of the battery and not for the > entire battery, then object batteryCellIdentifier should be > set to a value that identifies the cell or set of cells. > Otherwise, the value of object batteryCellIdentifier should > be set to the empty string when this notification is > generated." > ::=3D { batteryNotifications 4 } >=20 > TOM: The same comment about rate limiting as above. I can see when a > battery is failing this value could float just about and below this value= causing > numerious notifications to be issued. Have you considered such cases? Thank you for pointing to this. Yes, we considered the issue for=20 Notifications, but unfortunately not for all.=20 The batteryLowNotification and the batteryCriticalNotification=20 have statements in their DESCRIPTION clause that prohibits repeated=20 generation of the notification before the battery has been charged again. But for the batteryTemperatureNotification and the=20 batteryAgingNotification there are no such statements. Here additional=20 text is needed as you suggest. For the batteryAgingNotification we know how to address the issue. But for the batteryTemperatureNotification=20 we still have to find an appropriate solution. I will make this an open issue and bring it to the group at the eman session. Thanks, Juergen From nobody Sun Mar 2 23:41:33 2014 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 2D9BD1A07B3 for ; Sun, 2 Mar 2014 23:41:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 EEvwo281osYj for ; Sun, 2 Mar 2014 23:41:24 -0800 (PST) Received: from out23-ams.mf.surf.net (out23-ams.mf.surf.net [145.0.1.23]) by ietfa.amsl.com (Postfix) with ESMTP id C05811A0349 for ; Sun, 2 Mar 2014 23:41:23 -0800 (PST) Received: from EXEDGE01.ad.utwente.nl (exedge01.ad.utwente.nl [130.89.5.48]) by outgoing1-ams.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s237fEd6023095; Mon, 3 Mar 2014 08:41:16 +0100 Received: from EXHUB01.ad.utwente.nl (130.89.4.228) by EXEDGE01.ad.utwente.nl (130.89.5.48) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 3 Mar 2014 08:37:31 +0100 Received: from EXMBX23.ad.utwente.nl ([169.254.3.208]) by EXHUB01.ad.utwente.nl ([130.89.4.228]) with mapi id 14.02.0328.009; Mon, 3 Mar 2014 08:37:27 +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: AQHPLSakvFovduBxAkm3DlLTR33McZrPCQNngAADh48= Date: Mon, 3 Mar 2014 07:37:26 +0000 Message-ID: References: , 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: [80.229.76.233] Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F432FAFEXMBX23adutwent_" MIME-Version: 1.0 X-Bayes-Prob: 0.0001 (Score 0, tokens from: utwente-out:default, base:default, @@RPTN) X-CanIt-Geo: ip=130.89.5.48; 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: 0uLwTFgbm - c27e7651c192 - 20140303 (trained as not-spam) X-Scanned-By: CanIt (www . roaringpenguin . com) Archived-At: http://mailarchive.ietf.org/arch/msg/eman/c_jJWOCmvsx5UXo8hbp_va9V-hI 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, 03 Mar 2014 07:41:29 -0000 --_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F432FAFEXMBX23adutwent_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi Brad, Thanks for working out my comments! Regarding your questions, please see in line! > Van: Brad Schoening [brads@coraid.com] > Verzonden: woensdag 19 februari 2014 4:56 > To: Karagiannis, G. (EWI); eman@ietf.org > Onderwerp: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-= mib-08 and draft-ietf-eman-> > energy-aware-mib-13 > Hi Georgios, > I have made changes to the latest published draft (v9) that should addres= s you comments 3-7 and 11. For a few of > the remaining comment, please see detailed responses below: Georgios: Thanks! > Comment_1 & 2 =96 I wasn't sure what you found unclear here Georgios: I thought that this relation can be made more clear if you would = have had a small introductory text! > Comment_8 =96 the text immediately above the diagram explains the horizon= tal axis and then the vertical axis. > Comment_9 - the text immediately above the diagram already does elaborat= es on how the overlapping windows Georgios: Yes, the text describes this, but it is not clear to me whether t= his is what you would like to show in these graphs. Would it not be more cl= ear to emphasize that the vertical axis represents the amount of measured p= ower at the end of the sampling period? > Comment_12 =96 this is a good point, but we felt it would be better to pr= ovide examples in the use cases section of > the applicability statement. As you observe, use cases could representin= g both the EnergyMonitoringMIB AND the > EnergyAwareMIB and this would be best placed in a separate document. Georgios: Okay! > Comment_13 =96 compliance with SMIv2 can be assumed since the MIB import= s from SNMPv2-SMI, correct? Georgios: Yes, but I have missed this statement "the MIB imports from SNMPv= 2-SMI" from the draft! > Best Regards, > Brad Best regards, Georgios From: > Date: Tue, 31 Dec 2013 10:17:05 +0000 To: > Subject: Re: [eman] WG Last Call for draft-ietf-eman-energy-monitoring-mib-= 08 and draft-ietf-eman-energy-aware-mib-13 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 Thom= as 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 > 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 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 > > _______________________________________________ eman mailing list eman@ietf= .org https://www.ietf.org/mailman/listinfo/eman --_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F432FAFEXMBX23adutwent_ Content-Type: text/html; charset="Windows-1252" Content-ID: <943DE7B049FDED4F8475FD3E74BFD303@exchange.utwente.nl> Content-Transfer-Encoding: quoted-printable

Hi Brad,

 

Thanks for working out my comments!

Regarding your questions, please see in line!

> Van: Brad Sc= hoening [brads@coraid.com]
> Verzonden: woensdag 19 februari 2014 4:56
> To: Karagiannis, G. (EWI); eman@ietf.org
> Onderwerp: Re: [eman] WG Last Call for draft-i= etf-eman-energy-monitoring-mib-08 and draft-ietf-eman->
> energy-aware-mib-13
> Hi Georgios,
> I have made changes to the latest published draft (v9= ) that should address you comments 3-7 and 11.  For a few of
>  the remaining comment, please see detailed= responses below:
 
Georgios: Thanks!

> Comment_1 & 2 =96 I wasn't sure what you fou= nd unclear here
 
Georgios: I thought that this relation can be made more clear if you w= ould have had a small introductory text!
 
> Comment_8 =96 the text immediately above the dia= gram explains the horizontal axis and then the vertical axis. 
> Comment_9 -  the text immediately above the= diagram already does elaborates on how the overlapping windows 
 
Georgios: Yes, the text describes this, but it is not clear to me whet= her this is what you would like to show in these graphs. Would it not be mo= re clear to emphasize that the vertical axis represents the amount of measu= red power at the end of the sampling period?
 
 
 
> Comment_12 =96 this is a good point, but we felt= it would be better to provide examples in the use cases section of
> the applicability statement.  As you observ= e, use cases could representing both the EnergyMonitoringMIB AND the
> EnergyAwareMIB and this would be best placed in = a separate document.
 
Georgios: Okay!
 
>  Comment_13 =96 compliance with SMIv2 can b= e assumed since the MIB imports from SNMPv2-SMI, correct?
Georgios: Yes, but I have missed this statement "the MIB imports = from SNMPv2-SMI" from the draft!

> Best Regards,

> Brad
 

Best regards,
Georgios

 

From: <karagian@cs.utwente.nl>
Date: Tue, 31 Dec 2013 10:17:05 &#= 43;0000
To: <eman@ietf.org>
Subject: Re: [eman] WG Last Call f= or draft-ietf-eman-energy-monitoring-mib-08 and draft-ietf-eman-energy-awar= e-mib-13

Hi all,

 

Sorry for the delay on pro= viding comments on time for the WGLC of draft-ietf-eman-energy-monitoring-m= ib-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-i= etf-eman-energy-aware-mib-13:

 

Comment_1: Section 5, page= 6 shows the entries/attributes  (MIB objects) of the eaTable and eoRelationTable. In Fig= ure 1 the UML diagram illustrates the relationship of the MIB objects in th= e eatable and eoRelationTable. However not all entries (MIB objects) depict= ed 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 be 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: = 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 a= nd 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-ie= tf-eman-energy-monitoring-mib-08:

 

Comment_1:Section 5: It is= not clear what is the relation between the ENERGY-OBJECT-MIB MIB module ta= bles, 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 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 page 8 is too short. A simil= ar 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 t= he UML diagram given in Figure 2 as representing the relations in the power= AttributeMIB are (probabl)  part of the ENERGY-OBJECT-MIB. These are the Energy Para= metersTable and EnergyTable.

 

Comment_5: not all entries= (MIB objects) depicted in the ENERGY-OBJECT-MIB MIB module tables are show= n 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.<= /p>

 

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 clear to me. Are both horizon= tal axis and vertical axis representing time. Regarding the vertical axis you might want to say that the vertical axis r= epresents the amount of measured power ?

 

Comment_9: The description= of Figure 4 is not clear to me. You might 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+L). You can then explain that the= value of the EoEnergyConsumed is obtained at these time intervals (Sx+= L)..

 

Comment_10: Section 6 is v= ery important and its importance should be emphasized more clearly in the I= ntroduction.

 

Comment_11: In Section 6 t= he term EMAN-MON-MIB is used for the first time. I considered that it refer= es to this document. Please emphasize that in the text.

 

Comment_12: Section 8 prov= ides an example for the implementation of the Energy Object, including the = Energy Object relationships. Is it possible to provide an example of the IANAEnergyRelationship (in particular regarin= g aggregation) defined in [ENERGY-AWARE-MIB].

 

Comment_13: Are the MIB ob= jects defined in this draft complying with 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> 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.o= rg
>>> https://www.ietf.org/mailman/listinfo/eman
>
>

_______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman
--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F432FAFEXMBX23adutwent_-- From nobody Mon Mar 3 10:32:23 2014 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 3FE901A02D3; Mon, 3 Mar 2014 10:32:21 -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 kx5mn6wMp4Fx; Mon, 3 Mar 2014 10:32:19 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D6EB1A02EE; Mon, 3 Mar 2014 10:32:18 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.0.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140303183218.25201.31576.idtracker@ietfa.amsl.com> Date: Mon, 03 Mar 2014 10:32:18 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/eman/8GZyeDNfZL1q7GV6NccYNJP9OwA Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-framework-16.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: Mon, 03 Mar 2014 18:32:21 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Energy Management Working Group of the IETF. Title : Energy Management Framework Authors : Benoit Claise Brad Schoening Juergen Quittek Filename : draft-ietf-eman-framework-16.txt Pages : 57 Date : 2014-03-03 Abstract: This document defines a framework for Energy Management for devices and device components within or connected to communication networks. The framework presents a physical reference model and information model. The information model consists of an Energy Management Domain as a set of Energy Objects. Each Energy Object can be attributed with identity, classification, and context. Energy Objects can be monitored and controlled with respect to power, Power State, energy, demand, Power Attributes, and battery. Additionally the framework models relationships and capabilities between Energy Objects. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-framework/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-framework-16 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-eman-framework-16 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 nobody Wed Mar 5 01:10:34 2014 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 88D931A0267 for ; Wed, 5 Mar 2014 01:10:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.148 X-Spam-Level: X-Spam-Status: No, score=-1.148 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, 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 6t6zy7vQbTHP for ; Wed, 5 Mar 2014 01:10:30 -0800 (PST) Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) by ietfa.amsl.com (Postfix) with ESMTP id C89E21A01C7 for ; Wed, 5 Mar 2014 01:10:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1394010627; x=1425546627; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=TqRlj0r7ODGryM6aEoKY3BeECzQ8V8Nz4/6SDmGn1wE=; b=Wgk1gpAG0A3TAoL5WmoC+n6+GN2MMg+oCJfi1+zGM4MFE03voIinwtEi MroLyZ6usHFw6os29PllSS8Ju9XFev6c4bAeQAzkKZEFuNm9aY5/f4l5P jj0mHkEVoyoaswXdEyzmc8dFUGOEUYugT9ZFZut4Cd95vAaKICLvJHLJX Q=; X-IronPort-AV: E=Sophos;i="4.97,591,1389697200"; d="scan'208";a="237544810" X-Ironport-HAT: None - $RELAY-AUTH X-Ironport-Source: 31.133.167.82 - Outgoing - Outgoing-SSL Received: from dhcp-a752.meeting.ietf.org (HELO [31.133.167.82]) ([31.133.167.82]) by mx2-int.auckland.ac.nz with ESMTP; 05 Mar 2014 22:10:25 +1300 Message-ID: <5316E9FD.2030406@auckland.ac.nz> Date: Wed, 05 Mar 2014 22:10:21 +1300 From: Nevil Brownlee User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: eman@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/eman/Hn2i77zyLquNIAjB5Rr3k63yPwE Subject: [eman] Authentication for Constrained environments 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: Wed, 05 Mar 2014 09:10:32 -0000 Hi EMAN folk: If you're interested in this - and EMAN devices may well be a constrained environment - the ACE WG is meeting at IETF-89 at 0900 this morning. If you're not at the meeting, you could join the ACE list. Cheers, Nevil -- --------------------------------------------------------------------- Nevil Brownlee Computer Science Department | ITS Phone: +64 9 373 7599 x88941 The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand From nobody Wed Mar 5 09:03:50 2014 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 846FA1A0140 for ; Wed, 5 Mar 2014 09:03:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.948 X-Spam-Level: X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_56=0.6, RP_MATCHES_RCVD=-0.547, 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 zP_8txd9YsiK for ; Wed, 5 Mar 2014 09:03:43 -0800 (PST) Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) by ietfa.amsl.com (Postfix) with ESMTP id 16FD91A012A for ; Wed, 5 Mar 2014 09:03:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1394039020; x=1425575020; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=YfN3bAX0GkXRqtsubqC4PUVhoxH4XSy8vzIxfZHzScI=; b=F+m/dTxnm6yRKdYAZKfH+xIcy9LxmjSnQY+USHHKK7A9simBdi8k0gRB hhFs4YVK6W4XCT6R5DlJvruvjzSoP7nQzFD8BGAESbFTISgLVOkdS8gTU nRnIJ9xwRTeIc/ehJ3MbIrdJyH6UCfM6xfmt70qxaePD5uUlKLTq/vBql w=; X-IronPort-AV: E=Sophos;i="4.97,593,1389697200"; d="scan'208";a="237581288" X-Ironport-HAT: None - $RELAY-AUTH X-Ironport-Source: 31.133.167.82 - Outgoing - Outgoing-SSL Received: from dhcp-a752.meeting.ietf.org (HELO [31.133.167.82]) ([31.133.167.82]) by mx2-int.auckland.ac.nz with ESMTP; 06 Mar 2014 06:03:38 +1300 Message-ID: <531758DF.4070708@auckland.ac.nz> Date: Thu, 06 Mar 2014 06:03:27 +1300 From: Nevil Brownlee User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: eman@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/eman/J1psy-zizOrO83-sG0PeW8X-yu8 Subject: [eman] DRAFT minutes for our meeting at IETF-89 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: Wed, 05 Mar 2014 17:03:47 -0000 Hi all: Here is the first draft of the meeting minutes. Corrections and/or comments to the EMAN list please. Cheers, Nevil 1-para summary for EMAN meeting at IETF-89 The EMAN Framework draft is now with IESG, work progresses on our three MIB drafts. We expect to submit all three before IETF-90. That leaves the EMAN Applicability Statement; we discussed what's needed to complete that. Our target is to get this to WGLC soon after IETF-91. Two other drafts were presented, mailing list discussion is encouraged. Minutes of the EMAN meeting at IETF 89 in London, version 00 About 25 people attended the meeting + several on jabber Scribes: Nevil Brownlee, John Parello Jabber Scribe: Rolf Winter WG Status --------- - Rolf Winter commented that in Framework-15, "must" in "An Energy Object must be a member of a single Energy Management Domain" ought to be "MUST." - Framework-16 (with that change) is on IESG telechat agenda for 20 Mar 14 - All three MIB drafts completed WGLC by 24 Jan 14, to discussed in meeting - Applicability has been parked, will now be worked on Energy-aware- MIB -15 ------------------------- Presented by John Parello - Reviewed changes, reviewed issues with r/w MIB objects. - Chair guidance was "the MIB was developed using r/w, changing to r/o would require significant work, keep them as r/w." The meeting had clear consensus for r/w, our AD agreed with that; clear WG consensus is to use r/w objects for all three MIBs - This version is ready to submit Power and Energy Monitoring MIB -09 ----------------------------------- Presented by John Parello - IANA section was edited, but introduced errors in not making this an IANA-controlled MIB. This will be be resolved with a new version - New revision needed Battery MIB -11 ------------------------ Presented by Rolf Winter - Many open issues closed at -10 - John commented that batteryIdentifier should be "a general UUID, with the manufacturer model,serial and number being used to create the UUID." - Notification rate limiting is not in place for all monitoring values, this is hard to fix for batteryTemperatureNotification - New revision needed, with fixes to above issues Applicability Statement -04 --------------------------- Presented by Nevil Brownlee - Single slide from Mouli Chandramouli listed work still needed - Most of the text is already available, since it was culled from other drafts, or is in list discussions - Rolf suggested including a section on Energy Management Domains, explaining why the Framework uses "MUST be a member of a single Energy Management Domain;" he will provide text - New revision needed, aim for WGLC soon after IETF-90 Other Presentations ------------------- Network Proxy Protocol -02 -------------------------- Presented by Sangjin Jeong - Modified for IPv4, added DHCP operation - The chairs were not able to show two video clips for this presentation, URLs for them are given in this meeting's agenda - Rolf commented that Bonjour has a similar sleeping proxy - Continue to discuss on EMAN list Green Usage MIB -03 ------------------- Presented by Takuo Suganuma - Reviewed progress, added power estimation - Next will ink to EMAN MIB and Framework - Further discussion on EMAN list is welcome Next steps for EMAN ------------------- - Update milestones, goal is to submit the MIBs before IETF-90, and the Applicability Statement soon after that. That will complete the EMAN charter - WG will not close until all our drafts are through IESG - New work will not be added to our charter unless there is clear consensus for doing that. OpsArea WG would be a good place for such work The meeting finished at 1620. -- Nevil Brownlee (ISE), rfc-ise@rfc-editor.org -- --------------------------------------------------------------------- Nevil Brownlee Computer Science Department | ITS Phone: +64 9 373 7599 x88941 The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand From nobody Thu Mar 6 06:39:45 2014 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 988931A0428; Thu, 6 Mar 2014 06:39:39 -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 cSuflNSmbIaR; Thu, 6 Mar 2014 06:39:34 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB3C1A027D; Thu, 6 Mar 2014 06:39:34 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.1.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140306143934.24303.80999.idtracker@ietfa.amsl.com> Date: Thu, 06 Mar 2014 06:39:34 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/eman/Us37oambo75G_zht8wcJMkXqJ6Q Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-battery-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: Thu, 06 Mar 2014 14:39:39 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Energy Management Working Group of the IETF. Title : Definition of Managed Objects for Battery Monitoring Authors : Juergen Quittek Rolf Winter Thomas Dietz Filename : draft-ietf-eman-battery-mib-12.txt Pages : 34 Date : 2014-03-06 Abstract: This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines managed objects that provide information on the status of batteries in managed devices. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-battery-mib/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-battery-mib-12 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-eman-battery-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 nobody Fri Mar 7 02:22:54 2014 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 4D1E71A018F for ; Fri, 7 Mar 2014 02:22:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.149 X-Spam-Level: X-Spam-Status: No, score=-3.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547, 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 hqckc2cfFwMM for ; Fri, 7 Mar 2014 02:22:51 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id D3A871A017B for ; Fri, 7 Mar 2014 02:22:50 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 6E98C106FB4 for ; Fri, 7 Mar 2014 11:22:46 +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 eQypylMPukZL for ; Fri, 7 Mar 2014 11:22:46 +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 506AA106FAE for ; Fri, 7 Mar 2014 11:22:41 +0100 (CET) Received: from PALLENE.office.hd ([169.254.1.233]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Fri, 7 Mar 2014 11:22:41 +0100 From: Juergen Quittek To: "eman@ietf.org" Thread-Topic: [eman] I-D Action: draft-ietf-eman-battery-mib-12.txt Thread-Index: AQHPOUn1uIYC7shCEU+L/Wo/n415YZrVZZfQ Date: Fri, 7 Mar 2014 10:22:41 +0000 Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E877A789FE@PALLENE.office.hd> References: <20140306143934.24303.80999.idtracker@ietfa.amsl.com> In-Reply-To: <20140306143934.24303.80999.idtracker@ietfa.amsl.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 Archived-At: http://mailarchive.ietf.org/arch/msg/eman/tSSpwzI7c4R9vbKz11SRqReFnXs Subject: Re: [eman] I-D Action: draft-ietf-eman-battery-mib-12.txt 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, 07 Mar 2014 10:22:53 -0000 Dear all, This update addresses the comments received during WGLC. Below please find a list of changes compared to version -11.=20 If there are no problems with the way that issues raised=20 during WGLC have been addressed, then work on this draft=20 is done and we can request publication. Cheers, Juergen List of changes since version -11: 1. editorial changes improving readability, fixing a typo 2. Types of charge and capacity objects In Version -09 we changed the type of object batteryActualCharge=20 from Unsigned32 to Unsigned64TC in order to batteries with large capacity. This was fine, but there are other objects dealing with the same issue: - batteryDesignCapacity - batteryActualCapacity - batteryAlarmLowCharge - batteryAlarmLowCapacity They all are defined in units of milliampere hours. The new version uses Unsigned64TC for all these objects. 3. Compliance with ACPI ACPI uses two objects for identifying a battery: model no. and serial no.=20 The Battery MIB has just one object, the batteryIdentifier. We added text to the DESCRIPTION clause of object batteryIdentifier About how to embed the two ACPI objects into the single object. 4. Limiting notification rates For two notification we did not have rate limitations, the batteryTemperatureNotification and the batteryAgingNotification. We added text on this to the respective DESCRIPTION clauses and 5. Relaxing rate limitations=20 For notifications batteryLowNotification and batteryCritical Notification we had rate limitations in place, but these were too strict in some cases. We relaxed them adding text to the respective DESCRIPTION clauses. > -----Original Message----- > From: eman [mailto:eman-bounces@ietf.org] On Behalf Of internet- > drafts@ietf.org > Sent: Donnerstag, 6. M=E4rz 2014 15:40 > To: i-d-announce@ietf.org > Cc: eman@ietf.org > Subject: [eman] I-D Action: draft-ietf-eman-battery-mib-12.txt >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts direct= ories. > This draft is a work item of the Energy Management Working Group of the > IETF. >=20 > Title : Definition of Managed Objects for Battery Monit= oring > Authors : Juergen Quittek > Rolf Winter > Thomas Dietz > Filename : draft-ietf-eman-battery-mib-12.txt > Pages : 34 > Date : 2014-03-06 >=20 > Abstract: > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols in the Internet community. > In particular, it defines managed objects that provide information on > the status of batteries in managed devices. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-eman-battery-mib/ >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-eman-battery-mib-12 >=20 > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-battery-mib-12 >=20 >=20 > Please note that it may take a couple of minutes from the time of submiss= ion > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman From nobody Fri Mar 7 20:59:35 2014 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 180051A01F0 for ; Fri, 7 Mar 2014 20:59:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.447 X-Spam-Level: X-Spam-Status: No, score=-9.447 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, J_CHICKENPOX_56=0.6, RP_MATCHES_RCVD=-0.547, 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 zeW0Nu48tC72 for ; Fri, 7 Mar 2014 20:59:31 -0800 (PST) Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id 08FB81A0226 for ; Fri, 7 Mar 2014 20:59:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13161; q=dns/txt; s=iport; t=1394254767; x=1395464367; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Tl/fJ6UtmIH3oLRkBo0DUfon6bA9KfZ/4yDcfPOmCk0=; b=BpVCx1KhkT1PBsjxe9n2LOw773TRTx8PYjXbZljM5zfWt87JgRd8v6ih b9h3UnXKbAu8gSXWStdrBIJdD7pG1YKQ1fFAzDDSj7weOZxDidOV5jE12 EXD0ihjp3SGhiKFgilxWHT3MpjhBnccIWmR0C+cOTGBu5Hi8eexFXfGhS I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvoFAPCiGlOtJV2c/2dsb2JhbABRCQ6CNEQ7V4QkvQqBFRZ0giYBAQQBAQFrCw4CAgEIDjEHGwwLFBECBAENBYd5DdAXEwQEjW8NBwZKBAeEOASYRZIrgm4/gis X-IronPort-AV: E=Sophos; i="4.97,612,1389744000"; d="scan'208,217"; a="25873918" Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-1.cisco.com with ESMTP; 08 Mar 2014 04:59:26 +0000 Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s284xQ6l008909 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 8 Mar 2014 04:59:26 GMT Received: from xmb-rcd-x08.cisco.com ([169.254.8.10]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Fri, 7 Mar 2014 22:59:25 -0600 From: "Mouli Chandramouli (moulchan)" To: Nevil Brownlee , "eman@ietf.org" Thread-Topic: [eman] DRAFT minutes for our meeting at IETF-89 Thread-Index: AQHPOJTmxF3M1w4qekCZssHaGBWPVJrXZfaA Date: Sat, 8 Mar 2014 04:59:24 +0000 Message-ID: References: <531758DF.4070708@auckland.ac.nz> In-Reply-To: <531758DF.4070708@auckland.ac.nz> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-originating-ip: [10.65.35.76] Content-Type: multipart/alternative; boundary="_000_CF409FC823F16moulchanciscocom_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/eman/SWPvgpvfDOZTDLeopEoXvGArSIU Subject: Re: [eman] DRAFT minutes for our meeting at IETF-89 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, 08 Mar 2014 04:59:34 -0000 --_000_CF409FC823F16moulchanciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Nevil and Tom, There is one point I would like to mention. As of now, the title of the draft is - draft-ietf-eman-energy-aware-mib= -14 But the actual name of the MIB module is : (this name was feedback from = the WG). ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::=3D BEGIN energyObjectContextMIB MODULE-IDENTITY We did not change the name of the draft, since ID tracker would revert to d= raft.00 We request that the name of the draft would be consistent with the name of = MIB module, before it becomes an RFC. Thanks Mouli Thanks Mouli Hi all: Here is the first draft of the meeting minutes. Corrections and/or comment= s to the EMAN list please. Cheers, Nevil 1-para summary for EMAN meeting at IETF-89 The EMAN Framework draft is now with IESG, work progresses on our three MIB drafts. We expect to submit all three before IETF-90. That leaves the EMAN Applicability Statement; we discussed what's needed to complete that. Our target is to get this to WGLC soon after IETF-91. Two other drafts were presented, mailing list discussion is encouraged. Minutes of the EMAN meeting at IETF 89 in London, version 00 About 25 people attended the meeting + several on jabber Scribes: Nevil Brownlee, John Parello Jabber Scribe: Rolf Winter WG Status --------- - Rolf Winter commented that in Framework-15, "must" in "An Energy Object must be a member of a single Energy Management Domain" ought to be "MUST." - Framework-16 (with that change) is on IESG telechat agenda for 20 Mar 14 - All three MIB drafts completed WGLC by 24 Jan 14, to discussed in meeting - Applicability has been parked, will now be worked on Energy-aware- MIB -15 ------------------------- Presented by John Parello - Reviewed changes, reviewed issues with r/w MIB objects. - Chair guidance was "the MIB was developed using r/w, changing to r/o would require significant work, keep them as r/w." The meeting had clea= r consensus for r/w, our AD agreed with that; clear WG consensus is to use r/w objects for all three MIBs - This version is ready to submit Power and Energy Monitoring MIB -09 ----------------------------------- Presented by John Parello - IANA section was edited, but introduced errors in not making this an IANA-controlled MIB. This will be be resolved with a new version - New revision needed Battery MIB -11 ------------------------ Presented by Rolf Winter - Many open issues closed at -10 - John commented that batteryIdentifier should be "a general UUID, with the manufacturer model,serial and number being used to create the UUID." - Notification rate limiting is not in place for all monitoring values, this is hard to fix for batteryTemperatureNotification - New revision needed, with fixes to above issues Applicability Statement -04 --------------------------- Presented by Nevil Brownlee - Single slide from Mouli Chandramouli listed work still needed - Most of the text is already available, since it was culled from other drafts, or is in list discussions - Rolf suggested including a section on Energy Management Domains, explaining why the Framework uses "MUST be a member of a single Energy Management Domain;" he will provide text - New revision needed, aim for WGLC soon after IETF-90 Other Presentations ------------------- Network Proxy Protocol -02 -------------------------- Presented by Sangjin Jeong - Modified for IPv4, added DHCP operation - The chairs were not able to show two video clips for this presentation, URLs for them are given in this meeting's agenda - Rolf commented that Bonjour has a similar sleeping proxy - Continue to discuss on EMAN list Green Usage MIB -03 ------------------- Presented by Takuo Suganuma - Reviewed progress, added power estimation - Next will ink to EMAN MIB and Framework - Further discussion on EMAN list is welcome Next steps for EMAN ------------------- - Update milestones, goal is to submit the MIBs before IETF-90, and the Applicability Statement soon after that. That will complete the EMAN charter - WG will not close until all our drafts are through IESG - New work will not be added to our charter unless there is clear consensus for doing that. OpsArea WG would be a good place for such work The meeting finished at 1620. -- Nevil Brownlee (ISE), rfc-ise@rfc-editor.org -- --------------------------------------------------------------------- Nevil Brownlee Computer Science Department | ITS Phone: +64 9 373 7599 x88941 The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman --_000_CF409FC823F16moulchanciscocom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
Hi Nevil and Tom,

There is one point I would like to mention.  

As of now,  the title of the draft  is   - draft-i= etf-eman-energy-aware-mib-14

But the actual name of the MIB module is :  (this   name was= feedback from the WG). 
        ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::=3D BEGIN=20
     =20
        energyObjectContextMIB MODULE-IDENTITY 

We did not change t=
he name of the draft, since ID tracker would revert to draft.00

We request that the name of the draft would be consistent with the nam=
e of MIB module, before it becomes an RFC.





Thanks


Mouli





Thanks


Mouli


Hi all:

Here is the first draft of the meeting minutes.  Corrections= and/or comments
to the EMAN list please.

Cheers, Nevil


1-para summary for EMAN meeting at IETF-89

The EMAN Framework draft is now with IESG, work progresses on our
three MIB drafts.   We expect to submit all three before IET= F-90.
That leaves the EMAN Applicability Statement; we discussed what's
needed to complete that.  Our target is to get this to WGLC = soon
after IETF-91.  Two other drafts were presented, mailing lis= t
discussion is encouraged.


Minutes of the EMAN meeting at IETF 89 in London, version 00

About 25 people attended the meeting + several on jabber

Scribes: Nevil Brownlee, John Parello
Jabber Scribe: Rolf Winter

WG Status
---------
- Rolf Winter commented that in Framework-15, "must" in &quo= t;An Energy
   Object must be a member of a single Energy Management Dom= ain"
   ought to be "MUST."
- Framework-16 (with that change) is on IESG telechat agenda for 20 Ma= r 14
- All three MIB drafts completed WGLC by 24 Jan 14, to discussed in me= eting
- Applicability has been parked, will now be worked on

Energy-aware- MIB -15
-------------------------
Presented by John Parello
- Reviewed changes, reviewed issues with r/w MIB objects.
- Chair guidance was "the MIB was developed using r/w, changing t= o r/o
   would require significant work, keep them as r/w."&n= bsp; The meeting had clear
   consensus for r/w, our AD agreed with that; clear WG cons= ensus is to
   use r/w objects for all three MIBs
- This version is ready to submit

Power and Energy Monitoring MIB -09
-----------------------------------
Presented by John Parello
- IANA section was edited, but introduced errors in not making this
   an IANA-controlled MIB. This will be be resolved with a n= ew version
- New revision needed

Battery MIB -11
------------------------
Presented by Rolf Winter
- Many open issues closed at -10
- John commented that batteryIdentifier should be "a general UUID= , with
   the manufacturer model,serial and number being used to cr= eate the UUID."
- Notification rate limiting is not in place for all monitoring values= ,
   this is hard to fix for batteryTemperatureNotification
- New revision needed, with fixes to above issues

Applicability Statement -04
---------------------------
Presented by Nevil Brownlee
- Single slide from Mouli Chandramouli listed work still needed
- Most of the text is already available, since it was culled from othe= r
   drafts, or is in list discussions
- Rolf suggested including a section on Energy Management Domains,
   explaining why the Framework uses "MUST be a member = of a single Energy
   Management Domain;" he will provide text
- New revision needed, aim for WGLC soon after IETF-90

Other Presentations
-------------------

Network Proxy Protocol -02
--------------------------
Presented by Sangjin Jeong
- Modified for IPv4, added DHCP operation
- The chairs were not able to show two video clips for this presentati= on,
   URLs for them are given in this meeting's agenda
- Rolf commented that Bonjour has a similar sleeping proxy
- Continue to discuss on EMAN list

Green Usage MIB -03
-------------------
Presented by Takuo Suganuma
- Reviewed progress, added power estimation
- Next will ink to EMAN MIB and Framework
- Further discussion on EMAN list is welcome

Next steps for EMAN
-------------------
- Update milestones, goal is to submit the MIBs before IETF-90,
   and the Applicability Statement soon after that. &nb= sp;That will complete
   the EMAN charter
- WG will not close until all our drafts are through IESG
- New work will not be added to our charter unless there is clear
   consensus for doing that.  OpsArea WG would be = a good place for
   such work

The meeting finished at 1620.

--
Nevil Brownlee (ISE), rfc-is= e@rfc-editor.org

--
---------------------------------------------------------------------<= /div>
  Nevil Brownlee       &n= bsp;            = ;Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941    &n= bsp;        The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auc= kland 1142, New Zealand

_______________________________________________
eman mailing list

--_000_CF409FC823F16moulchanciscocom_-- From nobody Wed Mar 12 10:57:44 2014 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 5E7771A074D for ; Wed, 12 Mar 2014 10:57:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.449 X-Spam-Level: X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, 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 UPEcMCGkoteM for ; Wed, 12 Mar 2014 10:57:37 -0700 (PDT) Received: from mailbox.snmp.com (mailbox.snmp.com [192.147.142.80]) by ietfa.amsl.com (Postfix) with ESMTP id 883C61A0729 for ; Wed, 12 Mar 2014 10:57:32 -0700 (PDT) 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 NAA23036; Wed, 12 Mar 2014 13:57:16 -0400 (EDT) Received: (from luchuk@localhost) by adminfs.snmp.com (8.9.3p2-20030922/snmpclient.mc-990525) id NAA24671; Wed, 12 Mar 2014 13:57:06 -0400 (EDT) Date: Wed, 12 Mar 2014 13:57:06 -0400 (EDT) From: Alan Luchuk Message-Id: <201403121757.NAA24671@adminfs.snmp.com> To: eman@ietf.org Archived-At: http://mailarchive.ietf.org/arch/msg/eman/d8ligeMDyDn291obuVXNEmdac44 Subject: [eman] Comments on draft-ietf-eman-battery-mib-12 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: Wed, 12 Mar 2014 17:57:42 -0000 Hello, Here are comments on draft-ietf-eman-battery-mib-12.txt. I think only the last issue in the list may be a true problem; it is easily fixed. There is one technical issue that might be worthy of further consideration. The rest are these are typos or grammatical nits. I hope these are helpful to the EMAN WG. Regards, --Alan Page 3, Introduction (typo) ---------------------------- The second paragraph from the bottom contains the sentence: Many battery-driven devices have existing instrumentation for monitoring the battery status, because this is already needed for local control of the battery by the device. I think the comma is not needed; perhaps the sentence should read: Many battery-driven devices have existing instrumentation for monitoring the battery status because this is already needed for local control of the battery by the device. Page 4, Introduction (typo) --------------------------- The first paragraph from the top contains the sentence: The former allows tracing a battery and allows continuous monitoring even if the battery is e.g. installed in another device." I think the "e.g." is not needed; perhaps the sentence should read: The former allows tracing a battery and allows continuous monitoring even if the battery is installed in another device." Page 5, MIB Module Structure (grammer) -------------------------------------- The third paragraph from the top reads: If batteries are replaced, and the replacing battery uses the same ^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^ physical connector as the replaced battery, then the replacing battery SHOULD be indexed with the same value of object entPhysicalIndex as the replaced battery. In the first clause the subject is plural, in the second clause, the subject is singular. Perhaps the sentence should read: If a battery is replaced, and the replacing battery uses the same ^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^ physical connector as the replaced battery, then the replacing battery SHOULD be indexed with the same value of object entPhysicalIndex as the replaced battery. The same text appears in the description clause for the batteryTable on page 10. Page 5, MIB Module Structure (nit) ---------------------------------- The last paragraph on page 5 and the first paragraph on page 6 mention three groups of objects: objects with OIDs ending with 1-10, objects with OIDs ending with 11-18, and objects with OIDs ending with 20-25. The batteryCellIdentifier object ends with SID 19 and is not included in any of the three groups. Page 13, DESCRIPTION for batteryTechnology ------------------------------------------ The DESCRIPTION for batteryTechnology reads: "This object indicates the technology used by the battery. Numbers identifying battery types are registered at IANA. A current list of assignments can be found at . Value 0 (unknown) MUST be used if the type of battery cannot be determined. Value 1 (other) can be used if the battery type is known but not one of the types already registered at IANA." I tried to access the URL shown above, and could not. I assume it has not yet been created by IANA. Also, the values and enumeration names do not match the table shown in section 3.2 on page 7. I think this part of the DESCRIPTION should read: "Value 1 (unknown) MUST be used if the type of battery cannot be determined. Value 2 (other) can be used if the battery type is known but not one of the types already registered at IANA." Page 14, batteryMaxChargingCurrent (possible technical issue) ------------------------------------------------------------- Between drafts -11 and -12, the battery capacity values were increased in size from an Unsigned32 to an Unsigned64TC to accomodate very high capacity batteries. For batteries with a capacity large enough to require an Unsigned64TC is it sufficient to have a batteryMaxChargingCurrent limited to an Unsigned32? For example, if a battery is ever built that has a capacity that must be reported with the maximum value of the Unsigned64TC batteryDesignCapacity, the maximum allowed charging current for that battery might be too large to report with the Unsigned32 batteryMaxChargingCurrent. This same issue might apply to the batteryTrickleChargingCurrent MIB object on Page 14, as well as the batteryActualCurrent MIB object on Page 19. Not sure what the best course of action is here. Page 16, DESCRIPTION for batteryChargingCycleCount -------------------------------------------------- The second paragraph of the DESCRIPTION for batteryChargingCycleCount reads: "For batteries of type primary(1) the value of this object is always 0." This enumeration name/number does not match the enumerated values listed for the batteryType MIB object on page 12/13: batteryType OBJECT-TYPE SYNTAX INTEGER { unknown(1), other(2), primary(3), rechargeable(4), capacitor(5) } Also, I think the charging cycle count only applies to a batteryType of rechargeable(4), so would rewording this second paragraph make sense? "For batteries of any type other than rechargeable(4), the value of this object is always 0." Page 17, DESCRIPTION for batteryChargingAdminState (nit) -------------------------------------------------------- The first sentence of the first paragraph of the DESCRIPTION for batteryChargingAdminState reads: "The value of this object indicates the desired status of the charging state of the battery. Perhaps the following text is a little more concise: "The value of this object indicates the desired charging state of the battery. Page 28, batteryTemperatureNotification (problem) ------------------------------------------------- OBJECT batteryTemperatureNotification MIN-ACCESS read-only DESCRIPTION "A compliant implementation is not required to support set operations to this object." A MIB checker squawked about batteryTemperatureNotification is not defined as an OBJECT-TYPE. Should this be removed from the BATTERY-MIB? From nobody Fri Mar 21 10:01:17 2014 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 B5E481A09E1 for ; Fri, 21 Mar 2014 10:01:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.948 X-Spam-Level: X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_56=0.6, RP_MATCHES_RCVD=-0.547, 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 2oX7eu-F8m0j for ; Fri, 21 Mar 2014 10:00:51 -0700 (PDT) Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) by ietfa.amsl.com (Postfix) with ESMTP id 2CDF91A09C1 for ; Fri, 21 Mar 2014 10:00:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1395421242; x=1426957242; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=A0PbUJuOpAgyUurxL8rRjEeV4ElKLHEuXnQ53Y88mTk=; b=hDViR26Of5fjxoegLdfZ9ZEAYxjueGwY9oIkK1JdObbWn1CqqydI+TWr rXkbDiuAcw7WS6V0aLrEOj9koDzQEf70cCOCjc5Vpkj9oFOhxfx3oszMp T8hJ7ryIr8p5VAX14EprfiBRB7UgjW9Ft0pZgfFcVRdZKOwDQLGoIn/DZ U=; X-IronPort-AV: E=Sophos;i="4.97,704,1389697200"; d="scan'208";a="241662771" X-Ironport-HAT: None - $RELAY-AUTH X-Ironport-Source: 192.172.226.43 - Outgoing - Outgoing-SSL Received: from dyn43.caida.org (HELO [192.172.226.43]) ([192.172.226.43]) by mx2-int.auckland.ac.nz with ESMTP; 22 Mar 2014 06:00:40 +1300 Message-ID: <532C7037.7010002@auckland.ac.nz> Date: Sat, 22 Mar 2014 06:00:39 +1300 From: Nevil Brownlee User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: "Mouli Chandramouli (moulchan)" , "eman@ietf.org" References: <531758DF.4070708@auckland.ac.nz> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/eman/2TxnM9d9TAWCWlFV_4Un0nlIJ3c Subject: Re: [eman] DRAFT minutes for our meeting at IETF-89 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, 21 Mar 2014 17:01:07 -0000 Hi Mouli: I agree that this is sensible. I think the best way to make sure it happens will be for the Document Shepherd (probably Tom) should include the 'please change title when published' request in the Shepherd write-ip. Cheers, Nevil On 03/08/2014 05:59 PM, Mouli Chandramouli (moulchan) wrote: > Hi Nevil and Tom, > > There is one point I would like to mention. > > As of now, the title of the draft is - draft-ietf-eman-energy-aware-mib-14 > > But the actual name of the MIB module is : (this name was feedback from the WG). > > ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::= BEGIN > > energyObjectContextMIB MODULE-IDENTITY > > > We did not change the name of the draft, since ID tracker would revert to draft.00 > > We request that the name of the draft would be consistent with the name of MIB module, before it becomes an RFC. > > > Thanks > > Mouli > > > Thanks > > Mouli > > > Hi all: > > Here is the first draft of the meeting minutes. Corrections and/or comments > to the EMAN list please. > > Cheers, Nevil > > > 1-para summary for EMAN meeting at IETF-89 > > The EMAN Framework draft is now with IESG, work progresses on our > three MIB drafts. We expect to submit all three before IETF-90. > That leaves the EMAN Applicability Statement; we discussed what's > needed to complete that. Our target is to get this to WGLC soon > after IETF-91. Two other drafts were presented, mailing list > discussion is encouraged. > > > Minutes of the EMAN meeting at IETF 89 in London, version 00 > > About 25 people attended the meeting + several on jabber > > Scribes: Nevil Brownlee, John Parello > Jabber Scribe: Rolf Winter > > WG Status > --------- > - Rolf Winter commented that in Framework-15, "must" in "An Energy > Object must be a member of a single Energy Management Domain" > ought to be "MUST." > - Framework-16 (with that change) is on IESG telechat agenda for 20 Mar 14 > - All three MIB drafts completed WGLC by 24 Jan 14, to discussed in meeting > - Applicability has been parked, will now be worked on > > Energy-aware- MIB -15 > ------------------------- > Presented by John Parello > - Reviewed changes, reviewed issues with r/w MIB objects. > - Chair guidance was "the MIB was developed using r/w, changing to r/o > would require significant work, keep them as r/w." The meeting had clear > consensus for r/w, our AD agreed with that; clear WG consensus is to > use r/w objects for all three MIBs > - This version is ready to submit > > Power and Energy Monitoring MIB -09 > ----------------------------------- > Presented by John Parello > - IANA section was edited, but introduced errors in not making this > an IANA-controlled MIB. This will be be resolved with a new version > - New revision needed > > Battery MIB -11 > ------------------------ > Presented by Rolf Winter > - Many open issues closed at -10 > - John commented that batteryIdentifier should be "a general UUID, with > the manufacturer model,serial and number being used to create the UUID." > - Notification rate limiting is not in place for all monitoring values, > this is hard to fix for batteryTemperatureNotification > - New revision needed, with fixes to above issues > > Applicability Statement -04 > --------------------------- > Presented by Nevil Brownlee > - Single slide from Mouli Chandramouli listed work still needed > - Most of the text is already available, since it was culled from other > drafts, or is in list discussions > - Rolf suggested including a section on Energy Management Domains, > explaining why the Framework uses "MUST be a member of a single Energy > Management Domain;" he will provide text > - New revision needed, aim for WGLC soon after IETF-90 > > Other Presentations > ------------------- > > Network Proxy Protocol -02 > -------------------------- > Presented by Sangjin Jeong > - Modified for IPv4, added DHCP operation > - The chairs were not able to show two video clips for this presentation, > URLs for them are given in this meeting's agenda > - Rolf commented that Bonjour has a similar sleeping proxy > - Continue to discuss on EMAN list > > Green Usage MIB -03 > ------------------- > Presented by Takuo Suganuma > - Reviewed progress, added power estimation > - Next will ink to EMAN MIB and Framework > - Further discussion on EMAN list is welcome > > Next steps for EMAN > ------------------- > - Update milestones, goal is to submit the MIBs before IETF-90, > and the Applicability Statement soon after that. That will complete > the EMAN charter > - WG will not close until all our drafts are through IESG > - New work will not be added to our charter unless there is clear > consensus for doing that. OpsArea WG would be a good place for > such work > > The meeting finished at 1620. > > -- > Nevil Brownlee (ISE), rfc-ise@rfc-editor.org > > -- > --------------------------------------------------------------------- > Nevil Brownlee Computer Science Department | ITS > Phone: +64 9 373 7599 x88941 The University of Auckland > FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > > -- --------------------------------------------------------------------- Nevil Brownlee Computer Science Department | ITS Phone: +64 9 373 7599 x88941 The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand From nobody Fri Mar 21 10:04:52 2014 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 A83231A098A for ; Fri, 21 Mar 2014 10:04:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.847 X-Spam-Level: X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_56=0.6, RP_MATCHES_RCVD=-0.547] 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 UdkmCyukaO-j for ; Fri, 21 Mar 2014 10:04:45 -0700 (PDT) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 5F04E1A08ED for ; Fri, 21 Mar 2014 10:04:45 -0700 (PDT) Received: from [192.168.1.103] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 9F10E273DCD4; Fri, 21 Mar 2014 13:04:35 -0400 (EDT) Content-Type: multipart/signed; boundary="Apple-Mail=_F7CD2BCA-3CA0-40BD-9D98-164AD7ECAEA8"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Thomas Nadeau In-Reply-To: <532C7037.7010002@auckland.ac.nz> Date: Fri, 21 Mar 2014 13:04:34 -0400 Message-Id: References: <531758DF.4070708@auckland.ac.nz> <532C7037.7010002@auckland.ac.nz> To: Nevil Brownlee X-Mailer: Apple Mail (2.1874) Archived-At: http://mailarchive.ietf.org/arch/msg/eman/z3v9OWkDn-EXVdhEN-6frllfkWM Cc: "eman@ietf.org" Subject: Re: [eman] DRAFT minutes for our meeting at IETF-89 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, 21 Mar 2014 17:04:48 -0000 --Apple-Mail=_F7CD2BCA-3CA0-40BD-9D98-164AD7ECAEA8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Yes, that is the best way to handle this.=20 --Tom On Mar 21, 2014:1:00 PM, at 1:00 PM, Nevil Brownlee = wrote: >=20 > Hi Mouli: >=20 > I agree that this is sensible. I think the best way to > make sure it happens will be for the Document Shepherd (probably > Tom) should include the 'please change title when published' > request in the Shepherd write-ip. >=20 > Cheers, Nevil >=20 >=20 > On 03/08/2014 05:59 PM, Mouli Chandramouli (moulchan) wrote: >> Hi Nevil and Tom, >>=20 >> There is one point I would like to mention. >>=20 >> As of now, the title of the draft is - = draft-ietf-eman-energy-aware-mib-14 >>=20 >> But the actual name of the MIB module is : (this name was feedback = from the WG). >>=20 >> ENERGY-OBJECT-CONTEXT-MIB DEFINITIONS ::=3D BEGIN >>=20 >> energyObjectContextMIB MODULE-IDENTITY >>=20 >>=20 >> We did not change the name of the draft, since ID tracker would = revert to draft.00 >>=20 >> We request that the name of the draft would be consistent with the = name of MIB module, before it becomes an RFC. >>=20 >>=20 >> Thanks >>=20 >> Mouli >>=20 >>=20 >> Thanks >>=20 >> Mouli >>=20 >>=20 >> Hi all: >>=20 >> Here is the first draft of the meeting minutes. Corrections and/or = comments >> to the EMAN list please. >>=20 >> Cheers, Nevil >>=20 >>=20 >> 1-para summary for EMAN meeting at IETF-89 >>=20 >> The EMAN Framework draft is now with IESG, work progresses on our >> three MIB drafts. We expect to submit all three before IETF-90. >> That leaves the EMAN Applicability Statement; we discussed what's >> needed to complete that. Our target is to get this to WGLC soon >> after IETF-91. Two other drafts were presented, mailing list >> discussion is encouraged. >>=20 >>=20 >> Minutes of the EMAN meeting at IETF 89 in London, version 00 >>=20 >> About 25 people attended the meeting + several on jabber >>=20 >> Scribes: Nevil Brownlee, John Parello >> Jabber Scribe: Rolf Winter >>=20 >> WG Status >> --------- >> - Rolf Winter commented that in Framework-15, "must" in "An Energy >> Object must be a member of a single Energy Management Domain" >> ought to be "MUST." >> - Framework-16 (with that change) is on IESG telechat agenda for 20 = Mar 14 >> - All three MIB drafts completed WGLC by 24 Jan 14, to discussed in = meeting >> - Applicability has been parked, will now be worked on >>=20 >> Energy-aware- MIB -15 >> ------------------------- >> Presented by John Parello >> - Reviewed changes, reviewed issues with r/w MIB objects. >> - Chair guidance was "the MIB was developed using r/w, changing to = r/o >> would require significant work, keep them as r/w." The meeting = had clear >> consensus for r/w, our AD agreed with that; clear WG consensus is = to >> use r/w objects for all three MIBs >> - This version is ready to submit >>=20 >> Power and Energy Monitoring MIB -09 >> ----------------------------------- >> Presented by John Parello >> - IANA section was edited, but introduced errors in not making this >> an IANA-controlled MIB. This will be be resolved with a new = version >> - New revision needed >>=20 >> Battery MIB -11 >> ------------------------ >> Presented by Rolf Winter >> - Many open issues closed at -10 >> - John commented that batteryIdentifier should be "a general UUID, = with >> the manufacturer model,serial and number being used to create the = UUID." >> - Notification rate limiting is not in place for all monitoring = values, >> this is hard to fix for batteryTemperatureNotification >> - New revision needed, with fixes to above issues >>=20 >> Applicability Statement -04 >> --------------------------- >> Presented by Nevil Brownlee >> - Single slide from Mouli Chandramouli listed work still needed >> - Most of the text is already available, since it was culled from = other >> drafts, or is in list discussions >> - Rolf suggested including a section on Energy Management Domains, >> explaining why the Framework uses "MUST be a member of a single = Energy >> Management Domain;" he will provide text >> - New revision needed, aim for WGLC soon after IETF-90 >>=20 >> Other Presentations >> ------------------- >>=20 >> Network Proxy Protocol -02 >> -------------------------- >> Presented by Sangjin Jeong >> - Modified for IPv4, added DHCP operation >> - The chairs were not able to show two video clips for this = presentation, >> URLs for them are given in this meeting's agenda >> - Rolf commented that Bonjour has a similar sleeping proxy >> - Continue to discuss on EMAN list >>=20 >> Green Usage MIB -03 >> ------------------- >> Presented by Takuo Suganuma >> - Reviewed progress, added power estimation >> - Next will ink to EMAN MIB and Framework >> - Further discussion on EMAN list is welcome >>=20 >> Next steps for EMAN >> ------------------- >> - Update milestones, goal is to submit the MIBs before IETF-90, >> and the Applicability Statement soon after that. That will = complete >> the EMAN charter >> - WG will not close until all our drafts are through IESG >> - New work will not be added to our charter unless there is clear >> consensus for doing that. OpsArea WG would be a good place for >> such work >>=20 >> The meeting finished at 1620. >>=20 >> -- >> Nevil Brownlee (ISE), = rfc-ise@rfc-editor.org >>=20 >> -- >> --------------------------------------------------------------------- >> Nevil Brownlee Computer Science Department | ITS >> Phone: +64 9 373 7599 x88941 The University of Auckland >> FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand >>=20 >> _______________________________________________ >> eman mailing list >> eman@ietf.org >> https://www.ietf.org/mailman/listinfo/eman >>=20 >>=20 >=20 >=20 > --=20 > --------------------------------------------------------------------- > Nevil Brownlee Computer Science Department | ITS > Phone: +64 9 373 7599 x88941 The University of Auckland > FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand >=20 > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman >=20 --Apple-Mail=_F7CD2BCA-3CA0-40BD-9D98-164AD7ECAEA8 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 iQIcBAEBCgAGBQJTLHEiAAoJEPcO+I7eiUJZSmgP/jelhM+FPGuSeSy4nqqLlUU1 KSFfJuoQs5ve5Bj1Re65v/ocivEBLjEIP/NYKQDa3IDKxmBNLRoOkGTdWzgj0kld kuZTm/5jnPhnGuTsdlWRCD+95EMnzsgzNjKz2PHcpSWR9MEzt+KBMUygc88eA4pS f2SeC4Sk/KJ3SQL6hmnv9rtyV4OBIwkj1kDdj2VZk6snu1f7ePqQEHI2E6Y1LSMu Ow8Ig6KG5gD90p0yREt065ZgxwVc/vC8MTH6ZUosb6YSwciaU95Aoe6l1ZmEBgus zelRVlnYXRgg2qxMoZI8bJl6HwpQHL4n2/cnqa3D2VKUvRgI479vENQ5nq76Iika aB2Vnzv/ElGpAJiZTUVHwt/sX85m3gGghsCzA2IZKoumLaynUP6g5e3SGZ7f/j8H QM30AfCbnxhqQCR0G+6VezrfPTFMs1Szqs0GH7I6GGE63TUI7c12hjax95wyK5hO 4OvVXTiZpOQ7pr2eWMuFPMpCnPemYSPqr6h3Kzb31qbJUt2Lwxar4ObCPR6Tj/N/ onNGkZvP+F21RlGLY58IvhNJL2DmmfuXNIaZf2vogQKxinv9GyWJSMQ/r4L5uwb1 vjlyYgbB+1eLGLriQpXXXaiyxQsVa7QpVe8SD2/aeDgIl68ZqnyXcQ0+M/Xrppc6 lJ+OVGJLPxfJMJCTOBxS =L2il -----END PGP SIGNATURE----- --Apple-Mail=_F7CD2BCA-3CA0-40BD-9D98-164AD7ECAEA8--