Virtualization of the Forwarding Plane Devices with ForCES
draft-haleplidis-forces-virtualization-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Evangelos Haleplidis , Odysseas Koufopavlou , Spyros Denazis | ||
Last updated | 2013-04-25 (Latest revision 2012-10-22) | ||
RFC stream | (None) | ||
Intended RFC status | (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
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 provides a formal way to represent the capabilities, state, and configuration of forwarding elements within the context of the ForCES protocol, so that control elements (CEs) can control the FEs accordingly. 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 ForCES model provides the necessary abstractions to natively support virtualization of the forwarding plane. This documents describes a formal approach to model the necessary parameters required for defining and managing virtual network forwarding planes to create virtual network elements.
Authors
Evangelos Haleplidis
Odysseas Koufopavlou
Spyros Denazis
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)