Re: [Netconf] I-D Action: draft-wu-netconf-restconf-factory-restore-00.txt

Hi,

I have a couple of additional comments:

I have an intuitive idea of what factory default configuration is, and
many devices offer means for activating it. I see it as a useful
addition to enable RESTCONF clients to activate it, if the device
supports such a function.

However, I don't understand this text in sec. 2.1:

   The factory default setting datastore assumes the place of the
   datastore resource as defined in [RFC8040] Section 3.4.  This means
   that the entire datastore resources inside the "{+restconf}/data"
   subtree correspond to data instances in the factory default setting
   datastore.  Therefore, the contents of the factory default setting
   datastore can be retrieved by means of the GET method as specified in
   [RFC8040] and but can not be modified by means of PUT methods as
   specified in [RFC8040].

This looks like the factory default datastore is what the RESTCONF
client edits, which makes no sense to me.

In fact, this paragraph is almost literally copied from
draft-lhotka-netconf-restconf-transactions-00. In my draft, though, it
is intentional that the user's staging datastore appears exactly as the
"unified" datastore in RESTCONF. It is IMO not the case in your draft.

If the factory default configuration is made accessible to the RESTCONF
client (which is definitely useful), it should be a read-only datastore,
and the resource representing it should be something like

    {+restconf}/ds/ietf-restconf-restore:factory-default

Section 2 says:

   A RESTCONF server implementing this document ... is implemented in a
   device that does not have a NETCONF server [RFC8040].

On the other hand, the descriptions of all features defined in the YANG
module require each feature to be set if it corresponding NETCONF
capability is advertised. This seems contradictory to the above
statement.

Thanks, Lada

Qin Wu <bill.wu@huawei.com> writes:

> Hi, All:
> We submit a new I-D to discuss "Factory default Setting Capability for RESTCONF"
> https://tools.ietf.org/html/draft-wu-netconf-restconf-factory-restore-00
> The abstract:
>    This document defines capability based extension to RESTCONF protocol
>    that allows RESTCONF client to configure newly deployed devices with
>    just its preconfigured initial state (i.e., factory default settings)
>    during zero touch bootstrapping process or restore the configuration
>    to its preconfigured initial state or system restore point either
>    during device rooting process or at the time of system fatal error or
>    malfunction.
> Your comments and suggestions are welcome.
>
> -Qin
> -----邮件原件-----
> 发件人: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] 代表 internet-drafts@ietf.org
> 发送时间: 2018年6月27日 19:29
> 收件人: i-d-announce@ietf.org
> 主题: I-D Action: draft-wu-netconf-restconf-factory-restore-00.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>         Title           : Factory default Setting Capability for RESTCONF
>         Authors         : Qin Wu
>                           Ye Niu
> 	Filename        : draft-wu-netconf-restconf-factory-restore-00.txt
> 	Pages           : 11
> 	Date            : 2018-06-27
>
> Abstract:
>    This document defines capability based extension to RESTCONF protocol
>    that allows RESTCONF client to configure newly deployed devices with
>    just its preconfigured initial state (i.e., factory default settings)
>    during zero touch bootstrapping process or restore the configuration
>    to its preconfigured initial state or system restore point either
>    during device rooting process or at the time of system fatal error or
>    malfunction.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-wu-netconf-restconf-factory-restore/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-wu-netconf-restconf-factory-restore-00
> https://datatracker.ietf.org/doc/html/draft-wu-netconf-restconf-factory-restore-00
>
>
> 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.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf

-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67