%% You should probably cite draft-voit-netmod-yang-mount-requirements instead of this I-D.
@techreport{voit-netmod-peer-mount-requirements-03,
    number =    {draft-voit-netmod-peer-mount-requirements-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-voit-netmod-peer-mount-requirements/03/},
    author =    {Eric Voit and Alexander Clemm and Sander Mertens},
    title =     {{Requirements for mounting of local and remote YANG subtrees}},
    pagetotal = 21,
    year =      2015,
    month =     sep,
    day =       14,
    abstract =  {Network integrated applications want simple ways to reference and access YANG objects and subtrees. These simplifications might include aliasing of local YANG information. These simplifications might include remote referencing of YANG information distributed across network. For such applications, development complexity must be minimized. Specific aspects of complexity developers want to ignore include: o whether multiple aliases and paths for the same information are exposed on a single device, o whether authoritative information is actually sourced from local or remote datastores, o the overhead of session establishment and maintenance which is needed in order to access information on remote datastores, o whether objects have been locally cached or not, and o whether there is a mix of controllers, NMSs, and/or CLI which have access permission to update the primary copy of a particular object. The solution requirements described in this document detail what is needed to support application access to authoritative network YANG objects locally (via aliasing), or remotely from controllers or peering network devices in such a way to meet these goals.},
}