Re: [Roll] [roll] #92: Is it possible to make P2P-RPL independent of trickle algorithm

C Chauvenet <c.chauvenet@watteco.com> Thu, 05 April 2012 13:33 UTC

Return-Path: <c.chauvenet@watteco.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01DB821F86C6 for <roll@ietfa.amsl.com>; Thu, 5 Apr 2012 06:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z+xl69ReF9Jd for <roll@ietfa.amsl.com>; Thu, 5 Apr 2012 06:33:32 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id 4C53C21F86C4 for <roll@ietf.org>; Thu, 5 Apr 2012 06:33:32 -0700 (PDT)
Received: from mail93-va3-R.bigfish.com (10.7.14.253) by VA3EHSOBE003.bigfish.com (10.7.40.23) with Microsoft SMTP Server id 14.1.225.23; Thu, 5 Apr 2012 13:33:31 +0000
Received: from mail93-va3 (localhost [127.0.0.1]) by mail93-va3-R.bigfish.com (Postfix) with ESMTP id 4C82F1A0656; Thu, 5 Apr 2012 13:33:31 +0000 (UTC)
X-SpamScore: -70
X-BigFish: VPS-70(zzc89bh15caKJzz1202hzz1033IL8275bh8275dhz2dh2a8h668h839h93fhd25h)
X-Forefront-Antispam-Report: CIP:157.56.248.181; KIP:(null); UIP:(null); IPV:NLI; H:AMXPRD0510HT002.eurprd05.prod.outlook.com; RD:none; EFVD:NLI
Received: from mail93-va3 (localhost.localdomain [127.0.0.1]) by mail93-va3 (MessageSwitch) id 1333632809110535_31795; Thu, 5 Apr 2012 13:33:29 +0000 (UTC)
Received: from VA3EHSMHS030.bigfish.com (unknown [10.7.14.237]) by mail93-va3.bigfish.com (Postfix) with ESMTP id EB49E1C0155; Thu, 5 Apr 2012 13:33:28 +0000 (UTC)
Received: from AMXPRD0510HT002.eurprd05.prod.outlook.com (157.56.248.181) by VA3EHSMHS030.bigfish.com (10.7.99.40) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 5 Apr 2012 13:33:26 +0000
Received: from AMXPRD0510MB390.eurprd05.prod.outlook.com ([169.254.3.137]) by AMXPRD0510HT002.eurprd05.prod.outlook.com ([10.255.57.37]) with mapi id 14.16.0135.002; Thu, 5 Apr 2012 13:33:15 +0000
From: C Chauvenet <c.chauvenet@watteco.com>
To: "roll@ietf.org" <roll@ietf.org>, "mukul@UWM.EDU" <mukul@UWM.EDU>, "jpv@cisco.com" <jpv@cisco.com>
Thread-Topic: [Roll] [roll] #92: Is it possible to make P2P-RPL independent of trickle algorithm
Thread-Index: AQHNExtfOwbjn/lazkWu39jVRXfkapaMOt4A
Date: Thu, 05 Apr 2012 13:33:14 +0000
Message-ID: <97B69B30E0EF244B940B65EA541E3F2D0221638D@AMXPRD0510MB390.eurprd05.prod.outlook.com>
References: <055.4f67aded0ee3d83f8b18258686aba080@trac.tools.ietf.org>
In-Reply-To: <055.4f67aded0ee3d83f8b18258686aba080@trac.tools.ietf.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.3.4.7]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: watteco.com
Subject: Re: [Roll] [roll] #92: Is it possible to make P2P-RPL independent of trickle algorithm
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 05 Apr 2012 13:33:33 -0000

See inline.

-----Message d'origine-----
De : roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] De la part de roll issue tracker
Envoyé : jeudi 5 avril 2012 13:00
À : mukul@UWM.EDU; jpv@cisco.com
Cc : roll@ietf.org
Objet : [Roll] [roll] #92: Is it possible to make P2P-RPL independent of trickle algorithm

#92: Is it possible to make P2P-RPL independent of trickle algorithm

 Discussion:

 [Cedric]
 Another point that has been discussed today during the ROLL meeting, is  that some people may find other mechanisms than trickle more efficient to  flood the RDO.
 Could we let the door opened to other flooding optimization mechanism, or  explicitly say that the trickle mechanism MUST be used ?

 [Mukul]
 I think inherent dependence on the trickle mechanism is apparent because  of the fact that the route discovery takes place by forming a temporary  DAG. DAG creation (or DIO generation) depends on trickle algorithm. So,  P2P-RPL also depends on trickle algorithm. P2P-RPL being an extension of  core RPL, I dont think there is a way to separate P2P-RPL from trickle  algorithm.

[Cedric2]
Fine. If this is needed for RPL compliancy, then I agree.

-- 
-----------------------------------+---------------------
 Reporter:  jpv@…                  |      Owner:  mukul@…
     Type:  defect                 |     Status:  new
 Priority:  major                  |  Milestone:
Component:  p2p-rpl                |    Version:
 Severity:  Submitted WG Document  |   Keywords:
-----------------------------------+---------------------

Ticket URL: <http://trac.tools.ietf.org/wg/roll/trac/ticket/92>
roll <http://tools.ietf.org/wg/roll/>

_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll