title: Attributes sequencing in Netconf <edit-config> operation
body: <p>My device wants attribute X to be set before attribute Y. How do we implement it in an NMS/EMS?</p>
  <p>My understanding is that irrespective of the protocol being used such as Netconf, SNMP, etc, my NMS has to send 2 SET/EDIT PDUs. But, ConfD Kick Start Guide mentioned that NMS doesn’t need to bother with the sequencing. How is that possible?</p>
  <p>I have pasted ConfD Kick Start Guide below.</p>
  <p>From this perspective, any requirements that certain parameters must be specified on the same command line, or must be sent in separate PDUs, or that attribute X must be sent before attribute Y are just pointless bottlenecks in the flow of ideas from the manager to device...... With a transactional interface, the network management application doesn’t need to bother with this serialization, sequencing or error recovery. With a suitable encoding like NETCONF, the whole idea can also be transferred directly, without any need to break it down into individual commands.</p>