Programming Model for Protocol Oblivious Forwarding SDN Networks
draft-irtf-sdnrg-pop-00

Document Type Active Internet-Draft (sdnrg RG)
Last updated 2017-01-05
Stream IRTF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream IRTF state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
INTERNET-DRAFT                                                   Y. Tian
Intended Status: Informational               Univ. Sci. & Tech. of China
Expires: July 6, 2017                                                   
                                                                        
                                                                        
                                                                        
                                                         January 5, 2017

   Programming Model for Protocol Oblivious Forwarding SDN Networks 
                        draft-irtf-sdnrg-pop-00

Abstract

   This document presents POP, a Software-Defined Networking (SDN)
   programming model for the Protocol Oblivious Forwarding (POF)
   network. POF is an SDN forwarding plane technology proposed by
   Huawei. A POF forwarding element (FE) does no need to understand the
   packet format, and can be programmed to support new forwarding
   protocols. POP enables user to define forwarding protocols and
   program the POF SDN network on the centralized control plane with
   algorithmic policies that are expressed with high-level programming
   languages.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   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
   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

 

<Author>                 Expires <Expiry Date>                  [Page 1]
INTERNET DRAFT              <Document Title>                <Issue Date>

Copyright and License 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
   (http://trustee.ietf.org/license-info) 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
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  4
   2  Programming Model . . . . . . . . . . . . . . . . . . . . . . .  4
   3  Protocol Specification Language . . . . . . . . . . . . . . . .  5
   4  Programming APIs for Protocol Oblivious Networking Algorithm  .  7
     4.1 Packet Operation API . . . . . . . . . . . . . . . . . . . .  7
     4.2 Net Topology Search API  . . . . . . . . . . . . . . . . . . 10
     3.3 Path Planning API  . . . . . . . . . . . . . . . . . . . . . 12
   5  Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
   6  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     6.1  Normative References  . . . . . . . . . . . . . . . . . . . 15
     6.2  Informative References  . . . . . . . . . . . . . . . . . . 15
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15

 

<Author>                 Expires <Expiry Date>                  [Page 2]
INTERNET DRAFT              <Document Title>                <Issue Date>

1  Introduction

   Software-Defined Networking (SDN)[RFC7149] gives operators
   programmatic control over their networks. In SDN, the control plane
   is physically separate from the forwarding plane, and one control
   plane controls multiple forwarding devices. In SDN, a common, open,
   vendor-agnostic interface between the control plane and the
   forwarding plane, which may contain forwarding devices from different
   hardware and software vendors, is required. OpenFlow is such an
   interface. In OpenFlow, operators express their rules with the
   abstractions that could match packets on a dozen header fields (e.g.,
   MAC addresses, IP addresses, protocol, TCP/UDP port numbers, etc.),
   and specify the corresponding actions (e.g., output, drop,
Show full document text