[{"author": "Joe Clarke", "text": "

https://notes.ietf.org/notes-ietf-118-opsawg#

", "time": "2023-11-08T12:03:01Z"}, {"author": "Joe Clarke", "text": "

Notes for this slot are at the bottom of the notes page. You'll see the section for session II.

", "time": "2023-11-08T12:04:31Z"}, {"author": "Randy Bush", "text": "

ADs can rat hole too

", "time": "2023-11-08T12:19:35Z"}, {"author": "Anthony Somerset", "text": "

on this topic being power usage/measurement stuff

", "time": "2023-11-08T12:21:18Z"}, {"author": "Warren Kumari", "text": "

s/can/do/ .. ?

", "time": "2023-11-08T12:22:51Z"}, {"author": "Warren Kumari", "text": "

A reminder that the NomCom feedback cycle is still open. In addition to providing AD feedback, please please also provide IAB feedback....

", "time": "2023-11-08T12:24:37Z"}, {"author": "Joe Clarke", "text": "

Sorry, @Anthony. Didn't have this window open. Yes, the poll was for the topic of energy management/monitoring.

", "time": "2023-11-08T12:25:02Z"}, {"author": "Warren Kumari", "text": "

https://datatracker.ietf.org/nomcom/2023/feedback/ -- I can't really make it much easier than this....

", "time": "2023-11-08T12:26:01Z"}, {"author": "Robert Wilton", "text": "

Re: draft-rcr-opsawg-operational-compute-metrics - I would suggest at least trying to present this work in CATS to see if what interest/overlap is there.

", "time": "2023-11-08T12:35:13Z"}, {"author": "Jordi Ros-Giralt", "text": "

Robert, yes, in addition to this afternoon's side meeting, we will be presenting the draft in CATS on Friday.

", "time": "2023-11-08T12:36:17Z"}, {"author": "Tianran Zhou", "text": "

If metrics are in the CATS charter, I think it's the place. Otherwise, maybe IPPM is generally a place for metrics.

", "time": "2023-11-08T12:39:15Z"}, {"author": "Jordi Ros-Giralt", "text": "

Adrian brought up one of the four questions we are targeting to get rough consensus on, which is: do we think there exist a common set of compute metrics?

\n

It seems to me that there is a need to have a holistic approach and that a common set of metrics are applicable to all stages of the service lifecycle (although a stage might have additional metrics specific for it). An analogy we are used to understand might help here. The two key service lifecycle stages (service deployment and service selection) are equivalent to the two main lifecycle stages of a communication network: (1) \"capacity planning\" and (2) \"traffic engineering\". Capacity planning deals with provisioning the right disposition of resources (say for example bandwidth and latency) to provide a communication service to a set of users. Once these resources are deployed, traffic engineering kicks in, which deals with how these resources (the same bandwidth and latency provisioned in the first stage) are utilized. These are distinct stages in the lifecycle, but they deal with the same core metrics (bw and latency). It is important that these metrics are defined taking the whole process into account, to ensure that the second stage in the lifecycle makes decisions based on metrics that are aligned with the resources deployed in the first stage.

\n

Based on this view, we agree that not all metrics are common, but some would be, and they would need to be specified taking into account the full lifecycle, rather than just one stage of it. We plan to bring this question up during today's side meeting (Karlin 4 at 15:30) and we look forward to everyone's input. Thanks.

", "time": "2023-11-08T12:45:16Z"}, {"author": "Robert Wills", "text": "

What is the RFC number Italo just referenced?

", "time": "2023-11-08T12:46:28Z"}, {"author": "Mohamed Boucadair", "text": "

I think he is pointing to rfc8795

", "time": "2023-11-08T12:47:07Z"}, {"author": "Italo Busi", "text": "

RFC8795: YANG Data Model for Traffic Engineering (TE) Topologies

", "time": "2023-11-08T12:47:15Z"}, {"author": "Italo Busi", "text": "

On Friday in TEAS WG, we are discussing the option to define some profiles for the TE topology for non-TE applications

", "time": "2023-11-08T12:47:48Z"}, {"author": "Mohamed Boucadair", "text": "

Some profiling would be needed I guess

", "time": "2023-11-08T12:47:49Z"}, {"author": "Joe Clarke", "text": "

@Rob Wills, please note an AI for us to query on-list for appetite to take on bis work for 8345. This can kick of some additional discussion around the topic.

", "time": "2023-11-08T12:49:21Z"}, {"author": "Mohamed Boucadair", "text": "

this draft is reusing ietf-schedule common model presented early this week in opsawg

", "time": "2023-11-08T12:55:28Z"}, {"author": "Joe Clarke", "text": "

Yeah, I noticed that.

", "time": "2023-11-08T12:55:39Z"}, {"author": "Robert Wills", "text": "

AI added to minutes.

", "time": "2023-11-08T12:59:32Z"}]