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

Carlos Pignataro <cpignata@gmail.com> Wed, 10 April 2024 12:00 UTC

Return-Path: <cpignata@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 0C96CC14F615; Wed, 10 Apr 2024 05:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.594
X-Spam-Level:
X-Spam-Status: No, score=-1.594 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, GB_ABOUTYOU=0.5, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 Alsn1lz9Ij7j; Wed, 10 Apr 2024 05:00:13 -0700 (PDT)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 3E4F2C14F5F1; Wed, 10 Apr 2024 05:00:13 -0700 (PDT)
Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-56e136cbcecso9178168a12.3; Wed, 10 Apr 2024 05:00:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712750411; x=1713355211; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=YSiJBVzrqpg/6k4/U9G3G2zaw/WWd2WAEHPcYhmmeVE=; b=L2HeE1sNMrNbLSglxWwj81H15Znj8oeyGn+v2MS7mD+8lyk2uz+Pnmy3MwxW0fpXWL G4MvVLrE72VwDvZOdWVNYB2lsvDpAh8PfvKgeQr9qKLKHcOIDE3ikue1LZnRtZIpITdp GEE2wyZ31PaM5cNzMc80vuv0Iy3Rt4NwhW9aKxvLfCD0C+4l2Clz/qBZAiiEUeNMQksr tKE4/5OAu/M01gQVQ3f5T8UMkKma7BY1GwvfaitufAsZP/4NhmHFyI1zHws/DWkr4lHV i5fttRNVe1+9o0bcEe/dBXCEYtCdwRDoiLUQpaKbUiOK9+bxC2kOH4azBPHktSc3BQNK 3omw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712750411; x=1713355211; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YSiJBVzrqpg/6k4/U9G3G2zaw/WWd2WAEHPcYhmmeVE=; b=e2vUyfbka1CbNHnwbQenl8eCy56O89KTuDBnrV55mT+cJje+XXJZrOwsEY02VWbtWA hfCnI1s4Rtkb7se72imlNhVCwwTfwHEBvx611uW2sS52SRMjEBbTTr1HePFMqE86lQt6 c4r5hmyF65iNwrJxSxSRVYqP9ztDy0XH364kZS+TtBOaBG8FRbQBV3d8dGIhIJ/f1p59 XAtkOlIR0YZYWV7WXH8buNgdGBLgQBGl6DA9Rp514YeIaUWbPqJKIkwonylPqy9ZMj7X tCe398HtgLA99pdu5c8i+CeJ/FD+zl4jkeqP1rfstkikrDlFaLAg7zBszCVk1il3wncc IbBg==
X-Forwarded-Encrypted: i=1; AJvYcCUQOgwv7NtUWDjnqcgXSnNkrUpCzp+WHalBy70bgy14dnFY0lJPzijeUmhyqpgy2k2NO2ZWL24ZSTfQ2DC0XN+KJxg+2jm2gjnjQAafElM8eZsu9Oo2zx8hmf+gGTnY3LaFxRm3zb9tmd9k4g==
X-Gm-Message-State: AOJu0YxK9YDDzzEzyqD86AI+hgNYYMvVs1Oui5EAtdp35TqixHXaR2Qb N1Yj7hDP/KkfgraHGnCERW+8T3UFGhnMxgNj6PvjOrhqAxgbC7u0yObshLu+CYIU7oJNkLbfR9v n0pIjvYZ+BMU6mYslekOW0Ut/gvU=
X-Google-Smtp-Source: AGHT+IG5ZxzLch4OsvKkfxTxqUeVka6AaZaa711/Kf2Opl4YYlvFUMWBW3DaCCuDs8B7iMArBUK/7tdckYwyiIbDKDY=
X-Received: by 2002:a17:906:b181:b0:a4e:7a8f:2101 with SMTP id w1-20020a170906b18100b00a4e7a8f2101mr1904100ejy.2.1712750410435; Wed, 10 Apr 2024 05:00:10 -0700 (PDT)
MIME-Version: 1.0
References: <DM4PR11MB52778685A92225856D21BB16C5282@DM4PR11MB5277.namprd11.prod.outlook.com> <CACe62Mnii4FMwkYAtvDHPEriy_BmEx4MtLtte1s1KKxFShJHZg@mail.gmail.com> <LV8PR11MB853621C7E833FDB26C6B729EB5362@LV8PR11MB8536.namprd11.prod.outlook.com> <BEF7EDBC-973E-4C97-AB90-D890180A72C0@gmail.com> <PH8PR11MB8288AB37CD13D12619E10D34A1362@PH8PR11MB8288.namprd11.prod.outlook.com>
In-Reply-To: <PH8PR11MB8288AB37CD13D12619E10D34A1362@PH8PR11MB8288.namprd11.prod.outlook.com>
From: Carlos Pignataro <cpignata@gmail.com>
Date: Wed, 10 Apr 2024 08:00:00 -0400
Message-ID: <CACe62MmbFJPtwz0G2T5Fkmsm6Te58NooE8nXCLv8yU7gPTgCbQ@mail.gmail.com>
To: "Suresh Krishnan (sureshk)" <sureshk@cisco.com>
Cc: "Rob Wilton (rwilton)" <rwilton@cisco.com>, "Marisol Palmero Amador (mpalmero)" <mpalmero=40cisco.com@dmarc.ietf.org>, Ops Area WG <opsawg@ietf.org>, E-Impact IETF <e-impact@ietf.org>, "inventory-yang@ietf.org" <inventory-yang@ietf.org>, Alexander Clemm <alex@clemm.org>, "Alberto Rodriguez-Natal (natal)" <natal@cisco.com>, Ronald Bonica <rbonica@juniper.net>, Mahesh Jethanandani <mjethanandani@gmail.com>, "Ali Rezaki (Nokia)" <ali.rezaki@nokia.com>, Jari Arkko <jari.arkko@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000cd93d30615bcc71c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/Hw6gW5jG6Ph1_rZTSpfJxwUWAQ4>
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, 10 Apr 2024 12:00:18 -0000

