
From nobody Sat May  2 21:27:01 2015
Return-Path: <joelja@bogus.com>
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 32B631A0087 for <eman@ietfa.amsl.com>; Sat,  2 May 2015 21:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-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 iYfM5-QcSG3w for <eman@ietfa.amsl.com>; Sat,  2 May 2015 21:26:55 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 865841A0086 for <eman@ietf.org>; Sat,  2 May 2015 21:26:55 -0700 (PDT)
Received: from mb-aye.local ([64.88.227.134]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id t434Qijt021198 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 3 May 2015 04:26:52 GMT (envelope-from joelja@bogus.com)
To: Brad Schoening <brad.schoening@verizon.net>, eman@ietf.org
references: <20150423113547.27316.23286.idtracker@ietfa.amsl.com> <D15EEB57.40C72%moulchan@cisco.com> <553DA67B.5030504@verizon.net>
From: joel jaeggli <joelja@bogus.com>
message-id: <5545A37D.3010107@bogus.com>
Date: Sat, 2 May 2015 21:26:37 -0700
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.0
mime-version: 1.0
in-reply-to: <553DA67B.5030504@verizon.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gRnmqBq13d49WBtuBb5ODkJmwWU01oGrL"
Archived-At: <http://mailarchive.ietf.org/arch/msg/eman/d0LLA1RPMnxmOQjfjFWXiXZIl9A>
Subject: Re: [eman] Brian Haberman's Discuss on draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMMENT)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 May 2015 04:27:00 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--gRnmqBq13d49WBtuBb5ODkJmwWU01oGrL
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 4/26/15 8:01 PM, Brad Schoening wrote:
> Mouli,
>=20
> Your comments address the intent for adding these use cases, but they
> don't respond to the critique of them, and therefore don't justify
> them.  Can you please respond to Pete & Alissa's questions.  Otherwise,=

> let's delete them as Bruce & I have suggested.

yeah I'm ok with that.

We will find I suspect in the future that the reporting wiill be used
across many of the applications it's not specifically tailored to
because it's sufficient for the expression to end users and other
management systems.

thanks for working on this final change.

joel

>=20
> Regards,
>=20
> Brad
>=20
> On 4/23/2015 9:45 PM, Mouli Chandramouli (moulchan) wrote:
>> Hi  Brian,
>>
>> Some of the specific use cases, you are referring had been provided as=

>> feedback to WG (email or meetings)  when the draft was draft was
>> presented.=20
>> It was felt that it would be useful  "unique, non-overlapping" set of
>> use cases (scenarios) of interest to energy management.=20
>> It may be that after the other MIB drafts have evolved over the years,=

>> it may be that we solve only a subset of use cases.=20
>>
>> Thanks
>> Mouli
>>
>>
>>
>>
>> From: Brian Haberman <brian@innovationslab.net
>> <mailto:brian@innovationslab.net>>
>> Date: Thursday, 23 April 2015 4:35 AM
>> To: The IESG <iesg@ietf.org <mailto:iesg@ietf.org>>
>> Cc: "eman-chairs@ietf.org <mailto:eman-chairs@ietf.org>"
>> <eman-chairs@ietf.org <mailto:eman-chairs@ietf.org>>, "eman@ietf.org
>> <mailto:eman@ietf.org>" <eman@ietf.org <mailto:eman@ietf.org>>
>> Subject: [eman] Brian Haberman's Discuss on
>> draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMMENT)=

>>
>>     Brian Haberman has entered the following ballot position for
>>     draft-ietf-eman-applicability-statement-10: Discuss
>>
>>     When responding, please keep the subject line intact and reply to =
all
>>     email addresses included in the To and CC lines. (Feel free to cut=

>>     this
>>     introductory paragraph, however.)
>>
>>
>>     Please refer to
>>     http://www.ietf.org/iesg/statement/discuss-criteria.html
>>     for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>>     The document, along with other ballot positions, can be found here=
:
>>     http://datatracker.ietf.org/doc/draft-ietf-eman-applicability-stat=
ement/
>>
>>
>>
>>     ------------------------------------------------------------------=
----
>>     DISCUSS:
>>     ------------------------------------------------------------------=
----
>>
>>     The draft still calls out some use cases that appear out of scope,=

>>     especially after the discussion around the EMAN MIB document. This=

>>     DISCUSS is a placeholder to address one of the author's suggestion=
 to
>>     delete: 1) the use cases in section 2.7 last paragraph (net-zero
>>     building), 2) 2.12 (off-grid devices), and 3) 2.14 (power capping)=
=2E
>>
>>
>>     ------------------------------------------------------------------=
----
>>     COMMENT:
>>     ------------------------------------------------------------------=
----
>>
>>     Thank you for addressing the issue of the document's status.
>>
>>
>>     _______________________________________________
>>     eman mailing list
>>     eman@ietf.org <mailto:eman@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/eman
>>
>>
>>
>> _______________________________________________
>> eman mailing list
>> eman@ietf.org
>> https://www.ietf.org/mailman/listinfo/eman
>=20
>=20
> --=20
> *Brad Schoening*
> Email:
>=20
>=20
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman
>=20



--gRnmqBq13d49WBtuBb5ODkJmwWU01oGrL
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlVFo30ACgkQ8AA1q7Z/VrKmWACfSU/o2woLCh7ZVK8V0qbZCv9C
f4IAn1FzR/JOmX7YGiU8f9PvWpFfKBLq
=U/Qo
-----END PGP SIGNATURE-----

--gRnmqBq13d49WBtuBb5ODkJmwWU01oGrL--


From nobody Mon May  4 15:55:07 2015
Return-Path: <iesg-secretary@ietf.org>
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 18BD11A894C; Mon,  4 May 2015 15:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v8vdBWU5SWSJ; Mon,  4 May 2015 15:55:03 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 777A01A8960; Mon,  4 May 2015 15:54:57 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.2.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150504225457.20903.352.idtracker@ietfa.amsl.com>
Date: Mon, 04 May 2015 15:54:57 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/eman/8bXl7G67E9NinP4JIZooa3K8AGs>
Cc: eman mailing list <eman@ietf.org>, eman chair <eman-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [eman] Protocol Action: 'Definition of Managed Objects for Battery Monitoring' to Proposed Standard (draft-ietf-eman-battery-mib-20.txt)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 May 2015 22:55:05 -0000

The IESG has approved the following document:
- 'Definition of Managed Objects for Battery Monitoring'
  (draft-ietf-eman-battery-mib-20.txt) as Proposed Standard

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

The IESG contact persons are Benoit Claise and Joel Jaeggli.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-eman-battery-mib/





Technical Summary

This document defines a portion of the Management Information Base
(MIB) for managed objects that provide information on the status of
batteries in managed devices.

According to the framework for energy management it is an Energy
Managed Object, so MIB modules such as the Power and Energy
Monitoring MIB could in principle be implemented for batteries.  The
Battery MIB extends the more generic aspects of energy management by
adding battery-specific information.  Amongst other things, the
Battery MIB enables the monitoring of:
 - the current charge of a battery,
 - the age of a battery (charging cycles),
 - the state of a battery (e.g. being re-charged),
 - last usage of a battery,
 - maximum energy provided by a battery (remaining and total capacity).

Working Group Summary

Version -01 of the draft was published in April 2011.
New versions were published about every three months from then
until version -11 in early January 2014.

Document Quality

Version -11 had its WG Last Call from 10 to 24 January 2014;
as part of that it was reviewed by the MIB-Doctors.  Several reviews
were received from the EMAN list, as well as a list of
changes and improvements from the MIB Doctors.
The authors have modified the draft in response to that feedback; 
we believe that the current (-12) version has resolved all the 
issues.  That discussion took place on the EMAN list through March
2014.

Personnel

Document Shepherd:         Nevil Brownlee
Responsible Area Director: Joel Jaegli


From nobody Mon May 11 20:34:33 2015
Return-Path: <brad.schoening@verizon.net>
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 1AB031A0065 for <eman@ietfa.amsl.com>; Mon, 11 May 2015 20:34:32 -0700 (PDT)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, T_RP_MATCHES_RCVD=-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 F8AyaA294MuZ for <eman@ietfa.amsl.com>; Mon, 11 May 2015 20:34:30 -0700 (PDT)
Received: from vms173021pub.verizon.net (vms173021pub.verizon.net [206.46.173.21]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE5DF1A0063 for <eman@ietf.org>; Mon, 11 May 2015 20:34:28 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_99ian+iqfXzfV+9ELTmDwA)"
Received: from [192.168.1.4] ([71.187.162.161]) by vms173021.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0NO7008BMWL26MD0@vms173021.mailsrvcs.net> for eman@ietf.org; Mon, 11 May 2015 22:34:15 -0500 (CDT)
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.1 cv=AawGxMSu c=1 sm=1 tr=0	a=7OEOyNKZuZM57qySakjcRQ==:117 a=naziTCeN6agA:10 a=o1OHuDzbAAAA:8	a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=h1PgugrvaO0A:10	a=r77TgQKjGQsHNAKrUKIA:9 a=9iDbn-4jx3cA:10 a=cKsnjEOsciEA:10 a=gZbpxnkM3yUA:10 a=wnRk2I__AAAA:8 a=48vgC7mUAAAA:8	a=lyIImqxFjPhcPLHMGGkA:9 a=RlnwBTcekcMf97DX:21 a=ZqmyuOEECryjqqoz:21	a=pILNOxqGKmIA:10 a=mYAOWqAtFUkA:10 a=AUd_NHdVAAAA:8	a=DZwRA8OoM96Mk-iLaGQA:9 a=WLL1Tre_MRvQZEpM:21 a=Sa85J-5C7jj_eikw:21	a=eaQZg1OVPp2qiH88:21 a=_W_S_7VecoQA:10
Message-id: <5551744E.5060309@verizon.net>
Date: Mon, 11 May 2015 23:32:30 -0400
From: Brad Schoening <brad.schoening@verizon.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
To: eman@ietf.org, "Mouli Chandramouli (moulchan)" <moulchan@cisco.com>
References: <20150423113547.27316.23286.idtracker@ietfa.amsl.com> <D15EEB57.40C72%moulchan@cisco.com> <553DA67B.5030504@verizon.net>
In-reply-to: <553DA67B.5030504@verizon.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/eman/wuP-OiqxL_5-7tw2_egGanelZ_c>
Subject: [eman] 2nd try: Brian Haberman's Discuss on draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMMENT)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2015 03:34:32 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_99ian+iqfXzfV+9ELTmDwA)
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT

