Specify valid Name Types for ServiceInterfacePoint

Open-Network-Models-and-Interfaces-ONMI / TAPI

LF ONMI Transport API Repository (TAPI)

https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI/wiki

Apache License 2.0

94 stars 80 forks source link

Specify valid Name Types for ServiceInterfacePoint #190

Closed karthik-sethuraman closed 7 months ago

karthik-sethuraman commented 7 years ago

In TAPI, the NameAndValue is currently being used as "KeyAndValue" - the valueName attribute of the data-type is specified to be object key.

So it would make sense to refactor the attribute "valueName" to "nameType"
Make the type of "key" attribute to be an extensible enumeration NameType
use the following initial values for the NameType enum - [IPV4, IPV6, MAC, TNA, LFID, LABEL, TID, TE_ID, NODEID]

karthik-sethuraman commented 7 years ago

TAPI Call 6/6/2017: - Noted that since this is a common data type used by all TAPI classes, the valid/applicable list of enum literals would be constrained by the usage (specific to class type it is being applied). So we need to define this as an extensible base enumeration type NameType and create specific extensions per usage class type, e.g. NodeNameType, ServiceInterfacePointNameType, etc

amazzini commented 7 months ago

This issue has been closed due to the lack of activity for more than one year. Please reopen it if follow up is necessary.