From nobody Tue Apr 20 07:24:54 2021 Return-Path: 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 8F69E3A25D6; Tue, 20 Apr 2021 07:24:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 E5G0cJmpBMtR; Tue, 20 Apr 2021 07:24:45 -0700 (PDT) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AB4A3A25D7; Tue, 20 Apr 2021 07:24:44 -0700 (PDT) Received: by mail-ed1-x529.google.com with SMTP id j7so8409577eds.8; Tue, 20 Apr 2021 07:24:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=lZosBAWDrPI/Epx5au+koMEFGPtppIlfSvT3ynjmwQw=; b=Cw6XSdyoaUcyILrIR53m6QPnt8ftUbcNQQSMgk5upqMjULVbIAAngxn2bB/ABdhjLn ZgjtON3ydpp46CSDvzwA6NZNmcRf6rNXXMq1psJJAavEj+BdU10MYjSxVwMC4+e4CRgD xYU/QLNm+QboTtkCaEQ5WF32xbrxmH93t2WGhCB7zOft24CvDMIvYZ6/ViRWNrliGc8p 5qAuagUpD00+nv5d52NvKCvwzRF1/dumRnnAosYPpd1Nir/LpgE69t2aenRlWziJF/SZ 0TQHrm8LA+ecpRwZD7q88M/uc7jKXGFP0wTPpvu84719vZcrZboskB+o2rNrtG3Q+h3X Jjhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=lZosBAWDrPI/Epx5au+koMEFGPtppIlfSvT3ynjmwQw=; b=b1FNjmJ5ZbIoBelGc46ejnu6sp9DmmAQqELhZExHfrf11vTd6TOm6Zt3mZ6HmWteHh Dem0gf3T4z4yFqZUbG/xscBgsoZ9+h5X5pjNyTsrHqyQe+8dXMd5tzPcSvrP8jBDMqvv 45Cc43bELJZ8nIsxaRo5minKXxkGl9Wp4EEvkuyisOWfTjzAfT2ICrxqQg/sW9Uzd0Gj f1fbmS5UbPfEhJUkfSccfLeSTgTAznfuoFhUHUbkgbuhwwydlxjisLanI8JEc2Qh1uVT 87rVmKiJAGqOq73qupZ9R/28msdItOjcejAXuQBtIeQ411B18WOq6kMM7bM/umPvaE3G duBQ== X-Gm-Message-State: AOAM532viLNF3kWkHaGS0+R8/419d5g8t+g+jWNyhuG5VQUEV1C407SB P9XEnON3x/fNCgDcGMlBljVa98UZjPRLFmrV+99EZqQF3shqow== X-Google-Smtp-Source: ABdhPJz+sASy//FGlbq6rbuQcjH1zubIDqmeqvJC3iGzGNuwMna94t+oMEYyco5lqoqsN3fDTPLQZYFD7Ax73NAHYIo= X-Received: by 2002:aa7:dbd3:: with SMTP id v19mr32456136edt.314.1618928677358; Tue, 20 Apr 2021 07:24:37 -0700 (PDT) Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 20 Apr 2021 07:24:36 -0700 From: Alvaro Retana In-Reply-To: <161891771644.17807.13402380343710528758@ietfa.amsl.com> References: <161891771644.17807.13402380343710528758@ietfa.amsl.com> MIME-Version: 1.0 Date: Tue, 20 Apr 2021 07:24:36 -0700 Message-ID: To: Robert Wilton Cc: draft-ietf-roll-aodv-rpl@ietf.org, roll@ietf.org, roll-chairs@ietf.org, Ines Robles , The IESG Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [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 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: Tue, 20 Apr 2021 14:24:50 -0000 On April 20, 2021 at 7:21:57 AM, Robert Wilton wrote: Rob: Hi! =C2=A0Thanks for your review! ... > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- ... > So, the specific questions that I have are: > > (1) Are YANG data models and the existing NETCONF/RESTCONF protocols suit= able > 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: I= s > there a plan for the ROLL WG to develop a YANG data model for this protoc= ol > (and RPL if required)? AODV-RPL builds on RPL; it uses a new Mode of Operation (MOP) dedicated to the discovery of p2p routes. =C2=A0Yes, any RPL-specific management should be able to be extended for AODV-RPL. The roll charter specifically mentions the definition of a data model for RPL. =C2=A0The WG has been focused on other work and this item hasn't been a priority yet. Alvaro.