Hi Mouli,

Just wondering if you plan further updates to the applicability 
statement draft responding to the concerns raised, or if you would be ok 
deleting these specific use cases as not really being unique and 
non-overlapping.

Regards,

Brad

On 4/26/2015 11:01 PM, Brad Schoening wrote:
> Mouli,
>
> Your comments address the intent for adding these use cases, but they 
> don't respond to the critique of them, and therefore don't justify 
> them.  Can you please respond to Pete & Alissa's questions.  
> Otherwise, let's delete them as Bruce & I have suggested.
>
> Regards,
>
> Brad
>
> On 4/23/2015 9:45 PM, Mouli Chandramouli (moulchan) wrote:
>> Hi  Brian,
>>
>> Some of the specific use cases, you are referring had been provided 
>> as feedback to WG (email or meetings)  when the draft was draft was 
>> presented.
>> It was felt that it would be useful  "unique, non-overlapping" set of 
>> use cases (scenarios) of interest to energy management.
>> It may be that after the other MIB drafts have evolved over the 
>> years, it may be that we solve only a subset of use cases.
>>
>> Thanks
>> Mouli
>>
>>
>>
>>
>> From: Brian Haberman <brian@innovationslab.net 
>> <mailto:brian@innovationslab.net>>
>> Date: Thursday, 23 April 2015 4:35 AM
>> To: The IESG <iesg@ietf.org <mailto:iesg@ietf.org>>
>> Cc: "eman-chairs@ietf.org <mailto:eman-chairs@ietf.org>" 
>> <eman-chairs@ietf.org <mailto:eman-chairs@ietf.org>>, "eman@ietf.org 
>> <mailto:eman@ietf.org>" <eman@ietf.org <mailto:eman@ietf.org>>
>> Subject: [eman] Brian Haberman's Discuss on 
>> draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMMENT)
>>
>>     Brian Haberman has entered the following ballot position for
>>     draft-ietf-eman-applicability-statement-10: Discuss
>>
>>     When responding, please keep the subject line intact and reply to all
>>     email addresses included in the To and CC lines. (Feel free to
>>     cut this
>>     introductory paragraph, however.)
>>
>>
>>     Please refer to
>>     http://www.ietf.org/iesg/statement/discuss-criteria.html
>>     for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>>     The document, along with other ballot positions, can be found here:
>>     http://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/
>>
>>
>>
>>     ----------------------------------------------------------------------
>>     DISCUSS:
>>     ----------------------------------------------------------------------
>>
>>     The draft still calls out some use cases that appear out of scope,
>>     especially after the discussion around the EMAN MIB document. This
>>     DISCUSS is a placeholder to address one of the author's suggestion to
>>     delete: 1) the use cases in section 2.7 last paragraph (net-zero
>>     building), 2) 2.12 (off-grid devices), and 3) 2.14 (power capping).
>>
>>
>>     ----------------------------------------------------------------------
>>     COMMENT:
>>     ----------------------------------------------------------------------
>>
>>     Thank you for addressing the issue of the document's status.
>>
>>
>>     _______________________________________________
>>     eman mailing list
>>     eman@ietf.org <mailto:eman@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/eman
>>
>>
>>
>> _______________________________________________
>> eman mailing list
>> eman@ietf.org
>> https://www.ietf.org/mailman/listinfo/eman
>
>
> -- 
> *Brad Schoening*
> Email:


-- 
*Brad Schoening*
Email:

--Boundary_(ID_99ian+iqfXzfV+9ELTmDwA)
Content-type: text/html; charset=windows-1252
Content-transfer-encoding: 8BIT

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Mouli,<br>
      <br>
      Just wondering if you plan further updates to the applicability
      statement draft responding to the concerns raised, or if you would
      be ok deleting these specific use cases as not really being unique
      and non-overlapping.<br>
      <br>
      Regards,<br>
      <br>
      Brad<br>
      <br>
      On 4/26/2015 11:01 PM, Brad Schoening wrote:<br>
    </div>
    <blockquote cite="mid:553DA67B.5030504@verizon.net" type="cite">
      <meta content="text/html; charset=windows-1252"
        http-equiv="Content-Type">
      <div class="moz-cite-prefix">Mouli,<br>
        <br>
        Your comments address the intent for adding these use cases, but
        they don't respond to the critique of them, and therefore don't
        justify them.  Can you please respond to Pete &amp; Alissa's
        questions.  Otherwise, let's delete them as Bruce &amp; I have
        suggested.<br>
        <br>
        Regards,<br>
        <br>
        Brad<br>
        <br>
        On 4/23/2015 9:45 PM, Mouli Chandramouli (moulchan) wrote:<br>
      </div>
      <blockquote cite="mid:D15EEB57.40C72%25moulchan@cisco.com"
        type="cite">
        <meta http-equiv="Content-Type" content="text/html;
          charset=windows-1252">
        <div>Hi  Brian,</div>
        <div><br>
        </div>
        <div>Some of the specific use cases, you are referring had been
          provided as feedback to WG (email or meetings)  when the draft
          was draft was presented. </div>
        <div>It was felt that it would be useful  "unique,
          non-overlapping" set of use cases (scenarios) of interest to
          energy management. </div>
        <div>It may be that after the other MIB drafts have evolved over
          the years, it may be that we solve only a subset of use
          cases. </div>
        <div><br>
        </div>
        <div>Thanks</div>
        <div>Mouli</div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
        <span id="OLK_SRC_BODY_SECTION">
          <div style="font-family:Calibri; font-size:11pt;
            text-align:left; color:black; BORDER-BOTTOM: medium none;
            BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT:
            0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;
            BORDER-RIGHT: medium none; PADDING-TOP: 3pt"> <span
              style="font-weight:bold">From: </span>Brian Haberman &lt;<a
              moz-do-not-send="true"
              href="mailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;<br>
            <span style="font-weight:bold">Date: </span>Thursday, 23
            April 2015 4:35 AM<br>
            <span style="font-weight:bold">To: </span>The IESG &lt;<a
              moz-do-not-send="true" href="mailto:iesg@ietf.org">iesg@ietf.org</a>&gt;<br>
            <span style="font-weight:bold">Cc: </span>"<a
              moz-do-not-send="true" href="mailto:eman-chairs@ietf.org">eman-chairs@ietf.org</a>"
            &lt;<a moz-do-not-send="true"
              href="mailto:eman-chairs@ietf.org">eman-chairs@ietf.org</a>&gt;,

            "<a moz-do-not-send="true" href="mailto:eman@ietf.org">eman@ietf.org</a>"
            &lt;<a moz-do-not-send="true" href="mailto:eman@ietf.org">eman@ietf.org</a>&gt;<br>
            <span style="font-weight:bold">Subject: </span>[eman] Brian
            Haberman's Discuss on
            draft-ietf-eman-applicability-statement-10: (with DISCUSS
            and COMMENT)<br>
          </div>
          <div><br>
          </div>
          <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
            style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5;
            MARGIN:0 0 0 5;">
            <div>
              <div>
                <div>Brian Haberman has entered the following ballot
                  position for</div>
                <div>draft-ietf-eman-applicability-statement-10: Discuss</div>
                <div><br>
                </div>
                <div>When responding, please keep the subject line
                  intact and reply to all</div>
                <div>email addresses included in the To and CC lines.
                  (Feel free to cut this</div>
                <div>introductory paragraph, however.)</div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>Please refer to <a moz-do-not-send="true"
                    href="http://www.ietf.org/iesg/statement/discuss-criteria.html">
http://www.ietf.org/iesg/statement/discuss-criteria.html</a></div>
                <div>for more information about IESG DISCUSS and COMMENT
                  positions.</div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>The document, along with other ballot positions,
                  can be found here:</div>
                <div><a moz-do-not-send="true"
href="http://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/">http://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/</a></div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>----------------------------------------------------------------------</div>
                <div>DISCUSS:</div>
                <div>----------------------------------------------------------------------</div>
                <div><br>
                </div>
                <div>The draft still calls out some use cases that
                  appear out of scope,</div>
                <div>especially after the discussion around the EMAN MIB
                  document. This</div>
                <div>DISCUSS is a placeholder to address one of the
                  author's suggestion to</div>
                <div>delete: 1) the use cases in section 2.7 last
                  paragraph (net-zero</div>
                <div>building), 2) 2.12 (off-grid devices), and 3) 2.14
                  (power capping).</div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>----------------------------------------------------------------------</div>
                <div>COMMENT:</div>
                <div>----------------------------------------------------------------------</div>
                <div><br>
                </div>
                <div>Thank you for addressing the issue of the
                  document's status.</div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>_______________________________________________</div>
                <div>eman mailing list</div>
                <div><a moz-do-not-send="true"
                    href="mailto:eman@ietf.org">eman@ietf.org</a></div>
                <div><a moz-do-not-send="true"
                    href="https://www.ietf.org/mailman/listinfo/eman">https://www.ietf.org/mailman/listinfo/eman</a></div>
                <div><br>
                </div>
              </div>
            </div>
          </blockquote>
        </span> <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
