[Roll] any interest in a RPL adjancy MIB/YANG model

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 05 September 2014 12:44 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A49181A066B; Fri, 5 Sep 2014 05:44:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.56
X-Spam-Level:
X-Spam-Status: No, score=-0.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_NO_TEXT=1.999, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=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 OSg9VoHPFa94; Fri, 5 Sep 2014 05:44:10 -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 678311A0696; Fri, 5 Sep 2014 05:44:10 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 51E332002A; Fri, 5 Sep 2014 08:48:19 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id D303E63AE9; Fri, 5 Sep 2014 08:44:02 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id BD560638D6; Fri, 5 Sep 2014 08:44:02 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: roll@ietf.org, 6tisch@ietf.org
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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-sha1; protocol="application/pgp-signature"
Date: Fri, 05 Sep 2014 08:44:02 -0400
Message-ID: <7864.1409921042@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/oSAA8xEBkT7taWrrTlaKJ4hsPP8
Subject: [Roll] any interest in a RPL adjancy MIB/YANG model
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
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: <http://www.ietf.org/mail-archive/web/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: Fri, 05 Sep 2014 12:44:11 -0000

This reminded me:

internet-drafts@ietf.org wrote:
    >         Title : Definition of Managed Objects for IPv6 over Low-Power
    > Wireless Personal Area Networks (6LoWPANs) Authors : Juergen

that I think it would be useful to have a standard way to get the list of
adjacencies from a route-over mesh.   I know that RedwireLLC produced a
really nice graphic from some custom instrumentation that they did, and
I've seen similar graphs from Cisco too.

I was thinking about this the other morning during my cycle to work, and
realized that the list of possible adjancies is perhaps the read-only version
of the 6top data model.  The PCE would need to know the list of all the
possible adjancies (not just the ones that RPL locally chose), and so that
there is significant overlap.

Am I missing something here?

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