[08:25:17] anssi.turkulainen joins the room [08:26:09] anssi.turkulainen leaves the room [09:32:38] dlpartain joins the room [09:33:14] dlpartain has set the subject to: IETF75 NETMOD Session 2, July 2 1300 - 1500 [09:33:40] dlpartain has set the subject to: IETF75 NETMOD Session 2, July 29 1300 - 1500 [09:33:56] dlpartain leaves the room [10:52:44] lhotka joins the room [10:54:05] lhotka leaves the room [10:56:51] David Reid joins the room [10:59:53] arneos joins the room [11:00:16] balazs.lengyel joins the room [11:00:29] mbj joins the room [11:01:31] Is the audio ok? [11:01:31] Audio is fine [11:02:04] lhotka joins the room [11:02:05] Mark Ellison joins the room [11:02:10] arneos, who are you? Please tell us, we need it for the notes. [11:02:26] audio is good here [11:02:35] Arne Oslebo [11:03:02] Thanks [11:03:35] ersue joins the room [11:03:47] Juergen Schoenwaelder joins the room [11:05:57] slide 7 [11:06:11] NETMOD Agenda [11:06:25] andy.bierman joins the room [11:06:43] Hi everybody! [11:07:03] I'm going to guide you today through the jabber session. [11:07:17] david.kessens joins the room [11:07:20] If you have comment you want to be read in the session room: please wite "READ: " as prefix before your comment. [11:07:48] I will read the comments which have the prefix "READ: " in the session room. [11:08:13] Hi remotes; today the meeting is relatively small - I counted about 22 people in the room. [11:08:47] Now we go to "Issue resolution day 2" [11:09:16] slide 2 - issue 1 xpath warnings [11:12:30] agree with proposal [11:13:02] I agree [11:13:31] slide 3 [11:13:37] Issue 2 [11:13:43] mbj leaves the room: Replaced by new connection [11:14:46] good; makes it easier to compare leafs from the agent [11:14:55] mbj joins the room [11:15:01] ray joins the room [11:15:20] balazs.lengyel leaves the room [11:18:09] test [11:18:57] slide 4 [11:19:17] Issue 3 - Types document: inclusion of 'date' type [11:19:38] READ: if operators always know in which timezone a device resides then a 'location' or 'time offset' is not necessary. Otherwise, it would be good to have the device let the operator know what the device location (time zone) is. [11:20:54] Bert Wijnen joins the room [11:21:00] sorry for time lag [11:21:10] no worries [11:21:32] ok [11:22:04] slide 5 [11:22:12] Issue 4 – Include prefix in IANA registry [11:24:39] this does not help; it might fool people into thinking all prefixes are unique; but vendor prefixes will never be unique for sure [11:25:35] going to read [11:28:01] with mandatory prefixes, do I have to use this prefix in all imports? what about those prefixes? [11:28:33] please write "READ: " as a prefix to be explicite it should be read. [11:29:43] Atarashi Yoshifumi joins the room [11:31:35] do not agree with this proposal [11:33:14] READ: this will effectively crunch readable module names into unreadable prefixes. Use the module name as the prefix in docs if it matters [11:35:21] lada is right! this sounds good when the module count is < 5; how about 300? [11:37:13] mbj leaves the room: Replaced by new connection [11:38:47] do not care - don't think it is needed [11:39:32] mbj joins the room [11:40:44] what if vendors publish prefixes that the IANA later adds to the registry? (do not read) [11:40:57] Linus Nordberg joins the room [11:44:56] yes [11:45:50] yes - Martin's interpretation [11:47:05] OK - I can leave this out, if adding enums is considered better [11:48:39] guidelines document - last slide [11:48:49] open issues [11:50:26] anssi joins the room [11:51:13] I-D name is OK [11:54:38] OK to not add any CLR on this [11:56:01] david.kessens leaves the room [11:56:23] mandatory means the manager MUST provide the value (ask Phil) [11:58:20] That is not my understanding of the mandatory-stmt [11:59:43] Otherwise, why is default-stmt not allowed with mandatory-stmt? [12:02:35] anssi leaves the room [12:03:57] read: the Q: Is the agent allowed to supply a value for a mandatory leaf? [12:04:26] david.kessens joins the room [12:05:16] that's not what I asked -- I know it MUST exist. Is the agent allowed to create it? [12:05:54] maxired joins the room [12:08:24] OK -- I can remove preceding-sibling, but say order may not be stable [12:09:24] thank you Andy. [12:11:55] maxired leaves the room [12:14:13] Translation of SMIv2 MIB Modules to YANG Modules [12:14:18] Slide 6 [12:15:45] slide 7 [12:16:11] 8 [12:17:33] 9 [12:21:03] good stuff: the high level issue is how new YANG modules will be added; will the SMIv2 structure be used as the framework, and read-only changed to read-write, or new config added to existing monitoring, or something else? [12:25:01] how would the translation be used in IETF standards? vs. how will the translated modules be used in IETF standards? [12:34:01] this is important work because we need algorithmic (instant) access to all SMIv2 models for monitoring and maybe config [12:36:00] READ: I support this work and will post some comments to the list rather than trying to type on jabber [12:56:51] Atarashi Yoshifumi leaves the room [12:57:57] Session ends [12:58:01] ersue leaves the room [12:58:06] mbj leaves the room [12:58:06] andy.bierman leaves the room [12:58:28] David Reid leaves the room [12:58:32] lhotka leaves the room [12:58:42] arneos leaves the room [12:58:44] Mark Ellison leaves the room [13:02:01] Bert Wijnen leaves the room [13:02:36] Linus Nordberg leaves the room [13:03:48] david.kessens leaves the room [13:06:07] Juergen Schoenwaelder leaves the room: Disconnected [13:08:41] Linus Nordberg joins the room [13:08:48] Linus Nordberg leaves the room [13:16:06] ray leaves the room [13:48:53] Juergen Schoenwaelder joins the room [14:33:31] Atarashi Yoshifumi joins the room [15:14:34] Atarashi Yoshifumi leaves the room [17:13:26] Juergen Schoenwaelder leaves the room