Document: draft-ietf-ipcdn-subscriber-mib-15.txt
From: John Loughney
Date: 25 september 2004 

> Reviews should focus on these questions: "Is this document a reasonable
> contribution to the area of Internet engineering which it covers? If
> not, what changes would make it so?"

Yes, it is.  Document seems ready, a couple of small nits:

1) Shouldn't the Security Considerations come before the references?
2) For the references, there is text that says the following:

        ************************************************************
        * NOTES TO RFC Editor (to be removed prior to publication) *
        *                                                          *
        *     The I-D <draft-ietf-ipcdn-device-mibv2-06.txt> (or a *
        * successor) is expected to eventually replace RFC 2669.   *
        * If that draft (or a successor) is published as an RFC    *
        * prior to or concurrently with this document, then the    *
        * normative reference [RFC2669] should be updated to       *
        * point to the replacement RFC, and the reference tag      *
        * [RFC2669] should be updated to match.                    *
        *                                                          *
        ************************************************************

Shouldn't the I-D just be referenced? Some of these references
seem that they should reference the I-D, not the RFC.