Re: [RSN] Update

On Jun 6, 2007, at 4:19 AM, Anders Brandt wrote:

> -----Original Message-----
> From: Timothy J. Salo [mailto:salo@saloits.com]
> Sent: 5. juni 2007 05:03
>
>> (e.g., some nodes may sleep much of the time;
>
> ...
>
>>  Should some nodes, such as power-rich or gateway nodes, act as
>>  proxies (for some functions) for power constrained node?
>
> ...
>
>>  - Should a link/subnet use both MAC addresses and network-addresses,
>      or should only a single set of addresses be used for both  
> purposes?
>
> Operating nodes running on small batteries in very low bandwidth
> environments
> is at the heart of this initiative.
>
> While awareness of sleeping nodes and the use of certain nodes as
> proxies
> is very much inside the scope of this group,

Absolutely.

> I am a bit uncertain
> whether
> header and/or data compression is relevant on the routing layer.
> It might be specific to the individual L2 implementations?
>

Header compression is clearly handled by 6lowpan. As far as data  
compression/fusion/..., if the technique and potential protocol
extensions are within the scope of 6lowpan, the knowledge of some  
node capabilities may be used to route the traffic and are
consequently part of RL2N. Again, a simple line of demarcation.

JP.

> Concerning the proxy node topic, there are (at least) two  
> situations to
> consider:
>
> A: Certain transmission mechanisms are asymmetrical, so that  
> sending to
> a 99% sleeping
> requires a transmission activity from the sending part than from the
> node waking up a
> short while to detect traffic. This case may be considered a
> _POWER_PROXY_.
> Latency for the node response may not be higher than a few 100
> milliseconds.
>
> B: Water sensing nodes and other nodes may wake up extremely  
> rarely, say
> every 5 minutes.
> They send a measurement report to a local proxy, that confirms the
> receival.
> Then the node goes back to sleep for the next 5 minutes.
> The only way to change settings, e.g. the measument interval or the
> target proxy
> for such a node, is to provide a mailbox service, where  
> instructions are
> queued up,
> waiting for the next time, the node makes contact.
> We could call this a _TIME_PROXY_.
>
> Anders Brandt
>
> _______________________________________________
> RSN mailing list
> RSN@ietf.org
> https://www1.ietf.org/mailman/listinfo/rsn

_______________________________________________
RSN mailing list
RSN@ietf.org
https://www1.ietf.org/mailman/listinfo/rsn