I think that options 1 and 2 are closer than we think and can be aligned
if we can agree on getting rid of the network-hardware-inventory
container object that is defined in draft-ietf-ccamp-network-inventory.
This will allow us to move forward quickly with a model for network
hardware inventory, as required by ccamp, while preserving the option
for a model that can be generalized and extended to incorporate other
types of inventory, as desired by ivy. I'll describe a bit more details
in a separate email in order to not distract from the poll.
I guess this makes me a proponent of option 3, but with the caveat that
this would not need to restart from scratch. Instead it can be derived
in very straighforward manner from the existing models with these slight
alignments as described. I am also sure that a lot of the existing text
can be salvaged.
--- Alex
On 8/27/2023 11:21 PM, maqiufang (A) wrote:
Hi Working Group,
It’s now time to start considering how to move forward with the
inventory base model. We have two different documents that could be
used as a starting point for our work or, in case the working group
believes none of them is “good enough”, we can start a brand new ID.
In case the latter option is chosen, Daniele and I will write a -00
version including just the table of content and what we’d like to be
covered in each section. The document will then be handed over to a
pool of authors which will bring it till the WG adoption.
Hence, we will have a 3 weeks polling starting today. We decided to
make it a bit longer than usual because this time the working group is
requested to review two drafts instead of one.
This mail starts a 3 weeks polling, terminating on September 15^th ,
where we would like the working group to express your preference among:
1. Adopt draft-ietf-ccamp-network-inventory-yang-02 in IVY and evolve
it to become the network inventory base model
2. Adopt draft-wzwb-opsawg-network-inventory-management-03 in IVY and
evolve it to become the network inventory base model
3. Start a brand new document from scratch as described above
In the week after the closure of the polling (between September 18 and
25) we will have an IVY interim meeting to discuss the issues/concerns
raised during the polling ( A separate mail will be sent).
Thank you,
Qiufang and Daniele
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
