[sfc] [Technical Errata Reported] RFC7665 (4974)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 21 March 2017 12:13 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E59891297C4 for <sfc@ietfa.amsl.com>; Tue, 21 Mar 2017 05:13:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 9LA7w0dkjAoq for <sfc@ietfa.amsl.com>; Tue, 21 Mar 2017 05:13:17 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45CDB1297E6 for <sfc@ietf.org>; Tue, 21 Mar 2017 05:13:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1D1F6B816C9; Tue, 21 Mar 2017 05:13:14 -0700 (PDT)
To: jmh@joelhalpern.com, cpignata@cisco.com, akatlas@gmail.com, db3546@att.com, aretana@cisco.com, james.n.guichard@huawei.com, jmh@joelhalpern.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: mphaneendra@gmail.com, sfc@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20170321121314.1D1F6B816C9@rfc-editor.org>
Date: Tue, 21 Mar 2017 05:13:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/d5SyouMNND2Vwd_RucLZJI_hRpE>
X-Mailman-Approved-At: Mon, 27 Mar 2017 04:38:10 -0700
Subject: [sfc] [Technical Errata Reported] RFC7665 (4974)
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Mar 2017 12:13:19 -0000
The following errata report has been submitted for RFC7665, "Service Function Chaining (SFC) Architecture". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7665&eid=4974 -------------------------------------- Type: Technical Reported by: Phaneendra Manda <mphaneendra@gmail.com> Section: 1.4 Original Text ------------- One or more service functions can be involved in the delivery of added-value services. A non-exhaustive list of abstract service functions includes: firewalls, WAN and application acceleration, Deep Packet Inspection (DPI), Lawful Intercept (LI), server load balancing, NAT44 [RFC3022], NAT64 [RFC6146], NPTv6 [RFC6296], HOST_ID injection, HTTP Header Enrichment functions, and TCP optimizer. Corrected Text -------------- One or more service functions can be involved in the delivery of added-value services. A non-exhaustive list of abstract service functions includes: firewalls, WAN and application acceleration, Deep Packet Inspection (DPI), Lawful Intercept (LI), server load balancing, NAT44 [RFC3022], NAT64 [RFC6146], NPTv6 [RFC6296], HOST_ID injection, HTTP Header Enrichment functions, TCP optimizer, Parental control etc. Notes ----- Parental control can be added in the non-exhaustive list of abstract service functions. Also this list cannot be fixed, so etc an be added at the end of the list. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC7665 (draft-ietf-sfc-architecture-11) -------------------------------------- Title : Service Function Chaining (SFC) Architecture Publication Date : October 2015 Author(s) : J. Halpern, Ed., C. Pignataro, Ed. Category : INFORMATIONAL Source : Service Function Chaining Area : Routing Stream : IETF Verifying Party : IESG
- [sfc] [Technical Errata Reported] RFC7665 (4974) RFC Errata System