Subject: [forces] [Editorial Errata Reported] RFC5812 (3371)

From: RFC Errata System <[email-masked]>
Date: Sun, 7 Oct 2012 14:37:07 -0700 (PDT)

The following errata report has been submitted for RFC5812,
"Forwarding and Control Element Separation (ForCES) Forwarding Element Model".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5812&eid=3371

--------------------------------------
Type: Editorial
Reported by: Evangelos Haleplidis <[email-masked]>

Section: GLOBAL

Original Text
-------------
Page 65
<product> lists the allowed frame formats...

For the XML schema:
Page 95
      <xsd:element name="frameProduced"> 

Corrected Text
--------------
Page 65
<product> MAY lists the allowed frame formats...

Also, I think it should be valuable to say in the end:
The <product> element MUST contain at least either a frame format or a metadata.

For the XML schema:
Page 95
      <xsd:element name="frameProduced" minOccurs="0">

Notes
-----
Issue with frameProduced being mandatory for an output port.

Instructions:
-------------
This errata 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 (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5812 (draft-ietf-forces-model-16)
--------------------------------------
Title               : Forwarding and Control Element Separation (ForCES) Forwarding Element Model
Publication Date    : March 2010
Author(s)           : J. Halpern, J. Hadi Salim
Category            : PROPOSED STANDARD
Source              : Forwarding and Control Element Separation
Area                : Routing
Stream              : IETF
Verifying Party     : IESG