Re: [Roll] IOTdir Review of draft-ietf-roll-dao-projection-19

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 07 September 2021 13:02 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 88A983A1EE7 for <roll@ietfa.amsl.com>; Tue, 7 Sep 2021 06:02:34 -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 SyWbrSZWgaCH for <roll@ietfa.amsl.com>; Tue, 7 Sep 2021 06:02:30 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BB483A1EE1 for <roll@ietf.org>; Tue, 7 Sep 2021 06:02:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9D33F39762 for <roll@ietf.org>; Tue, 7 Sep 2021 09:08:47 -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 nF6VsVQQaaxh for <roll@ietf.org>; Tue, 7 Sep 2021 09:08:43 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id EE9FA39761 for <roll@ietf.org>; Tue, 7 Sep 2021 09:08:42 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 956282CC for <roll@ietf.org>; Tue, 7 Sep 2021 09:02:22 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <CO1PR11MB4881F8390A8B4167774E35D9D8D29@CO1PR11MB4881.namprd11.prod.outlook.com>
References: <20210829222620.GA6858@faui48f.informatik.uni-erlangen.de> <1673.1630595658@localhost> <CO1PR11MB4881986E6AB6E69F42652213D8CE9@CO1PR11MB4881.namprd11.prod.outlook.com> <CO1PR11MB4881F8390A8B4167774E35D9D8D29@CO1PR11MB4881.namprd11.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: Tue, 07 Sep 2021 09:02:22 -0400
Message-ID: <8227.1631019742@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/cB87PsZ8T-1jYjNcqQkvJsxaZ5c>
Subject: Re: [Roll] IOTdir Review of draft-ietf-roll-dao-projection-19
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: Tue, 07 Sep 2021 13:02:35 -0000

Pascal Thubert \(pthubert\) <pthubert=40cisco.com@dmarc.ietf.org> wrote:
    > On you point about a storing mode main DODAG; I suggest we keep it as a
    > side addition by having a new section about it.  What about " 10.
    > Storing-Mode Main DODAG

I like your text.

I think that a major advantage of P-DAO in the ACP case is that we can
establish routes that stay within a DC,  which we can't really depend upon if
the DC has good uplinks.

    >    In Storing Mode, the Root misses the Child to Parent relationship
    > that forms the main DODAG, as well as the sibling information.  To
    > provide that knowledge the nodes in the network MUST send additional
    > DAO messages that are unicast to the Root as Non-Storing DAO messages
    > are.

My opinion is that this is perhaps new MOP :-)
I think that it requires RH3 to be implemented, possibly also RPI, which ACP
does not have at present.

    >    The DAO message MUST be formed as follows:

I will need to write code to validate the rest of the text.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide