Draft:  draft-ietf-rmonmib-raqmon-pdu-12.txt
Reviewer: Joel M. Halpern [joel@stevecrocker.com]
Review Date: Saturday 2/4/2006 6:56 PM
IETF LC Date: 2/13/2006

Summary: This document is ready for publication as a Proposed Standard.
The few minor items should be considered if there is a need to revise 
the document.

Minor: In describing the T bits, it says "A value of zero is 
considered to be valid..."  If I am reading this right, a value of 0 
would be common, since many times there is no application specific 
information to add to the basic information.  If it was intended that 
this count include the basic application information, then "that 
trail the BASIC Part" would need to become "including the BASIC 
part."  (And if it does not include the basic part, can we change 
"trail" to "follow"?)

Minor: The Packet Discard in Fraction field occurs in the packet 
before the Packet Loss in Fraction field.  But discard is bit 31 and 
loss is bit 30 in the bits.  And the field descriptions after the bit 
table are in yet a different order.  Is there a need for this variation?

Minor: The WG probably considered it obvious, but I think there ought 
to be a short section that says roughly ~to use TCP to transport 
RAQMON PDUs, it is sufficient to send the PDUs as the TCP data.  As 
each PDU carries its length, the receiver can determine the PDU boundaries."

Nit: "...both functional parts trail a field carrying ..."  I am sure 
that there is a better word than "trail".  Contain?