Subject: [Roll] dt-roll-rpl: constraint

From: Mukul Goyal <[email-masked]>
Date: Wed, 1 Jul 2009 10:50:16 -0500 (CDT)

Section 4.2 in the draft defines a "constraint" as follows:

"A constraint is a link or a node characteristic that must be
   satisfied by the computed path..."

This definition excludes the possibility that a routing constraint may be a function of characteristics of multiple (or all) links/nodes in the path. For example, it seems that it may not be possible to allow the following objective function under the given definition of "constraint".

"Find the shortest path (path with lowest cost where the path cost is same as the hop-count) such that the end-to-end reliability of the path is more than 75%."

Thanks
Mukul