E N D
MIB for 802.19.1 Authors: Date:2012-01-18 Notice:This document has been prepared to assist IEEE 802.19. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Mika Kasslin, Nokia
Abstract This contribution is intended to open discussions in the TG1 on reasons, use and benefits of a management information base (MIB) specification as part of the 802.19.1 specification Mika Kasslin, Nokia
Basics • A MIB is a virtual database that is typically defined to be used for managing entities • Entities in a communication networks have typically MIB for e.g. local/remote management purposes • In the IEEE 802 standards the MIB is specified in a normative annex • Typically ASN.1 is used to specify the MIB Mika Kasslin, Nokia
MIB and 802.19.1 • We most likely would need to have separate ones for CE, CM and CDIS • All in one annex but one for each • The MIB doesn’t necessarily mean that an entity implementation must support management e.g. with SNMP • The MIB may be seen also as a standard development tool to develop a well structured and comprise specification Mika Kasslin, Nokia
Closing remarks • We believe a MIB would be beneficial for the 802.19.1 specification • The 802.19.1 MIB should deal with the entities like CE, CM and CDIS separately • The TG1 should be able to proceed to the WG LB with a draft even without a MIB that can be added to the draft during the LB process • The MIB is not like the PICS that we absolutely must have in our specification and without which we should not go to the LB Mika Kasslin, Nokia