This read-create INTEGER serves double duty: for a cascade-type policer it points to the next policer in the chain, with 0 meaning none, and for an explicit-remark action it instead holds the actual remark value to apply. An admin configures this field differently depending on the chosen policer type or action, pointing to a downstream policer when cascading rate limits, or supplying a specific DSCP or CoS remark value when the action is explicit remarking. For example, an admin building a two-tier rate-limiting cascade would set this field on the first policer to point at the index of a second policer that further restricts any traffic passing the first stage.