RFC 7665 on Service Function Chaining (SFC) Architecture

rfc-editor@rfc-editor.org Mon, 19 October 2015 22:57 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 9DD5B1B2E37; Mon, 19 Oct 2015 15:57:52 -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 FkOHYT9iVKML; Mon, 19 Oct 2015 15:57:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD0D1ACE71; Mon, 19 Oct 2015 15:57:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B5ADC187DBF; Mon, 19 Oct 2015 15:57:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7665 on Service Function Chaining (SFC) Architecture
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151019225714.B5ADC187DBF@rfc-editor.org>
Date: Mon, 19 Oct 2015 15:57:14 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/lzrqVZWqz9nuP-isZREKczRQUOA>
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Oct 2015 22:57:52 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7665

        Title:      Service Function Chaining (SFC) Architecture 
        Author:     J. Halpern, Ed.,
                    C. Pignataro, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       October 2015
        Mailbox:    jmh@joelhalpern.com, 
                    cpignata@cisco.com
        Pages:      32
        Characters: 74825
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sfc-architecture-11.txt

        URL:        https://www.rfc-editor.org/info/rfc7665

        DOI:        http://dx.doi.org/10.17487/RFC7665

This document describes an architecture for the specification,
creation, and ongoing maintenance of Service Function Chains (SFCs)
in a network.  It includes architectural concepts, principles, and
components used in the construction of composite services through
deployment of SFCs, with a focus on those to be standardized in the
IETF.  This document does not propose solutions, protocols, or
extensions to existing protocols.

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