Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
IEEE<br />
Std 802.<strong>11</strong>a-1999 SUPPLEMENT TO IEEE STANDARD FOR INFORMATION TECHNOLOGY—<br />
SYNTAX INTEGER (0..99)<br />
MAX-ACCESS read-write<br />
STATUS current<br />
DESCRIPTION<br />
“The number of the current operating frequency channel of the OFDM PHY.”<br />
::= {dot<strong>11</strong>PhyOFDMEntry 1}<br />
dot<strong>11</strong>TIThreshold<br />
SYNTAX INTEGER32<br />
MAX-ACCESS read-write<br />
STATUS current<br />
DESCRIPTION<br />
“The Threshold being used to detect a busy medium (frequency).<br />
CCA shall report a busy medium upon detecting the RSSI above this threshold.”<br />
::= {dot<strong>11</strong>PhyOFDMEntry 2}<br />
dot<strong>11</strong>FrequencyBandsSupported<br />
SYNTAX INTEGER (1..7)<br />
MAX-ACCESS read-only<br />
STATUS current<br />
DESCRIPTION<br />
“The capability of the OFDM PHY implementation to operate in the three U-NII<br />
bands. Coded as an integer value of a three bit field as follows:<br />
bit 0 .. capable of operating in the lower (5.15-5.25 GHz) U-NII band<br />
bit 1 .. capable of operating in the middle (5.25-5.35 GHz) U-NII band<br />
bit 2 .. capable of operating in the upper (5.725-5.825 GHz) U-NII band<br />
For example, for an implementation capable of operating in the lower and mid<br />
bands this attribute would take the value 3.”<br />
::= {dot<strong>11</strong>PhyOFDMEntry 3}<br />
--**********************************************************************<br />
-- * End of dot<strong>11</strong>PhyOFDM TABLE<br />
--<br />
**********************************************************************<br />
4. In Annex D, update “compliance statements” section as the following text:<br />
**********************************************************************<br />
-- * compliance statements<br />
--<br />
**********************************************************************<br />
dot<strong>11</strong>Compliance MODULE-COMPLIANCE<br />
STATUS current<br />
DESCRIPTION<br />
“The compliance statement for SNMPv2 entities<br />
that implement the IEEE 802.<strong>11</strong> MIB.”<br />
MODULE -- this module<br />
MANDATORY-GROUPS {<br />
dot<strong>11</strong>SMTbase,<br />
dot<strong>11</strong>MACbase, dot<strong>11</strong>CountersGroup,<br />
dot<strong>11</strong>SmtAuthenticationAlgorithms,<br />
dot<strong>11</strong>ResourceTypeID, dot<strong>11</strong>PhyOperationComplianceGroup}<br />
GROUP dot<strong>11</strong>PhyDSSSComplianceGroup<br />
DESCRIPTION<br />
“Implementation of this group is required when object<br />
dot<strong>11</strong>PHYType has the value of dsss. This group is<br />
mutually exclusive with the groups dot<strong>11</strong>PhyIRComplianceGroup,<br />
dot<strong>11</strong>PhyFHSSComplianceGroup and dot<strong>11</strong>PhyOFDMComplianceGroup.”<br />
GROUP dot<strong>11</strong>PhyIRComplianceGroup<br />
DESCRIPTION<br />
“Implementation of this group is required when object<br />
52 Copyright © 1999 IEEE. All rights reserved.
Change language