Re: Last Call: draft-klensin-norm-ref (Handling Normative References for Standards Track Documents) to BCP

This document has a reasonable goal, but the implementation is objectionable.

The reasonable goal (from the introduction): 

    This document replaces the "hold on normative reference" rule with a
    "note downward normative reference and move on" approach for
    normative references to standards-track documents and BCPs.

The objectionable implementation: 

      A note is included in the reference text that indicates that the
      reference is to a target document of a lower maturity level, that
      some caution should be used since it may be less stable than the
      document from which it is being referenced

In many  cases (probably  the vast majority)  where a document  is advancing
despite a "downward normative reference", the referenced document (and the
technology  described  therein)  is  no  less stable  than  the  referencing
document, and  no "caution" is required.  It's  great to be able  to "make a
downward reference and move on", but  we should not be required to tell lies
and spread FUD.  

An acceptable implementation would be: 

      A note is included in the reference text that indicates that the
      reference is to a target document which is at a prior step in the
      official IETF standardization process.

That statement adequately captures the facts, and does not require the WG to
make dishonest statements or to spread FUD.

Another alternative, probably a better one, is simply to annotate each
reference with its standards status, and make no editorial comment about it
at all.

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf