Implementation Report for Forwarding and Control Element Separation (ForCES) (RFC6053)
Original Publication Date: 2010-Nov-01
Included in the Prior Art Database: 2010-Nov-08
Internet Society Requests For Comment (RFCs)
E. Haleplidis: AUTHOR [+4]
This document is an implementation report for the ForCES protocol, model, and the SCTP TML documents, and includes an interoperability report.
Internet Engineering Task Force (IETF) E. Haleplidis Request for Comments: 6053 University of Patras Category: Informational K. Ogawa ISSN: 2070-1721 NTT Corporation W. Wang Zhejiang Gongshang University J. Hadi Salim Mojatatu Networks November 2010
Implementation Report for Forwarding and Control Element Separation (ForCES)
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.
Status of This Memo
This document is not an Internet Standards Track specification; it is published for informational purposes.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6053.
al. Informational [Page 1]
RFC 6053 Implementation Report for ForCES November 2010
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust'...