[rfc-dist] RFC 9196 on YANG Modules Describing Capabilities for Systems and Datastore Update Notifications
rfc-editor@rfc-editor.org Thu, 17 February 2022 21:32 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B48093A12FF for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 17 Feb 2022 13:32:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.9
X-Spam-Level:
X-Spam-Status: No, score=-7.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 XBm9U-PrwKqJ for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 17 Feb 2022 13:32:29 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B27CD3A12EB for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 17 Feb 2022 13:32:29 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D19F86AAF0; Thu, 17 Feb 2022 13:32:27 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 499) id 595596AAC4; Thu, 17 Feb 2022 13:32:27 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, netconf@ietf.org
Message-Id: <20220217213227.595596AAC4@rfc-editor.org>
Date: Thu, 17 Feb 2022 13:32:27 -0800
Subject: [rfc-dist] RFC 9196 on YANG Modules Describing Capabilities for Systems and Datastore Update Notifications
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9196
Title: YANG Modules Describing Capabilities for
Systems and Datastore Update Notifications
Author: B. Lengyel,
A. Clemm,
B. Claise
Status: Standards Track
Stream: IETF
Date: February 2022
Mailbox: balazs.lengyel@ericsson.com,
ludwig@clemm.org,
benoit.claise@huawei.com
Pages: 22
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-netconf-notification-capabilities-21.txt
URL: https://www.rfc-editor.org/info/rfc9196
DOI: 10.17487/RFC9196
This document defines two YANG modules, "ietf-system-capabilities"
and "ietf-notification-capabilities".
The module "ietf-system-capabilities" provides a placeholder
structure that can be used to discover YANG-related system
capabilities for servers. The module can be used to report capability
information from the server at runtime or at implementation time by
making use of the YANG instance data file format.
The module "ietf-notification-capabilities" augments
"ietf-system-capabilities" to specify capabilities related to
"Subscription to YANG Notifications for Datastore Updates" (RFC
8641).
This document is a product of the Network Configuration 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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org