I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
Please resolve these comments along with any other Last Call
comments you may receive.
Document..........: draft-ietf-mpls-tp-requirements
Reviewer..........: Christian Vogt
Review date.......: July 15, 2009
Summary: This draft is basically ready for publication, but has nits
that should be fixed before publication.
This document specifies protocol requirements for MPLS in packet
transport networks. The document is of very good quality, with an
elaborate introduction explaining the background for this document.
Two editorial nits that the authors should consider addressing prior
to publication of this document are the following:
- The fourth paragraph on page 6, which is part of the introduction,
already specifies a requirement. I suggest moving this to section
2, since this is the section that is dedicated to requirements.
- The first paragraph of section 2 is a duplicate; it already appears in
the introduction. I suggest removing it from section 2. The
paragraph is important for the reader to understand the scope of the
document, and hence should retain its prominent position in the
introduction rather than the position in section 2.
Best regards,
- Christian
On Jul 2, 2009, The IESG wrote:
The IESG has received a request from the Multiprotocol Label
Switching WG
(mpls) to consider the following document:
- 'MPLS-TP Requirements '
<draft-ietf-mpls-tp-requirements-09.txt> as a Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to
the
ietf@xxxxxxxx mailing lists by 2009-07-16. Exceptionally,
comments may be sent to iesg@xxxxxxxx instead. In either case, please
retain the beginning of the Subject line to allow automated sorting.
The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-requirements-09.txt
IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18021&rfc_flag=0
_______________________________________________
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf