NOTE: There seems to be problems with the HedgeDoc Note takers are encouraged to take notes off-line [11:30] Introduction and draft status Chairs 10 min Agenda bashing; scribe; Jabber scribe EV: Thaking Shwetha and introducing the new responsible AD - Jen. Welcome, Jen Jen: Thank you! LT: doing the notewell and agenda bashing Carles: update on the status of PASA for LLNs and GAAO for 6LowPAN ND, SCHC over IEEE 802.15.4, Eric: intends to remain the responsible for the PASA and GAAO until publication [11:35] PASA and GAAO Luigi Iannone 10 min (draft-ietf-6lo-path-aware-semantic-addressing-16) Luigi presenting the timeline of the draft. Presents the update from last version. No pending actions. Eric: to the Chairs - update it to ‘experimental’ and not standards track. Once this is done, we go for WGLC Carles: is there need to update the Shepherd review? Eric: yes, explain why we are changing the status (draft-ietf-6lo-nd-gaao-12) Luigi: main concern: how GAAO compares to other address assignment mechanisms, e.g. DHCPv6 and SLAAC Main quesiton: WHEN GAAO can be used? 3 conditions to be used: RFC 8505-based 6LoWPAN depl Distributed Address Assignmenet Function (AAF) Inefficient multicast Added applicability compared to SLAAC and DHCPv6 (in which cases to use what). LT: the appendix is useful. [11:46] SCHC-Compressed Packets over 802.15.4 Carles Gomez 10 min (draft-ietf-6lo-schc-15dot4-15) Carles: presenting the objective Update version -15 - alligned to draft-schc-architecture-06 Omar Merroun - feedback on the ML Some changes were introduced to answer his requests PRO frame format change - ECN bits are now part of the PRO frame format. That comes from the feedback from Omar, there was the need to be able to access the ECN field (2 bits). Omar conirmed on the list that this fixes the issue. Appendix C from the draft gives the address residue length, which is very long. A comment on the ML suggested that this should be moved to the text - and this was done - now part of seciton 3. Allignement with draft-schc-architecture-06. Several updates, a lot of concepts were clarified: SCHC Instance vs Session, Endpoint, Control Header, etc. However, changes in draft-schc-architecture-07: “SCHC Payload” is back “SCHC Header” These terms are quite clear - next update is clear as well. Alexander: do the changes make sense? Carles: yes, we are converging Kerry Lynn: does that mean it should be also validated by the SCHC WG ? Eric: it’s a 6lo document, send a mail to SCHC WG when in WGLC for info Alexander: please do, we’ll be happy to review Carles: not yet WGLC-ready, but very happy with how it goes. [11:58] Transm. of IPv6 packets over SR OWC Younghwan Choi 10 min (draft-ietf-6lo-owc-08) Younghwan: clarification of the changes Next step: request for final review of remaiing sections LT: it is important - the integration of the SCHC bit - should we keep it in this document, or make it more generic? Carles: also having similar thoughts. That is a question - should there be a document to indicate if SCHC is supported. [12:02] RFC 8163 bis Kerry Lynn 10 min (draft-ietf-6lo-rfc8163-bis-01) 4CommentHighlight Agenda (II/II) Kerry: presenting updated, since -00 Building a testbed, which is compatible with useful / more recent OS/system. One issue that was identified is that if nothing is compressed, we add 1 byte, max lenght field 1509 -> 1510, so MSDU. <= 1501 There doesn’t seem to be implementations yet, so that is not a breaking change. MS/TP Terminology corrections. Added test cases, which can be used with scapy to validate. Implementation status: Attempted to do a RIOT-OS port with STM32. There was some issue with buffer sizes. New target is nRF52840-DK (3 nodes) - it works. In the process 3 RIOT bugs were identified. 2 PRs were accepted, 1 is being reviewed. Open issues: Proposal - that SCHC over MS/TP is treated as a separate document. Not an expert in SCHC. Ship this document now, do SCHC as a separate document. Invitation to researchers, students, academics or other people - do an review. Invitation to do other implementations (Zephyr?). Wireshark is the conformance tool Carles: agree with the point on SCHC - to do another document on SCHC. Martine Lenders: RIOT maintainer. What would it take to bring the branch working? Kerry: this is a completely new work Dave Robin: agree this should go to WGLC and excited. LT: for the SCHC compression, if you can provide PCAP traces we can work on the SCHC compression profile. Also, as academic, can work on implementation. Kerry: will follow up. [12:16] 6LoWPAN Payload Length w/ L2 Padding Adnan Rashid 5 min (draft-rashid-pecorella-6lo-lowpan-padding-length-01) Adnan: found a problem L2 / Ethernet padding is the problem It is a well known problem - please read the draft. LT: a little surprised by the term 6LBR, as there is no routing function, only bridging. Adnan: you can consider it as a switch. Consider it as a bridge. Carles: no hat. Did a review of the -00 version. It is already quite complete for a -00. It tackles a problem and provides a solution. Carles: chair hat: on. Need more reviews. Discuss on the ML on the issues to progress. LT: a good document that has to be adopted by the group after reading. Luigi: wanted to say that will review and share on the mailing list. [12:25] IPv6 over CAN Jungsoo Park 5 min Jungsoo: The bus cannot be replacedd/ The devices have to be reachable. Hannes on the chat: CAN buses in cars are getting replaced by T1s Jungsoo: description of the CAN topology/identifier specs. 4 questions: Frame format, rule ID size, coexistence (identifiers), adoption ? LT: out of time. Answer the questions on the Mailing List Carles: yes, very intersting work. Glad the work restarted. To note - an implementation is not per se a requirement. We need rough consensus for adoption. Thank you all, see you in Kuala Lumpur.