<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.wang-forces-compare-openflow-forces" target="https://datatracker.ietf.org/doc/html/draft-wang-forces-compare-openflow-forces-01">
   <front>
      <title>Analysis of Comparisons between OpenFlow and ForCES</title>
      <author initials="Z." surname="Wang" fullname="Zhiliang Wang">
         <organization>Tsinghua University</organization>
      </author>
      <author initials="T." surname="Tsou" fullname="Tina Tsou (Ting ZOU)">
         <organization>Huawei</organization>
      </author>
      <author initials="J." surname="Huang" fullname="Jing Huang">
         <organization>Huawei</organization>
      </author>
      <author initials="X." surname="Shi" fullname="Xingang Shi">
         <organization>Tsinghua University</organization>
      </author>
      <author initials="X." surname="Yin" fullname="Xia Yin">
         <organization>Tsinghua University</organization>
      </author>
      <date month="March" day="12" year="2012" />
      <abstract>
	 <t>   While both ForCES and OpenFlow follow the basic idea of separations
   of forwarding plane and control plane in network elements, they have
   some technical differences. This document analyzes the differences
   between OpenFlow and ForCES technically from the aspects of goals,
   architecture, forwarding model and protocol interface. The two
   techniques can learn much from each other in their standardization
   process.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-wang-forces-compare-openflow-forces-01" />
   
</reference>
