OpFlex Control Protocol
draft-smith-opflex-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael Smith , Robert Edward Adams , Mike Dvorkin , Youcef Laribi , Vijoy Pandey , Pankaj Garg , Nik Weidenbacher | ||
| Last updated | 2018-02-11 (Latest revision 2016-04-25) | ||
| RFC stream | (None) | ||
| Intended RFC status | Informational | ||
| 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
The OpFlex architecture provides a distributed control system based on a declarative policy information model. The policies are defined at a logically centralized policy repository (PR) and enforced within a set of distributed policy elements (PE). The PR communicates with the subordinate PEs using the OpFlex Control protocol. This protocol allows for bidirectional communication of policy, events, statistics, and faults. This document defines the OpFlex Control Protocol.
Authors
Michael Smith
Robert Edward Adams
Mike Dvorkin
Youcef Laribi
Vijoy Pandey
Pankaj Garg
Nik Weidenbacher
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)