On 19/03/14 06:05, Cao Zhen (CZ) wrote:
[...]
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.
Maybe a useful implementation guidance would then be to look for these
APIs or chipsets that provide these APIs if all don't. I guess their
existence may not be self-evident.
[...]
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.
Maybe this could be rephrased to be more clear.
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.
How can you specify the traffic? Is it specific protocol fields that are
applicable or could you throw in e.g., an arbitrary bit mask extending
through the whole protocol stack that if matches would cause the filters
to do something? Some details along those lines would be helpful in the
draft.
Cheers,
Ari
_______________________________________________
Lwip mailing list
Lwip@ietf.org
https://www.ietf.org/mailman/listinfo/lwip
