Hello Ari, Thanks a lot for your comments and suggestion.
Please see my inline reply. > Here's some comments on draft-hex-lwig-energy-efficient-02. > > In general I think this is good stuff and looking forward to seeing more > especially > on how to take L2 & L1 features into account at L3 and above. Are there some > standard APIs or such available BTW? Sadly, not yet standard, and the chipset do provide some APIs for their own chipset. > > More specific comments on the text: > > As show in > Figure 1 below, the IETF has developed CoAP as the application layer > and 6LoWPAN as the adaption layer to run IPv6 over IEEE 802.15.4 and > Bluetooth Low-Energy, > > Considering the current work at 6lo it would be good to mention 15.4 and BTLE > are just examples of what 6LoWPAN can and will be used on. That said, focusing > only to those two in this draft is probably a good idea. I discussed with authors, they agree to focus on 15.4 and BTLE. > Below we list the energy consumption profile of the > most common atom operations on a prevalent sensor node platform. > > What's "atom operations"? We meant the basic operations that are not dividable. > Traffic Filtering Service (TFS): A service provided by an access > > Especially since the IEEE standards are not easily accessible, a bit more > details on > this would be interesting. Can one e.g., address application layer protocols > with > the filters? That's an issue. Normally the IEEE specs will be free for 6 months since publication. The TFS is a capability provided by 802.11v. e.g. it can be used to filter out ICMP message over the air. The Access Point sends a TFS Request to the node, and the node will ack and then the specified traffic will not passed from the infrastructure to the wireless nodes. _______________________________________________ Lwip mailing list [email protected] https://www.ietf.org/mailman/listinfo/lwip
