Re: [Idr] I-D Action: draft-ietf-idr-5g-edge-service-metadata-09.txt

["[e-mail]" <[e-mail]>]

Hi, linda，
Thanks for your response.  
Section 3 Metadata Influenced Ingress Node Behavior. 
As of now, the document describes 4 examples of  edge DC running environment metrics. We think it is useful to list a few more examples, such as computing resources，service capability and service status, which are the possible candidates but not to be specified. Of course, it is better to coordinates with CATS WG, however, I think this draft is not fully linked to CATS, so we suggest to retaining my proposed modifications to make this draft more comprehensive and easy to understand.

Section 4.4 Service Delay Predication
Computing service status is to indictcate the current state of the  computing service, the parameters can include  at least one of service identification (service ID),service connections number and service duration and so on. 
Service connections number refers to the current number of available service connections(e.g. sessions number). 
Service Duration means the time period between the start date and the terminated date of each Service. Additional definitions may apply in Service Description.
   
Thannk you very much,
 Yao huijuan 


[e-mail]
 
From: Linda Dunbar
Date: 2023-10-18 07:24
To: [e-mail]; draft-ietf-idr-5g-edge-service-metadata
CC: idr
Subject: RE: [Idr] I-D Action: draft-ietf-idr-5g-edge-service-metadata-09.txt
Yaohuijuan, 
 
Thank you very much for your valuable comments. 
 
Here are our resolutions to your suggested changes:
 
Section 3 Metadata Influenced Ingress Node Behavior:
 
The original text is
“The goal of this Edge Service Metadata Path Attribute is for egress routers to propagate the metrics about their running environment to ingress routers. Here are some examples of the metrics propagated by
the egress routers:”
 
 
For your following suggested addition, I think most of them, such as computing power, resources, etc. , should be discussed in the CATS WG. The purpose of BGP Metadata Path Attribute is to carry the detailed SUB-TLVs once those proposed metrics are finalized by CATS WG.
 
How about we change the text to:
“The goal of this Edge Service Metadata Path Attribute is for egress routers to propagate the metrics about their running environment to ingress routers. CATS WG has been created to identify more detailed metrics about edge services running environment, such as  [draft-ldbc-cats-framework]. Once those metrics are finalized, their corresponding sub-TLVs can be carried under the Metadata Path Attribute if those metrics need to be distributed by BGP. Here are some examples of the metrics propagated by the egress routers.”
 
Section 4.4 Service Delay Predication:
 
The original text of -09 is:
“The Service Delay Prediction Index is a value that predicts processing delays at the site for future service requests. The
higher the value, the longer of the delay.”
 
You suggest changing to the following:
The Service Delay Prediction Index is a value that predicts processing delays at the site for future service requests. The
higher the value, the longer of the delay. The Service Delay Prediction Index is one of computing service status information,which can also include service connections number, and service duration and so on.
 
What do you mean by “service connections number”?  what is your definition of “service duration” and “computing service status”? 
 
Thank you very much, 
Linda
 
From: [e-mail] <[e-mail]> 
Sent: Wednesday, October 11, 2023 6:56 PM
To: draft-ietf-idr-5g-edge-service-metadata <[e-mail]>
Cc: idr <[e-mail]>; Linda Dunbar <[e-mail]>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-5g-edge-service-metadata-09.txt
 
Hi, authors,
 
I have read through this document, it is clear to define the Metadata Path Attribute for the computing characters. I have some comments  in attachment,thanks. 
 


[e-mail]
 
From: internet-drafts
Date: 2023-09-08 00:00
To: [e-mail]
CC: idr
Subject: [Idr] I-D Action: draft-ietf-idr-5g-edge-service-metadata-09.txt
Internet-Draft draft-ietf-idr-5g-edge-service-metadata-09.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
            Haibo Wang
            Gyan Mishra
            Zongpeng Du
   Name:    draft-ietf-idr-5g-edge-service-metadata-09.txt
   Pages:   21
   Dates:   2023-09-07
 
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-09
 
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-idr-5g-edge-service-metadata-09
 
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
 
 
_______________________________________________
Idr mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/idr