[{"author": "Kent Watsen", "text": "

https://notes.ietf.org/notes-ietf-119-netmod?both

", "time": "2024-03-21T03:03:04Z"}, {"author": "Scott Mansfield", "text": "

https://datatracker.ietf.org/liaison/1890/

", "time": "2024-03-21T03:07:36Z"}, {"author": "Lou Berger", "text": "

forgot to mention Jason, our secretary, was very helpful preparing for the session -- thank you Jason

", "time": "2024-03-21T03:17:48Z"}, {"author": "Mahesh Jethanandani", "text": "

I would agree with Lou on that we should agree on how the filename changes and not duck the issue.

", "time": "2024-03-21T03:25:53Z"}, {"author": "Andy Bierman", "text": "

revision-label in filename is NBC change to YANG 1.1 so needs to wait for YANG-next

", "time": "2024-03-21T03:31:06Z"}, {"author": "Robert Wilton", "text": "

Hi Andy, I guess you mean an NBC change on tooling. We wouldn't be taking away the old revision date scheme so that would still work.

", "time": "2024-03-21T03:33:47Z"}, {"author": "Italo Busi", "text": "

I think that as soon as revision labels are going to be used, there will be the need to deliver different versions of the same YANG model in one day. This could not be done because the revision-date MUST still be unique in YANG 1.1. I therefore prefer to complete this work and to start YANG-next quickly rather than fixing a naming issue

", "time": "2024-03-21T03:34:20Z"}, {"author": "Robert Wilton", "text": "

Just a reminder that more note takers would be helpful please : https://notes.ietf.org/notes-ietf-119-netmod?both

", "time": "2024-03-21T03:34:31Z"}, {"author": "Lou Berger", "text": "

not sure the room mic is working

", "time": "2024-03-21T03:45:07Z"}, {"author": "Mahesh Jethanandani", "text": "

Are you not able to hear the room?

", "time": "2024-03-21T03:49:50Z"}, {"author": "Jan Lindblad", "text": "

it wasn't easy to hear james talking recently, but that was probably due to misalignment between speaker and mic height

", "time": "2024-03-21T03:50:34Z"}, {"author": "Lou Berger", "text": "

possibly, was hard to tell

", "time": "2024-03-21T03:51:12Z"}, {"author": "Mahesh Jethanandani", "text": "

How about hearing what Joe is saying? Is he clear?

", "time": "2024-03-21T03:54:38Z"}, {"author": "Jan Lindblad", "text": "

loud and clear

", "time": "2024-03-21T03:54:49Z"}, {"author": "Lou Berger", "text": "

sounds fine to me

", "time": "2024-03-21T03:56:05Z"}, {"author": "Lou Berger", "text": "

@meetecho remote mic is low in room

", "time": "2024-03-21T03:56:19Z"}, {"author": "Mahesh Jethanandani", "text": "

I think what Maria is saying is that why we are using string in the version field (for the semver portion of the field)?

", "time": "2024-03-21T03:58:00Z"}, {"author": "Lorenzo Miniero", "text": "

Ack, just a sec

", "time": "2024-03-21T03:58:11Z"}, {"author": "Lou Berger", "text": "

@lorenzo, think we're okay now

", "time": "2024-03-21T03:58:30Z"}, {"author": "Lou Berger", "text": "

@kent, please confirm

", "time": "2024-03-21T03:58:39Z"}, {"author": "Maria Mat\u011bjka", "text": "

yes, the question is, if the string is actually \"major.minor.patch_whatever\", then why this isn't like

\n

grouping semver {
\nuint32 major;
\nuint32 minor;
\nuint32 patch;
\nstring whatever;
\n}

", "time": "2024-03-21T03:59:26Z"}, {"author": "Maria Mat\u011bjka", "text": "

(i know that this is applying another layer language but hopefully you get this)

", "time": "2024-03-21T04:00:15Z"}, {"author": "Alex Huang Feng", "text": "

Also, I believe for CBOR is the same, the namespace is present in the data, so same applies to this encoding

", "time": "2024-03-21T04:05:02Z"}, {"author": "Kent Watsen", "text": "

we're fine, room-speakers just need speak louder

", "time": "2024-03-21T04:08:55Z"}, {"author": "Jan Lindblad", "text": "

Thomas, thank you for the feedback. I'm certainly very interested to align with your work.

", "time": "2024-03-21T04:18:37Z"}, {"author": "Lou Berger", "text": "

so 'schema-include' vs 'schema-mount'

", "time": "2024-03-21T04:22:42Z"}, {"author": "Mahesh Jethanandani", "text": "

@Jan, not to put you on the spot, but doesn't tail-f have a solution that kind of solves the problem that Jean is talking about? How does it align with what Jean is proposing.

", "time": "2024-03-21T04:28:01Z"}, {"author": "Ahmed Elhassany", "text": "

@Alex thank you for clarification about cbor

", "time": "2024-03-21T04:28:51Z"}, {"author": "Jan Lindblad", "text": "

@Mahesh, the solution we have is more similar to schema-mount, where you don't know what YANG modules are mounted at design time. Recently, I have stumbled over the same/similar need for something like full-include, so I think this is interesting to discuss, even if I'm also a bit worried about the deeper implications of this addition.

", "time": "2024-03-21T04:42:19Z"}, {"author": "Lou Berger", "text": "

sounds like draft-wwx-netmod-event-yang

", "time": "2024-03-21T04:42:51Z"}, {"author": "Lou Berger", "text": "

https://datatracker.ietf.org/doc/html/draft-wwx-netmod-event-yang-10

", "time": "2024-03-21T04:44:24Z"}, {"author": "Jan Lindblad", "text": "

@Ed, maybe you could try asking YANG-doctors for help?

", "time": "2024-03-21T04:44:28Z"}, {"author": "Lou Berger", "text": "

@jan good idea

", "time": "2024-03-21T04:44:48Z"}, {"author": "Vishnu Beeram", "text": "

https://datatracker.ietf.org/doc/draft-liu-netmod-yang-schedule/ -- this is the old ietf-schedules draft that was discussed in the past..

", "time": "2024-03-21T04:52:46Z"}, {"author": "Mahesh Jethanandani", "text": "

For folks who were not in IVY or OPSAWG, Rob and I have discussed this, and believe that this work is distinct enough and has enough interest for a BOF. Therefore I am hoping the interested parties will come together to propose a plan for a BOF in IETF 120.

", "time": "2024-03-21T04:57:51Z"}, {"author": "Mahesh Jethanandani", "text": "

I am of course referring to the power management draft.

", "time": "2024-03-21T04:58:27Z"}]