UpdatedINFORMATIONALIETF stream

RFC 6053: Implementation Report for Forwarding and Control Element Separation (ForCES)

Still current, but amended. Parts of this document are changed or extended by RFC 6984. Read both.

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC6053
Published
November 2010
Authors
E. Haleplidis; K. Ogawa; W. Wang; J. Hadi Salim
Status
INFORMATIONAL
Stream
IETF
Area
rtg
Pages
34
Also known as
Updated by:
RFC 6984

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.

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?

canonical URL: /rfc/6053-implementation-report-for-forwarding-and-control-element-separation-forces