Re: [Roll] RA-DIOs and next-door destinations

Jonathan Hui <jhui@archrock.com> Mon, 03 August 2009 19:37 UTC

Return-Path: <jhui@archrock.com>
X-Original-To: roll@core3.amsl.com
Delivered-To: roll@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E4923A6EA2 for <roll@core3.amsl.com>; Mon, 3 Aug 2009 12:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.025
X-Spam-Level:
X-Spam-Status: No, score=-2.025 tagged_above=-999 required=5 tests=[AWL=0.574, BAYES_00=-2.599]
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 iCSa86mALTBf for <roll@core3.amsl.com>; Mon, 3 Aug 2009 12:37:36 -0700 (PDT)
Received: from mail.sf.archrock.com (mail.sf.archrock.com [216.121.16.71]) by core3.amsl.com (Postfix) with ESMTP id 3EA2C3A6E25 for <roll@ietf.org>; Mon, 3 Aug 2009 12:37:35 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sf.archrock.com (Postfix) with ESMTP id 46511AF879; Mon, 3 Aug 2009 12:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
Received: from mail.sf.archrock.com ([127.0.0.1]) by localhost (mail.sf.archrock.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NT6mN720Nw8y; Mon, 3 Aug 2009 12:37:32 -0700 (PDT)
Received: from [192.168.7.71] (69-12-164-133.sfo.archrock.com [69.12.164.133]) by mail.sf.archrock.com (Postfix) with ESMTP id 97EB7AF859; Mon, 3 Aug 2009 12:37:32 -0700 (PDT)
Message-Id: <B8949F83-E028-4CAE-B5E4-E74EC5531F66@archrock.com>
From: Jonathan Hui <jhui@archrock.com>
To: Richard Kelsey <richard.kelsey@ember.com>
In-Reply-To: <87prbc5231.fsf@kelsey-ws.hq.ember.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 03 Aug 2009 12:37:31 -0700
References: <87prbc5231.fsf@kelsey-ws.hq.ember.com>
X-Mailer: Apple Mail (2.935.3)
Cc: roll@ietf.org
Subject: Re: [Roll] RA-DIOs and next-door destinations
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Aug 2009 19:37:37 -0000

Hi Richard,

On Aug 3, 2009, at 8:50 AM, Richard Kelsey wrote:
> In the section on RA-DIO reception, draft-dt-roll-rpl-01
> says that a RA-DIO from a neighbor that is not a potential
> parent or a sibling should be ignored.  Is it permissable
> to remember the neighbor in order to route messages to
> it directly?  In other words, can a packet whose
> destination is a neighbor with a greater depth be sent
> directly to that neighbor?


Let me speak to your comment directly, rather than the draft.

I don't see any problem using the RA-DIO to figure out what neighbors  
are around you. One issue is that if the RA-DIO source address is a  
link-local address, it may not be so useful if you're trying to talk  
to that node using its global address. What is more useful is to allow  
including some kind of DAO in the same RA so that you know what  
addresses (other than the source address) are assigned to that node's  
interface.

--
Jonathan Hui