See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/326960645

RPL Message DIO

Poster · August 2018

CITATIONS READS

0 911

1 author:

Anatol Badach
University of Applied Sciences Fulda
215 PUBLICATIONS   61 CITATIONS   

SEE PROFILE

Some of the authors of this publication are also working on these related projects:

Voice over IP View project

Internet of Things – Technologies, Protocols and Applications View project

All content following this page was uploaded by Anatol Badach on 10 August 2018.

The user has requested enhancement of the downloaded file.

 RPL Message DIO
Anatol Badach

The RPL (IPv6 Routing Protocol for Low-Power and Lossy Networks) message DIO (DODAG
Information Object) is fundamental in setting up and modifying the DODAG (Destination Oriented
Directed Acyclic Graph). The construction of a new DODAG is always initiated from the root and
then continued from the intermediate node to the end node. In addition, each node with the DIO
periodically signals its status to all other nodes that it can reach directly. The DIO is always the first
protocol message that each node sends to all its neighboring nodes immediately after startup.
 Anatol Badach: RPL Message DIO July 2018

Each message DIO must contain the information that can be used to uniquely identify the current
version of DODAG that is to be rebuilt. This information includes:
• RPLInstanceID – the identification (ID) of the RPL instance. It describes the affiliation of the
sender to an RPL instance.
• (DODAG) Version Number – the numeric value continuously incremented by the root to
determine the current DODAG Version.
• DODAG ID – the identification of a DODAG.
To allow flexible logical structures in the form of several DODAGs in LLNs, the current and LLN-
wide unique DODAG Version is uniquely determined by tuple (RPL instance ID, DODAG ID,
DODAG Version Number).

Further details in the DIO are to be interpreted as follows:

• Rank
With this indication in DIO, each node informs all its neighboring nodes about its rank, that is,
about its logical distance to the root node. This is fundamental in determining the route.
• G – Grounded
A DODAG can be either grounded or floating on the Internet. G = 1 indicates that the DODAG is
grounded and G = 0 indicates that the DODAG is floating. A grounded DODAG provides access to
the Internet. A floating DODAG, on the other hand, only allows the verification of connectivity
(e.g. in a test phase).
• MOP – Mode of Operation
The operating mode of the RPL is entered here.
• Prf – DODAG Preference
Here, the root can assign a preference to a new DODAG to be set up.
• DTSN – Destination Advertisement Trigger Sequence Number
This information is used to maintain so-called downward routes.
• Flags
The reserved space for any future flags.

Option: DAG Metric Container

In the DIO message, the DAG Metric Container option is of high relevance. This option, specified
in RFC 6551, is used to convey information about the metrics of links and the various types of links
that apply to links in the form of Routing Metric/Constraint Objects (Routing M/C Objects).

In a DAG Metric Container several Routing M/C Objects can be transported. Such an object contains
the specification of a link metric or the constraints associated with the link. If different metrics have
been assigned to a link and/or multiple constraints have to be met, a Routing M/C Object is formed
and then transmitted in a DAG Metric Container. These individual Routing M/C Object of a link must
then be assigned priorities according to which they are used in the route selection. Each Routing M/C
Object therefore has a priority, which is entered as Precedence (Prec) in the Metric Container.

Using the indicators P, C, O and R, it is possible for the receiver of the Routing M/C Object to
determine whether it is a Routing Metric or a Routing Constraint and how the details are to be
interpreted.

View publication stats