Priority based Flow Rule Request Message Processing Mechanism in the OpenFlow Switch

Document Type Active Internet-Draft (individual)
Last updated 2016-10-02
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
SDNRG                                                            X. Long
Internet-Draft                                                   W. Wang
Intended status: Informational                                   X. Gong
Expires: April 5, 2017                                            X. Que
                                                                   Q. Qi
                        Beijing University of Post and Telecommunication
                                                         October 2, 2016

  Priority based Flow Rule Request Message Processing Mechanism in the
                            OpenFlow Switch


   In the SDN, the controller is in charge of the maintenance and
   administration of variable aspects like the network topology and the
   network resources etc. of the whole network.  Administrative
   strategies are made upon these work and sent to the switches from the
   controller so as to instruct the network devices to apply appropriate
   policies to the data flows.  As for the data packet which reaches the
   ingress OpenFlow switch for the first time, the packet itself or a
   fraction of the packet will be encapsulated into a packet-in message
   and will be sent to the controller to request for a new flow rule.
   After the flow-mod message and the packet-out message are sent back
   to the switch from the controller, the determined forwarding action
   will be applied to the certain data flow.

   So far, the inbound latency caused by the creation of the packet-in
   message and the outbound latency caused by the receive and the
   execution of the flow-mod message are highlighted when it comes to
   the concerns about the latency and the effectiveness of the data
   transportation in the SDN[Mazu].  Attention to the studies on the
   processing order of the flow rule request message like the packet-in
   message and the packet-out message is comparatively low.  As the SDN
   continually grows in scale and complexity and the packets' forwarding
   policies become more recursive and dynamic, the number of the
   switches under the administration of the same controller is elevated
   and unavoidably causes the network congestion problem widespread.
   The scale of modern networks and data-centers and the associated
   operational expense deteriorates the delay problem in the network
   with congestion.  The ability to help the services with high priority
   be processed without delay becomes critical.

   This document proposes the combination of appending a priority tag to
   the packet-in message and the Priority based Flow Rule Request
   Message Processing Mechanism(PFRRMPM) as a solution to help the data
   flow with high priority or lantency-sensitive to acquire the

Long, et al.              Expires April 5, 2017                 [Page 1]
Internet-Draft                   PFRRMPM                    October 2016

   forwarding rule without or with shorter waiting latency when there
   are excess flow rule request messages in the SDN.

Status of This Memo

   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
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at

   Internet-Drafts are draft documents valid for a maximum of six months
   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."

   This Internet-Draft will expire on April 5, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   ( in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Flow Rule Request Message and Problem Analysis  . . . . . . .   5
   5.  Priority based Flow Rule Request Message Processing Mechanism   6
Show full document text