DOCS-QOS-MIB

1
DOCS-QOS-MIB

• Version 7 (February 1, 2003)
• Authors
• Michael Patrick
• William Murwin

2
DOCS-QOS-MIB version 4

• tCOM and Cable Labs require DOCS-QOS-MIB version
  4 for Certification Wave Testing.
• All DOCSIS 1.1 certified CMs and CMTSs currently
  implement DOCS-QOS-MIB version 4.

3
DOCS-QOS-MIB version 5

• The description of docsQosServiceFlowPkts was
  changed to avoid requiring CMs to classify
  downstream packets. However the new description
  gave the impression that this counter now counted
  delayed, dropped, and transmitted packets.

4
DOCS-QOS-MIB version 6

• InetAddress objects added in favor of IpAddress
  syntax for IPv6.
• Deprecated objects of type IpAddress for
  backwards compatibility with DOC-QOS-MIB version
  4.

5
DOCS-QOS-MIB version 6 cont.

• Added objects that were removed from earlier
  revisions of the MIB, as obsolete objects. This
  was done to explain the gaps in the numbering of
  objects, to prevent re-use in future versions of
  the MIB.

6
DOCS-QOS-MIB version 7

• Re-Root the MIB
• Why?
• There was a compilation error introduced from
  version 2, that was best fixed by re-rooting the
  DOCS-QOS-MIB.
• (2)The MIB doctor is recommending this for a
  number of the DOCSIS MIBs.
• Benefits -
• Removed obsolete deprecated objects.
• Renumbering of objects.
• Removed objects were only needed for backwards
  compatibility.

7
DOCS-QOS-MIB version 7 cont.

• 2. 64-bit packet counters
• Due to the large amounts of traffic passed on the
  CMTS, a larger range was need than the 32-bit
  counters from past revisions of this MIB.

8
DOCS-QOS-MIB version 7 cont.

• 3. ECN OSS-N-02214
• ECN RFI-N-02091 changed the default values for
  the Maximum Traffic Burst and the Maximum
  Concatenated Burst parameters. The DOCS-QOS-MIB
  was changed to reflect the changes in the DOCSIS
  Specification.

9
DOCS-QOS-MIB version 7 cont.

• 4. Clarify the packet counters descriptions
• Caused by changes introduced in DOC-QOS-MIB
  version 5.
• Caused confusion for both testers and
  implementers.

10
docsQosServiceFlowPkts

• 64-bit counter of the number of Packet Data PDUs
  classified to this service flow and forwarded
  beyond a service flow maximum rate policing
  function.
• CMs not classifing downstream data report 0.
• Does NOT count MAC-specific management messages.
• Counts Delayed packets
• Does NOT count Drop due policing. I.E.
  docQosServiceFlowDropPkts
• Particularly for UGS flows, packets sent on the
  primary service flow in violation of the UGS
  grant size should be counted only on the primary
  service flow's counters.

11
docsQosServiceFlowDropPkts

• 32-bit counter of the number of Packet Data PDUs
  classified to this service flow and dropped due
  to a Maximum Rate Policing Function.
• Also counts UGS packets dropped due to exceeding
  the Unsolicited Grant Size with a
• Request/Transmission policy that requires such
  packets to be dropped.
• Any other reason a classified packet is dropped
  MUST BE counted in ifOutDiscards and not
  docsQosServiceFlowDropPkts.