RFC 8342 on Network Management Datastore Architecture (NMDA)
rfc-editor@rfc-editor.org Fri, 16 March 2018 21:29 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA0D712D86D; Fri, 16 Mar 2018 14:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rcYSzlBaJOd4; Fri, 16 Mar 2018 14:29:32 -0700 (PDT)
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 EDE03126FB3; Fri, 16 Mar 2018 14:29:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9B6C8B80CA7; Fri, 16 Mar 2018 14:29:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8342 on Network Management Datastore Architecture (NMDA)
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: <20180316212929.9B6C8B80CA7@rfc-editor.org>
Date: Fri, 16 Mar 2018 14:29:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Kg6RsXRo-gKKyRMEn51-vOcyRu4>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2018 21:29:51 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8342
Title: Network Management Datastore Architecture (NMDA)
Author: M. Bjorklund,
J. Schoenwaelder,
P. Shafer,
K. Watsen,
R. Wilton
Status: Standards Track
Stream: IETF
Date: March 2018
Mailbox: mbj@tail-f.com,
j.schoenwaelder@jacobs-university.de,
phil@juniper.net,
kwatsen@juniper.net,
rwilton@cisco.com
Pages: 44
Characters: 79301
Updates: RFC 7950
I-D Tag: draft-ietf-netmod-revised-datastores-10.txt
URL: https://www.rfc-editor.org/info/rfc8342
DOI: 10.17487/RFC8342
Datastores are a fundamental concept binding the data models written
in the YANG data modeling language to network management protocols
such as the Network Configuration Protocol (NETCONF) and RESTCONF.
This document defines an architectural framework for datastores based
on the experience gained with the initial simpler model, addressing
requirements that were not well supported in the initial model. This
document updates RFC 7950.
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
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