[netmod] FW: I-D Action: draft-ietf-netmod-system-config-05.txt

Hi, all

This version reflects the outcome of the interim we had last month:

1.       the "origin" issue

*         The current document explicitly states that system configuration copied from <system> into <running> have its origin value being reported as "intended" and update the examples accordingly

*         Also, update the definition of "intended" origin identity in 8342 to allow a subset of configuration in <intended> to use "system" as origin value

*         The current document states data migration is out-of-scope except that gives a couple of implementation examples in section 4.2 (please feel free to propose text if you have better suggestion)

2.       validity of <running> alone

*         The current document is silent on this point. Related statements which requires referenced system nodes must be copied into <running> are removed.

3.       Other updates

*         Usage examples refinement, e.g., fix validation errors, remove redundancy for conciseness

The authors believe all open issues have been resolved now and thus ready for WGLC, but would really also appreciate any review and feedback from the WG.

Thanks a lot!

Best Regards,

Qiufang

-----Original Message-----
From: netmod [mailto:netmod-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Wednesday, February 21, 2024 4:35 PM
To: i-d-announce@ietf.org
Cc: netmod@ietf.org
Subject: [netmod] I-D Action: draft-ietf-netmod-system-config-05.txt

Internet-Draft draft-ietf-netmod-system-config-05.txt is now available. It is a work item of the Network Modeling (NETMOD) WG of the IETF.

   Title:   System-defined Configuration

   Authors: Qiufang Ma

            Qin Wu

            Feng Chong

   Name:    draft-ietf-netmod-system-config-05.txt

   Pages:   41

   Dates:   2024-02-21

Abstract:

   This document defines how a management client and server handle YANG-

   modeled configuration data that is defined by the server itself.  The

   system-defined configuration can be referenced (e.g. leafref) by

   configuration explicitly created by a client.

   The Network Management Datastore Architecture (NMDA) defined in RFC

   8342 is updated with a read-only conventional configuration datastore

   called "system" to hold system-defined configuration.

   As an alternative to clients explicitly copying referenced system-

   defined configuration into the target configuration datastore (e.g.,

   <running>) so that the datastore is valid, a "resolve-system"

   parameter is defined to allow the server acting as a "system client"

   to copy referenced system nodes automatically.  This solution enables

   clients manipulating the target configuration datastore (e.g.,

   <running>) to reference nodes defined in <system>, override system-

   provided values, and configure descendant nodes of system-defined

   configuration.

   This document updates RFC 8342, RFC 6241, RFC 8526 and RFC 8040.

The IETF datatracker status page for this Internet-Draft is:

https://datatracker.ietf.org/doc/draft-ietf-netmod-system-config/

There is also an HTMLized version available at:

https://datatracker.ietf.org/doc/html/draft-ietf-netmod-system-config-05

A diff from the previous version is available at:

https://author-tools.ietf.org/iddiff?url2=draft-ietf-netmod-system-config-05

Internet-Drafts are also available by rsync at:

rsync.ietf.org::internet-drafts

_______________________________________________

netmod mailing list

netmod@ietf.org<mailto:netmod@ietf.org>

https://www.ietf.org/mailman/listinfo/netmod