Re: [Roll] interest in mixed network topology

"Mani, Mehdi" <Mehdi.Mani@itron.com> Tue, 18 February 2014 10:55 UTC

Return-Path: <Mehdi.Mani@itron.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 02B011A00DD for <roll@ietfa.amsl.com>; Tue, 18 Feb 2014 02:55:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_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 w4vPN3Pawr9X for <roll@ietfa.amsl.com>; Tue, 18 Feb 2014 02:55:40 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0210.outbound.protection.outlook.com [207.46.163.210]) by ietfa.amsl.com (Postfix) with ESMTP id BC0431A032F for <roll@ietf.org>; Tue, 18 Feb 2014 02:55:39 -0800 (PST)
Received: from CO2PR04MB715.namprd04.prod.outlook.com (10.141.229.144) by CO2PR04MB714.namprd04.prod.outlook.com (10.141.229.142) with Microsoft SMTP Server (TLS) id 15.0.878.16; Tue, 18 Feb 2014 10:55:35 +0000
Received: from CO2PR04MB715.namprd04.prod.outlook.com ([10.141.229.144]) by CO2PR04MB715.namprd04.prod.outlook.com ([10.141.229.144]) with mapi id 15.00.0878.008; Tue, 18 Feb 2014 10:55:35 +0000
From: "Mani, Mehdi" <Mehdi.Mani@itron.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>, "draft-ko-roll-mix-network-pathology@tools.ietf.org" <draft-ko-roll-mix-network-pathology@tools.ietf.org>
Thread-Topic: [Roll] interest in mixed network topology
Thread-Index: AQHPJ2DujgTP/DUAtkWf56SM0RYhnZq639rw
Date: Tue, 18 Feb 2014 10:55:34 +0000
Message-ID: <2283739730e54ff39ae193773f2dc48c@CO2PR04MB715.namprd04.prod.outlook.com>
References: <30140.1392147480@sandelman.ca>
In-Reply-To: <30140.1392147480@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [109.2.132.3]
x-forefront-prvs: 0126A32F74
x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(13464003)(199002)(189002)(83072002)(85852003)(63696002)(54316002)(85306002)(51856001)(69226001)(54356001)(76482001)(81542001)(53806001)(81342001)(87266001)(50986001)(47976001)(87936001)(2656002)(90146001)(80022001)(56816005)(66066001)(74706001)(65816001)(74876001)(74366001)(33646001)(76576001)(76796001)(76786001)(74316001)(80976001)(19580405001)(19580395003)(83322001)(77982001)(95666001)(74502001)(94316002)(86362001)(93136001)(93516002)(81686001)(47446002)(56776001)(4396001)(47736001)(49866001)(95416001)(46102001)(92566001)(74662001)(31966008)(81816001)(94946001)(59766001)(79102001)(15202345003)(15975445006)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:CO2PR04MB714; H:CO2PR04MB715.namprd04.prod.outlook.com; CLIP:109.2.132.3; FPR:BC40F07D.AE33D7C9.B3C3BC63.44E39E69.20362; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: itron.com
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/YwotN2aTFBpFLaTtzhHPXVIahJ8
Cc: Ines Robles <mariainesrobles@googlemail.com>
Subject: Re: [Roll] interest in mixed network topology
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: Tue, 18 Feb 2014 10:55:45 -0000

I believe that it is an interesting subject to peruse. There are certainly some usecases for storing mode and mixed storing/non-storing modes. 
-Mehdi 

-----Original Message-----
From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of Michael Richardson
Sent: mardi 11 février 2014 20:38
To: draft-ko-roll-mix-network-pathology@tools.ietf.org
Cc: roll@ietf.org; Ines Robles
Subject: [Roll] interest in mixed network topology


draft-ko-roll-mix-network-pathology, which expires on Friday from:
   http://datatracker.ietf.org/doc/draft-ko-roll-mix-network-pathology/

describes a way to do mixed storing/non-storing topologies.   My first
question is to the authors:
  1) do you continue to pursue this work?  What is your intent for this
     document?
  2) will you update with any new results?

To the WG:
  3) is there interest in persuing this line of investigation at this time?
     We had previously put investigation of this on hold until we figured out
     a number of other things.   Please read this document, and consider
     whether this document would help advance this, or if we need one or a
     number of approaches.
     Do we have a good enough problem statement?

If we recharter in Toronto, I would expect that solving this problem will among the most important reasons to re-charter.

(again, please recall that absence of comments implies disinterest. +1 are welcome)


Abstract

   The RPL specification allows nodes running with storing or non-
   storing modes to operate in the same network.  We describe how such a
   mix can result in network partitioning even when there are plenty of
   physical links available in the network.  The partitioning affects
   both upwards (nodes to root) and downwards (root to leaf) traffic.
   This routing pathology stems from a recommendation made in the RPL
   specification forcing nodes with different modes of operation to join
   the RPL network as leaf nodes only.  We propose a solution that
   modifies RPL by mandating that all the nodes parse and interpret
   source routing headers and storing mode nodes to sometimes act like a
   non-storing mode root by attaching source routing headers.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/