IEEE 1326.2-1993

This standard defines requirements for test methods for measuring conformance to IEEE Std 1224.2-1993 {14}. IEEE Std 1224.2-1993 {14} is stated in terms that are independent of any particular programming language, but each implementation that conforms to it implements a particular programming language binding, and conforms to its programming language binding specification. Each set of test methods for measuring conformance to IEEE Std 1224.2-1993 {14} assumes a particular programming language binding specification. Each programming language binding specification may impose further, programming language specific, requirements on the test methods that, in conjunction with the requirements imposed by this standard, constitute the requirements that shall be satisfied by test methods used for measuring conformance to that programming language binding specification. This standard applies to all sets of test methods for measuring conformance to any programming language binding specification for IEEE Std 1224.2-1993 {14}.

The purpose of this standard is to define test methods for the language-independent specification contained in IEEE Std 1224.2-1993 of the application programming interface (API) to directory services. A directory is a distributed collection of information that programs can access in order to make queries or updates. IEEE Std 1224.2-1993 defines, in programming language-independent terms, an API to directory services. This API is known as the Directory Services API (DS API). The DS API is intended to be used to provide access to a range of directory services that are instances of a common abstract model. That model is defined in the CCITT X.500 Series recommendations and in ISO/IEC 9594:1990. IEEE Std 1224.2-1993 prescribes how the DS API is to be used to access the particular directory service defined in ISO/IEC 9594:1990 and indicates how it may be used to access other directory services that conform to the same abstract model. Nothing in IEEE Std 1224.2-1993 or in this standard requires that the implementation of the interface or the Directory itself actually make use of the Directory Access Protocol (DAP), the Directory System Protocol (DSP) or other parts of the model, just so long as it provides the defined service. The interface is designed for operational interactions with a directory, rather than for management interactions such as knowledge management or schema management. Also, security features are not generally visible in the interface, in order to permit flexibility in security policies. It is intended that an application program should be able to use the interface to access a single directory service or to access several directory services at the same time.

New IEEE Standard - Inactive-Withdrawn. Withdrawn Standard. Withdrawn Date: Mar 06, 2000. No longer endorsed by the IEEE. Test methods for IEEE Std 1224.2-1993, language-independent specification of the applications interface to directory services are defined.