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

"Dijk, Esko" <esko.dijk@philips.com> Mon, 23 May 2011 09:40 UTC

Return-Path: <esko.dijk@philips.com>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB32FE076E for <6lowpan@ietfa.amsl.com>; Mon, 23 May 2011 02:40:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level:
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gX8C5JaY1Tea for <6lowpan@ietfa.amsl.com>; Mon, 23 May 2011 02:40:00 -0700 (PDT)
Received: from VA3EHSOBE005.bigfish.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id 510D4E0774 for <6lowpan@ietf.org>; Mon, 23 May 2011 02:40:00 -0700 (PDT)
Received: from mail165-va3-R.bigfish.com (10.7.14.239) by VA3EHSOBE005.bigfish.com (10.7.40.25) with Microsoft SMTP Server id 14.1.225.22; Mon, 23 May 2011 09:24:56 +0000
Received: from mail165-va3 (localhost.localdomain [127.0.0.1]) by mail165-va3-R.bigfish.com (Postfix) with ESMTP id 1763C1370971 for <6lowpan@ietf.org>; Mon, 23 May 2011 09:24:56 +0000 (UTC)
X-SpamScore: -13
X-BigFish: VPS-13(zz217bL15d6O9251Jzz1202hzz8275bh8275dhz2dh2a8h668h839h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: CIP:168.87.56.20; KIP:(null); UIP:(null); IPVD:NLI; H:smtpx.philips.com; RD:smtpx.philips.com; EFVD:NLI
Received: from mail165-va3 (localhost.localdomain [127.0.0.1]) by mail165-va3 (MessageSwitch) id 1306142695698356_13663; Mon, 23 May 2011 09:24:55 +0000 (UTC)
Received: from VA3EHSMHS015.bigfish.com (unknown [10.7.14.251]) by mail165-va3.bigfish.com (Postfix) with ESMTP id A226F1198054 for <6lowpan@ietf.org>; Mon, 23 May 2011 09:24:55 +0000 (UTC)
Received: from smtpx.philips.com (168.87.56.20) by VA3EHSMHS015.bigfish.com (10.7.99.25) with Microsoft SMTP Server (TLS) id 14.1.225.22; Mon, 23 May 2011 09:24:54 +0000
Received: from NLHILEXH02.connect1.local (172.16.153.92) by connect1.philips.com (172.16.156.160) with Microsoft SMTP Server (TLS) id 8.3.106.1; Mon, 23 May 2011 11:24:32 +0200
Received: from NLCLUEXM03.connect1.local ([172.16.153.29]) by NLHILEXH02.connect1.local ([172.16.153.92]) with mapi; Mon, 23 May 2011 11:24:17 +0200
From: "Dijk, Esko" <esko.dijk@philips.com>
To: "6lowpan@ietf.org" <6lowpan@ietf.org>
Date: Mon, 23 May 2011 11:24:32 +0200
Thread-Topic: 6lowpan-nd-15 node mobility and default router(s)
Thread-Index: AcwZKzmpKZVlzeP6RTeW1EGGGNJaVg==
Message-ID: <A337AA36B3B96E4D853E6182B2F27AE2CD92D4EC21@NLCLUEXM03.connect1.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A337AA36B3B96E4D853E6182B2F27AE2CD92D4EC21NLCLUEXM03con_"
MIME-Version: 1.0
X-OriginatorOrg: philips.com
Subject: [6lowpan] 6lowpan-nd-15 node mobility and default router(s)
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 23 May 2011 09:40:02 -0000

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

- 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.