Document: draft-ymbk-downref-02
Reviewer: John Loughney
Date: June 9, 2004

Generally, I think this is a good thing.  Some nits and two comments:

1) Section 1:

   The Internet Standards Process [RFC2026] Section 4.2.4 specifies:

   Standards track specifications normally must not depend on other
      standards track specifications which are at a lower maturity level
      or on non standards track specifications other than referenced
      specifications from other standards bodies.

-> indent sentence starting from "Standards.

2) Informative References empty.
3) Examples are always nice ...

Comments:

1) Section 3. The Procedure to be Used

   This section outlines the IETF LC procedure, however, I wonder if it
   also reasonable to mark this "down reference" inside of the RFC as well?
  
2) Section 5. Security Considerations

   This document is not known to create any new vulnerabilities for the
   internet.  On the other hand, inappropriate or excessive use of the
   process might be considered a down-grade attack on the quality of
   IETF standards, or worse, on the rigorous review of security aspects
   of standards.

 -> this section talks about a down-grade attack, but I wonder if there
    would be an upgrade attack? What I mean is that it would be possible to
    'upgrade' that status of a document the percieved status of a document
    by normatively referencing a standard in this manner.

John