errata logo graphic

Found 4 records.

Status: Verified (3)

RFC5812, "Forwarding and Control Element Separation (ForCES) Forwarding Element Model", March 2010

Source of RFC: forces (rtg)

Errata ID: 2576

Status: Verified
Type: Editorial

Reported By: Jamal Hadi Salim
Date Reported: 2010-10-16
Verifier Name: Adrian Farrel
Date Verified: 2010-10-17

Section Table 1 says:

   |                |            |               |     information     |
   |   FE Protocol  |      2     |      [2]      |  Defines parameters |
   |     Object     |            |               |    for the ForCES   |
   |                |            |               |  protocol operation |


It should say:

   |                |            |               |     information     |
   |   FE Protocol  |      2     |    RFC 5810   |  Defines parameters |
   |     Object     |            |               |    for the ForCES   |
   |                |            |               |  protocol operation |


Notes:

Reference [2] used to be the reference to the I-D that became RFC 5810


Errata ID: 3371

Status: Verified
Type: Editorial

Reported By: Evangelos Haleplidis
Date Reported: 2012-10-07
Verifier Name: Adrian Farrel
Date Verified: 2012-11-04

Throughout the document, when it says:

Page 65 Section 4.7.2 paragraph 1
<product> lists the allowed frame formats...

Page 95 Section 5.1
      <xsd:element name="frameProduced"> 

It should say:

Page 65 Section 4.7.2 paragraph 1
<product> MAY lists the allowed frame formats...

Page 65 Section 4.7.2 paragraph 1 additional text at end of paragraph
The <product> element MUST contain at least either a frame format or a metadata.

Page 95 Section 5.1
      <xsd:element name="frameProduced" minOccurs="0">

Notes:

Issue with frameProduced being mandatory for an output port.


Errata ID: 3487

Status: Verified
Type: Editorial

Reported By: Jamal Hadi Salim
Date Reported: 2013-02-18
Verifier Name: Adrian Farrel
Date Verified: 2013-02-19

Section 5.1 says:

                  <component access="read-only" componentID="7">
                    <name>FEState</name>
                    <synopsis>State of this FE</synopsis>
                    <typeRef>FEStateValues</typeRef>
                  </component>

It should say:

                  <component access="read-write" componentID="7">
                    <name>FEState</name>
                    <synopsis>State of this FE</synopsis>
                    <typeRef>FEStateValues</typeRef>
                  </component>

Notes:

FEObject FEState (component ID 7) is read-write. It was mistakenly
labelled read-only


Status: Rejected (1)

RFC5812, "Forwarding and Control Element Separation (ForCES) Forwarding Element Model", March 2010

Source of RFC: forces (rtg)

Errata ID: 2577

Status: Rejected
Type: Editorial

Reported By: Jamal Hadi Salim
Date Reported: 2010-10-16
Rejected by: Adrian Farrel
Date Rejected: 2011-07-24

Section global says:

I dont know where to capture this, but it needs to be
captured somewhere and i couldnt think of a better place..
This is in regards to the XML definitions..

The baseID of events, componentIDs and capabilitiyIDs should be unique
within the LFB. The schema now distinguishes per category, not globally.

It should say:

It would valuable to be able to validate via the schema that there is
uniqueness.

Notes:


--VERIFIER NOTES--
This Erratum is rejected after consultation with the ForCES chair.

The LFB Class is unique globaly. The LFB instance is unique per LFB.
The LFB components are uniquely identified by LFB class::instance id.
Therefore by inference, the LFB events, componentIDs and capabilitiyIDs
are globaly unique.


Report New Errata