RFC 7729: Forwarding and Control Element Separation (ForCES) Logical Functional Block (LFB) Subsidiary Management
In plain English — editorial summary, not part of the RFC
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 modeled by creating a Logical Functional Block (LFB) to represent its functionality. We refer to this LFB as the Subsidiary Mechanism (SM) LFB. A Control Element (CE) that controls a Forwarding Element's (FE) resources can also manage its configuration via the SM LFB. This document introduces the SM LFB class, an LFB class that specifies the configuration parameters of an FE. The configuration parameters include new LFB class loading and CE associations; they also provide manipulation of debug mechanisms along with a general purpose attribute definition to describe configuration information.
Document record
- Document ID
- RFC7729
- Published
- December 2015
- Authors
- B. Khasnabish; E. Haleplidis; J. Hadi Salim
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6956Forwarding and Control Element Separation (ForCES) Logical Function Block (LFB) LibraryCurrent
June 2013
- RFC 8013Forwarding and Control Element Separation (ForCES) Inter-FE Logical Functional Block (LFB)Current
February 2017
- RFC 7409Forwarding and Control Element Separation (ForCES) Packet ParallelizationCurrent
November 2014
- RFC 7408Forwarding and Control Element Separation (ForCES) Model ExtensionCurrent
November 2014
- RFC 7391Forwarding and Control Element Separation (ForCES) Protocol ExtensionsCurrent
October 2014
- RFC 7121High Availability within a Forwarding and Control Element Separation (ForCES) Network ElementUpdated
February 2014
- RFC 5811SCTP-Based Transport Mapping Layer (TML) for the Forwarding and Control Element Separation (ForCES) ProtocolCurrent
March 2010
- RFC 3654Requirements for Separation of IP Control and ForwardingCurrent
December 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?