Re: [STDS-802-16] update of P802.16f/D3 Sponsor Ballot comment database
Entry 332 in ieee802.org/16/docs/05/80216-05_022r2.zip database was
truncated:
The following is the original comment and suggested remedy:
===== comment =====
The WMAN-IF-MIB is defined under the "transmission" arc, as is typical for
managed objects that must be indexed by ifIndex. But this MIB contains a
large number of elements that are not interface-specific.
Consider these management objects that are device attributes and are not
tied to an interface:
The "wmanIfBsSnmpAgentConfigTable" (p.154) is a table with a fixed number of
rows (1).
WmanIfBsSnmpAgentConfigEntry ::= SEQUENCE {
wmanIfBsSnmpAgentConfigIndex INTEGER,
wmanIfBsSnmpAgentV1V2TrapDestIpAddrType InetAddressType,
wmanIfBsSnmpAgentV1V2TrapDestIpAddr InetAddress,
wmanIfBsSnmpAgentV1V2TrapDestPort Integer32,
wmanIfBsSnmpAgentResetBs INTEGER,
wmanIfBsSnmpAgentConfigRowStatus RowStatus}
The "wmanIfSsConfigFileEncodingTable" (p. 156) is a table with a fixed
number of rows (1).
WmanIfSsConfigFileEncodingEntry ::= SEQUENCE {
wmanIfSsMicConfigSetting OCTET STRING,
wmanIfSsVendorId OCTET STRING,
wmanIfSsHwId OCTET STRING,
wmanIfSsSwVersion OCTET STRING,
wmanIfSsUpgradeFileName OCTET STRING,
wmanIfSsSwUpgradeTftpServer InetAddress,
wmanIfSsTftpServerTimeStamp DateAndTime}
Similarly, trap bits defined for "wmanIfBsTrapControlRegister" (p.108)
include
wmanIfBsPowerStatusChange
wmanIfBsFanStatusChange
wmanIfBsTemperatureChange
wmanIfBsEvent
It is hard to understand why "wmanIfBsFanStatusChange" is in an IF-MIB.
===== suggested_remedy =====
Remove these management objects from the wmanIf arc (this MIB).
Move these management objects to the arc already defined for ieee802
devices.
Namely iso(1).std(0).iso8802(8802).
Consider iso(1).std(0).iso8802(8802).wman(16).wmanDev(1) ...
See section 13.2 of the 802b-2004 standard.
More examples of how this is used are discussed in section 2.9 of:
[ grouper.ieee.org/groups/802/802_tutorials/chair_guidelines_1-6.pdf ]
Or [ ieee802.org/secmail/pdf00157.pdf ]
It is inappropriate for the interface MIB to contain elements
that are not specific to the RF interface we're describing.
There are numerous needs which need to be incorporated into a
WMAN-DEV-MIB".
***** eor *****
Examples I found with a quick google search:
iso(1).std(0).iso8802(8802).ieee802dot1(1).ieee802dot1mibs(1).
iso(1).std(0).iso8802(8802).csma(3).hubmgt(18).
iso(1).std(0).iso8802(8802).csma(3).mauMgt(20).
--
Mike Geipel
Axxcelera Broadband Wireless