RFC 8529 on YANG Data Model for Network Instances
rfc-editor@rfc-editor.org Thu, 07 March 2019 03:59 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 648721313EF; Wed, 6 Mar 2019 19:59:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 yTx5n6pGRo6B; Wed, 6 Mar 2019 19:59:28 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 566201313FD; Wed, 6 Mar 2019 19:59:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0C03AB82514; Wed, 6 Mar 2019 19:59:23 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8529 on YANG Data Model for Network Instances
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, rtgwg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190307035923.0C03AB82514@rfc-editor.org>
Date: Wed, 06 Mar 2019 19:59:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/JhA23DoJxNwoXxe_h9AqXEKIP84>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2019 03:59:34 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8529
Title: YANG Data Model for Network Instances
Author: L. Berger,
C. Hopps,
A. Lindem,
D. Bogdanovic,
X. Liu
Status: Standards Track
Stream: IETF
Date: March 2019
Mailbox: lberger@labn.net,
chopps@chopps.org,
acee@cisco.com,
ivandean@gmail.com,
xufeng.liu.ietf@gmail.com
Pages: 44
Characters: 76775
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rtgwg-ni-model-12.txt
URL: https://www.rfc-editor.org/info/rfc8529
DOI: 10.17487/RFC8529
This document defines a network instance module. This module can be
used to manage the virtual resource partitioning that may be present
on a network device. Examples of common industry terms for virtual
resource partitioning are VPN Routing and Forwarding (VRF) instances
and Virtual Switch Instances (VSIs).
The YANG data model in this document conforms to the Network
Management Datastore Architecture (NMDA) defined in RFC 8342.
This document is a product of the Routing Area Working Group 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