Skip to main content

Minutes interim-2020-lpwan-03: Wed 16:00
minutes-interim-2020-lpwan-03-202002051600-00

Meeting Minutes IPv6 over Low Power Wide-Area Networks (lpwan) WG
Title Minutes interim-2020-lpwan-03: Wed 16:00
State Active
Other versions plain text
Last updated 2020-02-06

minutes-interim-2020-lpwan-03-202002051600-00
Connection details
------------------
Date: 7-8am US Pacific, 4pm CET:
https://www.worldtimebuddy.com/?qm=1&lid=100,12,5392171,1850147&h=100&date=2020-02-05&sln=15-16
Meeting link:
https://cisco.webex.com/cisco/j.php?MTID=me91d56b37454056b8c5ef3b102b9da50
Meeting number: 201 266 501 Password: txCGJTrS (89245877 from phones)

Agenda
------
The general agenda for all meetings is as follows:
[16:05] Administrivia                                        [ 5min]
    o    Note-Well, Scribes, Agenda Bashing
    o    Status of drafts

[16:10] LoRaWAN IID (Olivier)                                [ 5min]
[16:15] Update on OpenSCHC                                   [10min]
[16:25] Plans for interop testing at IETF107 hackathon       [ 5min]
[16:30] OAM draft update                                     [10min]
[16:40] RFC-to-be 8724 update: work in progress (AUTH48)     [10min]
[16:50] SCHC Tutorial at IETF107                             [ 5min]
[16:55] AOB                                                  [ 5min]

TODO: Pacal Add COSE to the tech overlap section in the meeting request IETF
107. Also other conflicts, see notes below. DB: Ask EDU team for a tutorial slot

Minutes takers
-------------------
Ana Minaburo
Pascal Thubert
Arunprabhu Kandasamy
Laurent
Dominique
Olivier

Attendees
-------------
- Ana Minaburo
- Arunprabhu Kandasamy
- Laurent Toutain
- Carles Gomez
- Julien Catalano
- Pascal Thubert
- Dominique Barthel
- Olivier Gimenez
- Ivaylo Petrov
- Alexander Pelov
- Diego Dujovne
- Juan Carlos Zuniga

Past Attendees
-------------
- Ana Minaburo
 - Laurent Toutain
 - Carles Gomez
 - Julien Catalano
- Pascal Thubert
 - Dominique Barthel
 - Olivier Gimenez
 - Ivaylo Petrov
  - Alexander Pelov
 - Vincent Audebert
 - Juan Carlos Zuniga
 - Arunprabhu Kandasamy
 - Diego Dujovne

Meeting minutes
------
The general agenda for all meetings is as follows:
[16:05] Administrivia                                        [ 5min]
    o    Note-Well, Scribes, Agenda Bashing
    o    Status of drafts

* Pascal: Gives the Note-Well, minutes are taken and it will not be recorded
* Pascal: ToDo Change the Edit to AUTH48 for RFC8724,  look for the conflicts
it is very important * Pascal: IETF 107  slot requested (1.5 hour) * Ivo: I
will need to be in COSE, so that might be a conflict that needs to be avoided.
* Dominique suggests to add 6TiSCH as a technology conflict

