Minutes IETF123: 6lo
minutes-123-6lo-00
| Meeting Minutes | IPv6 over Networks of Resource-constrained Nodes (6lo) WG | |
|---|---|---|
| Date and time | 2025-07-23 07:30 | |
| Title | Minutes IETF123: 6lo | |
| State | Active | |
| Other versions | markdown | |
| Last updated | 2025-07-29 |
6lo WG Agenda - IETF 123, Madrid
07:30-9:00 (UTC) @ Patio 2
09:30-11:00 (Meeting venue time) @ Patio 2
Wednesday, July 23, 2025
Chairs: Shwetha Bhandari, Carles Gomez
Responsible AD: Éric Vyncke
Minute takers: L. Toutain
Jabber scribe: TBD
Introduction and draft status Bhandari/Gomez 10 min
Agenda bashing; blue sheets; scribe; Jabber scribe
Chairs slides
No comments on agenda
Status report
2 documents in RFC Editor Queue
A new draft to fix the C-flag, no conflict with existing implementation
Fastest draft to RFC - on track :-)
4 other WG documents
No comments on documents
Path-Aware Semantic Addressing for LLNs - Luigi Iannone 15 min
No news - good news :)
Generic Address Assignment Option for 6LoWPAN ND
Int area and GENART review done
GENART review, clarify some points on error coding and R bit usage, pending
INTDIR review, done
Main changes in -04, -05 and -06
Specification of GAAO is stable
No objection in the room to move Generic Address Assignment Option for 6LoWPAN ND to WGLC, will start WGLC on mailing list
Shepherd to be assigned, volunteers welcome
Transmission of SCHC-compressed Packets over IEEE 802.15.4 Carles Gomez 15 min
Version -10: transition Protocol Stack (TPS)
Appedix B: different scenarios
Editorial improvement
Structure of the document remains stable
TPS: keep 6lo for IPv6 and SCHC for upper layers (UDP and CoAP)
Slide 7 -
Terminology may change a little bit to align with SCHC architecture document evolving terminology
Opinion on SCHC stratum - whether to have one for UDP and another after UDP before CoAP
L. Toutain > depends on the scope of CoAP, and cryptography/encryption profile for CoAP
Pascal > SCHC stratum - terminology discussed in Side meeting, but no decision done, will be done at the SCHC WG meeting and confirmed on ML. PLease
hold updates to document till the decision is made. This is a great work to explore the architecture
Slide 9 -
Pascal > draft has 4 options , is there a plan to limit it to one recommendation?
Carles > WG polled earlier and wanted the flexibility as long there could be a clear applicability statement.
The same mode has to be used in a domain.
Carles > question to the WG - what should we do
Alexander Pelov > poll the WG , in 6lo deployments could be heteregenous there could be SCHC enabled nodes along side the 6lo only nodes.
Ask Wi-Sun, Thread and other implementers which mode are the most interesting.
Carles > for the mix of nodes in the network we need something like this. There is a bit of content in the OWC draft,
to indicate which node is supporting SCHC, good for transition.
Added Annex B.4 with a summary of Pros and Cons
Next Steps: complete examples, stabilize section 5 and align with SCHC terminology.
Shwetha > Will you consider adding SCHC stratum for CoAP and security/encryption aspects
Carles > based on SCHC discussions that will be considered
Alexander Pelov > terminology in the draft is confusing post update (e.g. "multiple-endpoint")- need other reviewers to help make it more clarify
Carles > Will be great to get reviews to make the draft more consistent
Marion Dumay - volunteered to review
Chat:
Robert Moskowitz >
Yes, ask the deployed field. Which will actually be used?
Robert Moskowitz >
can you map these modes to “common” actual use cases?
Transmission of IPv6 Packets over Short-Range OWC Younghwan Choi 10 min
a new section to include SCHC
introduce S bit to indicate SCHC capability
Ann Krieger > IEEE 802.15 vice chair - have reviewed the draft and thank you for addressing the comments. IEEE 802 follows the work
IPv6 Neighbor Discovery Prefix Registration Pascal Thubert 10 min
extend ND mechanism to support prefix registration
IESG Review cycle complete
In RFC editor queue.
Pascal > Question to the group with this draft done 6LOWPAN-ND is done, we could make it more efficient by extending it to broadcast and mixed networks
Éric Vyncke > if there is energy in the group it is ok to take this up as it fits in the charter.
When there is no more work (or energy) the group is closed.
Poll :
Should we take up 6LOWPAN ND extensions to broadcast and unicast mix to make it efficient
total participants: 30
yes - 7 + 1 (manual update)
no - 1
no opinion - 7
Chairs > If there are people who want to take this on the mailing list and create a draft they are welcome
Fixing the C-Flag in EARO Adnan Rashid 10 min
Slides
fixing C bit position and register it to IANA
IESG review done, in rfc queue and waiting to be published
Éric Vyncke > It wasnt a errata not a mistake. Errata is on published text.
Éric Vyncke > 84 days from draft to RFC
No AOB
Session ended (total duration: 67 minutes)
Total agenda time: 70 min