6lo WG Minutes - IETF 116, Yokohama 02:30-04:30 (UTC) @ G316 09:30-11:30 (Meeting venue time) @ G316 Friday, March 31, 2023 Chairs: Shwetha Bhandari, Carles Gomez Responsible AD: Erik Kline Minute takers: Shwetha Bhandari Jabber scribe: TBD Introduction and draft status Bhandari/Gomez 10 min Agenda bashing; blue sheets; scribe; Jabber scribe https://datatracker.ietf.org/meeting/116/materials/slides-116-6lo-6lo-chairs-introduction IPv6 Multicast address registration draft - shepherd write up to be completed - AI Shwetha No additions to agenda Status update of 6lo Applicability & Use Cases Yong-Geun Hong 10 min https://datatracker.ietf.org/doc/html/draft-ietf-6lo-use-cases-15 https://datatracker.ietf.org/meeting/116/materials/slides-116-6lo-status-update-of-6lo-applicability-use-cases Yong-Geun Hong presenting -16 will be ready for RFC editor - Erik will progress the draft when -16 is published Path-Aware Semantic Addressing for LLNs Luigi Iannone 15 min https://datatracker.ietf.org/doc/html/draft-ietf-6lo-path-aware-semantic-addressing-00 https://datatracker.ietf.org/meeting/116/materials/slides-116-6lo-path-aware-semantic-addressing-pasa-for-low-power-and-lossy-networks Luigi presenting Luigi: It’s experimental now, it’s up to the WG if to standard track. Any comments here? Erik Kline > Requires implementation reference and deployment section. Luigi > will update on implementation reference On Slide 7 : Pascal Thubert > On P and H bit - The bits are mostly consumed by other drafts On Slide 7 : Kiran > Make the router and host bit explicit, suggests to use 2 bits , 1 bit for host, 1 bit for forwarder On Slide 7 : Luigi > discuss on the list Pascal > See section 7.1 of https://datatracker.ietf.org/doc/html/draft-ietf-6lo-multicast-registration#name-placing-the-new-p-field-in- Carles > To authors - other than security, multicast is also missing Reliability Considerations of Path-Aware Semantic Addressing Luigi Iannone 15 min https://datatracker.ietf.org/doc/html/draft-li-6lo-pasa-reliability-01 https://datatracker.ietf.org/meeting/116/materials/slides-116-6lo-reliability-considerations-of-path-aware-semantic-addressing Luigi presenting Slide 12: Guangpeng Li > General comment: reliability part should be additional feature of PASA, it depends on redundancy conditions, redundant links and redundant nodes. Slide 12: Guangpeng Li > Another comment: whether to use multiple addresses mechanism should depend on applications, because some applications can not work with multiple addresses at all. Slide 12: Luigi > multiple addresses is not mandatory, it depends on application - applications do not have to change Slide 12: Guangpeng Li > We need more input and discussion from community including in the list. Carles to WG> need community discussion and feedback Transmission of SCHC-compressed Packets over IEEE 802.15.4 Carles Gomez 30 min https://datatracker.ietf.org/doc/html/draft-ietf-6lo-schc-15dot4-01 https://datatracker.ietf.org/meeting/116/materials/slides-116-6lo-transmission-of-schc-compressed-packets-over-ieee-802154-networks Carles presenting End of presentation Stuart Cheshire > cryptographic security and integrity appreciated and needed. But making it optional leads to accidental corruption Carles > Need to check how many 15.4 use no security mode, integrity protection is sufficient with udp checksum. Stuart Cheshire > e2e security, studies show corruption happens not in transit but due to software bugs on the end systems. Worried about omiting integrity checks Pascal on chat > For all I know that mode may be used in short windows of time to set up communication After the join the l2 security is set up Chat room: Adnan Rashid Please consider my vote for Pasa adaptation. I don’t remember if I gave my vote through email or not. 🙃 06:07:17 IST Pascal Thubert See section 7.1 of https://datatracker.ietf.org/doc/html/draft-ietf-6lo-multicast-registration#name-placing-the-new-p-field-in- 06:28:45 IST Adnan Rashid it would be a good contribution if SCHC use for 6lowpan-ND messages. 07:24:05 IST Pascal Thubert For all I know that mode may be used in short windows of time to set up communication 07:29:14 IST After the join the l2 security is set up Session concludes in 90 minutes