Minutes IETF117: 6lo
minutes-117-6lo-00

Introduction and draft status Bhandari/Gomez 10 min
Agenda bashing; blue sheets; scribe; Jabber scribe
slides

Agenda bashing, no comments.
Status report
IPv6 ND Multicast Address Listener Subscription (Publication requested)
https://tools.ietf.org/html/draft-ietf-6lo-multicast-registration-15 - Erik -
in AD evaluation, tenatively can be discussed in telechat end of August

------------------------

Transmission of SCHC-compressed Packets over IEEE 802.15.4 Carles Gomez 15 min
https://datatracker.ietf.org/doc/html/draft-ietf-6lo-schc-15dot4-02
slides

Adopted in Jan 2023

Version 2 updates

Request a new SCHC Pointer Dispatch. To avoid limiting the RuleIDs after the
SCHC Dispatch

It is useful to know the IP@ for routing without decompressing the SCHC header
The new SCHC Pointer is byte aligned, and able to represent 128 bit IPv6
destination addresses

Appendix A. Gives header compression examples

Appendix B. Analyses the different RO multihop approaches

- Straightforward even if has the best performance needs all Rules to be stored
by all nodes - Tunneled, RPL-based. Reduce memory requirements, more scalable
but increase the header overhead. - Pointer-based. Scalable, reduce memory req.
but its performance depends on the IPv6 destination address compression
residue. Does not require RPL, not constrained to traversing the root node (may
be subject to other constraints depending on the routing solution). The
solutions depend on the size of the network. Question to the WG: Do we keep the
3 approaches?

Georgios Z. Papadopoulos> I gave some feedback on ML saying that they are
complementary and can fit suitably the deployments Pascal > its worthwhile
keeping the 3 approaches, as long as there is a clear applicability statement
Question to split the document into generic and specifics?

Laurent Toutain - supports linking this draft to the SCHC generic/arch
document, new SCHC header format has been worked on in the hackathon. Pascal -
as LPWAN chair, SCHC header committed to provide as LPWAN wg. Progressing,
defined as a v6 header. 15.4 to be documented in the arch as a generic scheme.
This draft to point to such an architecture doc. Erik - any conflict between
this and LPWAN SCHC work? Pascal - no conflict between LPWAN SCHC work and
this. on chat - Michael Richardson - Do a document for 802.15.4, if that’s what
you are want to deploy and allows others to do theirs, because otherwise,
you’ll never finish. Carsten B - +1 Georgios P - +1

------------------------

Path-Aware Semantic Addressing for LLNs Luigi Iannone 10 min
https://datatracker.ietf.org/doc/html/draft-ietf-6lo-path-aware-semantic-addressing-02
slides
presentation starts - 13:27

Added security

Msg Chat. Errata RFC8138 instead of 3818

Erik > no to NAT66 (it would be a can of worms...)

Solve the conflict between 2 bits (F & H) with signaling

Pascal asks the conflict to be solved

------------------------

Generic Address Assignment Option for 6LoWPAN ND Luigi Iannone 10 min
https://datatracker.ietf.org/doc/html/draft-iannone-6lo-nd-gaao-00
slides
Presentation starts 13:42

Pascal > likes defining a separate option, not necessarily aligning with ERO,
this option needs no map to EARO Luigi Iannone > needs coherence for routing
between EARO and this Pascal > register for which topology the address belongs
to

------------------------

IPv6 Neighbor Discovery Prefix Registration Pascal Thubert 15 min
https://datatracker.ietf.org/doc/html/draft-thubert-6lo-prefix-registration-03
slides
Presentation starts 13:47

wg adopted
Luigi > Registering prefix (slide 4) - the F flag - seems too
overloaded/complex to include in this draft, recommends a separate draft. On
chat Erik > that seems like it’s impossible to do securely especially across
providers (i.e. the phone and wifi case)

------------------------

Architecture and Framework for IPv6 over NBA Pascal Thubert 10 min
https://datatracker.ietf.org/doc/html/draft-ietf-6man-ipv6-over-wireless-04
slides
Presentation starts 14:04
Erik: hard to know if it is better to split the doc in parts or not…

Split the doc - Can be done after 6man last call or part of AD eval

Erik will discuss with Bob (6man chair)

Erik > Redoing multilink subnet - l2->l3 interface is too drastic, requires
careful consideration and discussions.

Pascal/Erik : A BOF on this topic? this may be beyond 6man scope too

Michael Richardson: it is only documenting the assumptions of L2-L3 interface.
Dave Thaler’s document on multi-link does not capture this.

------------------------

Transmission of IPv6 Packets over Short-Range OWC Younghwan Choi 10 min
https://datatracker.ietf.org/doc/html/draft-choi-6lo-owc-00
slides
Presentation start 14:23

- No questions
- Carles: as coauthor, this presentation today was about the bigger picture,
the applicability and the technology, but the draft has already quite some
content. Please feel free to provide feedback.

--------------------------

Session adjourned at 14:31.