Browse Prior Art Database

Problem Statement for Service Function Chaining (RFC7498)

IP.com Disclosure Number: IPCOM000241287D
Original Publication Date: 2015-Apr-01
Included in the Prior Art Database: 2015-Apr-14
Document File: 26 page(s) / 29K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

P. Quinn: AUTHOR [+4]

Abstract

The delivery of end-to-end services often requires various service functions including traditional network service functions (for example, firewalls and server load balancers), as well as application-specific features such as HTTP header manipulation. Service functions may be delivered within the context of an isolated user (e.g., a tenant) or shared amongst many users or user groups.

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

Internet Engineering Task Force (IETF)                     P. Quinn, Ed. Request for Comments: 7498                           Cisco Systems, Inc. Category: Informational                                   T. Nadeau, Ed. ISSN: 2070-1721                                                  Brocade                                                               April 2015

             Problem Statement for Service Function Chaining

Abstract

   This document provides an overview of the issues associated with the    deployment of service functions (such as firewalls, load balancers,    etc.) in large-scale environments.  The term "service function    chaining" is used to describe the definition and instantiation of an    ordered list of instances of such service functions, and the    subsequent "steering" of traffic flows through those service    functions.

   The set of enabled service function chains reflects operator service    offerings and is designed in conjunction with application delivery    and service and network policy.

   This document also identifies several key areas that the Service    Function Chaining (SFC) working group will investigate to guide its    architectural and protocol work and associated documents.

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    http://www.rfc-editor.org/info/rfc7498.

Quinn & Nadeau                Informational                     [Page 1]
 RFC 7498                  SFC Problem Statement               April 2015

 Copyright Notice

   Copyright (c) 2015 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 describ...