RFC 7121: High Availability within a Forwarding and Control Element Separation (ForCES) Network Element
In plain English — editorial summary, not part of the RFC
This document discusses Control Element (CE) High Availability (HA) within a Forwarding and Control Element Separation (ForCES) Network Element (NE). Additionally, this document updates RFC 5810 by providing new normative text for the Cold Standby High Availability mechanism.
Document record
- Document ID
- RFC7121
- Published
- February 2014
- Authors
- K. Ogawa; W. Wang; E. Haleplidis; J. Hadi Salim
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 31
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
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 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 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
- RFC 5419Why the Authentication Data Suboption is Needed for Mobile IPv6 (MIPv6)Current
January 2009
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?