Received: by mx.ietf.org (Postfix) id 51EF74B;
	Wed, 16 Sep 2026 23:05:55 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rfc-editor.org;
	s=mail; t=1789599955;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding;
	bh=Z1EFdZWKyyvM9YM9yLBbwkbdwrK1my4o51OYE6lAmpI=;
	b=dLmaaWYFRssbBBT0/LuTnipvxaywzFr9lol94NhNfTvjMK2Mr58fJOtU8jbbC2YT4KR0OG
	OzliVsiMGnsLA4y9O/St+VrB3PsS4//XNTfiHkG7rAE6vDpvHgFcwe8LVqKBFxBhaBb41A
	95kN+Bl8DrFlO5KCoZydrSNRsy5leB0=
Authentication-Results: ORIGINATING;
	auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=rfc-editor@rfc-editor.org
Received: from celery-677557546b-7bffc (gaia.k8s.ietf.org [4.156.85.76])
	by mail2.ietf.org (Postfix) with ESMTP id F29F81397207A;
	Wed, 16 Sep 2026 16:05:54 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: RFC 10016 on System-Defined Configuration
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Wed, 16 Sep 2026 23:05:54 -0000
message-id: <178959995485.10.8905452511500547068@rfc-editor.org>
Message-ID-Hash: G2KGQJI3GC5SLNOTDZFYHF6BM5AJCVG6
X-Message-ID-Hash: G2KGQJI3GC5SLNOTDZFYHF6BM5AJCVG6
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop;
 banned-address; header-match-ietf-announce.ietf.org-0; emergency;
 member-moderation; nonmember-moderation; administrivia; implicit-dest;
 max-recipients; max-size; news-moderation; no-subject; digests;
 suspicious-header
CC: netmod@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/ietf-announce/gLEUGNCrpcFoWgGzKBE_OXLyFGM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

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

        RFC 10016

        Title:      System-Defined Configuration
        Author:     Q. Ma, Ed.,
                    Q. Wu,
                    C. Feng
        Status:     Proposed Standard
        Stream:     IETF
        Date:       September 2026
        Mailbox:    maqiufang1@huawei.com,
                    bill.wu@huawei.com,
                    fengchongllly@gmail.com
        Pages:      30
        Updates:    RFC 8342


        I-D Tag:    draft-ietf-netmod-system-config-20

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

        DOI:        10.17487/RFC10016

The Network Management Datastore Architecture (NMDA) in RFC 8342 defines several 
configuration datastores holding configuration. The contents of these configuration 
datastores are controlled by clients. This document introduces the concept of a 
system configuration datastore holding configuration controlled by the system on 
which a server is running. The system configuration can be referenced (e.g., leafref) 
by configuration explicitly created by clients.

This document updates RFC 8342.

This document is a product of the Network Modeling Working Group of the IETF.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. 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/series/rfc-download/

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
