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

Suresh Krishnan <suresh.krishnan@gmail.com> Thu, 11 April 2024 03:33 UTC

Return-Path: <suresh.krishnan@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 CBD58C14F6B1; Wed, 10 Apr 2024 20:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.085
X-Spam-Level:
X-Spam-Status: No, score=-7.085 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_PDS_SHORTFWD_URISHRT_QP=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 0Y4iyZ1r7hki; Wed, 10 Apr 2024 20:33:04 -0700 (PDT)
Received: from mail-yw1-x1134.google.com (mail-yw1-x1134.google.com [IPv6:2607:f8b0:4864:20::1134]) (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 3146CC14F60F; Wed, 10 Apr 2024 20:33:04 -0700 (PDT)
Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-614ec7ee902so75521167b3.2; Wed, 10 Apr 2024 20:33:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712806383; x=1713411183; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ii6zyW3DY6vVEYHLIpfkMvTgUt3lVW6qaCyv6c0xs3E=; b=U5Sb3PuBkN7ju6ViwbOnA+QG7ZGzlxDVEpiPNkzOPHKufo25hnynQg1uNJM4DtX9he k1V/rJZUDsKfeaMg7bQRJjwwk20PO+vm1DV0lo1I4SThJ5Vg5BHfyeN/cX5TrxaD3PLV LZxYbHdnlfJmTuH4Z1eeqC72RvZfKzSts8ZFO1mo9kLcQSbJtKF2E9bsVxJYS84xkp68 Dw/zxqjDaZYqU1h2D3wtu1hRL9EfetRw99q54OEAGgkJtTv7D3GV/fzWnmrNcWYgF5KL 3vRvS7Npp1bu+Oo1qIbLtVqzu0tsZAekxR/9rLdASfKPnvFYXFpLSruRLdXJ9gTaytIj 430g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712806383; x=1713411183; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ii6zyW3DY6vVEYHLIpfkMvTgUt3lVW6qaCyv6c0xs3E=; b=EEPB43Uk9jeXyy9nl4cSv0MYgBMvONboerU0R+yx8HRUKY48BsVvJkfsBlmDR2+hkM 1PqAZeKoesvp0nkT+HxKT4Iw8nuyGtSQdRTgKRwsb7eDJHEmK2eovxffxd27IXZVLuQf iX/9tG9dwV6gFukQozFogeq9w8SG6aqK/6GjBJopanrVztwzwJ3t/QXrVGPIW99wrnkb fee7tEB9c58nkDQXkPbJgpcX1v00OkzR+gGgpoY19wQlvMwDoNuCDznQ2H711dl8EOuK RYp8dfkjHlu9+5+FbW+mjT1O6+uB2QyEfn1enZZmYWJR8jGLqOokrHlTPKZHAe1ytbuB Y37g==
X-Forwarded-Encrypted: i=1; AJvYcCX+WuudH2QZjI4qOE7x0eVCuQJTd/4WIAAA3J552VF1614Ggwl7WxwELJ9FrGAmqaIMj7s77FHBQXOTgeRySPLdMT9qHcDk16vd/xasbC+dbbern98+iffOIJ/kdlECNJ2YocEq9VyLIgdeKQ==
X-Gm-Message-State: AOJu0YylFYAan26j/Mb9jGbcj7oBsU6dMr/lEgNvtbLPuskJMj+lO+5N rs7LJ4MJo54myV0jgLo4uePUfLGJF6GobBp6oyq3BZjxreeIQHb9MA1zES8w
X-Google-Smtp-Source: AGHT+IFFLVi4I/ilThXfklUub5FDsGrqy7h6FEnD9iIDTCfBWivr4kZMOEpWBcyGTxBAIapOW1lhcA==
X-Received: by 2002:a81:e946:0:b0:609:fff2:3bbc with SMTP id e6-20020a81e946000000b00609fff23bbcmr4174057ywm.49.1712806382877; Wed, 10 Apr 2024 20:33:02 -0700 (PDT)
Received: from smtpclient.apple (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id x12-20020a81e70c000000b0060a16fb9209sm123652ywl.115.2024.04.10.20.33.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Apr 2024 20:33:02 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Suresh Krishnan <suresh.krishnan@gmail.com>
In-Reply-To: <CACe62MmbFJPtwz0G2T5Fkmsm6Te58NooE8nXCLv8yU7gPTgCbQ@mail.gmail.com>
Date: Wed, 10 Apr 2024 23:32:51 -0400
Cc: "Suresh Krishnan (sureshk)" <sureshk@cisco.com>, "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-Transfer-Encoding: quoted-printable
Message-Id: <A3F3804B-DE96-459F-B583-5B0050A787AD@gmail.com>
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> <CACe62MmbFJPtwz0G2T5Fkmsm6Te58NooE8nXCLv8yU7gPTgCbQ@mail.gmail.com>
To: Carlos Pignataro <cpignata@gmail.com>
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/64HgEPIm2sIrCYhyLiqNcYZ9Dyk>
Subject: Re: [OPSAWG] [E-impact] 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: Thu, 11 Apr 2024 03:33:08 -0000

Hi Carlos,

> On Apr 10, 2024, at 8:00 AM, Carlos Pignataro <cpignata@gmail.com> wrote:
> 
> Hi, Suresh,
> 
> Thanks for the response, and apologies for my delay!

Yep. No worries.

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

Correct. There was no e-impact program meeting in Brisbane. 

> and the goal was to push drafts through the respective WGs and not through a WG-forming BOF:

Toerless did mention that some of the draft authors were thinking of a side meeting in Brisbane and it was not official.

>         • 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?"

Marisol and Jan organized the side meeting and sent the invites fairly wide to the WGs where the concerned drafts were previously discussed. Since both of them were remote, I am listed as a contact in case there were any local issues in the meeting room. 

>     • 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)?

There is no green WG yet. There will hopefully be a green *BOF* in Vancouver and the sponsoring AD along with the IESG will decide whether a WG needs to be formed or if the work needs to be divvied up among existing working groups. I will not be a proponent of this BoF, but I am extremely supportive of the work happening (either in a new working group or in existing working groups).
Also, E-impact cannot and will not do standards track work. Any standards track work has to be done in an IETF working group. Hope this is clear.

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

No worries.

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

I was responding to your text where you said "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 :-|”. I was asking *who you asked for a WG, and who shot you down and referred you to the program instead*. As far as I can see, none of the links you provided provide any details regarding this or a proposed charter for this (broader and more e-impactful) WG. 

Thanks
Suresh