Re: [OPSAWG] side meeting #119: Power Metrics: concrete usage example

Jari Arkko <jari.arkko@gmail.com> Wed, 27 March 2024 00:09 UTC

Return-Path: <jari.arkko@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0551CC14CF1C; Tue, 26 Mar 2024 17:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UzC-2AZ14YlT; Tue, 26 Mar 2024 17:09:00 -0700 (PDT)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 251FBC14F70F; Tue, 26 Mar 2024 17:08:55 -0700 (PDT)
Received: by mail-pl1-x62f.google.com with SMTP id d9443c01a7336-1e00d1e13a2so38928675ad.0; Tue, 26 Mar 2024 17:08:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711498134; x=1712102934; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=LpKJ0iEn6kJf1IqvE7kgYhkTL1hItoVdB9+J0IKxkzQ=; b=SY+yYL0uRVQfbVuMSrUmgu26ljB5exDs8tMvdnpMcjkA3OeqExegUrI4nZZ/DfI3Rp EwolcPnstpYGNVkaURkm7voboS3bBa93DjEBcy1rhv/xv8OSS88WAld3gGMQw4IUB7zV CgfEDoOeHu19O/WuMsvgwsRHNcn7jsUjU7yWBgL5adrJD9cDhN3DZGYwf8O8jqXTKFh3 OmxgQeqVpD/AonO6FdVnS9YCLzHFqbE43/BaYr1jDikg6qQHmav8B3U1hygMh+nlFWiB Xb586BJmb9oZgsdDvsqKmssQs5cAwYf6tJelEkW1hcMgRi0zuW54WjV7gFMMeWFBZb1y BL7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711498134; x=1712102934; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=LpKJ0iEn6kJf1IqvE7kgYhkTL1hItoVdB9+J0IKxkzQ=; b=lnYJNvmbXoEcudzcOJMpAg0wJI0x8LkN1bdWoAQobe7szfOgNuIsK6ae8jgbg2T8F0 lHrp7kmO1l+yGgDTFWiIvxRc0WpZ4hIhFofnEEX3z1ZmFZdpdyRdefKMLOSldexCuwCE Xc9tPzvYWEgmWughPZwl1Wx8WR82vk0Uq0/OUgY1sKZDSRUI4QQ1wJlbHmIrncFAyA4B vsuXgRn7ss7LuLGMPzGqcs9I2rSrJX7jgw0rHAfvKFRd7c3CDDPpaxNLDM5dRulXLo2w V+YkBf9qvgtxeTVNvrh6+2bz+MXn11C88gjiUgZVYEoQGyAujBeKYSw6YQGMi5PpEvYS KOtw==
X-Forwarded-Encrypted: i=1; AJvYcCXYM6VHYeB3RKthKh9dICNeuRZk+97LZaF7/c9o6f3fUXMYArNlDFVD7m+ttsEUDPqQbO6vU9rIfcf8ZMpIIr7yu1qWy4nelI+/ZXKkaF7Ntpg395rN+c0vzQzUQiJsbFRoYjJDkrt3GdO1aA==
X-Gm-Message-State: AOJu0Yx4B8wcNUvXeYN0HQoTK+qSxiglafg0LFLq/mH2uInm2BShT1on fmwbuFcDqAQBzWgz7E5lVg5cZxAsFr4hpOR9XHW8/RBcRysYpRT1
X-Google-Smtp-Source: AGHT+IERul+8teCkI+T634mzApKHRC1RoyK2Kd9VM8QF/07ZC4zqsU7ZMXNf6TsgOKdEUrCTODfOxQ==
X-Received: by 2002:a17:902:e884:b0:1e0:b3a4:ba52 with SMTP id w4-20020a170902e88400b001e0b3a4ba52mr1587806plg.24.1711498133782; Tue, 26 Mar 2024 17:08:53 -0700 (PDT)
Received: from smtpclient.apple (194-223-161-170.static.tpgi.com.au. [194.223.161.170]) by smtp.gmail.com with ESMTPSA id im16-20020a170902bb1000b001e09322cd01sm7703949plb.45.2024.03.26.17.08.48 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Mar 2024 17:08:52 -0700 (PDT)
From: Jari Arkko <jari.arkko@gmail.com>
Message-Id: <BCDEFF28-03A9-4D62-A474-B4662BBE2AF6@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2CAFB90E-9B1E-47D9-A73D-28AA442B12CB"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Date: Wed, 27 Mar 2024 10:08:35 +1000
In-Reply-To: <LV8PR11MB853621C7E833FDB26C6B729EB5362@LV8PR11MB8536.namprd11.prod.outlook.com>
Cc: Carlos Pignataro <cpignata@gmail.com>, "Marisol Palmero Amador (mpalmero)" <mpalmero=40cisco.com@dmarc.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "e-impact@ietf.org" <e-impact@ietf.org>, "inventory-yang@ietf.org" <inventory-yang@ietf.org>, Alexander Clemm <alex@clemm.org>, "Alberto Rodriguez-Natal (natal)" <natal@cisco.com>, Ron Bonica <rbonica@juniper.net>, Mahesh Jethanandani <mjethanandani@gmail.com>, "Ali Rezaki (Nokia)" <ali.rezaki@nokia.com>, "Suresh Krishnan (sureshk)" <sureshk@cisco.com>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>
References: <DM4PR11MB52778685A92225856D21BB16C5282@DM4PR11MB5277.namprd11.prod.outlook.com> <CACe62Mnii4FMwkYAtvDHPEriy_BmEx4MtLtte1s1KKxFShJHZg@mail.gmail.com> <LV8PR11MB853621C7E833FDB26C6B729EB5362@LV8PR11MB8536.namprd11.prod.outlook.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/pcUxmzz4bj8LOeHOSQsTt61MAU8>
Subject: Re: [OPSAWG] side meeting #119: Power Metrics: concrete usage example
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2024 00:09:04 -0000

