Principle and Implementation of. Protocol Oblivious Forwarding
|
|
- Oliver Hawkins
- 8 years ago
- Views:
Transcription
1 Principle and Implementation of Protocol Oblivious Forwarding PUBLICATION DATE DECEMBER 27, 2012 Contents Principle and Implementation of... 1 Protocol Oblivious Forwarding... 1 AUTHORS... 错 误! 未 定 义 书 签 PUBLICATION DATE... 1 Contents... 1 Glossary Summary Problem of the OpenFlow-based SDN Principle of Protocol Oblivious Forwarding Abstraction of Protocol Forwarding Goto-Table Set-Field Write-Metadata-From-Packet Forwarding Procedure Configuration of flow tables Implementation of Protocol Oblivious Forwarding How POF Device Interoperates with Standard OpenFlow Controller Challenges for Protocol Oblivious Forwarding Contact Information References Page1, Total15
2 Glossary SDN POF OF QoS NP ASIC MAC ACL GUI UI Software Defined Networking Protocol Oblivious Forwarding OpenFlow Quality of Service Network Processor Application Specific Integrated Circuit Media Access Control Access Control List Graphic User Interface User Interface Page2, Total15
3 1. Summary Protocol Oblivious Forwarding (POF) is an enhancement to the current OpenFlow-based SDN forwarding architecture. It will improve the programmability of SDN. POF enables forwarding devices to support any new protocols without modifying any code of the devices. An abstraction of protocols is used to realize this target. To support new protocols, the operators only need to download some flows with associated instructions into the forwarding devices after implementing POF. POF can help carriers to deploy any new policies or services based on new protocols more conveniently and rapidly. For example, carriers can implement security or QoS policies on any video, voice, or P2P protocols easily by implementing POF. 2. Problem of the OpenFlow-based SDN The current OpenFlow-based SDN promotes the programmability of network devices by downloading flows into devices from the controller; but it cannot support new protocols automatically. The programmability can only apply to the existing protocols. If one service based on a new protocol needs to be implemented, the operator has to ask the device vendor to modify the code of the devices to support the new service. A packet is composed of multiple protocol headers and payload. The protocol headers are parsed and modified by NP micro-code or ASIC logic during the forwarding process. The position of each protocol field, such as the IPv4 source address, is calculated by the code that is preloaded into the devices according to protocol format by the device vendor. If one new protocol needs to be supported, the code must be modified. This will lead to a long deployment cycle for new services based on new protocols. The current OpenFlow-based SDN cannot resolve the aforementioned problem. In the OpenFlow specifications, the protocol field is only identified by the field type. The position of the protocol fields cannot be derived from the flow s forwarding instructions. So the position of each protocol fields must be calculated by the code, which means the code of the devices must be modified for processing new protocol headers. 3. Principle of Protocol Oblivious Forwarding 3.1 Abstraction of Protocol POF denotes any protocol field with the following structure. The metadata is considered as one special protocol header that can be configured by the controller. Any metadata field is also denoted in the same way as below. field { type; offset; length; }; Page3, Total15
4 The type is used to indicate the field type, for which the value 0 means the field is a packet data field and the value 1 means it is a metadata field. The offset is the field s start position relative to the current protocol head. The following example shows the MAC protocol header format. MAC dst src type There are three fields: dst, src, and type. They are denoted as follows: dst: {0, 0, 48}; /*packet field, offset is 0bit, length is 48bit*/ src: {0, 48, 48}; /*packet field, offset is 48bit, length is 48bit*/ type: {0, 96, 16}; /*packet field, offset is 96bit, length is 16bit*/ It is easy to see that any existing or new protocols can be denoted in the similar way. 3.2 Forwarding POF can realize the functions of all forwarding instructions/actions defined in OpenFlow 1.3.0, not only for the existing protocols but also for any new protocols. The followings are the definitions of three classic forwarding instructions/actions in POF. For the definitions of all other instructions/actions, interested readers can refer to the User Manual of POF Controller.pdf Goto-Table The Goto-Table Instruction instructs micro-code to match one table with keys extracted from the packet data or the metadata. The structure of Goto-Table instruction is: Goto-Table { type; next_table_id; packet_offset; match_field_num; fields_array[]; } The type indicates the instruction type, which is Goto-Table in this example. The next_table_id indicates the table to search. The match_field_num indicates the number of match fields. The fields_array[] indicates the fields of packet data or metadata used for match. The structure of each field is described in section 3.1. The packet offset instructs the micro-code to move forward Packet Process Pointer first before extract match field from the packet. In the figure below, one new protocol IPvX is defined, which comprises three fields: Dst_Addr, Src_Addr, and Type. Page4, Total15
5 IPvX Dst_Addr Src_Addr Type Dst_Addr: {0, 0, 64}; /*packet field, offset is 0bit, length is 64bit*/ Src_Addr: {0, 64, 64}; /*packet field, offset is 64bit, length is 64bit*/ Type: {0, 128, 8}; /*packet field, offset is 128bit, length is 8bit*/ In POF, the packet header is processed layer by layer, and the position of one protocol field is relative to its own protocol header. For example, the Src_Addr position has a 64-bit offset relative to the starting position of the IPvX header field. The following figure shows the process of IPvX packets by using the instruction Goto-Table. Flow Table 0 (Dst, Type) Flow Table 1 (Src_Addr) Goto-Table{ Table 1, /*Flow Table 1*/ 14, /*Packet Process Pointer move forward 14bytes */ 1, /*match field number is 1*/ {0, 64,64}, /*match field is Src_Addr*/ } Packet Process Pointer Packet Process Pointer MAC IPvX MAC IPvX Dst_Addr Src_Addr Type Dst_Addr Src_Addr Type Figure 1: Instance for Goto-Table Instruction In Flow Table 0, the destination address and the type of the MAC header are used as the match fields. Flow Table 0 has one flow entry configured by controller which instructs the microcode to go to Flow Table 1 for further processing. In Flow Table 1, the Src_Addr of IPvX is used as the match field. Flow Table 1 consists of some flow entries configured by the controller. A packet with the Ethernet type being IPvX will match a flow entry in Flow Table 0.The Goto-Table instruction in the flow entry will instruct the microcode to move the Packet Process Pointer forward 14 bytes first (i.e. the length of the MAC header), and then extract the Src_Addr field at the 64-bit offset position relative to the Packet Process Pointer. Finally the microcode will use the extracted Src_Addr field as the match key to search Flow Page5, Total15
6 Table 1 and do the further processing as instructed by the matching flow entry Set-Field The Set-Field instruction assigns the value of a protocol field in a packet header. The structure of the Set-Field instruction is shown below: Set-Field { type; field; value; } The type indicates the instruction type, which is Set-Field. The field identifies one field of the current protocol layer for which the structure is described in section 3.1. The value is what to be set in the field. The following figure is an example of Set-Field process on the IPvX Dst_Addr. In Flow Table 1, the matched flow entry 1 has a Set-Field instruction which instructs the microcode to set Dst_Addr of IPvX to 0x Flow Table 1 (Src_Addr) Set-Field{ {0, 0, 64}, /*field to be set is Dst_Addr*/ 0x , /*value */ } Packet Process Pointer 0 14 MAC IPvX Dst_Addr Src_Addr Type Figure 2: Instance for Set-Field Instruction Write-Metadata-From-Packet The Write-Metadata-From-Packet instruction copies the value of one packet field to the metadata memory. This instruction helps the microcode to fetch and retain the value of preceding protocol layers fields for process such as ACL. The structure of Write-Metadata-From-Packet is shown below. Write-Metadata-From-Packet { type; metadata_offset; Page6, Total15
7 } packet_field_offset; length; The type indicates the instruction type, which is Write-Metadata-From-Packet. The metadata_offset is the starting position to write in the metadata memory. The packet_field_offset is the starting position of the packet field to be copied. The length is the length of the field to be copied. The following figure is an instance of the Write-Metadata-From-Packet process. In Flow Table 1, the matched flow entry 1 has one Write-Metadata-From-Packet instruction which instructs the microcode to copy Dst_Addr of IPvX to the designated position of metadata memory. Flow Table 1 (Src_Addr) 0 Metadata Memory Write_Metadata_From_Packet{ 512, /*metadata offset*/ 0, /*packet field offset*/ 64, /*packet field length */ } Packet Process Pointer 0 14 MAC IPvX Dst_Addr Src_Addr Type Figure 3: Instance for Write-Metadata-From-Packet Instruction 3.3 Forwarding Procedure POF uses multiple flow tables for packet processing. Each flow table can realize one or more functions of the following: - Parsing the type of the next protocol header. - Set/Modify the current protocol header. - Add/Delete a protocol header. - Copy the current protocol field to the metadata. - Set the packet s committed access rate. - Set the packet s queue ID. - Access control: forward/drop/send upward a packet. - Output packet to designated port(s): unicast/multicast. Page7, Total15
8 POF handles packet headers layer by layer. Each layer has one or more relative flow tables for parsing the next protocol, setting/modifying the current protocol fields, adding/deleting protocol headers to/from the packet, or copying the protocol header to the metadata. The flow tables dedicated to one layer cannot handle any other preceding or rear protocol headers. Metadata can be used to hold the previous protocol headers. One Flow table executing match across multiple protocol layers will be introduced later. As shown in figure 4, one packet contains four layers of protocol header, Header0 ~ Header 3. The microcode uses Flow Table 0 to handle Header 0, and then go to Flow Table 1 to process Header 1. The Packet Process Pointer is moved forward to the start position of Header 1 as instructed by the Goto-Table instruction. Header 2 and Header 3 are processed in the same way. fields fields fields fields fields fields Goto Table 3 Goto Table 1 Flow Table 1 fields fields fields Goto Table 2 Flow Table 3 fields fields fields Packet Process Pointer Header 0 Header 1 Header 2 Header 3 Payload Figure 4: Forwarding procedure Each protocol layer can have multiple flow tables for processing the current protocol layer. For example, we can use one small flow table to parse the next protocol type and write the protocol fields into the metadata; meanwhile we use one big flow table to do other processes on the protocol layer. The small flow table can locate on chip and the big flow table can locate off chip for the best efficiency. If one flow table such as ACL needs to use multiple fields across multiple protocols as the match key, these fields should be copied from the protocol headers to the metadata memory first during the layer-by-layer packet parsing process. For example, in Figure 5 below, Flow Table 0 will instruct the microcode to write Header 0 s fields into one place of the metadata memory, and Flow Table 1will instruct the microcode to write Header 1 s fields into another place of the metadata memory, and so on. In Flow Table 3, after copying the fields of Header 3 into the metadata memory, the instruction Goto-Table instructs the microcode to extract those fields from the metadata memory as the match key and then execute the search in Flow table 4 for a match (note that we do not need to copy all the fields of a protocol header to the metadata memory, but only those fields needed for table match). Page8, Total15
9 Metadata Memory 0 32bit Flow Table 0 Goto Table Write Metadata From Packet Flow Table 1 Flow Table 2 Flow Table 3 Goto Table Write Metadata From Packet Write Metadata From Packet Goto Table Write Metadata From Packet Goto Table Flow Table 4 Packet Process Pointer Header 0 Header 1 Header 2 Header 3 Payload Figure 5: Match multiple fields across multiple protocol headers Each protocol field for match has its identified position in the metadata memory. The position can be configured by the controller. The following configuration is one example: the controller can add new fields to the metadata for any new protocol field which is needed for match. VLAN_ID_Outer VPN_ID TCP_Src_Port UDP_Src_Port VLAN_ID_Inner Rsv IPv4_Protocol_1 IPv4_Protocol_2 IPv4_Src_1 IPv4_Dst_1 IPv4_Src_2 IPv4_Dst_2 TCP_Dst_Port UDP_Dst_Port 3.4 Configuration of flow tables Figure6: Metadata Format All flow tables in a device are configured by a controller. The flow entries in any flow table are configured automatically by applications or manually through GUI on the controller. The controller provides the user interface for configuring protocols and metadata. The controller stores all protocols in one database in the format described in section 3.1. During configuring flow entries, applications on the controller may reference any protocol field in the protocol database for building the flow entries match fields and instructions (note that the Page9, Total15
10 metadata is considered as one special protocol header in controller). Figure 7 is a sketch map of POF architecture. Operator can configure protocol/metadata through an UI. Applications create flow tables as services required. During the procedure, the protocol database may be referenced. Applications download all flow tables entries into the designated device through the OpenFlow channel. Controller Protocol Database UI Metadata Protocol 0 Protocol 1 Protocol 2 Protocol 3 Protocol 4 Protocol 5 Application 0 Application 1 Application n Flow Table 0 Flow Table 1 Flow Table n Device OpenFlow Flow Table 0 Flow Table 1 Flow Table n Packet Forwarding Engine Metadata Figure 7: Sketch Map of POF Architecture 4. Implementation of Protocol Oblivious Forwarding In order to demonstrate the capability of POF and evaluate the possibility of using the existing hardware to support POF, we have finished developing two prototypes in parallel. One is an open-source software prototype. The other is based on one of our NP-based router platforms. The POF controller in our prototypes is responsible for managing devices resource like flow tables, group tables, counters, meters and so on. The POF device will report the capacity of each kind of resource to the POF controller during handshaking. The POF controller uses GUI to create and configure flow tables in the designated POF device. The POF controller stores the protocols formats which are configured through GUI by user. The POF controller also stores packets and error messages received from POF devices. For the detail information of the POF controller, interested readers can refer to POFController Introduction(1.0).pdf and Page10, Total15
11 User Manual of POF Controller.pdf. The hardware-based POF prototype is realized on a core router. We add a POF hardware abstraction layer in the core router s control plane for configuring POF flow tables, and add microcode in forwarding engine for parsing and executing POF instructions. The software architecture of POF device is shown in Figure 8. Our tests verify that the POF router can realize packet forwarding for any existing or user-defined packet formats. There are two classical use cases in the user manual of POF for demonstrating the flexible forwarding capability of POF router. Controller MPU HUAWEI Core Router OpenFlow Connection Management LPU OpenFlow Parse OpenFlow Encap HAL of POF Forwarding Engine Driver Forwarding Engine Figure 8: Software Architecture of POF device The POF software switch is implemented with a similar POF driver and software forwarding code on LINUX. The POF software switch can almost realize all forwarding functions as the POF hardware device. For the detail information of the POF software switch, interested readers can refer to the introduction document of the POF software switch POFSwitch Introduction(1.0).pdf. The POF controller communicates with the POF device through the OpenFlow protocol. POF uses the same control command as the standard OpenFlow 1.3. The data structure of the most control commands remains unchanged. POF only changes the data structure of forwarding instructions/actions of the standard OpenFlow How POF Device Interoperates with Standard OpenFlow Controller Page11, Total15
12 Now many vendors have developed their standard OpenFlow (OF) controllers. In order to enable POF devices to interoperate with standard OF controllers, the POF device should implement one translation layer on the POF driver as shown in Figure 9. Standard OF / POF Controller OpenFlow Channel POF Device POF Standard OF Translate OF Instruction to POF Instruction. Protocol Description Database POF Driver POF Forwarding Engine Figure 9: Translate Standard OF into POF In Figure 9, the POF device is able to interoperate with both standard OpenFlow controllers and POF controllers. If the POF device receives one control command from a standard OpenFlow controller, it will translate the OpenFlow instructions into the POF instructions by referencing the protocol database. The protocol database is prebuilt in the device and new protocol cannot be supported automatically while interoperating with the standard OpenFlow controller. (New protocol can be supported unless that the standard OpenFlow controller implements new control command for configuring protocol database in the POF device.) As discussed in section 3.3, each flow table can only process one protocol layer in the POF device. If one application flow table needs multiple protocol fields for match, metadata must be used. But the existing applications on standard OpenFlow controllers may not conform to the aforementioned limitation. Some existing applications on standard OpenFlow controllers may not be able to work and need to be rewritten while interoperating with POF devices. An alternative scheme can be used to avoid the problem above. As shown in Figure 10, we make POF instructions as an extending part of the standard OpenFlow instructions, and the POF instructions types are different from the standard OpenFlow instructions types. Page12, Total15
13 Standard OF/ POF Controller OpenFlow Channel POF Device Standard OF POF Standard OF Driver POF Driver (Standard OF + POF) Forwarding Engine Figure 10: Extend Standard OF with POF In Figure 10, the forwarding engine of the POF device supports both standard OpenFlow instructions and POF instructions. The standard OpenFlow configuration commands are executed by the standard OpenFlow driver and the POF configuration commands are executed by the POF driver. In this way, the POF device can interoperate with the standard OpenFlow controller or POF controller automatically. This scheme needs the forwarding engine of POF devices to implement both standard OpenFlow instructions and POF instructions, which require much more microcode to be stored in NP s instruction buffer. Actually, a POF device can realize all functions of a standard OpenFlow device as discussed in section 3. In our opinion, the POF scheme should be included into the OpenFlow specification for denoting match fields in instructions/actions, and then eventually SDN forwarding devices will not need to support the current OpenFlow instructions any more in the future. 6. Challenges for Protocol Oblivious Forwarding POF enables network devices to support full programmability for any new services based on existing or new protocols. While it is great to achieve this aim, there are still a number of challenges to address. The challenges we have identified are: Standardization and Interoperability. Many vendors have developed their SDN forwarding devices and controllers without supporting POF. We need to make POF standardized as one necessary part of SDN implementation (At least should be an extending part as discussed in section 5). Otherwise the devices/controllers implementing POF may not be able to interoperate with the controllers/devices which do not implement POF. Performance. Performance is a challenge not only for POF but also for the current Page13, Total15
14 OpenFlow-based SDN as many flow tables are accessed, translated, and performed during the forwarding procedure. The following are the possible causes that make the performance drop: - Too many clock cycles are used for accessing flow tables, translating SDN instructions, and performing instructions. The process latency of SDN is longer than that of the traditional process. - The bandwidth of the on-chip and off-chip memory is not enough for storing/accessing so many flow tables. We propose the following methods to improve the performance of SDN devices: - Create as few flow tables as possible. We should combine multiple flow tables to one table if possible. By this way, forwarding engine has fewer flow tables to access. - Use hardware to execute the complex instructions to reduce process latency. - Put small flow tables on chip as accessing on-chip memory is much faster than accessing off-chip memory and on-chip memory provides higher bandwidth. - If necessary, duplicate some small flow tables to provide high bandwidth as required. - Divide on-chip memory into many small blocks to provide enough bandwidth for flow tables. - Embed one or multiple small TCAMs on chip to store small flow tables, such as those tables for parsing the type of the next protocol layer. Simplicity. In OpenFlow specifications, Flow Table can comprise more than ten match fields. The match fields can be wild card and the maximum length of match key can reach more than 512 bits. In this condition, it is difficult to match the flow table quickly if the flow table is too large to be stored in TCAM. Sophisticated algorithms have to be implemented to do the job. The algorithm may consume much resource including memory space, memory bandwidth, and logic units. It can cause the forwarding engine to be very complex and large. Even the complicated algorithm can be realized, the lookup performance is still in doubt. In order to avoid the complexity of flow tables, we should design flow tables with as few match fields as possible. But it may result in too many flow tables and the performance suffers. The tradeoff between the complexity of flow tables and the number of flow tables must be considered carefully during the application design. Contact Information Please provide your feedback to any of the following. Haoyu Song: haoyu.song@huawei.com Jun Gong: gongjun@huawei.com Xiaozhong Wang: rossel.wangxiaozhong@huawei.com Yuanming Zheng: zhengyuanming@huawei.com Jian Song: jack.songjian@huawei.com Page14, Total15
15 Zhen Wang: Jinzhou Yu: References 1. openflow-spec-v1.3.0.pdf: Page15, Total15
基 於 SDN 與 可 程 式 化 硬 體 架 構 之 雲 端 網 路 系 統 交 換 器
基 於 SDN 與 可 程 式 化 硬 體 架 構 之 雲 端 網 路 系 統 交 換 器 楊 竹 星 教 授 國 立 成 功 大 學 電 機 工 程 學 系 Outline Introduction OpenFlow NetFPGA OpenFlow Switch on NetFPGA Development Cases Conclusion 2 Introduction With the proposal
More informationSoftware Defined Networking and the design of OpenFlow switches
Software Defined Networking and the design of OpenFlow switches Paolo Giaccone Notes for the class on Packet Switch Architectures Politecnico di Torino December 2015 Outline 1 Introduction to SDN 2 OpenFlow
More informationSDN. WHITE PAPER Intel Ethernet Switch FM6000 Series - Software Defined Networking. Recep Ozdag Intel Corporation
WHITE PAPER Intel Ethernet Switch FM6000 Series - Software Defined Networking Intel Ethernet Switch FM6000 Series - Software Defined Networking Recep Ozdag Intel Corporation Software Defined Networking
More informationSecuring Local Area Network with OpenFlow
Securing Local Area Network with OpenFlow Master s Thesis Presentation Fahad B. H. Chowdhury Supervisor: Professor Jukka Manner Advisor: Timo Kiravuo Department of Communications and Networking Aalto University
More informationLimitations of Current Networking Architecture OpenFlow Architecture
CECS 572 Student Name Monday/Wednesday 5:00 PM Dr. Tracy Bradley Maples OpenFlow OpenFlow is the first open standard communications interface that enables Software Defined Networking (SDN) [6]. It was
More informationSDN 交 換 機 核 心 技 術 - 流 量 分 類 以 及 應 用 辨 識 技 術. 黃 能 富 教 授 國 立 清 華 大 學 特 聘 教 授, 資 工 系 教 授 E-mail: nfhuang@cs.nthu.edu.tw
SDN 交 換 機 核 心 技 術 - 流 量 分 類 以 及 應 用 辨 識 技 術 黃 能 富 教 授 國 立 清 華 大 學 特 聘 教 授, 資 工 系 教 授 E-mail: nfhuang@cs.nthu.edu.tw Contents 1 2 3 4 5 6 Introduction to SDN Networks Key Issues of SDN Switches Machine
More informationOpenFlow - the key standard of Software-Defined Networks. Dmitry Orekhov, Epam Systems
OpenFlow - the key standard of Software-Defined Networks Dmitry Orekhov, Epam Systems Software-defined network The Need for a New Network Architecture Limitations of Current Networking Technologies Changing
More informationOpen Source Network: Software-Defined Networking (SDN) and OpenFlow
Open Source Network: Software-Defined Networking (SDN) and OpenFlow Insop Song, Ericsson LinuxCon North America, Aug. 2012, San Diego CA Objectives Overview of OpenFlow Overview of Software Defined Networking
More informationUnderstanding OpenFlow
Understanding OpenFlow Technical Whitepaper June, 2014 Saurabh Kumar Agarwal Email: saurabh29july@gmail.com Abstract Technical overview of OpenFlow Switch Specification, Version 1.0.0, published on December
More informationSoftware Defined Networking (SDN) - Open Flow
Software Defined Networking (SDN) - Open Flow Introduction Current Internet: egalitarian routing/delivery based on destination address, best effort. Future Internet: criteria based traffic management,
More informationThe Lagopus SDN Software Switch. 3.1 SDN and OpenFlow. 3. Cloud Computing Technology
3. The Lagopus SDN Software Switch Here we explain the capabilities of the new Lagopus software switch in detail, starting with the basics of SDN and OpenFlow. 3.1 SDN and OpenFlow Those engaged in network-related
More informationProtocol-Oblivious Forwarding: Unleash the Power of SDN through a Future-Proof Forwarding Plane
Protocol-Oblivious Forwarding: Unleash the Power of SDN through a Future-Proof Forwarding Plane Haoyu Song Huawei Technologies, USA Santa Clara, CA, 95050 haoyu.song@huawei.com ABSTRACT A flexible and
More informationSoftware Defined Networking
Software Defined Networking Richard T. B. Ma School of Computing National University of Singapore Material from: Scott Shenker (UC Berkeley), Nick McKeown (Stanford), Jennifer Rexford (Princeton) CS 4226:
More informationSoftware Defined Networking
Software Defined Networking Dr. Nick Feamster Associate Professor In this course, you will learn about software defined networking and how it is changing the way communications networks are managed, maintained,
More informationBROADCOM SDN SOLUTIONS OF-DPA (OPENFLOW DATA PLANE ABSTRACTION) SOFTWARE
BROADCOM SDN SOLUTIONS OF-DPA (OPENFLOW DATA PLANE ABSTRACTION) SOFTWARE Network Switch Business Unit Infrastructure and Networking Group 1 TOPICS SDN Principles Open Switch Options Introducing OF-DPA
More informationSoftware Defined Networks
Software Defined Networks Inspired from the article Software-defined Networking: A Comprehensive Survey by Diego Kreutz, Fernando M. V. Ramos, Paulo Verissimo, Christian Esteve Rothenberg, Siamak Azodolmolky
More informationCloud Networking Disruption with Software Defined Network Virtualization. Ali Khayam
Cloud Networking Disruption with Software Defined Network Virtualization Ali Khayam In the next one hour Let s discuss two disruptive new paradigms in the world of networking: Network Virtualization Software
More informationExtending the Internet of Things to IPv6 with Software Defined Networking
Extending the Internet of Things to IPv6 with Software Defined Networking Abstract [WHITE PAPER] Pedro Martinez-Julia, Antonio F. Skarmeta {pedromj,skarmeta}@um.es The flexibility and general programmability
More informationInteractive Programming for Dynamic Network Probes A Use Case for POF Data Plane. Haoyu Song, Huawei Technologies
Interactive Programming for Dynamic Network Probes A Use Case for POF Data Plane Haoyu Song, Huawei Technologies Service Provider s Pain Point Lack of real-time and full visibility of network states, so
More informationSDN/Virtualization and Cloud Computing
SDN/Virtualization and Cloud Computing Agenda Software Define Network (SDN) Virtualization Cloud Computing Software Defined Network (SDN) What is SDN? Traditional Network and Limitations Traditional Computer
More informationAutonomicity Design in OpenFlow Based Software Defined Networking
GC'12 Workshop: The 4th IEEE International Workshop on Management of Emerging Networks and Services Autonomicity Design in OpenFlow Based Software Defined Networking WANG Wendong, Yannan HU, Xirong QUE,
More informationSDN CENTRALIZED NETWORK COMMAND AND CONTROL
SDN CENTRALIZED NETWORK COMMAND AND CONTROL Software Defined Networking (SDN) is a hot topic in the data center and cloud community. The geniuses over at IDC predict a $2 billion market by 2016
More informationHuawei Agile Network FAQ... 2. 1 What is an agile network? What is the relationship between an agile network and SDN?... 2
Contents Huawei Agile Network FAQ... 2 1 What is an agile network? What is the relationship between an agile network and SDN?... 2 2 What is an agile campus?... 3 3 What are the benefits of an agile network?...
More informationSOFTWARE-DEFINED NETWORKING AND OPENFLOW
SOFTWARE-DEFINED NETWORKING AND OPENFLOW Freddie Örnebjär TREX Workshop 2012 2012 Brocade Communications Systems, Inc. 2012/09/14 Software-Defined Networking (SDN): Fundamental Control
More informationWhat is SDN (Software Defined Networking) and Openflow? SDN/OF Part of Kernel / SoC to provide security, steering & monitoring
What is SDN (Software Defined Networking) and Openflow? Control and Data Plane Separation Control SDN/OF Part of Kernel / SoC to provide security, steering & monitoring External Use 1 Software Defined
More informationOpenFlow Switch Specification
( Wire Protocol 0x02 ) February 28, 2011 Contents 1 Introduction 3 2 Switch Components 3 3 Glossary 4 4 OpenFlow Tables 5 4.1 Flow Table.............................................. 5 4.1.1 Pipeline Processing......................................
More informationThe State of OpenFlow: Advice for Those Considering SDN. Steve Wallace Executive Director, InCNTRE SDN Lab Indiana University ssw@iu.
The State of OpenFlow: Advice for Those Considering SDN Steve Wallace Executive Director, InCNTRE SDN Lab Indiana University ssw@iu.edu 2 3 4 SDN is an architecture Separation of Control and Data Planes
More informationHP OpenFlow Protocol Overview
HP OpenFlow Protocol Overview Technical Solution Guide Version: 1 September 2013 Table of Contents Introduction: Traditional Switch and Openflow... 2 Destination Address-based Switching... 2 Flow-based
More informationCarrier/WAN SDN. SDN Optimized MPLS Demo
Carrier/WAN SDN SDN Optimized MPLS Demo Problem Statement! Service Providers around the world have large investments in highly sophisticated and feature rich IP/MPLS network infrastructures for providing
More informationAn Overview of OpenFlow
An Overview of OpenFlow By Jim Metzler, Ashton Metzler & Associates Distinguished Research Fellow and Co-Founder, Webtorials Editorial/Analyst Division The OpenFlow Protocol Figure 1 depicts the Open Networking
More informationSoftware Defined Networking What is it, how does it work, and what is it good for?
Software Defined Networking What is it, how does it work, and what is it good for? slides stolen from Jennifer Rexford, Nick McKeown, Michael Schapira, Scott Shenker, Teemu Koponen, Yotam Harchol and David
More informationCOMPSCI 314: SDN: Software Defined Networking
COMPSCI 314: SDN: Software Defined Networking Nevil Brownlee n.brownlee@auckland.ac.nz Lecture 23 Current approach to building a network Buy 802.3 (Ethernet) switches, connect hosts to them using UTP cabling
More informationDefinition of a White Box. Benefits of White Boxes
Smart Network Processing for White Boxes Sandeep Shah Director, Systems Architecture EZchip Technologies sandeep@ezchip.com Linley Carrier Conference June 10-11, 2014 Santa Clara, CA 1 EZchip Overview
More informationNetwork Virtualization Based on Flows
TERENA NETWORKING CONFERENCE 2009 June 9, 2009 Network Virtualization Based on Flows Peter Sjödin Markus Hidell, Georgia Kontesidou, Kyriakos Zarifis KTH Royal Institute of Technology, Stockholm Outline
More informationSmart Queue Scheduling for QoS Spring 2001 Final Report
ENSC 833-3: NETWORK PROTOCOLS AND PERFORMANCE CMPT 885-3: SPECIAL TOPICS: HIGH-PERFORMANCE NETWORKS Smart Queue Scheduling for QoS Spring 2001 Final Report By Haijing Fang(hfanga@sfu.ca) & Liu Tang(llt@sfu.ca)
More informationSDN and Streamlining the Plumbing. Nick McKeown Stanford University
SDN and Streamlining the Plumbing Nick McKeown Stanford University What is SDN? (when we clear away all the hype) A network in which the control plane is physically separate from the forwarding plane.
More informationSoftware Defined Networking and OpenFlow: a Concise Review
Software Defined Networking and OpenFlow: a Concise Review Stefano Forti stefano.forti92@gmail.com MSc in Computer Science and Networking Scuola Superiore Sant'Anna - University of Pisa 1. Introduction
More informationThe Internet: A Remarkable Story. Inside the Net: A Different Story. Networks are Hard to Manage. Software Defined Networking Concepts
The Internet: A Remarkable Story Software Defined Networking Concepts Based on the materials from Jennifer Rexford (Princeton) and Nick McKeown(Stanford) Tremendous success From research experiment to
More informationOpenFlow and Onix. OpenFlow: Enabling Innovation in Campus Networks. The Problem. We also want. How to run experiments in campus networks?
OpenFlow and Onix Bowei Xu boweixu@umich.edu [1] McKeown et al., "OpenFlow: Enabling Innovation in Campus Networks," ACM SIGCOMM CCR, 38(2):69-74, Apr. 2008. [2] Koponen et al., "Onix: a Distributed Control
More informationOpen Flow Controller and Switch Datasheet
Open Flow Controller and Switch Datasheet California State University Chico Alan Braithwaite Spring 2013 Block Diagram Figure 1. High Level Block Diagram The project will consist of a network development
More informationOpenFlow Switch Specification Version 1.3.4 ( Protocol version 0x04 )
OpenFlow Switch Specification Version 1.3.4 ( Protocol version 0x04 ) March 27, 2014 Copyright 2014; Open Networking Foundation Disclaimer THIS SPECIFICATION IS PROVIDED AS IS WITH NO WARRANTIES WHATSOEVER,
More informationSDN AND SECURITY: Why Take Over the Hosts When You Can Take Over the Network
SDN AND SECURITY: Why Take Over the s When You Can Take Over the Network SESSION ID: TECH0R03 Robert M. Hinden Check Point Fellow Check Point Software What are the SDN Security Challenges? Vulnerability
More informationConfiguring NetFlow-lite
CHAPTER 55 Note NetFlow-lite is only supported on Catalyst 4948E Ethernet Switch. This chapter describes how to configure NetFlow-lite on the Catalyst 4948E switch. NetFlow-lite provides traffic monitoring
More informationImproving Quality of Service
Improving Quality of Service Using Dell PowerConnect 6024/6024F Switches Quality of service (QoS) mechanisms classify and prioritize network traffic to improve throughput. This article explains the basic
More informationIPv4 and IPv6: Connecting NAT-PT to Network Address Pool
Available online www.jocpr.com Journal of Chemical and Pharmaceutical Research, 2014, 6(5):547-553 Research Article ISSN : 0975-7384 CODEN(USA) : JCPRC5 Intercommunication Strategy about IPv4/IPv6 coexistence
More informationArchitecture of distributed network processors: specifics of application in information security systems
Architecture of distributed network processors: specifics of application in information security systems V.Zaborovsky, Politechnical University, Sait-Petersburg, Russia vlad@neva.ru 1. Introduction Modern
More informationInternet Packets. Forwarding Datagrams
Internet Packets Packets at the network layer level are called datagrams They are encapsulated in frames for delivery across physical networks Frames are packets at the data link layer Datagrams are formed
More informationHow To Make A Vpc More Secure With A Cloud Network Overlay (Network) On A Vlan) On An Openstack Vlan On A Server On A Network On A 2D (Vlan) (Vpn) On Your Vlan
Centec s SDN Switch Built from the Ground Up to Deliver an Optimal Virtual Private Cloud Table of Contents Virtualization Fueling New Possibilities Virtual Private Cloud Offerings... 2 Current Approaches
More informationOpenFlow Switch Specification
(Wire Protocol 0x02) February 28, 2011 ONF TS-002 (Wire Protocol 0x02) ONF Document Type: OpenFlow Spec ONF Document Name: openflow-spec-v1.1.0 Disclaimer THIS SPECIFICATION IS PROVIDED AS IS WITH NO WARRANTIES
More informationTowards Software Defined Cellular Networks
Towards Software Defined Cellular Networks Li Erran Li (Bell Labs, Alcatel-Lucent) Morley Mao (University of Michigan) Jennifer Rexford (Princeton University) 1 Outline Critiques of LTE Architecture CellSDN
More informationESSENTIALS. Understanding Ethernet Switches and Routers. April 2011 VOLUME 3 ISSUE 1 A TECHNICAL SUPPLEMENT TO CONTROL NETWORK
VOLUME 3 ISSUE 1 A TECHNICAL SUPPLEMENT TO CONTROL NETWORK Contemporary Control Systems, Inc. Understanding Ethernet Switches and Routers This extended article was based on a two-part article that was
More informationOpenFlow Switch Specification. Version 1.3.2 (Wire Protocol 0x04) April 25, 2013
OpenFlow Switch Specification Version 1.3.2 (Wire Protocol 0x04) April 25, 2013 Disclaimer THIS SPECIFICATION IS PROVIDED "AS IS" WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY,
More informationSwitch Fabric Implementation Using Shared Memory
Order this document by /D Switch Fabric Implementation Using Shared Memory Prepared by: Lakshmi Mandyam and B. Kinney INTRODUCTION Whether it be for the World Wide Web or for an intra office network, today
More informationSOFTWARE-DEFINED NETWORKING AND OPENFLOW
SOFTWARE-DEFINED NETWORKING AND OPENFLOW Eric Choi < echoi@brocade.com> Senior Manager, Service Provider Business Unit, APJ 2012 Brocade Communications Systems, Inc. EPF 7 2012/09/17 Software-Defined Networking
More informationCisco Integrated Services Routers Performance Overview
Integrated Services Routers Performance Overview What You Will Learn The Integrated Services Routers Generation 2 (ISR G2) provide a robust platform for delivering WAN services, unified communications,
More informationTyrant: A High Performance Storage over IP Switch Engine
Tyrant: A High Performance Storage over IP Switch Engine Stuart Oberman, Rodney Mullendore, Kamran Malik, Anil Mehta, Keith Schakel, Michael Ogrinc, Dane Mrazek Hot Chips 13, August 2001 1 Background:
More informationOpenFlow. Ihsan Ayyub Qazi. Slides use info from Nick Mckeown
OpenFlow Ihsan Ayyub Qazi Slides use info from Nick Mckeown Why Openflow? Deployment of new experimental protocols is challenging Huge installed base of protocols and equipment Reluctance by network operators
More informationNetwork Infrastructure Technology Supporting Parallelization and Multiplexing of Services
Network Infrastructure Technology Supporting Parallelization and Multiplexing of Services Yuzuru Iida Hiroaki Tanaka The increasingly fierce competition between information and communications technology
More informationHow To Understand The Power Of The Internet
DATA COMMUNICATOIN NETWORKING Instructor: Ouldooz Baghban Karimi Course Book: Computer Networking, A Top-Down Approach, Kurose, Ross Slides: - Course book Slides - Slides from Princeton University COS461
More informationVLAN for DekTec Network Adapters
Application Note DT-AN-IP-2 VLAN for DekTec Network Adapters 1. Introduction VLAN (Virtual LAN) is a technology to segment a single physical network into multiple independent virtual networks. The VLANs
More informationExam 1 Review Questions
CSE 473 Introduction to Computer Networks Exam 1 Review Questions Jon Turner 10/2013 1. A user in St. Louis, connected to the internet via a 20 Mb/s (b=bits) connection retrieves a 250 KB (B=bytes) web
More informationImplementing Open flow switch using FPGA based platform
Implementing Open flow switch using FPGA based platform Ting Liu Master of Telematics - Communication Networks and Networked Services (2 Submission date: June 2014 Supervisor: Yuming Jiang, ITEM Co-supervisor:
More informationOutline. Institute of Computer and Communication Network Engineering. Institute of Computer and Communication Network Engineering
Institute of Computer and Communication Network Engineering Institute of Computer and Communication Network Engineering Communication Networks Software Defined Networking (SDN) Prof. Dr. Admela Jukan Dr.
More informationHigh-Performance IP Service Node with Layer 4 to 7 Packet Processing Features
UDC 621.395.31:681.3 High-Performance IP Service Node with Layer 4 to 7 Packet Processing Features VTsuneo Katsuyama VAkira Hakata VMasafumi Katoh VAkira Takeyama (Manuscript received February 27, 2001)
More informationHow To Orchestrate The Clouddusing Network With Andn
ORCHESTRATING THE CLOUD USING SDN Joerg Ammon Systems Engineer Service Provider 2013-09-10 2013 Brocade Communications Systems, Inc. Company Proprietary Information 1 SDN Update -
More informationSDN, OpenFlow and the ONF
SDN, OpenFlow and the ONF OpenFlow/Software-Defined Networking (SDN) OpenFlow/SDN is emerging as one of the most promising and disruptive networking technologies of recent years. It has the potential to
More informationSDN and OpenFlow. Naresh Thukkani (ONF T&I Contributor) Technical Leader, Criterion Networks
SDN and OpenFlow Naresh Thukkani (ONF T&I Contributor) Technical Leader, Criterion Networks Open 2014 Open SDN Networking India Foundation Technology Symposium, January 18-19, 2015, Bangalore Agenda SDN
More informationSoftware Defined Networks
Software Defined Networks Damiano Carra Università degli Studi di Verona Dipartimento di Informatica Acknowledgements! Credits Part of the course material is based on slides provided by the following authors
More informationFibre Channel over Ethernet in the Data Center: An Introduction
Fibre Channel over Ethernet in the Data Center: An Introduction Introduction Fibre Channel over Ethernet (FCoE) is a newly proposed standard that is being developed by INCITS T11. The FCoE protocol specification
More informationOpenFlow: Enabling Innovation in Campus Networks
OpenFlow: Enabling Innovation in Campus Networks Nick McKeown Stanford University Presenter: Munhwan Choi Table of contents What is OpenFlow? The OpenFlow switch Using OpenFlow OpenFlow Switch Specification
More informationStateful vs. stateless traffic analysis
Stateful vs. stateless traffic analysis Rahul Patel Business Line Manager, Advanced Products Group Hifn, Inc. Introduction Over the past few years, the Internet has become a conduit of diverse and complex
More informationOpenFlow and Software Defined Networking presented by Greg Ferro. OpenFlow Functions and Flow Tables
OpenFlow and Software Defined Networking presented by Greg Ferro OpenFlow Functions and Flow Tables would like to thank Greg Ferro and Ivan Pepelnjak for giving us the opportunity to sponsor to this educational
More informationThis topic lists the key mechanisms use to implement QoS in an IP network.
IP QoS Mechanisms QoS Mechanisms This topic lists the key mechanisms use to implement QoS in an IP network. QoS Mechanisms Classification: Each class-oriented QoS mechanism has to support some type of
More informationQuality of Service (QoS) for Enterprise Networks. Learn How to Configure QoS on Cisco Routers. Share:
Quality of Service (QoS) for Enterprise Networks Learn How to Configure QoS on Cisco Routers Share: Quality of Service (QoS) Overview Networks today are required to deliver secure, measurable and guaranteed
More informationOpenFlow: History and Overview. Demo of OpenFlow@home routers
Affan A. Syed affan.syed@nu.edu.pk Syed Ali Khayam ali.khayam@seecs.nust.edu.pk OpenFlow: History and Overview Dr. Affan A. Syed OpenFlow and Software Defined Networking Dr. Syed Ali Khayam Demo of OpenFlow@home
More informationLecture 8. IP Fundamentals
Lecture 8. Internet Network Layer: IP Fundamentals Outline Layer 3 functionalities Internet Protocol (IP) characteristics IP packet (first look) IP addresses Routing tables: how to use ARP Layer 3 functionalities
More informationVXLAN: Scaling Data Center Capacity. White Paper
VXLAN: Scaling Data Center Capacity White Paper Virtual Extensible LAN (VXLAN) Overview This document provides an overview of how VXLAN works. It also provides criteria to help determine when and where
More informationWhite Paper Abstract Disclaimer
White Paper Synopsis of the Data Streaming Logical Specification (Phase I) Based on: RapidIO Specification Part X: Data Streaming Logical Specification Rev. 1.2, 08/2004 Abstract The Data Streaming specification
More informationFPGA Implementation of IP Packet Segmentation and Reassembly in Internet Router*
SERBIAN JOURNAL OF ELECTRICAL ENGINEERING Vol. 6, No. 3, December 2009, 399-407 UDK: 004.738.5.057.4 FPGA Implementation of IP Packet Segmentation and Reassembly in Internet Router* Marko Carević 1,a,
More informationOpenFlow Switch Specification
OpenFlow Switch Specification Version 1.3.1 (Wire Protocol 0x04) September 6, 2012 ONF TS-007 (Wire Protocol 0x04) ONF Document Type: OpenFlow Spec ONF Document Name: openflow-spec-v1.3.1 Disclaimer THIS
More informationOpenFlow Based Load Balancing
OpenFlow Based Load Balancing Hardeep Uppal and Dane Brandon University of Washington CSE561: Networking Project Report Abstract: In today s high-traffic internet, it is often desirable to have multiple
More informationFiber Channel Over Ethernet (FCoE)
Fiber Channel Over Ethernet (FCoE) Using Intel Ethernet Switch Family White Paper November, 2008 Legal INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR
More informationIPV6 流 量 分 析 探 讨 北 京 大 学 计 算 中 心 周 昌 令
IPV6 流 量 分 析 探 讨 北 京 大 学 计 算 中 心 周 昌 令 1 内 容 流 量 分 析 简 介 IPv6 下 的 新 问 题 和 挑 战 协 议 格 式 变 更 用 户 行 为 特 征 变 更 安 全 问 题 演 化 流 量 导 出 手 段 变 化 设 备 参 考 配 置 流 量 工 具 总 结 2 流 量 分 析 简 介 流 量 分 析 目 标 who, what, where,
More informationA Case for Overlays in DCN Virtualization Katherine Barabash, Rami Cohen, David Hadas, Vinit Jain, Renato Recio and Benny Rochwerger IBM
Presenter: Vinit Jain, STSM, System Networking Development, IBM System & Technology Group A Case for Overlays in DCN Virtualization Katherine Barabash, Rami Cohen, David Hadas, Vinit Jain, Renato Recio
More informationA DIY Hardware Packet Sniffer
A DIY Hardware Packet Sniffer Affordable Penetration Testing for the Individual Veronica Swanson: University of California, Irvine CyberSecurity for the Next Generation North American Round, New York 15
More informationAPPLICATION NOTE 211 MPLS BASICS AND TESTING NEEDS. Label Switching vs. Traditional Routing
MPLS BASICS AND TESTING NEEDS By Thierno Diallo, Product Specialist Protocol Business Unit The continuing expansion and popularity of the Internet is forcing routers in the core network to support the
More informationSoftware Defined Networking
Software Defined Networking Stefano Giordano Dipartimento di Ingegneria dell Informazione Università di Pisa 3D Reference model of ISDN Hourglass reference model of a TCP/IP network Network Ossification
More informationOpenFlow with Intel 82599. Voravit Tanyingyong, Markus Hidell, Peter Sjödin
OpenFlow with Intel 82599 Voravit Tanyingyong, Markus Hidell, Peter Sjödin Outline Background Goal Design Experiment and Evaluation Conclusion OpenFlow SW HW Open up commercial network hardware for experiment
More informationNetFlow probe on NetFPGA
Verze #1.00, 2008-12-12 NetFlow probe on NetFPGA Introduction With ever-growing volume of data being transferred over the Internet, the need for reliable monitoring becomes more urgent. Monitoring devices
More informationBenchmarking the SDN controller!
! SDN Testing Benchmarking the SDN controller! Ralph Daniels! Spirent Communications! Vice Chair, ONF Testing & Interoperability, Benchmarking! 2014 Open Networking Foundation At Spirent Communications
More informationQoS in PAN-OS. Tech Note PAN-OS 4.1. Revision A 2011, Palo Alto Networks, Inc.
QoS in PAN-OS Tech Note PAN-OS 4.1 Revision A Contents Overview... 3 Why QoS... 3 Learn about Applications in your Network... 3 Terms and Concepts... 3 Classification... 3 Priority Queues... 4 Limiting
More informationethernet services for multi-site connectivity security, performance, ip transparency
ethernet services for multi-site connectivity security, performance, ip transparency INTRODUCTION Interconnecting three or more sites across a metro or wide area network has traditionally been accomplished
More informationHow the emergence of OpenFlow and SDN will change the networking landscape
How the emergence of OpenFlow and SDN will change the networking landscape Software-defined networking (SDN) powered by the OpenFlow protocol has the potential to be an important and necessary game-changer
More informationHigh-performance vswitch of the user, by the user, for the user
A bird in cloud High-performance vswitch of the user, by the user, for the user Yoshihiro Nakajima, Wataru Ishida, Tomonori Fujita, Takahashi Hirokazu, Tomoya Hibi, Hitoshi Matsutahi, Katsuhiro Shimano
More informationOpenFlow Switch Specification Version 1.5.0 ( Protocol version 0x06 )
OpenFlow Switch Specification Version 1.5.0 ( Protocol version 0x06 ) December 19, 2014 ONF TS-020 Copyright 2014; Open Networking Foundation Disclaimer THIS SPECIFICATION HAS BEEN APPROVED BY THE BOARD
More informationSDN, a New Definition of Next-Generation Campus Network
SDN, a New Definition of Next-Generation Campus Network Contents Campus Evolution and Development Trends... 1 Three Changes to Drive the Campus Network Development... 2 Fundamental Changes in User Behaviors...2
More informationSupporting Information-Centric Networking in SDN
Supporting Information-Centric Networking in SDN Peng Li, Wu Muqing, Wang Ning, and Liu Hongbao Abstract Recently the Software-Defined Networking (SDN) has attracted increasing attention in the research
More informationSOFTWARE DEFINED NETWORKS REALITY CHECK. DENOG5, Darmstadt, 14/11/2013 Carsten Michel
SOFTWARE DEFINED NETWORKS REALITY CHECK DENOG5, Darmstadt, 14/11/2013 Carsten Michel Software Defined Networks (SDN)! Why Software Defined Networking? There s a hype in the industry!! Dispelling some myths
More informationTransport and Network Layer
Transport and Network Layer 1 Introduction Responsible for moving messages from end-to-end in a network Closely tied together TCP/IP: most commonly used protocol o Used in Internet o Compatible with a
More information