Minutes interim-2021-lpwan-08: Tue 16:00
minutes-interim-2021-lpwan-08-202105181600-00

Meeting Minutes IPv6 over Low Power Wide-Area Networks (lpwan) WG
Date and time 2021-05-18 14:00
Title Minutes interim-2021-lpwan-08: Tue 16:00
State Active
Other versions markdown
Last updated 2021-05-18

minutes-interim-2021-lpwan-08-202105181600-00

Meeting Information

Data / Time

Join by meeting number

  • Meeting number (access code): 186 222 6870
  • Meeting password: gZrRTwNE457 (49778963 from phones)

Tap to join from a mobile device (attendees only)

  • +1-408-525-6800,,1862226870#49778963# Call-in toll number (US/Canada)
  • Some mobile devices may ask attendees to enter a numeric password.

Join by phone

Join by video system, application or Skype for business

Agenda

[16:05] Administrivia [15min]

  • Note-Well, Scribes, Agenda Bashing
  • WG Status, IETF 111

[16:20] Data Model for SCHC [15min]

  • Yang Doctors feedback

[16:35] AOB [ QS ]

Attendees / Blue Sheets

  • Carsten Bormann, TZI
  • Pascal Thubert, Cisco
  • Laurent Toutain, IMT Atlantique
  • Dominique Barthel, Orange
  • Ana Minaburo, Acklio

Attendees at some previous meeting for CC:

  • Carsten Bormann, TZI
  • Éric Vyncke, Cisco
  • Pascal Thubert, Cisco
  • Alexander Pelov, Acklio
  • Laurent Toutain, IMT Atlantique
  • Julien Catalano, Kerlink
  • Carles Gomez, Universitat Politecnica de Catalunya
  • Sergio Aguilar
  • Vincent Audebert, EDF
  • Olivier Gimenez, Semtech
  • Juan Carlos Zúñiga, Sigfox
  • Diego Dujovne, UDP
  • Georgios Papadopoulos, IMT Atlantique
  • Dominique Barthel, Orange
  • Ana Minaburo, Acklio
  • Edgar Ramos, Ericsson
  • Paul Duffy, Cisco
  • Ivaylo Petrov, Acklio
  • Arunprabhu Kandasamy, Acklio
  • Sean Turner, sn3rd
  • J Lecoeuvre
  • David Millman
  • Ricardo Andreasen
  • Arthur Oval

To Dos

  • Pascal to call for adoption of LPWAN architecture framework doc

Minutes

[16:05] Administrivia [15min]

  • Note-Well, Scribes, Agenda Bashing

RFC9011 published
static-coap nearing exit of RFC Editor queue

  • WG Status, IETF 111
    Probably not meeting at IETF111

[16:20] Data Model for SCHC [15min]

  • Yang Doctors feedback

  • multiple instances of SCHC

  • Pascal: operate independantly. How do we structure the data model?
  • Carsten: if crypto instances in the middle
  • Carsten: had the issue with ROHC, a few RFCs to describe that
  • see RFC5856, 5857, 5858. Extended IKEv2 to be able to negotiate RoHC
  • Pascal, Ana: need to know wich layers are compressed.
  • Pascal: actual endpoint may happen be designated through uri, which you don't know until you have decompressed CoAP.
  • Carsten: when OSCORE is setup, could negociate that content has to go through SCHC as well
  • Pascal: and which RuleSet
  • Carsten: yes, could be part of security context
  • Carsten: again, like RFC 5856, extend security context to negotiate SCHC
  • Carsten: whatever sets up the OSCORE security should set up the SCHC RuleSet as well
  • Pascal: look at the PPP draft for an example of TLV to signal the Rules. Could also have a hash of the RuleSet.
  • Carsten: hash makes sure rules came correctly in the right place. Need an architecture to describe how the rules get there.
  • Pascal: device could issue hash and uri, and core would fetch that.
  • Carsten: see RFC 6920
  • Carsten: see core discussion https://mailarchive.ietf.org/arch/msg/core/YODoXp7vEKl5tDMtem-343Tc6Nk
  • Ana: what goes in a feature; Carles wants to add a feature to say IPv6 only vs IPv4 + TCP, etc.... We think it is already done by looking at the rules
  • Carsten : there was a syntax error the fix should be simple
  • Ana: answer was a lot of input but we did not get to discuss the details. We need more discussion about the features on the data model, to identify Comp vs Fragmentation or something more detailed about which layer is been compressed, or fragmented.

[16:35] AOB [ QS ]