eman mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:eman@ietf.org">eman@ietf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/eman">https://www.ietf.org/mailman/listinfo/eman</a>
</pre>
      </blockquote>
      <br>
      <br>
      <div class="moz-signature">-- <br>
        <b>Brad Schoening</b> <br>
        Email: </div>
    </blockquote>
    <br>
    <br>
    <div class="moz-signature">-- <br>
      <b>Brad Schoening</b>
      <br>
      Email: </div>
  </body>
</html>

--Boundary_(ID_99ian+iqfXzfV+9ELTmDwA)--


From nobody Tue May 12 03:07:00 2015
Return-Path: <moulchan@cisco.com>
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 BEA111A8770 for <eman@ietfa.amsl.com>; Tue, 12 May 2015 03:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level: 
X-Spam-Status: No, score=-14.5 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, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, T_RP_MATCHES_RCVD=-0.01, 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 s8f3VYHkGe1Z for <eman@ietfa.amsl.com>; Tue, 12 May 2015 03:06:55 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 656EC1A874D for <eman@ietf.org>; Tue, 12 May 2015 03:06:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12992; q=dns/txt; s=iport; t=1431425215; x=1432634815; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Mnr1VlueOSyOm+t9Hv7oBhc1VbJDSxoFJLiiD+COP/g=; b=OAlthppv7A/6pbRrpOZL7t6r977pEvlssrBQAbcYNFQXCK34j0wIiU7J wN6Jrq5MQ8eJnUpwj2ElOaFFrqvcEGJ4Q0G+Ecys9KxoGNHQJfwFtqW0U KReM3b9zaYEHvdRb7+jew3fFl+qa/AfFxEOyYjCAY72n2mcYAyVddaCW0 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BiBACuz1FV/5FdJa1cgkVKVF4GxDBmCYFOAQuGAwKBNjgUAQEBAQEBAYEKhCABAQEEAQEBaxsCAQgRAwECJAQHJwsUCQgCBAESCYgOAxINyQgBAQEBAQEBAQEBAQEBAQEBAQEBGYs5gj8OF4E+EQECPhcBhC0FhmKLa4QlhkaBJD6DII4Tg1UjYYEoHBWBPW8BgQs5gQEBAQE
X-IronPort-AV: E=Sophos;i="5.13,414,1427760000";  d="scan'208,217";a="149308699"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-2.cisco.com with ESMTP; 12 May 2015 10:06:54 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t4CA6r4F022142 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 12 May 2015 10:06:53 GMT
Received: from xmb-rcd-x08.cisco.com ([169.254.8.164]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0195.001; Tue, 12 May 2015 05:06:53 -0500
From: "Mouli Chandramouli (moulchan)" <moulchan@cisco.com>
To: Brad Schoening <brad.schoening@verizon.net>, "eman@ietf.org" <eman@ietf.org>
Thread-Topic: 2nd try: [eman] Brian Haberman's Discuss on draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMMENT)
Thread-Index: AQHQfbmq/GXtWlDjfEGVomBJRiui8Z1bQ6uAgAVBjICAF5u0AIAAymGA
Date: Tue, 12 May 2015 10:06:52 +0000
Message-ID: <D177CD39.41D26%moulchan@cisco.com>
References: <20150423113547.27316.23286.idtracker@ietfa.amsl.com> <D15EEB57.40C72%moulchan@cisco.com> <553DA67B.5030504@verizon.net> <5551744E.5060309@verizon.net>
In-Reply-To: <5551744E.5060309@verizon.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [10.142.111.250]
Content-Type: multipart/alternative; boundary="_000_D177CD3941D26moulchanciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eman/8kOwOa2b78kVa-3DwJFkiuushgI>
Subject: Re: [eman] 2nd try: Brian Haberman's Discuss on draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMMENT)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2015 10:06:58 -0000

--_000_D177CD3941D26moulchanciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi  Brad,

I had replied earlier  that the EMAN use cases were compiled based on sever=
al WG meetings and comments or feedback on the email list.

The feedback from Pete Resnick  was that the the specific use cases in ques=
tion,  were not addressed in EMAN, and hence either mention "out of scope" =
or delete them.

As suggested by Pete, we can mention that those use cases are out of scope.

Thanks
Mouli



From: Brad Schoening <brad.schoening@verizon.net<mailto:brad.schoening@veri=
zon.net>>
Date: Tuesday, 12 May 2015 9:02 AM
To: "eman@ietf.org<mailto:eman@ietf.org>" <eman@ietf.org<mailto:eman@ietf.o=
rg>>, Mouli Chandramouli <moulchan@cisco.com<mailto:moulchan@cisco.com>>
Subject: 2nd try: [eman] Brian Haberman's Discuss on draft-ietf-eman-applic=
ability-statement-10: (with DISCUSS and COMMENT)

Hi Mouli,

Just wondering if you plan further updates to the applicability statement d=
raft responding to the concerns raised, or if you would be ok deleting thes=
e specific use cases as not really being unique and non-overlapping.

Regards,

Brad

On 4/26/2015 11:01 PM, Brad Schoening wrote:
Mouli,

Your comments address the intent for adding these use cases, but they don't=
 respond to the critique of them, and therefore don't justify them.  Can yo=
u please respond to Pete & Alissa's questions.  Otherwise, let's delete the=
m as Bruce & I have suggested.

Regards,

Brad

On 4/23/2015 9:45 PM, Mouli Chandramouli (moulchan) wrote:
Hi  Brian,

Some of the specific use cases, you are referring had been provided as feed=
back to WG (email or meetings)  when the draft was draft was presented.
It was felt that it would be useful  "unique, non-overlapping" set of use c=
ases (scenarios) of interest to energy management.
It may be that after the other MIB drafts have evolved over the years, it m=
ay be that we solve only a subset of use cases.

Thanks
Mouli




From: Brian Haberman <brian@innovationslab.net<mailto:brian@innovationslab.=
net>>
Date: Thursday, 23 April 2015 4:35 AM
To: The IESG <iesg@ietf.org<mailto:iesg@ietf.org>>
Cc: "eman-chairs@ietf.org<mailto:eman-chairs@ietf.org>" <eman-chairs@ietf.o=
rg<mailto:eman-chairs@ietf.org>>, "eman@ietf.org<mailto:eman@ietf.org>" <em=
an@ietf.org<mailto:eman@ietf.org>>
Subject: [eman] Brian Haberman's Discuss on draft-ietf-eman-applicability-s=
tatement-10: (with DISCUSS and COMMENT)

Brian Haberman has entered the following ballot position for
draft-ietf-eman-applicability-statement-10: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

The draft still calls out some use cases that appear out of scope,
especially after the discussion around the EMAN MIB document. This
DISCUSS is a placeholder to address one of the author's suggestion to
delete: 1) the use cases in section 2.7 last paragraph (net-zero
building), 2) 2.12 (off-grid devices), and 3) 2.14 (power capping).


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for addressing the issue of the document's status.


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




_______________________________________________
eman mailing list
eman@ietf.org<mailto:eman@ietf.org>https://www.ietf.org/mailman/listinfo/em=
an


--
Brad Schoening
Email:


--
Brad Schoening
Email:

--_000_D177CD3941D26moulchanciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <8186B67ED3094E478F7A11B8CE8D1C50@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Hi &nbsp;Brad,</div>
<div><br>
</div>
<div>I had replied earlier &nbsp;that the EMAN use cases were compiled base=
d on several WG meetings and comments or feedback on the email list.&nbsp;<=
/div>
<div><br>
</div>
<div>The feedback from Pete Resnick &nbsp;was that the the specific use cas=
es in question, &nbsp;were not addressed in EMAN, and hence either mention =
&quot;out of scope&quot; or delete them.&nbsp;</div>
<div><br>
</div>
<div>As suggested by Pete, we can mention that those use cases are out of s=
cope.&nbsp;</div>
<div><br>
</div>
<div>Thanks</div>
<div>Mouli</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Brad Schoening &lt;<a href=3D=
"mailto:brad.schoening@verizon.net">brad.schoening@verizon.net</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, 12 May 2015 9:02 AM<=
br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:eman@ie=
tf.org">eman@ietf.org</a>&quot; &lt;<a href=3D"mailto:eman@ietf.org">eman@i=
etf.org</a>&gt;, Mouli Chandramouli &lt;<a href=3D"mailto:moulchan@cisco.co=
m">moulchan@cisco.com</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>2nd try: [eman] Brian Habe=
rman's Discuss on draft-ietf-eman-applicability-statement-10: (with DISCUSS=
 and COMMENT)<br>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
<div class=3D"moz-cite-prefix">Hi Mouli,<br>
<br>
Just wondering if you plan further updates to the applicability statement d=
raft responding to the concerns raised, or if you would be ok deleting thes=
e specific use cases as not really being unique and non-overlapping.<br>
<br>
Regards,<br>
<br>
Brad<br>
<br>
On 4/26/2015 11:01 PM, Brad Schoening wrote:<br>
</div>
<blockquote cite=3D"mid:553DA67B.5030504@verizon.net" type=3D"cite">
<div class=3D"moz-cite-prefix">Mouli,<br>
<br>
Your comments address the intent for adding these use cases, but they don't=
 respond to the critique of them, and therefore don't justify them.&nbsp; C=
