Received-SPF: Pass (protection.outlook.com: domain of Aviatnet.com designates
 192.147.115.54 as permitted sender)
 receiver=protection.outlook.com; 
 client-ip=192.147.115.54; helo=mail-send.aviatnet.com;
From: Alex Campbell <Alex.Campbell@Aviatnet.com>
To: "i2rs@ietf.org" <i2rs@ietf.org>
Thread-Topic: [i2rs] RFC 8431 on A YANG Data Model for the Routing Information
 Base (RIB)
Thread-Index: AQHUVe5cLGgpm6Sm6Uy4MnXkU+j/xw==
Date: Wed, 26 Sep 2018 23:12:14 +0000
Message-ID: <1538003535558.58948@Aviatnet.com>
References: <20180926165205.39838B811AB@rfc-editor.org>
In-Reply-To: <20180926165205.39838B811AB@rfc-editor.org>
Accept-Language: en-NZ, en-US
Content-Language: en-NZ
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 Sep 2018 23:12:15.7372 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 2904a56c-0448-4ab9-95d9-08d624057fd8
X-MS-Exchange-CrossTenant-Id: 8d7d22b9-3890-4eef-95a6-a226e64151be
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=8d7d22b9-3890-4eef-95a6-a226e64151be; Ip=[192.147.115.54]; 
 Helo=[mail-send.aviatnet.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR2201MB1110
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/jUfjllstAlvJoavBF5dyaWTru3k>
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: Wed, 26 Sep 2018 23:12:28 -0000

Hi,=0A=
=0A=
I noticed that all of the data in this YANG model (routing-instance and eve=
rything inside it) is configuration data.=0A=
=0A=
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.=0A=
=0A=
=0A=
=0A=
=0A=
________________________________________=0A=
From: i2rs <i2rs-bounces@ietf.org> on behalf of rfc-editor@rfc-editor.org <=
rfc-editor@rfc-editor.org>=0A=
Sent: Thursday, 27 September 2018 4:52 a.m.=0A=
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org=0A=
Cc: drafts-update-ref@iana.org; i2rs@ietf.org; rfc-editor@rfc-editor.org=0A=
Subject: EXTERNAL: [i2rs] RFC 8431 on A YANG Data Model for the Routing Inf=
ormation Base (RIB)=0A=
=0A=
A new Request for Comments is now available in online RFC libraries.=0A=
=0A=
=0A=
        RFC 8431=0A=
=0A=
        Title:      A YANG Data Model for=0A=
                    the Routing Information Base (RIB)=0A=
        Author:     L. Wang,=0A=
                    M. Chen,=0A=
                    A. Dass,=0A=
                    H. Ananthakrishnan,=0A=
                    S. Kini,=0A=
                    N. Bahadur=0A=
        Status:     Standards Track=0A=
        Stream:     IETF=0A=
        Date:       September 2018=0A=
        Mailbox:    wang_little_star@sina.com,=0A=
                    mach.chen@huawei.com,=0A=
                    dass.amit@gmail.com,=0A=
                    hari@netflix.com,=0A=
                    sriganeshkini@gmail.com,=0A=
                    nitin_bahadur@yahoo.com=0A=
        Pages:      71=0A=
        Characters: 118915=0A=
        Updates/Obsoletes/SeeAlso:   None=0A=
=0A=
        I-D Tag:    draft-ietf-i2rs-rib-data-model-15.txt=0A=
=0A=
        URL:        https://www.rfc-editor.org/info/rfc8431=0A=
=0A=
        DOI:        10.17487/RFC8431=0A=
=0A=
This document defines a YANG data model for the Routing Information=0A=
Base (RIB) that aligns with the Interface to the Routing System=0A=
(I2RS) RIB information model.=0A=
=0A=
This document is a product of the Interface to the Routing System Working G=
roup of the IETF.=0A=
=0A=
This is now a Proposed Standard.=0A=
=0A=
STANDARDS TRACK: This document specifies an Internet Standards Track=0A=
protocol for the Internet community, and requests discussion and suggestion=
s=0A=
for improvements.  Please refer to the current edition of the Official=0A=
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the=
=0A=
standardization state and status of this protocol.  Distribution of this=0A=
memo is unlimited.=0A=
=0A=
This announcement is sent to the IETF-Announce and rfc-dist lists.=0A=
To subscribe or unsubscribe, see=0A=
  https://www.ietf.org/mailman/listinfo/ietf-announce=0A=
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist=0A=
=0A=
For searching the RFC series, see https://www.rfc-editor.org/search=0A=
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk=0A=
=0A=
Requests for special distribution should be addressed to either the=0A=
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless=0A=
specifically noted otherwise on the RFC itself, all RFCs are for=0A=
unlimited distribution.=0A=
=0A=
=0A=
The RFC Editor Team=0A=
Association Management Solutions, LLC=0A=
=0A=
=0A=
_______________________________________________=0A=
i2rs mailing list=0A=
i2rs@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/i2rs=0A=