RFC 6041: Forwarding and Control Element Separation (ForCES) Applicability Statement
In plain English — editorial summary, not part of the RFC
The Forwarding and Control Element Separation (ForCES) protocol defines a standard framework and mechanism for the interconnection between control elements and forwarding elements in IP routers and similar devices. In this document we describe the applicability of the ForCES model and protocol. We provide example deployment scenarios and functionality, as well as document applications that would be inappropriate for ForCES. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6041
- Published
- October 2010
- Authors
- A. Crouch; H. Khosravi; A. Doria; X. Wang; K. Ogawa
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 4223Reclassification of RFC 1863 to HistoricCurrent
October 2005
- RFC 2236Internet Group Management Protocol, Version 2Updated
November 1997
- RFC 2103Mobility Support for Nimrod : Challenges and Solution ApproachesCurrent
February 1997
- RFC 2096IP Forwarding Table MIBObsoleted
January 1997
- RFC 2082RIP-2 MD5 AuthenticationObsoleted
January 1997
- RFC 2081RIPng Protocol Applicability StatementCurrent
January 1997
- RFC 2080RIPng for IPv6Current
January 1997
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?