Re: [6lowpan] 6lowpan-nd-15 node mobility and default router(s)

Zach Shelby <> Mon, 13 June 2011 08:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0C24311E8082 for <>; Mon, 13 Jun 2011 01:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EAitYNrXd39B for <>; Mon, 13 Jun 2011 01:11:16 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id AB94611E8071 for <>; Mon, 13 Jun 2011 01:11:15 -0700 (PDT)
Received: from [] ([]) (authenticated bits=0) by (8.13.4/8.13.4) with ESMTP id p5D8BBJ2019051 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Jun 2011 11:11:11 +0300
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-367--1067008794; protocol="application/pkcs7-signature"; micalg=sha1
From: Zach Shelby <>
In-Reply-To: <A337AA36B3B96E4D853E6182B2F27AE2CD92D4EC21@NLCLUEXM03.connect1.local>
Date: Mon, 13 Jun 2011 11:11:12 +0300
Message-Id: <>
References: <A337AA36B3B96E4D853E6182B2F27AE2CD92D4EC21@NLCLUEXM03.connect1.local>
To: "Dijk, Esko" <>
X-Mailer: Apple Mail (2.1084)
Cc: "" <>
Subject: Re: [6lowpan] 6lowpan-nd-15 node mobility and default router(s)
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 13 Jun 2011 08:11:17 -0000


On May 23, 2011, at 12:24 PM, Dijk, Esko wrote:

> Dear all,
> A comment on Section 1.3 of 6lowpan-nd-15, last bullet:
> When a node moves away from the registered default router, it SHOULD first de-register by
> sending a registration message with zero lifetime and then
> registers with a new default router that is reachable

This text was meant as an example of how to handle intra-domain mobility when registered with a single default router. You are correct that a host can be registered to multiple default routers (and this is recommended). This text in 1.3 shouldn't have been normative as you point out. The normative text for this was already in Section 5.5, so I will remove this from the assumptions. I added the bit about using a suitably short lifetime to Section 5.5 as that was missing there. 


> - it should probably say “moves away from _a_ registered default router” here, because there may be more default routers? Or otherwise if there is only one that should be made explicit as a special case.
> - If a node has >1 default routers, it could also de-register from one without registering with a new router, or not?
> - why shouldn’t a node register first with a new default router before de-registering with the router it is moving away from? This ensures that the node remains reachable. This works only of course in those cases the new router is already available prior to the move.
> - finally, this text should probably not be under the “1.3 Assumptions” section because it describes normative node behaviour in case of mobility, not only an assumption.
> best regards,
> Esko
> 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.
> _______________________________________________
> 6lowpan mailing list

Zach Shelby, Chief Nerd, Sensinode Ltd.  - My blog "On the Internet of Things" - My book "6LoWPAN: The Wireless Embedded Internet"
Mobile: +358 40 7796297