Interpretation request - IEEE Std 802.1AE-2006 In the MIB module text of this standard, the data type secyCipherSuiteProtectionOffset is defined on page 100 as of type INTEGER and in the OBCT-TYPE macro it has a SYNTAX of Integer32. This will cause compilation errors when the MIB module is processed by the standard tools. I believe that the appropriate fix for this would be to change the definition of this data type on page 100 from INTEGER to Integer32.
The following response was approved by 802.1 at its November 2006 meeting.
The 802.1 Working Group agrees that the proposal made in the interpretation request, namely that the appropriate solution is to change the definition of the secyCipherSuiteProtectionOffset data type on page 100 of the standard from INTEGER to Integer32, is correct. A corrected version of the MIB text, with this change made, has been posted on the 802.1 website at: http://www.ieee802.org/1/files/public/MIBs/802-1ae-2006-mib-corrected.txt.
Pages copyright © Institute of Electrical and Electronics Engineers, Inc. Please read the rules on Confidentiality Statements and Copyright Notices on Communications. Information on Privacy and opting out of cookies is available. If you have any comments on these pages, please send them to me.