Re: [Roll] [roll] #163 (applicability-home-building): DAO Policy
peter van der Stok <stokcons@xs4all.nl> Fri, 14 November 2014 00:19 UTC
Return-Path: <stokcons@xs4all.nl>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8FD71A0072 for <roll@ietfa.amsl.com>; Thu, 13 Nov 2014 16:19:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 131vDw10kVsT for <roll@ietfa.amsl.com>; Thu, 13 Nov 2014 16:19:00 -0800 (PST)
Received: from lb2-smtp-cloud6.xs4all.net (lb2-smtp-cloud6.xs4all.net [194.109.24.28]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20D161A006F for <roll@ietf.org>; Thu, 13 Nov 2014 16:18:59 -0800 (PST)
Received: from roundcube.xs4all.nl ([194.109.20.199]) by smtp-cloud6.xs4all.net with ESMTP id FCJy1p00L4Hiz6i01CJyBP; Fri, 14 Nov 2014 01:18:58 +0100
Received: from t2001067c03700160f829bdf226b269cc.wireless.v6.meeting.ietf.org ([2001:67c:370:160:f829:bdf2:26b2:69cc]) by roundcube.xs4all.nl with HTTP (HTTP/1.1 POST); Fri, 14 Nov 2014 01:18:58 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Fri, 14 Nov 2014 01:18:58 +0100
From: peter van der Stok <stokcons@xs4all.nl>
To: roll@ietf.org
Organization: vanderstok consultancy
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <071.7c177dda1330be795d5ea4936294a319@trac.tools.ietf.org>
References: <071.7c177dda1330be795d5ea4936294a319@trac.tools.ietf.org>
Message-ID: <800e9c000d3ee95159be615efb6b4b13@xs4all.nl>
X-Sender: stokcons@xs4all.nl (oVATWIulgzoRte3CPCRoQ0QuqpamtKLV)
User-Agent: XS4ALL Webmail
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/52P-ACPtHEndI_4IM1NDT6OPvC8
Cc: draft-ietf-roll-applicability-home-building@tools.ietf.org, yvonneanne.pignolet@gmail.com
Subject: Re: [Roll] [roll] #163 (applicability-home-building): DAO Policy
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: consultancy@vanderstok.org, Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 14 Nov 2014 00:19:01 -0000
HI Yvonne, after some discussions we propose the following text, that you will easily recognize. Nodes send DAO messages to establish downward paths from the root to themselves. DAO messages are not acknowledged in networks composed of battery operated field devices in order to minimize the power consumption overhead associated with path discovery. The DAO messages build up a source route because the nodes are recommended to be in non-storing mode. If devices in LLNs participate in multiple RPL instances and DODAGs, it is highly recommended that both the RPLInstance ID and the DODAGID be included in the DAO. many thanks, Peter roll issue tracker schreef op 2014-11-10 23:09: > #163: DAO Policy > > Yvonne-Anne Pignolet: > In 4.1.3. The authors consider DAO policy to be > out of scope. However, if basic RPL is applicable for home and > building automation scenarios then due to P2MP traffic from roots > DAOs are required. As in the industrial applicability statement I thus > recommend a paragraph such as "Nodes send DAO messages to establish > downward paths from the root to themselves. DAO messages are not > acknowledged in networks composed of battery operated field devices in > order to minimize the power consumption overhead associated with path > discovery. If devices in LLNs participate in multiple RPL instances > and DODAGs, it is highly recommended that both the RPLInstance ID and > the DODAGID be included in the DAO." If the mailing list consensus is > that P2P RPL is to be used only, then this Section should state that > DAO messages are not sent in this case. In addition a comment on > P2P-DRO Acknowledgement (P2P-DRO-ACK) would be helpful > > Peter van der Stok: > Some text to motivate the out of scope of DAO policy can be added. > For the multiple RPL instances, I prefer to include a reference to > other > texts.
- [Roll] [roll] #163 (applicability-home-building):… roll issue tracker
- Re: [Roll] [roll] #163 (applicability-home-buildi… peter van der Stok
- Re: [Roll] [roll] #163 (applicability-home-buildi… Yvonne-Anne Pignolet
- Re: [Roll] [roll] #163 (applicability-home-buildi… roll issue tracker
- Re: [Roll] [roll] #163 (applicability-home-buildi… roll issue tracker