Markdown Version | Session Recording

Session Date/Time: 10 Jan 2024 15:00

IVY

Summary

The IVY interim meeting primarily focused on discussing the scope of the adopted Network Inventory Core Model, specifically whether to incorporate read/write configuration capabilities. Cha presented several use cases for configurable inventory attributes, leading to a broader discussion among participants regarding the definition of "inventory" within the context of the IVY Working Group. A clear sense emerged that the WG needs to establish an explicit definition of "inventory" to guide the inclusion of future features, particularly those related to configuration, hardware management, and distinguishing between network and device-level concerns.

Key Discussion Points

• Working Group Status and Logistics:
  • The Network Inventory Core Model document has been adopted by the working group after IETF 118, with sufficient support and no objections indicating working group consensus.
  • This was the second of three planned interim meetings before IETF 119.
  • The chairs apologized for issues in the previous interim meeting and encouraged participants to utilize interim meetings for document acceleration.
  • Weekly design team meetings for the Network Inventory Core Model are ongoing and open to all.
• Discussion on Read/Write Capabilities for Inventory Model:
  • Cha presented on the "YANG data model for Network Inventory" (read/write capabilities).
  • It was clarified that the current read/write state of attributes in the adopted draft was an oversight; the initial intention was a read-only inventory model.
  • Six potential use cases for configurable inventory attributes were presented:
    1. Configuring user-defined information (e.g., name, alias, description, asset ID, UUID) for inventory objects. This approach was confirmed as acceptable by one participant via both GUI/EMS and direct domain controller interaction.
    2. Configuring maintenance status for network elements, allowing for suppression of unnecessary alarms during maintenance windows.
    3. Configuring ASON switch (an optical-specific feature) for network elements.
    4. Creation of virtual network elements: Previously, a participant (Bo) indicated this is typically service-driven rather than an interface-driven action for IP technology, and is not an inventory function for creation but might relate to planning.
    5. Configuration of power management parameters: Tony Lee later elaborated on this, proposing power-save (read/write) and expected-input/output-bandwidth leaves to enable hardware power management.
    6. Matching intent/planned network element configuration.
• Debate on the Definition and Scope of "Inventory":
  • A central concern was raised by Daniel and other participants regarding whether use cases 2, 3, 4, 5, and 6 truly fit the definition of "inventory."
  • Nigel emphasized that the term "inventory" has varied definitions across the industry (e.g., TMF includes "everything" as inventory, others focus on "physical equipment"). He stressed the need for the IVY WG to explicitly define what it means by "inventory" to scope its work effectively and avoid future confusion.
  • Italo suggested that configuring "intended inventory" (use case 6) might still be within scope, but for others like ASON switch (use case 3), the boundary is blurred.
  • Tony Lee framed his power management proposal (use case 5) as "Hardware Management" and suggested the WG consider abstracting to solve these broader hardware management problems.
  • The discussion also touched upon the relationship between device models (Tony's focus) and network models (Cha's focus), with a suggestion that device-specific configurations might augment RFC 8348 rather than the network inventory model directly.
  • There was a strong sense that defining "inventory" is a top priority before adding more features to the core model.
  • It was reiterated that discussions should primarily occur on the mailing list.

Decisions and Action Items

• Decision: The IVY Working Group requires a clear, explicit definition of "inventory" to properly scope its work, especially concerning read/write configuration capabilities and to delineate between network-level and device-level concerns.
• Action Item: Nigel volunteered to initiate a mailing list discussion to propose starting thoughts on the definition of "inventory" for the IVY WG.
• Action Item: Authors and contributors of the Network Inventory Core Model draft are encouraged to prioritize and resolve outstanding issues via the mailing list or weekly design team calls to stabilize the draft as soon as possible.

Next Steps

• The immediate focus for the working group is to establish a clear definition of "inventory" through discussions on the mailing list, led by Nigel. This definition is considered a higher priority than adding new features to the core model until clarity is achieved.
• Continue active participation in weekly design team calls and mailing list discussions to address open issues within the Network Inventory Core Model draft.