Re: [Lime] WGLC: draft-ietf-lime-yang-oam-model-08

["Adrian Farrel" <[e-mail]>]

Hi,

I read through this document again and think it is ready for publication.

Here are some minor things to ix along the way.

Thanks,
Adrian
===
You might sort out the line lengths.
---
Abstract is missing a final period.
---
Some of the references in sections 1 8 and 9 seem to be duplicated.
---
The last sentence of section 2 presumably belongs with the first 
paragraph.
---
The text in section 2 that defines the notation used in the trees that
are found in this document is useful, but I suspect it of being generic.
(It would be nice if this was in a separate document so that everyone
can reference it, but that is not the job of these authors or this WG.)

I did find several parts of the text confusing and I wondered whether:
- you can can drop the statuses that are not used in this document
  (I think there are no deprecated or obsoleted objects)
- add the other flags that are used (I see, "w" although I am surprised
  to find what is effective a write-only object so perhaps that is an
  error?)
- give simple examples (because "x" and "-x" may be hard to distinguish)
---
In 4 you have
   Under each MA, there can be two or more MEPs (Maintenance Association
   End Points).
But your primary expansion of MEP in section 2.1 is different.
---
Sections 1 and 2.1 use "RPC" the rest of the document uses "rpc"
---
Section 4.4 has
   Please refer to Section 4 for the complete
   data hierarchy
which is a bit odd given that we are in the middle of section 4.
---
Not asking you to do it, but why after the whole of section 4, why are
there no "fragments" in section 4.5?
---
A number of description clauses need to begin with capital letters.
---
loss-of-continuity refers to the receiving MEP's configured CC-V
reception period.  I cannot find where I can read the value of that.
---
Any reason why sometimes

      leaf cc-transmit-interval {
        type Interval;
        description
          "Interval between echo requests";
      }

and sometimes

      leaf interval {
        type Interval;
        description
          "Interval between echo requests";
      }
---
Why is there a minimum packet-size of 64 octets?
Why can't I send smaller CC and CV packets?
---
Stray text "YANG module of OAM" right at the end of the module?
---
6.2 has MEPID and MEP-ID and MEP ID.
---
6.2 has
   In this document we propose to extend the range to 0 to
   65535.
s/propose to extend/extend/
---
6.3 has "MAID" unexpanded.  This is probably just the ID of the MA, but
...
---
Section 7 has
   This section demonstrates the usability of the connection-oriented
   YANG OAM data model to various connection-oriented OAM technologies,
   e.g., TRILL and MPLS-TP.
This should probably be
   This section demonstrates the applicability of the connection-oriented
   YANG OAM data model to TRILL and MPLS-TP.
---
I think the affiliations and emails of the Contributors and Authors need
to be double-checked.