Software-Defined Networking: A Service Provider's Perspective
draft-sin-sdnrg-sdn-approach-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Mohamed Boucadair  , Christian Jacquenet 
Last updated 2013-03-20
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
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 Working Group                                         M. Boucadair
Internet-Draft                                              C. Jacquenet
Intended status: Informational                            France Telecom
Expires: September 21, 2013                               March 20, 2013

     Software-Defined Networking: A Service Provider's Perspective
                    draft-sin-sdnrg-sdn-approach-00

Abstract

   Software-Defined Networking (SDN) has been one of the major buzz
   words of the networking industry for the past couple of years.  And
   yet, no clear definition of what SDN actually covers has been broadly
   admitted so far.  This document aims at contributing to the
   clarification of the SDN landscape.

   It is not meant to endlessly discuss what SDN truly means, but rather
   to suggest a functional taxonomy of the techniques that can be used
   under a SDN umbrella and to elaborate on the various pending issues
   the combined activation of such techniques inevitably raises.  As
   such, a definition of SDN is only mentioned for the sake of
   clarification.

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 http://datatracker.ietf.org/drafts/current/.

   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 September 21, 2013.

Copyright Notice

   Copyright (c) 2013 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

Boucadair & Jacquenet  Expires September 21, 2013               [Page 1]
Internet-Draft                   On SDN                       March 2013

   (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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Context . . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  What is In and What is Out? . . . . . . . . . . . . . . . . .   4
     2.1.  Remember the Past . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Be Pragmatic  . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Measure Experience Against Expectations . . . . . . . . .   5
     2.4.  Design Carefully  . . . . . . . . . . . . . . . . . . . .   6
     2.5.  There is Life Beyond OpenFlow . . . . . . . . . . . . . .   6
     2.6.  Non Goals . . . . . . . . . . . . . . . . . . . . . . . .   7
   3.  A Definition of Software-Defined Networking . . . . . . . . .   7
     3.1.  A Tautology . . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  On Flexibility  . . . . . . . . . . . . . . . . . . . . .   8
     3.3.  A Tentative Definition  . . . . . . . . . . . . . . . . .   8
     3.4.  Functional Meta-Domains . . . . . . . . . . . . . . . . .   8
   4.  Disscussion . . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  Full Automation: a Viable Objective?  . . . . . . . . . .   9
     4.2.  The Intelligence resides in the PDP . . . . . . . . . . .  10
     4.3.  Simplicity and Adaptability vs. Complexity  . . . . . . .  10
     4.4.  Performance & Scalability . . . . . . . . . . . . . . . .  11
     4.5.  Risk Assessement  . . . . . . . . . . . . . . . . . . . .  11
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   8.  Informative References  . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

1.1.  Context

   The Internet has become the federative network that supports a wide
   range of service offerings.  The delivery of network services such as
   IP VPNs assumes the combined activation of various capabilities that
   include (but are not necessarily limited to) forwarding and routing
Show full document text