Implementation Report for Forwarding and Control Element Separation
RFC 6053, “Implementation Report for Forwarding and Control Element Separation”, is an Informational document published in November 2010 by E. Haleplidis, K. Ogawa, W. Wang, J. Hadi Salim. It has since been updated by RFC 6984. The canonical text is published by the RFC Editor.
Abstract
Forwarding and Control Element Separation (ForCES) defines an architectural framework and associated protocols to standardize information exchange between the control plane and the forwarding plane in a ForCES network element (ForCES NE). RFC 3654 has defined the ForCES requirements, and RFC 3746 has defined the ForCES framework.
This document is an implementation report for the ForCES Protocol, Model, and the Stream Control Transmission Protocol-based Transport Mapping Layer (SCTP TML) documents, and includes a report on interoperability testing and the current state of ForCES implementations. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6053 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6052 IPv6 Addressing of IPv4/IPv6 Translators
- RFC 6054 Using Counter Modes with Encapsulating Security Payload and Authentication Header to Protect Group Traffic
- RFC 6051 Rapid Synchronisation of RTP Flows
- RFC 6050 A Session Initiation Protocol Extension for the Identification of Services
- RFC 6057 Comcast's Protocol-Agnostic Congestion Management System
- RFC 6048 Network News Transfer Protocol Additions to LIST Command
- RFC 6047 iCalendar Message-Based Interoperability Protocol
- RFC 6059 Simple Procedures for Detecting Network Attachment in IPv6