openflow和ForCES的比较

This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
1. Introduction
ForCES (Forwarding and Control Element Separation) [RFC5810] defines
a framework and associated protocols to standardize information
new architecture of network devices, e.g., routers and switches.
However, they are technically different in many aspects. It is
necessary to compare the two techniques so that they can learn much
7.1. Normative References................................... 10
7.2. Informative References................................. 10
8. Acknowledgments ............................................ 11
process.
Table of Contents
1. Introduction ................................................ 2
2. Definitions used in this document............................ 3
publication of this document. Please review these documents carefully,
as they describe your rights and restrictions with respect to this
document.
exchange between the control and forwarding plane in a ForCES network
element (NE).
OpenFlow [McKeown2008][OpenFlow1.1] is an implementation of the idea
Expires: June 2012 J. Huang
Huawei
X. Shi
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
centralized controller is used to control the behavior of OpenFlow
switches by adding, updating and deleting flow table entries in
switches. ONF (Open Networking Foundation, Website:
3. Comparisons between ForCES and OpenFlow...................... 4
3.1. Difference in Goals..................................... 4
3.2. Difference in Architecture.............................. 5
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
/shadow.html
This Internet-Draft will expire on June 2, 2009.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
The list of current Internet-Drafts can be accessed at
/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
While both ForCES and OpenFlow follow the basic idea of separations
of forwarding plane and control plane in network elements, they are
technically very different. This document analyzes the differences
Analysis of Comparisons between OpenFlow and ForCES
draft-wang-forces-compare-openflow-forces-00.txt
Status of this Memo
https:///) has been founded in March of 2011 to
promote the SDN, and especially Standardize OpenFlow protocol.
Both ForCES and OpenFlow follow the basic idea of forwarding plane
3.3. Difference in Forwarding Model.......................... 8
3.4. Difference in Protocol Interface........................ 9
4. Security Considerations...................................... 9
and control plane separation in network elements, and result in the
Wang, et al. Expires June 2, 2012 [Page 2]
Internet-Draft OpenFlow vs. ForCES December 2011
Wang, et al. Expires June 2, 2012 [Page 1]
Internet-Draft OpenFlow vs. ForCES December 2011
Abstract
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
Hale Waihona Puke (/license-info) in effect on the date of
X. Yin
Tsinghua University
December 2, 2011
of so-called SDN (Software-Defined Networking). In network elements,
i.e., OpenFlow switches, control plane has been separated from
forwarding plane and only forwarding plane is retained. The
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
5. IANA Considerations ......................................... 9
6. Conclusions ................................................. 9
7. References ................................................. 10