DOCSIS config file-General Packet Classifier Encodings
1: Classifier Reference
The value of the field specifies a reference for the Classifier. This value is unique per Dynamic Service message,
configuration file, or Registration Request message.
Type Length Value
[22/23/60].1 1 1 - 255
The CM MUST use the Classifier Reference as the Classifier ID when implementing the Upstream Drop Classifiers
provided in the configuration file because the CMTS does not provide a Classifier ID in the REG-RSP-MP
message.
2: Service Flow Reference
The value of the field specifies a Service Flow Reference that identifies the corresponding Service Flow.
In all Packet Classifier TLVs that occur in any message where the Service Flow ID is not known (e.g., CM-initiated
DSA-REQ and REG-REQ/REG-REQ-MP) this TLV MUST be included. In all Packet Classifier TLVs that occur in
a DSC-REQ and CMTS-initiated DSA-REQ messages the Service Flow Reference MUST NOT be specified.
Type Length Value
[22/23].3 2 1 - 65535
3: Rule Priority
The value of this field specifies the priority for the Classifier, which is used for determining the classification order.
A higher value indicates higher priority.
Classifiers that appear in Configuration files and Registration messages can have priorities in the range 0 – 255. If
no Rule Priority is specified in the Registration Request, the CMTS MUST use the default Rule Priority of 0. If no
Rule Priority is specified in the Registration Response, the CM MUST use the default Rule Priority of 0. Classifiers
that appear in the DSA/DSC message MUST have priorities in the range 64-191, with the default value 64.
The Rule Priority of the Upstream QoS Classifier and the Rule Priority of the Upstream Drop Classifier interact. If a
packet matches both an Upstream QoS Classifier and an Upstream Drop Classifier, the CM MUST select the
Classifier with the higher Rule Priority.
Type Length Value
[22/23/60].5 1
4: Classifier Activation State
The value of this field specifies whether this classifier should become active in selecting packets for the Service
Flow. An inactive Classifier is typically used with an AdmittedQoSParameterSet to ensure resources are available
for later activation. The actual activation of the classifier depends both on this attribute and on the state of its service
flow. If the service flow is not active then the classifier is not used, regardless of the setting of this attribute.
Type Length Value
[22/23].6 1 0 — Inactive
1 — Active
5: CM Interface Mask (CMIM) Encoding
In addition to classifying traffic based on L2/L3/L4 fields in the packet headers, upstream traffic can be classified
based on which CM interface received the packet. The CM Interface Mask Encoding provides a bit mask
representing the in-bound interfaces of the CM for which this classifier applies. Each bit of the CM Interface Mask
corresponds to an interface, logical or physical. By convention, bit position 0 corresponds to the CM’s IP stack,
even though it is not an actual interface.
For example, a CMIM classifier intended to match all of the CPE ports (i.e., external interfaces) of a CM has a
CMIM value setting bits 1 and 5-15, i.e., an encoding of either 0x47FF or 0x47FF0000. Either value is valid.
SubType Length Value
[22/60].13 N BITS -Encoded bit map with bit position K representing CM interface index value K. Bit
position 0 is the most significant bit of the most significant octet. Refer to [DOCSIS
eDOCSIS] for latest logical interface index assignments for eCMs.
Bit 0 (0x80): CM’s IP stack
Bit 1 (0x40): primary CPE Interface (also ePS or eRouter)
Bit 2 (0x20) RF interface
Bits 3,4 reserved
Bits 5..15 (0x07 FF) Other CPE Ports
Bits 16-31, embedded logical interfaces. Currently defined interfaces include:
Bit 16 (0x00 00 80) PacketCable-eMTA
Bit 17 (0x00 00 40) eSTB-IP
Bit 18 (0x00 00 20) reserved
Bits 19..31 (0x00 00 1F FF) Other eSAFE interfaces