RFC 7317 on A YANG Data Model for System Management
rfc-editor@rfc-editor.org Thu, 07 August 2014 19:24 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 445031ABB27 for <ietf-announce@ietfa.amsl.com>; Thu, 7 Aug 2014 12:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 Ro9I1duHJUku for <ietf-announce@ietfa.amsl.com>; Thu, 7 Aug 2014 12:24:07 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 106EA1ABB2B for <ietf-announce@ietf.org>; Thu, 7 Aug 2014 12:24:07 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3713C18B57F; Thu, 7 Aug 2014 12:22:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7317 on A YANG Data Model for System Management
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140807192235.3713C18B57F@rfc-editor.org>
Date: Thu, 07 Aug 2014 12:22:35 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/z6RtouXm2o65DTqptu6zHmyaChY
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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: Thu, 07 Aug 2014 19:24:10 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7317
Title: A YANG Data Model for
System Management
Author: A. Bierman, M. Bjorklund
Status: Standards Track
Stream: IETF
Date: August 2014
Mailbox: andy@yumaworks.com,
mbj@tail-f.com
Pages: 35
Characters: 60119
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-netmod-system-mgmt-16.txt
URL: https://www.rfc-editor.org/rfc/rfc7317.txt
This document defines a YANG data model for the configuration and
identification of some common system properties within a device
containing a Network Configuration Protocol (NETCONF) server. This
document also includes data node definitions for system
identification, time-of-day management, user management, DNS resolver
configuration, and some protocol operations for system management.
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 Internet
Official Protocol Standards (STD 1) 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/rfc.html
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