Re: [i2rs] RFC 8431 on A YANG Data Model for the Routing Information Base (RIB)
Mach Chen <mach.chen@huawei.com> Thu, 27 September 2018 03:59 UTC
Return-Path: <mach.chen@huawei.com>
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 6D3E5130DE2 for <i2rs@ietfa.amsl.com>; Wed, 26 Sep 2018 20:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 yFP9y5j9Esdl for <i2rs@ietfa.amsl.com>; Wed, 26 Sep 2018 20:59:47 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 08E73130DE0 for <i2rs@ietf.org>; Wed, 26 Sep 2018 20:59:47 -0700 (PDT)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id B02445E32A859 for <i2rs@ietf.org>; Thu, 27 Sep 2018 04:59:43 +0100 (IST)
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.399.0; Thu, 27 Sep 2018 04:59:44 +0100
Received: from DGGEML510-MBS.china.huawei.com ([169.254.3.6]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0399.000; Thu, 27 Sep 2018 11:59:40 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Alex Campbell <Alex.Campbell@Aviatnet.com>, "i2rs@ietf.org" <i2rs@ietf.org>
Thread-Topic: [i2rs] RFC 8431 on A YANG Data Model for the Routing Information Base (RIB)
Thread-Index: AQHUVblTaAnkddvmZ0KZB50z4m/KTKUCqykAgADPbfA=
Date: Thu, 27 Sep 2018 03:59:40 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE2926A3B1C@dggeml510-mbs.china.huawei.com>
References: <20180926165205.39838B811AB@rfc-editor.org> <1538003535558.58948@Aviatnet.com>
In-Reply-To: <1538003535558.58948@Aviatnet.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.194.201]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/y4fzCk6tks75BVNHZ9W8Lg4K4ko>
Subject: Re: [i2rs] RFC 8431 on A YANG Data Model for the Routing Information Base (RIB)
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Sep 2018 03:59:49 -0000
Hi Alex, That's the intention, this model conforms to the NMDA architecture. Best regards, Mach > -----Original Message----- > From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Alex Campbell > Sent: Thursday, September 27, 2018 7:12 AM > To: i2rs@ietf.org > Subject: Re: [i2rs] RFC 8431 on A YANG Data Model for the Routing > Information Base (RIB) > > Hi, > > I noticed that all of the data in this YANG model (routing-instance and > everything inside it) is configuration data. > > Is this model intended to require the use of NMDA (RFC 8342)? Without > NMDA, I don't see how the client can retrieve non-static routes. > > > > > ________________________________________ > From: i2rs <i2rs-bounces@ietf.org> on behalf of rfc-editor@rfc-editor.org > <rfc-editor@rfc-editor.org> > Sent: Thursday, 27 September 2018 4:52 a.m. > To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org > Cc: drafts-update-ref@iana.org; i2rs@ietf.org; rfc-editor@rfc-editor.org > Subject: EXTERNAL: [i2rs] RFC 8431 on A YANG Data Model for the Routing > Information Base (RIB) > > A new Request for Comments is now available in online RFC libraries. > > > RFC 8431 > > Title: A YANG Data Model for > the Routing Information Base (RIB) > Author: L. Wang, > M. Chen, > A. Dass, > H. Ananthakrishnan, > S. Kini, > N. Bahadur > Status: Standards Track > Stream: IETF > Date: September 2018 > Mailbox: wang_little_star@sina.com, > mach.chen@huawei.com, > dass.amit@gmail.com, > hari@netflix.com, > sriganeshkini@gmail.com, > nitin_bahadur@yahoo.com > Pages: 71 > Characters: 118915 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-i2rs-rib-data-model-15.txt > > URL: https://www.rfc-editor.org/info/rfc8431 > > DOI: 10.17487/RFC8431 > > This document defines a YANG data model for the Routing Information Base > (RIB) that aligns with the Interface to the Routing System > (I2RS) RIB information model. > > This document is a product of the Interface to the Routing System Working > Group of the IETF. > > This is now a Proposed Standard. > > STANDARDS TRACK: This document specifies an Internet Standards Track > protocol for the Internet community, and requests discussion and > suggestions for improvements. Please refer to the current edition of the > Official Internet Protocol Standards (https://www.rfc-editor.org/standards) > for the standardization state and status of this protocol. Distribution of this > memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > https://www.ietf.org/mailman/listinfo/ietf-announce > https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see https://www.rfc-editor.org/search For > downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk > > Requests for special distribution should be addressed to either the author of > the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted > otherwise on the RFC itself, all RFCs are for unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > > _______________________________________________ > i2rs mailing list > i2rs@ietf.org > https://www.ietf.org/mailman/listinfo/i2rs > > _______________________________________________ > i2rs mailing list > i2rs@ietf.org > https://www.ietf.org/mailman/listinfo/i2rs