RFC 5810: Forwarding and Control Element Separation (ForCES) Protocol Specification
In plain English — editorial summary, not part of the RFC
This document specifies the Forwarding and Control Element Separation (ForCES) protocol. The ForCES protocol is used for communications between Control Elements (CEs) and Forwarding Elements (FEs) in a ForCES Network Element (ForCES NE). This specification is intended to meet the ForCES protocol requirements defined in RFC 3654. Besides the ForCES protocol, this specification also defines the requirements for the Transport Mapping Layer (TML). [STANDARDS-TRACK]
Document record
- Document ID
- RFC5810
- Published
- March 2010
- Authors
- A. Doria; J. Hadi Salim; R. Haas; H. Khosravi; W. Wang; L. Dong; R. Gopal; J. Halpern
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 124
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5813Forwarding and Control Element Separation (ForCES) MIBCurrent
March 2010
- RFC 5811SCTP-Based Transport Mapping Layer (TML) for the Forwarding and Control Element Separation (ForCES) ProtocolCurrent
March 2010
- RFC 4577OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 2006
- RFC 7152Requirements for Metro Ethernet Forum (MEF) Ethernet-Tree (E-Tree) Support in Layer 2 Virtual Private Network (L2VPN)Current
March 2014
- RFC 7550Issues and Recommendations with Multiple Stateful DHCPv6 OptionsObsoleted
May 2015
- RFC 9408A YANG Network Data Model for Service Attachment Points (SAPs)Current
June 2023
- RFC 5812Forwarding and Control Element Separation (ForCES) Forwarding Element ModelUpdated
March 2010
- RFC 5814Label Switched Path (LSP) Dynamic Provisioning Performance Metrics in Generalized MPLS NetworksCurrent
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?