Skip to main content

Minutes interim-2023-lpwan-04: Tue 15:00
minutes-interim-2023-lpwan-04-202302141500-00

Meeting Minutes IPv6 over Low Power Wide-Area Networks (lpwan) WG
Date and time 2023-02-14 15:00
Title Minutes interim-2023-lpwan-04: Tue 15:00
State Active
Other versions markdown
Last updated 2023-02-27

minutes-interim-2023-lpwan-04-202302141500-00

Interim #4 2023

Data / Time

Meeting Information

Interim Agenda

[16:00] Administrivia [10min]

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

[16:10] Rechartering [5 min]

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

[16:15] SCHC Compound Ack [30 min]

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

[?] AOB [ QS ]

Meeting Minutes (times in CET)

[16:05] Administrivia [10min]

  • Note-Well, Scribes, Agenda Bashing

    • Laurent: published new draft about access control. Very basic,
      just a summary of what was discussed at last meeting.
    • Pascal: have you seen discussion on ML today?
    • Laurent: not yet
    • Pascal: "a YANG data model" instead of "data model"
    • Laurent: solved this a week ago, document published today
    • Eric: comment in AUTH48 stage was just to move the last
      paragraph of the security section directly after the first two
      paragraph (from the YANG security template).
    • Ana: answered together
    • Eric: can find the mails in the auth48 email archive
  • WG Status

    • schc-over-sigfox waiting for compound-ack
    • yang model will be RFC9363

[16:12] SCHC Compound Ack [30 min]

  • Presenter: Carles / Sergio
  • Associated draft: draft-ietf-lpwan-schc-compound-ack
  • comments by Eric (AD) already answered in upcoming -11, almost
    ready.
  • Eric: strongly suggest replacing complete sub-sections, not parts of
    text within sections
  • Eric: regarding Appendix of RFC8724, append new text to it with NEW
    TEXT
    marker before and after.
  • Sergio: will add paragraph to explain ACK (???)
  • Pascal: can we submit to IESG
  • Eric: as soon as he is happy with new draft by Sergio, I-D will go
    to IETF Last Call

[16:19] Rechartering [5 min]

  • Presenter: Pascal Thubert
  • Topics: Review proposed work item
  • received comments by Ana
  • gave a list of what we could support, but without committing to them
  • Eric: "foo" could be replaced by "under IP"
  • Dominique: "underlying layer" was used in RFC8724
  • Eric: "bar" could be replaced by "carried protocol"
  • Pascal applying these changes on charter text now.
  • Eric: this will be reviewed by IESG anyway, will come back with lots
    of changes requested.

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

  • Presenter: Chairs, Ana Minaburo
  • Associated draft: draft-ietf-lpwan-architecture
  • Topics: Ivan’s comments, cont.
  • let's have one architecture that encompasses all use cases.
  • having the historical two steps of the architecture (point-to-point
    and multi-hop) does not help.
  • Alex: once we have the new charter, we'll read the arch doc again
    and make sure everything is covered.
  • Pascal: arch doc should describe how SCHC can be inserted between
    layers at multiple positions
  • Pascal: discussion by Laurent on access control will get in there
    when stable enough.
  • Laurent: access control just a draft, then find its way into the
    architecture. Should not be specific to point-to-point or mesh.
    E.g., make sure to identify SCHC instances.
  • Pascal: please post a mail with crafted wording for the arch doc
    (security consideration section?)
  • Laurent: not fully clear yet.
  • Pascal: the "how" is in the standards track doc, arch is only
    overview
  • Alex: we need time to work on the access control, looking forward to
    the discussion.
  • Pascal: more discussion when Bob M is with us.

[16:38] AOB [ QS ]

  • IETF116

    • LPWAN session requested for Yokohama
    • Pascal might be flying, not sure yet
    • Alex not flying
    • Laurent won't be in person
    • Need to find somebody to be on stage in person, will see
  • Next interim meeting

    • conflicts with MWC, Alex will not be available for the interim