[sfc] [Editorial Errata Reported] RFC8300 (5939)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 18 December 2019 01:45 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 68EEF120045 for <sfc@ietfa.amsl.com>; Tue, 17 Dec 2019 17:45:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 AfvdkgQPQWiZ for <sfc@ietfa.amsl.com>; Tue, 17 Dec 2019 17:45:36 -0800 (PST)
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 0CD82120043 for <sfc@ietf.org>; Tue, 17 Dec 2019 17:45:36 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 166ECF4070F; Tue, 17 Dec 2019 17:45:18 -0800 (PST)
To: paulq@cisco.com, uri.elzur@intel.com, cpignata@cisco.com, db3546@att.com, aretana.ietf@gmail.com, martin.vigoureux@nokia.com, james.n.guichard@futurewei.com, jmh@joelhalpern.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: alissa@cooperw.in, sfc@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20191218014518.166ECF4070F@rfc-editor.org>
Date: Tue, 17 Dec 2019 17:45:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/w0UN5Du714E5i-bpeqaSFiCx6wk>
X-Mailman-Approved-At: Tue, 17 Dec 2019 19:04:25 -0800
Subject: [sfc] [Editorial Errata Reported] RFC8300 (5939)
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 18 Dec 2019 01:45:37 -0000

The following errata report has been submitted for RFC8300,
"Network Service Header (NSH)".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid5939

--------------------------------------
Type: Editorial
Reported by: Alissa Cooper <alissa@cooperw.in>

Section: 8.2.1

Original Text
-------------
Given that NSH is transport independent, as mentioned above, a secure transport, such as IPsec can be used for carry NSH.

Corrected Text
--------------
Given that NSH is transport independent, as mentioned above, a secure transport, such as IPsec, can be used for carrying NSH.

Notes
-----
There is subject-verb disagreement in the RFC text.

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. 

--------------------------------------
RFC8300 (draft-ietf-sfc-nsh-28)
--------------------------------------
Title               : Network Service Header (NSH)
Publication Date    : January 2018
Author(s)           : P. Quinn, Ed., U. Elzur, Ed., C. Pignataro, Ed.
Category            : PROPOSED STANDARD
Source              : Service Function Chaining
Area                : Routing
Stream              : IETF
Verifying Party     : IESG