an you please respond to Pete &amp; Alissa's questions.&nbsp; Otherwise, le=
t's delete them as Bruce &amp; I have suggested.<br>
<br>
Regards,<br>
<br>
Brad<br>
<br>
On 4/23/2015 9:45 PM, Mouli Chandramouli (moulchan) wrote:<br>
</div>
<blockquote cite=3D"mid:D15EEB57.40C72%25moulchan@cisco.com" type=3D"cite">
<div>Hi &nbsp;Brian,</div>
<div><br>
</div>
<div>Some of the specific use cases, you are referring had been provided as=
 feedback to WG (email or meetings) &nbsp;when the draft was draft was pres=
ented.&nbsp;</div>
<div>It was felt that it would be useful &nbsp;&quot;unique, non-overlappin=
g&quot; set of use cases (scenarios) of interest to energy management.&nbsp=
;</div>
<div>It may be that after the other MIB drafts have evolved over the years,=
 it may be that we solve only a subset of use cases.&nbsp;</div>
<div><br>
</div>
<div>Thanks</div>
<div>Mouli</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt;
            text-align:left; color:black; BORDER-BOTTOM: medium none;
            BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT:
            0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;
            BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Brian Haberman &lt;<a moz-do-=
not-send=3D"true" href=3D"mailto:brian@innovationslab.net">brian@innovation=
slab.net</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Thursday, 23 April 2015 4:35 =
AM<br>
<span style=3D"font-weight:bold">To: </span>The IESG &lt;<a moz-do-not-send=
=3D"true" href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a moz-do-not-send=3D"tru=
e" href=3D"mailto:eman-chairs@ietf.org">eman-chairs@ietf.org</a>&quot; &lt;=
<a moz-do-not-send=3D"true" href=3D"mailto:eman-chairs@ietf.org">eman-chair=
s@ietf.org</a>&gt;, &quot;<a moz-do-not-send=3D"true" href=3D"mailto:eman@i=
etf.org">eman@ietf.org</a>&quot;
 &lt;<a moz-do-not-send=3D"true" href=3D"mailto:eman@ietf.org">eman@ietf.or=
g</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[eman] Brian Haberman's Di=
scuss on draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMM=
ENT)<br>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5;
            MARGIN:0 0 0 5;">
<div>
<div>
<div>Brian Haberman has entered the following ballot position for</div>
<div>draft-ietf-eman-applicability-statement-10: Discuss</div>
<div><br>
</div>
<div>When responding, please keep the subject line intact and reply to all<=
/div>
<div>email addresses included in the To and CC lines. (Feel free to cut thi=
s</div>
<div>introductory paragraph, however.)</div>
<div><br>
</div>
<div><br>
</div>
<div>Please refer to <a moz-do-not-send=3D"true" href=3D"http://www.ietf.or=
g/iesg/statement/discuss-criteria.html">
http://www.ietf.org/iesg/statement/discuss-criteria.html</a></div>
<div>for more information about IESG DISCUSS and COMMENT positions.</div>
<div><br>
</div>
<div><br>
</div>
<div>The document, along with other ballot positions, can be found here:</d=
iv>
<div><a moz-do-not-send=3D"true" href=3D"http://datatracker.ietf.org/doc/dr=
aft-ietf-eman-applicability-statement/">http://datatracker.ietf.org/doc/dra=
ft-ietf-eman-applicability-statement/</a></div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>----------------------------------------------------------------------=
</div>
<div>DISCUSS:</div>
<div>----------------------------------------------------------------------=
</div>
<div><br>
</div>
<div>The draft still calls out some use cases that appear out of scope,</di=
v>
<div>especially after the discussion around the EMAN MIB document. This</di=
v>
<div>DISCUSS is a placeholder to address one of the author's suggestion to<=
/div>
<div>delete: 1) the use cases in section 2.7 last paragraph (net-zero</div>
<div>building), 2) 2.12 (off-grid devices), and 3) 2.14 (power capping).</d=
iv>
<div><br>
</div>
<div><br>
</div>
<div>----------------------------------------------------------------------=
</div>
<div>COMMENT:</div>
<div>----------------------------------------------------------------------=
</div>
<div><br>
</div>
<div>Thank you for addressing the issue of the document's status.</div>
<div><br>
</div>
<div><br>
</div>
<div>_______________________________________________</div>
<div>eman mailing list</div>
<div><a moz-do-not-send=3D"true" href=3D"mailto:eman@ietf.org">eman@ietf.or=
g</a></div>
<div><a moz-do-not-send=3D"true" href=3D"https://www.ietf.org/mailman/listi=
nfo/eman">https://www.ietf.org/mailman/listinfo/eman</a></div>
<div><br>
</div>
</div>
</div>
</blockquote>
</span><br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset> <br>
<pre wrap=3D"">_______________________________________________
eman mailing list
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" href=3D"mail=
to:eman@ietf.org">eman@ietf.org</a><a moz-do-not-send=3D"true" class=3D"moz=
-txt-link-freetext" href=3D"https://www.ietf.org/mailman/listinfo/eman">htt=
ps://www.ietf.org/mailman/listinfo/eman</a></pre>
</blockquote>
<br>
<br>
<div class=3D"moz-signature">-- <br>
<b>Brad Schoening</b> <br>
Email: </div>
</blockquote>
<br>
<br>
<div class=3D"moz-signature">-- <br>
<b>Brad Schoening</b> <br>
Email: </div>
</div>
</div>
</blockquote>
</span>
</body>
</html>

--_000_D177CD3941D26moulchanciscocom_--


From nobody Tue May 12 05:01:17 2015
Return-Path: <tnadeau@lucidvision.com>
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 701F71A89FB for <eman@ietfa.amsl.com>; Tue, 12 May 2015 05:01:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.896
X-Spam-Level: 
X-Spam-Status: No, score=0.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 ZQyijQYtmpk8 for <eman@ietfa.amsl.com>; Tue, 12 May 2015 05:01:11 -0700 (PDT)
Received: from lucidvision.com (unknown [50.255.148.178]) by ietfa.amsl.com (Postfix) with ESMTP id A94E11A90D1 for <eman@ietf.org>; Tue, 12 May 2015 05:01:10 -0700 (PDT)
Received: from [192.168.1.108] (unknown [50.255.148.181]) by lucidvision.com (Postfix) with ESMTP id B272C347EEE7; Tue, 12 May 2015 08:01:09 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_9019DF28-D0BA-4DA1-A978-272A2B0D5047"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
In-Reply-To: <D177CD39.41D26%moulchan@cisco.com>
Date: Tue, 12 May 2015 08:01:09 -0400
Message-Id: <8AB342FE-CABA-4886-8368-AE987633DDB6@lucidvision.com>
References: <20150423113547.27316.23286.idtracker@ietfa.amsl.com> <D15EEB57.40C72%moulchan@cisco.com> <553DA67B.5030504@verizon.net> <5551744E.5060309@verizon.net> <D177CD39.41D26%moulchan@cisco.com>
To: "Mouli Chandramouli (moulchan)" <moulchan@cisco.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/eman/gajxF4ijqDl4cPXjBsjOq2o3UMg>
Cc: "eman@ietf.org" <eman@ietf.org>
Subject: Re: [eman] 2nd try: Brian Haberman's Discuss on draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMMENT)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2015 12:01:16 -0000

--Apple-Mail=_9019DF28-D0BA-4DA1-A978-272A2B0D5047
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On May 12, 2015:6:06 AM, at 6:06 AM, Mouli Chandramouli (moulchan) =
<moulchan@cisco.com> wrote:
>=20
> Hi  Brad,
>=20
> I had replied earlier  that the EMAN use cases were compiled based on =
several WG meetings and comments or feedback on the email list.=20
>=20
> The feedback from Pete Resnick  was that the the specific use cases in =
question,  were not addressed in EMAN, and hence either mention "out of =
scope" or delete them.=20
>=20
> As suggested by Pete, we can mention that those use cases are out of =
scope.=20
>=20
> Thanks
> Mouli

	Yes, this was a specific suggestion and I think that the =
agreement was to indeed strike them from the draft to keep things =
consistent.=20

	=E2=80=94Tom


