Interim #2 2023

Data / Time

• Date: January 17st, 2023
• Time: 7-8am US Pacific PST, 4pm CET

Meeting Information

• Agenda: on datatracker
• Meeting material: on datatracker
• Meeting link: Meetecho
• Live Minutes: CODIMD Link
• ical: ICS

Interim Agenda

[16:00] Administrivia [10min]

• Note-Well, Scribes, Agenda Bashing
• WG Status
• Slides

[16:10] Rechartering [20 min]

• Presenter: Pascal Thubert
• Topics: Review proposed work item

[16:30] SCHC Data Model (new work for tools compatibility) [10 min]

• Presenter: Laurent Toutain
• Associated draft: draft-ietf-lpwan-schc-yang-data-model
  Associated draft: draft-ietf-lpwan-schc-yang-data-model
  (RFC-EDITOR)

Slides

[16:40] A proposal to manage access control on the rule [10 min]

• Presenter: Laurent Toutain

[16:50] Architecture Next Steps [10 min]

• Presenter: Chairs, Ana Minaburo
• Associated draft: draft-ietf-lpwan-architecture
• Topics: Ivan’s comments

Associated draft: draft-ietf-lpwan-architecture (expired)

[16:xx] AOB [ QS ]

Interim Minutes

[16:00] Administrivia [10min]

• Note-Well, Scribes, Agenda Bashing
• WG Status
• YANG: Editorial modifications can be made at AUTH48 stage
• NB-Iot: Any input from RFC EDITOR
• Compound: IDNits

• SigFox: Reference to be added to the text at Roman D's request, then
  Eric V will approve

• change in Yang data model, although in RFC Editor status?

• Eric: until in Auth48, can still do editorial changes or minor
  technical changes
• Pascal: such changes will be implemented during the Auth48 editing
• CompoundAck:
• Alex: Sergio did not answer to what ??
• Rechartering items:
• Edgar: other places where SCHC cnan be used: low-energy devices for
  6G. Delay-tolerant transmissions. Zero-Energy or Energy-harvesting
  devices.
• Edgar: short bursty transmission
• Pascal: what would we deliver? Anything specific for us.
• Edgar: Configuration of the IP address, configuration on special
  changes for the timers, how to configure such long periods of time.
• Pascal, this is managment, not SCHC?
• Edgar: yes, more about adjustment of these parameters.
• Pascal: a profile for energy scavenging devices.
• Laurent: I think is very important, is not only adapting compression
  but also fragmentation. Clearly state that SCHC over foo covers both
  compression and fragmentation
• Alex: the delay aspect, is something that we need to look a bit more
  closer, whats happends if we have a very big packet, maybe new SCHC
  profile?, I'm not sure if that needs re-chartering but it is indeed
  important.
• Alex: decide if already covered by current charter items or need
  some specific.
• Pascal: from chat: "The group will extend its scope to enable the
  benefits of the SCHC technology over non-LPWA networks and even
  stricter low Power devices line zero-energy / scavenging devices
  that may operate in Delay Tolerant Mode"
• Pascal: this sentence is supposed to replace the first sentence of
  the charter text.

[16:26] Rechartering [20 min]

• Presenter: Pascal Thubert
• Topics: Review proposed work item
• Laurent: we should not be referring to the previous charter. Just
  write the content in the new charter.
• Pascal: unfortnate page break in the slides. There is a list
  following immediately.
• Pascal: not committing on doing work on each technology listed here.
  Yet we need to provide examples.
• Alex: does like the examples
• Ana: will we be able to work on a technology not listed?
• Pascal: can't be open bar. Need a least an indication, but
  "IPCMPv6-based protocols" is very wide.
• Carsten: these work items should in a list of milestones, not in the
  charter proper.
• Carsten: exception is statement of collaboration with other
  organisations, which need to stay in the charter.
• Pascal: any other item people would want on the list?
• Alex: personally, nothing to add.
• (no other items proposed during the call)

[16:40] SCHC Data Model (new work for tools compatibility) [10 min]

• Presenter: Laurent Toutain
• Associated draft: draft-ietf-lpwan-schc-yang-data-model

• Laurent: I work on openSCHC and I found some little details to be
  changed in the new version:

  • type definition, need put the union on the compression structure
    in order to get it work with validation tools XML -- JSON
  • Made a new model to take this into consideration, the change is
    just a few lines to move the union from typedef
  • I also included a CoAP option from the discussion with Quentin
    'fit-coap-option', this has no impact on what we have before

• Laurent: Any comments ?

• Quentin: Addition of the "raw", "on the wire" fields, is there any
  interest on addressing these fields as well?
• Laurent: for this version is too late. Not changing field
  representation, only the model.
• Laurent, there is a video I put on the lsit to present how the model
  works

• [16:48] A proposal to manage access control on the rule [10 min]

• Presenter: Laurent Toutain

• Laurent: I have some ideas but I want to discuss before writing a
  draft.
• Laurent: Now all the fields are rw, the idea is to give permission
  not to a colon but to an specific line. We just need to add an extra
  entry, it can be done modularly.
• Laurent: who has these restricted access??, is easy for comrpession
  but I'm not sure how this can be done in fragmentation?, maybe the
  timers?, number of fragments? -- flow control?.
• Laurent: Any comments?
• Eric: So this will be a new draft.
• Leurent: yes
• Carsten: I have hard time imagining that there is a need for
  individual access to rules. This should be a "wholesale" approach.
• Laurent: this can be for example oneM2M
• Alex: What can be the possible use-cases, we need to identify one or
  two to go ahead
• Pascal: What happends with very similar rules?, can this become an
  attack vector?
• Alex: We need a document listing the possible attack vectors, and
  the we can work on that
• Quentin: This is related to the definition of context
• Laurent: There might be two kind of attacks, core vs device and
  viceversa.
• Pascal: go to the mailing list, talk about use-cases.
• Laurent: where is the arch document?
• Pascal: Normally anything is on the github
• Pascal: Meeting adjourned, thanks to the note takers

[17:02] meeting adjourned