IETF Logo Mail Archive

Re: WG Adoption for "RIB YANG Data Model" - draft-acee-rtgwg-yang-rib-extend

"Acee Lindem (acee)" <acee@cisco.com> Mon, 18 February 2019 20:00 UTC

Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43980131084; Mon, 18 Feb 2019 12:00:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 header.b=KhVlrQCT; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Ok84x/4P
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 d6UlRBJS3cpz; Mon, 18 Feb 2019 12:00:46 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1864F1310DB; Mon, 18 Feb 2019 12:00:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17117; q=dns/txt; s=iport; t=1550520043; x=1551729643; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=JOgp4mOrKHVamvdj7m1Yf5K3BQhgIwf/h9VoE8GDdVY=; b=KhVlrQCT/MEmhE9ryAcWJa7u5m46bqS55+l56uCdu7ehKvAQQx1sO4aP VNM9EWmA9f8zxLBVitFjOoIIeTiPML7MCCc92qgZF0wYxqX+A44Rda1/f 5DyrkpPVGFVeaqr2rP5X99Cd7H2C4G7NGTf+K7MdIqmSZUVJMxRfiJjXU c=;
IronPort-PHdr: 9a23:f5Rx0BOxYC1LJ6cj4hIl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEuKg/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDOIdJSwdDjMwXmwI6B8vQAEb2IdbhbjcxG4JJU1o2t3w=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BdAADpDWtc/5NdJa1jGgEBAQEBAgEBAQEHAgEBAQGBZYEOI1ADZ3QECycKg3yDRwOPbYJXiSuIfIYEgRADVAsBARgBCgmEQAIXg1kiOBIBAwEBAgEBAm0cDIVKAQEBAQMBASEdAQEsBAIGDwIBCBEDAQIoAwICAh8GCxQJCAIEARKDIAGBDkwDFQECDKENAooUcYEvgngBAQWBBQGDfA0LggsDBYxEF4F/gTgfgkyCV0cBAYEpBQESATYJDQmCUzGCJpAohxeLSjMJAopshC2DOxmBb4VUizeJcglGhnOLBAIEAgQFAg0BAQWBXSFlcXAVOyoBgkGCHINuhRSFCAE2coEojFKBHwGBHgEB
X-IronPort-AV: E=Sophos;i="5.58,385,1544486400"; d="scan'208,217";a="435853236"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Feb 2019 20:00:23 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id x1IK0NgA025679 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 18 Feb 2019 20:00:23 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 18 Feb 2019 14:00:22 -0600
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 18 Feb 2019 14:00:22 -0600
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 18 Feb 2019 14:00:21 -0600
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=JOgp4mOrKHVamvdj7m1Yf5K3BQhgIwf/h9VoE8GDdVY=; b=Ok84x/4PLBGiAKnQfQX5kzA4fPVhbfuFSD5kS7sWGdtL5/cpnGoKg4toHIAFPEGiKxpmgndEsd+DbvDW5c+ypukdLSEo+nZ5amb0boWduML1D3bqbDuvar+jrKhxTbXB5aouyvTZozbBTG6P1kjRlVOZZCGtpVXCRcnfDg+9QIA=
Received: from BN8PR11MB3683.namprd11.prod.outlook.com (20.178.220.74) by BN8PR11MB3746.namprd11.prod.outlook.com (20.178.221.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1622.19; Mon, 18 Feb 2019 20:00:19 +0000
Received: from BN8PR11MB3683.namprd11.prod.outlook.com ([fe80::d042:6a6e:589b:b242]) by BN8PR11MB3683.namprd11.prod.outlook.com ([fe80::d042:6a6e:589b:b242%6]) with mapi id 15.20.1601.023; Mon, 18 Feb 2019 20:00:19 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>, Routing WG <rtgwg-chairs@ietf.org>, "draft-acee-rtgwg-yang-rib-extend@ietf.org" <draft-acee-rtgwg-yang-rib-extend@ietf.org>
Subject: Re: WG Adoption for "RIB YANG Data Model" - draft-acee-rtgwg-yang-rib-extend
Thread-Topic: WG Adoption for "RIB YANG Data Model" - draft-acee-rtgwg-yang-rib-extend
Thread-Index: AQHUx3vDftS+4JWPEkOOvBGKPqjqeKXlplsA
Date: Mon, 18 Feb 2019 20:00:19 +0000
Message-ID: <C50763F7-125E-4BB7-B08F-385ACF0F3A22@cisco.com>
References: <d352c810-1b50-4843-b86d-45f1e9d08257@Spark> <a95eb664-4a20-458d-a894-93693c9e31eb@Spark> <b0d9411f-19ad-2cef-359e-b722ac84e5ad@cisco.com>
In-Reply-To: <b0d9411f-19ad-2cef-359e-b722ac84e5ad@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [173.38.117.71]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e4673066-88f4-485b-3887-08d695dbb5a4
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:BN8PR11MB3746;
x-ms-traffictypediagnostic: BN8PR11MB3746:
x-ms-exchange-purlcount: 1
x-ld-processed: 5ae1af62-9505-4097-a69a-c1553ef7840e,ExtAddr
x-microsoft-exchange-diagnostics: 1;BN8PR11MB3746;23:k8SV6/65Hz9g5DXugUPbMks/z0f5aPXLgNk9QmtlMiyIOPVKoBNZiPGCOKtK3NsqlB0/X5KJr3Mx9VrqNsIT1ALjjMm+rPgIwzrZmCOyvMhBZDSkko0QgijXUCWCmFg3boHGEW1rS7Tb5YmEtFDpTnh4htWW+YMSMtJYFF0/Agnx0JDk5wOh/IrUuRwhuR9Mp89xuJSnYSCEn644IBhd4N0Wf+F40MlhA/z/Tt66iFpxvqbZ993vAgZpU8nRYdp7qDsVv4lyuLesH17sb0MdhiWRDEoyrszPxViZnx52bzkmzAXbfEiY6qav82AcZp4sRcDs/nP/ctEXzDbSJxAxCGA2eTl+oPwJjaPci8ugPCNStCTGsey3mRKtHMLeMLgaatRgKsCvwXBjyBOVNTJpfPyugYwKy+muyRAfSPPUjnapBjW721JJJAu8Ux4nL1ePT1LVQVHNe/zEu5qcxkfPSyZJoETN+f8iUmmVsw+3ykutYAhWgdVCrKEgpzKW14vazyMnlmbboXeHAJ8H4lzSBXQvMY1JEHCVXLd7Y0/XL9FxboTZG6Qg7s2muUWdLcFSqshGTPihPwNBrnQZaDT+0LalDlGyQTharYokBTxvTq+8BFNMv72/kYiI0pSqd+Ajq07xvAw7qrDafR/37DkSWXYkKQBUh2VgguuKfPlR6eaizHqFM9/0XGi815GVk/tiPufQ8HeeCS9uANmhBlSeVVZteO2ZySiaSN0dy0eB6ZabAD6dX+ZGNV9L84P95gdEiSKMyHQtLUFZX8nanMnswwSPW4nGRTOPOYUCZ1ii2Aoyh3Y7+gjMuyf32pBUUdwsrPSdb4UVQPYtOBNU39YcwBMizy/OiYW/tLQbW30/MwGlKfW2ULIbV5FLTkeaQm1v/XeuvSg9rdTHWQLSBakL83A9BNuQq0m7LxEG0985gZydkAC+zfIjpGa91j7Vt4lNvskrz8RilI0UMdyyFDONZH8BOvw6MLSEslOPZFS7LbacXI9F326BKnjm5MWRT6HKKb4pZtsF3zWv95bCgLSE1R5dN4uSCOkKebIOYuaJoSgBPSQ88Rc1p7cUPyQcDVABLDS3CwGoRlpG98Iw4G2YWzH0lkSj7+KMQEi3PokI2IGnb7xukq7hH7SVJ8zHtSUYgC8FjEtsYINJBVRfFK96e0vBCSIzU4ZbzaG5VdR1P4sG3Kp0WlKZXuxqG++8MVQE4wUPKmd/c2PQcKKGGS80V3SewzHNfsTKRUk2u39ayB4vHcIO3FbhQC9+uGmkZ3tQyB0wyeOHMYgsDMKviBpjs7V/iyZritz24GIdWHplXHRRFJuZ0UeP6awwJ1vmf5n6WpfBuwU9lveUNj0XojtH4NWqf0Y6ficDSE13hjHvu1E=
x-microsoft-antispam-prvs: <BN8PR11MB3746C79507F3884E251B9443C2630@BN8PR11MB3746.namprd11.prod.outlook.com>
x-forefront-prvs: 09525C61DB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(366004)(136003)(396003)(376002)(346002)(189003)(199004)(51444003)(256004)(9326002)(14444005)(68736007)(606006)(53546011)(97736004)(6506007)(25786009)(26005)(102836004)(476003)(6512007)(11346002)(446003)(2501003)(53936002)(186003)(2906002)(2616005)(36756003)(82746002)(486006)(54896002)(236005)(66066001)(33656002)(6306002)(105586002)(6436002)(6246003)(7736002)(81156014)(81166006)(99286004)(8676002)(3846002)(106356001)(217873002)(229853002)(76176011)(83716004)(478600001)(71190400001)(71200400001)(316002)(110136005)(14454004)(966005)(6116002)(8936002)(6486002)(86362001)(5660300002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN8PR11MB3746; H:BN8PR11MB3683.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: yZQfL0O/Qqv8R94LIe8ef2+DL2ZWSY44oUfBdqOWX9Rhbkas0YL1N3ERKMwMWIiwqtHRs/LZ8W0cmvqTC9af0DgW7ou30eprSvPBm4iguL+00zVbyxWfUwOWeBAaNYN3qvWVoylDvTBvO8Uq0Qydn01hUrBXkOu2/McBRt30PqPEbbxycMIetR94kpzk1yEj6IX0ZrLYShAhG41vI8BWGcdbRNFe7DAeCLrgchO1tVuHUi8fa+G/Fi/tNPalOOuNb720GwSP2WDxEWcZFZX9r4qbi33menOl0EI5Gmt0QttHFYDJtxKvQn+1WCGm6nSIxdd45s61ZJ6BuqE8mr8LUpqrCAjKFwrl39bDiXLIzYm40ASw1vuej0p2yubgCloVrUeC6xaQ15rPIDGzZsxTRi4sXc99ItCXTY+jT8FMSUQ=
Content-Type: multipart/alternative; boundary="_000_C50763F7125E4BB7B08F385ACF0F3A22ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e4673066-88f4-485b-3887-08d695dbb5a4
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Feb 2019 20:00:19.4706 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR11MB3746
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.12, xch-aln-002.cisco.com
X-Outbound-Node: rcdn-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/hUVCH9jGP3MUBlzLLwNJoZqcFb0>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2019 20:00:53 -0000

Hi Rob,
I’ve taken all your comments. However, I’ve deferred adding the examples as this is best done with confd and I don’t have time to get that all setup right now.
Thanks,
Acee

From: Robert Wilton <rwilton@cisco.com>
Date: Monday, February 18, 2019 at 6:19 AM
To: Jeff Tantsura <jefftant.ietf@gmail.com>, Routing WG <rtgwg@ietf.org>, Routing WG <rtgwg-chairs@ietf.org>, "draft-acee-rtgwg-yang-rib-extend@ietf.org" <draft-acee-rtgwg-yang-rib-extend@ietf.org>
Subject: Re: WG Adoption for "RIB YANG Data Model" - draft-acee-rtgwg-yang-rib-extend
Resent-From: <alias-bounces@ietf.org>
Resent-To: Acee Lindem <acee@cisco.com>, Yingzhen Qu <yingzhen.qu@huawei.com>
Resent-Date: Monday, February 18, 2019 at 6:19 AM


Support.

I think that it is important for IETF to continue to work towards complete YANG models for managing network devices, and I see this work as another part of that.

To the authors, please may I also suggest:
1) Referencing RFC 8340 for the tree diagram text in section 4.  E.g. the current explanation text could be replaced with something like:

   The tree associated with the "ietf-rib-extensions" module follows.  The

   meaning of the symbols can be found in [RFC8340].

2) Perhaps adding the full tree output (i.e. inc the nodes from RFC8349) into an appendix.  As long as it is not too verbose, seeing the entire structure can be helpful for folks checking completeness, and for understanding the structure.

3) Adding some examples to the appendix.  No need to do every augmentation where the same groupings are being used, but seeing the output can greatly help the reader properly understand the structure and relationship between the data described in the model.

Thanks,
Rob


On 15/02/2019 19:18, Jeff Tantsura wrote:
Dear RTGWG,

The authors have requested the RTGWG to adopt draft-acee-rtgwg-yang-rib-extend
as the working group documents.

The authors have addressed the comments raised.

Please indicate support or no-support by March 3rd, 2019.

If you are listed as a document author or contributor please
respond to this email stating of whether or not you are aware of
any relevant IPR. The response needs to be sent to the RTGWG
mailing list. The document will not advance to the next stage
until a response has been received from each author and each
individual that has contributed to the document.

Cheers,
Jeff



_______________________________________________

rtgwg mailing list

rtgwg@ietf.org<mailto:rtgwg@ietf.org>

https://www.ietf.org/mailman/listinfo/rtgwg

v2.23.0 | Report a Bug | By Email