SDN Layers and Architecture Terminology
draft-haleplidis-sdnrg-layer-terminology-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-07-15
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                                                      E. Haleplidis
Internet-Draft                                                S. Denazis
Intended status: Informational                            O. Koufopavlou
Expires: January 16, 2014                           University of Patras
                                                          K. Pentikousis
                                                     Huawei Technologies
                                                           J. Hadi Salim
                                                       Mojatatu Networks
                                                           July 15, 2013

                SDN Layers and Architecture Terminology
              draft-haleplidis-sdnrg-layer-terminology-00

Abstract

   Software-Defined Networking introduces an abstraction layer and by
   doing so separates the Forwarding from the Control layer.  This
   separation can allow faster innovation cycles at both layers as
   experience has already shown.  However, there is increasing confusion
   as to what exactly SDN is, what is the layer stucture in an SDN
   architecture and how do layers interface with each other.  This
   document aims to provide a concise reference for future discussions
   in SDNRG.

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 January 16, 2014.

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

Haleplidis, et al.      Expires January 16, 2014                [Page 1]
Internet-Draft   SDN Layers and Architecture Terminology       July 2013

   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.  Requirements Language  . . . . . . . . . . . . . . . . . .  3
     1.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  SDN Layers and Architecture  . . . . . . . . . . . . . . . . .  5
     2.1.  Network Devices  . . . . . . . . . . . . . . . . . . . . .  6
     2.2.  Control Plane  . . . . . . . . . . . . . . . . . . . . . .  6
     2.3.  Management Plane . . . . . . . . . . . . . . . . . . . . .  7
     2.4.  Service Abstraction Layer  . . . . . . . . . . . . . . . .  7
     2.5.  Application Plane  . . . . . . . . . . . . . . . . . . . .  7
   3.  SDN Model View . . . . . . . . . . . . . . . . . . . . . . . .  8
     3.1.  ForCES . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     3.2.  Openflow . . . . . . . . . . . . . . . . . . . . . . . . .  8
     3.3.  NETCONF  . . . . . . . . . . . . . . . . . . . . . . . . .  8
   4.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  9
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
   7.  Informative References . . . . . . . . . . . . . . . . . . . . 12
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13

Haleplidis, et al.      Expires January 16, 2014                [Page 2]
Internet-Draft   SDN Layers and Architecture Terminology       July 2013

1.  Introduction

   Software-Defined Networking introduces an abstraction layer between
   the Forwarding and the Control layer in order to separate them.  This
   separation allows faster innovation for both layers as experience has
   already shown.  However, there is increasing confusion as to what
   exactly SDN is, what layers comprise the SDN architecture and what
   are the interfaces.  This draft attempts to provide a concise
   reference document for future discussions on SDN.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
Show full document text