Document:   draft-ietf-mpls-ecmp-bcp-01.txt
Reviewer: john.loughney@nokia.com
Review Date:  Wednesday 9/14/2005 6:39 AM CST
LC Date:  9/21/2005

Summary: I think that this document needs a revision, I think
clarifications on my open issues would be a good thing, and probably
would only require a few extra lines of text.

Open issues:

1) Abstract says that the document "... makes best practice
recommendations ..." but is listed as a Standards Track document in the
draft header.  This is confusing - is it a standards track document or
BCP?

2) Section 3 Recommendations for Avoiding ECMP Treatment, seems to
define a new attribute.  I'm not an MPLS expert, so I don't know if this
is a new attribute or if it is defined elsewhere.  If it is defined
elsewhere, I think a pointer to the specification is needed.

3) Security consideration section should have some text about security.
Do current EMCP practices have any security issues?  If not, then say
that.

4) Lots of ID nit problems, here is the report.

John


idnits 1.78 

tmp/draft-ietf-mpls-ecmp-bcp-01.txt:

tmp/draft-ietf-mpls-ecmp-bcp-01.txt(270): Line is too long: the
offending characters are 'S'
tmp/draft-ietf-mpls-ecmp-bcp-01.txt(275): Line is too long: the
offending characters are 'el'
tmp/draft-ietf-mpls-ecmp-bcp-01.txt(277): Line is too long: the
offending characters are 'ck'
tmp/draft-ietf-mpls-ecmp-bcp-01.txt(279): Line is too long: the
offending characters are 'load'


  Checking nits according to http://www.ietf.org/ID-Checklist.html:
  * The document seems to lack an IANA Considerations section.
    
    Checking conformance with RFC 3978/3979 boilerplate...

  * The document seems to lack an RFC 3978 Section 5.5 Disclaimer --
    however, there's a paragraph with a matching beginning. Boilerplate
error?

  (Expected a match on the following text:
    "This document and the information contained herein are provided on
    an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
    REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
    INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
    IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
  
   ... but found this:
    "This document and the information contained herein are provided on
    an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
    REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
    INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
    IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
    THE INFOR-MATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
.............^
    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.")


  * The document seems to lack an RFC 3979 Section 5, para 1 IPR
Disclosure
    Acknowledgement. 

  (Expected a match on the following text:
    "The IETF takes no position regarding the validity or scope of any
    Intellectual Property Rights or other rights that might be claimed
to
    pertain to the implementation or use of the technology described in
    this document or the extent to which any license under such rights
    might or might not be available; nor does it represent that it has
    made any independent effort to identify any such rights.
Information
    on the procedures with respect to rights in RFC documents can be
    found in BCP 78 and BCP 79.")

  * The document seems to lack an RFC 3979 Section 5, para 2 IPR
Disclosure
    Acknowledgement. 

  (Expected a match on the following text:
    "Copies of IPR disclosures made to the IETF Secretariat and any
    assurances of licenses to be made available, or the result of an
    attempt made to obtain a general license or permission for the use
of
    such proprietary rights by implementers or users of this
    specification can be obtained from the IETF on-line IPR repository
at
    http://www.ietf.org/ipr.")

  * The document seems to lack an RFC 3979 Section 5, para 3 IPR
Disclosure
    Invitation. 

  (Expected a match on the following text:
    "The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    this standard.  Please address the information to the IETF at
    ietf-ipr@ietf.org.")


  Checking nits according to
http://www.ietf.org/ietf/1id-guidelines.txt:
  * The document seems to lack a 1id_guidelines paragraph about
    Internet-Drafts being working documents. 

  (Expected a match on the following text:
    "Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as
Internet-Drafts.")