IETF ForCES Logical Function Block (LFB) Subsidiary Management
draft-khs-forces-lfb-subsidiary-management-05

Document Type Replaced Internet-Draft (forces WG)
Last updated 2015-10-14 (latest revision 2015-01-14)
Replaced by draft-ietf-forces-lfb-subsidiary-management
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-forces-lfb-subsidiary-management
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-khs-forces-lfb-subsidiary-management-05.txt

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 (vumip1@gmail.com)
Evangelos Haleplidis (ehalep@ece.upatras.gr)
Jamal Hadi Salim (hadi@mojatatu.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)