RFC 7498 on Problem Statement for Service Function Chaining
rfc-editor@rfc-editor.org Mon, 13 April 2015 23:35 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0EFD1ACEA4; Mon, 13 Apr 2015 16:35:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NAPfPoTNGvvW; Mon, 13 Apr 2015 16:35:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 12A641AD353; Mon, 13 Apr 2015 16:35:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7C6A0180206; Mon, 13 Apr 2015 16:34:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7498 on Problem Statement for Service Function Chaining
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150413233449.7C6A0180206@rfc-editor.org>
Date: Mon, 13 Apr 2015 16:34:49 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/7qy86j7w_gmk-ZhN257DHTaiEAk>
Cc: sfc@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 23:35:28 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7498
Title: Problem Statement for Service Function
Chaining
Author: P. Quinn, Ed.,
T. Nadeau, Ed.
Status: Informational
Stream: IETF
Date: April 2015
Mailbox: paulq@cisco.com,
tnadeau@lucidvision.com
Pages: 13
Characters: 28970
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-sfc-problem-statement-13.txt
URL: https://www.rfc-editor.org/info/rfc7498
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.
This document is a product of the Service Function Chaining Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC