Requirements for Peer Mounting of YANG subtrees from Remote Datastores
draft-voit-netmod-peer-mount-requirements-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Eric Voit , Alexander Clemm , Sander Mertens | ||
| Last updated | 2015-09-11 (Latest revision 2015-03-10) | ||
| Replaced by | draft-voit-netmod-yang-mount-requirements | ||
| RFC stream | (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
Network integrated applications want simple ways to access YANG objects and subtrees which might be distributed across network. Performance requirements may dictate that it is unaffordable for a subset of these applications to go through existing centralized management brokers. For such applications, development complexity must be minimized. Specific aspects of complexity developers want to ignore include: o whether authoritative information is actually sourced from remote datastores (as well as how to get to those datastores), o whether such information has been locally cached or not, o whether there are zero, one, or more controllers asserting ownership of information, and o whether there are interactions with other applications concurrently running elsewhere The solution requirements described in this document detail what is needed to support application access to authoritative network YANG objects from controllers (star) or peering network devices (mesh) in such a way to meet these goals.
Authors
Eric Voit
Alexander Clemm
Sander Mertens
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)