[netmod] Clarifications re RFC 8342 NMDA

[Jonathan <[e-mail]>]

Hi,

I have been reading through RFC 8342 and have a number of questions I 
couldn't resolve after a couple of passes through. Can anyone advise?
The RFC states "The startup configuration datastore may not be supported 
by all protocols or implementations", "the candidate configuration 
datastore may not be supported by all protocols or implementations" and 
"<running> MUST be supported if the device can be configured via 
conventional configuration datastores". I can find no explicit guidance 
on:The intended configuration datastore: The RFC does state, "Whenever 
data is written to <running>, the server MUST also immediately update 
and validate <intended>." Is <intended> mandatory for NMDA-supporting 
servers that support <running>?The operational state datastore: The RFC 
does state it is "a read-only datastore that consists of all "config 
true" and "config false" nodes defined in the datastore's schema" and 
that "the datastore schema for <operational> MUST be a superset of the 
combined datastore schema used in all configuration datastores ...". Is 
<operational> mandatory for NMDA-supporting servers?RFC 8525, section 1 
states, "For backwards compatibility, an NMDA-supporting server SHOULD 
populate the deprecated "/modules-state" tree in a backwards-compatible 
manner."That suggests an NMDA-supporting server SHOULD be 
backwards-compatible with a non-NMDA-supporting client. Is that 
correct?Can an MMDA-supporting client be backwards-compatible with a 
non-NMDA-supporting server?I can't find any mention of YANG version 1 in 
RFC 8342. Is it safe to assume NMDA is compatible with YANG version 1 
modules?
Thanks,

Jonathan