[{"author": "Tony Li", "text": "

Audio is very choppy

", "time": "2023-09-20T14:08:52Z"}, {"author": "Oscar de Dios", "text": "

I hear bad

", "time": "2023-09-20T14:08:56Z"}, {"author": "Italo Busi", "text": "

Also on my side

", "time": "2023-09-20T14:09:07Z"}, {"author": "Carsten Bormann", "text": "

Audio is bad

", "time": "2023-09-20T14:09:10Z"}, {"author": "Alexander Clemm", "text": "

same here

", "time": "2023-09-20T14:09:12Z"}, {"author": "Italo Busi", "text": "

Also for me

", "time": "2023-09-20T14:09:23Z"}, {"author": "Dieter Beller", "text": "

no problem with Daniele's audio

", "time": "2023-09-20T14:09:40Z"}, {"author": "Daniele Ceccarelli", "text": "

I'll continue with the presentation. Qiufang please shout when you're back

", "time": "2023-09-20T14:10:01Z"}, {"author": "Tony Li", "text": "

Audio is getting bad again.

", "time": "2023-09-20T14:18:13Z"}, {"author": "Robert Wilton", "text": "

Note, in terms of combining larger numbers of authors, one pragmatic choice is to appoint a single editor and then list everyone else as contributors.

", "time": "2023-09-20T14:18:21Z"}, {"author": "Tony Li", "text": "

The mic is having a problem with plosives.

", "time": "2023-09-20T14:18:26Z"}, {"author": "Robert Wilton", "text": "

Can folks also try and help make meeting notes in https://notes.ietf.org/notes-ietf-interim-2023-ivy-01-ivy?both

", "time": "2023-09-20T14:22:56Z"}, {"author": "Robert Wilton", "text": "

I know that generally helps chairs get the minutes out more quickly because there is less work to do. It also ensures that any comments that you make are accurately captured.

", "time": "2023-09-20T14:23:31Z"}, {"author": "Carsten Bormann", "text": "

Is an inventory a list of <devices> or a list of <devices> with purpose-in-life (role) information tacked on?

", "time": "2023-09-20T14:27:40Z"}, {"author": "Carsten Bormann", "text": "

Do the mentions of \"software\" in any way relate to the active discussions about SBOM-related concepts in SCITT?

", "time": "2023-09-20T14:28:04Z"}, {"author": "Alexander Clemm", "text": "

I wouldn't call license inventory \"optional\". I would call it a related but separate concern, that can be handled separately / defined in a separate module, possibly augmenting (or not) a generic inventory module

", "time": "2023-09-20T14:29:16Z"}, {"author": "Alexander Clemm", "text": "

FWIW, I do think we need to be able to accommodate virtual inventory (if not initially, at least in the future), very much appreciate the fact that this draft is addressing this

", "time": "2023-09-20T14:34:05Z"}, {"author": "Alexander Clemm", "text": "

And I do agree with augmenting ietf-network-topology (rather than defining something unconnected)

", "time": "2023-09-20T14:37:00Z"}, {"author": "Alexander Clemm", "text": "

Is draft-xxx-ivy-network-inventory-yang a new draft?

", "time": "2023-09-20T14:39:51Z"}, {"author": "Bo Wu", "text": "

This is a proposal for the merged draft

", "time": "2023-09-20T14:42:24Z"}, {"author": "Robert Wilton", "text": "

Does hardware mean \"device\", i.e., would it cover virtual devices?

", "time": "2023-09-20T14:43:08Z"}, {"author": "Juan Cardona", "text": "

As an author of a draft that includes licenses (entitlements), I think licenses should be separated, be able to reference the core ivy HW and SW models, but not to be included in those core models.

", "time": "2023-09-20T14:44:04Z"}, {"author": "Adrian Farrel", "text": "

I agree with Juan. Given the complexity of licensing, it would be well to put it in another model in another document. The inventory can point to license as an optional extension, but we don't need the inventory work to be gated on completing the license work

", "time": "2023-09-20T14:46:45Z"}, {"author": "Robert Wilton", "text": "

I also think the licensing should be a separate module (for modularity reasons) and possibly shouldn't even augment into the topology, but may be better as a separate list with leafrefs into the inventory model.

", "time": "2023-09-20T14:50:01Z"}, {"author": "Robert Wilton", "text": "

It is worth noting that the OC components model allows for devices to be flexible on their physical structure, where you would normally logically list software components under the hardware components (or sub-components)

", "time": "2023-09-20T14:52:10Z"}, {"author": "Daniele Ceccarelli", "text": "

i like the split into 4 modules in 4 different documents as well

", "time": "2023-09-20T14:53:12Z"}, {"author": "Mohamed Boucadair", "text": "

5 I guess (with the topo correlation one)

", "time": "2023-09-20T14:53:46Z"}, {"author": "Daniele Ceccarelli", "text": "

yep

", "time": "2023-09-20T14:55:21Z"}, {"author": "Italo Busi", "text": "

if it helps reaching agreement, also six modules/drafts (splitting the base network-inventory and the hardware-network-inventory augmentation) can work as well

", "time": "2023-09-20T15:14:07Z"}, {"author": "Marisol", "text": "

Tony, I will reach out to you. We have augmented based on DMLMO proposal to report on power measurement (dynamicly)

", "time": "2023-09-20T15:16:43Z"}, {"author": "Alexander Clemm", "text": "

I am interested in the power work as well

", "time": "2023-09-20T15:22:41Z"}, {"author": "Adrian Farrel", "text": "

Care that your show of hands doesn't overrun the end of the meeting!

", "time": "2023-09-20T15:28:59Z"}, {"author": "Italo Busi", "text": "

thanks

", "time": "2023-09-20T15:33:18Z"}]