Data / Time

• Date: February 22th, 2022
• Time: 7-8am US Pacific PST, 4pm CET

Meeting Information

• Agenda: on datatracker

• Meeting material: on datatracker

• Meeting link: Meetecho Link

• Live Minutes: CODIMD Link

To Do's

• Alexander: Check adoption of OAM draft else call for it

• Alexander: Change pub date or OAM for end of 2022

• Pascal: Shepherd review

• Dominique: Recheck if Laurent's changes in data model addresse the issues

• Dominique: Publish the OAM doc that is elapsed

• Laurent: Republish the data model so we can WGLC before IETF 113

• Laurent: Suggest a hackathon for IETF 113

Interim Agenda

[16:05] Administrivia [15min]

• Note-Well, Scribes, Agenda Bashing
• WG Status
• IETF agenda and presence

Pascal presenting the usual introduction, NoteWell, IPR, all usual. This is an IETF official meeting, all IETF rules apply.

Pascal done a review of the compound ack

Alexander: OAM document was not adopted before, but Dominique has issues can publish it to make the adoption

Pascal: How about Yang model last call,

Laurent: has made the changes but needs to finish the last modifications before last week

Pascal: If we want to have the lastcall we need to have the last version ready before the cutoff

Pascal ask to Laurent to have an Hackathon session for next meeting

Chairs to call for adoption of the document.

IETF meeting slot will be 1h
Chairs will not be there, but Laurent will be with Eric on front desk

[16:20] NB-IOT [15min]

• Presenter: Ana Minaburo

Ana presents the changes in version 7. Removed DTN problem, to be published separately.
Ready forlast call

Carles: todo a review by IETF 113 session

Chairs to assess whether ready for WGLC at IETF 113

[16:35] "Dev and App for SCHC HC over 802.15.4" [15min]

• Presenter: Carles Gomez Montenegro

Carles: trigger discussion for using the HC piece of SCHC over IEEE 802.15.4

Carles: Dev and App as used in rfc8724 - which gives the uplink and downlink (Dev->App) or (App->Dev)

Carles: How does that map to 802.15.4 Mesh networks?

In an peer to peer IOT netwpork there's not really an app and a dev.

Ana: depends who's sending, basically the sender could be the dev. So you have a Rule for Uplink and another for Downlink

Laurent: this impacts the data model document which clearly echoes the terminology of dev and app

Pascal: this means taht we need a special signaling in P2P case to agree who plays the dev and who plays the app

Alexander: can be a bit to mark Uplink (bit=1) or Downlink (bit=0), which gives how to be

Laurent: depends also on the space of rules - is it shared among all devices or is it specific between two devices?

Pascal: probably we need to consider all devices having the same set of rules

Alexander: having two nodes sharing a set of rules is equivallent to the peer-to-peer scenario, which we already can handle. having all nodes in the mesh (or at least more than 2), then we may need something new

[16:50] Data Model Progress [05min]

Laurent: nothing we haven't discussed previously

[16:55] AOB [ QS ]

Interim Minutes

[16:05] Administrivia [15min]

• Note-Well, Scribes, Agenda Bashing
• WG Status
• IETF agenda and presence

[16:20] NB-IOT [15min]

• Presenter: Ana Minaburo

[16:35] "Dev and App for SCHC HC over 802.15.4" [15min]

• Presenter: Carles Gomez Montenegro

[16:50] Data Model Progress [05min]

[16:55] AOB [ QS ]