||May 2016 Interim
||secyCipherSuiteProtectionOffset has been deprecated in P802.1AEcg D1.1 (passed WG ballot, no further comment on this issue at WG ballot), so there is no longer a possibility of protection offset setting conflict between the SecY MIB (in .1AE) and the .1X MIB so far as current objects are concerned.
Note: It is not possible to simply change an existing object, or to remove it from the MIB. Deprecation is the appropriate step. Note further: The confidentiality offset was introduced in .1AE-2006 to facilitate early deployment, and the XPN Cipher Suites (.1AEbw-2013) do not support Confidentiality Offset.