From nobody Wed Jul 6 04:53:05 2016 Return-Path: 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 ; 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 ; 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 ; 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 , "Romascanu, Dan (Dan)" , Rolf Winter , Nadeau Thomas References: <556E820E.4040208@bogus.com> <55720A99.2030407@cisco.com> <944DE63C-1467-4EC2-976F-24C46588693F@lucidvision.com> <9494BFE6-4782-4B9B-B4BC-B9C474F1C93D@lucidvision.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 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: Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 >>>>> 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 >>>>> 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 >>>>>>>> > Date: Saturday, 6 >>>>>>>>> June 2015 2:22 AM To: "Benoit Claise (bclaise)" >>>>>>>>> > Cc: eman >>>>>>>>> mailing list >, >>>>>>>>> "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 >>>>>>>>>> > >>>>>>>>>> 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 >> > > From nobody Fri Jul 8 05:25:04 2016 Return-Path: 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 9096512B012 for ; Fri, 8 Jul 2016 05:24:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.353 X-Spam-Level: X-Spam-Status: No, score=-5.353 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 YB8XMzl8CyzJ for ; Fri, 8 Jul 2016 05:24:51 -0700 (PDT) Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0D7B12D5CA for ; Fri, 8 Jul 2016 05:24:50 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u68COYLe016869; Fri, 8 Jul 2016 14:24:34 +0200 Received: from localhost.localdomain (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id D7EB0208F5D; Fri, 8 Jul 2016 14:24:34 +0200 (CEST) Received: from pisaure by pisaure with queue id 4696214-2; Fri, 08 Jul 2016 12:24:34 GMT Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 92BB2200F07; Fri, 8 Jul 2016 14:24:34 +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 u68COY9e012455; Fri, 8 Jul 2016 14:24:34 +0200 To: eman@ietf.org References: <556E820E.4040208@bogus.com> <55720A99.2030407@cisco.com> <944DE63C-1467-4EC2-976F-24C46588693F@lucidvision.com> <9494BFE6-4782-4B9B-B4BC-B9C474F1C93D@lucidvision.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> <6ae6e435-dfff-f058-446e-546ba11b9ddf@gmail.com> From: Alexandre Petrescu Message-ID: Date: Fri, 8 Jul 2016 14:24:34 +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: <6ae6e435-dfff-f058-446e-546ba11b9ddf@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Cc: "Plymoth Nilsson Anders \(anders@telhoc.se\)" , Erkki Harjula , BEN HADJ SAID Siwar , bjorn.landfeldt@eit.lth.se Subject: [eman] YANG model for battery MIB X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 12:24:55 -0000 Hello, We have submitted a new draft describing a YANG model for the battery MIB: https://tools.ietf.org/html/draft-petrescu-battery-mib-yang-00 How should we pursue this draft? Alex Le 06/07/2016 à 13:52, Alexandre Petrescu a écrit : > > > 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 >>>>>> 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 >>>>>> 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 >>>>>>>>> > Date: Saturday, 6 >>>>>>>>>> June 2015 2:22 AM To: "Benoit Claise (bclaise)" >>>>>>>>>> > Cc: eman >>>>>>>>>> mailing list >, >>>>>>>>>> "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 >>>>>>>>>>> > >>>>>>>>>>> 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 >>> >> >> > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman From nobody Fri Jul 8 05:31:23 2016 Return-Path: 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 A96EF12B044 for ; Fri, 8 Jul 2016 05:31:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.626 X-Spam-Level: X-Spam-Status: No, score=-5.626 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 AzJT6VhkHe_7 for ; Fri, 8 Jul 2016 05:31:19 -0700 (PDT) Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E202D12B012 for ; Fri, 8 Jul 2016 05:31:18 -0700 (PDT) Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 946ECEF1; Fri, 8 Jul 2016 14:31:17 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from atlas3.jacobs-university.de ([10.70.0.205]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id b0aVrzXp_PCu; Fri, 8 Jul 2016 14:31:13 +0200 (CEST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Fri, 8 Jul 2016 14:31:14 +0200 (CEST) Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 0DC2720075; Fri, 8 Jul 2016 14:31:14 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id hEjm506sVnET; Fri, 8 Jul 2016 14:31:11 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id A98DD20074; Fri, 8 Jul 2016 14:31:10 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id E41CC3BC2627; Fri, 8 Jul 2016 14:31:09 +0200 (CEST) Date: Fri, 8 Jul 2016 14:31:09 +0200 From: Juergen Schoenwaelder To: Alexandre Petrescu Message-ID: <20160708123109.GA23658@elstar.local> Mail-Followup-To: Alexandre Petrescu , eman@ietf.org, "Plymoth Nilsson Anders (anders@telhoc.se)" , Erkki Harjula , BEN HADJ SAID Siwar , bjorn.landfeldt@eit.lth.se References: <9494BFE6-4782-4B9B-B4BC-B9C474F1C93D@lucidvision.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> <6ae6e435-dfff-f058-446e-546ba11b9ddf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Clacks-Overhead: GNU Terry Pratchett Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) Archived-At: Cc: BEN HADJ SAID Siwar , "Plymoth Nilsson Anders \(anders@telhoc.se\)" , bjorn.landfeldt@eit.lth.se, eman@ietf.org, Erkki Harjula Subject: Re: [eman] YANG model for battery MIB X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 12:31:22 -0000 Hi, how is this different from 'smidump -f yang BATTERY-MIB', which implements the translation defined in RFC 6643? RFC 6643 was written to avoid manual translations and having to republish MIB modules /js On Fri, Jul 08, 2016 at 02:24:34PM +0200, Alexandre Petrescu wrote: > Hello, > > We have submitted a new draft describing a YANG model for the battery MIB: > > https://tools.ietf.org/html/draft-petrescu-battery-mib-yang-00 > > How should we pursue this draft? > > Alex > > Le 06/07/2016 à 13:52, Alexandre Petrescu a écrit : > > > > > > 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 > > > > > > > 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 > > > > > > > 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 > > > > > > > > > > > Date: Saturday, 6 > > > > > > > > > > > June 2015 2:22 AM To: "Benoit Claise (bclaise)" > > > > > > > > > > > > Cc: eman > > > > > > > > > > > mailing list >, > > > > > > > > > > > "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 > > > > > > > > > > > > > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > _______________________________________________ > > eman mailing list > > eman@ietf.org > > https://www.ietf.org/mailman/listinfo/eman > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 From nobody Mon Jul 11 08:17:53 2016 Return-Path: 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 CB13E12D51D for ; Mon, 11 Jul 2016 08:17:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.353 X-Spam-Level: X-Spam-Status: No, score=-5.353 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 LUUl22ejYuIF for ; Mon, 11 Jul 2016 08:17:48 -0700 (PDT) Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82E2F12D576 for ; Mon, 11 Jul 2016 08:17:46 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u6BFHW7r025878; Mon, 11 Jul 2016 17:17:32 +0200 Received: from localhost.localdomain (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id F2AAD20A32A; Mon, 11 Jul 2016 17:17:31 +0200 (CEST) Received: from pisaure by pisaure with queue id 4705226-2; Mon, 11 Jul 2016 15:17:31 GMT Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 9EF9820A32A; Mon, 11 Jul 2016 17:17:31 +0200 (CEST) Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u6BFHVn9024594; Mon, 11 Jul 2016 17:17:31 +0200 To: eman@ietf.org, "Plymoth Nilsson Anders (anders@telhoc.se)" , Erkki Harjula , BEN HADJ SAID Siwar , bjorn.landfeldt@eit.lth.se References: <9494BFE6-4782-4B9B-B4BC-B9C474F1C93D@lucidvision.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> <6ae6e435-dfff-f058-446e-546ba11b9ddf@gmail.com> <20160708123109.GA23658@elstar.local> From: Alexandre Petrescu Message-ID: Date: Mon, 11 Jul 2016 17:17:29 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160708123109.GA23658@elstar.local> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [eman] YANG model for battery MIB X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 15:17:51 -0000 We will have to check this, but for now I must say I did not know that one could generate the YANG model simply by issuing that command. Quickly skimming through it seems that 'smidump -f yang BATTERY-MIB' would not add a contact address of the person who performed the translation. Alex Le 08/07/2016 à 14:31, Juergen Schoenwaelder a écrit : > Hi, > > how is this different from 'smidump -f yang BATTERY-MIB', which > implements the translation defined in RFC 6643? RFC 6643 was written > to avoid manual translations and having to republish MIB modules > > /js > > On Fri, Jul 08, 2016 at 02:24:34PM +0200, Alexandre Petrescu wrote: >> Hello, >> >> We have submitted a new draft describing a YANG model for the >> battery MIB: >> >> https://tools.ietf.org/html/draft-petrescu-battery-mib-yang-00 >> >> How should we pursue this draft? >> >> Alex >> >> Le 06/07/2016 à 13:52, Alexandre Petrescu a écrit : >>> >>> >>> 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 >>>>>>>> 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 >>>>>>>> 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 >>>>>>>>>>> > Date: >>>>>>>>>>>> Saturday, 6 June 2015 2:22 AM To: "Benoit >>>>>>>>>>>> Claise (bclaise)" >>>>>>>>>>> > Cc: eman mailing >>>>>>>>>>>> list >, >>>>>>>>>>>> "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 >>>>>>>>>>>> > 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 >>>>> >>>> >>>> >>> >>> _______________________________________________ eman mailing >>> list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman >> >> _______________________________________________ eman mailing list >> eman@ietf.org https://www.ietf.org/mailman/listinfo/eman > From nobody Mon Jul 11 08:20:37 2016 Return-Path: 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 5702912D559 for ; Mon, 11 Jul 2016 08:20:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.487 X-Spam-Level: X-Spam-Status: No, score=-5.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287] 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 Xm5l4jn6xvRT for ; Mon, 11 Jul 2016 08:20:34 -0700 (PDT) Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9654B12D532 for ; Mon, 11 Jul 2016 08:20:34 -0700 (PDT) Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 6299B8FA; Mon, 11 Jul 2016 17:20:33 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from atlas3.jacobs-university.de ([10.70.0.205]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id Cp3BhzvvQ6Nf; Mon, 11 Jul 2016 17:20:32 +0200 (CEST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Mon, 11 Jul 2016 17:20:32 +0200 (CEST) Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id A2BDB20069; Mon, 11 Jul 2016 17:20:32 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id lyI0UmKL6r2h; Mon, 11 Jul 2016 17:20:32 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id DD72720063; Mon, 11 Jul 2016 17:20:31 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id EFD7E3BCAAF7; Mon, 11 Jul 2016 17:20:30 +0200 (CEST) Date: Mon, 11 Jul 2016 17:20:30 +0200 From: Juergen Schoenwaelder To: Alexandre Petrescu Message-ID: <20160711152030.GA33482@elstar.local> Mail-Followup-To: Alexandre Petrescu , eman@ietf.org, "Plymoth Nilsson Anders (anders@telhoc.se)" , Erkki Harjula , BEN HADJ SAID Siwar , bjorn.landfeldt@eit.lth.se References: <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> <6ae6e435-dfff-f058-446e-546ba11b9ddf@gmail.com> <20160708123109.GA23658@elstar.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) Archived-At: Cc: BEN HADJ SAID Siwar , "Plymoth Nilsson Anders \(anders@telhoc.se\)" , bjorn.landfeldt@eit.lth.se, eman@ietf.org, Erkki Harjula Subject: Re: [eman] YANG model for battery MIB X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 15:20:36 -0000 On Mon, Jul 11, 2016 at 05:17:29PM +0200, Alexandre Petrescu wrote: > We will have to check this, but for now I must say I did not know that > one could generate the YANG model simply by issuing that command. > > Quickly skimming through it seems that 'smidump -f yang BATTERY-MIB' > would not add a contact address of the person who performed the translation. Yep, why would it. The key is automated translations in order to avoid having to republish stuff. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 From nobody Wed Jul 20 01:40:21 2016 Return-Path: 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 5635012D9D1 for ; Wed, 20 Jul 2016 01:40:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.353 X-Spam-Level: X-Spam-Status: No, score=-5.353 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 OHqaUv8x6byR for ; Wed, 20 Jul 2016 01:40:18 -0700 (PDT) Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6975912D0B3 for ; Wed, 20 Jul 2016 01:40:18 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u6K8e6qa006777; Wed, 20 Jul 2016 10:40:06 +0200 Received: from localhost.localdomain (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id C7F65203F8E; Wed, 20 Jul 2016 10:40:06 +0200 (CEST) Received: from pisaure by pisaure with queue id 4731365-2; Wed, 20 Jul 2016 08:40:06 GMT Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 7E043200D0F; Wed, 20 Jul 2016 10:40:06 +0200 (CEST) Received: from [132.166.84.207] ([132.166.84.207]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u6K8e4TJ016220; Wed, 20 Jul 2016 10:40:05 +0200 To: eman@ietf.org, "Plymoth Nilsson Anders (anders@telhoc.se)" , Erkki Harjula , BEN HADJ SAID Siwar , bjorn.landfeldt@eit.lth.se References: <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> <6ae6e435-dfff-f058-446e-546ba11b9ddf@gmail.com> <20160708123109.GA23658@elstar.local> <20160711152030.GA33482@elstar.local> From: Alexandre Petrescu Message-ID: <246b2e02-3ae2-984b-af33-f3527a9a7a25@gmail.com> Date: Wed, 20 Jul 2016 10:40:04 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160711152030.GA33482@elstar.local> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [eman] YANG model for battery MIB X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 08:40:20 -0000 Le 11/07/2016 à 17:20, Juergen Schoenwaelder a écrit : > On Mon, Jul 11, 2016 at 05:17:29PM +0200, Alexandre Petrescu wrote: >> We will have to check this, but for now I must say I did not know that >> one could generate the YANG model simply by issuing that command. >> >> Quickly skimming through it seems that 'smidump -f yang BATTERY-MIB' >> would not add a contact address of the person who performed the translation. > > Yep, why would it. The key is automated translations in order to avoid > having to republish stuff. I just noticed in the DHC WG meeting that there is this YANG Data Model for DHCPv6 Configuration draft-ietf-dhc-dhcpv6-yang-03 And I suspect there are already many MIBs for DHCPv6 on major platforms. This gives some credit to the idea to lay down the smidump output in an Internet Draft. Alex PS: I am in Berlin and willing to meet talk about YANG model for battery MIB. > > /js > From nobody Wed Jul 20 03:29:46 2016 Return-Path: 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 A508D12D578 for ; Wed, 20 Jul 2016 03:29:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.487 X-Spam-Level: X-Spam-Status: No, score=-5.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287] 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 enyIe9a45tmX for ; Wed, 20 Jul 2016 03:29:44 -0700 (PDT) Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDD0212D178 for ; Wed, 20 Jul 2016 03:29:43 -0700 (PDT) Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id A0E6BCDB; Wed, 20 Jul 2016 12:29:42 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from atlas3.jacobs-university.de ([10.70.0.205]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id 1ROVcGg0Xmbu; Wed, 20 Jul 2016 12:29:38 +0200 (CEST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Wed, 20 Jul 2016 12:29:41 +0200 (CEST) Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 321FE20079; Wed, 20 Jul 2016 12:29:41 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id nSPtLS3BaBIA; Wed, 20 Jul 2016 12:29:39 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6241220075; Wed, 20 Jul 2016 12:29:39 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 49CBA3BDBF9B; Wed, 20 Jul 2016 12:29:39 +0200 (CEST) Date: Wed, 20 Jul 2016 12:29:39 +0200 From: Juergen Schoenwaelder To: Alexandre Petrescu Message-ID: <20160720102939.GA52214@elstar.local> Mail-Followup-To: Alexandre Petrescu , eman@ietf.org, "Plymoth Nilsson Anders (anders@telhoc.se)" , Erkki Harjula , BEN HADJ SAID Siwar , bjorn.landfeldt@eit.lth.se References: <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> <6ae6e435-dfff-f058-446e-546ba11b9ddf@gmail.com> <20160708123109.GA23658@elstar.local> <20160711152030.GA33482@elstar.local> <246b2e02-3ae2-984b-af33-f3527a9a7a25@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Clacks-Overhead: GNU Terry Pratchett Content-Transfer-Encoding: 8bit In-Reply-To: <246b2e02-3ae2-984b-af33-f3527a9a7a25@gmail.com> User-Agent: Mutt/1.6.0 (2016-04-01) Archived-At: Cc: BEN HADJ SAID Siwar , "Plymoth Nilsson Anders \(anders@telhoc.se\)" , bjorn.landfeldt@eit.lth.se, eman@ietf.org, Erkki Harjula Subject: Re: [eman] YANG model for battery MIB X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 10:29:46 -0000 On Wed, Jul 20, 2016 at 10:40:04AM +0200, Alexandre Petrescu wrote: > Le 11/07/2016 à 17:20, Juergen Schoenwaelder a écrit : > > On Mon, Jul 11, 2016 at 05:17:29PM +0200, Alexandre Petrescu wrote: > > > We will have to check this, but for now I must say I did not know that > > > one could generate the YANG model simply by issuing that command. > > > > > > Quickly skimming through it seems that 'smidump -f yang BATTERY-MIB' > > > would not add a contact address of the person who performed the translation. > > > > Yep, why would it. The key is automated translations in order to avoid > > having to republish stuff. > > I just noticed in the DHC WG meeting that there is this YANG Data Model for > DHCPv6 Configuration draft-ietf-dhc-dhcpv6-yang-03 > > And I suspect there are already many MIBs for DHCPv6 on major platforms. > > This gives some credit to the idea to lay down the smidump output in an > Internet Draft. > > Alex > PS: I am in Berlin and willing to meet talk about YANG model for battery > MIB. The BATTERY-MIB is not configuration; the IETF does not have the resources to republish ~100 mostly read-only MIB modules rendered in YANG. This is why RFC 6643 was created. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 From nobody Wed Jul 20 07:12:55 2016 Return-Path: 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 82A1D12D662 for ; Wed, 20 Jul 2016 07:12:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.187 X-Spam-Level: X-Spam-Status: No, score=-8.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.287] 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 wdijGuEK0Kz3 for ; Wed, 20 Jul 2016 07:12:48 -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 BEEEF12B050 for ; Wed, 20 Jul 2016 07:12:47 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2F5AQDchY9X/xUHmMZdGgEBAQGCdC2BU?= =?us-ascii?q?gaNJKkfgg+BeoYaAoEwOBQBAQEBAQEBA2InhFwBAQEBAxJnDAQCAQgNAQMEAQE?= =?us-ascii?q?BCh0HMhQJCAIEAQ0FCBqIDgGlCZg8AQEBAQEBAQEBAQEBAQEBAQEBAQEBHIYrh?= =?us-ascii?q?EyEDDaDKoIvBY5EimIBiQ2HQId9DIVEkCAeNoILHIFMboYoAX4BAQE?= X-IPAS-Result: =?us-ascii?q?A2F5AQDchY9X/xUHmMZdGgEBAQGCdC2BUgaNJKkfgg+BeoY?= =?us-ascii?q?aAoEwOBQBAQEBAQEBA2InhFwBAQEBAxJnDAQCAQgNAQMEAQEBCh0HMhQJCAIEA?= =?us-ascii?q?Q0FCBqIDgGlCZg8AQEBAQEBAQEBAQEBAQEBAQEBAQEBHIYrhEyEDDaDKoIvBY5?= =?us-ascii?q?EimIBiQ2HQId9DIVEkCAeNoILHIFMboYoAX4BAQE?= X-IronPort-AV: E=Sophos;i="5.28,394,1464667200"; d="scan'208";a="162829652" Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 20 Jul 2016 10:12:44 -0400 X-OutboundMail_SMTP: 1 Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES256-SHA; 20 Jul 2016 10:12:42 -0400 Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Wed, 20 Jul 2016 16:12:41 +0200 From: "Romascanu, Dan (Dan)" To: Juergen Schoenwaelder , "Alexandre Petrescu" Thread-Topic: [eman] YANG model for battery MIB Thread-Index: AQHR4mJfv6KfXUy+7U6QxuWlqMIFxqAg/PGAgABfWAA= Date: Wed, 20 Jul 2016 14:12:39 +0000 Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA75242C16@AZ-FFEXMB04.global.avaya.com> References: <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> <6ae6e435-dfff-f058-446e-546ba11b9ddf@gmail.com> <20160708123109.GA23658@elstar.local> <20160711152030.GA33482@elstar.local> <246b2e02-3ae2-984b-af33-f3527a9a7a25@gmail.com> <20160720102939.GA52214@elstar.local> In-Reply-To: <20160720102939.GA52214@elstar.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.64.58.47] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: "eman@ietf.org" , "Plymoth Nilsson Anders \(anders@telhoc.se\)" , Erkki Harjula , BEN HADJ SAID Siwar , "bjorn.landfeldt@eit.lth.se" Subject: Re: [eman] YANG model for battery MIB X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 14:12:54 -0000 > -----Original Message----- > From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Juergen > Schoenwaelder > Sent: Wednesday, July 20, 2016 1:30 PM > To: Alexandre Petrescu > Cc: BEN HADJ SAID Siwar; Plymoth Nilsson Anders (anders@telhoc.se); > bjorn.landfeldt@eit.lth.se; eman@ietf.org; Erkki Harjula > Subject: Re: [eman] YANG model for battery MIB >=20 > On Wed, Jul 20, 2016 at 10:40:04AM +0200, Alexandre Petrescu wrote: > > Le 11/07/2016 =E0 17:20, Juergen Schoenwaelder a =E9crit : > > > On Mon, Jul 11, 2016 at 05:17:29PM +0200, Alexandre Petrescu wrote: > > > > We will have to check this, but for now I must say I did not know > > > > that one could generate the YANG model simply by issuing that > command. > > > > > > > > Quickly skimming through it seems that 'smidump -f yang BATTERY-MIB= ' > > > > would not add a contact address of the person who performed the > translation. > > > > > > Yep, why would it. The key is automated translations in order to > > > avoid having to republish stuff. > > > > I just noticed in the DHC WG meeting that there is this YANG Data > > Model for > > DHCPv6 Configuration draft-ietf-dhc-dhcpv6-yang-03 > > > > And I suspect there are already many MIBs for DHCPv6 on major platforms= . > > > > This gives some credit to the idea to lay down the smidump output in > > an Internet Draft. > > > > Alex > > PS: I am in Berlin and willing to meet talk about YANG model for > > battery MIB. >=20 > The BATTERY-MIB is not configuration; the IETF does not have the resource= s > to republish ~100 mostly read-only MIB modules rendered in YANG. This is > why RFC 6643 was created. >=20 > /js >=20 I would add 'the IETF does not have the resources and there is no need to r= epublish ...'. But I can certainly can be wrong. I am in Berlin as well, an= d if you want discuss, Alexandru, I am willing to do it also.=20 Regards, Dan From nobody Wed Jul 20 23:15:45 2016 Return-Path: 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 C4AC812D181 for ; Wed, 20 Jul 2016 23:15:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.com 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 jXA5xoyJzF8q for ; Wed, 20 Jul 2016 23:15:42 -0700 (PDT) Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78CE812D0C9 for ; Wed, 20 Jul 2016 23:15:42 -0700 (PDT) Received: by mail-vk0-x236.google.com with SMTP id n129so54394446vke.3 for ; Wed, 20 Jul 2016 23:15:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=KAm62C/h8+SIk9Beofi9jMse3D52vGMo2qcnuOsQ7nE=; b=bk1iMNmizNdov2SWGJoZYG1L0bosHFbYhipAY4pcb4bDKn1seURlWLaz1NPTkdm2if PCm5E53msZ8wDDJjLYLFt0OQMsZCy28ydBEj9/4/u8TIP2MZhNQNbUK90J5pJJ9tXwVq YFrWgRKCSYvqCOanCGnBgfBC0lQDOLhfW7j3LFig6ZsEKaWwn0DS2ZvALtLjdHGIs5Z3 YrePstAFvuswD6rCq0958hjIrMPIyaxYFvq+OC+f9WVMln16jWdY7Lx5SQtKHvrT9XV2 QnpCUMZbGp3h8faUGvw6lvWvZE6OqWFmjSIUAxE6pWmZC4BslB1JYbp9Dq1VZoWNtzBe Jvww== 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:from:date :message-id:subject:to; bh=KAm62C/h8+SIk9Beofi9jMse3D52vGMo2qcnuOsQ7nE=; b=ae66nhTbUsuTvFu4NQkJa+trRm0803VvmjIfr6ipRwCA3nOZCEHjo6DNVi4pFMoyqd qsa62WRk3+PhpgdTrhHwoihCgBLJMDE1wdhxq6jK7ZdNzzHL3AXsbwcTltXYOiJavA/5 monU0LA4gfBz+gF5AQGwdzB0UGSK7kcKOQV2IdMta3gu8jknH03EnevMJccSgTrmUCrY nPuY/sicswi5dI1Hi43l0SFuqpO+OZrEspfUyw408t6cP8NbJrM4tddg/VDSbGiMHXLq 2Mjvx73IptML1EKkxHA+razaHAbs+ujaNl3ZNwPsUS9T/XRtVPiF4+nJu8sXp8XDTdp8 BoLg== X-Gm-Message-State: ALyK8tLe0kUUy7ejJknBB7Kngmxhbc6K33uZrZ699TQ/wkL/NmJfozjoESzafnTV38ZORyAKUnj5JxcTs3j4Ww== X-Received: by 10.176.69.210 with SMTP id u76mr14968932uau.16.1469081741569; Wed, 20 Jul 2016 23:15:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.20.2 with HTTP; Wed, 20 Jul 2016 23:15:41 -0700 (PDT) In-Reply-To: <20160720102939.GA52214@elstar.local> References: <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> <6ae6e435-dfff-f058-446e-546ba11b9ddf@gmail.com> <20160708123109.GA23658@elstar.local> <20160711152030.GA33482@elstar.local> <246b2e02-3ae2-984b-af33-f3527a9a7a25@gmail.com> <20160720102939.GA52214@elstar.local> From: Andy Bierman Date: Wed, 20 Jul 2016 23:15:41 -0700 Message-ID: To: Juergen Schoenwaelder , Alexandre Petrescu , eman mailing list , "Plymoth Nilsson Anders (anders@telhoc.se)" , Erkki Harjula , BEN HADJ SAID Siwar , bjorn.landfeldt@eit.lth.se Content-Type: multipart/alternative; boundary=94eb2c11c3045a4bf405381f3f72 Archived-At: Subject: Re: [eman] YANG model for battery MIB X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2016 06:15:45 -0000 --94eb2c11c3045a4bf405381f3f72 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Jul 20, 2016 at 3:29 AM, Juergen Schoenwaelder < j.schoenwaelder@jacobs-university.de> wrote: > On Wed, Jul 20, 2016 at 10:40:04AM +0200, Alexandre Petrescu wrote: > > Le 11/07/2016 =C3=A0 17:20, Juergen Schoenwaelder a =C3=A9crit : > > > On Mon, Jul 11, 2016 at 05:17:29PM +0200, Alexandre Petrescu wrote: > > > > We will have to check this, but for now I must say I did not know > that > > > > one could generate the YANG model simply by issuing that command. > > > > > > > > Quickly skimming through it seems that 'smidump -f yang BATTERY-MIB= ' > > > > would not add a contact address of the person who performed the > translation. > > > > > > Yep, why would it. The key is automated translations in order to avoi= d > > > having to republish stuff. > > > > I just noticed in the DHC WG meeting that there is this YANG Data Model > for > > DHCPv6 Configuration draft-ietf-dhc-dhcpv6-yang-03 > > > > And I suspect there are already many MIBs for DHCPv6 on major platforms= . > > > > This gives some credit to the idea to lay down the smidump output in an > > Internet Draft. > > > > Alex > > PS: I am in Berlin and willing to meet talk about YANG model for batter= y > > MIB. > > The BATTERY-MIB is not configuration; the IETF does not have the > resources to republish ~100 mostly read-only MIB modules rendered in > YANG. This is why RFC 6643 was created. > big +1 However it would be really useful to have those converted MIB modules available. Perhaps the next hackathon can have a project to convert the most relevant MIB modules to YANG and put them in github https://github.com/YangModels/yang > /js > > Andy > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > --94eb2c11c3045a4bf405381f3f72 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Jul 20, 2016 at 3:29 AM, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
On Wed, Jul 20, 2016 at 10:40:04AM +0200, Alexandre Petrescu wrote= :
> Le 11/07/2016 =C3=A0 17:20, Juergen Schoenwaelder a =C3=A9crit :
> > On Mon, Jul 11, 2016 at 05:17:29PM +0200, Alexandre Petrescu wrot= e:
> > > We will have to check this, but for now I must say I did not= know that
> > > one could generate the YANG model simply by issuing that com= mand.
> > >
> > > Quickly skimming through it seems that 'smidump -f yang = BATTERY-MIB'
> > > would not add a contact address of the person who performed = the translation.
> >
> > Yep, why would it. The key is automated translations in order to = avoid
> > having to republish stuff.
>
> I just noticed in the DHC WG meeting that there is this YANG Data Mode= l for
> DHCPv6 Configuration draft-ietf-dhc-dhcpv6-yang-03
>
> And I suspect there are already many MIBs for DHCPv6 on major platform= s.
>
> This gives some credit to the idea to lay down the smidump output in a= n
> Internet Draft.
>
> Alex
> PS: I am in Berlin and willing to meet talk about YANG model for batte= ry
> MIB.

The BATTERY-MIB is not configuration; the IETF does not have the
resources to republish ~100 mostly read-only MIB modules rendered in
YANG. This is why RFC 6643 was created.


big +1

However it would be really = useful to have those converted MIB modules
available.=C2=A0 Perha= ps the next hackathon can have a project to convert
the most rele= vant MIB modules to YANG and put them in github

https://github.com/YangModels/= yang



/js


Andy
=C2=A0
--
Juergen Schoenwaelder=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Jacobs Univer= sity Bremen gGmbH
Phone: +49 421 200 3587=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Campus Ring 1 | 28= 759 Bremen | Germany
Fax:=C2=A0 =C2=A0+49 421 200 3103=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<http://www.jacobs-university.de/>

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

--94eb2c11c3045a4bf405381f3f72-- From nobody Fri Jul 22 06:29:20 2016 Return-Path: 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 4C4E512D149 for ; Fri, 22 Jul 2016 06:29:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 6Pvlht-mCkff for ; Fri, 22 Jul 2016 06:29:16 -0700 (PDT) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45F8B12B049 for ; Fri, 22 Jul 2016 06:29:16 -0700 (PDT) Received: by mail-lf0-x22a.google.com with SMTP id b199so85740105lfe.0 for ; Fri, 22 Jul 2016 06:29:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=6a4pJ/mXl1nFbSF3jdkUctDA4kE0nxmwq4OJKKNwF0A=; b=RiLI4LDpuF3fICDK9ybxyZMS8X0JuRZCdRrt6oClA7qKoRsPxsBnIgoUBAvxc57lyu lk3E3aP+JwXfV8dzYm/MDCpQoZARt1zePRY8N4wY6AXJoP+EcFF8MpwkxfE/CCjxPI2Y 0DWLuNgOIODhyk5p/6Zs/eGdj1OS2bafgXep7g0opxxmQQzdFJqoPZ6RWOiAL2fi7214 g6Oo0ZpPYxHNlwQhA/SJD04VF0ARI8qnZmuZjhnGlSJLCzgrKheRTAud4BI4bcUbUBgV Q2oCVB/xtMEP0g0pNMBLlHtdKRhlHypml7L4Iij+C7LW9Mmx2X+dFOTPLYU6MXMAs1kK C99w== 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; bh=6a4pJ/mXl1nFbSF3jdkUctDA4kE0nxmwq4OJKKNwF0A=; b=UJS9pV7xio8oFu8McBop9vRvKwGrg0TdsyNlIHCkGTz5z+t68Wp4155iKXS62pqiOv KBWY7G2IDoaeO0wmrjHvsEdIMDQ7IpDohe594nwjFDoWnfKB8MPWdH3InGEz3dRS+mBV mD73iRD16JpGE+pHFptzGtDb+/ntbf0Q5NtLQzvncFHigHjngFmMMzjNWOy4M6d/zOFl qeS8mJrHW7pnNVigYfmInfPWQwcdDeZwK1zhi3bNbNIeIpgtIFVuztnVuGfASCCzXddu sTh1UFzJQCoE46m6LIUHnkcFBYEaz2zL0+9h3OGgwJ+YfPzx9LXuc4bWJPXXFJFXljXI XXlA== X-Gm-Message-State: AEkoouuIBoL1bWCm8K6FELkMD63TSow6zY3Bp99zbzXK8hMKM8FopOfTHufKI9cK6md5J5r6D6xGy2n0x4cefA== MIME-Version: 1.0 X-Received: by 10.25.31.9 with SMTP id f9mr2710468lff.34.1469194154267; Fri, 22 Jul 2016 06:29:14 -0700 (PDT) Received: by 10.25.35.88 with HTTP; Fri, 22 Jul 2016 06:29:13 -0700 (PDT) Received: by 10.25.35.88 with HTTP; Fri, 22 Jul 2016 06:29:13 -0700 (PDT) In-Reply-To: References: <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> <6ae6e435-dfff-f058-446e-546ba11b9ddf@gmail.com> <20160708123109.GA23658@elstar.local> <20160711152030.GA33482@elstar.local> <246b2e02-3ae2-984b-af33-f3527a9a7a25@gmail.com> <20160720102939.GA52214@elstar.local> Date: Fri, 22 Jul 2016 15:29:13 +0200 Message-ID: From: Rolf Winter To: Andy Bierman Content-Type: multipart/alternative; boundary=001a11402784abd9a00538396b15 Archived-At: Cc: eman@ietf.org Subject: Re: [eman] YANG model for battery MIB X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2016 13:29:19 -0000 --001a11402784abd9a00538396b15 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Great suggestion. Maybe our AD can make sure that authors of new MIB modules will add their converted YANG modules to that repository as part of the publishing process. On 21 Jul 2016 8:15 a.m., "Andy Bierman" wrote: > > > On Wed, Jul 20, 2016 at 3:29 AM, Juergen Schoenwaelder < > j.schoenwaelder@jacobs-university.de> wrote: > >> On Wed, Jul 20, 2016 at 10:40:04AM +0200, Alexandre Petrescu wrote: >> > Le 11/07/2016 =C3=A0 17:20, Juergen Schoenwaelder a =C3=A9crit : >> > > On Mon, Jul 11, 2016 at 05:17:29PM +0200, Alexandre Petrescu wrote: >> > > > We will have to check this, but for now I must say I did not know >> that >> > > > one could generate the YANG model simply by issuing that command. >> > > > >> > > > Quickly skimming through it seems that 'smidump -f yang BATTERY-MI= B' >> > > > would not add a contact address of the person who performed the >> translation. >> > > >> > > Yep, why would it. The key is automated translations in order to avo= id >> > > having to republish stuff. >> > >> > I just noticed in the DHC WG meeting that there is this YANG Data Mode= l >> for >> > DHCPv6 Configuration draft-ietf-dhc-dhcpv6-yang-03 >> > >> > And I suspect there are already many MIBs for DHCPv6 on major platform= s. >> > >> > This gives some credit to the idea to lay down the smidump output in a= n >> > Internet Draft. >> > >> > Alex >> > PS: I am in Berlin and willing to meet talk about YANG model for batte= ry >> > MIB. >> >> The BATTERY-MIB is not configuration; the IETF does not have the >> resources to republish ~100 mostly read-only MIB modules rendered in >> YANG. This is why RFC 6643 was created. >> > > > big +1 > > However it would be really useful to have those converted MIB modules > available. Perhaps the next hackathon can have a project to convert > the most relevant MIB modules to YANG and put them in github > > https://github.com/YangModels/yang > > > >> /js >> >> > Andy > > >> -- >> Juergen Schoenwaelder Jacobs University Bremen gGmbH >> Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany >> Fax: +49 421 200 3103 >> >> _______________________________________________ >> eman mailing list >> eman@ietf.org >> https://www.ietf.org/mailman/listinfo/eman >> > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > > --001a11402784abd9a00538396b15 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Great suggestion. Maybe our AD can make sure that authors of= new MIB modules will add their converted YANG modules to that repository a= s part of the publishing process.


On 21 Jul 2016 8:= 15 a.m., "Andy Bierman" <andy@yumaworks.com> wrote:


On Wed, Jul 20, 2016 at 3:29 AM, Juergen Schoenwaelder <= span dir=3D"ltr"><j.schoenwaelder@jacobs-university.de> wro= te:
On Wed, Jul 20, 2016 at 10:40:04AM +0200, Alexandre= Petrescu wrote:
> Le 11/07/2016 =C3=A0 17:20, Juergen Schoenwaelder a =C3=A9crit :
> > On Mon, Jul 11, 2016 at 05:17:29PM +0200, Alexandre Petrescu wrot= e:
> > > We will have to check this, but for now I must say I did not= know that
> > > one could generate the YANG model simply by issuing that com= mand.
> > >
> > > Quickly skimming through it seems that 'smidump -f yang = BATTERY-MIB'
> > > would not add a contact address of the person who performed = the translation.
> >
> > Yep, why would it. The key is automated translations in order to = avoid
> > having to republish stuff.
>
> I just noticed in the DHC WG meeting that there is this YANG Data Mode= l for
> DHCPv6 Configuration draft-ietf-dhc-dhcpv6-yang-03
>
> And I suspect there are already many MIBs for DHCPv6 on major platform= s.
>
> This gives some credit to the idea to lay down the smidump output in a= n
> Internet Draft.
>
> Alex
> PS: I am in Berlin and willing to meet talk about YANG model for batte= ry
> MIB.

The BATTERY-MIB is not configuration; the IETF does not have the
resources to republish ~100 mostly read-only MIB modules rendered in
YANG. This is why RFC 6643 was created.


big +1

However it would be really = useful to have those converted MIB modules
available.=C2=A0 Perha= ps the next hackathon can have a project to convert
the most rele= vant MIB modules to YANG and put them in github

https://gith= ub.com/YangModels/yang



/js


Andy
=C2=A0
--
Juergen Schoenwaelder=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Jacobs Univer= sity Bremen gGmbH
Phone: +49 421 200 3587=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Campus= Ring 1 | 28759 Bremen | Germany
Fax:=C2=A0 =C2=A0+49 421 200 3103=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0<http://www.jacobs-university.de/>

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


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

--001a11402784abd9a00538396b15-- From nobody Sat Jul 23 15:12:43 2016 Return-Path: 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 0430812D611 for ; Sat, 23 Jul 2016 15:12:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.807 X-Spam-Level: X-Spam-Status: No, score=-15.807 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com 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 puRaNLoEZngE for ; Sat, 23 Jul 2016 15:12:39 -0700 (PDT) Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0D5012D1E3 for ; Sat, 23 Jul 2016 15:12:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12296; q=dns/txt; s=iport; t=1469311959; x=1470521559; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=gWa7K4PLb2NRLFlJV0N3Cop9z/yVhKHSmOk6pOsdy9E=; b=hS0wAhUHKdnLtoHXK97tj0vYpDy5/vDWgwQqiujxkR1HMP8Vvpy4lUyD k/B+slGnssKpqbLTDwXCl9Ai9RH4f3CR+MXVEjoCnp6bwMotGe6nnh6e5 qg21YiHxtG+yLaiE/Nfk+HCYdLlxqsKJc3YOQ80bS+GPu3qjqndA5UT6z 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DbBwBh6ZNX/xbLJq1aA4QVKlKzXocBI?= =?us-ascii?q?4V5AoF0AQEBAQEBXieEXQEFAQFsCw4CCxAIJwcbDB8RBgEMBgIBAYgsDrgKAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEBHAWGJYF4CIJNhAxAFSaFFAWZJoYWgnuFXYFsh?= =?us-ascii?q?2cjhUWQIVSCCxyBTjoyh2oBAQE?= X-IronPort-AV: E=Sophos;i="5.28,411,1464652800"; d="scan'208,217";a="637195128" Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Jul 2016 22:12:36 +0000 Received: from [10.61.98.115] (dhcp-10-61-98-115.cisco.com [10.61.98.115]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u6NMCaWT017586; Sat, 23 Jul 2016 22:12:36 GMT To: Rolf Winter , Andy Bierman References: <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> <6ae6e435-dfff-f058-446e-546ba11b9ddf@gmail.com> <20160708123109.GA23658@elstar.local> <20160711152030.GA33482@elstar.local> <246b2e02-3ae2-984b-af33-f3527a9a7a25@gmail.com> <20160720102939.GA52214@elstar.local> From: Benoit Claise Message-ID: <92bfef61-599d-369b-6771-545935a0ba87@cisco.com> Date: Sun, 24 Jul 2016 00:12:36 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------034526D1402CB4AF299C225C" Archived-At: Cc: eman@ietf.org Subject: Re: [eman] YANG model for battery MIB X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jul 2016 22:12:42 -0000 This is a multi-part message in MIME format. --------------034526D1402CB4AF299C225C Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit On 7/22/2016 3:29 PM, Rolf Winter wrote: > > Great suggestion. Maybe our AD can make sure that authors of new MIB > modules will add their converted YANG modules to that repository as > part of the publishing process. > We could try, but the rate of MIB modules production at the IETF slows down. Regards, B. > > On 21 Jul 2016 8:15 a.m., "Andy Bierman" > wrote: > > > > On Wed, Jul 20, 2016 at 3:29 AM, Juergen Schoenwaelder > > wrote: > > On Wed, Jul 20, 2016 at 10:40:04AM +0200, Alexandre Petrescu > wrote: > > Le 11/07/2016 à 17:20, Juergen Schoenwaelder a écrit : > > > On Mon, Jul 11, 2016 at 05:17:29PM +0200, Alexandre > Petrescu wrote: > > > > We will have to check this, but for now I must say I did > not know that > > > > one could generate the YANG model simply by issuing that > command. > > > > > > > > Quickly skimming through it seems that 'smidump -f yang > BATTERY-MIB' > > > > would not add a contact address of the person who > performed the translation. > > > > > > Yep, why would it. The key is automated translations in > order to avoid > > > having to republish stuff. > > > > I just noticed in the DHC WG meeting that there is this YANG > Data Model for > > DHCPv6 Configuration draft-ietf-dhc-dhcpv6-yang-03 > > > > And I suspect there are already many MIBs for DHCPv6 on > major platforms. > > > > This gives some credit to the idea to lay down the smidump > output in an > > Internet Draft. > > > > Alex > > PS: I am in Berlin and willing to meet talk about YANG model > for battery > > MIB. > > The BATTERY-MIB is not configuration; the IETF does not have the > resources to republish ~100 mostly read-only MIB modules > rendered in > YANG. This is why RFC 6643 was created. > > > > big +1 > > However it would be really useful to have those converted MIB modules > available. Perhaps the next hackathon can have a project to convert > the most relevant MIB modules to YANG and put them in github > > https://github.com/YangModels/yang > > > > /js > > > Andy > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 > Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman --------------034526D1402CB4AF299C225C Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit
On 7/22/2016 3:29 PM, Rolf Winter wrote:

Great suggestion. Maybe our AD can make sure that authors of new MIB modules will add their converted YANG modules to that repository as part of the publishing process.

We could try, but the rate of MIB modules production at the IETF slows down.

Regards, B.

On 21 Jul 2016 8:15 a.m., "Andy Bierman" <andy@yumaworks.com> wrote:


On Wed, Jul 20, 2016 at 3:29 AM, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
On Wed, Jul 20, 2016 at 10:40:04AM +0200, Alexandre Petrescu wrote:
> Le 11/07/2016 à 17:20, Juergen Schoenwaelder a écrit :
> > On Mon, Jul 11, 2016 at 05:17:29PM +0200, Alexandre Petrescu wrote:
> > > We will have to check this, but for now I must say I did not know that
> > > one could generate the YANG model simply by issuing that command.
> > >
> > > Quickly skimming through it seems that 'smidump -f yang BATTERY-MIB'
> > > would not add a contact address of the person who performed the translation.
> >
> > Yep, why would it. The key is automated translations in order to avoid
> > having to republish stuff.
>
> I just noticed in the DHC WG meeting that there is this YANG Data Model for
> DHCPv6 Configuration draft-ietf-dhc-dhcpv6-yang-03
>
> And I suspect there are already many MIBs for DHCPv6 on major platforms.
>
> This gives some credit to the idea to lay down the smidump output in an
> Internet Draft.
>
> Alex
> PS: I am in Berlin and willing to meet talk about YANG model for battery
> MIB.

The BATTERY-MIB is not configuration; the IETF does not have the
resources to republish ~100 mostly read-only MIB modules rendered in
YANG. This is why RFC 6643 was created.


big +1

However it would be really useful to have those converted MIB modules
available.  Perhaps the next hackathon can have a project to convert
the most relevant MIB modules to YANG and put them in github




/js


Andy
 
--
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

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


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



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

--------------034526D1402CB4AF299C225C--