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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 28 June 2016 15:10 UTC

Return-Path: <dromasca@avaya.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 7974612D158 for <eman@ietfa.amsl.com>; Tue, 28 Jun 2016 08:10:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.346
X-Spam-Level:
X-Spam-Status: No, score=-8.346 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] 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 MHFp3FLX0S6h for <eman@ietfa.amsl.com>; Tue, 28 Jun 2016 08:10:33 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (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 C0F1A12D151 for <eman@ietf.org>; Tue, 28 Jun 2016 08:10:32 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2EhAQAOknJX/xUHmMZbGQEBAQEBgnMtg?= =?us-ascii?q?VMGjSSgfYl8gg+Be4YYAhyBEzgUAQEBAQEBAQNiJ4RMAQEBAQMSERE6CwwEAgE?= =?us-ascii?q?IDQQDAQEBAQICBh0DAgICHxEUAQgIAgQBDQUIDAsDh3QDFwGoQ4pQjB4NhAoBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEcgQGFKIRMgkOBSTYVgmorgi8FiBiQNjQBjDE?= =?us-ascii?q?Bg3CHdgyFOYgQh28eNoNwbogxAX4BAQE?=
X-IPAS-Result: =?us-ascii?q?A2EhAQAOknJX/xUHmMZbGQEBAQEBgnMtgVMGjSSgfYl8gg+?= =?us-ascii?q?Be4YYAhyBEzgUAQEBAQEBAQNiJ4RMAQEBAQMSERE6CwwEAgEIDQQDAQEBAQICB?= =?us-ascii?q?h0DAgICHxEUAQgIAgQBDQUIDAsDh3QDFwGoQ4pQjB4NhAoBAQEBAQEBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEcgQGFKIRMgkOBSTYVgmorgi8FiBiQNjQBjDEBg3CHdgyFOYgQh?= =?us-ascii?q?28eNoNwbogxAX4BAQE?=
X-IronPort-AV: E=Sophos;i="5.26,541,1459828800"; d="scan'208";a="160220181"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 28 Jun 2016 11:10:29 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES256-SHA; 28 Jun 2016 11:10:29 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Tue, 28 Jun 2016 11:10:26 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, Rolf Winter <rolf.winter@gmail.com>, Nadeau Thomas <tnadeau@lucidvision.com>
Thread-Topic: [eman] energy-specific efforts at IETF?
Thread-Index: AQHR0U0EQOJeGMDrzkiWuZcFEl9pm5/++pBA
Date: Tue, 28 Jun 2016 15:10:26 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA7521DEAC@AZ-FFEXMB04.global.avaya.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>
In-Reply-To: <8fb2d1ec-4a69-42c4-0063-123ada215fc8@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.48]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/eman/ae6epSNdR7vIQ7csXejGdFvJ_xM>
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: Tue, 28 Jun 2016 15:10:35 -0000

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. 

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
> >