search

ietf-wg-idr / draft-ietf-idr-5g-edge-service-metadata

Editing for the 5G Service Metadata
0 stars 2 forks source link

Add Resource ID #24

Open muzixing opened 5 months ago

muzixing commented 5 months ago

Also, I think it will be helpful if we can add a ResourceID into the sub-TLVs, such as Service-Oriented Capability Sub-TLV and Service-Oriented Utilization Sub-TLV. Because when we need to describe or handle the route associated with the route, it will be good to have a resourceID. A 4-octec/bytes ResourceID is recommended. How to set the value of it is up to the service.

A recommended format of service-oriented Capability is shown bellow.

image

A recommended format of service-oriented Utilization is shown bellow. image

Resource Identifier (4 bytes) is a logical term used to represent the resource associated with the service. It can be associated to various types of resources, such as compute, network, power, or others, within the site reachable by the NLRI. How to set the value of it depends on the need of the service.

lindadunbar commented 5 months ago

Thank you for the suggestion.

suehares commented 4 months ago

A resource ID was not added to the text (version -21, -22, or -23).

Issue 23 indicates that the reason is the resource ID does not stay consistent across the BGP sequence. (https://github.com/ietf-wg-idr/draft-ietf-idr-5g-edge-service-metadata-14/issues/23).

This comment needs to be confirmed, and this re-opened issue needs to be closed.