[Roll] Robert Wilton's Discuss on draft-ietf-roll-aodv-rpl-10: (with DISCUSS)

Robert Wilton via Datatracker <noreply@ietf.org> Tue, 20 April 2021 11:21 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: roll@ietf.org
Delivered-To: roll@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D5EC73A1E3E; Tue, 20 Apr 2021 04:21:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-roll-aodv-rpl@ietf.org, roll-chairs@ietf.org, roll@ietf.org, Ines Robles <mariainesrobles@googlemail.com>, aretana.ietf@gmail.com, mariainesrobles@googlemail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.28.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <161891771644.17807.13402380343710528758@ietfa.amsl.com>
Date: Tue, 20 Apr 2021 04:21:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/aaE6520X3Y4pBVXPyFW-gceJU-8>
Subject: [Roll] Robert Wilton's Discuss on draft-ietf-roll-aodv-rpl-10: (with DISCUSS)
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Apr 2021 11:21:57 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-roll-aodv-rpl-10: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:



Thank you for your work on this document.

I support John's comment that this document could more clearly state its
relationship to RPL, which may have a bearing on my discuss comment below.

I've balloted discuss on this document because it is not clear to me how this
network protocol would be managed.  I.e., this document doesn't seem to have
any text related to how the protocol is managed, nor does it define a YANG data
model, and I cannot see any YANG data models for this protocol currently in the

So, the specific questions that I have are:

(1) Are YANG data models and the existing NETCONF/RESTCONF protocols suitable
for managing devices running AODV-RPL?

(2) Does this protocol build on RPL, and hence would any YANG data models
expect to also build on an RPL YANG data model?

(3) If the answer to 1 or 2 is yes, then a question for the chairs/ADs: Is
there a plan for the ROLL WG to develop a YANG data model for this protocol
(and RPL if required)?

(4) If the answer to 1 or 2 is no, then what other information can be provided
in this document to help implementations create an interoperable management
interface for this protocol?

For clarity, I'm not saying that a YANG data model needs to be provided before
this document can progress, but I would like to understand the path to ensuring
that this protocol can be managed, which may require additional text depending
on the answers to the questions above.