[Roll] Child count in parent selection

Chenyang JI <chenyang.ji@imt-atlantique.net> Mon, 30 October 2017 07:40 UTC

Return-Path: <chenyang.ji@imt-atlantique.net>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F76013F6BD for <roll@ietfa.amsl.com>; Mon, 30 Oct 2017 00:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=imt-atlantique.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iYzdBwl-kom5 for <roll@ietfa.amsl.com>; Mon, 30 Oct 2017 00:40:05 -0700 (PDT)
Received: from zproxy110.enst.fr (zproxy110.enst.fr [137.194.2.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB04C139F67 for <roll@ietf.org>; Mon, 30 Oct 2017 00:40:05 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by zproxy110.enst.fr (Postfix) with ESMTP id 9055B8191B; Mon, 30 Oct 2017 08:40:03 +0100 (CET)
Received: from zproxy110.enst.fr ([IPv6:::1]) by localhost (zproxy110.enst.fr [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id csGU-gO06oy0; Mon, 30 Oct 2017 08:40:03 +0100 (CET)
Received: from localhost (localhost [IPv6:::1]) by zproxy110.enst.fr (Postfix) with ESMTP id DE1D4819B3; Mon, 30 Oct 2017 08:40:02 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy110.enst.fr DE1D4819B3
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imt-atlantique.net; s=6A0CDB44-C782-11E6-82EC-91BDBA474D24; t=1509349202; bh=4ywv4HU1BiQCeyrOgoxBbvfVqoD3U84tbpzXiZfHJSA=; h=Date:From:To:Message-ID:MIME-Version; b=Wq0rznixdY2YFnzPniJsut6esDH94ZQtVdCi7uERyUO201Omztj/DMGM389u82wQR 60CIoI1vzxz3fw9pHAcbf9uqqY4SkIbvSc00gSGd4BILJkAFS8saiscFIOOMkw2yHt 8II4UZZfHvzEwGPxQNIym1uP9QCCYfShB63ef3fQ=
X-Virus-Scanned: amavisd-new at zproxy110.enst.fr
Received: from zproxy110.enst.fr ([IPv6:::1]) by localhost (zproxy110.enst.fr [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id 4ScQ7dgUKBek; Mon, 30 Oct 2017 08:40:02 +0100 (CET)
Received: from zmail131.enst.fr (zmail131.enst.fr [137.194.2.203]) by zproxy110.enst.fr (Postfix) with ESMTP id B598281039; Mon, 30 Oct 2017 08:40:02 +0100 (CET)
Date: Mon, 30 Oct 2017 08:40:02 +0100
From: Chenyang JI <chenyang.ji@imt-atlantique.net>
To: roll@ietf.org
Cc: jichenyang920 <jichenyang920@gmail.com>
Message-ID: <961578433.3782382.1509349202587.JavaMail.zimbra@imt-atlantique.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [2001:660:7301:51:c126:3f76:249e:b974]
X-Mailer: Zimbra 8.7.11_GA_1854 (ZimbraWebClient - FF56 (Linux)/8.7.11_GA_1854)
Thread-Index: scGtGtECzxp8Ez74Cq84pyO91p2VoA==
Thread-Topic: Child count in parent selection
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/wQ15hVpaXgAs4qi0JFOw3FIcgY0>
Subject: [Roll] Child count in parent selection
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 07:40:08 -0000

Hello,

I have some questions about draft-hou-roll-rpl-parent-selection-00 and draft-qasem-roll-rpl-load-balancing-01.
In the draft,it describes a new type of metric which has this format:

CNC: 8 bits. The Child Node Count is encoded in 8 bits in unsigned
integer format, expressed in number count, representing the number of
child nodes.

MAX_CNC: 8 bits. The Maximum Child Node Count is encoded in 8 bits
in unsigned integer format, expressed in number count, representing
the maximum number of child nodes allowed in the neighbor cache.

but it does not clarify if this number of child nodes refers to the number of direct child or the subtree size.

In draft-qasem-roll-rpl-load-balancing-01:

In LB-OF algorithm, the received DIO from the child node
is counted by the preferred parent node. Each DIO contains the IP
address of the chosen preferred parent as detailed in section 4.3. Thus,
for each received DIO, the node matches its own IP address with the
preferred parent IP address which is inserted in the DIO message, then
increments the number of children by ONE for this node if there is a
matching.

My question is if that mean it will store the children's address and if yes,how will the node stores its children.

The first draft
https://tools.ietf.org/html/draft-hou-roll-rpl-parent-selection-00

The second draft
https://datatracker.ietf.org/doc/html/draft-qasem-roll-rpl-load-balancing

Best regards,
Chenyang Ji