From 7ab03d3b5f9b538279c4398eb217d8e78bd7d6bb Mon Sep 17 00:00:00 2001 From: YuChaode Date: Mon, 10 Jul 2023 18:22:42 +0800 Subject: [PATCH] Update some text description for IETF117 (#98) 1. provided location pattern: fix #3 2. provided description taht equipment room and rack are optional: fix #7 3. removed some attributes we agreed to, includes equipment room uuid in parent-references and firmware-rev of NE: see PR #67 --- draft-ietf-ccamp-network-inventory-yang.md | 61 +- draft-ietf-ccamp-network-inventory-yang.txt | 656 ++++++------ draft-ietf-ccamp-network-inventory-yang.xml | 1015 ++++++++++--------- minutes/minutes-2023-06-28.md | 44 + minutes/minutes-2023-07-05.md | 38 + 5 files changed, 1013 insertions(+), 801 deletions(-) create mode 100644 minutes/minutes-2023-06-28.md create mode 100644 minutes/minutes-2023-07-05.md diff --git a/draft-ietf-ccamp-network-inventory-yang.md b/draft-ietf-ccamp-network-inventory-yang.md index d169386..43a336d 100644 --- a/draft-ietf-ccamp-network-inventory-yang.md +++ b/draft-ietf-ccamp-network-inventory-yang.md @@ -4,7 +4,7 @@ coding: utf-8 title: A YANG Data Model for Network Hardware Inventory abbrev: Network Hardware Inventory YANG -docname: draft-ietf-ccamp-network-inventory-yang-01 +docname: draft-ietf-ccamp-network-inventory-yang-02 submissiontype: IETF workgroup: CCAMP Working Group category: std @@ -63,6 +63,10 @@ contributor: ins: O. Gonzalez de Dios org: Telefonica email: oscar.gonzalezdedios@telefonica.com + - + name: Nigel Davis + org: Ciena + email: ndavis@ciena.com normative: TMF_SD2-20: @@ -79,7 +83,6 @@ normative: org: IANA target: https://www.iana.org/assignments/yang-parameters -informative: ONF_TR-547: title: TAPI v2.1.3 Reference Implementation Agreement author: @@ -88,6 +91,8 @@ informative: seriesinfo: ONF TR-547 TAPI RIA v1.0 target: https://opennetworking.org/wp-content/uploads/2020/08/TR-547-TAPI-v2.1.3-Reference-Implementation-Agreement-1.pdf +informative: + --- abstract This document defines a YANG data model for network hardware inventory data information. @@ -241,15 +246,17 @@ Logically, the relationship between these inventory objects can be described by +------------+ || || || || 1:N \/ - ||______________\+------------+ - |---------------/| chassis | - +------------+ + ||______________\+-------------+ + |---------------/| chassis/ |---+ + | sub-chassis |<--| + +-------------+ || ______1:N______||_____1:M_______ ||------------------ ---------|| - \/ \/ + \/ \/ +--------------+ +-----------+ - | slot/subslot | | board | + +---| slot | | board | + |-->| /sub-slot | | | +--------------+ +-----------+ || ||1:N @@ -377,6 +384,25 @@ The YANG data model for network hardware inventory mainly follows the same appro Some of the definitions taken from {{!RFC8348}} are actually based on the ENTITY-MIB {{!RFC6933}}. +For the component location information, the suggested pattern is the same as the pattern defined in section 4.2 of {{ONF_TR-547}} for the INVENTORY_ID property. + +In this draft the term 'chassis' is used instead of the term 'shelf', used in {{ONF_TR-547}}, since the term 'chassis' has broader applicability than the term 'shelf' and it is aligned with the terminology of {{!RFC8348}}. However, the component location string will use the acronyms 'sh' and 's_sh' for consistency with the {{ONF_TR-547}} definitions. + +{{tab-onf}} summarizes the relationship between the \ defined in {{ONF_TR-547}} and the components defined in this document. + +| <field> |meaning | +| ------------ | ------------ | +| ne |network element | +| r |rack | +| sh |chassis component | +| s_sh |sub-chassis component | +| sl | slot component | +| s_sl |sub-slot component | +| p | port component | +{: #tab-onf title="Meaning of <field>"} + +This pattern is a common practice in optical transport networks, but we consider it as also applicable for other technologies. + For state data like admin-state, oper-state and so on, we consider they are related to device hardware management and not hardware inventory. Therefore, they are outside of scope of this document. Same for the sensor-data, they should be defined in some other performance monitoring data models instead of inventory data model. We re-defined some attributes listed in {{!RFC8348}}, based on some integration experience for network wide inventory data. @@ -391,15 +417,11 @@ We re-defined some attributes listed in {{!RFC8348}}, based on some integration +--ro components +--ro component* [uuid] ................................... - +--ro parent-references - | +--ro equipment-room-uuid? leafref - | +--ro ne-uuid? leafref - | +--ro rack-uuid? leafref - | +--ro component-references - | +--ro component-reference* [index] - | +--ro index uint8 - | +--ro class? leafref - | +--ro uuid? leafref + +--ro parent-component-references + | +--ro component-reference* [index] + | +--ro index uint8 + | +--ro class? -> ../../../class + | +--ro uuid? -> ../../../uuid ................................... ~~~~ @@ -441,10 +463,16 @@ According to the description in {{!RFC8348}}, the attribute named "model-name" u ### Equipment Room +Usually the information about equipment rooms is not detectable by domain controller and configured manually. Sometimes, this information is not configured in the domain controller but directly in the Operators' owned OSS and therefore reporting information about the equipment rooms is optional when implementing this data model. + +Another scenario to analyze is when racks are not located in any equipment room: one possible solution is that the domain controller provides a "default" equipment room that contains all these racks. + Note: add some more attributes about equipment room in the future. ### Rack +Likewise for equipment rooms, usually the information about the rack is not detectable by domain controller and configured manually. Therefore reporting information about the racks is optional when implementing this data model. + Besides the common attributes mentioned in above section, rack could have some specific attributes, such as appearance-related attributes and electricity-related attributes. The height, depth and width are described by the figure below (please consider that the door of the rack is facing the user): @@ -508,7 +536,6 @@ We consider that some of the attributes defined in {{?RFC8348}} for components a +--ro network-element* [uuid] ................................... +--ro hardware-rev? string - +--ro firmware-rev? string +--ro software-rev? string +--ro mfg-name? string +--ro mfg-date? yang:date-and-time diff --git a/draft-ietf-ccamp-network-inventory-yang.txt b/draft-ietf-ccamp-network-inventory-yang.txt index f2337f9..8e7837c 100644 --- a/draft-ietf-ccamp-network-inventory-yang.txt +++ b/draft-ietf-ccamp-network-inventory-yang.txt @@ -5,18 +5,18 @@ CCAMP Working Group C. Yu Internet-Draft Huawei Technologies Intended status: Standards Track S. Belotti -Expires: 11 September 2023 Nokia +Expires: 8 January 2024 Nokia J.-F. Bouquier Vodafone F. Peruzzini TIM P. Bedard Cisco - 10 March 2023 + 7 July 2023 A YANG Data Model for Network Hardware Inventory - draft-ietf-ccamp-network-inventory-yang-01 + draft-ietf-ccamp-network-inventory-yang-02 Abstract @@ -48,14 +48,14 @@ Status of This Memo time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on 11 September 2023. + This Internet-Draft will expire on 8 January 2024. -Yu, et al. Expires 11 September 2023 [Page 1] +Yu, et al. Expires 8 January 2024 [Page 1] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 Copyright Notice @@ -83,41 +83,41 @@ Table of Contents 2.1. YANG Model Overview . . . . . . . . . . . . . . . . . . . 7 2.1.1. Common Design for All Inventory Objects . . . . . . . 9 2.1.2. Reference from RFC8348 . . . . . . . . . . . . . . . 10 - 2.1.3. Changes with respect to RFC8348 . . . . . . . . . . . 11 - 2.1.4. Equipment Room . . . . . . . . . . . . . . . . . . . 13 - 2.1.5. Rack . . . . . . . . . . . . . . . . . . . . . . . . 13 - 2.1.6. Network Element . . . . . . . . . . . . . . . . . . . 15 + 2.1.3. Changes with respect to RFC8348 . . . . . . . . . . . 12 + 2.1.4. Equipment Room . . . . . . . . . . . . . . . . . . . 14 + 2.1.5. Rack . . . . . . . . . . . . . . . . . . . . . . . . 14 + 2.1.6. Network Element . . . . . . . . . . . . . . . . . . . 16 2.1.7. Relationship between Hardware Inventory and Network - Topology models . . . . . . . . . . . . . . . . . . . 15 - 2.2. Efficiency Issue . . . . . . . . . . . . . . . . . . . . 17 - 2.3. Some Other Considerations . . . . . . . . . . . . . . . . 18 - 3. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 18 - 3.1. Network Hardware Inventory Tree Diagram . . . . . . . . . 18 + Topology models . . . . . . . . . . . . . . . . . . . 16 + 2.2. Efficiency Issue . . . . . . . . . . . . . . . . . . . . 18 + 2.3. Some Other Considerations . . . . . . . . . . . . . . . . 19 + 3. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 19 + 3.1. Network Hardware Inventory Tree Diagram . . . . . . . . . 19 3.2. Relationship between Topology and Network Inventory Tree - Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 20 - 4. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 20 - 4.1. YANG Data Model for Network Hardware Inventory . . . . . 20 + Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 21 + 4. YANG Data Models . . . . . . . . . . . . . . . . . . . . . . 21 + 4.1. YANG Data Model for Network Hardware Inventory . . . . . 21 4.2. YANG Data Model for Relationship between Topology and - Network Inventory . . . . . . . . . . . . . . . . . . . . 33 - 5. Manageability Considerations . . . . . . . . . . . . . . . . 36 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 36 - 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 36 - 8.1. Normative References . . . . . . . . . . . . . . . . . . 36 - 8.2. Informative References . . . . . . . . . . . . . . . . . 37 - Appendix A. Appendix . . . . . . . . . . . . . . . . . . . . . . 38 + Network Inventory . . . . . . . . . . . . . . . . . . . . 34 + 5. Manageability Considerations . . . . . . . . . . . . . . . . 37 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . 37 + 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 + 8.1. Normative References . . . . . . . . . . . . . . . . . . 37 + 8.2. Informative References . . . . . . . . . . . . . . . . . 38 + Appendix A. Appendix . . . . . . . . . . . . . . . . . . . . . . 39 -Yu, et al. Expires 11 September 2023 [Page 2] +Yu, et al. Expires 8 January 2024 [Page 2] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 - A.1. Comparison With Openconfig-platform Data Model . . . . . 38 - Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 41 - Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 41 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42 + A.1. Comparison With Openconfig-platform Data Model . . . . . 39 + Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 42 + Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 42 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 1. Introduction @@ -165,9 +165,9 @@ Internet-Draft Network Hardware Inventory YANG March 2023 -Yu, et al. Expires 11 September 2023 [Page 3] +Yu, et al. Expires 8 January 2024 [Page 3] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 The intention is to define a generic YANG data model that would be as @@ -221,9 +221,9 @@ Internet-Draft Network Hardware Inventory YANG March 2023 -Yu, et al. Expires 11 September 2023 [Page 4] +Yu, et al. Expires 8 January 2024 [Page 4] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 * data node @@ -277,9 +277,9 @@ Internet-Draft Network Hardware Inventory YANG March 2023 -Yu, et al. Expires 11 September 2023 [Page 5] +Yu, et al. Expires 8 January 2024 [Page 5] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 an interface on board @@ -333,9 +333,9 @@ Internet-Draft Network Hardware Inventory YANG March 2023 -Yu, et al. Expires 11 September 2023 [Page 6] +Yu, et al. Expires 8 January 2024 [Page 6] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 2.1. YANG Model Overview @@ -368,15 +368,17 @@ Internet-Draft Network Hardware Inventory YANG March 2023 +------------+ || || || || 1:N \/ - ||______________\+------------+ - |---------------/| chassis | - +------------+ + ||______________\+-------------+ + |---------------/| chassis/ |---+ + | sub-chassis |<--| + +-------------+ || ______1:N______||_____1:M_______ ||------------------ ---------|| \/ \/ +--------------+ +-----------+ - | slot/subslot | | board | + +---| slot | | board | + |-->| /sub-slot | | | +--------------+ +-----------+ || ||1:N @@ -385,14 +387,14 @@ Internet-Draft Network Hardware Inventory YANG March 2023 | port | +-----------+ - Figure 1: Relationship between inventory objects - -Yu, et al. Expires 11 September 2023 [Page 7] +Yu, et al. Expires 8 January 2024 [Page 7] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + + Figure 1: Relationship between inventory objects In [RFC8348], rack, chassis, slot, sub-slot, board and port are defined as components of network elements with generic attributes. @@ -443,11 +445,9 @@ Internet-Draft Network Hardware Inventory YANG March 2023 - - -Yu, et al. Expires 11 September 2023 [Page 8] +Yu, et al. Expires 8 January 2024 [Page 8] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 2.1.1. Common Design for All Inventory Objects @@ -501,9 +501,9 @@ Internet-Draft Network Hardware Inventory YANG March 2023 -Yu, et al. Expires 11 September 2023 [Page 9] +Yu, et al. Expires 8 January 2024 [Page 9] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 module: ietf-network-hardware-inventory @@ -557,9 +557,9 @@ Internet-Draft Network Hardware Inventory YANG March 2023 -Yu, et al. Expires 11 September 2023 [Page 10] +Yu, et al. Expires 8 January 2024 [Page 10] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 +--ro components @@ -582,6 +582,65 @@ Internet-Draft Network Hardware Inventory YANG March 2023 Some of the definitions taken from [RFC8348] are actually based on the ENTITY-MIB [RFC6933]. + For the component location information, the suggested pattern is the + same as the pattern defined in section 4.2 of [ONF_TR-547] for the + INVENTORY_ID property. + + In this draft the term 'chassis' is used instead of the term 'shelf', + used in [ONF_TR-547], since the term 'chassis' has broader + applicability than the term 'shelf' and it is aligned with the + terminology of [RFC8348]. However, the component location string + will use the acronyms 'sh' and 's_sh' for consistency with the + [ONF_TR-547] definitions. + + Table 2 summarizes the relationship between the defined in + [ONF_TR-547] and the components defined in this document. + + + + + + + + + + + + + + + + + + +Yu, et al. Expires 8 January 2024 [Page 11] + +Internet-Draft Network Hardware Inventory YANG July 2023 + + + +=========+=======================+ + | | meaning | + +=========+=======================+ + | ne | network element | + +---------+-----------------------+ + | r | rack | + +---------+-----------------------+ + | sh | chassis component | + +---------+-----------------------+ + | s_sh | sub-chassis component | + +---------+-----------------------+ + | sl | slot component | + +---------+-----------------------+ + | s_sl | sub-slot component | + +---------+-----------------------+ + | p | port component | + +---------+-----------------------+ + + Table 2: Meaning of + + This pattern is a common practice in optical transport networks, but + we consider it as also applicable for other technologies. + For state data like admin-state, oper-state and so on, we consider they are related to device hardware management and not hardware inventory. Therefore, they are outside of scope of this document. @@ -610,26 +669,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 - - - -Yu, et al. Expires 11 September 2023 [Page 11] +Yu, et al. Expires 8 January 2024 [Page 12] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 +--ro components +--ro component* [uuid] ................................... - +--ro parent-references - | +--ro equipment-room-uuid? leafref - | +--ro ne-uuid? leafref - | +--ro rack-uuid? leafref - | +--ro component-references - | +--ro component-reference* [index] - | +--ro index uint8 - | +--ro class? leafref - | +--ro uuid? leafref + +--ro parent-component-references + | +--ro component-reference* [index] + | +--ro index uint8 + | +--ro class? -> ../../../class + | +--ro uuid? -> ../../../uuid ................................... The hierarchical components' identifier could be found by the @@ -662,25 +714,22 @@ Internet-Draft Network Hardware Inventory YANG March 2023 Note: The detail of each *-specific-info YANG container is still under discussion, and the leaf attributes will be defined in future. +2.1.3.3. Part Number + According to the description in [RFC8348], the attribute named + "model-name" under the component, is preferred to have a customer- + visible part number value. "Model-name" is not straightforward to + understand and we suggest to rename it as "part-number" directly. - -Yu, et al. Expires 11 September 2023 [Page 12] +Yu, et al. Expires 8 January 2024 [Page 13] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 -2.1.3.3. Part Number - - According to the description in [RFC8348], the attribute named - "model-name" under the component, is preferred to have a customer- - visible part number value. "Model-name" is not straightforward to - understand and we suggest to rename it as "part-number" directly. - +--ro components +--ro component* [uuid] ................................... @@ -689,10 +738,25 @@ Internet-Draft Network Hardware Inventory YANG March 2023 2.1.4. Equipment Room + Usually the information about equipment rooms is not detectable by + domain controller and configured manually. Sometimes, this + information is not configured in the domain controller but directly + in the Operators' owned OSS and therefore reporting information about + the equipment rooms is optional when implementing this data model. + + Another scenario to analyze is when racks are not located in any + equipment room: one possible solution is that the domain controller + provides a "default" equipment room that contains all these racks. + Note: add some more attributes about equipment room in the future. 2.1.5. Rack + Likewise for equipment rooms, usually the information about the rack + is not detectable by domain controller and configured manually. + Therefore reporting information about the racks is optional when + implementing this data model. + Besides the common attributes mentioned in above section, rack could have some specific attributes, such as appearance-related attributes and electricity-related attributes. The height, depth and width are @@ -717,17 +781,9 @@ Internet-Draft Network Hardware Inventory YANG March 2023 - - - - - - - - -Yu, et al. Expires 11 September 2023 [Page 13] +Yu, et al. Expires 8 January 2024 [Page 14] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 ---------------- --- @@ -781,9 +837,9 @@ Internet-Draft Network Hardware Inventory YANG March 2023 -Yu, et al. Expires 11 September 2023 [Page 14] +Yu, et al. Expires 8 January 2024 [Page 15] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 2.1.6. Network Element @@ -796,7 +852,6 @@ Internet-Draft Network Hardware Inventory YANG March 2023 +--ro network-element* [uuid] ................................... +--ro hardware-rev? string - +--ro firmware-rev? string +--ro software-rev? string +--ro mfg-name? string +--ro mfg-date? yang:date-and-time @@ -831,17 +886,21 @@ Internet-Draft Network Hardware Inventory YANG March 2023 connections, so that it should appear in L0, L1 and L2 network topology. - It is important to describe this relationship for the sake of network - Operation and Maintenance (O&M). For example, the actual path of a - connection is described by the objects in network topology. When -Yu, et al. Expires 11 September 2023 [Page 15] + + + + +Yu, et al. Expires 8 January 2024 [Page 16] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + It is important to describe this relationship for the sake of network + Operation and Maintenance (O&M). For example, the actual path of a + connection is described by the objects in network topology. When there is a failure along this connection, the O&M engineers are more concerned with the physical location information behind the network objects for troubleshooting. @@ -884,19 +943,22 @@ Internet-Draft Network Hardware Inventory YANG March 2023 Figure 3: Relationship between the three YANG modules - module: ietf-hw-inventory-ref-topo - augment /nw:networks/nw:network/nw:node: - +--ro inventory-id? leafref - augment /nw:networks/nw:network/nw:node/nt:termination-point: - +--ro inventory-id? leafref -Yu, et al. Expires 11 September 2023 [Page 16] + + +Yu, et al. Expires 8 January 2024 [Page 17] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + + module: ietf-hw-inventory-ref-topo + augment /nw:networks/nw:network/nw:node: + +--ro inventory-id? leafref + augment /nw:networks/nw:network/nw:node/nt:termination-point: + +--ro inventory-id? leafref NOTE: the association between a link and a fiber&cable object has to be added in the future version. @@ -940,20 +1002,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 implementation. With a generic model, it is only needed to augment a new component class and extend some specific attributes for this new inventory component class, which is more flexible. We consider that - this generic data model, enabling a flexible and backward compatible - approach for other technologies, represents the main scope of this - draft. Solution description to efficiency/scalability limitations - mentioned above is considered as out-of-scope. - - -Yu, et al. Expires 11 September 2023 [Page 17] +Yu, et al. Expires 8 January 2024 [Page 18] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + this generic data model, enabling a flexible and backward compatible + approach for other technologies, represents the main scope of this + draft. Solution description to efficiency/scalability limitations + mentioned above is considered as out-of-scope. + 2.3. Some Other Considerations Note: review in future versions of this document whether the @@ -997,19 +1058,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 | +--ro alias? string | +--ro location? string | +--ro racks - | +--ro rack* [uuid] - | +--ro uuid yang:uuid - | +--ro name? string - | +--ro description? string - | +--ro alias? string -Yu, et al. Expires 11 September 2023 [Page 18] +Yu, et al. Expires 8 January 2024 [Page 19] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + | +--ro rack* [uuid] + | +--ro uuid yang:uuid + | +--ro name? string + | +--ro description? string + | +--ro alias? string | +--ro rack-location | | +--ro equipment-room-name? leafref | | +--ro row-number? uint32 @@ -1053,19 +1114,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 | +--ro class? -> ../../../class | +--ro uuid? -> ../../../uuid +--ro hardware-rev? string - +--ro firmware-rev? string - +--ro software-rev? string - +--ro serial-num? string - +--ro mfg-name? string - +--ro part-number? string -Yu, et al. Expires 11 September 2023 [Page 19] +Yu, et al. Expires 8 January 2024 [Page 20] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + +--ro firmware-rev? string + +--ro software-rev? string + +--ro serial-num? string + +--ro mfg-name? string + +--ro part-number? string +--ro asset-id? string +--ro is-fru? boolean +--ro mfg-date? @@ -1109,19 +1170,20 @@ Internet-Draft Network Hardware Inventory YANG March 2023 "urn:ietf:params:xml:ns:yang:ietf-network-hardware-inventory"; prefix nhi; - import ietf-yang-types { - prefix yang; - reference - "RFC6991: Common YANG Data Types."; - } -Yu, et al. Expires 11 September 2023 [Page 20] +Yu, et al. Expires 8 January 2024 [Page 21] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + import ietf-yang-types { + prefix yang; + reference + "RFC6991: Common YANG Data Types."; + } + import iana-hardware { prefix ianahw; reference @@ -1165,19 +1227,18 @@ Internet-Draft Network Hardware Inventory YANG March 2023 The model fully conforms to the Network Management Datastore Architecture (NMDA). - Copyright (c) 2022 IETF Trust and the persons - identified as authors of the code. All rights reserved. - - Redistribution and use in source and binary forms, with or - without modification, is permitted pursuant to, and subject - -Yu, et al. Expires 11 September 2023 [Page 21] +Yu, et al. Expires 8 January 2024 [Page 22] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + Copyright (c) 2022 IETF Trust and the persons + identified as authors of the code. All rights reserved. + + Redistribution and use in source and binary forms, with or + without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents @@ -1221,19 +1282,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 (e.g., component, equipment room) defined in this module."; leaf uuid { type yang:uuid; - description - "Uniquely identifies an entity (e.g., component)."; - } - leaf name { - type string; -Yu, et al. Expires 11 September 2023 [Page 22] +Yu, et al. Expires 8 January 2024 [Page 23] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + description + "Uniquely identifies an entity (e.g., component)."; + } + leaf name { + type string; description "A name for an entity (e.g., component), as specified by a network manager, that provides a non-volatile 'handle' @@ -1277,19 +1338,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 } description "Names of equipment rooms where the NE is located. - Please note that a NE could be located in several - equipment rooms."; - } - } - uses ne-specific-info-grouping; -Yu, et al. Expires 11 September 2023 [Page 23] +Yu, et al. Expires 8 January 2024 [Page 24] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + Please note that a NE could be located in several + equipment rooms."; + } + } + uses ne-specific-info-grouping; uses components-grouping; } } @@ -1333,19 +1394,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 description "indicates the vendor-spefic device type infomation."; } - } - - grouping equipment-rooms-grouping { - description - "The attributes of the equipment rooms."; -Yu, et al. Expires 11 September 2023 [Page 24] +Yu, et al. Expires 8 January 2024 [Page 25] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + } + + grouping equipment-rooms-grouping { + description + "The attributes of the equipment rooms."; container equipment-rooms { description "The container for the list of equipment rooms."; @@ -1389,19 +1450,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 path "/nhi:network-hardware-inventory" + "/nhi:network-elements/nhi:network-element" + "[nhi:uuid=current()/../ne-ref]/nhi:components" - + "/nhi:component/nhi:uuid"; - } - description - "The reference to the chassis component within - the network element and contained by the rack."; -Yu, et al. Expires 11 September 2023 [Page 25] +Yu, et al. Expires 8 January 2024 [Page 26] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + + "/nhi:component/nhi:uuid"; + } + description + "The reference to the chassis component within + the network element and contained by the rack."; } leaf relative-position { type uint8; @@ -1445,19 +1506,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 } leaf height { type uint16; - units millimeter; - description - "Rack height."; - } - leaf width { -Yu, et al. Expires 11 September 2023 [Page 26] +Yu, et al. Expires 8 January 2024 [Page 27] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + units millimeter; + description + "Rack height."; + } + leaf width { type uint16; units millimeter; description @@ -1501,19 +1562,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 } leaf class { type identityref { - base ianahw:hardware-class; - } - description - "An indication of the general hardware type of the - component."; -Yu, et al. Expires 11 September 2023 [Page 27] +Yu, et al. Expires 8 January 2024 [Page 28] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + base ianahw:hardware-class; + } + description + "An indication of the general hardware type of the + component."; reference "RFC 8348: A YANG Data Model for Hardware Management."; } @@ -1557,19 +1618,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 hierarchy."; } leaf class { - type leafref { - path "../../../nhi:class"; - } - description - "Class of the hierarchial parent component."; -Yu, et al. Expires 11 September 2023 [Page 28] +Yu, et al. Expires 8 January 2024 [Page 29] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + type leafref { + path "../../../nhi:class"; + } + description + "Class of the hierarchial parent component."; } leaf uuid { type leafref { @@ -1613,19 +1674,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 } leaf serial-num { type string; - description - "The vendor-specific serial number string for the - component. The preferred value is the serial number - string actually printed on the component itself (if - present)."; -Yu, et al. Expires 11 September 2023 [Page 29] +Yu, et al. Expires 8 January 2024 [Page 30] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + description + "The vendor-specific serial number string for the + component. The preferred value is the serial number + string actually printed on the component itself (if + present)."; reference "RFC 6933: Entity MIB (Version 4) - entPhysicalSerialNum"; @@ -1669,19 +1730,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 "This node is a user-assigned asset tracking identifier for the component. - A server implementation MAY map this leaf to the - entPhysicalAssetID MIB object. Such an implementation - needs to use some mechanism to handle the differences in - size and characters allowed between this leaf and - entPhysicalAssetID. The definition of such a mechanism -Yu, et al. Expires 11 September 2023 [Page 30] +Yu, et al. Expires 8 January 2024 [Page 31] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + A server implementation MAY map this leaf to the + entPhysicalAssetID MIB object. Such an implementation + needs to use some mechanism to handle the differences in + size and characters allowed between this leaf and + entPhysicalAssetID. The definition of such a mechanism is outside the scope of this document."; reference "RFC 6933: Entity MIB (Version 4) - entPhysicalAssetID"; @@ -1725,19 +1786,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 defined by RFC8348. These attributes could be component-specific. Here we provide a extension structure for all the components - we recognized. We will enrich these component specifc - containers in the future."; - choice component-class { - description - "This extension differs between different component -Yu, et al. Expires 11 September 2023 [Page 31] +Yu, et al. Expires 8 January 2024 [Page 32] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + we recognized. We will enrich these component specifc + containers in the future."; + choice component-class { + description + "This extension differs between different component classes."; case chassis { when "./class = 'ianahw:chassis'"; @@ -1781,19 +1842,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 grouping chassis-specific-info-grouping { //To be enriched in the future. - description - "Specific attributes applicable to chassis only."; - } - - grouping slot-specific-info-grouping { -Yu, et al. Expires 11 September 2023 [Page 32] +Yu, et al. Expires 8 January 2024 [Page 33] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + + description + "Specific attributes applicable to chassis only."; + } + grouping slot-specific-info-grouping { //To be enriched in the future. description "Specific attributes applicable to slots only."; @@ -1837,19 +1898,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 } import ietf-network-hardware-inventory { - prefix nhi; - reference - "RFC XXXX: A YANG Data Model for Network Hardware Inventory."; - //RFC Editor: replace XXXX with actual RFC number, update date - //information and remove this note -Yu, et al. Expires 11 September 2023 [Page 33] +Yu, et al. Expires 8 January 2024 [Page 34] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + prefix nhi; + reference + "RFC XXXX: A YANG Data Model for Network Hardware Inventory."; + //RFC Editor: replace XXXX with actual RFC number, update date + //information and remove this note } organization @@ -1893,19 +1954,19 @@ Internet-Draft Network Hardware Inventory YANG March 2023 the RFC itself for full legal notices. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL - NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', - 'MAY', and 'OPTIONAL' in this document are to be interpreted as - described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, - they appear in all capitals, as shown here."; - -Yu, et al. Expires 11 September 2023 [Page 34] +Yu, et al. Expires 8 January 2024 [Page 35] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', + 'MAY', and 'OPTIONAL' in this document are to be interpreted as + described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, + they appear in all capitals, as shown here."; + // RFC Ed.: replace XXXX with actual RFC number and remove this // note. // RFC Ed.: update the date below with the date of RFC publication @@ -1949,20 +2010,20 @@ Internet-Draft Network Hardware Inventory YANG March 2023 path "/nhi:network-hardware-inventory/nhi:network-elements" + "/nhi:network-element/nhi:components/nhi:component" + "/nhi:uuid"; - } - config false; - description - "The identifier of the port component from which this Link - Termination Point (LTP) is abstracted"; -Yu, et al. Expires 11 September 2023 [Page 35] +Yu, et al. Expires 8 January 2024 [Page 36] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 } + config false; + description + "The identifier of the port component from which this Link + Termination Point (LTP) is abstracted"; + } } } @@ -1990,11 +2051,29 @@ Internet-Draft Network Hardware Inventory YANG March 2023 IANA, "YANG Parameters", n.d., . + [ONF_TR-547] + Open Networking Foundation (ONF), "TAPI v2.1.3 Reference + Implementation Agreement", ONF TR-547 TAPI RIA v1.0 , July + 2020, . + [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . + + + + + + +Yu, et al. Expires 8 January 2024 [Page 37] + +Internet-Draft Network Hardware Inventory YANG July 2023 + + [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, @@ -2009,15 +2088,6 @@ Internet-Draft Network Hardware Inventory YANG March 2023 RFC 6991, DOI 10.17487/RFC6991, July 2013, . - - - - -Yu, et al. Expires 11 September 2023 [Page 36] - -Internet-Draft Network Hardware Inventory YANG March 2023 - - [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . @@ -2052,27 +2122,17 @@ Internet-Draft Network Hardware Inventory YANG March 2023 Ceccarelli, "Applicability of Abstraction and Control of Traffic Engineered Networks (ACTN) to Packet Optical Integration (POI)", Work in Progress, Internet-Draft, - draft-ietf-teas-actn-poi-applicability-08, 11 January - 2023, . - - [ONF_TR-547] - Open Networking Foundation (ONF), "TAPI v2.1.3 Reference - Implementation Agreement", ONF TR-547 TAPI RIA v1.0 , July - 2020, . - - - - -Yu, et al. Expires 11 September 2023 [Page 37] +Yu, et al. Expires 8 January 2024 [Page 38] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + + draft-ietf-teas-actn-poi-applicability-08, 11 January + 2023, . [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., Ananthakrishnan, H., and X. Liu, "A YANG Data Model for @@ -2118,18 +2178,18 @@ A.1. Comparison With Openconfig-platform Data Model +------------------------+-----------------------+-----------------+ | firmware-version | firmware-rev | | +------------------------+-----------------------+-----------------+ - | software-version | software-rev | | - +------------------------+-----------------------+-----------------+ - | serial-no | serial-num | | - +------------------------+-----------------------+-----------------+ -Yu, et al. Expires 11 September 2023 [Page 38] +Yu, et al. Expires 8 January 2024 [Page 39] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + | software-version | software-rev | | + +------------------------+-----------------------+-----------------+ + | serial-no | serial-num | | + +------------------------+-----------------------+-----------------+ | part-no | part-number | | +------------------------+-----------------------+-----------------+ | clei-code | | TBD | @@ -2174,18 +2234,18 @@ Internet-Draft Network Hardware Inventory YANG March 2023 | subcomponents | contained-child | | +------------------------+-----------------------+-----------------+ | chassis | chassis-specific-info | | - +------------------------+-----------------------+-----------------+ - | port | port-specific-info | | - +------------------------+-----------------------+-----------------+ - | power-supply | | TBD | -Yu, et al. Expires 11 September 2023 [Page 39] +Yu, et al. Expires 8 January 2024 [Page 40] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + +------------------------+-----------------------+-----------------+ + | port | port-specific-info | | + +------------------------+-----------------------+-----------------+ + | power-supply | | TBD | +------------------------+-----------------------+-----------------+ | fan | | Fan is | | | | considered as a | @@ -2230,17 +2290,18 @@ Internet-Draft Network Hardware Inventory YANG March 2023 | | | need to define | | | | as a single | | | | component | - +------------------------+-----------------------+-----------------+ - - Table 2: Comparison between openconfig platform and inventory - data models -Yu, et al. Expires 11 September 2023 [Page 40] +Yu, et al. Expires 8 January 2024 [Page 41] -Internet-Draft Network Hardware Inventory YANG March 2023 +Internet-Draft Network Hardware Inventory YANG July 2023 + + + +------------------------+-----------------------+-----------------+ + Table 3: Comparison between openconfig platform and inventory + data models As it mentioned in Section 2.1.2 that state data and performance data are out of scope of our data model, it is same for alarm data and it @@ -2284,18 +2345,18 @@ Contributors Email: lana.wubo@huawei.com - Chenfang Zhang - China Unicom - Email: zhangcf80@chinaunicom.cn +Yu, et al. Expires 8 January 2024 [Page 42] + +Internet-Draft Network Hardware Inventory YANG July 2023 -Yu, et al. Expires 11 September 2023 [Page 41] - -Internet-Draft Network Hardware Inventory YANG March 2023 + Chenfang Zhang + China Unicom + Email: zhangcf80@chinaunicom.cn Oscar Gonzalez de Dios @@ -2303,6 +2364,11 @@ Internet-Draft Network Hardware Inventory YANG March 2023 Email: oscar.gonzalezdedios@telefonica.com + Nigel Davis + Ciena + Email: ndavis@ciena.com + + Authors' Addresses Chaode Yu @@ -2339,14 +2405,4 @@ Authors' Addresses - - - - - - - - - - -Yu, et al. Expires 11 September 2023 [Page 42] +Yu, et al. Expires 8 January 2024 [Page 43] diff --git a/draft-ietf-ccamp-network-inventory-yang.xml b/draft-ietf-ccamp-network-inventory-yang.xml index e02daa2..b3dcc71 100644 --- a/draft-ietf-ccamp-network-inventory-yang.xml +++ b/draft-ietf-ccamp-network-inventory-yang.xml @@ -13,7 +13,7 @@ - + A YANG Data Model for Network Hardware Inventory @@ -48,7 +48,7 @@ - + CCAMP Working Group @@ -251,15 +251,17 @@ Please remove this note. +------------+ || || || || 1:N \/ - ||______________\+------------+ - |---------------/| chassis | - +------------+ + ||______________\+-------------+ + |---------------/| chassis/ |---+ + | sub-chassis |<--| + +-------------+ || ______1:N______||_____1:M_______ ||------------------ ---------|| - \/ \/ + \/ \/ +--------------+ +-----------+ - | slot/subslot | | board | + +---| slot | | board | + |-->| /sub-slot | | | +--------------+ +-----------+ || ||1:N @@ -384,6 +386,33 @@ module: ietf-network-hardware-inventory Some of the definitions taken from are actually based on the ENTITY-MIB . +For the component location information, the suggested pattern is the same as the pattern defined in section 4.2 of for the INVENTORY_ID property. + +In this draft the term 'chassis' is used instead of the term 'shelf', used in , since the term 'chassis' has broader applicability than the term 'shelf' and it is aligned with the terminology of . However, the component location string will use the acronyms 'sh' and 's_sh' for consistency with the definitions. + + summarizes the relationship between the <field> defined in and the components defined in this document. + + + <field> + meaning + ne + network element + r + rack + sh + chassis component + s_sh + sub-chassis component + sl + slot component + s_sl + sub-slot component + p + port component + + +This pattern is a common practice in optical transport networks, but we consider it as also applicable for other technologies. + For state data like admin-state, oper-state and so on, we consider they are related to device hardware management and not hardware inventory. Therefore, they are outside of scope of this document. Same for the sensor-data, they should be defined in some other performance monitoring data models instead of inventory data model. We re-defined some attributes listed in , based on some integration experience for network wide inventory data. @@ -399,15 +428,11 @@ module: ietf-network-hardware-inventory +--ro components +--ro component* [uuid] ................................... - +--ro parent-references - | +--ro equipment-room-uuid? leafref - | +--ro ne-uuid? leafref - | +--ro rack-uuid? leafref - | +--ro component-references - | +--ro component-reference* [index] - | +--ro index uint8 - | +--ro class? leafref - | +--ro uuid? leafref + +--ro parent-component-references + | +--ro component-reference* [index] + | +--ro index uint8 + | +--ro class? -> ../../../class + | +--ro uuid? -> ../../../uuid ................................... ]]> @@ -453,11 +478,17 @@ module: ietf-network-hardware-inventory
Equipment Room +Usually the information about equipment rooms is not detectable by domain controller and configured manually. Sometimes, this information is not configured in the domain controller but directly in the Operators' owned OSS and therefore reporting information about the equipment rooms is optional when implementing this data model. + +Another scenario to analyze is when racks are not located in any equipment room: one possible solution is that the domain controller provides a "default" equipment room that contains all these racks. + Note: add some more attributes about equipment room in the future.
Rack +Likewise for equipment rooms, usually the information about the rack is not detectable by domain controller and configured manually. Therefore reporting information about the racks is optional when implementing this data model. + Besides the common attributes mentioned in above section, rack could have some specific attributes, such as appearance-related attributes and electricity-related attributes. The height, depth and width are described by the figure below (please consider that the door of the rack is facing the user): @@ -520,7 +551,6 @@ The height, depth and width are described by the figure below (please consider t +--ro network-element* [uuid] ................................... +--ro hardware-rev? string - +--ro firmware-rev? string +--ro software-rev? string +--ro mfg-name? string +--ro mfg-date? yang:date-and-time @@ -1492,140 +1522,150 @@ module ietf-hw-inventory-ref-topo { - - + + + TAPI v2.1.3 Reference Implementation Agreement + + Open Networking Foundation (ONF) + + + + + - -A YANG Data Model for Hardware Management - - - - - -This document defines a YANG data model for the management of hardware on a single server. - - - + + A YANG Data Model for Hardware Management + + + + + + + This document defines a YANG data model for the management of hardware on a single server. + + + + - - - -Network Management Datastore Architecture (NMDA) - - - - - - -Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950. - - - + + Network Management Datastore Architecture (NMDA) + + + + + + + + Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950. + + + + - - - -The YANG 1.1 Data Modeling Language - - -YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF). - - - + + The YANG 1.1 Data Modeling Language + + + + YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF). + + + + - - - -Network Configuration Protocol (NETCONF) - - - - - -The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] - - - + + Network Configuration Protocol (NETCONF) + + + + + + + The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] + + + + - - - -Key words for use in RFCs to Indicate Requirement Levels - - -In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. - - - - + + Key words for use in RFCs to Indicate Requirement Levels + + + + In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. + + + + + - - - -Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words - - -RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. - - - - + + Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words + + + + RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. + + + + + - - - -YANG Tree Diagrams - - - -This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language. - - - - + + YANG Tree Diagrams + + + + + This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language. + + + + + - - - -Common YANG Data Types - - -This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. - - - + + Common YANG Data Types + + + + This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. + + + + - - - -Entity MIB (Version 4) - - - - - -This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single Simple Network Management Protocol (SNMP) agent. This document specifies version 4 of the Entity MIB. This memo obsoletes version 3 of the Entity MIB module published as RFC 4133. - - - + + Entity MIB (Version 4) + + + + + + + This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single Simple Network Management Protocol (SNMP) agent. This document specifies version 4 of the Entity MIB. This memo obsoletes version 3 of the Entity MIB module published as RFC 4133. + + + + @@ -1635,16 +1675,6 @@ module ietf-hw-inventory-ref-topo { - - - TAPI v2.1.3 Reference Implementation Agreement - - Open Networking Foundation (ONF) - - - - - @@ -1687,22 +1717,22 @@ module ietf-hw-inventory-ref-topo { - - - -A YANG Data Model for Network Topologies - - - - - - - -This document defines an abstract (generic, or base) YANG data model for network/service topologies and inventories. The data model serves as a base model that is augmented with technology-specific details in other, more specific topology and inventory data models. - - - + + A YANG Data Model for Network Topologies + + + + + + + + + This document defines an abstract (generic, or base) YANG data model for network/service topologies and inventories. The data model serves as a base model that is augmented with technology-specific details in other, more specific topology and inventory data models. + + + + @@ -1900,346 +1930,363 @@ module ietf-hw-inventory-ref-topo { oscar.gonzalezdedios@telefonica.com + + Ciena +
+ ndavis@ciena.com +
+
diff --git a/minutes/minutes-2023-06-28.md b/minutes/minutes-2023-06-28.md new file mode 100644 index 0000000..eaabd0d --- /dev/null +++ b/minutes/minutes-2023-06-28.md @@ -0,0 +1,44 @@ +# Network Inventory weekly call (June 28, 2023) + +## Participants + +- Aihua Guo +- Daniel King +- Fabio Peruzzini +- Jeff Bouquier +- Nigel Davis +- Sergio Belotti +- Yu Chaode + +## Admin + +### Closed Issue + +None + +### Next calls + +- July 5th at 4pm CEST / 10am NA EDT / 10pm CST + +## Discussion + +### Structure for location/position information (issue #3) + +The text has been provided in the YANG file, we agree to close this issue. + +### Management of NEs with multiple racks (issue #7) + +The pizza box is modeled as a chassis. +We need to provide some text description in the document to indicate that equipment-room and rack are optional, so that the enterprise scenario can be satisfied. +the text is suggested to provided in the new update version of document. +the pizza box scenario can be closed. + +the case of a single-board NE is not a common scenario. we can close this issue, and may re-open this issue when needed + +### Management of pizza boxes (issue #13) + +We can close this issue once we provide text description. Please reference the conclusion of issue #7 + +### Management of equipment rooms and racks (issue #8) + +the modeling of equipment-room are related to the discussion of site, we suggest to close this issue after we are aligned with issue #86. diff --git a/minutes/minutes-2023-07-05.md b/minutes/minutes-2023-07-05.md new file mode 100644 index 0000000..ce4e92e --- /dev/null +++ b/minutes/minutes-2023-07-05.md @@ -0,0 +1,38 @@ +# Network Inventory weekly call (July 5, 2023) + +## Participants + +- Aihua Guo +- Italo Busi +- Jeff Bouquier +- Nigel Davis +- Sergio Belotti +- Yu Chaode + +## Admin + +### Closed Issue + +None + +### Next calls + +- July 12th at 4pm CEST / 10am NA EDT / 10pm CST + +## Discussion + +### Updated text for IETF 117 (PR #98) + +Review text proposal from Chaode to update the I-D text before IETF 117: +- aligned the YANG tree snapshots with the YANG model changes in PR #67 +- added to describe the suggested pattern for the component location (based on ONF TR-547): fix #3 +- added text to indicate that support for equipment-rooms and racks is optional: fix #7 + +More detailed text has to be provided to complete the specification of the component location format based on ONF TR-547. There are two options: +1. make a normative reference to ONF TR-547; +2. copy useful text from ONF TR-547. + +- [ ] Italo/Nigel: to check offline whether it is possible to copy text from ONF TR-547 + +- [ ] Chaode/Italo: add Nigel as contributor to the I-D +