ForCES Inter-FE LFB
draft-joachimpillai-forces-interfelfb-05
| Document | Type |
Replaced Internet-Draft
(forces WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Damascane M. Joachimpillai , Jamal Hadi Salim | ||
| Last updated | 2015-10-14 (Latest revision 2014-12-04) | ||
| Replaced by | draft-ietf-forces-interfelfb | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-forces-interfelfb | |
| Consensus boilerplate | Unknown | ||
| 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
Forwarding and Control Element Separation (ForCES) defines an architectural framework and associated protocols to standardize information exchange between the control plane and the forwarding plane in a ForCES Network Element (ForCES NE). RFC5812 has defined the ForCES Model which provides a formal way to represent the capabilities, state, and configuration of forwarding elements(FEs) within the context of the ForCES protocol. More specifically, the model describes the logical functions that are present in an FE, what capabilities these functions support, and how these functions are or can be interconnected. The control elements (CEs) can control the FEs using the ForCES model definition. The ForCES WG charter has been extended to allow the LFB topology to be across FEs. This documents describes a non-intrusive way to extend the LFB topology across FEs.
Authors
Damascane M. Joachimpillai
Jamal Hadi Salim
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)