[6lowpan] -nd-15: Battery host support seems to be incomplete

"Anders Brandt" <abr@sdesigns.dk> Fri, 25 February 2011 10:41 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 C74893A694D for <6lowpan@core3.amsl.com>; Fri, 25 Feb 2011 02:41:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 ShNpAplSeyBl for <6lowpan@core3.amsl.com>; Fri, 25 Feb 2011 02:41:20 -0800 (PST)
Received: from mail.zen-sys.com (mail.zen-sys.com [195.215.56.170]) by core3.amsl.com (Postfix) with ESMTP id 8A26D3A67D4 for <6lowpan@ietf.org>; Fri, 25 Feb 2011 02:41:20 -0800 (PST)
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 25 Feb 2011 11:42:12 +0100
Message-ID: <6D9687E95918C04A8B30A7D6DA805A3E01CCD782@zensys17.zensys.local>
In-Reply-To: <79D3D27D-F813-4773-8289-F973AB01F743@tzi.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: -nd-15: Battery host support seems to be incomplete
Thread-Index: AcvOu2LY74smpHOQS66nfu06H5x80wGGfkRg
References: <79D3D27D-F813-4773-8289-F973AB01F743@tzi.org>
From: Anders Brandt <abr@sdesigns.dk>
To: zach@sensinode.com, 6lowpan <6lowpan@ietf.org>
Subject: [6lowpan] -nd-15: Battery host support seems to be incomplete
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: Fri, 25 Feb 2011 10:41:21 -0000

Having read the doc carefully, I have a comment:

Section 5.8 addresses sleeping nodes.
While I agree with the text in this section it seems to me that the
description does not cover an important battery host category:

* The frequently listening node (FLN)

In a non-storing routing environment like the one we are specifying in
RPL-P2P in the ROLL WG, we have the option of issuing a reactive
discovery request when needing to get in touch with a host on short
notice. This is a major requirement for real users in home control and
building automation.

The abovementioned FLN is a battery powered
host that can be reached with semi-low latency. The typical use is
installations where wires would be hard to install without affecting
the architectural appearance. Examples include wireless window drape
controllers and electronic door locks.
802.15.4 and Z-Wave have different link-layer solutions for this but
the user experience is the same: Reaction within a second or less.

If an originating node (keyfob or remote control) has lost all its
working routes to a FLN, it must re-discover a source route to the FLN.
But the FLN is sleeping.
I would like a flag in the ARO: "advertise on behalf".
If set, a default router may use the neighbor information to respond
to discovery requests. The actual response format obviously depends
on the actual routing protocol. RPL-P2P is just my actual example.
Thus, how the default router uses the information is out of scope of
the ND spec.

Thanks,
  Anders

-----Original Message-----
From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On
Behalf Of Carsten Bormann
Sent: 17. februar 2011 16:58
To: 6lowpan
Subject: [6lowpan] Working Group Last call for draft-ietf-6lowpan-nd-15

In September/October, we had the first WGLC on 6LoWPAN-ND, which
resulted in a number of detailed comments and two resulting
fine-tuning iterations of the draft.

draft-ietf-6lowpan-nd-15.txt has been out for two months now.
I understand it has taken part in several interops with multiple
implementations in this period; no issues came up.

We now start the Working Group Last Call on:

   http://tools.ietf.org/html/draft-ietf-6lowpan-nd-15

The document is planned to be submitted by this Working Group to the
IESG for publication as a Standards-Track Document.

This is a two-week Working-Group Last-Call, ending on Thursday,
2011-03-03 at 2359 UTC.

Please review the changes to the document carefully once more, and
send your comments to the 6lowpan list.  Please also do indicate to
the list if you are all-OK with the document.

Gruesse, Carsten

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