>=20
>=20
>=20
> From: Brad Schoening <brad.schoening@verizon.net =
<mailto:brad.schoening@verizon.net>>
> Date: Tuesday, 12 May 2015 9:02 AM
> To: "eman@ietf.org <mailto:eman@ietf.org>" <eman@ietf.org =
<mailto:eman@ietf.org>>, Mouli Chandramouli <moulchan@cisco.com =
<mailto:moulchan@cisco.com>>
> Subject: 2nd try: [eman] Brian Haberman's Discuss on =
draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMMENT)
>=20
>> Hi Mouli,
>>=20
>> Just wondering if you plan further updates to the applicability =
statement draft responding to the concerns raised, or if you would be ok =
deleting these specific use cases as not really being unique and =
non-overlapping.
>>=20
>> Regards,
>>=20
>> Brad
>>=20
>> On 4/26/2015 11:01 PM, Brad Schoening wrote:
>>> Mouli,
>>>=20
>>> Your comments address the intent for adding these use cases, but =
they don't respond to the critique of them, and therefore don't justify =
them.  Can you please respond to Pete & Alissa's questions.  Otherwise, =
let's delete them as Bruce & I have suggested.
>>>=20
>>> Regards,
>>>=20
>>> Brad
>>>=20
>>> On 4/23/2015 9:45 PM, Mouli Chandramouli (moulchan) wrote:
>>>> Hi  Brian,
>>>>=20
>>>> Some of the specific use cases, you are referring had been provided =
as feedback to WG (email or meetings)  when the draft was draft was =
presented.=20
>>>> It was felt that it would be useful  "unique, non-overlapping" set =
of use cases (scenarios) of interest to energy management.=20
>>>> It may be that after the other MIB drafts have evolved over the =
years, it may be that we solve only a subset of use cases.=20
>>>>=20
>>>> Thanks
>>>> Mouli
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> From: Brian Haberman <brian@innovationslab.net =
<mailto:brian@innovationslab.net>>
>>>> Date: Thursday, 23 April 2015 4:35 AM
>>>> To: The IESG <iesg@ietf.org <mailto:iesg@ietf.org>>
>>>> Cc: "eman-chairs@ietf.org <mailto:eman-chairs@ietf.org>" =
<eman-chairs@ietf.org <mailto:eman-chairs@ietf.org>>, "eman@ietf.org =
<mailto:eman@ietf.org>" <eman@ietf.org <mailto:eman@ietf.org>>
>>>> Subject: [eman] Brian Haberman's Discuss on =
draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMMENT)
>>>>=20
>>>>> Brian Haberman has entered the following ballot position for
>>>>> draft-ietf-eman-applicability-statement-10: Discuss
>>>>>=20
>>>>> When responding, please keep the subject line intact and reply to =
all
>>>>> email addresses included in the To and CC lines. (Feel free to cut =
this
>>>>> introductory paragraph, however.)
>>>>>=20
>>>>>=20
>>>>> Please refer to =
http://www.ietf.org/iesg/statement/discuss-criteria.html =
<http://www.ietf.org/iesg/statement/discuss-criteria.html>
>>>>> for more information about IESG DISCUSS and COMMENT positions.
>>>>>=20
>>>>>=20
>>>>> The document, along with other ballot positions, can be found =
here:
>>>>> =
http://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/ =
<http://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/>=

>>>>>=20
>>>>>=20
>>>>>=20
>>>>> =
----------------------------------------------------------------------
>>>>> DISCUSS:
>>>>> =
----------------------------------------------------------------------
>>>>>=20
>>>>> The draft still calls out some use cases that appear out of scope,
>>>>> especially after the discussion around the EMAN MIB document. This
>>>>> DISCUSS is a placeholder to address one of the author's suggestion =
to
>>>>> delete: 1) the use cases in section 2.7 last paragraph (net-zero
>>>>> building), 2) 2.12 (off-grid devices), and 3) 2.14 (power =
capping).
>>>>>=20
>>>>>=20
>>>>> =
----------------------------------------------------------------------
>>>>> COMMENT:
>>>>> =
----------------------------------------------------------------------
>>>>>=20
>>>>> Thank you for addressing the issue of the document's status.
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> eman mailing list
>>>>> eman@ietf.org <mailto:eman@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/eman =
<https://www.ietf.org/mailman/listinfo/eman>
>>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> eman mailing list
>>>> eman@ietf.org =
<mailto:eman@ietf.org>https://www.ietf.org/mailman/listinfo/eman =
<https://www.ietf.org/mailman/listinfo/eman>
>>>=20
>>> --=20
>>> Brad Schoening=20
>>> Email:
>>=20
>>=20
>> --=20
>> Brad Schoening=20
>> Email:
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman


--Apple-Mail=_9019DF28-D0BA-4DA1-A978-272A2B0D5047
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On May 12, 2015:6:06 AM, at 6:06 AM, Mouli Chandramouli =
(moulchan) &lt;<a href=3D"mailto:moulchan@cisco.com" =
class=3D"">moulchan@cisco.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii" class=3D"">

<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; font-size: 14px; font-family: =
Calibri, sans-serif;" class=3D"">
<div class=3D"">Hi &nbsp;Brad,</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I had replied earlier &nbsp;that the EMAN use cases were =
compiled based on several WG meetings and comments or feedback on the =
email list.&nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">The feedback from Pete Resnick &nbsp;was that the the =
specific use cases in question, &nbsp;were not addressed in EMAN, and =
hence either mention "out of scope" or delete them.&nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">As suggested by Pete, we can mention that those use =
cases are out of scope.&nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Thanks</div>
<div class=3D"">Mouli</div></div></div></blockquote><div><br =
class=3D""></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Yes, this was a specific =
suggestion and I think that the agreement was to indeed strike them from =
the draft to keep things consistent.&nbsp;</div><div><br =
class=3D""></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>=E2=80=94Tom</div><div><br =
class=3D""></div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; font-size: 14px; =
font-family: Calibri, sans-serif;" class=3D"">
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<span id=3D"OLK_SRC_BODY_SECTION" class=3D"">
<div style=3D"font-family: Calibri; font-size: 11pt; text-align: left; =
border-width: 1pt medium medium; border-style: solid none none; padding: =
3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class=3D"">
<span style=3D"font-weight:bold" class=3D"">From: </span>Brad Schoening =
&lt;<a href=3D"mailto:brad.schoening@verizon.net" =
class=3D"">brad.schoening@verizon.net</a>&gt;<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">Date: </span>Tuesday, 12 May =
2015 9:02 AM<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">To: </span>"<a =
href=3D"mailto:eman@ietf.org" class=3D"">eman@ietf.org</a>" &lt;<a =
href=3D"mailto:eman@ietf.org" class=3D"">eman@ietf.org</a>&gt;, Mouli =
Chandramouli &lt;<a href=3D"mailto:moulchan@cisco.com" =
class=3D"">moulchan@cisco.com</a>&gt;<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">Subject: </span>2nd try: =
[eman] Brian Haberman's Discuss on =
draft-ietf-eman-applicability-statement-10: (with DISCUSS and =
COMMENT)<br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;" =
class=3D"" type=3D"cite">
<div class=3D"">
<div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"">
<div class=3D"moz-cite-prefix">Hi Mouli,<br class=3D"">
<br class=3D"">
Just wondering if you plan further updates to the applicability =
statement draft responding to the concerns raised, or if you would be ok =
deleting these specific use cases as not really being unique and =
non-overlapping.<br class=3D"">
<br class=3D"">
Regards,<br class=3D"">
<br class=3D"">
Brad<br class=3D"">
<br class=3D"">
On 4/26/2015 11:01 PM, Brad Schoening wrote:<br class=3D"">
</div>
<blockquote cite=3D"mid:553DA67B.5030504@verizon.net" type=3D"cite" =
class=3D"">
<div class=3D"moz-cite-prefix">Mouli,<br class=3D"">
<br class=3D"">
Your comments address the intent for adding these use cases, but they =
don't respond to the critique of them, and therefore don't justify =
them.&nbsp; Can you please respond to Pete &amp; Alissa's =
questions.&nbsp; Otherwise, let's delete them as Bruce &amp; I have =
suggested.<br class=3D"">
<br class=3D"">
Regards,<br class=3D"">
<br class=3D"">
Brad<br class=3D"">
<br class=3D"">
On 4/23/2015 9:45 PM, Mouli Chandramouli (moulchan) wrote:<br class=3D"">
</div>
<blockquote cite=3D"mid:D15EEB57.40C72%25moulchan@cisco.com" type=3D"cite"=
 class=3D"">
<div class=3D"">Hi &nbsp;Brian,</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Some of the specific use cases, you are referring had =
been provided as feedback to WG (email or meetings) &nbsp;when the draft =
was draft was presented.&nbsp;</div>
<div class=3D"">It was felt that it would be useful &nbsp;"unique, =
non-overlapping" set of use cases (scenarios) of interest to energy =
management.&nbsp;</div>
<div class=3D"">It may be that after the other MIB drafts have evolved =
over the years, it may be that we solve only a subset of use =
cases.&nbsp;</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Thanks</div>
<div class=3D"">Mouli</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<span id=3D"OLK_SRC_BODY_SECTION" class=3D"">
<div style=3D"font-family: Calibri; font-size: 11pt; text-align: left; =
border-width: 1pt medium medium; border-style: solid none none; padding: =
3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class=3D"">
<span style=3D"font-weight:bold" class=3D"">From: </span>Brian Haberman =
&lt;<a moz-do-not-send=3D"true" href=3D"mailto:brian@innovationslab.net" =
class=3D"">brian@innovationslab.net</a>&gt;<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">Date: </span>Thursday, 23 =
April 2015 4:35 AM<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">To: </span>The IESG &lt;<a =
moz-do-not-send=3D"true" href=3D"mailto:iesg@ietf.org" =
class=3D"">iesg@ietf.org</a>&gt;<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">Cc: </span>"<a =
moz-do-not-send=3D"true" href=3D"mailto:eman-chairs@ietf.org" =
class=3D"">eman-chairs@ietf.org</a>" &lt;<a moz-do-not-send=3D"true" =
href=3D"mailto:eman-chairs@ietf.org" =
class=3D"">eman-chairs@ietf.org</a>&gt;, "<a moz-do-not-send=3D"true" =
href=3D"mailto:eman@ietf.org" class=3D"">eman@ietf.org</a>"
 &lt;<a moz-do-not-send=3D"true" href=3D"mailto:eman@ietf.org" =
