Open muzixing opened 7 months ago
We can add a Service-Oriented Utilization Sub-TLV. The "Service-Oriented Utilization Sub-TLV" is for distributing a metric that measures the real-time utilization of resources allocated for processing specific services or applications at an edge site. This Sub-TLV complements the "Service-Oriented Capability Sub-TLV" described in Section 4.6, which addresses the static resource capability of a site for a service. While the Capability Abstract Value provides a baseline understanding of a site's potential to handle a service, the Utilization metric offers a dynamic perspective by quantifying how much of this capacity is currently being consumed. This distinction is crucial for managing resource efficiency and responsiveness in network operations, ensuring that capabilities are not only available but also optimally used to meet the actual service demands.
Shepherd Check. This utilization is in section 4.8 "Service-oriented available Resource."
Only with the service-oriented capability TLV, a service still cannot know how much resource is used, and how much is available now. So please consider to add a utilization TLV to indicate the percentage of the used resource or remaining resources. In this way, for a ingress router or a controller, it can know how much resource a site can provide for the service, and it can make the decision based on this info. Thanks.