Re: [netmod] Question on RFC8342 + RESTCONF extension (draft-ietf-netconf-nmda-restconf)

[Juergen Schoenwaelder <[e-mail]>]

On Tue, Dec 11, 2018 at 02:17:07PM +0000, Seehofer, Markus wrote:
> Hello,
> 
> Reading RFC 8342 along with draft-ietf-netconf-nmda-restconf-05 I've some questions or comprehension problems with the text.
> 
> 
> 1.       RFC 8342 (NMDA)
> Chapter 5.3.  The Operational State Datastore (<operational>) says:
> "The operational state datastore (<operational>) is a read-only datastore .... "
> Chapter 6.2. Invocation of Actions and RPCs says:
> "Actions are always invoked in the context of the operational state datastore. The node for which the action is invoked MUST exist in the operational state datastore."
> 
> Chapter 3.1 in https://tools.ietf.org/pdf/draft-ietf-netconf-nmda-restconf-05 says:
> "YANG actions can only be invoked in {+restconf}/ds/ietf-datastores:operational."
> 
> Question: How can one invoke an action in a as read-only defined datastore? Or am I missing something?

Why do you expect that a datastore has to be writable in order to
invoke an action? RFC 7950 has the example of a ping action tied to an
interface. (You ping a remote system from that specific interface.)
In general, actions are understood as being tied to real resources and
hence to the operational datastore. (For example, you can't ping from
an interface that is configured but not physically present.)

> 2.       The NMDA is a huge step forward for NC and RC, thanks for that. NMDA in combination with the new RESTCONF extensions let one now select one of the named datastores
> in RFC 8342. Reading the RFC and draft I'm still missing (or even more overlook I guess) the following. RFC 8040 Chapter 4.5 says:
> "A PUT on the datastore resource is used to replace the entire contents of the datastore...". So does this mean one can have the same behavior as in NETCONF where you can copy
> the "running" config to "startup" or "candidate" config to "running" if a RESTCONF server would support them? Is there any example how this would look like if it is allowed?

A PUT does not really get you there, to copy a datastore to another
you want an operation on the server.
 
> 3.       Typo in https://tools.ietf.org/pdf/draft-ietf-netconf-nmda-restconf-05 Chapter 3.1 "the server would implement the resource {+restconf}/ds/example- ds-ephemeral:ds-ephemeral."
> There is a space in between "example-" and "ds-ephemeral:ds-ephemeral".
 
Lets hope we get this fixed with the help of the RFC editor.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <https://www.jacobs-university.de/>