IETF-91 lwig agenda Session 2014-11-13 1520-1620: Coral 4 - Audio stream - lwig chatroom Minutes: - Matthias - Dominique Jabber: - Carsten Agenda ** Introduction, agenda bashing ** Document status lwig-cellular: ready for adoption? who has read the draft? a few hands. Ari comments that mostly editorial changes lwig-coap Mathias: on hold, work will resume. Did not get much feedback. Have new material to include and will see. Carsten: Feedback on Observe brought up interesting points for the document, Block will probably produce similar points Expired docs tls-minimal. additions to be made. Sandeep ? welcome more feedback from implementers ikev2-minimal has been dormant, actually even expired, will be rescucitated. Carsten: Old guidance document serves as "quarry." 6LoWPAN information still needs to be moved somewhere Brian: Think about rechartering due to what happened to the work. a lot of work was predicated on the guidance document. ** IoT use cases presentation: (Qiao Fu) * draft-fu-lwig-iot-usecase Many smart home devices in China (IP enabled light bulbs, smart plugs, ...) 920IP uses ZigBee IP (Japanese smart home control protocol, see ECHONET Lite, 920 MHz) makes a case for virtual CPE at the operator side. Draft is supposed to track industry development ** Energy efficient implementation presentation: (Carles Gomez) * draft-ietf-lwig-energy-efficient -00 was presented at Toronto, will today provide overview on updates Most changes in Section 3 (MAC and RDC) new text better motivates need for radio duty-cycling, explaining that idle-listening is the key problem. Duty cycling techniques: - several variants of channel sampling are possible (use of preamble, repetition of data frame). - scheduled transmissions (e.g. BT-LE) - Listen After Send (e.g. RIT of 15.4e) Effects of duty-cycling - increased latency - increaded need for buffering, waiting for transmission opportunity - both influence the upper layer, therefore shal be taken into account Energy-based routing metrics. Added text to refer to RFC6551 "Node Energy" metric. Application layer interactions. Proxies may help sleeping. More proposals currently being discussed. Cross layer optimization. Carles: Cross Layer optimization section is almost empty and the whole document deals with this. Should we simply remove it or is there specific interest? Robert Craige: Agrees to remove it ? Hong: Are there specific application layer techniques recommended? (???) Carles: No preferences/recommendations, just an overview what is there ? Hong: ??? Carles: Lower layers are out of scope for the IETF, but they have impact Dominique B: Cross-layer opt is a hot topic in research, but IETF mostly prevents it because it's so much about layers. What we need is for layers to provide better interfaces for the system to reach global optimal. Ari: Maybe incluse coap-pubsub which is the latest work on application layer support for sleepy nodes. Tim Carey: OneM2M has a CoAP binding with an application layer mechanism for sleepy nodes, and there is the LWM2M queueing mode ** IPv6 mapping to non-IP protocols: (no presentation) * draft-rizzo-6lo-6legacy-02 ** Organization Question to the WG if we should recharter. Original charter focuses on guidance around a list of specific protocols, but guidance was moved to protocol-specific WGs Hannes: Software and hardware considerations are useful, but it is not what IETF usually does. Hard to stay at this abstract level and make it useful for software developers. Often authors have not fully understood the challenges either, e.g., the details about radio technologies. We could provide something powerful here by "translating" the thick datasheets for hardware into something digestable for software developers. Brian H.: Last part of charter needs attention. Hannes touched on this. Charter states it would be mostly IP and transport layer, but we heard it is not. We heard about application and security (and radios). Robert C.: Low-layer things have impact on all layers up to the application, so it needs to be considered (e.g., sleeping or noisy channels). Brian H.: Would support such a recharter. There should not be hypotheses, but things that have been implemented. Hannes: Did not update the tls-minimal document for this meeeting, since was working on other documents and testing on hardware, which created new input for the document. Energy and performance measurements from different chips would be very helpful (Hannes mainly worked on ARM). Tim Carey: we've been consumer of information produced here. E.g. in OneM2M. Referenced LWIG documents. Thank you for that. Provides justification for choices. For the future? suggest terminology. Robert C.: Who is for rechartering? Humm Robert C.: Who is against rechartering? No humm