Analysis of Comparisons between OpenFlow and ForCES
draft-wang-forces-compare-openflow-forces-01

 
Document
Type Expired Internet-Draft (individual)
Last updated 2012-09-13 (latest revision 2012-03-12)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-wang-forces-compare-openflow-forces-01.txt

Abstract

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.

Authors

Zhiliang Wang (wzl@csnet1.cs.tsinghua.edu.cn)
Tina Tsou (tina.tsou.zouting@huawei.com)
Jing Huang (james.huang@huawei.com)
Xingang Shi (shixg@csnet1.cs.tsinghua.edu.cn)
Xia Yin (yxia@csnet1.cs.tsinghua.edu.cn)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)