class=3D"">eman@ietf.org</a>&gt;<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">Subject: </span>[eman] Brian =
Haberman's Discuss on draft-ietf-eman-applicability-statement-10: (with =
DISCUSS and COMMENT)<br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5;
            MARGIN:0 0 0 5;" class=3D"" type=3D"cite">
<div class=3D"">
<div class=3D"">
<div class=3D"">Brian Haberman has entered the following ballot position =
for</div>
<div class=3D"">draft-ietf-eman-applicability-statement-10: =
Discuss</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">When responding, please keep the subject line intact and =
reply to all</div>
<div class=3D"">email addresses included in the To and CC lines. (Feel =
free to cut this</div>
<div class=3D"">introductory paragraph, however.)</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Please refer to <a moz-do-not-send=3D"true" =
href=3D"http://www.ietf.org/iesg/statement/discuss-criteria.html" =
class=3D"">
http://www.ietf.org/iesg/statement/discuss-criteria.html</a></div>
<div class=3D"">for more information about IESG DISCUSS and COMMENT =
positions.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">The document, along with other ballot positions, can be =
found here:</div>
<div class=3D""><a moz-do-not-send=3D"true" =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-eman-applicability-stat=
ement/" =
class=3D"">http://datatracker.ietf.org/doc/draft-ietf-eman-applicability-s=
tatement/</a></div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div =
class=3D"">---------------------------------------------------------------=
-------</div>
<div class=3D"">DISCUSS:</div>
<div =
class=3D"">---------------------------------------------------------------=
-------</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">The draft still calls out some use cases that appear out =
of scope,</div>
<div class=3D"">especially after the discussion around the EMAN MIB =
document. This</div>
<div class=3D"">DISCUSS is a placeholder to address one of the author's =
suggestion to</div>
<div class=3D"">delete: 1) the use cases in section 2.7 last paragraph =
(net-zero</div>
<div class=3D"">building), 2) 2.12 (off-grid devices), and 3) 2.14 =
(power capping).</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div =
class=3D"">---------------------------------------------------------------=
-------</div>
<div class=3D"">COMMENT:</div>
<div =
class=3D"">---------------------------------------------------------------=
-------</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Thank you for addressing the issue of the document's =
status.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">_______________________________________________</div>
<div class=3D"">eman mailing list</div>
<div class=3D""><a moz-do-not-send=3D"true" href=3D"mailto:eman@ietf.org" =
class=3D"">eman@ietf.org</a></div>
<div class=3D""><a moz-do-not-send=3D"true" =
href=3D"https://www.ietf.org/mailman/listinfo/eman" =
class=3D"">https://www.ietf.org/mailman/listinfo/eman</a></div>
<div class=3D""><br class=3D"">
</div>
</div>
</div>
</blockquote>
</span><br class=3D"">
<fieldset class=3D"mimeAttachmentHeader"></fieldset> <br class=3D"">
<pre wrap=3D"" class=3D"">_______________________________________________
eman mailing list
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" =
href=3D"mailto:eman@ietf.org">eman@ietf.org</a><a moz-do-not-send=3D"true"=
 class=3D"moz-txt-link-freetext" =
href=3D"https://www.ietf.org/mailman/listinfo/eman">https://www.ietf.org/m=
ailman/listinfo/eman</a></pre>
</blockquote>
<br class=3D"">
<br class=3D"">
<div class=3D"moz-signature">-- <br class=3D"">
<b class=3D"">Brad Schoening</b> <br class=3D"">
Email: </div>
</blockquote>
<br class=3D"">
<br class=3D"">
<div class=3D"moz-signature">-- <br class=3D"">
<b class=3D"">Brad Schoening</b> <br class=3D"">
Email: </div>
</div>
</div>
</blockquote>
</span>
</div>

_______________________________________________<br class=3D"">eman =
mailing list<br class=3D""><a href=3D"mailto:eman@ietf.org" =
class=3D"">eman@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/eman<br =
class=3D""></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_9019DF28-D0BA-4DA1-A978-272A2B0D5047--


From nobody Tue May 12 20:09:57 2015
Return-Path: <internet-drafts@ietf.org>
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 130351A90C2; Tue, 12 May 2015 20:09:54 -0700 (PDT)
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 j6EuYlFKO3XB; Tue, 12 May 2015 20:09:52 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 46BCE1A9162; Tue, 12 May 2015 20:09:50 -0700 (PDT)
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: 6.0.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150513030950.3241.54211.idtracker@ietfa.amsl.com>
Date: Tue, 12 May 2015 20:09:50 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/eman/OUuS8sPEsyMqxUNsj0B7dOaelG0>
Cc: eman@ietf.org
Subject: [eman] I-D Action: draft-ietf-eman-applicability-statement-11.txt
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2015 03:09:54 -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 (EMAN) Applicability Statement
        Authors         : Brad Schoening
                          Mouli Chandramouli
                          Bruce Nordman
	Filename        : draft-ietf-eman-applicability-statement-11.txt
	Pages           : 28
	Date            : 2015-05-12

Abstract:
        The objective of Energy Management (EMAN) is to provide an
        energy management framework for networked devices.  This
        document presents the applicability of the EMAN information
        model in a variety of scenarios with cases and target devices.
        These use cases are useful for identifying requirements for the
        framework and MIBs.  Further, we describe the relationship of
        the EMAN framework to relevant other energy monitoring standards
        and architectures.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-eman-applicability-statement-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-eman-applicability-statement-11


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 May 13 09:19:59 2015
Return-Path: <bnordman@lbl.gov>
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 D25551A8F4A for <eman@ietfa.amsl.com>; Wed, 13 May 2015 09:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.587
X-Spam-Level: 
X-Spam-Status: No, score=-3.587 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, T_RP_MATCHES_RCVD=-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 alm_-ZKAu_eH for <eman@ietfa.amsl.com>; Wed, 13 May 2015 09:19:54 -0700 (PDT)
Received: from fe1.lbl.gov (fe1.lbl.gov [128.3.41.133]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A47D1A8AE6 for <eman@ietf.org>; Wed, 13 May 2015 09:19:54 -0700 (PDT)
X-Ironport-SBRS: 4.8
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao0DABB5U1XRVdS2lGdsb2JhbABZA4JFgR5eBoMYszmGFIdyggEBC4YDAoEyB0wBAQEBAQESAQEBAQcLCwkfMIQgAQEBAwEBAQEPEUsLBQsLCwYDAQIBIwcCAiIFDQEFARQIBhMJGYd1AwoIBQipcz4xiziSNwEBAQEBAQEBAQEBAQEBAQEBAQEBARcKizCCPw4XgT4RAQI+AQwEBxGCHDsSgTMFhmKFRIN6hl2GSYElPoMljheCDRIjgRWBBIEoHBWBXR4xAYELgToBAQE
X-IronPort-AV: E=Sophos;i="5.13,421,1427785200"; d="scan'208";a="86470270"
Received: from mail-wi0-f182.google.com ([209.85.212.182]) by fe1.lbl.gov with ESMTP; 13 May 2015 09:19:35 -0700
Received: by wicnf17 with SMTP id nf17so62543024wic.1 for <eman@ietf.org>; Wed, 13 May 2015 09:19:34 -0700 (PDT)
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=3xaszoezQCvj+AzQSRzadFl/tBqO6EMR5LOKY9EZzW8=; b=g7St1NrJjVuCX8kj2DJ8hDr5ZtVArxRlWiQd0TLux3nWB70nun78gUdvoXh3STTU2n JRLnRYEOqk2vIj8rTUlAwQGx7xnPq9GcO/4K79gpJ1JST8Ee0ytnkzbrJkQQ8QX3rQxs +voNRMr8uzcGlcsn0Za3f8U9jhd8XqEaspF46xKchwJFkr8lO4bYRikg/YeYo9/rG0Nm xMcuD94HkVnq2PL5k72AjKWmZmiWIUzztJo/2kMQR90qCs2GecL+OfP1wg5YHlc+Xa/X JpGETVVF3BtcmbvKCmoiBBzVnxYG6fi6FlrQXmutbgMDYSw2AoO4neQ3rHal9NzgfjOW 7M9w==
X-Gm-Message-State: ALoCoQlg3eK39EYKIOPbGtZiJK0RPWEiqV4fbNoLO4Hs1YfoqR/KJs171R5DQfj2lh9mjWYREN/5UwK7AEbyWei7fBpZ6EmwmcXbQOrCdTGrFB/kUVYVA5Y7CtUpcSNF5r5NYH9v/+iq
X-Received: by 10.194.78.105 with SMTP id a9mr42473003wjx.152.1431533974642; Wed, 13 May 2015 09:19:34 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.78.105 with SMTP id a9mr42472980wjx.152.1431533974515; Wed, 13 May 2015 09:19:34 -0700 (PDT)
Received: by 10.28.10.12 with HTTP; Wed, 13 May 2015 09:19:34 -0700 (PDT)
In-Reply-To: <D177CD39.41D26%moulchan@cisco.com>
References: <20150423113547.27316.23286.idtracker@ietfa.amsl.com> <D15EEB57.40C72%moulchan@cisco.com> <553DA67B.5030504@verizon.net> <5551744E.5060309@verizon.net> <D177CD39.41D26%moulchan@cisco.com>
Date: Wed, 13 May 2015 09:19:34 -0700
Message-ID: <CAK+eDP8iRcQYxqQHMADveB65A80+iDWxh4BA7Wv3QZsbrVnUxQ@mail.gmail.com>
From: Bruce Nordman <bnordman@lbl.gov>
To: "Mouli Chandramouli (moulchan)" <moulchan@cisco.com>
Content-Type: multipart/alternative; boundary=047d7bfcefa60904db0515f8fa1a
Archived-At: <http://mailarchive.ietf.org/arch/msg/eman/4ANnWefjdCPQkxcw7kQ07Ie8i60>
Cc: "eman@ietf.org" <eman@ietf.org>
Subject: Re: [eman] 2nd try: Brian Haberman's Discuss on draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMMENT)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2015 16:19:57 -0000

--047d7bfcefa60904db0515f8fa1a
Content-Type: text/plain; charset=UTF-8

I do agree with deleting them.
I don't agree they are out of scope, but if not in the doc, then doesn't
matter.
Thanks,
--Bruce

On Tue, May 12, 2015 at 3:06 AM, Mouli Chandramouli (moulchan) <
moulchan@cisco.com> wrote:

>  Hi  Brad,
>
>  I had replied earlier  that the EMAN use cases were compiled based on
> several WG meetings and comments or feedback on the email list.
>
>  The feedback from Pete Resnick  was that the the specific use cases in
> question,  were not addressed in EMAN, and hence either mention "out of
> scope" or delete them.
>
>  As suggested by Pete, we can mention that those use cases are out of
> scope.
>
>  Thanks
> Mouli
>
>
>
>   From: Brad Schoening <brad.schoening@verizon.net>
> Date: Tuesday, 12 May 2015 9:02 AM
> To: "eman@ietf.org" <eman@ietf.org>, Mouli Chandramouli <
> moulchan@cisco.com>
> Subject: 2nd try: [eman] Brian Haberman's Discuss on
> draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMMENT)
>
>   Hi Mouli,
>
> Just wondering if you plan further updates to the applicability statement
> draft responding to the concerns raised, or if you would be ok deleting
> these specific use cases as not really being unique and non-overlapping.
>
> Regards,
>
> Brad
>
> On 4/26/2015 11:01 PM, Brad Schoening wrote:
>
> Mouli,
>
> Your comments address the intent for adding these use cases, but they
> don't respond to the critique of them, and therefore don't justify them.
> Can you please respond to Pete & Alissa's questions.  Otherwise, let's
> delete them as Bruce & I have suggested.
>
> Regards,
>
> Brad
>
> On 4/23/2015 9:45 PM, Mouli Chandramouli (moulchan) wrote:
>
> Hi  Brian,
>
>  Some of the specific use cases, you are referring had been provided as
> feedback to WG (email or meetings)  when the draft was draft was presented.
> It was felt that it would be useful  "unique, non-overlapping" set of use
> cases (scenarios) of interest to energy management.
> It may be that after the other MIB drafts have evolved over the years, it
> may be that we solve only a subset of use cases.
>
>  Thanks
> Mouli
>
>
>
>
>   From: Brian Haberman <brian@innovationslab.net>
> Date: Thursday, 23 April 2015 4:35 AM
> To: The IESG <iesg@ietf.org>
> Cc: "eman-chairs@ietf.org" <eman-chairs@ietf.org>, "eman@ietf.org" <
> eman@ietf.org>
> Subject: [eman] Brian Haberman's Discuss on
> draft-ietf-eman-applicability-statement-10: (with DISCUSS and COMMENT)
>
>   Brian Haberman has entered the following ballot position for
> draft-ietf-eman-applicability-statement-10: Discuss
>
>  When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
>  Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
>  The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/
>
>
>
>  ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
>  The draft still calls out some use cases that appear out of scope,
> especially after the discussion around the EMAN MIB document. This
> DISCUSS is a placeholder to address one of the author's suggestion to
> delete: 1) the use cases in section 2.7 last paragraph (net-zero
> building), 2) 2.12 (off-grid devices), and 3) 2.14 (power capping).
>
>
>  ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
>  Thank you for addressing the issue of the document's status.
>
>
>  _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman
>
>
>
> _______________________________________________
> eman mailing listeman@ietf.orghttps://www.ietf.org/mailman/listinfo/eman
>
>
>
> --
> *Brad Schoening*
> Email:
>
>
>
> --
> *Brad Schoening*
> Email:
>
>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman
>
>


