Re: [eman] energy-specific efforts at IETF?

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 06 July 2016 11:53 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 817E012D688 for <eman@ietfa.amsl.com>; Wed, 6 Jul 2016 04:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level:
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 vu833Fzdz7X3 for <eman@ietfa.amsl.com>; Wed, 6 Jul 2016 04:53:01 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D075A12B02D for <eman@ietf.org>; Wed, 6 Jul 2016 04:53:00 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u66BqnGj008733; Wed, 6 Jul 2016 13:52:49 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 67CB3204950; Wed, 6 Jul 2016 13:53:59 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 55451204A86; Wed, 6 Jul 2016 13:53:59 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u66BqmhZ007987; Wed, 6 Jul 2016 13:52:48 +0200
To: joel jaeggli <joelja@bogus.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Rolf Winter <rolf.winter@gmail.com>, Nadeau Thomas <tnadeau@lucidvision.com>
References: <556E820E.4040208@bogus.com> <55720A99.2030407@cisco.com> <944DE63C-1467-4EC2-976F-24C46588693F@lucidvision.com> <D19C53A1.43722%moulchan@cisco.com> <dc75c6ae-8992-9f2b-9e0f-937eeb6bf54b@gmail.com> <9494BFE6-4782-4B9B-B4BC-B9C474F1C93D@lucidvision.com> <CADfatQ1_632NcmK9jZW9mc=fANEFnnFp2-q130ffZTavt+GsoQ@mail.gmail.com> <34c7f0db-6547-add3-333d-9f390558d0d7@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA751F8C6D@AZ-FFEXMB04.global.avaya.com> <8fb2d1ec-4a69-42c4-0063-123ada215fc8@gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA7521DEAC@AZ-FFEXMB04.global.avaya.com> <1419b926-5bd8-fc70-669a-02d22091a431@bogus.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <6ae6e435-dfff-f058-446e-546ba11b9ddf@gmail.com>
Date: Wed, 6 Jul 2016 13:52:48 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <1419b926-5bd8-fc70-669a-02d22091a431@bogus.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/eman/FkLS44nTcf3x5Hb21lwMninsEE4>
Cc: "eman@ietf.org" <eman@ietf.org>
Subject: Re: [eman] energy-specific efforts at IETF?
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 06 Jul 2016 11:53:03 -0000


Le 30/06/2016 à 06:49, joel jaeggli a écrit :
> On 6/28/16 8:10 AM, Romascanu, Dan (Dan) wrote:
>> Sure. But your two statements (in the first paragraph) use each of
>> the conditional 'may'. What is the reason to use YANG on the devices?
>> The SDN paradigm does not AFAIK make assumptions about using a
>> specific protocol or DML at the device management level. YANG comes
>> at a certain cost (bits on wire, memory). Maybe this is affordable,
>> or maybe YANG is needed for other reasons, but this needs to be shown
>> explicitely.
>
> Signaling presumes in some utility is derived from coordination.
>
> If I have a ten year primary battery or I'm a space probe headed to
> alpha centuri I'm not going to devote a lot of electrons to expressing
> my power consumption or battery condition.
>
> More active or particularly coordinated groups of devices such as the
> elements of a BST or a datacenter might well have information to share.

Whereas I can expect a BST (Base Station?) to be operated on chemical 
battery in emergency areas, it would be hard to imagine an entire 
datacenter on battery - wouldn't it rather be on combustion-engine 
electricity generators?

For the BST case: I will write separately.

For the datacenter: I think there would be a need for an entirely 
different MIB, different than a battery-MIB.

Alex

