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

From: RFC Errata System <[email-masked]>
Date: Tue, 17 Dec 2019 17:45:18 -0800 (PST)

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 <[email-masked]>

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