This records the 802.1p PCP value the latency results in this row apply to, letting an admin match measured latency figures to the specific CoS queue tested, since carrier SLAs for latency are almost always defined per traffic class. An admin needs this because a latency figure meaningful for best-effort traffic (PCP 0) would be an unacceptable violation if it actually belonged to the voice queue (PCP 5). For example, cienaCesBenchmarkGenTestSessionLatencyResultsPcp = 5 tags a latency result row for review against a tight sub-millisecond SLA reserved for voice-class traffic.