DESCRIPTION document 11-09/533 provides guidelines for general MIB attribute – definition, including a discussion of the information that should be included. This document provides more specific guidelines specifically for TruthValue attribute patterns listed here. Each usage pattern also includes guidelines for using and referencing the MIB attribute elsewhere in the Standard. For the purposes of this document, the term applies to any identifiable unique feature of the “feature” Standard that be independently present or absent in a particular implementation, or a similar set of behaviors which might be operational as a group, or none of them are. Patterns Static implementation capability (“Pattern A”) A static implementation pattern is for a feature that is an inherent capability of a implementation. As an capability, this pattern is for features that are permanently operational in an instantiation of “inherent” an implementation that supports it that is, it is not enabled or disabled dynamically during the lifetime of – an instance of the implementation. are two forms of this pattern: internal use only, and externally accessible, as described below Internal use only This form of the static implementation pattern is for a feature that is an inherent capability of a given implementation, and which is not expected to be queried by an external entity. The purpose of such an attribute is really only internal to the 802.11 Standard; defining such an attribute makes it clear that the indication of this support is in fact only useful to the internal 802.11 entities, and in effect becomes just a shorthand formalism (and makes for easier searching, etc.) for that implement XXX” for use “devices elsewhere in the Standard. External access provided The intent of this form of the static implementation pattern is for a feature that is an inherent capability of a given implementation, and where it would be useful for this attribute to be queried (for support in the implementation) by an external entity. Such an attribute can be used within the Standard to control protocol or behaviors which are optional dependent on whether the implementation supports the feature, as well as to inform external management systems of support for the feature thus allowing such systems to manage aspects of the feature, or make other dynamic decisions within the management of the overall deployment. Form of definition and use Both forms of this pattern have similar definition, only the setting for MAX-ACCESS differs, and the use in the Standard is also similar. Name: dot11<XXX>Implemented MAX-ACCESS: none - access to external entity not allowed OR MAX-ACCESS: read-only - access to external entity allowed
DESCRIPTION – document 11-09/533 provides guidelines for general MIB attribute definition, including a discussion of the information that should be included. This document provides more specific guidelines specifically for TruthValue attribute patterns listed here. Each usage pattern also includes guidelines for using and referencing the MIB attribute elsewhere in the Standard. For the purposes of this document, the term “feature” applies to any identifiable unique feature of the Standard that be independently present or absent in a particular implementation, or a similar set of behaviors which might be operational as a group, or none of them are. Patterns Static implementation capability (“Pattern A”) A static implementation pattern is for a feature that is an inherent capability of a implementation. As an “inherent” capability, this pattern is for features that are permanently operational in an instantiation of an implementation that supports it – that is, it is not enabled or disabled dynamically during the lifetime of an instance of the implementation. are two forms of this pattern: internal use only, and externally accessible, as described below Internal use only This form of the static implementation pattern is for a feature that is an inherent capability of a given implementation, and which is not expected to be queried by an external entity. The purpose of such an attribute is really only internal to the 802.11 Standard; defining such an attribute makes it clear that the indication of this support is in fact only useful to the internal 802.11 entities, and in effect becomes just a shorthand formalism (and makes for easier searching, etc.) for “devices that implement XXX” for use elsewhere in the Standard. External access provided The intent of this form of the static implementation pattern is for a feature that is an inherent capability of a given implementation, and where it would be useful for this attribute to be queried (for support in the implementation) by an external entity. Such an attribute can be used within the Standard to control protocol or behaviors which are optional dependent on whether the implementation supports the feature, as well as to inform external management systems of support for the feature thus allowing such systems to manage aspects of the feature, or make other dynamic decisions within the management of the overall deployment. Form of definition and use Both forms of this pattern have similar definition, only the setting for MAX-ACCESS differs, and the use in the Standard is also similar. Name: dot11<XXX>Implemented MAX-ACCESS: none - access to external entity not allowed OR MAX-ACCESS: read-only - access to external entity allowed
11-15-0355-09-0arc-mib-truthvalue-usage-patterns.docx