Re: [sfc] [Technical Errata Reported] RFC7665 (4974)

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Tue, 21 March 2017 12:31 UTC

From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
CC: "Joel M. Halpern" <jmh@joelhalpern.com>, Alia Atlas <akatlas@gmail.com>, Deborah Brungard <db3546@att.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, James N Guichard <james.n.guichard@huawei.com>, "mphaneendra@gmail.com" <mphaneendra@gmail.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [Technical Errata Reported] RFC7665 (4974)
Thread-Index: AQHSojyHsWWY1YTYtkGdHTzXuUzu7qGffJeA
Date: Tue, 21 Mar 2017 12:31:03 +0000
Message-ID: <29F54793-8F6B-450E-8927-C566623EBB09@cisco.com>
References: <20170321121314.1D1F6B816C9@rfc-editor.org>
In-Reply-To: <20170321121314.1D1F6B816C9@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.150.49.188]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5706B86FC9976E4396BCC99C07364017@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/WR46k94Vzvs-j4nZ1y_vn2SCZcU>
Subject: Re: [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:31:07 -0000

I do not believe this edit is necessary.

The sentence starts with “A non-exhaustive list”, which sets the tone and context for the enumeration of abstract service functions.

Thanks,

— Carlos.

> On Mar 21, 2017, at 8:13 AM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> 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

Re: [sfc] [Technical Errata Reported] RFC7665 (49… Carlos Pignataro (cpignata)