RFC 3746, "Forwarding and Control Element Separation (ForCES) Framework", April 2004

Errata ID: 5338
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Nikolai Malykh
Date Reported: 2018-04-27
Held for Document Update by: Martin Vigoureux
Date Held: 2019-09-09

Section 3.2 says:

   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

It should say:

   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

Report New Errata