RFC 6956: Forwarding and Control Element Separation (ForCES) Logical Function Block (LFB) Library
In plain English — editorial summary, not part of the RFC
This document defines basic classes of Logical Function Blocks (LFBs) used in Forwarding and Control Element Separation (ForCES). The basic LFB classes are defined according to the ForCES Forwarding Element (FE) model and ForCES protocol specifications; they are scoped to meet requirements of typical router functions and are considered the basic LFB library for ForCES. The library includes the descriptions of the LFBs and the XML definitions.
Document record
- Document ID
- RFC6956
- Published
- June 2013
- Authors
- W. Wang; E. Haleplidis; K. Ogawa; C. Li; J. Halpern
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 111
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7729Forwarding and Control Element Separation (ForCES) Logical Functional Block (LFB) Subsidiary ManagementCurrent
December 2015
- RFC 7121High Availability within a Forwarding and Control Element Separation (ForCES) Network ElementUpdated
February 2014
- RFC 7391Forwarding and Control Element Separation (ForCES) Protocol ExtensionsCurrent
October 2014
- RFC 7408Forwarding and Control Element Separation (ForCES) Model ExtensionCurrent
November 2014
- RFC 7409Forwarding and Control Element Separation (ForCES) Packet ParallelizationCurrent
November 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
- RFC 8013Forwarding and Control Element Separation (ForCES) Inter-FE Logical Functional Block (LFB)Current
February 2017
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?