I personally like it, and will refer people to the wiki. Its far
quicker/easier than finding a random RFC.
One suggestion might be to make the parts that do overlap, refer back to the
RFC from the wiki in order to
keep the document more dynamic in case there are errata changes in the future
and to keep from
having to maintain 2 copies of the same information.
—Tom
> On Jun 5, 2016:5:42 PM, at 5:42 PM, Andy Bierman <[email protected]> wrote:
>
> Hi,
>
> I don't really agree with idea that I2RS agents pick which
> YANG statements they will implement, but I think there is
> a way to handle this correctly in the datastore framework.
>
> The proposed enumeration for server validation
> capabilities (e.g., full, XPath, leafref) is not really needed.
> This enum is too course-grained to be useful.
>
> IMO it is better to say the server MAY do YANG validation
> on the ephemeral datastore. Whether or not the server uses
> data from the ephemeral datastore is left as an implementation detail.
> The server could use invalid input parameters or ignore them
> or reject them in the first place.
>
> The client needs to check operational state to know if/when the
> ephemeral data was applied to the system.
>
>
>
> Andy
>
> _______________________________________________
> i2rs mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/i2rs
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
