IETF ForCES Logical Function Block (LFB) Subsidiary Management
draft-khs-forces-lfb-subsidiary-management-05
| Document | Type |
Replaced Internet-Draft
(forces WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bhumip Khasnabish , Evangelos Haleplidis , Jamal Hadi Salim | ||
| Last updated | 2015-10-14 (Latest revision 2015-01-14) | ||
| Replaced by | draft-ietf-forces-lfb-subsidiary-management | ||
| 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-lfb-subsidiary-management | |
| 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
Deployment experience has demonstrated the value of using the Forwarding and Control Element Separation (ForCES) architecture to manage resources other than packet forwarding. In that spirit, the Forwarding Element Manager (FEM) is modelled by creating a Logical Functional Block (LFB) to represent its functionality. We refer to this LFB as the FE Configuration (FEC) LFB. A Control Element (CE) that controls a Forwarding Element's (FE) resources can also manage its configuration via the FEC LFB. This document introduces the FEC LFB, an LFB that specifies the configuration parameters of an FE.
Authors
Bhumip Khasnabish
Evangelos Haleplidis
Jamal Hadi Salim
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)