Hi Alex, That's the intention, this model conforms to the NMDA architecture.
Best regards, Mach > -----Original Message----- > From: i2rs [mailto:[email protected]] On Behalf Of Alex Campbell > Sent: Thursday, September 27, 2018 7:12 AM > To: [email protected] > 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 <[email protected]> on behalf of [email protected] > <[email protected]> > Sent: Thursday, 27 September 2018 4:52 a.m. > To: [email protected]; [email protected] > Cc: [email protected]; [email protected]; [email protected] > 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: [email protected], > [email protected], > [email protected], > [email protected], > [email protected], > [email protected] > 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 [email protected]. 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 > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs > > _______________________________________________ > i2rs mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
