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

"Rob Wilton (rwilton)" <rwilton@cisco.com> Tue, 26 March 2024 10:28 UTC

Return-Path: <rwilton@cisco.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 78813C15152C; Tue, 26 Mar 2024 03:28:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.595
X-Spam-Level:
X-Spam-Status: No, score=-14.595 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54McMomh1GB3; Tue, 26 Mar 2024 03:28:03 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (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 CDCA9C14F6EA; Tue, 26 Mar 2024 03:28:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.com; i=@cisco.com; l=99060; q=dns/txt; s=iport; t=1711448882; x=1712658482; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=0ER9PVGBuHKJvslL82eZUK4hEXh7BxXa0Z4BeDblnJY=; b=gPL7nEUjMfbAsqsbcA0TwA52A516+rObrOsQYvoXqpO9WnZN0YhMdmsd nfQn4NdErtXHiK2t3apEJBKk5znkmmh5dJYFSgaBx9bu373Mdtsoo9aRy PVgFtXcSYyrAfX8kcgPxDqwK4WcABk/tQCMtrmjqBq3ae7n72e37qByxZ M=;
X-CSE-ConnectionGUID: aidNRK41S+upM09dY16ueQ==
X-CSE-MsgGUID: zjMDRfJFTs22Dhosdnz/4Q==
X-IPAS-Result: A0AYAAAaogJmmJxdJa1aGwEBAQEBAQEBBQEBARIBAQEDAwEBAWWBGQMBAQELAYE1MSooegKBF0iEVYNMA4UthkmCIgOBE4pNiBqDdYE4gXuCeYERA1EFDwEBAQ0BAS4BDgcEAQGEQEYCFodvAiY3Bg4BAgQBAQEBAwIDAQEBAQEBAQEGAQEFAQEBAgEHBRQBAQEBAQEBAR4ZBQ4QJ4VsDYZZAQEBAQMBARAIAQIGCj8CCAMQAgEIDgMDAQINFAEGAwICAh4GCxQJCAIEDgUIEAMHgl4BghcUAzEDARCkagGBQAKKKHqBMoEBghYFgT0CAa5eDYJQBoFIAYgHBBoBBWVoAgKBbIZwJxuBSUSBFUKBZko4PoIfQgEBAgEXgQwFAQsHAQMgFQkMCoMlOYIvBIETKVaDN4EjgVUxOidPZYQpIYF3AYUOgQQ4gxJBgVsCgReGZFR4IgN9CARaDRsQHjcREBMNAwhuHQIxOgMFAwQyChIMCx8FEkIDQwZICwMCGgUDAwSBLQULGgIQGgYMJgMDEkkCEBQDOAMDBgMKMS5PQQxQA2cfMQk8DwwaAhsUDSQjAiw+AwkKEAIWAx0WBDARCQsmAyoGNgISDAYGBlwgFgkEIwMIBANQAyBwEQMEGgQLB3aCAIE9BBNHEIEyihYMgzMpgU4pgRKDKQs9A0QdQAMLbT01FBsFBB8BgRkFokt5AgGBaRscRBcXEBwKBAoYCwIDCQgKBhQMLwwFBgsCCBYeARUHBQkKLygCKw+SQigcDoJhAUmLKUeOBJQRcAqEE4pogSSLVYNThisXhAWMfIZ6kRM9ZIgOkFSCVIsfhACRQBMNhQYCBAIEBQIPAQEGgXoka3BwFTuCMwEzEz8ZD1Z0jGINCYEMAQmBJIYyimV4AjkCBwEKAQEDCYhugXIIAQE
IronPort-PHdr: A9a23:AqwM9R1wcXd5v5uRsmDPYFBlVkEcU/3cNwoR7N8gk71RN/jl9JX5N 0uZ7vJo3xfFXoTevupNkPGe87vhVmoJ/YubvTgcfYZNWR4IhYRenwEpDMOfT0yuBPXrdCc9W s9FUQwt5Gm1ZHBcA922fFjOuju35D8WFA/4MF9vOeXxBonUp8+2zOu1vZbUZlYAiD+0e7gnN Byttk2RrpwMjIlvIbp5xhrS931PfekXjW89LlOIlBG67cC1lKM=
IronPort-Data: A9a23:EPOcHK5qQ6a/ncR9ObrJ2wxRtBvHchMFZxGqfqrLsTDasY5as4F+v jBJDD2OOa7YYWfzKNt0PN6/oElXuZeBm9ZlHgRlrCg9Zn8b8sCt6fZ1gavT04J+CuWZESqLO u1HMoGowPgcFyKa/lH1dOG58RGQ7InQLpLkEunIJyttcgFtTSYlmHpLlvUw6mJSqYDR7zil5 5Wq/KUzBHf/g2QoajlOtfrZwP9SlK2aVA0w7wRWic9j5Dcyp1FNZLoDKKe4KWfPQ4U8NoZWk M6akdlVVkuAl/scIovNfoTTKyXmcZaOVeS6sUe6boD56vR0SoPe5Y5gXBYUQR8/ZzxkBLmdw v0V3XC7YV9B0qEhBI3xXjEAexySM5Gq95fOIHSZi+/PlnaFbmPJm6RiPRhoIIAhr7Mf7WFmr ZT0KRgXZRyFwumx2r/+F69nh98oK4/gO4Z3VnNIlG6CS615B8GYBfyXu7e03x9o7ixKNezBZ s4FbjxHZxXbaBoJMVASYH47tL3w2yGlKmYG9Dp5o4Il4U3/9gJT/oT2aoD5etuRScNH2Rqh8 zeuE2PRWUxCa4fFllJp6EmEh+nRkCXnX5gDUayx8PFCgVCPyCoUEhJ+fVb+oPyhg0Wic9NSN 0JS/TAhxYA17FeiUdbVXhCkrjiDpBF0ZjZLO/cx5AfIwa3O7kPEQGMFVTVGLtchsafaWADGy HeAnt/PPx8z6YbWVGq4ruaYnGrsJCUseDpqiTA/cSMJ5NzqoYcWhx3JT8p+HKPdsjETMW+tq 9xthHZk74j/nfI2O7OHEUcrag9AS7DTRQIzow7QRG/gs0VyZZWuYMqj7l2zARd8wGSxEAfpU JsswpT2AAUy4XelyHHlrAIlR+/B2hp9GGeA6WOD5rF4n9hXx1atfJpL/BZ1L1pzP8APdFfBO RCK4FgPucEKYib3MMebhr5d7ex0lsAM8vy4B5jpgiZmPfCdiSfepX4+OxTMt4wTuBF2yPhX1 WinnTaEVitCVv89k1Jats8W0KQgwWgl1HjPSJXghxWh2vz2WZJmYeltDbd6VchgtPnsiFyMq 753bpLWoz0BC7eWSneMruYuwaUicCJT6Wbe8ZIHL4Zu42NORQkcNhMm6eh9Jtc0x/gFyb+gE 7PUchYw9WcTTEbvcG2iQntic7joG514qBoG0eYEZD5EB1BLjV6T0Zoi
IronPort-HdrOrdr: A9a23:F+mMrapsVVOkL/d4YryVqpIaV5t4LNV00zEX/kB9WHVpm5Oj5q OTdaUgtSMc1gxxZJh5o6H/BEDhex/hHZ4c2/h2AV7QZniWhILIFvAu0WKM+UybJ8STzJ846U 4kSdkANDSSNyk3sS+Z2njELz9I+rDum87Y55a6854ud3AXV0gK1XYBNu/vKDwMeOAwP+tAKH Pz3LshmxOQPV4sQoCQAH4DU+Lfp9vNuq7HTHc9bSIP2U2ltx/tzKT1PSS5834lPg+nx41MzU H11yjCoomzufCyzRHRk0XJ6Y5NpdfnwtxfQOSRl8k8MFzX+0iVTbUkf4fHkCE+oemp5lpvus LLuQ0cM8N67G6UVn2poCHqxxLr3F8Vmj7fIB6j8DveSP7CNXAH4vl69Mdkm9zimg4dVeRHoe F2NqSixt1q5F377WLADpPzJmFXfwKP0AkfeKgo/jNiuU90Us4IkWTZl3klSasoDWb07psqH/ JpC9yZ7PFKcUmCZ3ScpWV3xsewN05DVitub3JyzPB96QIm1UxR3g8d3ogSj30A/JUyR91N4P nFKL1hkPVLQtUNZaxwCe8dSY/vY1a9Cy7kISaXOxDqBasHM3XCp9r+56g0/vijfNgNwIEpkJ rMXVtEvSo5el7oC8eJwJpXmyq9C1mVTHDo0IVT9pJ5srrzSP7iNjCCUkknl4+6r/AWEqTgKo GO0VJtcovexDHVaPR0NiXFKuxvFUU=
X-Talos-CUID: 9a23:GDzDWmp+cZp6dmw3pyDX+ZjmUckkflvn7yuJGAylEUMxGbGkEAGN9Zoxxg==
X-Talos-MUID: 9a23:JAPkIw/72Kg3TqITt3fDfdeQf9VqxoiUBmIjrY5c4eWEMjd8PSXa0A3iFw==
X-IronPort-Anti-Spam-Filtered: true
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-3.cisco.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Mar 2024 10:28:01 +0000
Received: from alln-opgw-4.cisco.com (alln-opgw-4.cisco.com [173.37.147.252]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id 42QAS1F0029624 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 26 Mar 2024 10:28:01 GMT
X-CSE-ConnectionGUID: hOm/O9PNTE6+8eR7nqe6vA==
X-CSE-MsgGUID: j5pO2dmSTiWUJc0ewfqHmA==
Authentication-Results: alln-opgw-4.cisco.com; dkim=pass (signature verified) header.i=@cisco.com; spf=Pass smtp.mailfrom=rwilton@cisco.com; dmarc=pass (p=reject dis=none) d=cisco.com
X-IronPort-AV: E=Sophos;i="6.07,156,1708387200"; d="scan'208,217";a="26941143"
Received: from mail-bn7nam10lp2100.outbound.protection.outlook.com (HELO NAM10-BN7-obe.outbound.protection.outlook.com) ([104.47.70.100]) by alln-opgw-4.cisco.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Mar 2024 10:28:00 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Xydvq2DhNrTuW0xrn/7aaVbDHeNNa1zrKx7GIBuIT3YZuAqhHYPuxK7GwbK09emcW6SD0J/SSGRAlqY3uZA1KPM0u72ntO7xzuENBZtpsk0lLIzbyqguXTzSSjHtQWjEG/cqL9Ug8cMHxo0JkOe3bB3FXLYmp8zMw9csF3GkeR/la1vvf6PKab5tn1lRzYPCr0fAlU11kDMKTelo1kR4c9i+rEp6HXVshqGNw/SS5iSYngZK9tiL0qSbVw3rTclYvCXAwBo4EVJ1oAK4hgR/DMr5/7ehSuRNgQ2Mm14JTitIXMSaXrjq5hxItpwKEE0yXU1BZR7+DMZiooETjbCasA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=0ER9PVGBuHKJvslL82eZUK4hEXh7BxXa0Z4BeDblnJY=; b=hsdL7ua0IexB2lHeubhkCcwn0fgLI0zzqe3XTJ40uaTDcIJojPGGMc9bDwTZgOl5R+QK7yZvC0faG9ENEp4VZwGFZ0akg7WrCxh3vM9I+4Hfri6on+1qHKGTgdltskSzIqfNd8Io9mICB0mrnsYXtqtefmvTlTTu39eYYuEN01A23m4/4G22PK/zPCK5K1QTQYY5PSlavGBR0H8WsNdy3XdNCksY2BtLGH/bZ4X3yEolGCHmngz8Ds6WZpwgQ2AoVJq3zBFVQRU/yYivvD/vNj4zqvD5RMEsz2xTRDOQ98FgDPTom7Zq0/Qk4GHba9IvTbe01x+bDRMYhSPf6lzZUw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
Received: from CH3PR11MB8519.namprd11.prod.outlook.com (2603:10b6:610:1ba::20) by DS0PR11MB8685.namprd11.prod.outlook.com (2603:10b6:8:193::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7409.31; Tue, 26 Mar 2024 10:27:58 +0000
Received: from CH3PR11MB8519.namprd11.prod.outlook.com ([fe80::68:d22b:4059:362]) by CH3PR11MB8519.namprd11.prod.outlook.com ([fe80::68:d22b:4059:362%6]) with mapi id 15.20.7409.031; Tue, 26 Mar 2024 10:27:58 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Carlos Pignataro <cpignata@gmail.com>
CC: "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>, "Suresh Krishnan (sureshk)" <sureshk@cisco.com>, Jari Arkko <jari.arkko@gmail.com>
Thread-Topic: [OPSAWG] side meeting #119: Power Metrics: concrete usage example
Thread-Index: AQHadvvqrcvTSD5xYUatEf2bcshhf7FIafUAgAAgkLCAAHj5AIAAvukT
Date: Tue, 26 Mar 2024 10:27:58 +0000
Message-ID: <CH3PR11MB85194E536266B789DACC367EB5352@CH3PR11MB8519.namprd11.prod.outlook.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>
In-Reply-To: <BEF7EDBC-973E-4C97-AB90-D890180A72C0@gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: CH3PR11MB8519:EE_|DS0PR11MB8685:EE_
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 6LzIhy9HnHEI8LyKZfAx4oPXcL/Gii5ZGZUbdSMgJPt7/xMcPvU4DDnzbZGytDYn1bsRG2tWQaR10X27cm/RUSx2VsctQe97PYjsgNZGM96OXy5HeaAnMRYO9LDhpCbsDuwk4VmBKWteOx2hDT7hCsY+qJ3uGcjW24NBnRu7Ort68mtnLKIrdvh0+y7DXvbL3z35Npp9J/PRNuMLptfdxpzolaRx68LwFpIKFoyBEl68u4iM761S6lPvQ9xlDTF4q/OlaUQUnhFVZ0Zwno+LQA1UKw0mOBGN5mcAOGzGUa5SfaO2sukDbX5FXyId47pimfv/WC8FBaosienFAKAn22pak+K2it/rf11+HuBO20Kl1BxmBWk6zTdcRm99z3+G7lJRzS0IPdomMXTcAAuHZJZI22c8Vu1mR7TOFeyTMH93KfAid/jgnX5e0nevfTNL5ClwXBHzlTyOHOsRks0CH/70Vi5ZBWdgnamEiA1MS1n+Zm6dqSkSnJXrQAXfQS6q6gMIPWeQbzKDNuzazt1Slc1oCzMhHLKSY07JnHob2ZvyUqqzyFI+So9/qtI+kWGAgfErkIlrrznlg9MtHqT8Z/Zef5fLlJMxOe85hKCIfylGJjG7zLfK5TXzXdLn/IIr
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CH3PR11MB8519.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230031)(7416005)(366007)(376005)(1800799015); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: vwrMKYNRkotYPdEAMpPc7fNRx33/oZ3JuuzglwCjNkGENaL0mK8C2NCIqhCyEZuBsVvSvFcjhEO3Rjw9LP+7kynE45Zl9QO2ZX1dbyaxWzptM4Lj+PeYESZcbqdRt87oTkm73si9pWqL5bh786EFaszKHlnrxTcql5SkyWUq2JUxm/nsS5pHU9LyB4H/GHFQZDg2e/n7DaQYoIc73eHDHAGeT3qofKrB/mZfLsxFzaWMxBP2sZoI+oduX4VXuOfciHyHzFv/uoGSGZudrpMVB7eftyHpbEIetuKIpABTk2OnKM2eixZwYWjA+yGASN16Ov9YUi5JPslgKsPYcf75Gk5m6xE9SIjFhsa3SNFYEpMySdbClhGGH1Ag2HELw+uo9FZT8FUyYjKQPeyM+zkw1Yx5qf0sAWl6LygfWk8I/ZkptDPPdyFTWq/N36VkqC+UhWfpsmQ8c88AwtZkvLHToqZeAWTg+4iZpS03irJO58DxglbB6Yb6sRjwOY/uoBCSyVTBANu16/hCKwFt0Vx4bmtOkiRxpoh9EsHDs5flvkQGI47+YeGrlQFKmSLXTwdCcbyJVXPwBmgJSLVONx8CpctkrSv9t7EH7TNlYPi1phINjj1KrnR1wGJo1fwLEK1I6s5zjLiBROSltWZcHfqF8HOdHR91H5YdIEtQaK13eb3/xR62kYxjlXQS7llV0BUXhYb13GdOzanzc17wC9C38qJlyuvWiv1AjIPiO0rW6jWOE3iVekL7Vtt/vlt3GCJiV9AxVvvoVlwIFiQUmoyRaVl2M/x8oGLl//YCwgLXcTOmibLf1fiYOFY+Josu1y2AyuxkclcggdidZTYjQAbAQOzx5RLF0M5523PIzmGgzeytUQU63f/hb1JEtHXcHDQDUkKOfjGjVMrzpKC0Tmq6ltp0FuzriyaYypDEdp3GqQ+FhWgv3bahoS3+jgJWCuEgZQB4bB83OB5AlC2CkASg3qV572/fZ7bLOGIW4fexriUmaYGsw9CRVOiQAFjvEoZ/4s0tEMmz7tjBOGs3A8hkNEnYDpi8cBITloKL7HqZRvvwGQc1WJSSgSXgvHPUyjPc8Bjc2FN7G/1SGEdqpI6BOsVx95Sd2QTF1R1IY8Shw3yBMp1wE/dhoNRidC4HQ0zYlOJOR6bRX1096V+XiHG5QFcrfWuN+sGOmodd6KAjct0mhG5Ioist3b6A9xR2KR3gU8DTZQr78qTWha8LQ3fqtui3eyKWdJmnVvuRzZ6ILlEG0Hg8RU9QvIMPY2CZBAvpPkTrPMUhYqb4DsRdHjuVMlbLLCPsTW5d89TDBMXHaVHhqRHJyaLvlwTCzVfPl11S6HUN9QGuR9Iw1nS/sMF3L/b6PxQIgsPcFGOCHH4xpmJuLGY9BK/9zlpKB4SludPn/nxFVNL58LzjvI+4ZiKmIniukmXCv2cu8/ZCvOmtKPj+talQit9OydvRa/OPnQnHFw01D7ljkfkkK4leDyzrn5PU13lhqEa+QgU8XoPXKhtmV/JSG6gHPY8GUhbbPad0539RtGTykEfbwwHctVPymfEzw1D2FcKIRFEQOm0IEURDRVd6+PGKAWpHMo/UZsIVjksoBf2+kX6Li+K0Vpj1RP1ftd9OWT13bYY+k56EPatzs5weOHJaeecGLaBuoPv6WWaeWRhJ0rM+6ppnXeMzCQ==
Content-Type: multipart/alternative; boundary="_000_CH3PR11MB85194E536266B789DACC367EB5352CH3PR11MB8519namp_"
MIME-Version: 1.0
X-OriginatorOrg: cisco.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH3PR11MB8519.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 519c8fe9-1298-4d76-7ec8-08dc4d7f6817
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Mar 2024 10:27:58.1998 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: BimtPJSErydc3OSRl5St0h02rxuTELO3zDnhW34Jrd7A1ni/YoXRcvYLXNvZKtIp7xXMSa6kuuxlq6CkgSla9w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DS0PR11MB8685
X-Outbound-SMTP-Client: 173.37.147.252, alln-opgw-4.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/oIH8FFr8Zy0-pSNCguFckNfKdnQ>
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: Tue, 26 Mar 2024 10:28:07 -0000

Hi Carlos,

Thanks for the comments.  I’ve provided some comments (RW) inline …

From: Carlos Pignataro <cpignata@gmail.com>
Date: Monday, 25 March 2024 at 21:09
To: Rob Wilton (rwilton) <rwilton@cisco.com>
Cc: 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>, Suresh Krishnan (sureshk) <sureshk@cisco.com>, Jari Arkko <jari.arkko@gmail.com>
Subject: Re: [OPSAWG] side meeting #119: Power Metrics: concrete usage example
Hi, Rob,

Thanks for the comprehensive email, and for your desire to support the industry towards improved energy efficiency!

RW: Great!  I think that at least our broader goals are aligned here, although you seem to disagree on the particular path that I’m pushing for.  I’m hoping that we can manage to get alignment, working towards the common good.


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"
RW: Sorry, I had a conflict and couldn’t attend the e-impact interim.  My previous understanding was based on when this was discussed between the IESG and IAB retreat last summer was that the IAB program was for more future looking working, and incubating ideas that were not yet ready to be standardized but any actual work would happen in IETF WGs.

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

RW: Sorry, but I don’t really follow.  Why would standardizing metrics and power controls now impact the overall strategy?  This is perhaps where I see things quite differently.  I see this as a simple split between what we can standardize now, relatively quickly, starting to reap the benefits now vs spending a long time discussing what we plan to do before taking any action.


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.

RW: I don’t believe that metrics/models are the ultimate goal at all, but they do seem like a useful first step.  Further, the purpose of this proposed WG isn’t really to create new work, but to better corral the existing work that folks are already trying to get started within the IETF now, and as I see it, struggling to get traction.


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

RW: When I was an AD, both in the previous side meetings and in the IESG/IAB retreat I was also a vocal proponent for creating a WG, and yes, the agreement at that time (9-10 months ago) that we should start with the IAB e-Impact program, and that the work could proceed in existing WGs.  However, I’ve since seen “green” related drafts being presented in OPSAWG, within IVY and it was on the agenda for NETMOD.  I.e., it looks to me like there is work ready to progress now but looking for a good home.  The issue here is that this work isn’t obviously and clearly in charter for any of these WGs except maybe OPSAWG.  IVY is meant to be specifically focussed on a base inventory YANG model and should concentrating on that task until it is complete. Alas, one of the downsides of OPSAWG is that it’s made up of different groups of individuals working on their own topics and lacks the cohesiveness and collective direction that a dedicate WG could provide.


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)

RW: green-bof is just a list name.  I don’t really care what the BOF or WG is called.  My intention is that the scope of the WG that I’m trying to create is that it will be narrow to the work items that are achievable in the short term.  Regarding participation, for me, I would suggest that interested folks may wish to participate in both: E-impact for overall strategy and longer-term considerations of how we should evolve our protocols.  The new WG for short term focused work on green related work that is understood well enough and that we can get standardized now, in the short term.

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.

RW: Right, my drive for encouraging this work is not as Cisco employee, but was as an AD, and as someone who feels that environment impact is a significant issue to humanity and I would rather the IETF takes steps towards standardizing something now in the short term (noting that it can always evolve over time) than to spend 3 years having discussions before taking concrete action.

Because of the timing of the side meeting, the discussion didn’t really end up being about particular drafts at all, but instead focused on what drafts currently exist in this space.  My brief, very rough notes that I captured were:

Alex:
Green Networking Metrics OPSAWG
Data models could be derived
NMRG problem statement
Sustainability considerations

Luis:
APi for getting energy data from routers, SD WAN focus

Tony Li:
Traffic engineering, optimize across the network, greatest benefit is turning off parts of network device rather than just reducing traffic.  YANG module to disable links across the system.

Qin: + Carlos (BMWG draft currently):
Controlller level model, reporting and configuration, benchmark and test invididual devices. Reference work from other SDOs

Marisol/Jan:
Sustainability insights doc
Telemetry philatelist. (collecting telemetry data in general + green metrics + device level control
Power - Data model for devices, YANG based, or other protocols
Telemetry to TSDB mapping doc

RW: I.e., it seems to be me that there are multiple folk from different companies who are all interested in directly working on this, and this is why I suggested within that meeting that I thought that it would be helpful to target a WG forming BOF, with a narrow charter to focus on the items achievable in the short term.  My goal is to help connect these folks together and help give them the tools to help succeed.  For me, the benefits of a dedicate WG are: (i) Interested parties know where to go, and where to target their work, where to have discussions (ii) Guaranteed dedicated agenda time rather than competing with all other topics happening within these WGs.  (iii) an easy ability to hold virtual-interims to progress this work more quickly.

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.

RW: Sorry, I still don’t follow.  Reporting power metrics off devices (to management agents can get better current information about what the actual power usage is), and the ability to selective disable ports, forwarding ASICs, linecards, etc … seems like an obvious first step.  What is the bigger picture that I’m missing here?


I hope and trust these are useful and clear,

RW: Sure.  I still believe that this is significant interest and energy to target a WG forming BOF for IETF 120.  Perhaps, initially, you would be willing to participate and help in that effort to scope what such a WG could look like?  If, after we get into the details, you still believe that it is the wrong path, or we can’t get consensus on what work we want to do then you can of course drop out at any time, or indeed speak at the BOF (if it gets scheduled) to indicate why you think that this isn’t the best path forward.  Does that seem like a reasonable/pragmatic way forward?

Regards,
Rob


Best,

Carlos.

[1] I did not see a response to this:

RW: I’m not familiar with this draft/work, but I only see Cisco authors listed currently.  But my understanding is that others have proposed similar drafts leveraging similar ideas, e.g., draft-cwbgp-ivy-energy-saving-management-01, that you are an author on, and which I also haven’t read …. However, it is also worth noting that draft-cwbgp-ivy-energy-saving-management-01 is targeted at the IVY WG, which I believe that is outside the scope of the current IVY WG charter, at least until the core inventory YANG model is completed and the WG recharters.



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

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

b.     Get the initial BOF submission in before 5th May

c.      Refine the BOF proposal based on feedback received, and update by 7th June

d.     14th June, we hear back whether the BOF has been approved for IETF 120

e.      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<mailto:opsawg-bounces@ietf.org>> on behalf of Carlos Pignataro <cpignata@gmail.com<mailto:cpignata@gmail.com>>
Date: Monday, 25 March 2024 at 12:01
To: Marisol Palmero Amador (mpalmero) <mpalmero=40cisco.com@dmarc.ietf.org<mailto:mpalmero=40cisco.com@dmarc.ietf.org>>
Cc: opsawg@ietf.org<mailto:opsawg@ietf.org> <opsawg@ietf.org<mailto:opsawg@ietf.org>>, e-impact@ietf.org<mailto:e-impact@ietf.org> <e-impact@ietf.org<mailto:e-impact@ietf.org>>, inventory-yang@ietf.org<mailto:inventory-yang@ietf.org> <inventory-yang@ietf.org<mailto:inventory-yang@ietf.org>>, Alexander Clemm <alex@clemm.org<mailto:alex@clemm.org>>, Alberto Rodriguez-Natal (natal) <natal@cisco.com<mailto:natal@cisco.com>>, Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>, Mahesh Jethanandani <mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>>, Ali Rezaki (Nokia) <ali.rezaki@nokia.com<mailto:ali.rezaki@nokia.com>>, Suresh Krishnan (sureshk) <sureshk@cisco.com<mailto:sureshk@cisco.com>>, Jari Arkko <jari.arkko@gmail.com<mailto: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