Rob,

One of the challenges we appear to be having is that the working groups that should potentially care about some of the metrics work for instance are busy. I find that somewhat unfortunate, but it may be what it is. The IAB program is not a place for us to standardize protocols or data models, though of course it can be a place to discuss what work is happening in the IETF or is not but should.  So if the WGs like OPSAWG or IVY have little bandwidth for the the work that needs to happen, then new IETF activities should be created for it.

I have two comments to consider though:

1. Sometimes if the work is clear enough but no room in an existing working group, WGs can also created directly. Not sure if this is feasible in this case. 

2. I’d be happy to contribute to a BoF personally. But it is *very* important that it be scoped extremely tightly. This is a topic where we can easily attract any level of discussion, and BoF proposals with clear, concrete goals (”add this YANG thing”) succeed, whereas proposals with vague or unclear or debated scopes may not proceed as fast or at all.

Jari

> Rob Wilton (rwilton) <rwilton@cisco.com> kirjoitti 26.3.2024 kello 0.48:
> 
> Hi Carlos,
>  
> During IETF 119, I had a couple of discussions with Suresh and Mahesh regarding how we actual get some of the short term “green” related work happening in IETF to get critical mass and cross review and get published in the short term.  This seemed to somewhat culminate during the Power Metrics side meeting where it is clear that:
> Various folks, representing different organizations, have various drafts related to Green networking.
> Currently these drafts are spread out to different working groups, have various amounts of overlap, and it is unclear that they currently have a good homes and sufficient traction in IETF to progress effectively.
> There was support in the meeting to target a WG forming BOF for IETF 120 to create a new WG with a limited targeted charter.
>  
> Hence the proposal from Suresh and I was to try and help coordinate for a WG forming BOF for IETF 120 scoped specifically to work on items that are understood and achievable in the short term.  E.g., roughly, I currently think of this work scope as being: e.g., energy related terminology and definitions (that should try and leverage and reference existing definitions from existing published sources), reporting energy and sustainability at the device and network layer via operational YANG models, and to facilitate configuration or YANG RPCs to influence and optimise power usage on network devices.  Longer term energy efficiency and Green networking goals are intended to be out of scope for the proposed WG’s initial charter, and should continue to be discussed as part of the E-Impact IAB program.  The exact scope of the charter would be worked out between the interested parties in the coming weeks.
> 
> I’m happy to try and help this work gain traction within the IETF.  I appreciate that several of the proponents for this work are also from Cisco, but I have no vested interest other than trying to help the industry take small steps that may help improve energy efficiency in networks (e.g., reporting power usage, and as Tony suggests by selectively powering off ports or linecards) to try and help mitigate some of the impacts of the Internet on climate change.
> 
> To that end the proposed next steps from that side meeting were:
> 
> For me to request the creation of new open “green-bof” mailing list from Mahesh (hopefully should be done over the next few days).
> I asked for, and received, permission to subscribe those who attended the side meeting, but once created, I also intended to circulate the existence of the mailing list to e-impact, and other places where related discussions have been taking place, so that others can join.
> To create a github location where we can reference drafts and collecting work on a BOF proposal and draft charter for the WG (which as I stated above, should be narrowly scoped to only the work that is well understood and achievable in the short term).  If I can get this under the IETF github space, great, otherwise I can host a personal github.  I’m already checking with Mahesh on the feasibility of the github location being IETF hosted.
> Once the mailing list is up and running, the next step is to arrange a few virtual meetings to try and gain consensus on the proposed initial scope of the WG, and to start reviewing and pulling together the BOF proposal, and charter text.
> To submit a BOF request for IETF 120.  The key dates being:
> Warn the IESG and Secretariat that we are hoping for a BOF by 22nd April (note Mahesh is already aware and this has already been informally flagged to the IESG)
> Get the initial BOF submission in before 5th May
> Refine the BOF proposal based on feedback received, and update by 7th June
> 14th June, we hear back whether the BOF has been approved for IETF 120
> Continue prepping slides, etc, for the BOF, running up to early July
> In my experience, despite it being 4 months between IETF meetings, the time invariably disappears quickly, so I think that we need to frontload the BOF preparation effort to achieve consensus at IETF 120 for creating a working group.
>  
> Anyone else in the side meeting, please feel free to add anything that I have missed, or correct me, if I have misrepresented anything.
>  
> Carlos, hopefully you are also interested in participating in these efforts.  If you have any feedback on the planned approach I would be glad to hear it.
> 
> Regards,
> Rob
>  
>  
> From: OPSAWG <opsawg-bounces@ietf.org> on behalf of Carlos Pignataro <cpignata@gmail.com>
> Date: Monday, 25 March 2024 at 12:01
> To: Marisol Palmero Amador (mpalmero) <mpalmero=40cisco.com@dmarc.ietf.org>
> Cc: opsawg@ietf.org <opsawg@ietf.org>, e-impact@ietf.org <e-impact@ietf.org>, inventory-yang@ietf.org <inventory-yang@ietf.org>, Alexander Clemm <alex@clemm.org>, Alberto Rodriguez-Natal (natal) <natal@cisco.com>, Ron Bonica <rbonica@juniper.net>, Mahesh Jethanandani <mjethanandani@gmail.com>, Ali Rezaki (Nokia) <ali.rezaki@nokia.com>, Suresh Krishnan (sureshk) <sureshk@cisco.com>, Jari Arkko <jari.arkko@gmail.com>
> Subject: Re: [OPSAWG] side meeting #119: Power Metrics: concrete usage example
> 
> +Jari
>  
> Hello,
>  
> Suresh, Jari,
>  
> I'm confused by this bullet point:
> •              next steps? E.g. WG coordination/status, form a WG Design Team, call for a BOF?
>  
> Could you please clarify?
>  
> I understood there's no WG (and hence no WG coordination nor status), in favor of the IAB Program. There cannot be a WG Design Team without a WG. I cannot find "design team" or 'BOF" (WG forming or not?) in the minutes of eimpact meetings <https://datatracker.ietf.org/program/eimpact/meetings/>, maybe I missed it.
>  
> Is this an effort parallel to eimpact or a shadow meeting?
>  
> Poweff authors,
>  
> Is Poweff still a Cisco-only effort, as recorded in https://youtu.be/m4vpThE5K9c?feature=shared&t=3534? Verbatim youtube transcript:
> Many of the um products uh that we have uh mainly in Cisco right we are still looking into multivendor and this will be really good for um the participants to um provide feedback how this H um standardization of the data model might impact in your network equipment but um
>  
> Thanks!
>  
> Carlos.
>  
> On Fri, Mar 15, 2024 at 1:30 PM Marisol Palmero Amador (mpalmero) <mpalmero=40cisco.com@dmarc.ietf.org <mailto:40cisco.com@dmarc.ietf.org>> wrote:
> Dear all,
>  
> We have booked a side meeting in Brisbone,  IETF #119
> Thursday 9:00 am local time.
> Headline: Power Metrics: concrete usage example
>  
>  
> Please see the agenda that we are proposing:
>  
> •              Overview of ongoing sustainability work in IETF (everyone contributes)
> •              Brief presentation of sustainability insights/poweff updates, incl. look at a more concrete example
> •              Any other short updates?
> •              next steps? E.g. WG coordination/status, form a WG Design Team, call for a BOF?
>  
>  
> As we would like to leave time to discuss and review **next steps**, for the overview we propose not more than 20 min.
> As authors from specific drafts, please let me know which draft(s) you would like to review, we would like to make sure that we could fit them into the 20 min
>  
> Safe travels, and have a nice weekend
>  
> Marisol Palmero, on behalf of the authors of sustainability insights& poweff drafts
>  
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org <mailto:OPSAWG@ietf.org>
> https://www.ietf.org/mailman/listinfo/opsawg