Re: [alto] [Cats] DMDTF and CATS Metrics

"" <> Thu, 13 April 2023 15:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ED12DC151B0D for <>; Thu, 13 Apr 2023 08:29:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.849
X-Spam-Status: No, score=0.849 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, HELO_DYNAMIC_IPADDR=1.951, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id K7yekab4lzt1 for <>; Thu, 13 Apr 2023 08:29:08 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EC7CEC14CE40 for <>; Thu, 13 Apr 2023 08:29:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=s201512; t=1681399743; bh=XvFiwKvwChBFODDKCRvt9jpvZy3cz+TRz4kNUoFfqaY=; h=Date:From:To:Cc:Subject:References; b=LApxp6LIybazKMbJ9f2/SCjPylfI/TXL1uNQGMa8KE70PL04j4Tb2gigMFdgbPdBl zAGhngxRbmaUWrTg8HX9IlcYlz00i54GGZMXgsZUb6V4wBLe5M0LcJk16N0WSp8Mlg 4JCnlBaLb1JucyPjM8Th65rKhdy3a7tqQ1E5iqOc=
Received: from cmcc-PC ([]) by (NewEsmtp) with SMTP id 740A72E9; Thu, 13 Apr 2023 23:29:00 +0800
X-QQ-mid: xmsmtpt1681399740to9iakiyx
Message-ID: <>
X-QQ-XMAILINFO: OZsapEVPoiO692zZB5ypniTapPMnhq9oSbkXH+vOZgFBmeHcLoacAuDBqXyRpZ LUGMObCL40anrJE/NhKScpMIa85DNIxT4Q5p41XtX5L5S6idZ0mHKQElrqK6zgB6qD6gMifIO4wI KfmtWhX7hcH8RM/n9IwEz8aHWvlu8H7I913vEatfcQBToWoool7u8Xp+7Z6cAwoGs2GPRbZIYkmS xQQ3/lvEaZV2J/HlHr8+67GZQQWbtq2Zhy201dbl3rRcpOrYzA2cWIlCvrZ+yEPu8vW5Kq4wD9t7 LUONyT46TilB2VXBVit+tx7FvhnpaqD015pV054Kh3t1fGlVGR7Znbry+pkFf7LnioZrypZwf76M Dmvm38FXT0U+LpRRzH3yPomczarNT8Z/gnkSN18PTAcVKKJSKvSK44JiSWCLRkWcWSKhuND8EUHQ KePfjbCXq6Lv9nT5diwY9Y9j24ghVEF1vlDPZSz7Cmp/7/z3++385aiU1uf9kYFaqtP5v1kv1CMa RMOy0HsuBwiZejNoQtlUm69kXHwPOC5BRlAWXeYVsifMp4xzUsNRPIgpnKNK83y9NFxM59mHC1pS 5c0CC4QRSUfgZmoiGjvBqsxuR+cQrRB0AHL4uE94fKeKVREuYulxBGXFkixS/F8PQ0foKAoVmU11 2uNJHuPyGJuEjKAl4lXjzqPbcvbdMyLum3pOXu19a5LyqdDWK1iX03ztbgL/DLKzDrcNWgHjpZy1 fMpVQpEZak7I0b9aNe+gDesEs7R9l5a7YQdqtpXerq8L9u30DOhSSlFxwkDb7KLtc2MTacj9B4QH MTaQ7nOS+Wsgjatax+TvjBlEwcBIWbR3h1TWe7YnfZyBUwsL86UCbIYI3mzjAdkznzXFLIPvkexW JQsUyYM1bRPPS04hXZ2wXwtgT0S80ClcABvf/xOQV3u1jVQbuejkkwQ4uex2d9Er15SVC/KkAw4p ctE/ro721hHUHHDEwrShJirRKLrWrfeH2xt72lU9m66ZzR7X6Yu/CUQmx6AbAbKNkoZxQukZQ=
Date: Thu, 13 Apr 2023 23:29:01 +0800
From: "" <>
To: LUIS MIGUEL CONTRERAS MURILLO <>, "" <>, 'Dean Bogdanovic' <>
Cc: cats <>, "''" <>
References: <0e5e01d9696e$d3c9d840$7b5d88c0$>, <>, <0e8d01d9697d$153ce0c0$3fb6a240$>, <>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail[cn]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_001_NextPart627286744524_=----"
Archived-At: <>
Subject: Re: [alto] [Cats] DMDTF and CATS Metrics
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 13 Apr 2023 15:29:13 -0000

Hi, Luis

    Many jobs about the management of the cloud or the edge have been done.

    IMHO, the metrics defined in the redfish, rfc7666, Anuket, etc., perhaps can be used directly if for a service, it is considered valuable and reasonable.

    Some personal understanding for discussion. 
    The metrics can be used by two entities: the first is the management/control node which can be aware both the computing and network information, and the second is the ingress which can make a on-path decision.

    The management/control node can do the service deployment, and the ingress can do the traffic steering. The service deployment should be the precondition for the CATS.

    For the former, more detailed information is needed, and the information normally should be informed by using some application layer communication methods.

    For the later, perhaps we need to simplify the metrics, and only communicate necessary information into the network to influence the traffic steering.

    Of course, the management/control node can also make a policy about traffic steering considering more detailed information.

Best Regards
Zongpeng Du &
Date: 2023-04-12 13:25
To:; 'Dean Bogdanovic'
CC:; ''
Subject: Re: [Cats] DMDTF and CATS Metrics
(Adding ALTO in cc since discussion on metrics is also relevant for that WG)
Hi Adrian, Dean, 
Another reference work we can consider is This RFC provides several metrics as part of the MIB definition that could be leveraged on.
Apart from that, I think we need to look at what current cloud / VI managers provide nowadays in terms of metrics (i.e., OpenStack, Kubernetes, etc) since the metrics that we could handle will be generated most probably for those non-IETF components. So a good exercise to start with would be to check and compare what kind of metrics these kind of sustems provide nowadays, and derive from that a common / abstract set of metrics that could be consumed by both CATS and ALTO.
In there is reference as well to CNTT and Anuket efforts, which probably need to be revisited and updated. 
All in all, an exercise of collecting different sources is needed, and from that select relevant metrics for the purposes of ALTO and CATS.
Best regards
De: Cats <> En nombre de Adrian Farrel
Enviado el: viernes, 7 de abril de 2023 20:17
Para: 'Dean Bogdanovic' <>
Asunto: Re: [Cats] DMDTF and CATS Metrics
Ah, thanks Dean.
Interesting coincidence of acronyms. 
This work does, indeed, look relevant.
From: Dean Bogdanovic <> 
Sent: 07 April 2023 19:01
To: Adrian Farrel <>
Subject: Re: DMDTF and CATS Metrics
I was referring to the work that is being done by Redfish and has been presented at IETF 98 by Joe White ( This work didn’t continue within the IETF, but Redfish has published and keeps developing and maintaining their data model (] They did lot of compute resource modeling and taking a loot at their work is very useful IMO. DMTF folks know lot about compute, so it might be worth even rekindling the joint work.
On Apr 7, 2023, at 12:34 PM, Adrian Farrel <> wrote:
Hi all,

In the meeting in Yokohama, Dean Bogdanovic mentioned a presentation from
IETF-98 that might be relevant to our metrics works.

I did some digging and found the presentation by the IEEE 802.3cf - YANG
Data Model Definitions Task Force. The purpose of that work was to migrate
relevant MIB modules to YANG.

The slides for that session are at
The presentation is at and the presenter
was Rob Wilton who would, I'm sure, be responsive to questions.

I'm not clear how much this is relevant.

Dean, was that the presentation you were referring to?



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição