Minutes IETF125: 6lo
minutes-125-6lo-03
| Meeting Minutes | IPv6 over Networks of Resource-constrained Nodes (6lo) WG | |
|---|---|---|
| Date and time | 2026-03-20 03:30 | |
| Title | Minutes IETF125: 6lo | |
| State | Active | |
| Other versions | plain text | |
| Last updated | 2026-03-29 |
minutes-125-6lo-03
IETF 125 - 6lo Working Group Minutes
Location: Shenzhen, China
Venue: Auditorium
Date: Friday, March 20, 2026
Time: 11:30-12:30 (Local) / 03:30-04:30 (UTC)
Session Administration
Chairs: Shwetha Bhandari, Carles Gomez
Delegate: Luigi Iannone
Responsible AD: Éric Vyncke
Minute Takers: Luigi Iannone, Shwetha Bhandari
Jabber Scribe: [Name]
Official Meeting Link: DataTracker Session
Agenda & Materials
1. Introduction and Draft Status (10 min)
Presenter: Bhandari/Gomez
Materials: Slides: 6lo chairs introduction
Discussion:
Agenda bashing, blue sheets, scribe selection.
No comments on the agenda
AD Review Timeline: Éric Vyncke (Responsible AD) confirmed that he
plans to conduct the AD review by the end of next week. Following this
review, the documents are expected to progress further.
2. Path-Aware Semantic Addressing (PASA) for LLNs (10 min)
Presenter: Luigi Iannone
Draft: draft-ietf-6lo-path-aware-semantic-addressing-13
Materials: Slides: PASA for LLNs
Discussion:
Document Status: Publication has been officially requested for both
documents. The PASA document is considered stable and did not require a
new technical revision. It is primarily an application of GAAO.
3. Generic Address Assignment Option (GAAO) for 6LoWPAN ND
Presenter: Luigi Iannone
Draft: draft-ietf-6lo-nd-gaao-09
Materials: Slides: GAAO for 6LoWPAN ND
Discussion:
The Technical Dispute (Lorenzo Colliti as reviewer of the draft from
6man review request):
Redundancy: Lorenzo argued that DHCPv6 is already a stable,
one-packet exchange mechanism that can be run locally on a router.
He contended that the draft’s justification—that DHCPv6 is too
“expensive” for LLNs—is technically inaccurate. Mechanism vs.
Protocol: Luigi clarified that GAAO is a small option within the
existing 6LoWPAN ND framework, not a standalone new protocol. He
argued it aligns with the 6LoWPAN philosophy of minimizing
multicast and centralized overhead. Alignment with 6LoWPAN
Philosophy: Luigi argued that 6LoWPAN ND specifically tries to
avoid the multicast and architectural overhead often associated
with standard DHCPv6 deployments. GAAO is designed as a generic
container to support various address allocation algorithms (like
PASA), which provides a different use case than standard prefix
delegation. Luigi noted that interoperability documents aren’t
strictly required to prove performance over other methods,
especially when they address different architectural puzzles.
Architectural Philosophy (Stuart Cheshire)
The “One Way” Principle: Stuart referenced a classic IETF tenet:
the goal of the IETF is to find the one agreed-upon way to do
something. He argued that having two ways to do the same thing is a
“downside,” not a benefit. Burden of Proof: Stuart stated that the
burden is not on the IETF to provide counter-arguments, but on the
proposers to prove that a new mechanism is absolutely necessary
because existing ones (like DHCPv6) are insufficient.
Process and Cross-WG Coordination (Jen Linkova, 6man Chair)
Concerns of Duplication: Jen echoed the concerns regarding protocol
duplication and expressed a need for the 6man (IPv6 Maintenance)
working group to weigh in. Next Steps for Review: She noted that
many 6man participants may not be tracking 6lo closely and
committed to bringing this document to the attention of the 6man
mailing list to ensure a broader consensus on whether this
“alternative” mechanism is acceptable to the wider IPv6 community.
Will trigger a formal discussion in 6man to address duplication
concerns.
Carles Gomez(6lo chair hatoff): He noted that the devices used in these
environments will already be using the 6LoWPAN framework. It may be
good to evaluate whether it may be less costly for these devices to add
support for GAAO than using DCHPv6.
Carles Gomez (6lo chair hat): He thanked 6man for managing getting more
feedback on this draft. 6man was CC'ed in relevant email messages about
the draft, but it will be good to get further attention and feedback
from 6man.
Shwetha Bhandari (6lo chair hat on): Identify what is missing in the
justification and update the sections to clarify the advantages over
DHCPv6 and gaps that this addresses. Authors may need to strengthen
Section 1.1 to specifically address Stuart and Lorenzo’s points about
why DHCPv6 was bypassed in favor of an ND-based option.
Éric Vyncke: justification of having a LLN specific mechanism has been
requested 1-2 years ago, he still has to do his AD review though. The
final say will be at the IETF Last Call whether there has to be an IETF
community consensus.
4. SCHC-compressed Packets over IEEE 802.15.4 (10 min)
Presenter: Carles Gomez
Draft: draft-ietf-6lo-schc-15dot4-12
Materials: Slides: Transmission of SCHC-compressed packets
Discussion:
Terminology: Alignment with the SCHC Architecture draft (e.g., “SCHC
Control Header”). ECN Capability: Modified the “B-pointer” in PRO mode
to allow routers to access ECN bits for congestion signaling. Node
Roles: Clarified that 6LNs can act as both hosts and routers, and can
use SCHC for management/control traffic. Open Issue: Address Residue
Length in PRO mode is currently capped at 127 bits; authors are
investigating a fix (e.g., covering only the IID).
Next Steps: Finalize PRO address length logic and monitor SCHC WG
architecture stability before requesting WGLC.
No comments.
5. Transmission of IPv6 Packets over Short-Range OWC (10 min)
Presenter: Younghwan Choi
Draft: draft-ietf-6lo-owc-06
Materials: Slides: Transmission of IPv6 Packets over SR OWCs
Discussion:
The presentation focused on significant updates to the Security
Considerations section, incorporating content from a previous
individual draft to streamline the document. Standards Alignment: The
draft now includes explicit references to IEEE 802.15.7 security
services, specifically focusing on confidentiality, data
authentication, and protection mechanisms. Consolidation: The
individual draft regarding security considerations for IPv6 over OWC
has been officially merged into this document (v-06). Younghwan Choi
noted that there is no longer a need for a separate security draft. No
comments.
6. Update of RFC 8163 (10 min)
Presenter: Kerry Lynn
Draft: draft-ietf-6lo-rfc8163-bis-00
Materials: Slides: Update of RFC 8163
Discussion:
Carles: Would be helpful to look at the previous draft (IPv6 over OWC)
as it has optional support for SCHC and can be of inspiration to do the
same thing in this document. Inclusive Language: Terminology updated to
align with the latest MS/TP specifications. Maintenance: Fixed errata
and updated obsolete references. Implementation: Kerry is exploring a
reference implementation for Zephyr OS. Kerry Lynn: There was an
implementation effort in RIOT but not sure it went upstream. Carles:
Would be good to have feedback from people who have been implementing
SCHC.
Total Scheduled Time: 50 minutes
Meeting Adjourned:
** Meeting Chat **
Éric Vyncke
09:00 Usual Q: do we have a minute taker ?
Shwetha Bhandari
09:00 https://notes.ietf.org/notes-ietf-125-6lo I am going to be taking the
notes , if others can help that will be great!
Éric Vyncke
09:06 RFC 9927 is indeed one of the fastest-to-be-published RFC ;-)
Carsten Bormann
09:07 Over in core, we can match: https://datatracker.ietf.org/doc/rfc9876/
Éric Vyncke
09:21 Thanks for the technical discussion
Carsten Bormann
09:35 Did only I have an audio gap?
Éric Vyncke
09:36 No audio issue in Shenzhen Carles was always heard
Kerry Lynn
09:36 I hear him remotely…
Carsten Bormann
09:36 Thanks
Éric Vyncke
09:51 Thanks to the chairs, the delegate, and all participants of this
session ;-)
----------------------------------------------
POSSIBLE AI HALLUCINATIONS/MISTAKES