Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
I would take a bit of an exception to that "best practice" statement. Prioritization is often done for a set of a CS and/or it's AFs, e.g. CS3, AF31, AF32, AF33 (which BTW, all "map" into IPPrec 3), although additional management (usually drop management) may take advantage of the various AF settings.
Within a policy you might have every DSCP value treated differently, or you might mix multiple DSCP values and/or IPPrec values. You might also have the same DSCP values treated differently (dependent on other match criteria).
How traffic is treated, depends on both your service needs and the capability of the equipment.
