Markdown Version | Session Recording

Session Date/Time: 14 Feb 2023 15:00

LPWAN

Summary

This interim LPWAN Working Group meeting focused on the status of various drafts, particularly the coap-lpwan-compound-ack document's AD review and preparation for IETF Last Call. Significant discussion also occurred regarding the proposed recharter text, with specific wording adjustments made. The working group also reviewed the architecture document's structure, deciding to maintain its current high-level approach, and discussed the future integration of Access Control principles once consensus is reached.

Key Discussion Points

• Agenda Review:
  • The proposed agenda included updates, rechartering discussion, compound-ack status, and next steps for the architecture document.
  • An additional item on Access Control (from a new draft by Lauren) was added for brief discussion, noting its early stage.
• Document Status Updates:
  • draft-ietf-lpwan-compound-ack (Compound-ACK): Received AD review, almost all changes applied. Eric (AD) received one slide of updates.
  • draft-ietf-lpwan-nbiot (NBIoT): Currently in the RFC Editor's "edit" state.
  • draft-ietf-lpwan-schc (SCHC): Publication is blocked by compound-ack; will be published concurrently.
  • draft-ietf-lpwan-yang-data-model (YANG Data Model): In AUTH48, with most issues resolved. RFC number 9363 is already assigned.
• Discussion on draft-ietf-lpwan-compound-ack:
  • Sergio presented updates following the AD review of version 10.
  • Main discussion revolved around how to specify changes to RFC 8724:
    • The authors' initial approach of indicating "new text" vs. "old text" was not preferred for readability.
    • Decision: For complete sections/subsections, replace the entire text. For appending to existing sections (like Appendix D), clearly state that new text is appended and mark its start/end.
  • A paragraph describing the Compound-ACK system will be added for clarity.
  • The updated draft is expected to be sent by end of day or early tomorrow.
  • Decision: Once the AD is satisfied with the updated text, the document will proceed immediately to IETF Last Call.
• Discussion on Rechartering:
  • The proposed recharter text was presented, noting stability since the last discussion, with only one mailing list reaction.
  • The primary change highlighted was the introduction of "multi-hub" in the second paragraph to emphasize the broader scope beyond traditional single-hub LPWANs, explicitly exposing sessions between endpoints.
  • Discussion on work items, particularly the placeholder terms "Foo" and "Bar" for SCHC encapsulation.
    • Dominique suggested changing "Foo" (underlying layer for SCHC) to "underlying layer(s)" or "sublayer(s)".
    • Dominique suggested changing "Bar" (protocols over SCHC) to "protocol(s)" or "carried protocol(s)".
  • Action Item: Pascal will edit the recharter text to incorporate these suggestions and send it to the AD (Eric) for the next stage of the process.
  • Decision: The rechartering process will be initiated this week.
• Discussion on Architecture Document (draft-ietf-lpwan-architecture):
  • Pascal revisited the previous discussion about a two-step or two-stage structure for the architecture document (single-hub vs. multi-hub with explicit sessions).
  • Decision: The working group converged on maintaining the current single, high-level architecture document structure. The document is meant to describe the current state and future direction, not a historical progression. The implicit/explicit session concept and multi-hub support are adequately covered.
  • Action Item: Once the new charter is finalized, WG participants will re-read the architecture document to ensure alignment and identify any missing details, particularly regarding SCHC's role in various layers and protocols (the "Foo" and "Bar" concepts from the recharter).
  • Access Control: Lauren's early draft on Access Control was mentioned. While critical, the architecture document should remain high-level and generic.
    • It was noted that the group needs to converge on Access Control principles before they can be reflected in the architecture.
    • Action Item: Lauren will craft specific wording for how Access Control could be described in the architecture's security section, based on use cases and principles discussed, and post it to the mailing list for wider feedback.
• Next Meetings:
  • A WG meeting has been requested for Yokohama. Attendance in person is uncertain for several participants.
  • The next interim meeting is scheduled for February 28th.

Decisions and Action Items

Decisions

• The draft-ietf-lpwan-compound-ack document will proceed to IETF Last Call immediately upon final AD approval of the incorporated changes.
• The LPWAN rechartering process will be formally initiated this week.
• The architecture document (draft-ietf-lpwan-architecture) will maintain its current high-level structure and will not be split into two stages (single-hub vs. multi-hub).

Action Items

• Sergio et al.: Update draft-ietf-lpwan-compound-ack to adhere to the agreed text replacement/appending strategy for modifications to RFC 8724 and submit the revised draft.
• Pascal: Edit the proposed recharter text to replace "Foo" with "underlying layer(s)" and "Bar" with "protocol(s)" or "carried protocol(s)", and then send the updated text to the AD (Eric).
• All WG Participants: Re-read the draft-ietf-lpwan-architecture document after the new charter is finalized, and contribute any necessary updates to ensure alignment, particularly concerning SCHC's flexibility in various layer configurations.
• Lauren: Draft specific text for the architecture document's security section that addresses Access Control principles, based on the ongoing discussions and use cases, and circulate it on the mailing list for feedback.
• Chairs: Continue efforts to secure a WG meeting slot and local delegate for Yokohama.

Next Steps

• Finalize and submit the draft-ietf-lpwan-compound-ack for IETF Last Call.
• Proceed with the formal LPWAN rechartering process.
• Further develop and discuss the Access Control draft by Lauren, aiming for convergence on principles that can inform the architecture document.
• Prepare for the next interim meeting on February 28th and the Yokohama IETF meeting.