Hi, all

In the "system-defined configuration(draft-ma-netmod-with-system)" work, an 
optional datastore named "system" is introduced to hold non-deletable system 
configurations.
We define that if a server implements <intended>, <system> MUST be merged into 
<intended>.  So there is the cases that the clients can fetch <intended> and 
<intended> contains merged <system>.
The question is should we extend the "with-origin" parameter to support 
<intended>? The possible considerations for following two choices:

     *   "with-origin" parameter should be supported for <intended>
        *   It may be helpful for a client to fetch <intended> to understand a 
certain data node is from <running> or from <intended>
     *   There is no need for <intended> to support "with-origin"
        *   We already have <operational> to provide the origin for a 
particular data node
Any thoughts on this?


Best Regards,
Qiufang Ma

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to