From nobody Wed May 2 00:44:17 2018 Return-Path: X-Original-To: i2rs@ietf.org Delivered-To: i2rs@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F1401252BA; Wed, 2 May 2018 00:44:11 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: i2rs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.79.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152524705146.11321.11516984014587259536@ietfa.amsl.com> Date: Wed, 02 May 2018 00:44:11 -0700 Archived-At: Subject: [i2rs] I-D Action: draft-ietf-i2rs-rib-info-model-16.txt X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2018 07:44:12 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Interface to the Routing System WG of the IETF. Title : Routing Information Base Info Model Authors : Nitin Bahadur Sriganesh Kini Jan Medved Filename : draft-ietf-i2rs-rib-info-model-16.txt Pages : 28 Date : 2018-05-02 Abstract: Routing and routing functions in enterprise and carrier networks are typically performed by network devices (routers and switches) using a routing information base (RIB). Protocols and configuration push data into the RIB and the RIB manager installs state into the hardware for packet forwarding. This draft specifies an information model for the RIB to enable defining a standardized data model, and it was used by the IETF's I2RS WG to design the I2RS RIB data model. It is being published to record the higher-level informational model decisions for RIBs so that other developers of RIBs may benefit from the design concepts. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-info-model/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-i2rs-rib-info-model-16 https://datatracker.ietf.org/doc/html/draft-ietf-i2rs-rib-info-model-16 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-rib-info-model-16 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/ From nobody Wed May 2 00:49:42 2018 Return-Path: X-Original-To: i2rs@ietfa.amsl.com Delivered-To: i2rs@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 645B4126C2F for ; Wed, 2 May 2018 00:49:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.165 X-Spam-Level: X-Spam-Status: No, score=0.165 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FSL_HELO_BARE_IP_2=1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_NUMERIC_HELO=1.164, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 VcXhxsw9bftz for ; Wed, 2 May 2018 00:49:40 -0700 (PDT) Received: from sonic307-33.consmr.mail.ir2.yahoo.com (sonic307-33.consmr.mail.ir2.yahoo.com [87.248.110.58]) (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 D8E4E1252BA for ; Wed, 2 May 2018 00:49:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1525247378; bh=BLdPA87rX88Lag4JM14ZgNU0JQKx+6Gb0dcctjLEp94=; h=Date:Subject:From:To:References:In-Reply-To:From:Subject; b=dV/Ik7Fkm/Yo6xsPETkhhLGPch5vdzrVQRMnkoGZgFGDxewFFkgYwgJeg1Nj1xUOllvHe2W5LlCnR6PPs+UzAGGQ1iA1xNT3LYexhi8blQ+PGfdYr+QqRJwFpR6dRdB1/GUsS3FFTDHCG3M9NfZKX4Tdy6pXsLk0nCS6lDzxNlLEI3gFWh3fy787pwd4eg88FjUo8cw5e4nTFxeAjyT8VEkoVimWjEUKT/5ofm+P3P5GqSR3ZQB5qPB99RCqzbT2zfP/G5dC0w2+EyQvZg7V0DOXlTr8DFQRyR27UqZtfX9hdJQvGBW9MFyDoaGtxuAUV7pfFNt3CHuXGei/FGy26g== X-YMail-OSG: GnH81XwVM1kDw79co7at.uUNk7RoXAk0nRpFlRS9G5S6HRRz5ugEVVt1.QEAlzG jbSP0q3oZ.VL8PJj5xS0AtBk7WEkf6Us4LSE8bNJ2o2jMd6edy3qps2S5ccPvl8CBbvpiuqoiGXx OrcgJXZ.vlNJNR5tNVcrtmtyPmMbYI0J2kNv4cQge_HjsJ7eGtwtjRFOEMYvDFcd5F253K8LdYDA HsA1ceuemlPRB_iT2PlqVubEKPJUbrGnREupSSbrpE2vdNHmnkJuvj5beQi3bhyX.uJ9xH4zbDtJ uGY1QYYAR6KljxQeB1D0.VbVbVD1fsnoWZdrkALLuNNbxBtVuTxN1u3Us_nfazLct8wKPAcYRTgJ P6y6xcbpSCVQ2QgT9wnCnKQz4AlivdTfyNXaw9JjjmKv5eAvrVFv46TlCj5AKWnH8NnkHqNUTjBl FRash5_yDrxJdciVhAJSI0MRb9QK1DC9t8AWeEUibGt37VOLuqfQPeMFP.TGoCRTQJfd3._8rNU7 OuiBj8Aa8bd1IsRMeipbVxRybg41891_pWjq0_sHq_qwNOmmO0Kei6G6awW3dTzxN.E0x09ij3M9 zxyYPxPLJPEYpilBSMc9TNKe_zPRyeoSruNj9q__yB2Re.w.MydouGRD4zlAcCdbJtsiHgpQH3cO kfEHaYBwwLZtRCwNJs2OARAp_sZij1GS.Gv.2 Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.ir2.yahoo.com with HTTP; Wed, 2 May 2018 07:49:38 +0000 Received: from 212.98.105.70 (EHLO [100.80.194.74]) ([212.98.105.70]) by smtp426.mail.ir2.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 7fb5cf323538ecc92eaf488fd4d35c6b for ; Wed, 02 May 2018 07:45:36 +0000 (UTC) User-Agent: Microsoft-MacOutlook/10.9.0.180116 Date: Wed, 02 May 2018 09:45:34 +0200 From: Nitin Bahadur To: "i2rs@ietf.org" Message-ID: <050E7FB6-859C-41D2-9003-1A3C126E9EA0@yahoo.com> Thread-Topic: New Version Notification for draft-ietf-i2rs-rib-info-model-16.txt References: <152524705177.11321.12484619828885710616.idtracker@ietfa.amsl.com> In-Reply-To: <152524705177.11321.12484619828885710616.idtracker@ietfa.amsl.com> Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable Archived-At: Subject: Re: [i2rs] New Version Notification for draft-ietf-i2rs-rib-info-model-16.txt X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2018 07:49:41 -0000 This version address IESG comments wrt document wording/language and fixes = some errors in the draft. =EF=BB=BFOn 5/2/18, 9:44 AM, "internet-drafts@ietf.org" wrote: =20 A new version of I-D, draft-ietf-i2rs-rib-info-model-16.txt has been successfully submitted by Nitin Bahadur and posted to the IETF repository. =20 Name: draft-ietf-i2rs-rib-info-model Revision: 16 Title: Routing Information Base Info Model Document date: 2018-05-02 Group: i2rs Pages: 28 URL: https://www.ietf.org/internet-drafts/draft-ietf-i2rs-ri= b-info-model-16.txt Status: https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-in= fo-model/ Htmlized: https://tools.ietf.org/html/draft-ietf-i2rs-rib-info-mo= del-16 Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-i2rs-r= ib-info-model Diff: https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2rs-rib-i= nfo-model-16 =20 Abstract: Routing and routing functions in enterprise and carrier networks are typically performed by network devices (routers and switches) using = a routing information base (RIB). Protocols and configuration push data into the RIB and the RIB manager installs state into the hardware for packet forwarding. This draft specifies an information model for the RIB to enable defining a standardized data model, and it was used by the IETF's I2RS WG to design the I2RS RIB data model. It is being published to record the higher-level informational model decisions for RIBs so that other developers of RIBs may benefit from the design concepts. =20 = =20 =20 =20 Please note that it may take a couple of minutes from the time of submi= ssion until the htmlized version and diff are available at tools.ietf.org. =20 The IETF Secretariat =20 =20 From nobody Wed May 2 06:32:33 2018 Return-Path: X-Original-To: i2rs@ietf.org Delivered-To: i2rs@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 75C671277BB; Wed, 2 May 2018 06:32:28 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Ladislav Lhotka To: Cc: i2rs@ietf.org, ietf@ietf.org, draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.79.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152526794842.11272.8213634409290285584@ietfa.amsl.com> Date: Wed, 02 May 2018 06:32:28 -0700 Archived-At: Subject: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04 X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2018 13:32:28 -0000 Reviewer: Ladislav Lhotka Review result: Ready This draft and YANG modules contained therein fit into the framework of I2RS network topology models. I have no substantial comments, from the YANG point of view this document is ready to be published. Comments and questions: 1. What is the purpose of the 'flag-type' type and 'flag-identity' identity? There are no identities derived from the latter. 2. Some descriptions overuse capitalization. For example, instead of 'VLAN Name' I would suggest 'VLAN name'. 3. An example of an instance document in an appendix would be very helpful. From nobody Thu May 3 19:08:52 2018 Return-Path: X-Original-To: i2rs@ietfa.amsl.com Delivered-To: i2rs@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 849DD126DCA; Thu, 3 May 2018 19:08:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 MwWJeuJHME3m; Thu, 3 May 2018 19:08:45 -0700 (PDT) Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 E6274127286; Thu, 3 May 2018 19:08:44 -0700 (PDT) Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 9144717BADC42; Fri, 4 May 2018 03:08:41 +0100 (IST) Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 4 May 2018 03:08:42 +0100 Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.29]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0361.001; Fri, 4 May 2018 10:08:38 +0800 From: "Dongjie (Jimmy)" To: Ladislav Lhotka , "yang-doctors@ietf.org" CC: "i2rs@ietf.org" , "ietf@ietf.org" , "draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org" Thread-Topic: Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04 Thread-Index: AQHT4hoIU9osNzC9q0uYjvWwfuv4MqQd3dlg Date: Fri, 4 May 2018 02:08:37 +0000 Message-ID: <76CD132C3ADEF848BD84D028D243C92798440318@NKGEML515-MBS.china.huawei.com> References: <152526794842.11272.8213634409290285584@ietfa.amsl.com> In-Reply-To: <152526794842.11272.8213634409290285584@ietfa.amsl.com> Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.130.151.75] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: Re: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04 X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2018 02:08:46 -0000 SGkgTGFkYSwgDQoNClRoYW5rcyBhIGxvdCBmb3IgeW91ciByZXZpZXcgY29tbWVudHMuIFBsZWFz ZSBzZWUgc29tZSByZXBsaWVzIGlubGluZToNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0t LQ0KPiBGcm9tOiBMYWRpc2xhdiBMaG90a2EgW21haWx0bzpsaG90a2FAbmljLmN6XQ0KPiBTZW50 OiBXZWRuZXNkYXksIE1heSAwMiwgMjAxOCA5OjMyIFBNDQo+IFRvOiB5YW5nLWRvY3RvcnNAaWV0 Zi5vcmcNCj4gQ2M6IGkycnNAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7DQo+IGRyYWZ0LWlldGYt aTJycy15YW5nLWwyLW5ldHdvcmstdG9wb2xvZ3kuYWxsQGlldGYub3JnDQo+IFN1YmplY3Q6IFlh bmdkb2N0b3JzIGVhcmx5IHJldmlldyBvZiBkcmFmdC1pZXRmLWkycnMteWFuZy1sMi1uZXR3b3Jr LXRvcG9sb2d5LTA0DQo+IA0KPiBSZXZpZXdlcjogTGFkaXNsYXYgTGhvdGthDQo+IFJldmlldyBy ZXN1bHQ6IFJlYWR5DQo+IA0KPiBUaGlzIGRyYWZ0IGFuZCBZQU5HIG1vZHVsZXMgY29udGFpbmVk IHRoZXJlaW4gZml0IGludG8gdGhlIGZyYW1ld29yayBvZiBJMlJTDQo+IG5ldHdvcmsgdG9wb2xv Z3kgbW9kZWxzLiBJIGhhdmUgbm8gc3Vic3RhbnRpYWwgY29tbWVudHMsIGZyb20gdGhlIFlBTkcg cG9pbnQNCj4gb2YgdmlldyB0aGlzIGRvY3VtZW50IGlzIHJlYWR5IHRvIGJlIHB1Ymxpc2hlZC4N Cj4gDQo+IENvbW1lbnRzIGFuZCBxdWVzdGlvbnM6DQo+IA0KPiAxLiBXaGF0IGlzIHRoZSBwdXJw b3NlIG9mIHRoZSAnZmxhZy10eXBlJyB0eXBlIGFuZCAnZmxhZy1pZGVudGl0eScgaWRlbnRpdHk/ DQo+IFRoZXJlIGFyZSBubyBpZGVudGl0aWVzIGRlcml2ZWQgZnJvbSB0aGUgbGF0dGVyLg0KDQpU aGUgImZsYWctdHlwZSIgdHlwZSBpcyB1c2VkIGluIHRoZSBncm91cGluZyAibDItbmV0d29yay1h dHRyaWJ1dGVzIiwgImwyLW5vZGUtYXR0cmlidXRlcyIgYW5kICJsMi1saW5rLWF0dHJpYnV0ZXMi Lg0KDQpXaGlsZSB0aGVyZSBpcyBubyBpZGVudGl0aWVzIGRlcml2ZWQgZnJvbSB0aGUgImZsYWct aWRlbnRpdHkiLCBpdCBpcyB1c2VkIGluIHRoZSB0eXBlZGVmIGZsYWctdHlwZS4gSXMgdGhpcyBP Sz8NCg0KPiAyLiBTb21lIGRlc2NyaXB0aW9ucyBvdmVydXNlIGNhcGl0YWxpemF0aW9uLiBGb3Ig ZXhhbXBsZSwgaW5zdGVhZCBvZiAnVkxBTiBOYW1lJw0KPiBJIHdvdWxkIHN1Z2dlc3QgJ1ZMQU4g bmFtZScuDQoNClRoYW5rcyBmb3IgY2F0Y2hpbmcgdGhpcy4gV2lsbCBmaXggaW4gbmV4dCByZXZp c2lvbi4NCg0KPiAzLiBBbiBleGFtcGxlIG9mIGFuIGluc3RhbmNlIGRvY3VtZW50IGluIGFuIGFw cGVuZGl4IHdvdWxkIGJlIHZlcnkgaGVscGZ1bC4NCg0KVGhhbmtzIGZvciB5b3VyIHN1Z2dlc3Rp b24uIFdlIHdpbGwgYWRkIGFuIGV4YW1wbGUgdG8gdGhlIGFwcGVuZGl4Lg0KDQpCZXN0IHJlZ2Fy ZHMsDQpKaWUNCg0K From nobody Fri May 4 01:04:51 2018 Return-Path: X-Original-To: i2rs@ietfa.amsl.com Delivered-To: i2rs@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 175D6127444; Fri, 4 May 2018 01:04:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7 X-Spam-Level: X-Spam-Status: No, score=-7 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] 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 xdc6d_B8Miyd; Fri, 4 May 2018 01:04:47 -0700 (PDT) Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 7CDA1127869; Fri, 4 May 2018 01:04:41 -0700 (PDT) Received: from birdie (unknown [IPv6:2001:718:1a02:1::380]) by mail.nic.cz (Postfix) with ESMTPSA id F3BA360571; Fri, 4 May 2018 10:04:38 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1525421079; bh=/RrHPiQeLnt0Hx77MSSS0EH6DhWitumUckV9iHuuBBM=; h=From:To:Date; b=X/PacDswbI3U8/y46jH+yILbl5kCvBqiVF4c7/yUKcO9ro9AuoB88+RvTS9UdV1Bp q5rZqkBexAczn68ctreA0Acm9VRq2xPmMMh/2yd7utLkCQli9DkZs0U2KqqtO8xTxW BeZog9X8V4/h0Z+NsdH41LHzYyK2/fQkg+7seI/k= Message-ID: <8978121dad28df18a46b45770649e33039f5917f.camel@nic.cz> From: Ladislav Lhotka To: "Dongjie (Jimmy)" , "yang-doctors@ietf.org" Cc: "i2rs@ietf.org" , "ietf@ietf.org" , "draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org" Date: Fri, 04 May 2018 10:04:48 +0200 In-Reply-To: <76CD132C3ADEF848BD84D028D243C92798440318@NKGEML515-MBS.china.huawei.com> References: <152526794842.11272.8213634409290285584@ietfa.amsl.com> <76CD132C3ADEF848BD84D028D243C92798440318@NKGEML515-MBS.china.huawei.com> Organization: CZ.NIC Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean Archived-At: Subject: Re: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04 X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2018 08:04:50 -0000 On Fri, 2018-05-04 at 02:08 +0000, Dongjie (Jimmy) wrote: > Hi Lada, > > Thanks a lot for your review comments. Please see some replies inline: > > > -----Original Message----- > > From: Ladislav Lhotka [mailto:lhotka@nic.cz] > > Sent: Wednesday, May 02, 2018 9:32 PM > > To: yang-doctors@ietf.org > > Cc: i2rs@ietf.org; ietf@ietf.org; > > draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org > > Subject: Yangdoctors early review of draft-ietf-i2rs-yang-l2-network- > > topology-04 > > > > Reviewer: Ladislav Lhotka > > Review result: Ready > > > > This draft and YANG modules contained therein fit into the framework of I2RS > > network topology models. I have no substantial comments, from the YANG point > > of view this document is ready to be published. > > > > Comments and questions: > > > > 1. What is the purpose of the 'flag-type' type and 'flag-identity' identity? > > There are no identities derived from the latter. > > The "flag-type" type is used in the grouping "l2-network-attributes", "l2- > node-attributes" and "l2-link-attributes". > > While there is no identities derived from the "flag-identity", it is used in > the typedef flag-type. Is this OK? >From the YANG point of view it is certainly OK. Do you expect other modules to define identities derived from "flag-identity"? > > > 2. Some descriptions overuse capitalization. For example, instead of 'VLAN > > Name' > > I would suggest 'VLAN name'. > > Thanks for catching this. Will fix in next revision. > > > 3. An example of an instance document in an appendix would be very helpful. > > Thanks for your suggestion. We will add an example to the appendix. Thanks, Lada > > Best regards, > Jie > -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 From nobody Fri May 4 13:39:43 2018 Return-Path: X-Original-To: i2rs@ietfa.amsl.com Delivered-To: i2rs@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7461012D967 for ; Fri, 4 May 2018 13:39:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.945 X-Spam-Level: X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no autolearn_force=no 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 9fZLZ5hzQn4s for ; Fri, 4 May 2018 13:39:41 -0700 (PDT) Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 F165312D965 for ; Fri, 4 May 2018 13:39:40 -0700 (PDT) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=107.92.121.30; From: "Susan Hares" To: "'Dongjie \(Jimmy\)'" , "'Ladislav Lhotka'" Cc: , "'Martin Vigoureux'" References: <152526794842.11272.8213634409290285584@ietfa.amsl.com> <76CD132C3ADEF848BD84D028D243C92798440318@NKGEML515-MBS.china.huawei.com> In-Reply-To: <76CD132C3ADEF848BD84D028D243C92798440318@NKGEML515-MBS.china.huawei.com> Date: Fri, 4 May 2018 16:39:18 -0400 Message-ID: <00c001d3e3e7$f9b18e70$ed14ab50$@ndzh.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Content-Language: en-us Thread-Index: AQNe1+FL8Tl1YbLI7rTemtnvRB4QjwKKzLXooPXGsaA= X-Authenticated-User: skh@ndzh.com Archived-At: Subject: Re: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04 X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2018 20:39:42 -0000 Jie and Lada: I've recently listened to the I2RS meeting in IETF 101. Chris Hopps asked about the notifications in L2. He was asking about a more general use of the notification that might be useful in the I'm not really sure how to approach responding to his operational request - since it really impacts all topology models. My inclination is to push this draft through into RFC usage, and then to work through a "-bis" functionality. Jie - would you ask the individuals pushing for L2 model if that works for them. Lada - would you ask the Yang doctors if this is the right approach to take. Of course, this might be easier if we had versioning instead of a model name change. Sue Hares -----Original Message----- From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Dongjie (Jimmy) Sent: Thursday, May 3, 2018 10:09 PM To: Ladislav Lhotka; yang-doctors@ietf.org Cc: i2rs@ietf.org; ietf@ietf.org; draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org Subject: Re: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04 Hi Lada, Thanks a lot for your review comments. Please see some replies inline: > -----Original Message----- > From: Ladislav Lhotka [mailto:lhotka@nic.cz] > Sent: Wednesday, May 02, 2018 9:32 PM > To: yang-doctors@ietf.org > Cc: i2rs@ietf.org; ietf@ietf.org; > draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org > Subject: Yangdoctors early review of > draft-ietf-i2rs-yang-l2-network-topology-04 > > Reviewer: Ladislav Lhotka > Review result: Ready > > This draft and YANG modules contained therein fit into the framework > of I2RS network topology models. I have no substantial comments, from > the YANG point of view this document is ready to be published. > > Comments and questions: > > 1. What is the purpose of the 'flag-type' type and 'flag-identity' identity? > There are no identities derived from the latter. The "flag-type" type is used in the grouping "l2-network-attributes", "l2-node-attributes" and "l2-link-attributes". While there is no identities derived from the "flag-identity", it is used in the typedef flag-type. Is this OK? > 2. Some descriptions overuse capitalization. For example, instead of 'VLAN Name' > I would suggest 'VLAN name'. Thanks for catching this. Will fix in next revision. > 3. An example of an instance document in an appendix would be very helpful. Thanks for your suggestion. We will add an example to the appendix. Best regards, Jie _______________________________________________ i2rs mailing list i2rs@ietf.org https://www.ietf.org/mailman/listinfo/i2rs From nobody Fri May 4 14:59:10 2018 Return-Path: X-Original-To: i2rs@ietfa.amsl.com Delivered-To: i2rs@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA51D12DA16 for ; Fri, 4 May 2018 14:59:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 Xj-dnBvsomGM for ; Fri, 4 May 2018 14:59:05 -0700 (PDT) Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 66D6E12DA15 for ; Fri, 4 May 2018 14:59:05 -0700 (PDT) Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 9333EFA04C7C0; Fri, 4 May 2018 22:59:00 +0100 (IST) Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 4 May 2018 22:59:02 +0100 Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.34]) by SJCEML702-CHM.china.huawei.com ([169.254.4.62]) with mapi id 14.03.0382.000; Fri, 4 May 2018 14:58:54 -0700 From: Alexander Clemm To: Susan Hares , "Dongjie (Jimmy)" , 'Ladislav Lhotka' CC: "i2rs@ietf.org" , 'Martin Vigoureux' Thread-Topic: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04 Thread-Index: AQHT40z51UI+FgakDUmlA+7uv/OvSqQgfrAA//+fwmA= Date: Fri, 4 May 2018 21:58:54 +0000 Message-ID: <644DA50AFA8C314EA9BDDAC83BD38A2E0EB057A9@sjceml521-mbx.china.huawei.com> References: <152526794842.11272.8213634409290285584@ietfa.amsl.com> <76CD132C3ADEF848BD84D028D243C92798440318@NKGEML515-MBS.china.huawei.com> <00c001d3e3e7$f9b18e70$ed14ab50$@ndzh.com> In-Reply-To: <00c001d3e3e7$f9b18e70$ed14ab50$@ndzh.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.209.216.254] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: Re: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04 X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2018 21:59:08 -0000 One way to support notifications for topology in a generic way will be thro= ugh YANG-Push (see https://tools.ietf.org/html/draft-ietf-netconf-yang-push= -15). Configure a subscription for on-change updates against the topology = data tree. That will give applications what they need without the definiti= on of custom notifications (which can of course also still be done). --- Alex > -----Original Message----- > From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Susan Hares > Sent: Friday, May 04, 2018 1:39 PM > To: Dongjie (Jimmy) ; 'Ladislav Lhotka' > Cc: i2rs@ietf.org; 'Martin Vigoureux' > Subject: Re: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l2-n= etwork- > topology-04 >=20 > Jie and Lada: >=20 > I've recently listened to the I2RS meeting in IETF 101. >=20 > Chris Hopps asked about the notifications in L2. He was asking about a m= ore > general use of the notification that might be useful in the >=20 > I'm not really sure how to approach responding to his operational request= - since > it really impacts all topology models. My inclination is to push this dr= aft through > into RFC usage, and then to work through a "-bis" > functionality. >=20 > Jie - would you ask the individuals pushing for L2 model if that works fo= r them. >=20 > Lada - would you ask the Yang doctors if this is the right approach to ta= ke. > Of course, this might be easier if we had versioning instead of a model n= ame > change. >=20 > Sue Hares > -----Original Message----- > From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Dongjie (Jimmy) > Sent: Thursday, May 3, 2018 10:09 PM > To: Ladislav Lhotka; yang-doctors@ietf.org > Cc: i2rs@ietf.org; ietf@ietf.org; > draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org > Subject: Re: [i2rs] Yangdoctors early review of > draft-ietf-i2rs-yang-l2-network-topology-04 >=20 > Hi Lada, >=20 > Thanks a lot for your review comments. Please see some replies inline: >=20 > > -----Original Message----- > > From: Ladislav Lhotka [mailto:lhotka@nic.cz] > > Sent: Wednesday, May 02, 2018 9:32 PM > > To: yang-doctors@ietf.org > > Cc: i2rs@ietf.org; ietf@ietf.org; > > draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org > > Subject: Yangdoctors early review of > > draft-ietf-i2rs-yang-l2-network-topology-04 > > > > Reviewer: Ladislav Lhotka > > Review result: Ready > > > > This draft and YANG modules contained therein fit into the framework > > of I2RS network topology models. I have no substantial comments, from > > the YANG point of view this document is ready to be published. > > > > Comments and questions: > > > > 1. What is the purpose of the 'flag-type' type and 'flag-identity' > identity? > > There are no identities derived from the latter. >=20 > The "flag-type" type is used in the grouping "l2-network-attributes", "l2= -node- > attributes" and "l2-link-attributes". >=20 > While there is no identities derived from the "flag-identity", it is used= in the > typedef flag-type. Is this OK? >=20 > > 2. Some descriptions overuse capitalization. For example, instead of > > 'VLAN > Name' > > I would suggest 'VLAN name'. >=20 > Thanks for catching this. Will fix in next revision. >=20 > > 3. An example of an instance document in an appendix would be very > helpful. >=20 > Thanks for your suggestion. We will add an example to the appendix. >=20 > Best regards, > Jie >=20 > _______________________________________________ > i2rs mailing list > i2rs@ietf.org > https://www.ietf.org/mailman/listinfo/i2rs >=20 > _______________________________________________ > i2rs mailing list > i2rs@ietf.org > https://www.ietf.org/mailman/listinfo/i2rs From nobody Sun May 6 18:48:58 2018 Return-Path: X-Original-To: i2rs@ietf.org Delivered-To: i2rs@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B9C512D885; Sun, 6 May 2018 18:48:48 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: i2rs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.79.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152565772807.1407.14118695798570015914@ietfa.amsl.com> Date: Sun, 06 May 2018 18:48:48 -0700 Archived-At: Subject: [i2rs] I-D Action: draft-ietf-i2rs-rib-data-model-13.txt X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2018 01:48:48 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Interface to the Routing System WG of the IETF. Title : A YANG Data Model for Routing Information Base (RIB) Authors : Lixing Wang Mach(Guoyi) Chen Amit Dass Hariharan Ananthakrishnan Sriganesh Kini Nitin Bahadur Filename : draft-ietf-i2rs-rib-data-model-13.txt Pages : 69 Date : 2018-05-06 Abstract: This document defines a YANG data model for the Routing Information Base (RIB) that aligns with the I2RS RIB information model. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-i2rs-rib-data-model-13 https://datatracker.ietf.org/doc/html/draft-ietf-i2rs-rib-data-model-13 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-rib-data-model-13 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/ From nobody Sun May 6 19:09:28 2018 Return-Path: X-Original-To: i2rs@ietf.org Delivered-To: i2rs@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7800D120047; Sun, 6 May 2018 19:09:23 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: i2rs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.79.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152565896344.1427.6720410387807171507@ietfa.amsl.com> Date: Sun, 06 May 2018 19:09:23 -0700 Archived-At: Subject: [i2rs] I-D Action: draft-ietf-i2rs-rib-data-model-14.txt X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2018 02:09:23 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Interface to the Routing System WG of the IETF. Title : A YANG Data Model for Routing Information Base (RIB) Authors : Lixing Wang Mach(Guoyi) Chen Amit Dass Hariharan Ananthakrishnan Sriganesh Kini Nitin Bahadur Filename : draft-ietf-i2rs-rib-data-model-14.txt Pages : 68 Date : 2018-05-06 Abstract: This document defines a YANG data model for the Routing Information Base (RIB) that aligns with the I2RS RIB information model. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-i2rs-rib-data-model-14 https://datatracker.ietf.org/doc/html/draft-ietf-i2rs-rib-data-model-14 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-rib-data-model-14 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/ From nobody Mon May 7 19:06:10 2018 Return-Path: X-Original-To: i2rs@ietfa.amsl.com Delivered-To: i2rs@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C3DA12D874 for ; Mon, 7 May 2018 19:06:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 W81MQHQuQjBr for ; Mon, 7 May 2018 19:06:05 -0700 (PDT) Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 B18C612D871 for ; Mon, 7 May 2018 19:06:05 -0700 (PDT) Received: from lhreml705-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 5641C5B6CED69; Tue, 8 May 2018 03:06:01 +0100 (IST) Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 8 May 2018 03:06:02 +0100 Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.29]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0382.000; Tue, 8 May 2018 10:05:55 +0800 From: "Dongjie (Jimmy)" To: Susan Hares , 'Ladislav Lhotka' CC: "i2rs@ietf.org" , 'Martin Vigoureux' Thread-Topic: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04 Thread-Index: AQHT4hoIU9osNzC9q0uYjvWwfuv4MqQd3dlggAGnyACABY4zQA== Date: Tue, 8 May 2018 02:05:55 +0000 Message-ID: <76CD132C3ADEF848BD84D028D243C92798449F5E@NKGEML515-MBS.china.huawei.com> References: <152526794842.11272.8213634409290285584@ietfa.amsl.com> <76CD132C3ADEF848BD84D028D243C92798440318@NKGEML515-MBS.china.huawei.com> <00c001d3e3e7$f9b18e70$ed14ab50$@ndzh.com> In-Reply-To: <00c001d3e3e7$f9b18e70$ed14ab50$@ndzh.com> Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.130.151.75] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: Re: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04 X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2018 02:06:08 -0000 Hi Sue,=20 I agree Chris's comment is generic and applicable to all topology models, a= nd what Alex suggested could be a solution to it.=20 And your proposal looks good to us (coauthors of L2 model). Best regards, Jie > -----Original Message----- > From: Susan Hares [mailto:shares@ndzh.com] > Sent: Saturday, May 05, 2018 4:39 AM > To: Dongjie (Jimmy) ; 'Ladislav Lhotka' > Cc: i2rs@ietf.org; 'Martin Vigoureux' > Subject: RE: [i2rs] Yangdoctors early review of > draft-ietf-i2rs-yang-l2-network-topology-04 >=20 > Jie and Lada: >=20 > I've recently listened to the I2RS meeting in IETF 101. >=20 > Chris Hopps asked about the notifications in L2. He was asking about a m= ore > general use of the notification that might be useful in the >=20 > I'm not really sure how to approach responding to his operational request= - since > it really impacts all topology models. My inclination is to push this dr= aft through > into RFC usage, and then to work through a "-bis" > functionality. >=20 > Jie - would you ask the individuals pushing for L2 model if that works fo= r them. >=20 > Lada - would you ask the Yang doctors if this is the right approach to ta= ke. > Of course, this might be easier if we had versioning instead of a model n= ame > change. >=20 > Sue Hares > -----Original Message----- > From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Dongjie (Jimmy) > Sent: Thursday, May 3, 2018 10:09 PM > To: Ladislav Lhotka; yang-doctors@ietf.org > Cc: i2rs@ietf.org; ietf@ietf.org; > draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org > Subject: Re: [i2rs] Yangdoctors early review of > draft-ietf-i2rs-yang-l2-network-topology-04 >=20 > Hi Lada, >=20 > Thanks a lot for your review comments. Please see some replies inline: >=20 > > -----Original Message----- > > From: Ladislav Lhotka [mailto:lhotka@nic.cz] > > Sent: Wednesday, May 02, 2018 9:32 PM > > To: yang-doctors@ietf.org > > Cc: i2rs@ietf.org; ietf@ietf.org; > > draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org > > Subject: Yangdoctors early review of > > draft-ietf-i2rs-yang-l2-network-topology-04 > > > > Reviewer: Ladislav Lhotka > > Review result: Ready > > > > This draft and YANG modules contained therein fit into the framework > > of I2RS network topology models. I have no substantial comments, from > > the YANG point of view this document is ready to be published. > > > > Comments and questions: > > > > 1. What is the purpose of the 'flag-type' type and 'flag-identity' > identity? > > There are no identities derived from the latter. >=20 > The "flag-type" type is used in the grouping "l2-network-attributes", > "l2-node-attributes" and "l2-link-attributes". >=20 > While there is no identities derived from the "flag-identity", it is used= in the > typedef flag-type. Is this OK? >=20 > > 2. Some descriptions overuse capitalization. For example, instead of > > 'VLAN > Name' > > I would suggest 'VLAN name'. >=20 > Thanks for catching this. Will fix in next revision. >=20 > > 3. An example of an instance document in an appendix would be very > helpful. >=20 > Thanks for your suggestion. We will add an example to the appendix. >=20 > Best regards, > Jie >=20 > _______________________________________________ > i2rs mailing list > i2rs@ietf.org > https://www.ietf.org/mailman/listinfo/i2rs From nobody Mon May 7 20:49:13 2018 Return-Path: X-Original-To: i2rs@ietf.org Delivered-To: i2rs@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E9E0F127058; Mon, 7 May 2018 20:49:00 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: i2rs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.79.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152575134089.20137.18308562187856460893@ietfa.amsl.com> Date: Mon, 07 May 2018 20:49:00 -0700 Archived-At: Subject: [i2rs] I-D Action: draft-ietf-i2rs-rib-info-model-17.txt X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2018 03:49:01 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Interface to the Routing System WG of the IETF. Title : Routing Information Base Info Model Authors : Nitin Bahadur Sriganesh Kini Jan Medved Filename : draft-ietf-i2rs-rib-info-model-17.txt Pages : 28 Date : 2018-05-07 Abstract: Routing and routing functions in enterprise and carrier networks are typically performed by network devices (routers and switches) using a routing information base (RIB). Protocols and configuration push data into the RIB and the RIB manager installs state into the hardware for packet forwarding. This draft specifies an information model for the RIB to enable defining a standardized data model, and it was used by the IETF's I2RS WG to design the I2RS RIB data model. It is being published to record the higher-level informational model decisions for RIBs so that other developers of RIBs may benefit from the design concepts. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-info-model/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-i2rs-rib-info-model-17 https://datatracker.ietf.org/doc/html/draft-ietf-i2rs-rib-info-model-17 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-rib-info-model-17 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/ From nobody Tue May 8 04:51:26 2018 Return-Path: X-Original-To: i2rs@ietf.org Delivered-To: i2rs@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C50A512D962; Tue, 8 May 2018 04:51:08 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.79.1 Auto-Submitted: auto-generated Precedence: bulk Cc: i2rs@ietf.org, Susan Hares , i2rs-chairs@ietf.org, The IESG , rfc-editor@rfc-editor.org, martin.vigoureux@nokia.com, shares@ndzh.com, draft-ietf-i2rs-rib-info-model@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-ID: <152578026879.20227.14439501580232893211.idtracker@ietfa.amsl.com> Date: Tue, 08 May 2018 04:51:08 -0700 Archived-At: Subject: [i2rs] Document Action: 'Routing Information Base Info Model' to Informational RFC (draft-ietf-i2rs-rib-info-model-17.txt) X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2018 11:51:09 -0000 The IESG has approved the following document: - 'Routing Information Base Info Model' (draft-ietf-i2rs-rib-info-model-17.txt) as Informational RFC This document is the product of the Interface to the Routing System Working Group. The IESG contact persons are Alvaro Retana, Deborah Brungard and Martin Vigoureux. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-info-model/ Technical Summary Routing and routing functions in enterprise and carrier networks are typically performed by network devices (routers and switches) using a routing information base (RIB). Protocols and configuration push data into the RIB and the RIB manager installs state into the hardware for packet forwarding. This draft specifies an information model for the RIB to enable defining a standardized data model, and it was used by the IETF's I2RS WG to design the I2RS RIB data model. It is being published to record the higher-level informational model decisions for RIBs so that other developers of RIBs may benefit from the design concepts. Working Group Summary The I2RS WG and the authors have waited on the NETMOD/NETCONF WG to complete its work on revising the network management datastore architecture. Now that the latter is completed the I2RS WG believes this Document can now itself progress. Document Quality This is an informational model which helped form the draft-ietf-i2rs-rib-data-model. The document has been through repeated reviews and debates within netmod/I2rs. It is worth publishing because we see repeatly additional attempts to do a RIB model without the same thought. This model can support NMDA dynamic datastores or normal datastores. It depends on where it is mounted. Personnel Susan Hares is the Document Shepherd Martin Vigoureux is the Responsible Area Director From nobody Fri May 11 08:58:48 2018 Return-Path: X-Original-To: i2rs@ietf.org Delivered-To: i2rs@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BEEA612E8E7; Fri, 11 May 2018 08:58:42 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Suresh Krishnan To: "The IESG" Cc: draft-ietf-i2rs-rib-data-model@ietf.org, Susan Hares , i2rs-chairs@ietf.org, shares@ndzh.com, i2rs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.80.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152605432277.10664.15874614287247534864.idtracker@ietfa.amsl.com> Date: Fri, 11 May 2018 08:58:42 -0700 Archived-At: Subject: [i2rs] Suresh Krishnan's No Objection on draft-ietf-i2rs-rib-data-model-14: (with COMMENT) X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2018 15:58:44 -0000 Suresh Krishnan has entered the following ballot position for draft-ietf-i2rs-rib-data-model-14: No Objection 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 IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for addressing my DISCUSS. From nobody Sun May 13 20:43:00 2018 Return-Path: X-Original-To: i2rs@ietf.org Delivered-To: i2rs@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AE16B1289B0; Sun, 13 May 2018 20:42:53 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: i2rs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.80.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <152626937366.10074.11025651495053739425@ietfa.amsl.com> Date: Sun, 13 May 2018 20:42:53 -0700 Archived-At: Subject: [i2rs] I-D Action: draft-ietf-i2rs-rib-data-model-15.txt X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2018 03:42:54 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Interface to the Routing System WG of the IETF. Title : A YANG Data Model for Routing Information Base (RIB) Authors : Lixing Wang Mach(Guoyi) Chen Amit Dass Hariharan Ananthakrishnan Sriganesh Kini Nitin Bahadur Filename : draft-ietf-i2rs-rib-data-model-15.txt Pages : 69 Date : 2018-05-13 Abstract: This document defines a YANG data model for the Routing Information Base (RIB) that aligns with the I2RS RIB information model. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-i2rs-rib-data-model-15 https://datatracker.ietf.org/doc/html/draft-ietf-i2rs-rib-data-model-15 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-rib-data-model-15 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/ From nobody Mon May 14 07:11:21 2018 Return-Path: X-Original-To: i2rs@ietf.org Delivered-To: i2rs@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 04DBA12D87D; Mon, 14 May 2018 07:11:06 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.80.0 Auto-Submitted: auto-generated Precedence: bulk Cc: i2rs@ietf.org, Susan Hares , draft-ietf-i2rs-rib-data-model@ietf.org, i2rs-chairs@ietf.org, The IESG , martin.vigoureux@nokia.com, shares@ndzh.com, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-ID: <152630706601.10198.13203871118143243582.idtracker@ietfa.amsl.com> Date: Mon, 14 May 2018 07:11:06 -0700 Archived-At: Subject: [i2rs] Protocol Action: 'A YANG Data Model for Routing Information Base (RIB)' to Proposed Standard (draft-ietf-i2rs-rib-data-model-15.txt) X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2018 14:11:06 -0000 The IESG has approved the following document: - 'A YANG Data Model for Routing Information Base (RIB)' (draft-ietf-i2rs-rib-data-model-15.txt) as Proposed Standard This document is the product of the Interface to the Routing System Working Group. The IESG contact persons are Alvaro Retana, Deborah Brungard and Martin Vigoureux. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/ Technical Summary This document defines a YANG data model for Routing Information Base (RIB) that aligns with the I2RS RIB information model. This yang data model complies with the network management datastore architecture. It can be loaded in configuration datastores or in dynamic datastores. Working Group Summary The I2RS WG and the authors have waited on the NETMOD/NETCONF WG to complete its work on revising the network management datastore architecture. Now that the latter is completed the I2RS WG believes this Document can now itself progress. Document Quality Some early implementations of this protocol existed as far back as 3 years ago. Personnel Susan Hares is the Document Shepherd Martin Vigoureux is the Responsible Area Director From nobody Mon May 14 07:14:54 2018 Return-Path: X-Original-To: i2rs@ietfa.amsl.com Delivered-To: i2rs@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC3D12D87D for ; Mon, 14 May 2018 07:14:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.945 X-Spam-Level: X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no autolearn_force=no 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 SOuOkdnQErtO for ; Mon, 14 May 2018 07:14:46 -0700 (PDT) Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 2CBDA12785F for ; Mon, 14 May 2018 07:14:46 -0700 (PDT) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=166.176.250.254; From: "Susan Hares" To: Cc: "'Martin Vigoureux'" , "'Alia Atlas'" Date: Mon, 14 May 2018 10:14:39 -0400 Message-ID: <00e701d3eb8d$e61cce80$b2566b80$@ndzh.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdPrjbpX+EqlyfYiTLC/+/nAxINbjA== Content-Language: en-us X-Authenticated-User: skh@ndzh.com Archived-At: Subject: [i2rs] Congratulations! X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2018 14:14:53 -0000 I2RS WG:=20 Congratulations! The IESG has now approved the I2RS RIB Information = Model and Data Model. I want to thank all the members of the I2RS WG = for their years of hard work on these specifications.=20 Susan Hares=20 -----Original Message----- From: The IESG [mailto:iesg-secretary@ietf.org]=20 Sent: Monday, May 14, 2018 10:11 AM To: IETF-Announce Cc: i2rs@ietf.org; Susan Hares; draft-ietf-i2rs-rib-data-model@ietf.org; = i2rs-chairs@ietf.org; The IESG; martin.vigoureux@nokia.com; = shares@ndzh.com; rfc-editor@rfc-editor.org Subject: Protocol Action: 'A YANG Data Model for Routing Information = Base (RIB)' to Proposed Standard (draft-ietf-i2rs-rib-data-model-15.txt) The IESG has approved the following document: - 'A YANG Data Model for Routing Information Base (RIB)' (draft-ietf-i2rs-rib-data-model-15.txt) as Proposed Standard This document is the product of the Interface to the Routing System = Working Group. The IESG contact persons are Alvaro Retana, Deborah Brungard and Martin = Vigoureux. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/ Technical Summary This document defines a YANG data model for Routing Information Base (RIB) that aligns with the I2RS RIB information model. =20 This yang data model complies with the network management datastore architecture. It can be loaded in configuration datastores or in = dynamic datastores.=20 Working Group Summary The I2RS WG and the authors have waited on the NETMOD/NETCONF WG to complete its work on revising the network management datastore architecture.=20 Now that the latter is completed the I2RS WG believes this Document can now itself progress. Document Quality Some early implementations of this protocol existed as far back as 3 = years ago.=20 Personnel Susan Hares is the Document Shepherd Martin Vigoureux is the Responsible Area Director From nobody Mon May 14 14:56:47 2018 Return-Path: X-Original-To: i2rs@ietfa.amsl.com Delivered-To: i2rs@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E243712D969 for ; Mon, 14 May 2018 14:56:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.835 X-Spam-Level: X-Spam-Status: No, score=-0.835 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_NUMERIC_HELO=1.164, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 cfctkSt07QXU for ; Mon, 14 May 2018 14:56:44 -0700 (PDT) Received: from sonic317-21.consmr.mail.gq1.yahoo.com (sonic317-21.consmr.mail.gq1.yahoo.com [98.137.66.147]) (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 490B1126C2F for ; Mon, 14 May 2018 14:56:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1526335003; bh=e4zeXmWiDITabkpn1crlX0rj+I8PX1IZ4hEYC2Qfn3c=; h=Date:Subject:From:To:References:In-Reply-To:From:Subject; b=oNV2if47Tq0zdXYJ5dT3fabb6gppPNXOrNrP/0Rsy5+Pd/IOwW22TmrZ55NBj1LXYV+LoNblqFEW70ULbqNJX4tfxD0IupU1xoNrpe9g1D2bEU3RbFT5BfqCXCwocCRNyF71rIFDT26uxc7ejuwul7r6HYtZ71IK8LPC1f3JuV8CkifTsaCgDbh/d4Ui8RCqROhqQZGSwrF2uPhlkp3RvVxgsGfJzU/KBoLQnl1AUak/77fA3BS7tpXAO890fXqnBOppcM7sQLLzmlvhVjg/yVIRZzF2jwvNWXvwfETUFHdea66U0Xhm2vZtKDIxMnPFFGRPKZWQRe4SgMmkrMbp6A== X-YMail-OSG: eEQ2Ax0VM1nSYW2v_8FDyxNPApB.wOX6FpEVZdcB3XAeC3I8Wprgeq8tiNliRCM 8B9yO__HlGCeBntsULolJ2KvIIwIiQKYa5i7xV6FtJHSt.rkPafJRQLH.dZnq3jqfIsu0pzUx_5X 77g6I8GhYi1ClLcWzXg..yWKGxgG50t1tZQ9lZ1AyLTRmtnXUTXmpAWT0H3s6Jr_BwcwQNFxyUWR 0RpHPFwmQnxxRQAZBJzOwSo_KROWJy7H3O4MdPJaATGqYk3MlGYQ00owbq.gGtOLSPHzQ.J9nIV5 0Mq.VV6uUCKSIJpZtbuO5CCxWgFAPKiXbXSSfOESjikLEQGcDfrk5NRHP8_YgEkeCl1sJ7pmC7D2 BgnBnUf9ayR4R4noNsd83xtEQYxoRWnwuljm7EM6NPYcBNfnNxapaXBtvM2r.cZnfamJ5caEPQw2 rGsfp.f8B1Dt_t3jJdAGhE5juh7leWnBlsFmH3hRi6eroFh4SXeHuQokXxj.U0W69d5oUkdbWCWz 9CFNkIdp_bM_T3bBppOG6EmeQgQ4NMeKPuALfgDQFPjJPYyY65pg2dTSmeQKjM.0qtaS1UOIUKAr a9AAG58T_p0kDwWNSAq9nXhpj3EWYGEdb0gHbiy6CeXS3Lf4M7qy0HQjVUsIvQD0vpWhEnJ8uwDT 5h894zqXA Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Mon, 14 May 2018 21:56:43 +0000 Received: from 207.231.170.7 (EHLO [172.24.68.239]) ([207.231.170.7]) by smtp427.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 2a483224f01f4c424bf892220a2a2937; Mon, 14 May 2018 21:56:40 +0000 (UTC) User-Agent: Microsoft-MacOutlook/10.9.0.180116 Date: Mon, 14 May 2018 14:56:38 -0700 From: Nitin Bahadur To: Susan Hares , CC: 'Martin Vigoureux' , 'Alia Atlas' Message-ID: <21D318C1-9A2B-4C37-9A6A-528FD8604CF5@yahoo.com> Thread-Topic: [i2rs] Congratulations! References: <00e701d3eb8d$e61cce80$b2566b80$@ndzh.com> In-Reply-To: <00e701d3eb8d$e61cce80$b2566b80$@ndzh.com> Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable Archived-At: Subject: Re: [i2rs] Congratulations! X-BeenThere: i2rs@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2018 21:56:46 -0000 And special thanks to the WG chairs and ADs for shepherding this over the y= ears. Your behind the scenes effort is very much appreciated __. =EF=BB=BFOn 5/14/18, 7:15 AM, "i2rs on behalf of Susan Hares" wrote: I2RS WG:=20 =20 Congratulations! The IESG has now approved the I2RS RIB Information Mo= del and Data Model. I want to thank all the members of the I2RS WG for thei= r years of hard work on these specifications.=20 =20 Susan Hares=20 =20 -----Original Message----- From: The IESG [mailto:iesg-secretary@ietf.org]=20 Sent: Monday, May 14, 2018 10:11 AM To: IETF-Announce Cc: i2rs@ietf.org; Susan Hares; draft-ietf-i2rs-rib-data-model@ietf.org= ; i2rs-chairs@ietf.org; The IESG; martin.vigoureux@nokia.com; shares@ndzh.co= m; rfc-editor@rfc-editor.org Subject: Protocol Action: 'A YANG Data Model for Routing Information Ba= se (RIB)' to Proposed Standard (draft-ietf-i2rs-rib-data-model-15.txt) =20 The IESG has approved the following document: - 'A YANG Data Model for Routing Information Base (RIB)' (draft-ietf-i2rs-rib-data-model-15.txt) as Proposed Standard =20 This document is the product of the Interface to the Routing System Wor= king Group. =20 The IESG contact persons are Alvaro Retana, Deborah Brungard and Martin= Vigoureux. =20 A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/ =20 =20 =20 =20 =20 Technical Summary =20 This document defines a YANG data model for Routing Information Base (RIB) that aligns with the I2RS RIB information model. =20 This yang data model complies with the network management datastore architecture. It can be loaded in configuration datastores or in dyn= amic datastores.=20 =20 Working Group Summary =20 The I2RS WG and the authors have waited on the NETMOD/NETCONF WG to complete its work on revising the network management datastore architecture.=20 Now that the latter is completed the I2RS WG believes this Document can now itself progress. =20 Document Quality =20 Some early implementations of this protocol existed as far back as 3 = years ago.=20 =20 Personnel =20 Susan Hares is the Document Shepherd Martin Vigoureux is the Responsible Area Director =20 _______________________________________________ i2rs mailing list i2rs@ietf.org https://www.ietf.org/mailman/listinfo/i2rs =20