%% You should probably cite draft-wu-netconf-nmda-compatibility-01 instead of this revision.
@techreport{wu-netconf-nmda-compatibility-00,
    number =    {draft-wu-netconf-nmda-compatibility-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-wu-netconf-nmda-compatibility/00/},
    author =    {Qin Wu and Chong Feng},
    title =     {{NMDA Backwards-Compatibility with Legacy Devices}},
    pagetotal = 10,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {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 a server needs to support both NMDA client and non-NMDA clients, it is not clear whether a NMDA compliant server can use existing operation to return the same results with \textless{}rpc-reply\textgreater{} 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.},
}