Skip to main content

NMDA protocol operation Backwards-Compatibility with Legacy Devices
draft-wu-netconf-nmda-compatibility-01

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Qin Wu , Chong Feng
Last updated 2019-09-10 (Latest revision 2019-03-09)
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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 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.

Authors

Qin Wu
Chong Feng

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