DHCPv6 messages processed by the node are rate-controlled toward the CPU. A Self-Generated Traffic (SGT) QoS configuration is not supported for DHCPv6 messages. However, in most scenarios the incoming packet markings is used to determine the ingress FC and color (if applicable) and the FC is used for forwarding it out of the appropriate queue on the egress with the appropriate packet header markings (depending on the egress object that packet is forwarded out of - dot1p, IP DSCP, and MPLS EXP field in the packet is updated).
On the 7210 SAS-Mxp, when SAP egress queues are enabled, CPU-generated and forwarded packets are sent out using default port queues.