[netconf] Wrong example in RFC 8040 Section 3.1

[Henning Rogge <[e-mail]>]

Hi,

I think the second example in section 3.1 "Root Resource Discovery" of
RFC 8040 is wrong (it is just the first example repeated):

> In this example, the client would use the path "/restconf" as the
>  RESTCONF root resource.
>
>   Example returning /top/restconf:

but then the example for "/.well-known/host-meta" follows.

I would expect something like in Appendix B.1.1.:

> The client may then retrieve the top-level API resource, using the
> root resource "/restconf".
>
>    GET /restconf HTTP/1.1
>    Host: example.com
>    Accept: application/yang-data+json

> The server might respond as follows:

>      HTTP/1.1 200 OK
>      Date: Thu, 26 Jan 2017 20:56:30 GMT
>      Server: example-server
>      Content-Type: application/yang-data+json
>
>      {
>        "ietf-restconf:restconf" : {
>          "data" : {},
>          "operations" : {},
>          "yang-library-version" : "2016-06-21"
>        }
>      }

Is it correct to report data/operations always with an empty
dictionary for this root query, even if there are data/operations
available?

Henning Rogge