Add "asset-id" attribute to the NE

[italobusi]

The "asset-id" is a user-assigned identifier (as indicated in the current I-D) that applies to both components and NEs.

However, it is currently defined only for the components.

See: https://github.com/ietf-ivy-wg/network-inventory-yang/issues/33#issuecomment-1933254876

See: https://github.com/ietf-ivy-wg/network-inventory-yang/issues/33#issuecomment-1934226018

[italobusi]

Following the same proposal in https://github.com/ietf-ivy-wg/network-inventory-yang/issues/15#issuecomment-1955249852 and https://github.com/ietf-ivy-wg/network-inventory-yang/issues/33#issuecomment-1955252334 we add:

asset-id as “The user-assigned asset tracking identifier of the network element”

[nigel-r-davis]

On the definition of asset...

I note that in the Terminology section of https://datatracker.ietf.org/doc/html/draft-palmero-ivy-ps-almo-00, asset is defined as ”Asset: refers to hardware, software, applications, or services. An asset can be physical or virtual. The granularity of what constitutes an asset is deployment and implementation specific.”. I was expecting something more related to value. So something like “Asset: An item owned by a person/company (property) considered as having value (being useful).”. Whilst I agree that it can be hardware, software etc., the key focuses of asset in my mind are ownership and value.

[italobusi]

2024-02-21 Base Network Inventory weekly call

The issue still open for further discussion is whether there is a need for owner-assigned identifiers (such as the asset-id in RFC8348):

• "The owner-assigned tracking identifier of the component type."

• "The owner-assigned tracking identifier of the component instance."

• "The owner-assigned asset tracking identifier of the network element type."

• "The owner-assigned asset tracking identifier of the network element instance."

The naming of these attributes should be discussed after the terminology is stable.