[16:11] LoRaWAN IID (Olivier)                                [ 5min]
  * See email sent to the list last week with a new proposal whereby the SCHC
  GW creates the IDs * new proposal, looks like NAT at the SCHC GW. * Laurent
  had proposed similar stuff before. But if address is needed at application
  layer (which is bad), run in trouble. * Pascal: Skype and FTP are examples. *
  Pascal: if you go this path, provide a way for the device to learn its
  address. * Julien: why not put address within Rule? * Pascal: does not work
  because ... * Pascal: how do you change IP address? You ned a provisioning
  system, or some protocol to convey the IP address to the device. * Pascal:
  like the idea that address is computed once and pushed to the device. *
  Oliver: shall this be part of SCHC or above it? * Pascal: part of the
  provisioning. Above SCHC. * Olivier: in Profile? * Pascal: write in Profile
  that address needs to be provisioned into the device. * Alex: given the
  probabilities, beleive that it's good enough to say device generates own
  address, and if collision detected, device must rejoin. * Pascal: also works
  for me. * Pascal: could we do this for link-local and NAT at SCHC GW, or
  provision global into device? * Alex: personal preference (chair hat off) to
  simpler solution. Leave as it is. Don't try to engineer the full solution.
  Will work on this later. * Pascal: fear that IDs end up being different at
  device and GW, if alternative computation methods are published later. *
  Laurent: like the simple proposal: if IID collision, block device until it
  rejons. * Pascal: how do you know that in the future, you won't want multiple
  addresses? * Laurent: we are targetting very simple devices. * Pascal: like
  the new proposal (NAT-like) as long as way to communicate its address to the
  device. * Alex: time's running. Enough info at this meeting? Otherwise, go to
  ML. * Olivier: will summarize this discussion on the ML.

[16:15] Update on OpenSCHC     (Laurent)                              [10min]
  * focus now more on easy access for third parties (academia, etc..), less on
  embedded code. * New version published last way with a new rule manager,
  compression rule direction * Merged Ack-on-Error code from student Sergio at
  IMT Atlantique * Steering meeting every two weeks, Etherpad:
  https://etherpad.tools.ietf.org/p/openschc?useMonospaceFont=true * These
  meetings are about implementation, not about the protocol.

[16:25] Plans for interop testing at IETF107 hackathon (Laurent)      [ 5min]
* Provide a set of rules that each implementer can parse
* Provide compressed packets in a file to test interrop
* Eventually do compression interrop in real time and No-Ack fragmentation
* 4 implementations: Acklio, libSCHC, openSCHC and Chile's implementation
* JCZ: Chile's implementation will be local, but working on their fragmentation.

[16:36] OAM draft update     (Dominique)                                [10min]
 * Presented slides, no questions

[16:40] RFC-to-be 8724 update: work in progress (AUTH48) (Dominique)     [10min]
* The Editor sent their comments about the edition of the work, with 15
questions to be answered * CG: IEEE paper trick is to use acronym like: Static
Context Header Compression and fragmentation (SCHC) * Proposition: Static
Context Header Compression and fragmentation (SCHC) Framework for Low-Power
Wide Area Network (LPWANs) and its application to UDP/IPv6 * Use SCHC as a
name, no longer an acronym? * Alexander: SCHC could be a name if it is widely
used, which is the case only in our "IETF-LPWAN" community, so it is still an
acronym. * Alexander: Chair hat off - See added value to keep it as acronym.
Makes it easier to remember the letters and their order. * Alex: does not like
SCHC to mean Static Context Header Compression and fragmentation, have to
explain why F does not show in the acronym * JCZ: ask the RFC Editor if they
would accept SCHC as a name, not expanded in the title. * JCZ: like the more
explicit title ("After" proposal, in the slide). * Julien: static context is
very important, needs to appear in the title. * AM: Proposes "a static context
framework for header compression and fragmentation ..." * Will run a beauty
contest on the ML for the title

[16:42] SCHC Tutorial at IETF107        (Dominique)                     [ 5min]
* Dominique: We need to commuicate about SCHC: papers, conferences, teaching
(some already) * Dominique: So why not make a tutorial *Laurent: Before SCHC we
need a tutorial on LPWAN, because people at IETF didn't imagine that there can
be links with only 100 bps datarates. * DB: Yes, let's see the content of this
Tutorial (slide) * OG: How much time? *DB: 1h or 1h30 *JCZ: Planning for 1h is
more or less what is used to do *  DB/OG: What is the deadline to propose a
tutorial ? * JCZ advises to contact EDU as soon as possible * DB: Do you have a
name, or email alias for the EDU team? edu-team@ietf.org . Mail sent out. * DB:
Call for volunters to provide material and run the tutorial

[16:55] AOB                                                  [ 5min]