Re: [Roll] Issue with multiple instances in RPL Thu, 04 September 2014 03:55 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 9D7C91A6F68 for <>; Wed, 3 Sep 2014 20:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.575
X-Spam-Status: No, score=-1.575 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RELAY_IS_203=0.994, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PefEPyRZjWVO for <>; Wed, 3 Sep 2014 20:55:08 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D5EE01A6F76 for <>; Wed, 3 Sep 2014 20:55:06 -0700 (PDT)
Received: from ( []) by (8.13.1/8.13.1) with ESMTP id s843spIA000741 for <>; Thu, 4 Sep 2014 09:24:51 +0530
Received: from (localhost []) by (8.13.6/8.13.6/SuSE Linux 0.8) with ESMTP id s843rGmq027941 for <>; Thu, 4 Sep 2014 09:23:16 +0530
Received: (from wwwrun@localhost) by (8.13.6/8.13.6/Submit) id s843rGKg027939; Thu, 4 Sep 2014 09:23:16 +0530
Received: from (proxying for (SquirrelMail authenticated user Anand) by with HTTP; Thu, 4 Sep 2014 09:23:16 +0530
Message-ID: <>
In-Reply-To: <>
References: <>
Date: Thu, 4 Sep 2014 09:23:16 +0530
To: "Routing Over Low power and Lossy networks" <>
User-Agent: SquirrelMail/1.4.19
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-IISc-MailScanner-Information: Please contact the ISP for more information
X-IISc-MailScanner: Found to be clean
X-IISc-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-0.799, required 6.5, ALL_TRUSTED -1.00, BAYES_00 -1.90, FSL_RCVD_USER 0.00, NO_REAL_NAME 1.00, _LOCAL_RCVD_THRU_RPROXY 1.10)
Subject: Re: [Roll] Issue with multiple instances in RPL
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <>
List-Id: Routing Over Low power and Lossy networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 04 Sep 2014 03:55:09 -0000

Hi Anuj,

Just curious to know, is it difficult to tweak IP layer code to realise
what you mentioned ? I know a typical IP implementation is what you are
referring to. These days with so much happening in the forwarding path in
the form of policy based routing, one can have an internal mechanism to
achieve what you are saying, no ?  Hope my understanding of your concern
is right.


> Hi,
> We are working on an application that would require the use of multiple
> RPL instances. For implementation purposes we adopted Contiki 2.7, since
> it has at least rudimentary support for multiple DODAGs and multiple
> instances already built-in. However, during our development of the
> multi-instance code in Contiki we discovered a problem that seems to stem
> from RFC 6550 itself.
> The RFC 6550 states that during preferred parent discovery "nodes that
> decide to join a DODAG MUST provision at least one DODAG parent as a
> default route for the associated instance." Even though the RFC states
> that the default route should be for the associated instance, while
> building a routing table in the IP layer there is no ability to select
> multiple default routes. Furthermore, an IP routing table does not allow
> for marking which default route applies to which instance. In fact, since
> IP packets do not carry any information as to which instance originated
> the packet, even special markup associated with IP routes cannot be used
> for making an appropriate routing decision.
> This essentially means that when a node is part of two instances, it can
> only have one default route, which either belongs to DODAG from instance
> A, or DODAG from instance B. Consequentially, whichever is the currently
> the "active" instance, i.e. the DODAG for which the last DIO message was
> received, occupies the default route within the IP routing table. Another
> side effect of this is that each time a DIO message is received from the
> other instance, the default route changes. Of course, this leads to
> non-decisive routing of packets; the main problem being that instance A
> might try to route packets for instance B and vice-versa, while this
> should not occur.
> Since the IP routing table does not support the ability to have two
> default routes, a simple solution appears to be that instead of
> configuring a default route upon receiving a DIO message, the node should
> just add a simple routing table entry for the prefixes announced in the
> message. This should solve the problem with multiple default routes, and
> even the constantly changing default route issue.
> The only shortcoming of not having a default route is that packets that
> are intended for being routed outside of the RPL instance(s) will not find
> a valid route. This could be solved by the intended border router also
> advertising a prefix for all routes. This should work in most applications
> since it would seem unlikely that there is more than one Internet gateway
> in an application.
> Based on the presented information, what do the authors of RFC 6550
> recommend be done with default routes, in case of multiple RPL instances?
> Furthermore, a clarification might be needed for the language in the RFC,
> so that implementations of RPL adopt the appropriate solution.
> Warm regards,
> Anuj Sehgal
> _______________________________________________
> Roll mailing list
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.

This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.