-- 
*Bruce Nordman*
Lawrence Berkeley National Laboratory
*nordman.lbl.gov <http://nordman.lbl.gov>*
BNordman@LBL.gov
510-486-7089
m: 510-501-7943

--047d7bfcefa60904db0515f8fa1a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>I do agree with deleting them.<br></div>I don&#3=
9;t agree they are out of scope, but if not in the doc, then doesn&#39;t ma=
tter.<br></div><div>Thanks,<br></div>--Bruce<br></div><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote">On Tue, May 12, 2015 at 3:06 AM, Mouli=
 Chandramouli (moulchan) <span dir=3D"ltr">&lt;<a href=3D"mailto:moulchan@c=
isco.com" target=3D"_blank">moulchan@cisco.com</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div>Hi =C2=A0Brad,</div>
<div><br>
</div>
<div>I had replied earlier =C2=A0that the EMAN use cases were compiled base=
d on several WG meetings and comments or feedback on the email list.=C2=A0<=
/div>
<div><br>
</div>
<div>The feedback from Pete Resnick =C2=A0was that the the specific use cas=
es in question, =C2=A0were not addressed in EMAN, and hence either mention =
&quot;out of scope&quot; or delete them.=C2=A0</div>
<div><br>
</div>
<div>As suggested by Pete, we can mention that those use cases are out of s=
cope.=C2=A0</div>
<div><br>
</div>
<div>Thanks</div>
<div>Mouli</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span>
<div style=3D"font-family:Calibri;font-size:11pt;text-align:left;color:blac=
k;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADD=
ING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:me=
dium none;PADDING-TOP:3pt">
<span style=3D"font-weight:bold">From: </span>Brad Schoening &lt;<a href=3D=
"mailto:brad.schoening@verizon.net" target=3D"_blank">brad.schoening@verizo=
n.net</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, 12 May 2015 9:02 AM<=
br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:eman@ie=
tf.org" target=3D"_blank">eman@ietf.org</a>&quot; &lt;<a href=3D"mailto:ema=
n@ietf.org" target=3D"_blank">eman@ietf.org</a>&gt;, Mouli Chandramouli &lt=
;<a href=3D"mailto:moulchan@cisco.com" target=3D"_blank">moulchan@cisco.com=
</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>2nd try: [eman] Brian Habe=
rman&#39;s Discuss on draft-ietf-eman-applicability-statement-10: (with DIS=
CUSS and COMMENT)<br>
</div>
<div><br>
</div>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
<div>Hi Mouli,<br>
<br>
Just wondering if you plan further updates to the applicability statement d=
raft responding to the concerns raised, or if you would be ok deleting thes=
e specific use cases as not really being unique and non-overlapping.<br>
<br>
Regards,<br>
<br>
Brad<br>
<br>
On 4/26/2015 11:01 PM, Brad Schoening wrote:<br>
</div>
<blockquote type=3D"cite">
<div>Mouli,<br>
<br>
Your comments address the intent for adding these use cases, but they don&#=
39;t respond to the critique of them, and therefore don&#39;t justify them.=
=C2=A0 Can you please respond to Pete &amp; Alissa&#39;s questions.=C2=A0 O=
therwise, let&#39;s delete them as Bruce &amp; I have suggested.<br>
<br>
Regards,<br>
<br>
Brad<br>
<br>
On 4/23/2015 9:45 PM, Mouli Chandramouli (moulchan) wrote:<br>
</div>
<blockquote type=3D"cite">
<div>Hi =C2=A0Brian,</div>
<div><br>
</div>
<div>Some of the specific use cases, you are referring had been provided as=
 feedback to WG (email or meetings) =C2=A0when the draft was draft was pres=
ented.=C2=A0</div>
<div>It was felt that it would be useful =C2=A0&quot;unique, non-overlappin=
g&quot; set of use cases (scenarios) of interest to energy management.=C2=
=A0</div>
<div>It may be that after the other MIB drafts have evolved over the years,=
 it may be that we solve only a subset of use cases.=C2=A0</div>
<div><br>
</div>
<div>Thanks</div>
<div>Mouli</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span>
<div style=3D"font-family:Calibri;font-size:11pt;text-align:left;color:blac=
k;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADD=
ING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:me=
dium none;PADDING-TOP:3pt">
<span style=3D"font-weight:bold">From: </span>Brian Haberman &lt;<a href=3D=
"mailto:brian@innovationslab.net" target=3D"_blank">brian@innovationslab.ne=
t</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Thursday, 23 April 2015 4:35 =
AM<br>
<span style=3D"font-weight:bold">To: </span>The IESG &lt;<a href=3D"mailto:=
iesg@ietf.org" target=3D"_blank">iesg@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:eman-ch=
airs@ietf.org" target=3D"_blank">eman-chairs@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:eman-chairs@ietf.org" target=3D"_blank">eman-chairs@ietf.org</a>=
&gt;, &quot;<a href=3D"mailto:eman@ietf.org" target=3D"_blank">eman@ietf.or=
g</a>&quot;
 &lt;<a href=3D"mailto:eman@ietf.org" target=3D"_blank">eman@ietf.org</a>&g=
