On Wed, Mar 11, 2020 at 06:58:53PM +0100, Benoit Claise wrote:
> Juergen,
>
> On on side, Balazs mentions:
>
> 4+ people asked me explicitly to state this similarity during the
> development of the draft.
>
> The current text is:
>
> P2 Instance data shall reuse existing encoding rules for YANG
> defined data. Its format will be similar to the response of a
> NETCONF <get> operation or the RESTCONF response to a GET method
> invocation on the (unified) datastore resource.
>
> This modification is based on your feedback:
>
> Well, then the correct wording would be "similar to the response of a
> NETCONF <get> operation or the RESTCONF response to a GET method
> invocation on the (unified) datastore resource". Sounds complex and I
> still prefer the text to be agnostic to specific operations
>
> On the other side, you insist now on removing the latter sentence.
> Could you propose a similar sentence that would satisfy your concern?
>
The new sentence is this:
[Yeah, I suggested removal so the new sentence is empty.]
/js
PS: I do not mind if somewhere there is an example stated. But even
then I would prefer something like this:
For example, instance data of the <running> configuration
datastore is encoded similar to the response of a NETCONF
<get-config> operation on the <running> datastore or a GET
method invocation on the <running> datastore resource and it
will be embedded into a container together with the metadata
describing the instance data.
(I prefer to avoid NETCONF GET and the RESTCONF unified datastore
since they have issues. But if people insist on an example using
operations that have issues, I will keep my mouth shut.)
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
