Document Action: 'Service Function Chaining Problem Statement' to Informational RFC (draft-ietf-sfc-problem-statement-13.txt)
The IESG <iesg-secretary@ietf.org> Mon, 23 February 2015 19:23 UTC
Return-Path: <iesg-secretary@ietf.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 EE16A1A6F0E; Mon, 23 Feb 2015 11:23:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ehCqjkkXQ0T9; Mon, 23 Feb 2015 11:23:16 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C99A41A6F02; Mon, 23 Feb 2015 11:23:14 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'Service Function Chaining Problem Statement' to Informational RFC (draft-ietf-sfc-problem-statement-13.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150223192314.25551.42551.idtracker@ietfa.amsl.com>
Date: Mon, 23 Feb 2015 11:23:14 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/rTLXKFfdqiSJ8LSZ15dpV6t-FeY>
Cc: sfc chair <sfc-chairs@tools.ietf.org>, sfc mailing list <sfc@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Feb 2015 19:23:18 -0000
The IESG has approved the following document: - 'Service Function Chaining Problem Statement' (draft-ietf-sfc-problem-statement-13.txt) as Informational RFC This document is the product of the Service Function Chaining Working Group. The IESG contact persons are Adrian Farrel and Alia Atlas. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-sfc-problem-statement/ Technical Summary This document provides an overview of the issues associated with the deployment of service functions (such as firewalls, load balancers) in large-scale environments. The term service function chaining is used to describe the definition and instantiation of an ordered set of instances of such service functions, and the subsequent "steering" of traffic flows through those service functions. Working Group Summary This document has been reviewed multiple times by many participants in the working group. Much of the content is widely supported, with minimal controversy. There has been some controversy around the content of section 3, which describes at a very high level the components of a service chaining solution. The working group chairs have concluded that the working group rough consensus is in favor of retaining that text in this document. Document Quality The document is in good shape, and the shepherd agrees with the chairs conclusion that it is ready for publication as an Informational RFC. There has been no formal review by outside experts, as this is an informational problem statement and does not therefore need any specified formal reviews. The shepherd has observed that the wg has received confirmation from all authors that all relevant IPR has been disclosed. There is one IPR disclosure which has caused the working group some concern. The chairs concluded that the WG had rough consensus to publish the document in the presence of the IPR disclosure. Personnel Document Shepherd: Joel Halpern Responsible Area Director: Alia Atlas