Re: [netmod] FW: I-D Action: draft-ietf-netmod-rfc8022bis-06.txt

Ladislav Lhotka <lhotka@nic.cz> Tue, 02 January 2018 10:42 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6CB0126FDC; Tue, 2 Jan 2018 02:42:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level:
X-Spam-Status: No, score=-7.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 Kd9WCcXkrqjD; Tue, 2 Jan 2018 02:42:39 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACA95126BF7; Tue, 2 Jan 2018 02:42:37 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:1f99:257b:62cc:c0d5]) by mail.nic.cz (Postfix) with ESMTPSA id 661886265F; Tue, 2 Jan 2018 11:42:35 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1514889755; bh=Q1eNNOy7Y5TSV69V7sTkGTsIFy8tuonKRkSUYnKa+Eg=; h=From:To:Date; b=H72o7JbnPTMhlYX2zWDqy1R6KdwizkcxLMJUbq1oT3a7Mpgy+a+BGnHN9kjPFfB9M lU7m2PidS7SYO6d+XGAsD55GcO9R+oCwD8/Bzim/vkjehwbMJmeyAL64lMRWLhEp6x XkF/UfgcWx+ueyUqaa3/5IMVCLDsGciwzDDe9rD8=
Message-ID: <1514889755.4068.17.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: "Acee Lindem (acee)" <acee@cisco.com>, "Benoit Claise (bclaise)" <bclaise@cisco.com>, NetMod WG <netmod@ietf.org>, "draft-ietf-rtgwg-yang-rip@ietf.org" <draft-ietf-rtgwg-yang-rip@ietf.org>
Date: Tue, 02 Jan 2018 11:42:35 +0100
In-Reply-To: <D669419C.E70A5%acee@cisco.com>
References: <151396733267.27997.4142470279197260306@ietfa.amsl.com> <D662B94E.E5B50%acee@cisco.com> <9019c1c5-ea86-5620-5421-749b4aee35d9@cisco.com> <D669419C.E70A5%acee@cisco.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.3
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/3zs-h_BcKPZXn0CqoK_KUbSfr2Q>
Subject: Re: [netmod] FW: I-D Action: draft-ietf-netmod-rfc8022bis-06.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jan 2018 10:42:42 -0000

On Wed, 2017-12-27 at 17:25 +0000, Acee Lindem (acee) wrote:
> Hi Benoit, 
> 
> On 12/27/17, 6:18 AM, "Benoit Claise (bclaise)" <bclaise@cisco.com>; wrote:
> 
> > Thanks Acee,
> > 
> > Minor question for the working group and the draft-ietf-rtgwg-yang-rip
> > authors.
> > 
> > The appendix is about adding a new control-plane protocol. It takes as
> > an example RIP.
> > However, draft-ietf-rtgwg-yang-rip is being finalized (on the IESG
> > telechat on Jan 11th).
> > Does it make sense to keep the RIP example? If so, is the example
> > consistent with draft-ietf-rtgwg-yang-rip?
> > Or should we just point to draft-ietf-rtgwg-yang-rip as the example?
> 
> It is probably better just to reference the RIP module draft. Does anyone
> disagree?

I tend to disagree. For this document, we need a simple example to illustrate
the steps that need to be done. Any production module, be it ietf-rip or
anything else, necessarily involves some complexity that defeats the purpose of
the example.

In my view, the present RIP example is fine. Perhaps we can extend the
disclaimer saying that it is not intended as a production module and also
provide a non-normative reference to the "real" RIP module.

Lada

> 
> Thanks,
> Acee 
> > 
> > Not strong views on my side.
> > 
> > Regards, Benoit
> > > This version includes Martin’s YANG doctor comments and some updates to
> > > the examples (e.g., YANG Library data) from Lada.
> > > 
> > > Thanks,
> > > Acee
> > > 
> > > On 12/22/17, 1:28 PM, "netmod on behalf of internet-drafts@ietf.org";
> > > <netmod-bounces@ietf.org on behalf of internet-drafts@ietf.org>; wrote:
> > > 
> > > > A New Internet-Draft is available from the on-line Internet-Drafts
> > > > directories.
> > > > This draft is a work item of the Network Modeling WG of the IETF.
> > > > 
> > > >         Title           : A YANG Data Model for Routing Management
> > > > (NDMA
> > > > Version)
> > > >         Authors         : Ladislav Lhotka
> > > >                           Acee Lindem
> > > >                           Yingzhen Qu
> > > > 	Filename        : draft-ietf-netmod-rfc8022bis-06.txt
> > > > 	Pages           : 77
> > > > 	Date            : 2017-12-22
> > > > 
> > > > Abstract:
> > > >    This document contains a specification of three YANG modules and one
> > > >    submodule.  Together they form the core routing data model that
> > > >    serves as a framework for configuring and managing a routing
> > > >    subsystem.  It is expected that these modules will be augmented by
> > > >    additional YANG modules defining data models for control-plane
> > > >    protocols, route filters, and other functions.  The core routing
> > > > data
> > > >    model provides common building blocks for such extensions -- routes,
> > > >    Routing Information Bases (RIBs), and control-plane protocols.
> > > > 
> > > >    The YANG modules in this document conform to the Network Management
> > > >    Datastore Architecture (NMDA).  This document obsoletes RFC 8022.
> > > > 
> > > > 
> > > > The IETF datatracker status page for this draft is:
> > > > https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc8022bis/
> > > > 
> > > > There are also htmlized versions available at:
> > > > https://tools.ietf.org/html/draft-ietf-netmod-rfc8022bis-06
> > > > https://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc8022bis-06
> > > > 
> > > > A diff from the previous version is available at:
> > > > https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-rfc8022bis-06
> > > > 
> > > > 
> > > > Please note that it may take a couple of minutes from the time of
> > > > submission
> > > > until the htmlized version and diff are available at tools.ietf.org.
> > > > 
> > > > Internet-Drafts are also available by anonymous FTP at:
> > > > ftp://ftp.ietf.org/internet-drafts/
> > > > 
> > > > _______________________________________________
> > > > netmod mailing list
> > > > netmod@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/netmod
> > > 
> > > _______________________________________________
> > > netmod mailing list
> > > netmod@ietf.org
> > > https://www.ietf.org/mailman/listinfo/netmod
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67