Scribd Logo
Upload

Welcome to Scribd!

  • 58 views

    RPL Message DIO: Pv6 Routing Protocol For Low-Power and Lossy Networks Dodag Information Object

    Uploaded by

    Niguss Mehari Gezahegn
    The RPL message DIO is used to establish and modify the DODAG, which is the routing structure in RPL networks. The DIO contains information about the RPL instance, DODAG version number, DODAG ID, and other details. It is sent by nodes to advertise their rank and other parameters. The DAG Metric Container option in the DIO conveys information about link metrics and constraints using Routing Metric/Constraint Objects.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    RPL Message DIO: Pv6 Routing Protocol For Low-Power and Lossy Networks Dodag Information Object

    Uploaded by

    Niguss Mehari Gezahegn
    58 views2 pages
    The RPL message DIO is used to establish and modify the DODAG, which is the routing structure in RPL networks. The DIO contains information about the RPL instance, DODAG version number, DODAG ID, and other details. It is sent by nodes to advertise their rank and other parameters. The DAG Metric Container option in the DIO conveys information about link metrics and constraints using Routing Metric/Constraint Objects.

    Original Title

    AnatolBadachResearchGateRPLMessageDIO

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The RPL message DIO is used to establish and modify the DODAG, which is the routing structure in RPL networks. The DIO contains information about the RPL instance, DODAG version number, DODAG ID, and other details. It is sent by nodes to advertise their rank and other parameters. The DAG Metric Container option in the DIO conveys information about link metrics and constraints using Routing Metric/Constraint Objects.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    58 views2 pages

    RPL Message DIO: Pv6 Routing Protocol For Low-Power and Lossy Networks Dodag Information Object

    Uploaded by

    Niguss Mehari Gezahegn
    The RPL message DIO is used to establish and modify the DODAG, which is the routing structure in RPL networks. The DIO contains information about the RPL instance, DODAG version number, DODAG ID, and other details. It is sent by nodes to advertise their rank and other parameters. The DAG Metric Container option in the DIO conveys information about link metrics and constraints using Routing Metric/Constraint Objects.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 2

    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.

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy