IETF Logo Mail Archive

Re: [Roll] Add ROVR in DAO?

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 24 August 2019 00:40 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 D91771200B8 for <roll@ietfa.amsl.com>; Fri, 23 Aug 2019 17:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 7U9o6_Hc_24l for <roll@ietfa.amsl.com>; Fri, 23 Aug 2019 17:40:21 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDB9A120077 for <roll@ietf.org>; Fri, 23 Aug 2019 17:40:21 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E379B3818F for <roll@ietf.org>; Fri, 23 Aug 2019 20:39:16 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id E77DDC07 for <roll@ietf.org>; Fri, 23 Aug 2019 20:40:18 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <982B626E107E334DBE601D979F31785C5DFB6CBE@BLREML503-MBX.china.huawei.com>
References: <MN2PR11MB35652CCE7A961CD581EDE47DD8C60@MN2PR11MB3565.namprd11.prod.outlook.com> <MN2PR11MB35653048AE54B21CCF055031D8A40@MN2PR11MB3565.namprd11.prod.outlook.com> <982B626E107E334DBE601D979F31785C5DFB6CBE@BLREML503-MBX.china.huawei.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Fri, 23 Aug 2019 20:40:18 -0400
Message-ID: <24307.1566607218@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/5jBD5TTvBGqFj8M6cVGVDofg0QA>
Subject: Re: [Roll] Add ROVR in DAO?
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 24 Aug 2019 00:40:24 -0000

Rahul Arvind Jadhav <rahul.jadhav@huawei.com> wrote:
    > 1.       Remove the ROVR generation on the 6LBR on behalf of the 6LN.
    > 2.       Use the ROVR from NS(EARO) directly in the DAO.
    > 3.       This would eliminate Keep-Alive EDAR/EDAC during initial/first registration.
    > 4.       This would eliminate the need for root node to set all ones in
    > the ROVR field of keep-alive EDAR.
    > This seems optimal.

    > But there is one downside if the DAO is used for such purpose; Adding a
    > 64-bit ROVR field in DAO would mean that in storing MOP all the parents
    > maintain the ROVR field in their routing table. This is an immense
    > overhead, since it impacts the routing entry size even if the RPL
    > network needs to support just a single RUL.

So, ideally, the RUL or 6LR would send some keepalives with the ROVR directly
to the 6LBR even in storing mode.  Maybe not in DAOs.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email