Re: [Netconf] [Technical Errata Reported] RFC6241 (4856)

I kind of agree with Andy and Juergen.

Mehmet

Benoit Claise <bclaise@cisco.com> schrieb am Di., 20. Dez. 2016, 12:38:

> OK, thanks Andy and Jürgen.
>
> Regards, B.
>
> Hi,
>
> this should be rejected.
> The changed text implies that different configurations are present,
> each derived from some unspecified subset of modules.
> This is not correct.
>
>
> Andy
>
>
> On Mon, Dec 19, 2016 at 2:57 AM, Benoit Claise <bclaise@cisco.com> wrote:
>
> Dear all,
>
> Please let me know what you think of this errata.
>
> Regards, Benoit.
>
> The following errata report has been submitted for RFC6241,
> "Network Configuration Protocol (NETCONF)".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6241&eid=4856
>
> --------------------------------------
> Type: Technical
> Reported by: frank feng <frank.fengchong@huawei.com>
>
> Section: 7.2
>
> Original Text
> -------------
> config:  A hierarchy of configuration data as defined by one of
>           the device's data models.  The contents MUST be placed in an
>           appropriate namespace, to allow the device to detect the
>           appropriate data model, and the contents MUST follow the
>           constraints of that data model, as defined by its capability
>           definition.  Capabilities are discussed in Section 8.
>
> Corrected Text
> --------------
> config:  A hierarchy of configuration data as defined by one or more of
>           the device's data models.  The contents MUST be placed in an
>           appropriate namespace, to allow the device to detect the
>           appropriate data model, and the contents MUST follow the
>           constraints of that data model, as defined by its capability
>           definition.  Capabilities are discussed in Section 8.
>
> Notes
> -----
>
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC6241 (draft-ietf-netconf-4741bis-10)
> --------------------------------------
> Title               : Network Configuration Protocol (NETCONF)
> Publication Date    : June 2011
> Author(s)           : R. Enns, Ed., M. Bjorklund, Ed., J. Schoenwaelder,
> Ed., A. Bierman, Ed.
> Category            : PROPOSED STANDARD
> Source              : Network Configuration
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
> .
>
>
>
>
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>
-- 
Cheers,
Mehmet