Re: [Roll] DIS-modifications use cases; Re: FW: New Version Notification for draft-ietf-roll-dis-modifications-01.txt

Rahul Jadhav <> Tue, 25 February 2020 05:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 989053A0A43 for <>; Mon, 24 Feb 2020 21:38:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RlY411MgQo94 for <>; Mon, 24 Feb 2020 21:38:41 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 834693A0A42 for <>; Mon, 24 Feb 2020 21:38:41 -0800 (PST)
Received: by with SMTP id 83so8688608lfh.9 for <>; Mon, 24 Feb 2020 21:38:41 -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=UeMofMx0dpSn5k5HhUZu0mhmtGP6iEBCVXbf2ZSuz24=; b=CMu3zpXvJlFOX0vjl3fWw/BzBH/1movIJbx2XSjPcrkUQvFesYcM4pAOKBmGMcLNEU FCu0O2Wypn77olP/QEBaBRNVL4fJZcgsPOvf+eCLhd6PKqqCEO9IlD8ZSzO8Ll/9+P+/ 9t/rtUuCBmEwjBFAUEKKgh+NQOFmxnZvUWNl7y1PCXy4j/2PHitGR5SKoVqpmR1LML69 20z/FMuDmj4DtVRN0sOOwHhKLji4aGZ6sWw4S8DRZQ75v6FT6D53/ye+rPsUyxd4rSZt i8y++mSa/WyMJ7+yCK3ymELh2YZqQiCigDOZ6Jt2LmnXENyLY2vfqr0Q7GpC5q92GJVZ gSeg==
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=UeMofMx0dpSn5k5HhUZu0mhmtGP6iEBCVXbf2ZSuz24=; b=ilynL3D3+wVKADIKnzOxR/b596MiN+VGr71yViOcW98Nv97p4J1qYhNS0d9kl3f1lv OBgBHWm6nApAIhe2i0/Zr/Aagm6lezyyuVKaivs2Pi9YqUpGXYlcMhf4ZQjvDLI+RGRt J9v8b4xTTyF05emC2fvDNu12GQwli3qXZhzOHa9JsSB3ul6K/VKN4M7/1smO/bV0vfT0 5whwYY8M/Lhu4sJnteNyaXCCiaJfGve3Wdu5oUDQRkbFy2jR5y6B01TvF32HWI8FL2AR SRwbxsYfXCilPAOJA56SVk36Yv3r/29vjNfRhh1heysTEdAQkhv942oWsqyD2wQn6Fbq DaEw==
X-Gm-Message-State: APjAAAVCW1ce0RhjUN01caoDhRvhTZsnuIIWg7Gl0haZ4ORo38+JLVkq IpU3pMiCxg/NMgV9J8RPwGehuvaonOOBo44YjVnsvg==
X-Google-Smtp-Source: APXvYqxEOh0IVsi3rwBSYSke9TqQYeCmrGfBec8Ft63pdwD03BAtdQc0AdrMLfRNy0H63mBqk0Nw8CY9RTj2jk0wVTc=
X-Received: by 2002:a05:6512:304d:: with SMTP id b13mr3563632lfb.134.1582609119396; Mon, 24 Feb 2020 21:38:39 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Rahul Jadhav <>
Date: Tue, 25 Feb 2020 11:08:27 +0530
Message-ID: <>
To: Routing Over Low power and Lossy networks <>
Content-Type: multipart/alternative; boundary="00000000000061462a059f5fe6af"
Archived-At: <>
Subject: Re: [Roll] DIS-modifications use cases; Re: FW: New Version Notification for draft-ietf-roll-dis-modifications-01.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: Tue, 25 Feb 2020 05:38:44 -0000

On Mon, 24 Feb 2020 at 22:22, <> wrote:

> Dear Rollers,
> In preparation for the modification of the DIS (DODAG Information
> Solicitation), we are collecting the use cases.
> We want to make sure we understand all the requirements before crafting a
> solution.
> Georgios has kindly prepared a document on the ROLL GitHub repo.
> See a text rendition at
> ft-papadopoulos-roll-dis-modifications-use-cases.txt
> <>

[RJ] Thanks Georgios. This surely helps. I am assuming that the use-cases
text will get merged in the dis-modifications draft.
One point mentioned in the use-cases draft is that unicast DIS can request
__specific__ metric information from the parent. Currently, the parent
sends the complete metric set to the child using unicast DIO. Wondering
whether we need this mechanism for sending specific metric info back to the
child node. The draft does not give a use-case for this. Anyways, this
would be discussed when the drafts get merged and sent to the group.

Currently, the document has two use cases:
> - a new node joins an established RPL network. The use case calls for a
> fairly quick confirmation that the node has joined with a good quality
> path. However, we don't want to reset the Trickle timers of all nearby
> routers and trigger broadcast, since the use case is that just one new
> node was added/replaced/rebooted.
> - another use case is that several nodes join at about the same time (e.g.
> electricity meters all reboot following power outage). We want the DIOs to
> be sent with broadcast so that all joining nodes benefit from them.
> The draft draft-thubert-roll-eliding-dio-information-03 has another
> request for modifying the DIS. We'll soon incorporate it into the use
> cases document.

[RJ] Another use-case is of "adjacency probing". While (I believe) no new
primitives need to be added, still the use-case is well-worth mentioning.
The RPL-observations draft points to this use-case and you can pick some
text from there.