[Idr] Re: Suggestion for the serice metadata draft//Re: I-D Action: draft-ietf-idr-5g-edge-service-metadata-19.txt

[Cheng Li <[e-mail]>]

Thank you Zongpeng, yes, your proposal of modifying the used capacity to available/left capacity looks better.
More clear and even, the available capacity/resource can be used alone without the total capacity/capability.

Respect,
Cheng


From: [e-mail] <[e-mail]>
Sent: Friday, June 28, 2024 4:58 AM
To: Linda Dunbar <[e-mail]>; Cheng Li <[e-mail]>
Cc: idr@ietf. org <[e-mail]>
Subject: Suggestion for the serice metadata draft//Re: [Idr] I-D Action: draft-ietf-idr-5g-edge-service-metadata-19.txt

Hi, Linda

    I have a suggestion for the draft.


[1]. https://datatracker.ietf.org/doc/html/draft-ietf-idr-5g-edge-service-metadata-19#section-4.7

    In the section 4.7, a untilzation sub-TLV is described. It describes the Utilization, i.e., how much of this capacity is currently being consumed.

    However, I suggest to change it to the available capacity, i.e., how much of this capacity is currently available for future usage.  In fact, it can be calculated out from the Utilization TLV by using the total capacity minus the Utilized capacity.

    After the modification, the total capacity in section 4.6 can be used as the weight for load balancing, which is relatively static; similarly, the available capacity can also be used as the weight for load balancing, which is relatively dynamic. Which one would be used on the Ingress (decision point) is the decided by the Ingress itself.


    The modification can reduce the minus process.




Best Regards
Zongpeng Du

________________________________
[e-mail]<mailto:[e-mail]> & [e-mail]<mailto:[e-mail]>

From: internet-drafts<mailto:[e-mail]>
Date: 2024-06-25 04:19
To: [e-mail]<mailto:[e-mail]>
CC: idr<mailto:[e-mail]>
Subject: [Idr] I-D Action: draft-ietf-idr-5g-edge-service-metadata-19.txt
Internet-Draft draft-ietf-idr-5g-edge-service-metadata-19.txt is now
available. It is a work item of the Inter-Domain Routing (IDR) WG of the IETF.

   Title:   BGP Extension for 5G Edge Service Metadata
   Authors: Linda Dunbar
            Kausik Majumdar
            Cheng Li
            Gyan Mishra
            Zongpeng Du
   Name:    draft-ietf-idr-5g-edge-service-metadata-19.txt
   Pages:   28
   Dates:   2024-06-24

Abstract:

   This draft describes a new Metadata Path Attribute and some Sub-TLVs
   for egress routers to advertise the Metadata about the attached edge
   services (ES).  The edge service Metadata can be used by the ingress
   routers in the 5G Local Data Network to make path selections not only
   based on the routing cost but also the running environment of the
   edge services.  The goal is to improve latency and performance for 5G
   edge services.

   The extension enables an edge service at one specific location to be
   more preferred than the others with the same IP address (ANYCAST) to
   receive data flow from a specific source, like a specific User
   Equipment (UE).

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-5g-edge-service-metadata/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-idr-5g-edge-service-metadata-19

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-idr-5g-edge-service-metadata-19

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
Idr mailing list -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>