RFC 3654: Requirements for Separation of IP Control and Forwarding
In plain English — editorial summary, not part of the RFC
This document introduces the Forwarding and Control Element Separation (ForCES) architecture and defines a set of associated terminology. This document also defines a set of architectural, modeling, and protocol requirements to logically separate the control and data forwarding planes of an IP (IPv4, IPv6, etc.) networking device.
Document record
- Document ID
- RFC3654
- Published
- December 2003
- Authors
- H. Khosravi; T. Anderson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5811SCTP-Based Transport Mapping Layer (TML) for the Forwarding and Control Element Separation (ForCES) ProtocolCurrent
March 2010
- RFC 6956Forwarding and Control Element Separation (ForCES) Logical Function Block (LFB) LibraryCurrent
June 2013
- 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 7729Forwarding and Control Element Separation (ForCES) Logical Functional Block (LFB) Subsidiary ManagementCurrent
December 2015
- 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?