Some editorial nits on the model draft

[McCann Peter-A001034 <[e-mail]>]

There are a few misplaced angle brackets in the document.

Section 4.5.6:  >alias> SHOULD BE <alias>

Section 4.7:    < version> SHOULD BE <version>
                <LFBClassDef< SHOULD BE <LFBClassDef>

Section 4.7.2:  <inputPort > SHOULD BE <inputPort>
                < expectation> SHOULD BE <expectation>
                <inputPorts< SHOULD BE <inputPorts>


Throughout the document:
  REPLACE "a metadata" with "a metadatum"

Section 4.7.2:

  ot the corresponding <ref> element
SHOULD BE:
  of the corresponding <ref> element

Section 4.7.3: < outputPort> SHOULD BE <outputPort>


Section 4.7.6.1:

  ealier
SHOULD BE:
  earlier

      The example event Gah10field1 illustrates the
      how the column
SHOULD BE:
      The example event Gah10field1 illustrates
      how the column


Section 4.7.6.3:

   then
   the The report MUST use a protocol format
SHOULD BE:
   then
   the report MUST use a protocol format


Section 4.8.5.2:

   < eventLessThan/>
SHOULD BE:
   <eventLessThan/>

   o  For a <eventGreaterThan/> condition with threshold T, once the
      event has been generated at least once it MUST NOT be generated
      again until the field first becomes less than or equal to T - -V,
      and then exceeds T.
Did you mean to say "T - V" here?  "T - -V" is technically "T + V".


Section 8:

  show how a data plain LFB might be build.
SHOULD BE:
  show how a data plane LFB might be built.

   interface carry Frame Relay traffic.
SHOULD BE:
   interface that carries Frame Relay traffic.


Section 8.1:

   useful statistics.  But it serves
SHOULD BE:
   useful statistics, but it serves

   are sent as meta- data,
SHOULD BE:
   are sent as metadata,


Section 8.4:

  Once common
SHOULD BE:
  One common