[netmod] RFC 8349 on A YANG Data Model for Routing Management (NMDA Version)

rfc-editor@rfc-editor.org Tue, 20 March 2018 03:25 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A34E812D94E; Mon, 19 Mar 2018 20:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ardeFk1riw7o; Mon, 19 Mar 2018 20:25:14 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E5C912D779; Mon, 19 Mar 2018 20:25:14 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A7B03B80C59; Mon, 19 Mar 2018 20:25:06 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, netmod@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180320032506.A7B03B80C59@rfc-editor.org>
Date: Mon, 19 Mar 2018 20:25:06 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/HRqrPva2T8FjFDt0YPnlxDHFoSg>
Subject: [netmod] =?utf-8?q?RFC_8349_on_A_YANG_Data_Model_for_Routing_Mana?= =?utf-8?q?gement_=28NMDA_Version=29?=
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 03:25:17 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8349

        Title:      A YANG Data Model for 
                    Routing Management (NMDA Version) 
        Author:     L. Lhotka,
                    A. Lindem,
                    Y. Qu
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    lhotka@nic.cz, 
        Pages:      80
        Characters: 147002
        Obsoletes:  RFC 8022

        I-D Tag:    draft-ietf-netmod-rfc8022bis-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8349

        DOI:        10.17487/RFC8349

This document specifies three YANG modules and one submodule.
Together, they form the core routing data model that serves as a
framework for configuring and managing a routing subsystem.  It is
expected that these modules will be augmented by additional YANG
modules defining data models for control-plane protocols, route
filters, and other functions.  The core routing data model provides
common building blocks for such extensions -- routes, Routing
Information Bases (RIBs), and control-plane protocols.

The YANG modules in this document conform to the Network Management
Datastore Architecture (NMDA).  This document obsoletes RFC 8022.

This document is a product of the Network Modeling 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

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