>
>> Regards,
>>
>> Dan
>>
>>
>>> -----Original Message----- From: Alexandre Petrescu
>>> [mailto:alexandre.petrescu@gmail.com] Sent: Tuesday, June 28, 2016
>>> 5:55 PM To: Romascanu, Dan (Dan); Rolf Winter; Nadeau Thomas Cc:
>>> eman@ietf.org Subject: Re: [eman] energy-specific efforts at IETF?
>>>
>>> The SDN paradigm may be applied not just to switches but to
>>> smartphones. Further, a tool like CoMI (CoAP Management Interface)
>>> may make use of YANG models on IoT devices which are typically
>>> constrained on battery.
>>>
>>> Yesterday I read about an NB-IoT LPWA device from u-blox which runs
>>> on a battery for 10 years.
>>>
>>> Alex
>>>
>>> Le 02/06/2016 à 11:20, Romascanu, Dan (Dan) a écrit :
>>>> No, RFC 7577 defines an SMIv2 MIB.
>>>>
>>>> Before engaging in a discussion about 'let us do EMAN data
>>>> modelling in YANG' I would like to see a use case - i.e. an
>>>> example of an energy monitoring system that uses YANG for
>>>> reporting energy information.
>>>>
>>>> Regards,
>>>>
>>>> Dan
>>>>
>>>>
>>>>> -----Original Message----- From: eman
>>>>> [mailto:eman-bounces@ietf.org] On Behalf Of Alexandre Petrescu
>>>>> Sent: Thursday, June 02, 2016 11:22 AM To: Rolf Winter; Nadeau
>>>>> Thomas Cc: eman@ietf.org Subject: Re: [eman] energy-specific
>>>>> efforts at IETF?
>>>>>
>>>>>
>>>>>
>>>>> Le 02/06/2016 à 10:18, Rolf Winter a écrit :
>>>>>> Is there anything that the EMAN work is not addressing or
>>>>>> that requires new protocol work?
>>>>>
>>>>> For my clarification - is the battery monitoring MIB RFC7577
>>>>> using YANG?
>>>>>
>>>>> Alex
>>>>>
>>>>>>
>>>>>> On Wed, Jun 1, 2016 at 8:00 PM, Nadeau Thomas
>>>>> <tnadeau@lucidvision.com> wrote:
>>>>>>>
>>>>>>> Not that I know of in the form of an official working
>>>>>>> group. EMAN was
>>>>> shut down something like a year ago.
>>>>>>>
>>>>>>> --Tom
>>>>>>>
>>>>>>>> On Jun 1, 2016:8:34 AM, at 8:34 AM, Alexandre Petrescu
>>>>> <alexandre.petrescu@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Is there any other effort focusing on energy consumption
>>>>>>>> happening at
>>>>> IETF currently?
>>>>>>>>
>>>>>>>> I am interested in aspects related to energy consumption
>>>>>>>> of IP networks
>>>>> used to deliver video streams.
>>>>>>>>
>>>>>>>> Yours,
>>>>>>>>
>>>>>>>> Alex Petrescu
>>>>>>>>
>>>>>>>> Le 09/06/2015 à 05:01, Mouli Chandramouli (moulchan) a
>>>>>>>> écrit :
>>>>>>>>> Thanks to all the WG chairs for shepherding the IETF
>>>>>>>>> drafts and taking them to a conclusion. I may not be
>>>>>>>>> able to travel to Prague.  So, enjoy.
>>>>>>>>>
>>>>>>>>> Cheers Mouli
>>>>>>>>>
>>>>>>>>> From: Nadeau Thomas <tnadeau@lucidvision.com
>>>>>>>>> <mailto:tnadeau@lucidvision.com>> Date: Saturday, 6
>>>>>>>>> June 2015 2:22 AM To: "Benoit Claise (bclaise)"
>>>>>>>>> <bclaise@cisco.com <mailto:bclaise@cisco.com>> Cc: eman
>>>>>>>>> mailing list <eman@ietf.org <mailto:eman@ietf.org>>,
>>>>>>>>> "eman-chairs@tools.ietf.org
>>>>>>>>> <mailto:eman-chairs@tools.ietf.org>"
>>>>>>>>> <eman-chairs@tools.ietf.org
>>>>>>>>> <mailto:eman-chairs@tools.ietf.org>> Subject: Re:
>>>>>>>>> [eman] Status of the EMAN W.G. effort.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Beers are on you! 8)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Jun 5, 2015:4:46 PM, at 4:46 PM, Benoit Claise
>>>>>>>>>> <bclaise@cisco.com <mailto:bclaise@cisco.com>>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Yes, thanks to the contributors, document editors, WG
>>>>>>>>>> chairs, previous ADs :-), basically the entire EMAN
>>>>>>>>>> community. Celebration in Prague? Fine with me.
>>>>>>>>>>
>>>>>>>>>> Regards, Benoit
>>>>>>>>>>> Greetings,
>>>>>>>>>>>
>>>>>>>>>>> Now that we've crossed the milstone of having
>>>>>>>>>>> draft-ietf-eman-applicability-statement-11 move to
>>>>>>>>>>> the RFC editor
>>>>> queue,
>>>>>>>>>>> I think we can pause and reflect on the effort that
>>>>>>>>>>> has completed.
>>>>> It
>>>>>>>>>>> took a while to get here and the consensus that we
>>>>>>>>>>> built was hard
>>>>> won
>>>>>>>>>>> but I hope durable.
>>>>>>>>>>>
>>>>>>>>>>> It's my intention to close down the working group,
>>>>>>>>>>> maintaining the mailing list for a time. The
>>>>>>>>>>> mailing list archive as with other IETF mailing
>>>>>>>>>>> lists will be preserved. in the immediate sense if
>>>>>>>>>>> there is
>>>>> work
>>>>>>>>>>> around the edges of this space we have the opsawg
>>>>>>>>>>> working
>>> group
>>>>> to
>>>>>>>>>>> support such activities.
>>>>>>>>>>>
>>>>>>>>>>> Thank you again for your diligent efforts,
>>>>>>>>>>> especially the present and former chairs who
>>>>>>>>>>> shepherded this work to the point that it is at
>>>>> now.
>>>>>>>>>>>
>>>>>>>>>>> Regards Joel
>>>>
>> _______________________________________________ eman mailing list
>> eman@ietf.org https://www.ietf.org/mailman/listinfo/eman
>>
>
>