RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Held for Document Update (1)

RFC 7498, "Problem Statement for Service Function Chaining", April 2015

Source of RFC: sfc (rtg)

Errata ID: 4527
Status: Held for Document Update
Type: Editorial

Reported By: Igor Duarte Cardoso
Date Reported: 2015-11-09
Held for Document Update by: Alia Atlas
Date Held: 2015-11-11

Section 4 says:

Although this problem statement does not introduce any protocols,
   when considering service function chaining, the three main areas
   begin investigated (see Section 3) by the WG have security aspects
   that warrant consideration.

It should say:

Although this problem statement does not introduce any protocols,
   when considering service function chaining, the three main areas
   being investigated (see Section 3) by the WG have security aspects
   that warrant consideration.

Notes:

"begin" replaced by "being", it seems to have been a missed typo.

Status: Rejected (1)

RFC 7498, "Problem Statement for Service Function Chaining", April 2015

Source of RFC: sfc (rtg)

Errata ID: 5336
Status: Rejected
Type: Technical

Reported By: Boyuan Yan
Date Reported: 2018-04-26
Rejected by: Martin Vigoureux
Date Rejected: 2018-05-22

Section 3.3 says:

   The SFC encapsulation also carries data-plane metadata that provides
   the ability to exchange information between logical classification
   points and service functions (and vice versa) and between service
   functions.  Metadata is not used as forwarding information to deliver
   packets along the service overlay.

It should say:

   The SFC encapsulation also carries data-plane metadata that provides
   the ability to exchange information between logical classification
   points and service functions (and vice versa) and between service
   functions.  Metadata is used as forwarding information to deliver
   packets along the service overlay.

Notes:

Error occurs in the last sentence of 2nd paragraph in Section 3.3. Metadata should be used as forwarding information to deliver packets along the service overlay.
--VERIFIER NOTES--
SFC Path identification is not part of the metadata.

Report New Errata