RFC 5811: SCTP-Based Transport Mapping Layer (TML) for the Forwarding and Control Element Separation (ForCES) Protocol
In plain English — editorial summary, not part of the RFC
This document defines the SCTP-based TML (Transport Mapping Layer) for the ForCES (Forwarding and Control Element Separation) protocol. It explains the rationale for choosing the SCTP (Stream Control Transmission Protocol) and also describes how this TML addresses all the requirements required by and the ForCES protocol. [STANDARDS TRACK]
Document record
- Document ID
- RFC5811
- Published
- March 2010
- Authors
- J. Hadi Salim; K. Ogawa
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5810Forwarding and Control Element Separation (ForCES) Protocol SpecificationUpdated
March 2010
- RFC 6956Forwarding and Control Element Separation (ForCES) Logical Function Block (LFB) LibraryCurrent
June 2013
- RFC 7121High Availability within a Forwarding and Control Element Separation (ForCES) Network ElementUpdated
February 2014
- RFC 7391Forwarding and Control Element Separation (ForCES) Protocol ExtensionsCurrent
October 2014
- RFC 7408Forwarding and Control Element Separation (ForCES) Model ExtensionCurrent
November 2014
- RFC 7409Forwarding and Control Element Separation (ForCES) Packet ParallelizationCurrent
November 2014
- 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
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?