# Meeting Information {#meeting-information} ## Data / Time {#data--time} * Date: January 4th, 2022 * Time: [7-8am US Pacific PST, 4pm CET][1] ## Meeting Information {#meeting-information-1} * Date: January 4th, 2022 * Time: [7-8am US Pacific PST, 4pm CET][1] * Agenda: [on datatracker][2] * Meeting material: [on datatracker][3] * Meeting link: [Meetecho Link][4] * Live Minutes: [CODIMD Link][5] ## Interim Agenda {#interim-agenda} ## \[16:05\] Administrivia \[05min\] {#1605-administrivia----------------------------05min} * Note-Well, Scribes, Agenda Bashing * WG Status ## \[16:10\] Compound Ack publication steps \[25min\] {#1610-compound-ack-publication-steps-----------25min} * data Model * Dominique's review * Shepherd selection * IPR ## \[16:35\] Yang Data Model WGLC steps \[20min\] {#1635-yang-data-model-wglc-steps---------------20min} * Dominique's review * Timing ## \[16:55\] AOB \[ QS \] {#1655-aob---------------------------------------qs-} ## Minutes {#minutes} ## \[16:05\] Administrivia \[05min\] {#1605-administrivia----------------------------05min-1} * Note-Well, Scribes, Agenda Bashing Alexander does the usual agenda bashing Pascal: Dominique, what is the intention with the OAM document? Dominique: OAM is still on the agenda. Probably need to review the release date. December 2022. * WG Status ## \[16:10\] Compound Ack publication steps \[25min\] {#1610-compound-ack-publication-steps-----------25min-1} * data Model * Dominique's review * Shepherd selection * IPR Laurent: question about the bitmap compression - we should probably include it in the YANG model? Sergio: only the last bitmap in the set of bitmaps in one compound ack is compressed Laurent: there no need to add something to disable bitmap compression, so the data model is OK. We need the full consistency of the data model in section three and the parameters in section 4. Alexander: there is a description of the parameter "compress last bitmap", which is optional. Either include it in the YANG Data Model of the draft, or remove the "optional" part. Dominique: Question about the extension / update of RFC8742. Pascal: if you want to do an extension or update, you need to specify it. There are some XML tags for both. Eric: The only meta language tag that is currently understood is "update". Pascal: add section 3.2.3 "extending RFC 8724" with the diff OLD/NEW The text in 3.2 needs to say specifically when it is an update or an extension instead of "besides" Dominique: A second expectation about the review was to provide Editorial instructions on how to apply the changes to RFC8724, e.g. Insert the following paragraph in RFC8724 at line XX. Eventually, also instructions if there are paragraphs to remove. TODO: chairs to call for a shepherd ## \[16:35\] Yang Data Model WGLC steps \[20min\] {#1635-yang-data-model-wglc-steps---------------20min-1} * Dominique's review * Timing TODO Dominique + Laurent: list parameters that need to be known on both sides like the lifetime of dtag ## \[16:55\] AOB \[ QS \] {#1655-aob---------------------------------------qs--1} [1]: https://www.worldtimebuddy.com/?qm=1&lid=100,12,5392171,1850147&h=100&date=2022-01-04&sln=15-16 [2]: https://datatracker.ietf.org/doc/agenda-interim-2022-lpwan-01-lpwan-01/ [3]: https://datatracker.ietf.org/meeting/interim-2022-lpwan-01/session/lpwan [4]: https://meetings.conf.meetecho.com/interim/?short=5650da9f-cc71-441f-ade5-99a15554f47b [5]: https://notes.ietf.org/notes-ietf-interim-2022-lpwan-01-lpwan#