Re: [Roll] I-D Action: draft-ietf-roll-dao-projection-07.txt

rabi narayan sahoo <> Mon, 04 November 2019 06:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 46EFD1200C5 for <>; Sun, 3 Nov 2019 22:54:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nGxqJOvBO6px for <>; Sun, 3 Nov 2019 22:54:20 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8DD1112006E for <>; Sun, 3 Nov 2019 22:54:20 -0800 (PST)
Received: by with SMTP id m5so4682382ilq.0 for <>; Sun, 03 Nov 2019 22:54:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=JVhfUEuDmi7QZjyONzxiuHZnvTJXcKP2Vn29n5jdNk8=; b=ohcIan2JKmhrBKeC7iutnZQaHiXGgf/xAgQXrz8X6SuY2SfnH6Tg7e2qLiyf+H6gxM FTpk3BaDpKIoDKOBw+BhRpB2bNw3/la06A5S1SZJyJlX0eriA7WPYkg/f9cb8n0xzbP8 xDH+2kxVg7zACbCrspzQ+psrYxMBJS91rYsDKFZT6AsaOId9FaG7MaZj1wx9WImjR7ZL YWbLhnD5k/LoOin35VYs8k3w4YwSTC6jG3oxSB0dOuFrqI0adlnvV4J0jxg7yjtCamkX Hzv95aJ9/AD2UZF8QoxafxoPb/3tfBvSNplxOHw6IdDj88aKb98xlY1VNTyAU5RqOWTN P2RA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=JVhfUEuDmi7QZjyONzxiuHZnvTJXcKP2Vn29n5jdNk8=; b=kU0+RvFvcyKYo/k4OX0GGMHWTNVL7+vOrJr7FqH8kd2CjRnDEKwczrrl9XYOyCyA1h hihFIm/tBM0tPRkKjqbMWLKIKFqTbyuuXNIhoGj7WfQTCugmP1HZnhNakwJPNhh9m3/E C9NHGjFSXePih5zsB+zood2MBMioVrvtDa0/dYXo2Ex6oRJN7Rl39BDzUAnmfRKRL+D8 qMHoItGKBI5PHOZ5PGbK7An71cC3DBfz1YGWNZ57N7UDpsVqKaHoWbSJCatOOC+dmkIh +tuVpakDZez1LkI0hM/VE2fLuzBp1jYTYR8Sr4/C6j7Tr0W9Uqoo3zczYu/AyaQvj7t9 fhnw==
X-Gm-Message-State: APjAAAWffgR3wpXezsK3U0ZsrbYuCozl+a/DjlTuqbevqcsrfJ+Ja1Pi LBkE8MKiZgQrDo227V+GgwnH0be3EpzXUcTdtuA2y3tK
X-Google-Smtp-Source: APXvYqyZsgb80gvtMgLFI1ZfDwhm1EPvWkD/juLgeCn/eE7K/pnmtnZOG53JfCmJ0TW0QC4CSUK45UQWIiemzxG+I0o=
X-Received: by 2002:a92:831d:: with SMTP id f29mr27515588ild.263.1572850459445; Sun, 03 Nov 2019 22:54:19 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: rabi narayan sahoo <>
Date: Mon, 04 Nov 2019 12:24:08 +0530
Message-ID: <>
To: Routing Over Low power and Lossy networks <>
Content-Type: multipart/alternative; boundary="000000000000eb8fc605967fc881"
Archived-At: <>
Subject: Re: [Roll] I-D Action: draft-ietf-roll-dao-projection-07.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Over Low power and Lossy networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Nov 2019 06:54:22 -0000

Dear authors

I reviewed the changes (only) and have some queries and suggestions for the
PDR and Sibling Information Option

   - P-DAO Request Message
      - [Suggestion] When a LN/LR requests for TE path using PDR  it can
      mention the Network Metric that PCE need to consider while computing the
      P-Route. Like A node can request for a TE path based of Hop
Count or based
      on Minimum latency or Minimum EXT or Maximum Battery Life. I think this
      will provide more flexibility for application.
      - [Query] Can PCE be a separate Physical Node Other than BR? If Yes
      how LR/LN will learn about it and send the PDR to it?
   - Sibling Information Option (SIO)
      - [Query] If PCE is a separate physical entity how the Sibling
      informations will be shared with it, as DAO messages will always
      at BR?
      - [Query] If the metric of P-Route need to be different from the
      Network Metric used for the global mesh network, how a LN/LR is going to
      learn about that so that it can send the correct metric
information in SIO?
      - [Issue] Description of Sibling Address filed of SIO is exact copy
      of VIA address filed in VIO (2 to 16 bytes, a compressed IPv6
Address. a *Via
      Address indicates* the next hop towards the destination(s).....).
      This need to be changed.


On Sun, Nov 3, 2019 at 7:38 PM <> wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Routing Over Low power and Lossy networks
> WG of the IETF.
>         Title           : Root initiated routing state in RPL
>         Authors         : Pascal Thubert
>                           Rahul Arvind Jadhav
>                           Matthew Gillmore
>         Filename        : draft-ietf-roll-dao-projection-07.txt
>         Pages           : 27
>         Date            : 2019-11-03
> Abstract:
>    This document proposes a protocol extension to RPL that enables to
>    install a limited amount of centrally-computed routes in a RPL graph,
>    enabling loose source routing down a non-storing mode DODAG, or
>    transversal routes inside the DODAG.  As opposed to the classical
>    route injection in RPL that are injected by the end devices, this
>    draft enables the Root of the DODAG to projects the routes that are
>    needed on the nodes where they should be installed.
> The IETF datatracker status page for this draft is:
> There are also htmlized versions available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> Roll mailing list