Document: draft-ietf-mpls-tp-nm-req-05.txt
	MPLS TP Network Management Requirements
Reviewer: Joel M. Halpern
Review Date: 25-Sept-2009
IETF LC End Date: 4-Oct-2009
IESG Telechat date: 8-Oct-2009

Summary: This document is probably ready for publication as a Proposed Standard

Major issues: None

Minor issues:
Is it reasonable for the references in the sentence:
    In writing this document, the authors assume the reader is
    familiar with references [12] and [15].
to be informational references?  One of the definitions of normative I have seen is "you have to have read that to correctly understand this" 
which seems to be what the sentence says.

It is slightly unclear how it is anticipated this document will be used. 
  If it is expected that the document will be cited in other (solution or architecture) documents, which are explaining how they meet these requirements, then there are two loosely related issues:
1) There is some descriptive text which may be intended to also be providing requirements.
2) The actual requirements are not named or numbered, so it will be difficult for any other document to say "we provide A-Q, but we do not provide R for this reason ..."
I understand that it may be too late to actually change this, and that the intended usage may be such that these two are non-issues, but I would appreciate clarification.