IETF Logo Mail Archive

Re: [Roll] capability handling

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 07 May 2020 18:01 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 EFCB03A0984 for <roll@ietfa.amsl.com>; Thu, 7 May 2020 11:01:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 XWgLg-mTKpV6 for <roll@ietfa.amsl.com>; Thu, 7 May 2020 11:01:20 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48DF93A0941 for <roll@ietf.org>; Thu, 7 May 2020 11:01:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 992613897F for <roll@ietf.org>; Thu, 7 May 2020 13:59:18 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dUrpCD0TAmZM for <roll@ietf.org>; Thu, 7 May 2020 13:59:18 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 540A33897E for <roll@ietf.org>; Thu, 7 May 2020 13:59:18 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 654D91D3 for <roll@ietf.org>; Thu, 7 May 2020 14:01:18 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <BM1PR01MB402011EE18D8BE1C70A15AE4A9A50@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM>
References: <BM1PR01MB402011EE18D8BE1C70A15AE4A9A50@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512"; protocol="application/pgp-signature"
Date: Thu, 07 May 2020 14:01:18 -0400
Message-ID: <31727.1588874478@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/d8svCcWmH4fCnBfyjSfLNKFz-Sc>
Subject: Re: [Roll] capability handling
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: Thu, 07 May 2020 18:01:25 -0000

Rahul Jadhav <nyrahul@outlook.com> wrote:
    > We would like to solicit some feedback about two points in context to
    > capabilities:

    > 1. Capability Instances: Currently the document instantiates two
    > capabilities viz, a) Capability Indicators (which can be used to carry
    > flags such as support of 6LoRH)
    > b) Routing Resource capability which
    > indicates total RIB capacity the node has. This should be useful for
    > DAO Projection.

    > Do you think we should add Neighbor Cache capacity
    > indication as well and what would be the use-case?

In some implementations the Neighbor Cache and RIB might come from the same
pool of resources.  Both are lookup /128 and add-header and xmit :-)
(BSD systems merged them back in BSD4.4, as an example)

If a node runs out of RIB entries, it can't add any more grandchildren.
If a node runs out of NC entries,  it can't add any more peers: children or parents.

It seems that we need to collect both information, but we might need to be
clear if they are linked.

    >   Do we need an explicit 'G' flag? We already have a flag (C-copy)
    >   which indicates that nodes have to copy the cap if they don't
    >   understand the cap. A global capability from the root can be
    >   advertised with this bit set. Nodes understanding this cap will
    >   anyways know how to handle and nodes not understanding it will copy
    >   it based on the 'C' flag. Thus not requiring another 'G' flag.

I have to think more on this.

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

v2.23.0 | Report a Bug | By Email