NMDA protocol operation Backwards-Compatibility with Legacy Devices

Document Type Expired Internet-Draft (individual)
Last updated 2019-09-10 (latest revision 2019-03-09)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


NMDA architectural framework eliminates the need to duplicate data structures to provide separate configuration and operational state sections and uses different datastores and new protocol operations to distinct configuration from operation state. However when non-NMDA clients communicate with NMDA aware server, it is not clear whether the NMDA aware server can use existing operation to return the same results with <rpc-reply> as non-NMDA-aware server does. This document identifies some of the major challenges, and provides solutions that are able to mitigate those challenges and smooth the migration towards NMDA deployment.


Qin Wu (bill.wu@huawei.com)
Chong Feng (frank.fengchong@huawei.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)