Minutes interim-2022-lpwan-01: Tue 16:00
minutes-interim-2022-lpwan-01-202201041600-01
Meeting Minutes | IPv6 over Low Power Wide-Area Networks (lpwan) WG | |
---|---|---|
Date and time | 2022-01-04 15:00 | |
Title | Minutes interim-2022-lpwan-01: Tue 16:00 | |
State | Active | |
Other versions | markdown | |
Last updated | 2022-01-04 |
Meeting Information
Data / Time
- Date: January 4th, 2022
- Time: 7-8am US Pacific PST, 4pm CET
Meeting Information
- Date: January 4th, 2022
-
Agenda: on datatracker
-
Meeting material: on datatracker
-
Meeting link: Meetecho Link
-
Live Minutes: CODIMD Link
Interim Agenda
[16:05] Administrivia [05min]
- Note-Well, Scribes, Agenda Bashing
- WG Status
[16:10] Compound Ack publication steps [25min]
- data Model
- Dominique's review
- Shepherd selection
- IPR
[16:35] Yang Data Model WGLC steps [20min]
- Dominique's review
- Timing
[16:55] AOB [ QS ]
Minutes
[16:05] Administrivia [05min]
- 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]
- 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]
- Dominique's review
- Timing
TODO Dominique + Laurent: list parameters that need to be known on both
sides like the lifetime of dtag