Document: draft-ietf-ccamp-lmp-mib-10.txt
Review: Mary Barnes
Date: 27 oktober 2004 1

Assignment: 
------------ 
Link Management Protocol Management Information Base (Proposed Standard) - 4 of 11 
draft-ietf-ccamp-lmp-mib-10.txt 
Token: Bert Wijnen 
Reviewer: Mary Barnes 

Summary: 
--------- 
Draft is ready to publish as Proposed Standard with the correction of
the following editorial nits ( based on the assumption that it's been
reviewed/approved by MIB doctors and run through the MIB compilation
tools).



 Nits: 
----- 
- Needs updating to new template reflecting RFC 3668/3667. 
- Blank lines between authors in the document heading is not at all necessary. 
- Section 2: Introduction: The 2nd sentence is quite awkward and I
  would propose rewriting (at a minimum the word "which" should be
  changed to "whose")

  from: 

      Along with Generalized MPLS (GMPLS) [RFC3471], the Link Management
    Protocol [LMP], which primary purpose is to manage traffic engineering
    (TE) links, is one of the key components of this stan dardization
    activity."

  to something like: 

       Generalized MPLS (GMPLS) [RFC3471] and the Link Management Protocol
    [LMP] are key components of this standardization activity. The primary
    purpose of LMP is to manage traffic engineering (TE) links."

- Section 14.1 Normative References: Remove reference to RFC 2026 per
 updates to template (curiously, RFC 3668 and 3667 are already listed
 as references - do they really need to be as I've not seen this done
 in other drafts?)