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)
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.
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.
Haleplidis, et al. Informational [Page 1]
RFC 6053 Implementation Report for ForCES November 2010
Copyright Notice
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's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Haleplidis, et al. Informational [Page 2]
RFC 6053 Implementation Report for ForCES November 2010
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. ForCES Protocol . . . . . . . . . . . . . . . . . . . . . 4
1.2. ForCES Model . . . . . . . . . . . . . . . . . . . . . . . 4
1.3. Transport Mapping Layer . . . . . . . . . . . . . . . . . 4
2. Terminology and Conventions . . . . . . . . . . . . . . . . . 4
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 5
3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Detail Section . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Implementation Experience . . . . . . . . . . . . . . . . 7
6.1.1. ForCES Protocol Features . . . . . . . . . . . . . . . 9
6.1.1.1. Protocol Messages . . . . . . . . . . . . . . . . 9
6.1.1.2. MainHeader Handling . . . . . . . . . . . . . . . 10
6.1.1.3. TLV Handling . . . . . . . . . . . . . . . . . . . 11
6.1.1.4. Operation Types Supported . . . . . . . . . . . . 12
6.1.1.5. ForCES Protocol Advanced Features . . . . . . . . 13
6.1.2. ForCES Model Features . . . . . . . . . . . . . . . . 14
6.1.2.1. Basic Atomic Types Supported . . . . . . . . . . . 14
6.1.2.2. Compound Types Supported . . . . . . . . . . . . . 15
6.1.2.3. LFBs Supported . . . . . . . . . . . . . . . . . . 15
6.1.3. ForCES SCTP TML Features . . . . . . . . . . . . . . . 19
datatracker.ietf.org