[netmod] Fwd: RFC 8022 on A YANG Data Model for Routing Management

Benoit Claise <bclaise@cisco.com> Thu, 10 November 2016 05:56 UTC

Return-Path: <bclaise@cisco.com>
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 B15D212948F for <netmod@ietfa.amsl.com>; Wed, 9 Nov 2016 21:56:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.018
X-Spam-Status: No, score=-16.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id MRI4zgpMkSfL for <netmod@ietfa.amsl.com>; Wed, 9 Nov 2016 21:56:54 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF611129476 for <netmod@ietf.org>; Wed, 9 Nov 2016 21:56:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9395; q=dns/txt; s=iport; t=1478757413; x=1479967013; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=CUqMjHMleovvl+lmgS2vVCR/bhdw+4pkMTOsHs5Q9+0=; b=S6jB0f2qh+FTRUBNzCyzma0kD4lGrQMKgbn+bSO1pE+lyzYQmTaAsTPo LqPIFrDRU7AKJBpXaWQLBKZwrJEYcfqCTOG+6OCoBYbJMcneZOIGczJ7k nH8bURlNv7QB7FJQHqPqWjGu9dcMrCszWbE0N4PlxWHiFpPlO9MP34Lv0 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AyAgCpCiRY/xbLJq1dGwEBAQMBAQEJA?= =?us-ascii?q?QEBgzABAQEBAXcDKVONPZcLjzyFGoIJHgEKhTFKAoJQFAECAQEBAQEBAWIohGE?= =?us-ascii?q?BAQEEAQEBSyAbHAMBAg0iJwocAggGDQYCAQEQBgECBIg7DrJJPosIAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEdhj6BfYJdgT0Sglo/hUEFmWpIhjiKF4FuhHSDGYYfhzW?= =?us-ascii?q?CJoNdhAceN2UQCxMJgyyBbT00AYVpgi0BAQE?=
X-IronPort-AV: E=Sophos;i="5.31,617,1473120000"; d="scan'208,217";a="649831507"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Nov 2016 05:56:48 +0000
Received: from [] (ams-bclaise-8915.cisco.com []) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id uAA5ulAV020136 for <netmod@ietf.org>; Thu, 10 Nov 2016 05:56:48 GMT
References: <20161110041836.0B46FB80F29@rfc-editor.org>
To: NETMOD Working Group <netmod@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
X-Forwarded-Message-Id: <20161110041836.0B46FB80F29@rfc-editor.org>
Message-ID: <6d6205de-72c5-145a-9a5f-4586641d9875@cisco.com>
Date: Thu, 10 Nov 2016 06:56:48 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <20161110041836.0B46FB80F29@rfc-editor.org>
Content-Type: multipart/alternative; boundary="------------20B47C2AF45D71B038E18D18"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/kA5_UG0rK12FGg9S3aviCTGrkK0>
Subject: [netmod] Fwd: RFC 8022 on A YANG Data Model for Routing Management
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 10 Nov 2016 05:56:55 -0000

Excellent news before the IETF meeting.
This set of YANG modules is the foundation for all routing modules.
As you can see here <http://www.claise.be/ietf-routing.png>there are 
many dependencies for the ietf-routing YANG module.

Many thanks to Lada, Acee, the chairs, and the community for this very 
long journey.

Regards, Benoit

-------- Forwarded Message --------
Subject: 	[netmod] RFC 8022 on A YANG Data Model for Routing Management
Date: 	Wed, 9 Nov 2016 20:18:36 -0800 (PST)
From: 	rfc-editor@rfc-editor.org
To: 	ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: 	drafts-update-ref@iana.org, netmod@ietf.org, rfc-editor@rfc-editor.org

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

         RFC 8022

         Title:      A YANG Data Model for
                     Routing Management
         Author:     L. Lhotka, A. Lindem
         Status:     Standards Track
         Stream:     IETF
         Date:       November 2016
         Mailbox:    lhotka@nic.cz,
         Pages:      64
         Characters: 115083
         Updates/Obsoletes/SeeAlso:   None

         I-D Tag:    draft-ietf-netmod-routing-cfg-25.txt

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

         DOI:        http://dx.doi.org/10.17487/RFC8022

This document contains a specification of 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.

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

netmod mailing list