Missing attributes from RFC8348

[italobusi]

Evaluate whether there are attributes missing in RFC8348 which are needed to be reported in the Network Inventory model

See: https://github.com/italobusi/ietf-network-inventory/issues/2#issuecomment-903086514

[italobusi]

2022-06-22 Network Inventory weekly call

Chaode presented some attributes not considered in RFC8348 for the equipment-room, rack, chassis, (sub-) slot , NE, board, port etc:

Attributes——0621.xlsx

The attributes have been reviewed one by one. Perhaps some of them are too detailed. Would be good to have the inputs from other Vendors like Nokia and Cisco to be able to cross-check if some attributes are missing according to these other Vendors.

Chaode then presented a proposal to define which attributes should be RW or RO. Aihua mentioned that, in principle, everything in the HW network inventory data model should be Read-Only.

• [ ] @jbouqui153 : check internally if RO is confirmed for network inventory info

[italobusi]

2022-07-01 Network Inventory weekly call

[x] @jbouqui153 : check internally if RO is confirmed for network inventory info

It is confirmed that all the attributes in the inventory model should be RO

Review of the additional attributes provided by Chaode in Attributes——0621.xlsx and agreed that:

• proposed attributes for the equipment-room
  • country-or-region and province-or-state attributes should not be added since this information is already provided by the location attribute already existing in PR ietf-ccamp-wg/ietf-network-inventory#43 (to be renamed as site-location)
  • rename the site attribute as site-name
  • the data type for the room-no should be string
  • remove the value unknown from the cable-layout-type and defent-static-floor attributes: the attribute can be omitted when not know
• proposed attributes for the ne:
  • the product-name is already existing in draft PR ietf-ccamp-wg/ietf-network-inventory#43
  • clarify the IPv4 and IPv6 addresses are to connect with the management system

[italobusi]

2022-09-14 Network Inventory weekly call

Chenfang and Chaode has reviewed the missing attributes and provided a proposal: Attribute_from_CU@2022-09-14.xlsx.

The attributes highlighted in yellow are identified gaps that need to be addressed by new attributes.

The proposal has been presented. To be further discussed in the next calls

[italobusi]

2022-09-21 Network Inventory weekly call

Reviewed table from @YuChaode : Attributes.xlsx

Jeff: The attributes from China Unicom are too detailed. I suggest to discuss the attributes table sent from @YuChaode before to discuss whether the attributes from RFC8348 are applicable for NE and components.