[forces] [Errata Held for Document Update] RFC3746 (5338)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 09 September 2019 08:34 UTC

To: nmalykh@gmail.com, lily.l.yang@intel.com, rdantu@unt.edu, todd.a.anderson@intel.com, ram.gopal@nokia.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: martin.vigoureux@nokia.com, iesg@ietf.org, forces@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190909083438.E8239B80064@rfc-editor.org>
Date: Mon, 09 Sep 2019 01:34:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/forces/YgxcNlD5Cr-rcEQ9XAbjjY9bbp8>
Subject: [forces] [Errata Held for Document Update] RFC3746 (5338)
Precedence: list

The following errata report has been held for document update 
for RFC3746, "Forwarding and Control Element Separation (ForCES) Framework". 

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

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Nikolai Malykh <nmalykh@gmail.com>
Date Reported: 2018-04-27
Held by: Martin Vigoureux (IESG)

Section: 3.2

Original Text
-------------
   a change via asynchronous messages (see [4], Section 5, requirement
   #6).
...
   This architecture permits multiple FEs to be present in an NE.  [4]
   dictates that the ForCES Protocol must be able to scale to at least
   hundreds of FEs (see [4] Section 5, requirement #11).  Each of these
   FEs may potentially have a different set of packet processing
...
   When multiple FEs are present, ForCES requires that packets must be
   able to arrive at the NE by one FE and leave the NE via a different
   FE (See [4], Section 5, Requirement #3).  Packets that enter the NE


Corrected Text
--------------
   a change via asynchronous messages (see [4], Section 4, requirement
   #6).
...
   This architecture permits multiple FEs to be present in an NE.  [4]
   dictates that the ForCES Protocol must be able to scale to at least
   hundreds of FEs (see [4] Section 4, requirement #11).  Each of these
   FEs may potentially have a different set of packet processing
...
   When multiple FEs are present, ForCES requires that packets must be
   able to arrive at the NE by one FE and leave the NE via a different
   FE (See [4], Section 4, Requirement #3).  Packets that enter the NE


Notes
-----
Incorrect reference to Section 5.

see also: https://www.rfc-editor.org/verify_errata_select.php?eid=5338

--------------------------------------
RFC3746 (draft-ietf-forces-framework-13)
--------------------------------------
Title               : Forwarding and Control Element Separation (ForCES) Framework
Publication Date    : April 2004
Author(s)           : L. Yang, R. Dantu, T. Anderson, R. Gopal
Category            : INFORMATIONAL
Source              : Forwarding and Control Element Separation
Area                : Routing
Stream              : IETF
Verifying Party     : IESG

[forces] [Errata Held for Document Update] RFC374… RFC Errata System