Re: [Roll] [ROLL] Projected DAO and Extended MOP

Michael Richardson <> Sat, 02 November 2019 20:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4A07B12002F for <>; Sat, 2 Nov 2019 13:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.199
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qaJw6t7l0uOi for <>; Sat, 2 Nov 2019 13:37:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 65A6012001E for <>; Sat, 2 Nov 2019 13:37:24 -0700 (PDT)
Received: from ( [IPv6:2607:f0b0:f:2::247]) by (Postfix) with ESMTP id C6F0B3897A for <>; Sat, 2 Nov 2019 16:34:32 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by (Postfix) with ESMTP id 5EA2771D for <>; Sat, 2 Nov 2019 16:37:22 -0400 (EDT)
From: Michael Richardson <>
To: Routing Over Low power and Lossy networks <>
In-Reply-To: <>
References: <> <>
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: Sat, 02 Nov 2019 16:37:22 -0400
Message-ID: <7662.1572727042@localhost>
Archived-At: <>
Subject: Re: [Roll] [ROLL] Projected DAO and Extended MOP
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: Sat, 02 Nov 2019 20:37:28 -0000

This is how I see the state of things:

1) unaware-leaves + useofrplinfo are synchronized, and this frees up some mind
   bandwidth, and I confess to have been overwhelmed by this part.

2) we came to the capability problem from rfc8138-turn-on and DAO-projection.

3) I'd really like implement rfc8138-turn-on with the capabilities.
   I don't like the use of the T-bit here, because we have other stuff that
   we also need.

4) I don't feel like we have properly concluded about whether or not
   DAO-projection is a new MOP or not.

I have a todo item which is to write sample text on how to express
DAO-projection in terms of mopex.  I haven't done this yet.

Michael Richardson <>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-