t;<br>
<span style=3D"font-weight:bold">Subject: </span>[eman] Brian Haberman&#39;=
s Discuss on draft-ietf-eman-applicability-statement-10: (with DISCUSS and =
COMMENT)<br>
</div>
<div><br>
</div>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div>
<div>Brian Haberman has entered the following ballot position for</div>
<div>draft-ietf-eman-applicability-statement-10: Discuss</div>
<div><br>
</div>
<div>When responding, please keep the subject line intact and reply to all<=
/div>
<div>email addresses included in the To and CC lines. (Feel free to cut thi=
s</div>
<div>introductory paragraph, however.)</div>
<div><br>
</div>
<div><br>
</div>
<div>Please refer to <a href=3D"http://www.ietf.org/iesg/statement/discuss-=
criteria.html" target=3D"_blank">
http://www.ietf.org/iesg/statement/discuss-criteria.html</a></div>
<div>for more information about IESG DISCUSS and COMMENT positions.</div>
<div><br>
</div>
<div><br>
</div>
<div>The document, along with other ballot positions, can be found here:</d=
iv>
<div><a href=3D"http://datatracker.ietf.org/doc/draft-ietf-eman-applicabili=
ty-statement/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf=
-eman-applicability-statement/</a></div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>----------------------------------------------------------------------=
</div>
<div>DISCUSS:</div>
<div>----------------------------------------------------------------------=
</div>
<div><br>
</div>
<div>The draft still calls out some use cases that appear out of scope,</di=
v>
<div>especially after the discussion around the EMAN MIB document. This</di=
v>
<div>DISCUSS is a placeholder to address one of the author&#39;s suggestion=
 to</div>
<div>delete: 1) the use cases in section 2.7 last paragraph (net-zero</div>
<div>building), 2) 2.12 (off-grid devices), and 3) 2.14 (power capping).</d=
iv>
<div><br>
</div>
<div><br>
</div>
<div>----------------------------------------------------------------------=
</div>
<div>COMMENT:</div>
<div>----------------------------------------------------------------------=
</div>
<div><br>
</div>
<div>Thank you for addressing the issue of the document&#39;s status.</div>
<div><br>
</div>
<div><br>
</div>
<div>_______________________________________________</div>
<div>eman mailing list</div>
<div><a href=3D"mailto:eman@ietf.org" target=3D"_blank">eman@ietf.org</a></=
div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/eman" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/eman</a></div>
<div><br>
</div>
</div>
</div>
</blockquote>
</span><br>
<fieldset></fieldset> <br>
<pre>_______________________________________________
eman mailing list
<a href=3D"mailto:eman@ietf.org" target=3D"_blank">eman@ietf.org</a><a href=
=3D"https://www.ietf.org/mailman/listinfo/eman" target=3D"_blank">https://w=
ww.ietf.org/mailman/listinfo/eman</a></pre>
</blockquote>
<br><span class=3D"HOEnZb"><font color=3D"#888888">
<br>
<div>-- <br>
<b>Brad Schoening</b> <br>
Email: </div>
</font></span></blockquote><span class=3D"HOEnZb"><font color=3D"#888888">
<br>
<br>
<div>-- <br>
<b>Brad Schoening</b> <br>
Email: </div>
</font></span></div>
</div>
</blockquote>
</span>
</div>

<br>_______________________________________________<br>
eman mailing list<br>
<a href=3D"mailto:eman@ietf.org">eman@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/eman" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/eman</a><br>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail=
_signature"><font size=3D"4"><b>Bruce Nordman</b></font><br><span style=3D"=
color:rgb(0,0,153)">Lawrence Berkeley National Laboratory</span><br><b><spa=
n style=3D"color:rgb(0,102,0)"><a href=3D"http://nordman.lbl.gov" target=3D=
"_blank">nordman.lbl.gov</a></span></b><br>BNordman@LBL.gov<br>510-486-7089=
<br>m: 510-501-7943<br></div>
</div>

--047d7bfcefa60904db0515f8fa1a--


From nobody Thu May 14 04:09:25 2015
Return-Path: <brian@innovationslab.net>
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 895E11A19F7; Thu, 14 May 2015 04:09:24 -0700 (PDT)
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 JKNbHMVHqQAG; Thu, 14 May 2015 04:09:23 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CDB91A1A13; Thu, 14 May 2015 04:09:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Brian Haberman" <brian@innovationslab.net>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150514110923.10618.67532.idtracker@ietfa.amsl.com>
Date: Thu, 14 May 2015 04:09:23 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/eman/N3cZYB_46RV5Fs4QetGKeWAchXM>
Cc: eman-chairs@ietf.org, eman@ietf.org
Subject: [eman] Brian Haberman's No Objection on draft-ietf-eman-applicability-statement-11: (with COMMENT)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2015 11:09:24 -0000

Brian Haberman has entered the following ballot position for
draft-ietf-eman-applicability-statement-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the updates to remove the out-of-scope use cases.



From nobody Thu May 14 07:06:55 2015
Return-Path: <ben@nostrum.com>
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 8C7111B2A5F; Thu, 14 May 2015 07:02:54 -0700 (PDT)
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 iAWo7V3KPWZT; Thu, 14 May 2015 07:02:52 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2150D1AC415; Thu, 14 May 2015 07:02:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Ben Campbell" <ben@nostrum.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150514140235.17316.97659.idtracker@ietfa.amsl.com>
Date: Thu, 14 May 2015 07:02:35 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/eman/x73L2RbAs3BPxPUo1FA9D3J4XRk>
X-Mailman-Approved-At: Thu, 14 May 2015 07:06:53 -0700
Cc: eman-chairs@ietf.org, eman@ietf.org
Subject: [eman] Ben Campbell's No Objection on draft-ietf-eman-applicability-statement-11: (with COMMENT)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2015 14:02:54 -0000

Ben Campbell has entered the following ballot position for
draft-ietf-eman-applicability-statement-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for addressing my DISCUSS. I've cleared.



From nobody Thu May 14 07:08:22 2015
Return-Path: <tnadeau@lucidvision.com>
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 EEE651B2A71; Thu, 14 May 2015 07:08:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.895
X-Spam-Level: 
X-Spam-Status: No, score=0.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 nQjqjItWGWvd; Thu, 14 May 2015 07:08:18 -0700 (PDT)
Received: from lucidvision.com (unknown [50.255.148.178]) by ietfa.amsl.com (Postfix) with ESMTP id E8F141B2A84; Thu, 14 May 2015 07:07:54 -0700 (PDT)
Received: from [192.168.1.108] (unknown [50.255.148.181]) by lucidvision.com (Postfix) with ESMTP id 7C74734A5A6B; Thu, 14 May 2015 10:07:54 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
In-Reply-To: <20150514140235.17316.97659.idtracker@ietfa.amsl.com>
Date: Thu, 14 May 2015 10:07:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5AE5751C-6ECC-4867-8E89-D01800CB0F42@lucidvision.com>
References: <20150514140235.17316.97659.idtracker@ietfa.amsl.com>
To: joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/eman/P-M7ZBFdVo1SXoftBYDP08txjSk>
Cc: eman-chairs@ietf.org, "eman@ietf.org >> eman mailing list" <eman@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [eman] Ben Campbell's No Objection on draft-ietf-eman-applicability-statement-11: (with COMMENT)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2015 14:08:22 -0000

	Cool. Thank you. Joel, it looks like the document is cleared to =
progress now.

	=E2=80=94Tom


> On May 14, 2015:10:02 AM, at 10:02 AM, Ben Campbell <ben@nostrum.com> =
wrote:
>=20
> Ben Campbell has entered the following ballot position for
> draft-ietf-eman-applicability-statement-11: No Objection
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut =
this
> introductory paragraph, however.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> =
https://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> Thank you for addressing my DISCUSS. I've cleared.
>=20
>=20
>=20


From nobody Mon May 18 16:23:31 2015
Return-Path: <iesg-secretary@ietf.org>
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 E931F1B2B04; Mon, 18 May 2015 16:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LKOGOK69uvVj; Mon, 18 May 2015 16:23:27 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8022C1B2B14; Mon, 18 May 2015 16:23:23 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150518232323.7378.28624.idtracker@ietfa.amsl.com>
Date: Mon, 18 May 2015 16:23:23 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/eman/YK9qtJ_FgLsy-Obt8qH-14sSK0A>
Cc: eman mailing list <eman@ietf.org>, eman chair <eman-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [eman] Protocol Action: 'Energy Management (EMAN) Applicability Statement' to Proposed Standard (draft-ietf-eman-applicability-statement-11.txt)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 May 2015 23:23:29 -0000

The IESG has approved the following document:
- 'Energy Management (EMAN) Applicability Statement'
  (draft-ietf-eman-applicability-statement-11.txt) as Proposed Standard

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

The IESG contact persons are Benoit Claise and Joel Jaeggli.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement/





Technical Summary

  The objective of Energy Management (EMAN) is to provide an 
  energy management framework for networked devices.  This 
  document presents the applicability of the EMAN information 
  model in a variety of scenarios with cases and target devices.  
  These use cases are useful for identifying requirements for the 
  framework and MIBs.  Further, we describe the relationship of 
  the EMAN framework to relevant other energy monitoring standards 
  and architectures. 

Working Group Summary

Version -00 of the draft was published in December 2011, shortly
after the WG was chartered.  The authors (and WG chairs) felt that
since there were many aspects of EMAN that neededed a lot of
discussion, it would be sensible to publish its Applicability
Statement after all the other EMAN drafts.

Document Quality

This draft has been revised at intervals as details of EMAN were
finalised.  It's WG Last Call for version 06 ran from 26 June 2014 to 
2 July 2014.  Since then it's authors have made further revisions,
in response to its ongoing discussion.

Personnel

Document Shepherd:         Nevil Brownlee
Responsible Area Director: Joel Jaegli

