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

"Acee Lindem (acee)" <acee@cisco.com> Tue, 02 January 2018 11:59 UTC

Return-Path: <acee@cisco.com>
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 C27461274D2; Tue, 2 Jan 2018 03:59:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 WKFd2e67zwUn; Tue, 2 Jan 2018 03:59:06 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AED28126D05; Tue, 2 Jan 2018 03:59:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6570; q=dns/txt; s=iport; t=1514894346; x=1516103946; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=h7VdK0Ivuhx1KpM4lrBryIsD0CjNc8pxTazFKMnKKo0=; b=cldue2+q64Fcp4nEQPunxXRrh/3gKeg7miba//Dj+q39kbBS7W+tcOGG hBwtIqxyqO/d88v7gPAObI3bfkyL7fu7AEpCRm+Ke/gKlo/Xgd32fpM+t g/AzRjv+udjNxEkC0FgWSRRJZkC0YDT++9IMXzmu/mqiCwAGNpzxlTdi/ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DrAAD9ckta/5tdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM+ZnQnB4QAiiSPGIIBlyqCFQoYC4RJTwIahBY/GAEBAQEBAQE?= =?us-ascii?q?BAWsohSQBAQEDAQEhETobAgEIEgYCAiYCAgIlCxUCDgIEARKKLhCyBYInhBcBh?= =?us-ascii?q?hkBAQEBAQEBAQEBAQEBAQEBAQEBAQEdgQ+CfYE1XYM/gy6DLwEBF4RtgmUFo0w?= =?us-ascii?q?CiAGNMoIXZYUxi1CNJIkyAhEZAYE7AR85gU9vFRkkgikJhBMBOniHaYEWAQEB?=
X-IronPort-AV: E=Sophos;i="5.45,496,1508803200"; d="scan'208";a="51286647"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jan 2018 11:59:05 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w02Bx5ui017417 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Jan 2018 11:59:05 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 2 Jan 2018 06:59:04 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Tue, 2 Jan 2018 06:59:04 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Ladislav Lhotka <lhotka@nic.cz>, "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>, Tom Petch <ietfc@btconnect.com>
Thread-Topic: [netmod] FW: I-D Action: draft-ietf-netmod-rfc8022bis-06.txt
Thread-Index: AQHTfwRmtyMCVakw5E6pebB4gVVRlKNXcWeAgAlRLoD//8F0gA==
Date: Tue, 2 Jan 2018 11:59:04 +0000
Message-ID: <D670DDDB.E7E40%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> <1514889755.4068.17.camel@nic.cz>
In-Reply-To: <1514889755.4068.17.camel@nic.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <EA94988165A4F44B88EDB21E04C250B0@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/-ZSaTICOpvE414Rx53XW2VVKpH0>
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 11:59:10 -0000

Hi Lada, Tom,

Okay - no sense in derailing this draft based on an example if there isn’t
consensus. 

Thanks,
Acee 

On 1/2/18, 5:42 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:

>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