Hi, Suresh,

Thanks for the response, and apologies for my delay!

Please find my follow-up inline below, and in the meantime, one additional
question to you -- context (my emphasis):

   - I seem to have gotten the impression, from your words and IAB program
   lead slides, that there was no eimpact-related meeting in Brisbane, and the
   goal was to push drafts through the respective WGs and not through a
   WG-forming BOF:
      - https://youtu.be/bfpuL1mkr3U?feature=shared&t=9646
      -
      https://datatracker.ietf.org/meeting/interim-2024-eimpact-02/materials/slides-interim-2024-eimpact-02-sessa-chair-slides-01
         - "Metrics – *Push through the WGs*"
         - "Benchmarking scenario or methodology standardization – *BMWG*"
         - "Carbon-aware routing – *IRTF? TVR?*"
         - "Do an interim session on backcasting what we need to do"
      -
      https://datatracker.ietf.org/meeting/interim-2024-eimpact-02/materials/minutes-interim-2024-eimpact-02-202402161500-00
      - "Suresh mentioned that the dispatch function is certainly in scope
         and depending on the readiness for engineering the work will
end up in the
         IETF or the IRTF. "
      - But then, you were proponent of a side-meeting
      - https://wiki.ietf.org/en/meeting/119/sidemeetings
      - "Power Metrics: concrete usage example", "mpalmero@cisco.com,
         jlindbla@cisco.com, sureshk@cisco.com"
         -  that said " (4) next steps? E.g. *WG coordination/status, form
         a WG Design Team, call for a BOF?*"
      - Even though the IAB slides on IETF119 say:
      - "Short term focus on metrics, benchmarking with dispatch to *relevant
      IETF WGs*"
      https://datatracker.ietf.org/meeting/119/materials/slides-119-iabopen-chair-slides-00
      - "*No in-person program meetings at IETF-119* But feel free to join
      the program mailing list: edm@iab.org and e-impact@iab.org"
      https://datatracker.ietf.org/meeting/119/materials/slides-119-ietf-sessa-119-internet-architecture-board-iab-report-00


*The question*: Are you in favor of running e-impact dispatching work to
existing WGs (as you said), or having a new "green" WG (as proponent)?

Please find follow-up responses inline below:


On Mon, Mar 25, 2024 at 10:02 PM Suresh Krishnan (sureshk) <
sureshk@cisco.com> wrote:

> Hi Carlos,
>
>   Since your message was sent to Rob, I will let him respond, but I wanted
> to chime on some things you said about the e-impact program.
>

Thanks for this -- the salutation did not imply exclusivity.


>
>
> >  On 3/25/24, 5:09 PM, "Carlos Pignataro" cpignata@gmail.com wrote:
>
> > …
>
> >  A second thought is that, while on the surface getting a couple of
> document with ‘green metrics’ is useful and might seem net-positive,
> knee-jerk reacting on tactics misaligned with strategy can further fragment
> the Eimpact work (which already can be characterized as ‘having a hard time
> finding itself’ with work from 2022 and no output).
>
>
>
> The e-impact program was created at the end of August 2023, barely seven
> months ago (and not 2022 as you mentioned). Announcement here:
>
>
>
> https://www.iab.org/announcements/eimpact-program/
>

You are absolutely right, and my mis-writing, with apologies. I meant (and
should have written) the IAB e-impact Workshop, which gave way to the IAB
e-impact Program -- in lieu of forming a WG.


