This shows the Control Channel/Connectivity Verification mechanism that the remote peer has advertised as configured on its end of this pseudowire, as learned via LDP signaling rather than locally configured on this router. If the local and remote CC/CV settings don't share any common supported mechanism, VCCV-based OAM (ping/traceroute over the PW) simply won't function even though the pseudowire's data path itself may be perfectly healthy. An admin unable to run VCCV connectivity checks on a PW that otherwise appears up should compare this remote value against the local CC/CV setting to check for a capability mismatch.