Re: [6lowpan] "Advertize on Behalf" flag in ARO

Thanks Mukul, 

I realized indeed that the case I had in mind is a special case, in which all nodes are routers. (e.g. as in ad-hoc networks with uniform stack on all nodes)

best regards
Esko

-----Original Message-----
From: Mukul Goyal [mailto:mukul@uwm.edu] 
Sent: Wednesday 30 March 2011 2:40
To: Dijk, Esko
Cc: 6lowpan; Erik Nordmark
Subject: Re: [6lowpan] "Advertize on Behalf" flag in ARO

Hi Esko

In RPL, a node can advertise reachability (in DAO messages) to its hosts and addresses in its sub-DAG. A node should (must?) not advertise reachability to any other addresses.

Also, a 6LN (host) need not know any thing about RPL at all. It can simply attach to a RPL router as a host. Any node that runs RPL is a router. An RPL leaf node is also a router.

Thanks
Mukul  

----- Original Message -----
From: "Esko Dijk" <esko.dijk@philips.com>
To: "Erik Nordmark" <nordmark@acm.org>, "Mukul Goyal" <mukul@uwm.edu>
Cc: "6lowpan" <6lowpan@ietf.org>
Sent: Tuesday, March 29, 2011 7:55:48 AM
Subject: RE: [6lowpan] "Advertize on Behalf" flag in ARO

Hello,

as far as I understand RPL reachability is indeed advertised to both 6LR/6LNs, the only distinction is that a 6LN (host) would operate as a RPL leaf node (as in section 8.5 of rpl-19). So a 6LR does not have to 'detect' first whether another node is 6LR or 6LN.

best regards,
Esko Dijk

-----Original Message-----
From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On Behalf Of Erik Nordmark
Sent: Tuesday 29 March 2011 13:14
To: Mukul Goyal
Cc: 6lowpan
Subject: Re: [6lowpan] "Advertize on Behalf" flag in ARO

On 3/3/11 5:07 AM, Mukul Goyal wrote:
> Hi all
>
> Recently Anders pointed out the need for the "Advertize on Behalf"
> flag in an Address Registration Option (ARO).
>
> We would not have needed this flag if only a host could send a
> unicast NS containing an ARO. However, the way I read Section 6.5.5
> in nd-15, a 6lowpan router (6LR) can also send a unicast NS to
> another 6lowpan router. This means that a registered neighbor cache
> entry (NCE) in a 6LR could refer to either a host or another 6LR. So,
> how does a 6LR know that a registered NCE belongs to an attached host
> and it should advertize reachability to this host in the routing
> protocol, such as RPL, it is running?
>
> The proposed flag will solve this problem. A host would set
> "Advertize on behalf" flag when it sends an ARO inside a unicast NS
> message, whereas a 6LR wont.
>
> I was wondering if ND authors could comment on this.

I didn't see anybody else comment, so let me try.

I don't know what assumptions RPL makes in particular, but if we are
talking about a general case of a routing protocol, I don't see why
there would be a need to tell a difference between a host sending an ARO
and a router (which might be initializing and haven't yet enabled
routing and forwarding) sending an ARO.

In both cases I'd assume that the unicast address that is registered is
something that should be reachable, hence it makes sense advertising
reachability to that address.

If this isn't the case, then a routing protocol would typically find out
about its neighboring routers IP addresses, and from that it can decide
to treat those IP addresses differently than the addresses assigned to
hosts.

    Erik
_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www.ietf.org/mailman/listinfo/6lowpan

The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.