Definitions of Managed Objects for IP Flow Information Export
RFC 6615

Note: This ballot was opened for revision 01 and is now closed.

(Dan Romascanu) Yes

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Ralph Droms) No Objection

(Wesley Eddy) No Objection

(Adrian Farrel) No Objection

Comment (2012-03-15 for -02)
This looks like a pretty solid MIB module and I have no objection to
its publication.

I do, however, see a few small points you might want to look at.


I think the copyright statement in the main Descirption clause should
be updated to the current year.


Revision history Description clause.

The plural of erratum is errata.


I may be mistaken, but I thought there was a recommendation on the 
maximum length of object names that capped them at 32 characters.
There are several really long names in this module: the lnngest I found
was the 50 character ipfixTransportSessionOptionsTemplateRefreshTimeout


I would need to check, but I am pretty sure there is an IANA TC for
protocol numbers as used in ipfixTransportSessionProtocol, but if not
I think the pointer to could be improved.


Unless you intend to support all address types defined by the TC
InetAddressType, I think the conformance clauses of all objects with
this Syntax need to limit the support, and the description clauses for
the objects should state what is and is not supported.

(Stephen Farrell) No Objection

(Russ Housley) (was Discuss) No Objection

(Pete Resnick) No Objection

Comment (2012-03-11 for -01)
This document appears to Obsolete RFC 5815, but that is not indicated anywhere in the document, nor in the header.

This appears to be simply errata fixes from 5815. Is there a reason it is recycling at Proposed rather than advancing to Internet Standard?

(Peter Saint-Andre) No Objection

(Robert Sparks) No Objection

(Sean Turner) No Objection

Comment (2012-03-12 for -02)
s1: Not sure you need the MUST/MAY in the following because they're not telling me much:

 Most of the objects defined by the IPFIX MIB module MUST
 be implemented.  Some objects MAY be implemented corresponding to the
 functionality implemented in the equipment.