>
>
> You seemed to want to run this program as a WG with set outputs. I had
> responded to you on list to mention that it was not
>
>
>
> https://mailarchive.ietf.org/arch/msg/e-impact/nq7_ToPvRjIm612NwonOqDL-3zI/
>

To be clear, I do not want to run this program -- that is up to the program
leads.

However, the e-impact program chair (i.e., lead) slides show the
acknowledged need for some management, akin a WG. Quoting from
https://datatracker.ietf.org/meeting/interim-2024-eimpact-02/materials/slides-interim-2024-eimpact-02-sessa-chair-slides-01
:
"
● Updating datatracker with all related drafts on this topic
● And a wiki page with drafts on this topic, along with status, next steps,
etc.
"


>
> Quoting relevant part of my mail above:
>
>
>
> “IAB programs don’t have milestones like WGs specifically because of the
> unclear nature of the space they are exploring. If you recall the initial
> meeting with the IAB regarding creation of the program that you
> participated in, this was something that was very clearly stated by various
> members of the IAB. If the work that needs to be done is clear it will be
> dispatched to a WG, an RG or if no relevant space exists to a BoF or
> proposed RG.”
>
>
>
> >  A third thought is that we had asked for a (broader and more
> e-impactful) WG a year ago, and that was shot down in favor of this IAB
> Program :-|
>
>
>
> Care sharing more info about this. Who did you ask for a WG and when? I am
> surprised because Jari and I have always and repeatedly made clear that the
> IAB program will not be doing any standards track work, and will delegate
> the work to IETF WGs/BoFs or IRTF RGs/pRGs. If you had created a proposal
> for a “more e-impactful” WG please feel free to share that proposed charter
> here. I am sure all of us would love to see it.
>

I am very surprised to see this response...

After the Dec 2022 IAB e-impact program, there was the question of Next
Steps, and how to further the work.
The suggestion for a WG (which is a default-gateway answer, so unsurprising
that it was on the table), was captured in the
Chat log:
https://datatracker.ietf.org/meeting/interim-2022-eimpactws-04/materials/slides-interim-2022-eimpactws-04-sessa-webex-chat-log-00
"Concretely, I wonder whether we should be chartering a WG within the IETF
(perhaps a bit like IOTOPS) with a goal of coordinating this work within
the IETF. "
Chair Slides:
https://datatracker.ietf.org/meeting/interim-2022-eimpactws-04/materials/slides-interim-2022-eimpactws-04-sessa-09-workshop-next-steps-01.pdf
"• A new working group ”e-interest group”?"
Unfortunately, there seems to be a 403 and no access to the workshop
mailing list:
https://mailarchive.ietf.org/arch/browse/e-impact-workshop-attendees/

Subsequently this was discussed at IETF116:
https://github.com/cpignata/e-impact/blob/main/ietf116/materials/08-ietf116-environmental-impact-outro.pdf
and
https://github.com/cpignata/e-impact/blob/main/ietf116/materials/00-ietf116-environmental-impact-intro-and-purpose.pdf
"Next Hope: BOF? Others?"



>
>
> > Fifth, and Lastly — frankly I was debating with myself whether to
> mention this privately or not, but since you brought it up and opened the
> topic — another issue. Backdrop: BOF and WG-forming suggestions were sent
> to /dev/null favoring the IAB Program as the solution.
>
>
>
> As mentioned above, please do share more details about your proposal since
> this does not seem right.
>

Above.

Thanks,

Carlos.

>
>
> Thanks
>
> Suresh
>
>
>
> Hi, Rob,
>
>
>
> Thanks for the comprehensive email, and for your desire to support the
> industry towards improved energy efficiency!
>
>
>
>
>
> My first reaction is that this direction seems counter to and in conflict
> with the conclusion and decisions from the IAB Program eimpact “interim”
> from just a month before:
>
>
>
> * See Chair Slides <
> https://datatracker.ietf.org/meeting/interim-2024-eimpact-02/materials/slides-interim-2024-eimpact-02-sessa-chair-slides-01>,
> that codified: " Metrics – Push through the WGs ” (etc. etc.)
>
> * See Minutes <
> https://datatracker.ietf.org/meeting/interim-2024-eimpact-02/materials/minutes-interim-2024-eimpact-02-202402161500-00>,
> that captured: " Suresh agreed and mentioned that the reason for having the
> drafts here is that people to get higher level view since all working
> groups need to have a sustainability angle "
>
>
>
>
>
>
>
> A second thought is that, while on the surface getting a couple of
> document with ‘green metrics’ is useful and might seem net-positive,
> knee-jerk reacting on tactics misaligned with strategy can further fragment
> the Eimpact work (which already can be characterized as ‘having a hard time
> finding itself’ with work from 2022 and no output).
>
>
>
>
>
> There are clear risks like (1) believing that metrics/models are the
> ultimate goal of “eimpact/green’ work, while (as mentioned on eimpact)
> there’s no analysis of the most useful focus area, and (2) forgetting what
> Suresh wrote that many WGs need ‘green’, and this would separate work in a
> corner, as opposed to embedding and integrating it.
>
>
>
>
>
> Fourth, ‘green-bof’ is very very broad, while I understood your desired
> scope to be narrow. This would eclipse eimpact as the shinny new ball, and
> would potentially confuse people on where to participate (outside the lucky
> ones that attended a side meeting)
>
>
>
>
>
> Fifth, and Lastly — frankly I was debating with myself whether to mention
> this privately or not, but since you brought it up and opened the topic —
> another issue. Backdrop: BOF and WG-forming suggestions were sent to
> /dev/null favoring the IAB Program as the solution. What follows is a set
> of factual observations and no judgement or intentionality attached to
> them. But there’s (1) cisco proponents and cisco side-meeting organizer
> despite the eimpact interim, (2) with a Cisco-only I-D [1], (3) a Cisco AD
> meeting with (4) a Cisco IAB Member, in the (5) historically least attended
> meeting, and change direction 180 degrees… Again, no extrapolation or
> conclusion, but even from an appearance or optics perspectives.
>
>
>
>
>
> Yes, I continue contributing in the industry and field to this topic, and
> I would cautious you consider a bigger picture to see what approach(es)
> actually help.
>
>
>
>
>
> I hope and trust these are useful and clear,
>
>
>
>
>
> Best,
>
>
>
>
>
> Carlos.
>
>
>
>
>
> [1] I did not see a response to this:
>
>
>
>
>
> Poweff authors,
>
>
>
>
>
>
>
> Is Poweff still a Cisco-only effort, as recorded in
> https://youtu.be/m4vpThE5K9c?feature=shared&t=3534 <color:blue>? 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 Mar 25, 2024, at 10:48 AM, Rob Wilton (rwilton) <rwilton@cisco.com>
> wrote:
>
>
>
> 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:
>
>
>
>
>
>
>
> 1. For me to request the creation of new open “green-bof” mailing list
> from Mahesh (hopefully should be done over the next few days).
>
> 2. 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.
>
> 3. 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.
>
> 4. 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.
>
> 5. To submit a BOF request for IETF 120. The key dates being:
>
>      1. 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)
>
>      2. Get the initial BOF submission in before 5th May
>
>      3. Refine the BOF proposal based on feedback received, and update by
> 7th June
>
>      4. 14th June, we hear back whether the BOF has been approved for IETF
> 120
>
>      5. Continue prepping slides, etc, for the BOF, running up to early
> July
>
> 6. 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 <color:blue;
> text-decoration:underline>> on behalf of Carlos Pignataro <
> cpignata@gmail.com <color:blue; text-decoration:underline>>
>
> Date: Monday, 25 March 2024 at 12:01
>
> To: Marisol Palmero Amador (mpalmero) <mpalmero=40cisco.com@dmarc.ietf.org
> <color:blue; text-decoration:underline>>
>
> Cc: opsawg@ietf.org <color:blue; text-decoration:underline> <
> opsawg@ietf.org <color:blue; text-decoration:underline>>,
> e-impact@ietf.org <color:blue; text-decoration:underline> <
> e-impact@ietf.org <color:blue; text-decoration:underline>>,
> inventory-yang@ietf.org <color:blue; text-decoration:underline> <
> inventory-yang@ietf.org <color:blue; text-decoration:underline>>,
> Alexander Clemm <alex@clemm.org <color:blue; text-decoration:underline>>,
> Alberto Rodriguez-Natal (natal) <natal@cisco.com <color:blue;
> text-decoration:underline>>, Ron Bonica <rbonica@juniper.net <color:blue;
> text-decoration:underline>>, Mahesh Jethanandani <mjethanandani@gmail.com
> <color:blue; text-decoration:underline>>, Ali Rezaki (Nokia) <
> ali.rezaki@nokia.com <color:blue; text-decoration:underline>>, Suresh
> Krishnan (sureshk) <sureshk@cisco.com <color:blue;
> text-decoration:underline>>, Jari Arkko <jari.arkko@gmail.com
> <color:blue; text-decoration:underline>>
>
> 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 <color:blue; text-decoration:underline>, 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 <color:blue;
> text-decoration:underline>? 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 <color:blue;
> text-decoration:underline>> 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 <color:blue; text-decoration:underline>
>
> https://www.ietf.org/mailman/listinfo/opsawg <color:blue;
> text-decoration:underline>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>