[6lowpan] How to find the mailbox? (related to "Advertize on Behalf")

"Anders Brandt" <abr@sdesigns.dk> Wed, 30 March 2011 06:06 UTC

Return-Path: <abr@sdesigns.dk>
X-Original-To: 6lowpan@core3.amsl.com
Delivered-To: 6lowpan@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D47FB3A67F8 for <6lowpan@core3.amsl.com>; Tue, 29 Mar 2011 23:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.754
X-Spam-Level:
X-Spam-Status: No, score=-1.754 tagged_above=-999 required=5 tests=[AWL=-0.552, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lCFKkWj3am7R for <6lowpan@core3.amsl.com>; Tue, 29 Mar 2011 23:06:41 -0700 (PDT)
Received: from mail.zen-sys.com (mail.zen-sys.com [195.215.56.170]) by core3.amsl.com (Postfix) with ESMTP id 3F5C83A6A8C for <6lowpan@ietf.org>; Tue, 29 Mar 2011 23:06:41 -0700 (PDT)
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBEEA0.DDD140EB"
Date: Wed, 30 Mar 2011 08:08:19 +0200
Message-ID: <6D9687E95918C04A8B30A7D6DA805A3E01AD48A2@zensys17.zensys.local>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: How to find the mailbox? (related to "Advertize on Behalf")
Thread-Index: AcvudA9GkYXcTZpZT6OKqY9tBiTn2wAKzz2/
References: <504410488.1444839.1301446046572.JavaMail.root@mail02.pantherlink.uwm.edu>
From: Anders Brandt <abr@sdesigns.dk>
To: Mukul Goyal <mukul@uwm.edu>, Carsten Bormann <cabo@tzi.org>, zach@sensinode.com
Cc: 6lowpan <6lowpan@ietf.org>
Subject: [6lowpan] How to find the mailbox? (related to "Advertize on Behalf")
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 06:06:43 -0000

OK, so now I can send this "Advertize on Behalf" flag.
 
As mentioned yesterday, there is a distinction between Frequently Listening (a.k.a duty cycled nodes) and
what I call call-back nodes, i.e. nodes that depend on a router holding a mailbox for that node.
Whether that mailbox feature is provided by any router, a few specialiezed routers or the border router
is a network implementation decision.
But how is that information conveyed to the sleeping node?
 
In the RA? 
By asking the default router with some new message?
Whereever this mailbox feature is offered in the network, this is where I will be sending 
my "Advertize on Behalf" flag if I am a call-back node.
 
Forgive me if this is obvious. I think I am getting close to a "detail overload" ;-)
 
Thanks,
  Anders

________________________________

Fra: 6lowpan-bounces@ietf.org på vegne af Mukul Goyal
Sendt: ti 29-03-2011 18:47
Til: Carsten Bormann
Cc: 6lowpan
Emne: Re: [6lowpan] "Advertize on Behalf" flag in ARO



Hi Carsten

>Hosts don't take part in routing protocols

I agree absolutely.

>The only source of information about reachability and network configuration a host has is ND (and DHCP for some of the latter, if present).

I agree. That's why I think 6lowpan ND should provide a mechanism to clearly identify a registered neighbor as a 6lowpan host or a 6lowpan router.

Thanks
Mukul

----- Original Message -----
From: "Carsten Bormann" <cabo@tzi.org>
To: "Esko Dijk" <esko.dijk@philips.com>
Cc: "Erik Nordmark" <nordmark@acm.org>, "Mukul Goyal" <mukul@uwm.edu>, "6lowpan" <6lowpan@ietf.org>
Sent: Tuesday, March 29, 2011 8:14:34 AM
Subject: Re: [6lowpan] "Advertize on Behalf" flag in ARO

On Mar 29, 2011, at 14:55, Dijk, Esko wrote:

> RPL reachability is indeed advertised to both 6LR/6LNs, the only distinction is that a 6LN (host) would operate as a RPL leaf node

Hosts don't take part in routing protocols, so I don't understand this sequence.
The only source of information about reachability and network configuration a host has is ND (and DHCP for some of the latter, if present).

Gruesse, Carsten

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