RFC 7391: Forwarding and Control Element Separation (ForCES) Protocol Extensions
In plain English — editorial summary, not part of the RFC
Experience in implementing and deploying the Forwarding and Control Element Separation (ForCES) architecture has demonstrated the need for a few small extensions both to ease programmability and to improve wire efficiency of some transactions. The ForCES protocol is extended with a table range operation and a new extension for error handling. This document updates the semantics in RFCs 5810 and 7121 to achieve that end goal.
Document record
- Document ID
- RFC7391
- Published
- October 2014
- Authors
- J. Hadi Salim
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7408Forwarding and Control Element Separation (ForCES) Model ExtensionCurrent
November 2014
- RFC 7409Forwarding and Control Element Separation (ForCES) Packet ParallelizationCurrent
November 2014
- RFC 1976PPP for Data Compression in Data Circuit-Terminating Equipment (DCE)Current
August 1996
- RFC 7179Transparent Interconnection of Lots of Links (TRILL): Header ExtensionUpdated
May 2014
- RFC 6956Forwarding and Control Element Separation (ForCES) Logical Function Block (LFB) LibraryCurrent
June 2013
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 6041Forwarding and Control Element Separation (ForCES) Applicability StatementCurrent
October 2010
- RFC 5811SCTP-Based Transport Mapping Layer (TML) for the Forwarding and Control Element Separation (ForCES) ProtocolCurrent
March 2010
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?