Minutes IETF114: lpwan: Wed 13:30
minutes-114-lpwan-202207271330-00

Meeting Minutes IPv6 over Low Power Wide-Area Networks (lpwan) WG
Date and time 2022-07-27 17:30
Title Minutes IETF114: lpwan: Wed 13:30
State Active
Other versions markdown
Last updated 2022-07-27

minutes-114-lpwan-202207271330-00

Meeting Information

WG info

Data / Time

Meeting Information

WG Meeting Agenda

[13:30] Administrivia [5min]

  • Presenter: Pascal Thubert
  • Note-Well, Scribes, Agenda Bashing
  • WG / drafts Status
  • Intro to the need for rechartering

[13:35] Status of SCHC-over-NBIOT (Publication Requested) [5min]

[13:40] Yang Data Model for SCHC (Publication Requested) [10min]

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

  • Topics: Present the updates on the data model, discuss on the
    security part and the integration of this Data Model is a Data Model

    with device/core identities.

[13:50] Compound Ack (Path to Publication) [5min]

  • Associated draft: draft-ietf-lpwan-schc-compound-ack
  • Presenter: Sergio Aguilar Romero
  • Topics: Present the latest changes in the draft, according to
    Dominiques review, and shepherd actions

[13:55] Status of SCHC-over-SigFox [5min]

[14:00] New Work on SCHC IP number (not in charter) [10min]

[14:10] Status of the Architecture draft [10min]

[14:20] Rechartering [QS]

  • Open discussion on need (applying SCHC to Non-LPWAN techs)
  • Presenter: Chairs

WG Meeting Minutes

[13:33] Administrivia [5min]

  • Presenter: Pascal Thubert
  • Note-Well
  • Scribes: Ivan Martinez, Dominique Barthel
  • Agenda Bashing: no comment.

  • WG / drafts Status

    • SCHC over Sigfox was delayed because splitting Compound Ack
      draft, we're getting there.
    • two sbmissions for publication requested to IESG

  • Intro to the need for rechartering

    • other underlying technologies like PPP and IEEE 802.15.x
    • protocol extensions: IP next header (protocol number) for SCHC,
      FEC or other reliability mechanisms

[13:39] Status of SCHC-over-NBIOT (Publication Requested) [5min]

  • Associated draft: draft-ietf-lpwan-schc-over-nbiot
  • Presenter: Ana Minaburo
  • Topics: New modifications mail from Pascal (shepherd review)
  • Notes
    • AM: Present last version (10) of the draft published in July
    • Handled Pascal's shepherd review
    • MTU recommendation in order to avoid RLC segmentation but it
      does not prevent to use other MTU
    • SCHC will be used in RLC, it will be only compression
    • Draft sent to publication
    • Eric: next step is AD review, hopefully done by mid August

[13:44] Yang Data Model for SCHC (Publication Requested) [10min]

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

  • Topics: Present the updates on the data model, discuss on the
    security part and the integration of this Data Model is a Data Model

    with device/core identities.

  • LT: 14 version of the YANG data model, we are converging.
    It covers only what is defined in RFCs, defines rules and
    parameters.
    First, a clarification, added a "-" since we cannot change what has
    been already published
    "Position" was changed to "Index"
    Timer units is adjustable (exponent/mantissa), tick goes from 1 us
    to many years. Default value fits LoRaWAN requirement.
    We got a review from YANG Doctors, very good review. They raised a
    major issue in the nature of the rule. I proposed a change that we
    need to discuss in the ML: nature of rule attribute. It will be
    included in the next version of the draft
    Future work: Add identification of devices in the architecture
    draft (in the YANG model?), we need to see what is the best option
    in order to be compact.
    No questions

[13:53] Compound Ack (Path to Publication) [5min]

  • Associated draft: draft-ietf-lpwan-schc-compound-ack
  • Presenter: Sergio Aguilar Romero
  • Topics: Present the latest changes in the draft, according to
    Dominiques review, and shepherd actions
  • Notes
    • SAR: We change the way padding bits are handled,
    • Remove references to Receiver-Abort
    • Added examples
    • Define Compound ACK as backward compatible

[13:56] Status of SCHC-over-SigFox [5min]

  • Associated draft: draft-ietf-lpwan-schc-over-sigfox
  • Presenter: Sergio Aguilar Romero
  • Topics: Present the latest changes in the draft (shepherd review)
  • Notes
    • SAR: Thanks AM for the review
    • Several changes in terminology across the text
    • Open discussion regarding DTag and RuleID
    • New version of both drafts to be uploaded in order to include
      last AM comments
    • AM: Do we need to wait untin Compound ACK is publish?
    • PT: You can press the button to submit to IESG, IETF will
      publish at the same time because of this dependency
    • PT: expect the shepherd review for the compound ack in a few
      weeks

[14:05] New Work on SCHC IP number (not in charter) [10min]

  • Associated draft: draft-moskowitz-lpwan-ipnumber
  • Presenter: Robert Moskowitz
  • Topics: Open discussion on need

  • Notes

    • RM: reads his slides.
    • Eric: no "Don't Fragment" in IPv6, it comes by default.
    • RM: Once I have a IP protocol number, can SCHC-compress DTLS
      outer headers, and SCHC-compress DTLS payload
    • PT: We don't have FEC for fragment reliability, this makes sense
      in lpwans
    • Pascal: see the network guys for FEC algorithms, and bring them
      here.
    • Pascal: SCHC does fragmentation, last fragment could carry FEC.
    • Eric: I think it would be better to put the draft in Intarea.
      Asking for a protocol number should be in their charter (to be
      checked).
    • Pascal: We'll see what Intarea says, we can maybe change the
      charter

    • Show of hands (in Meetecho): is "IP NH for SCHC a good idea?" 10
      positive answers, no negative.

    • Carstern (from chat): Getting a IP protocol number for SCHC is a
      no-brainer. But we need to say where the context comes from. See
      RFC 5857. There is no don't fragment in IPv6. Please read RFC
      5856, 5857, 5858 and think about how these can be done for SCHC

[14:10] Status of the Architecture draft [10min]

  • Associated draft: draft-ietf-lpwan-architecture
  • Presenter: Pascal Thubert
  • Topics: What's added, what's next (new techs)
  • Notes
    • extending SCHC to other areas than LPWAN.
    • in these situations, no more implicit what is "Up" and what is
      "Down"
    • also need to handle mutliple "sessions" or "connections". Only
      one SCHC instance within each session or connection.
    • "Device" is defined as the one that opened the
      session/connected.

[14:20] Rechartering [QS]

  • notes
    • SCHC over PPP did not attract attention at Interea, bring it
      back to LPWAN with rechartering.
    • FEC within SCHC would be nice, would benefit LPWA networks.
    • Show of hands "who's willing to take on more work in this WG?"
      11 yes, 2 no.
    • LT: Its a good ide of rechartering but what happends with the
      name?
    • Eric: I'd assume changing the name is useless, change the
      charter.
    • BM : The WG should be named SCHC
    • Carles: the mesh topology could be explictely mentioned in the
      architecture draft. Also discuss SCHC fragmentation vs. 6lo
      fragmentation
    • Pascal: if you want to forward fragments, SCHC fragmentation is
      not usable. Need to go back to 6LoWPAN fragmentation
    • Pascal: we need more discussion, more interim meetings, to
      decide what goes in the charter.

AOB

None

Meeting adjourns 14:27 local time.