Re: [Netconf] Representing URLs

[Andy Bierman <[e-mail]>]

Hi,

You have raised an important RESTCONF issue, which is the
client processing of server resource URIs.  I think the
client should be able to use the Location header URI for
all CRUD access to the data resource.

That's why the /restconf/config and /restconf/operational split
is broken. In order to retrieve operational data, the client
has to parse the URI and change it -- not too REST-ful ;-)

I think there should be one YANG data root: /restconf/data.
For RESTCONF, the ETag and Last-Modified headers are
only affected by configuration data resources.  The client
will have to add a query parameter to retrieve config=false
data, so it can also be aware that ETag and Last-Modified
are not affected by config=false data nodes.


Andy