IETF Logo Mail Archive

Re: [Roll] [roll] #163 (applicability-home-building): DAO Policy

Yvonne-Anne Pignolet <yvonne-anne.pignolet@ch.abb.com> Thu, 20 November 2014 00:06 UTC

Return-Path: <yvonne-anne.pignolet@ch.abb.com>
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 5CBBC1A1B1B for <roll@ietfa.amsl.com>; Wed, 19 Nov 2014 16:06:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] 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 A17R_bTIfJhz for <roll@ietfa.amsl.com>; Wed, 19 Nov 2014 16:06:47 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0670.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::670]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE53C1A1B18 for <roll@ietf.org>; Wed, 19 Nov 2014 16:06:46 -0800 (PST)
Received: from DB4PR06MB047.eurprd06.prod.outlook.com (10.242.154.154) by DB4PR06MB046.eurprd06.prod.outlook.com (10.242.154.147) with Microsoft SMTP Server (TLS) id 15.1.16.15; Wed, 19 Nov 2014 23:59:56 +0000
Received: from DB4PR06MB047.eurprd06.prod.outlook.com ([169.254.14.158]) by DB4PR06MB047.eurprd06.prod.outlook.com ([169.254.14.158]) with mapi id 15.01.0016.006; Wed, 19 Nov 2014 23:59:56 +0000
From: Yvonne-Anne Pignolet <yvonne-anne.pignolet@ch.abb.com>
To: "consultancy@vanderstok.org" <consultancy@vanderstok.org>, Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] [roll] #163 (applicability-home-building): DAO Policy
Thread-Index: AQHP/TMR4R3EnuuX00ycBs/OP1GkkZxfRsQAgAloULA=
Date: Wed, 19 Nov 2014 23:59:56 +0000
Message-ID: <7d2f04ccff7e4df8b74f14a8b76acf0c@DB4PR06MB047.eurprd06.prod.outlook.com>
References: <071.7c177dda1330be795d5ea4936294a319@trac.tools.ietf.org> <800e9c000d3ee95159be615efb6b4b13@xs4all.nl>
In-Reply-To: <800e9c000d3ee95159be615efb6b4b13@xs4all.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [12.238.14.100]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB046;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB046;
x-forefront-prvs: 04004D94E2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(51704005)(252514010)(189002)(199003)(377424004)(13464003)(66654002)(2501002)(19580395003)(15975445006)(50986999)(97736003)(31966008)(92566001)(86362001)(19580405001)(64706001)(21056001)(2656002)(20776003)(4396001)(54356999)(66066001)(77096003)(106356001)(122556002)(77156002)(101416001)(62966003)(76576001)(40100003)(46102003)(108616004)(105586002)(230783001)(87936001)(99396003)(120916001)(74316001)(107046002)(95666004)(106116001)(33646002)(76176999)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR06MB046; H:DB4PR06MB047.eurprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:0; LANG:en;
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ch.abb.com
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/94WcnqIE_WGyVj2NpPvQq6eDVSE
Cc: "draft-ietf-roll-applicability-home-building@tools.ietf.org" <draft-ietf-roll-applicability-home-building@tools.ietf.org>, "yvonneanne.pignolet@gmail.com" <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: 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: Thu, 20 Nov 2014 00:06:50 -0000

Dear Peter

Thanks for your suggestions on this and the other tickets I opened (#162-166). I agree with your proposed improvements and I am looking forward to the next version :)

Regards
Yvonne-Anne


Yvonne-Anne Pignolet
Dr. Sc. ETH Zürich
ABB Corporate Research
Segelhofstrasse 1K
5400 Baden-Dättwil, Switzerland
Phone: +41 58 586 86 56
Mobile: +41 79 766 10 54
email: yvonne-anne.pignolet@ch.abb.com


-----Original Message-----
From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of peter van der Stok
Sent: Donnerstag, 13. November 2014 16:19
To: roll@ietf.org
Cc: draft-ietf-roll-applicability-home-building@tools.ietf.org; yvonneanne.pignolet@gmail.com
Subject: Re: [Roll] [roll] #163 (applicability-home-building): DAO Policy

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 mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll

v2.23.0 | Report a Bug | By Email