<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-forces-implementation-report" target="https://datatracker.ietf.org/doc/html/draft-ietf-forces-implementation-report-02">
   <front>
      <title>Implementation Report for Forwarding and Control Element Separation (ForCES)</title>
      <author initials="W." surname="Wang" fullname="Weiming Wang">
         <organization>Zhejiang Gongshang University</organization>
      </author>
      <author initials="K." surname="Ogawa" fullname="Kentaro Ogawa">
         <organization>NTT Corporation</organization>
      </author>
      <author initials="E." surname="Haleplidis" fullname="Evangelos Haleplidis">
         <organization>University of Patras</organization>
      </author>
      <author initials="J." surname="Hadi Salim" fullname="Jamal Hadi Salim">
         <organization>Mojatatu Networks</organization>
      </author>
      <date month="June" day="27" year="2010" />
      <abstract>
	 <t>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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-forces-implementation-report-02" />
   
</reference>
