Browse Prior Art Database

Software-Defined Networking: A Perspective from within a Service Provider Environment (RFC7149) Disclosure Number: IPCOM000235525D
Original Publication Date: 2014-Mar-01
Included in the Prior Art Database: 2014-Mar-06
Document File: 40 page(s) / 47K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Boucadair: AUTHOR [+1]


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 (e.g., customer-specific addressing scheme management, dynamic path computation to reach a set of destination prefixes, dynamic establishment of tunnels, etc.); Quality of Service (e.g., traffic classification, marking, conditioning, and scheduling); security (e.g., filters to protect customer premises from network-originated attacks, to avoid malformed route announcements, etc.); and management (e.g., fault detection and processing).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

Internet Engineering Task Force (IETF)                      M. Boucadair Request for Comments: 7149                                  C. Jacquenet Category: Informational                                   France Telecom ISSN: 2070-1721                                               March 2014

             Software-Defined Networking: A Perspective from                  within a Service Provider Environment


   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 to clarify the SDN landscape by    providing a perspective on requirements, issues, and other    considerations about SDN, as seen from within a service provider    environment.

   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 an 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 document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

 Boucadair & Jacquenet         Informational                     [Page 1]
 RFC 7149                         On SDN                       March 2014

 Copyright Notice

   Copyright (c) 2014 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 Provisi...