[netconf] New Version Notification for draft-ma-netconf-with-system-01.txt

["maqiufang (A)" <[e-mail]>]

Hi, all:
We have submitted a draft: https://www.ietf.org/archive/id/draft-ma-netconf-with-system-01.txt

Just a little bit background why we wrote this draft.
In many situations, the client needs to get system configuration. 
However, not all server implementations treat system configuration data the same way. 
Besides, the duplicated system configured data item needs to be created and overridden by the client every time  the client wants a reference, which can be quite inconvenient.

Therefore, we define a  capability-based extension to the NETCONF protocol that allows the client to identify how system configuration are processed by the server, and also define a new mechanism for client control of server processing of system configuration data.

For more details please review the draft, any suggestions and comments would be welcome.

Qiufang Ma(on behalf of authors)


-----邮件原件-----
发件人: [e-mail] [mailto:[e-mail]] 
发送时间: 2020年11月2日 20:26
收件人: Fengchong (frank) <[e-mail]>; Fengchong (frank) <[e-mail]>; maqiufang (A) <[e-mail]>
主题: New Version Notification for draft-ma-netconf-with-system-01.txt


A new version of I-D, draft-ma-netconf-with-system-01.txt
has been successfully submitted by Qiufang Ma and posted to the IETF repository.

Name:		draft-ma-netconf-with-system
Revision:	01
Title:		With System Capability for NETCONF
Document date:	2020-11-02
Group:		Individual Submission
Pages:		23
URL:            https://www.ietf.org/archive/id/draft-ma-netconf-with-system-01.txt
Status:         https://datatracker.ietf.org/doc/draft-ma-netconf-with-system/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ma-netconf-with-system
Htmlized:       https://tools.ietf.org/html/draft-ma-netconf-with-system-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ma-netconf-with-system-01

Abstract:
   The NETCONF protocol [RFC6241] defines ways to read configuration and
   state data from a NETCONF server.  In some cases, a client-configured
   data item refers to a non-existent system generated data item
   (e.g.,the auto-create interfaces ("eth1") is not yet present).  In
   many situations, the system configured data item doesn't need to be
   know to the client and client-configured data item will automatically
   be removed from the operational state datastore and thus only appear
   in the intended datastore if client-configured data item doesn't
   exist.  In other situations system configured data item needs to be
   known and overriden by the client.  Not all server implementations
   treat the system configuration data in the same way.  This document
   defines a capability-based extension to the NETCONF protocol that
   allows the NETCONF client to identify how system configuration are
   processed by the server, and also defines a new mechanism for client
   control of server processing of system configuration data.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat