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

"Rob Wilton (rwilton)" <rwilton@cisco.com> Wed, 27 March 2024 11:34 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 6E41AC14F6A6; Wed, 27 Mar 2024 04:34:42 -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=unavailable 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 J6BMY1f65XVh; Wed, 27 Mar 2024 04:34:38 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (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 A529DC14F614; Wed, 27 Mar 2024 04:34:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.com; i=@cisco.com; l=58656; q=dns/txt; s=iport; t=1711539277; x=1712748877; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1ODn3WQp6i+zHuX0XWZGkZPdVqu4v2IaFBhQwKvHJeg=; b=kFHpxgoPHi3kiwoPOFaNrA15W5wJ2ZmFOZbfIgRrRwjOqfWQ0Ktxdvgm dPHuSB624JhYUjVEOLAVkK9Zbrpudb8pYaVPNi2ZbPpIB0ysI1U5NBD26 lPeB2cL+UgbcqGWlJr8FEa2KStCTfQ+pI9yzL+28qnU9JkJvjFIQsv/F/ Y=;
X-CSE-ConnectionGUID: SZUAZaDJTl+PGVW8aWApag==
X-CSE-MsgGUID: ew1EOQNvTte+RcX8jf55rg==
X-IPAS-Result: A0AFAAAQAwRmmIENJK1aGwEBAQEBAQEBBQEBARIBAQEDAwEBAWWBFgYBAQELAYE1MSooegKBF0iEVYNMA4ROX4ZJgiIDgROKTYgahyiCZRSBEQNRBQ8BAQENAQEuAQoLBAEBhEBGAhaHbwImNAkOAQIEAQEBAQMCAwEBAQEBAQEBBgEBBQEBAQIBBwUUAQEBAQEBAQEeGQUOECeFbQ2GWQEBAQEDAQEQCwYKPwIIAxACAQgRAwECDRQBBgMCAgIeBgsUCQgCBA4FCBAKgl4BghcUAzEDARCjawGBQAKKKHqBMoEBghYFsB4NglAGgUgBiAgEGgEFZWgCAohcJxuBSUSBFUKBZko4PoIfQgEBAgEXgQwRCyAeFoMlOYIvBIISgzeBJYFVgWGFECGBdwGFDoEFOINTgnWGfVR4IgN9CARaDRsQHjcREBMNAwhuHQIxOgMFAwQyChIMCx8FEkIDQAZICwMCGgUDAwSBLwULGgIQGgYMKAMDEkkCEBQDOAMDBgMKMS5PQQxQA2cfMQk8DwwaAhsUDSQjAiw+AwkKEAIWAx0WBDIRCQsmAyoGNgISDAYGBlwgFgkEIwMIBANQAyBwEQMEGgQLB3aCAIE9BBNHEIEyihkMgzMpgU4pgRKDJwtDHgNEHUADC209NRQbBQQfAYEZBaJjewGCBFoGFxc6IgsFCQgQFDsMCwsCHh4BHAEECTkoAjqSahwOgmEBSYspjkuUEXAKhBOKaIEki1WDU4YrF4QFjHyYSmSIDpBUglSLH4QAkUAEHIUGAgQCBAUCDwEBBoFkOoFbcBU7gjMBM1IZD1aNY4EVAQmBJIYykE14AjkCBwEKAQEDCYhugXoBAQ
IronPort-PHdr: A9a23:riN9ixKSIRuDhOS96Nmcua4yDhhOgF28FhQe5pxijKpBbeH/uZ/jJ 0fYo/5qiQyBUYba7qdcgvHN++D7WGMG6Iqcqn1KbpFWVhEEhMlX1wwtCcKIEwv6edbhbjcxG 4JJU1o2t2qjPx1tEd3lL0bXvmX06DcTHhvlMg8gPPv0HpLViey81vu5/NvYZAAbzDa4aKl5e Q2/th6Z9tFDm4ZgJ60tghfIuS5OfOJbhCtkcFmShB37oMy3+fZe
IronPort-Data: A9a23:3Gh5c66t05qCtgQdGr4H6QxRtBvHchMFZxGqfqrLsTDasY5as4F+v jQaC2rVOPeMYWL9ft4la4/j/EtQuMXdmNViS1Fk+ytjZn8b8sCt6fZ1gavT04J+CuWZESqLO u1HMoGowPgcFyKa/lH1dOG58RGQ7InQLpLkEunIJyttcgFtTSYlmHpLlvUw6mJSqYDR7zil5 5Wq/KUzBHf/g2QoajlOtPrawP9SlK2aVA0w7wRWic9j5Dcyp1FNZLoDKKe4KWfPQ4U8NoZWk M6akdlVVkuAl/scIovNfoTTKyXmcZaOVeS6sUe6boD56vR0SoPe5Y5gXBYUQR8/ZzxkBLmdw v0V3XC7YV9B0qEhBI3xXjEAexySM5Gq95f8E0WWg8W/7XHCMEPD/co+BX4fJYQXr7Mf7WFmr ZT0KRgEahSFwumx2r/+G69nh98oK4/gO4Z3VnNIlG6CS614B8mYBfyQtLe03x9o7ixKNezBZ s4FbjxHZxXbaBoJMVASYH47tL3w2yOvImcH9Tp5o4I6/DH+6zVXzoTxPZnvcezaR8sIw1yX8 zeuE2PRWUxCa4fFllJp6EmEh+nRkCXnX5gDUayx8PFCgVCPyCoUEhJ+fVb+oPyhg0Wic9NSN 0JS/TAhxYA17FeiUdbVXhCkrjiDpBF0ZjZLO+Q+7AfIwa3O7kPIQGMFVTVGLtchsafaWADGy Heyre7ANzVDkoGRCkqyyIjEpAybISEaeDpqiTA/cSMJ5NzqoYcWhx3JT8p+HKPdsjETMW+qq 9xthHZk74j/nfI2O7OHEUcrag9AS7DASgozow7QRG/gv0VyZZWuYMqj7l2zARd8wGSxEAfpU JsswpT2AAUy4Xelz3HlrAIlR+7B2hp9GGeA6WOD5rF4n9hXx1atfJpL/BZ1L1pzP8APdFfBO RCK4F8Ou88NYiH3M8ebhr5d7ex3nMAM8vy4B5jpgiZmPfCdiSfepX4+OxTMt4wTuBF2yP9X1 WinnTaEVitCVv89k1Jats8W0KQgwWgl1HjPSJXghxWh2vz2WZJmYeltDbd6VchgtPnsiFyMq 753bpLWoz0BC7eWSneMruYuwaUicCJT6Wbe8ZIHL4Zu42NORQkcNhMm6el+K9U7xP4LzrygE 7PUchYw9WcTTEbvcG2iQntic7joG514qBoG0eYEZD5EB1BLjV6T0Zoi
IronPort-HdrOrdr: A9a23:7mc0uKhzqR+zb5vppZTe8Zf26HBQX5N23DAbv31ZSRFFG/FwyP re/8jzhCWVtN9OYhAdcIi7Sde9qBPnmaKc4eEqTNGftXrdyRqVxeBZnMffKlLbalfDH4JmpM Ndmu1FeaLN5DtB/InHCWuDYqsdKbC8mcjC65a9vhJQpENRGt1dBmxCe3+m+zhNNXJ77O0CZe KhD6R81l2dUEVSRP6WQlMCWO/OrcDKkpXJXT4qbiRM1CC+yRmTxPrfCRa34jcyOgkj/V4lyw f4uj28wp/mn+Cwyxfa2WOWxY9RgsHdxtxKA9HJotQJKx334zzYJbhJavmnhnQYseuv4FElnJ 3nuBE7Jfl+7HvXYyWcvQbt4Q/9yzwjgkWSiWNwwEGT4vARdghKTvaptrgpNicxLHBQ++2U5Z g7nV5xcaAnSy8o0h6NvuQgHCsa5nZc6UBS4tL7yUYvH7f3rNRq3NciFIQ/KuZZIAvqrI8gC+ VgF8fa+bJfdk6bdWnQui11zMWrRWlbJGbMfqEugL3d79FtpgEw82IIgMgE2nsQ/pM0TJdJo+ zCL6RzjblLCssbd7h0CusNSda+TjWle2OADEuCZVD8UK0XMXPErJD6pL0z+eGxYZQNiJ8/go 7IXl9UvXM7P0juFcqN1ptW9Q2lehT2YR39jsVFo5RpsLz1Q7TmdSWFVVA1isOl5+4SB8XKMs zDTq6+w8WTWlcGNbw5qzEWAaMiW0X2ePdlz+oGZw==
X-Talos-CUID: 9a23:92JhpWN2nugm6e5DYxta3XwdNuIZdj7l40nvc0aHIH5gR+jA
X-Talos-MUID: 9a23:KBZKdQXU2//I6fnq/DLz3RxFDeF237ijS3oGocUEtZTZLyMlbg==
X-IronPort-Anti-Spam-Filtered: true
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-2.cisco.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Mar 2024 11:34:36 +0000
Received: from rcdn-opgw-4.cisco.com (rcdn-opgw-4.cisco.com [72.163.7.165]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id 42RBYasJ018664 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 27 Mar 2024 11:34:36 GMT
X-CSE-ConnectionGUID: 6X5PqDRKSpiiGWp19Ij7gw==
X-CSE-MsgGUID: bpzH2LdUSziXlVd5YuOCGw==
Authentication-Results: rcdn-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,158,1708387200"; d="scan'208,217";a="31433225"
Received: from mail-bn8nam11lp2168.outbound.protection.outlook.com (HELO NAM11-BN8-obe.outbound.protection.outlook.com) ([104.47.58.168]) by rcdn-opgw-4.cisco.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Mar 2024 11:34:35 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FdeEF8W7tD3hlUSss/LZW58aGp1hjqKMNwrXyi0OYaDkHSbj+wx4QUcU6n4aX4CVaZRtZvXdC5qD1XWgJ7SR3qX9WnhP9N+face6so47e/0KQ2V7jBzWFHEOmaqQdDY5KA8TcsG/IXfZDElBsv1sM8vzWOhDpUsSTFaVLm6/xkHLAdMVIcokLrB/XurwNYphFnCwB5l6gpiMeQA/Fz6XZIp5HR6F8a+Jr3POo9zvYL+C5UrtVLnewUV0/9LKXiDeHWQzQ9ucVOBVmMuepbljvHSlkx0tIIeffmgxmbU70175wzqnhz9nXKnP2RcRg3t1iyS0mb/nhGzpvDl2/P0Jww==
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=1ODn3WQp6i+zHuX0XWZGkZPdVqu4v2IaFBhQwKvHJeg=; b=mRG4tJ0L7liPzFQEU7j3e39pseftbbcQIbfTDyZcGmpU8eVFkjcEknF79SnM9qMhroGeB0NwgcCE/YGcbE9gDx9pW1WcOKa6AAnQ78phdEvpPmtoaCe9NSkTDGy7mUy6VX3ABL02j9hzWEEPePkEzy53bGeheM5qraeeTEmjPZznLRPUHASomdj+OJfu/LzCCwNFi6MnuQXYpKgHJqjBEp0n5Sji2SePdO2C5NE3qJp6lBjsAgvtZ5asByGi4cev7NCW1KLqVIrxQHi4hg4ROtsKb5KFihmlxN4c5zurfD4R68v1rlmIaF3i3zwpg/b+SY89i62Ci4oQ3EVMM4wqtg==
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 LV8PR11MB8536.namprd11.prod.outlook.com (2603:10b6:408:1ec::19) by MN2PR11MB4725.namprd11.prod.outlook.com (2603:10b6:208:263::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7409.33; Wed, 27 Mar 2024 11:34:33 +0000
Received: from LV8PR11MB8536.namprd11.prod.outlook.com ([fe80::dae8:c4e2:9d09:1d9]) by LV8PR11MB8536.namprd11.prod.outlook.com ([fe80::dae8:c4e2:9d09:1d9%7]) with mapi id 15.20.7409.031; Wed, 27 Mar 2024 11:34:31 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Jari Arkko <jari.arkko@gmail.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>, "Ali Rezaki (Nokia)" <ali.rezaki@nokia.com>, "Suresh Krishnan (sureshk)" <sureshk@cisco.com>, Mahesh Jethanandani <mjethanandani@gmail.com>
Thread-Topic: [OPSAWG] side meeting #119: Power Metrics: concrete usage example
Thread-Index: AQHadvvqrcvTSD5xYUatEf2bcshhf7FIafUAgAAgkLCAAj1VgIAAqGjk
Date: Wed, 27 Mar 2024 11:34:31 +0000
Message-ID: <LV8PR11MB85366E06BAE0A730AE92B59BB5342@LV8PR11MB8536.namprd11.prod.outlook.com>
References: <DM4PR11MB52778685A92225856D21BB16C5282@DM4PR11MB5277.namprd11.prod.outlook.com> <CACe62Mnii4FMwkYAtvDHPEriy_BmEx4MtLtte1s1KKxFShJHZg@mail.gmail.com> <LV8PR11MB853621C7E833FDB26C6B729EB5362@LV8PR11MB8536.namprd11.prod.outlook.com> <BCDEFF28-03A9-4D62-A474-B4662BBE2AF6@gmail.com>
In-Reply-To: <BCDEFF28-03A9-4D62-A474-B4662BBE2AF6@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: LV8PR11MB8536:EE_|MN2PR11MB4725:EE_
x-ms-office365-filtering-correlation-id: 9d60b50f-a37e-4b30-42f7-08dc4e51deca
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: kjPArQ+1kgyFA3ePT2M7kFvFDgoV05YH+Tptmghyk+DPEdygTrQQMc07S85Nld/Txu3BwNRpLovkRfJS0WenONpfGycU1519T0fO0/0FUzm294V/1XT05fP7WNuTdpbhGFrCtjgy7B1wKQDfj5/hK14Mm9/rVVc783x0Mt7nkv7HYvcb3k3H47fVhhdUsXSQrhkEz+x1p3QgRU5RHf405IV/gOcBBKEl18iruJz5UJnnzuhJCajsgcyBlg1meu3T6L05V0bVfVBCVj3YeUVuhirfSNroNwuM67HV/i1bjb6qvZ9SFrYcNI4CB/3Joj4bR03b0Oqyc2s351aPebiSAUqnn81K2d7dG0GRGBLFZHsddtfTHEMZwU0pDsCNtBod4Ss4bkKREU+bgP+edtnNNE5HmE1HAIUs0U6ag3y34sQo0nJDTeErnPRmZVjB3JOoyo4bAxAv3iE7fs0E1OMlTqMQaX4fQEIwszPbIQlRCi11+oOqvjYAt7nyGxW+o1aF90JrDvmCWrS4/7EIVIVSor8j7Bfwn36RYxCUiVJUej1DDDycyZ9TywH+OyL9gm57ErjWvaYfi4FCCaRNUfm0+1s8r6iOS5gP6XLN/QBwYTg634h+Ev+Oekt0I6GDnn0iK0svpiLY3XghMwYouAIwxQl/jTri6MvRa4CCi1w7UfJ7shyXfCyt0Aw84j4urnGh
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:LV8PR11MB8536.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230031)(376005)(7416005)(366007)(1800799015)(38070700009); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: 2fHLXANBjfrdNAhw6fNOjDWs/MdFAUQNOxbQjIl84zjy52pk5JroUcz7hRNGTPXqHv74RPpA5bpBNKRHfE+DGqBzEylnnc/q0pKAZz1+QEzTY3dTpYubPClg1bzz5ib/yde6asrvZa9Ioh9qOdj55KiA91ANMawuIR1xwsK2yK5Hrfe55CUDpW7TJzLJv/4ZHWK5JkfzrDsh3J7PBzf3tBEFv2eCrtLwL5fGEWMCHBd1aoS11aj2DKVxQ+dLq6asuJl6aM+UTSFWAnhXPNvpiiKSQ3HCll+CFIsY7iU2mE7wq8FDF30YZornpXVUWTGKTaqzeGSrfxzOneXatadSeYBMmqnSZ4K6miWYU7478+X3OgfiQh8ZgotjmXrC6Kih6J+URFeMKhPiS1oknaLu50e59HXS3lmECKdIE8PD9Q6oJkUHPSey62O1MpUWevuThsGT7RimrJ9hzm/EJMTFgJtIFeXaNsNOA4GsTCK5OqrjoGW7HjurSH8KLWEeVwf6CfDdBxTuQYgil0oiCnjrDDSrAVpHlFGFbn7r8I4OUU9luE+xY0cI0L/U2OG/wJ5wy8XO8niBLPI7NWm8viMVEJ5K8qr2ottXyA3nvF02ipVeGbgonbpGDZ4rTT2N7m6p0fN5vT/8JUy08vZyP3DYFJ2ER/qofIWLOfzhno2/85Yl4EFem7Hnte2O3OxNRnQOZKDP7u7HwpsLLUPxnsWQJY+7GLKKL7prjLbrxwyGE6CVx/mluqE2XetPJZz7jhMxyIGrX18QzQVOgWaOxajlR1e3L2slC0qyBlbDLxjWrGUsF1SAudAGSTmLxwiYXXMgUuCf/p4reL3VbI5sp8koFz4rwQUXhW/k6VK5or4q1bvyzCifPjDx422PTIox1pakQCneMtkC7m6PEHZlzQ/0+hgx8v2zcmpo3KiV8wYySG3d+oZfihZUr8nVhgCh//+IWOmzYZWNEpbj8bLu1QdgQsl4zB1Ql1SNEzv4rVe28XazTdYJEwGHteer8tCad0GxkKsP3BFCwqaP2shBk07yD1ve87FhlEuvtt4AYWW5GPct2YInoSLAD91YqJmILJTQWGpNoSUZfv9SScpiGbrJZbG84cepws38vrW/10nB3aBsIQNH03DRv4ld91eOxFlJ1w8tx8zt9OAz4tbXO4BcruhkXG3vRXUADolH8ATnkDmJdk5dJLy1QJynEgTznLMXWUCWSGXP+R/Cr8+PUpQlbiKdToY+LOaHFC+jlO2XzRll0LF9/GAPze0G+D99c16m6l97PTQRBvo6FmB9zp652AEzn9NoJ8uA2Xbugo6He41K5J83sfwyJRj1T1sKqGmsdCou8tixE7PX0CYK2o1VGxC3ux8QfvRDKEuLPRKrWftRFl7FI+6HD9Tw7dhLZcI/t7lkKWnXc2KR0hMXXpK5GbykmRI2OU7hRWbWmm4vMKqBvF2YUmolY4PPGT8fidxeC2YrDKHWPUB4Hb1oi8qJLrXfr1WuK62xzgArEq6TC9KArTVt0Xtsk6kjXx1Mw6XBvK/RaXdSidl2Wa8ILl+HJPD90EQbzDAHmJ2TF8tznpQoDrfg6g66/DFqj8GiHO66
Content-Type: multipart/alternative; boundary="_000_LV8PR11MB85366E06BAE0A730AE92B59BB5342LV8PR11MB8536namp_"
MIME-Version: 1.0
X-OriginatorOrg: cisco.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: LV8PR11MB8536.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9d60b50f-a37e-4b30-42f7-08dc4e51deca
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Mar 2024 11:34:31.6670 (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: FiWmHcfSbp9H4ZStnQKNjUf7adD0S0CpXa/wQuSU5Quv/Ve1EOgBWZJXc1Uw//LdGrwcZZj/gfXtt/o1FrsvSQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4725
X-Outbound-SMTP-Client: 72.163.7.165, rcdn-opgw-4.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/s8qM0E-VUUrc17qwhX0EflUMFRA>
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 11:34:42 -0000

Hi Jari,

Thanks for your comments and offer to help, it will be greatly received!  We are in the process of setting up the open mailing list.  Once that has been created, and advertised, then I will move discussion on the BOF and WG charter discussion there.

Ack, on whether a BOF is needed or not.  In the past, when I was an AD, I generally favoured chartering WGs directly, e.g., for IOTOPS, IVY, NMOP, but I’ll defer to Mahesh & the IESG to consider which may be the best path here.  Either, way I think that the key part of this work is really defining the charter for that WG.

I’m also in complete agreement with you on a very tightly scoped, short lived, WG.  In particular, I believe that it should be for work that is broadly understood and that can be achieved in a short time frame.

Regards,
Rob


From: Jari Arkko <jari.arkko@gmail.com>
Date: Wednesday, 27 March 2024 at 00:09
To: Rob Wilton (rwilton) <rwilton@cisco.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>
Subject: Re: [OPSAWG] side meeting #119: Power Metrics: concrete usage example
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:

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