Chairs: Zhen Cao, Mohit Sethi AD: Suresh Krishnan Presentation materials: https://datatracker.ietf.org/meeting/106/session/lwig Meetecho for remote participants: https://www.meetecho.com/ietf106/lwig/ Etherpad for notes: https://etherpad.tools.ietf.org/p/notes-ietf-106-lwig?useMonospaceFont=true Note takers: Mohit Sethi Note well Zhen: present update to working group and non-working group documents Mohit (no-hat): Should move forward draft-struik-lwig-curve-representations Rahul: need reviews for draft-ietf-lwig-nbr-mgmt-policy Zhen: we can do WGLC to force people to review Rahul: already deployed and working in production John: will add tls 1.2 numbers to draft-ietf-lwig-security-protocol-comparison Suresh: if you are going to wait for some numbers, just remove them. value in having this published Carsten: draft-ietf-lwig-6lowpan-virtual-reassembly ready for WGLC. Will submit Zhen: design team in 6lo Carsten: this draft is saying what you can do with the existing protocol Suresh: can hold this or if you want to merge that is also fine Carles: we have time in 6lo on Wednesday Carsten: draft-ietf-lwig-coap-06 updates Zhen: how to process this document Mohit: can we have an editor who we can poke Carsten: good idea. ask me again in february. in principle yes Suresh: let it die for now. when there is energy, we can update Zhen: draft-bormann-lwig-7228bis-05 adoption? Carsten: need feedback on new things in draft. one new thing is security classes and energy usage Mohit: documents specific on topic. Participants not providing comments. Participation seems to be going down. Maybe don't have meeting every time. We keep working group and list alive. When there is sufficient drive on documents, we can schedule a meeting. Up to you how frequently you want the meetings. Carsten: Standards track documents override informational documents. Maybe we should do virtual interims at some point when we are not in frenzy like the IETF week. Suresh: Mohit what you say sounds good. Also fine with setup a meeting mid cycle. I see the low energy. Similar thing happened to dhc. Carles: trying to involve participants from related working group helps Carles: presenting updates to lightweight tcp document Mohit: time for us to do shepherd writeup and send it forward Zhen: thank you to markku and ilpo for reviewing Rahul: presenting whitefield Abhijan: what is the reason for the number of Qualnet? Trying to understand if it is because of cost or features. Rahul: Not used Qualnet Abhijan: I have been using Qualnet. It is pain Mohit: should submit a blog? Suresh: yes, I can put you in touch with ietf.org people. Thanks Mohit for suggestion.