tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Glossaries     Architecture     IMS     UICC    |    search

RFC 2116

 
 
 

X.500 Implementations Catalog-96

Part 5 of 5, p. 130 to 164
Prev RFC Part

 


prevText      Top      Up      ToC       Page 130 
NAME

   OSIAM X.500-88

   MARBEN

ABSTRACT

   OSIAM X.500-88 is Marben's 1988 compliant directory product. It
   provides:

      * DUA, offering X/Open XOM and XDS APIs

      * Pocket DUA, providing Microsoft MAPI(tm)

      * DSA and C-ISAM based DIB

      * LDAP Server

   OSIAM DUA is a portable Directory User Agent implement, which
   implements DAP engine. It provides X/Open XOM and XDS APIs. It works
   on multiple lower layer stacks (OSI Transport or TCP/IP). An LDAP
   Server may be provided with the DUA.

   Pocket DUA is a light DUA implement which offers full DAP access, but
   light in terms of code size and memory occupation, and is mainly
   designed for PC environments. It provides MAPI(tm) interface, as an
   address book provider. It provides multiple network connectivities:
   X.25, [RFC 1006] over TCP/IP, and APS.

   OSIAM X.500 DSA provides full X.500 1988 functionality. Main features
   include: chaining/multicasting, extensible schema, proprietary access
   control list, comprehensive administration facilities.

   MARBEN is currently developing a new generation of directory product,
   providing X.500 1993 functionality. Main targets are:

      * high performance

      * robustness and administration facility with DIB on commercial
        RDBMS

      * replication

      * access control

      * extended information models

Top      Up      ToC       Page 131 
   Please contact MARBEN for more information on '93 product.

COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs)

   OSIAM X.500-88 DUA and DSA implement CCITT X.500 (1988) an ISO 9594
   standards.

   Compliant with EWOS and NIST OIW Stable Implementor's Agreement.

COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)

   1993 product is under development.

   Please contact MARBEN for more information on '93 product.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   Compliant with the following Internet Standards:

      * [RFC 1274]: the COSINE and Internet X.500 Schema (partially
        supported)

      * [RFC 1277]: encoding of network addresses

      * [RFC 1778], [RFC 1777], [RFC 1779]: LDAP and related
        standards

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   None is supported at the present time.

INTEROPERABILITY

   Have successfully interoperated, both on DAP and DSP, with QUIPU, E3X
   and other implementations involved in Paradise pilot project.

PILOT CONNECTIVITY

   Connected to Paradise pilot project.

BUGS

   [No Information Provided--Ed.]

CAVEATS AND GENERAL LIMITATIONS

   [No Information Provided--Ed.]

Top      Up      ToC       Page 132 
INTERNETWORKING ENVIRONMENT

   [RFC 1006] with TCP/IP, TP0 with X.25, TP4 with CLNS

HARDWARE PLATFORMS

   OSIAM X.500-88 is highly portable, and has been ported to a wide
   range of platforms, including:

      * HP9000 series

      * SUN SPARC Stations

      * SCO UNIX

      * Tandem

      * MARK III, etc.

   MARBEN Pocket DUA runs on PC/Windows and NT.

SOFTWARE PLATFORMS

   See HARDWARE PLATFORMS.

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   Commercially available from:

      MARBEN
      11 Rue Curie
      92150 Suresnes, France

      Contact Person: Karim Jammal or Shaofeng Li
      Phone: (33 - 1) 41 38 10 00
      Fax:   (33 - 1) 41 38 10 01
      X.400: C=FR;A=Atlas;P=Marben;O=Suresnes;OU1=MxMs;S=KJammal
      E-Mail:sli@wtk.suresnes.marben.fr

Top      Up      ToC       Page 133 
   Also available from:

      MARBEN Products Inc.
      2105 Hamilton Avenue, Suite 320
      San Jose, CA95125, USA

      Contact Person: Jean-Francois Chapuis
      Phone: (408) 879 4000
      Fax:   (408) 879 4001
      E-Mail: jfchapuis@marben.com

DATE LAST UPDATED or CHECKED

   October 1995

ADDITIONAL INFORMATION and/or COMMENTS

   [No Information Provided--Ed.]

Top      Up      ToC       Page 134 
NAME

   OSIAM X.500-93

   MARBEN

ABSTRACT

   OSIAM X.500-93 is Marben's 1993 compliant directory product.

   Open Directory

      * OSIAM X.500-93 provides both DAP and LDAP access

      * Support for distribution using the DSP protocol

      * Support for replication using the DISP protocol

      * Pocket DUA, providing Microsoft MAPI0(tm) and MAPI1(tm)
        interface to MS-Mail(tm) or Exchange(tm)

      * WEB gateway to access Directory information from WEB browsers

      * X/Open XOM/XDS API

      * High performance direct API

   High Capacity

      * Mapped on a RDBMS

      * Over 1.000.000 entries

      * Use of transaction, to ensure robustness

      * Can run on high-available hardware systems

      * Isolated interface, to be customized for various RDBMS

   High Performance

      * Use of cache at DUA level

      * Use of cache at DSA level

Top      Up      ToC       Page 135 
      * Use of replication. Can act as shadow supplier, shadow
        consumer or secondary shadow supplier. Support for total or
        incremental refresh. Support for both scheduled update and
        "on change" update.

      * Based on an indexed database, to ensure high-performance
        elaborated search.

   Security

      * Anonymous bind, simple and simple protected authentication

      * X.509 certificates storage

      * Access control

   Ease of administration

      * Extensible schema

      * Backup-recovery

      * Event logging

      * Statistics information about Directory use

      * Billing dockets generation

   Ease of integration

      * Provided as binary product or as portable source code

      * MARBEN services: training, consulting, system integration,
        hot-line support, maintenance.

COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs)

   OSIAM X.500-93 DUA and DSA implement CCITT X.500 (1988) and ISO 9594
   standards.

   Compliant with EWOS and NIST OIW Stable Implementor's Agreement.

COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)

   OSIAM X.500-93 DUA and DSA implement CCITT X.500 (1993) and ISO 9594
   standards.

Top      Up      ToC       Page 136 
CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   Compliant with the following Internet Standards:

      * [RFC 1274]: the COSINE and Internet X.500 Schema (partially
        supported)

      * [RFC 1277]: encoding of network addresses

      * [RFC 1778], [RFC 1777], [RFC 1779]: LDAP and related
        standards

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   None is supported at the present time.

INTEROPERABILITY

   Have successfully interoperated, both on DAP and DSP, with QUIPU, E3X
   and other implementations involved in Paradise pilot project.

PILOT CONNECTIVITY

   Connected to Paradise pilot project.

BUGS

   [No Information Provided--Ed.]

CAVEATS AND GENERAL LIMITATIONS

   [No Information Provided--Ed.]

INTERNETWORKING ENVIRONMENT

   [RFC 1006] with TCP/IP, TP0 with X.25, TP4 with CLNS

HARDWARE PLATFORMS

   OSIAM X.500-93 is highly portable, and has been ported to a wide
   range of platforms, including:

      * Windows NT

      * HP-UX

      * IBM AIX

Top      Up      ToC       Page 137 
      * SUN Solaris

      * SCO UNIX

      * IBM MVS

   MARBEN Pocket DUA runs on PC/Windows and NT.

SOFTWARE PLATFORMS

   See HARDWARE PLATFORMS.

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   Commercially available from:

      MARBEN
      11 Rue Curie
      92150 Suresnes, France

      Contact Person: Marc Chauvin or Olivier Gatine
      Phone: (33 - 1) 41   38 10 00
      Fax:   (33 - 1) 41   38 10 01
      E-Mail:sales@suresnes.marben.fr

   Also available from:

      MARBEN Products Inc.
      2105 Hamilton Avenue, Suite 320
      San Jose, CA95125, USA

      Contact Person: Jean-Francois Chapuis
      Phone: (408) 879 4000
      Fax:   (408) 879 4001
      E-Mail: jfchapuis@marben.com

DATE LAST UPDATED or CHECKED

   July 1996

ADDITIONAL INFORMATION and/or COMMENTS

   [No Information Provided--Ed.]

Top      Up      ToC       Page 138 
NAME

   PMDF-X500

   from:

   Innosoft International, Inc. 1050 East Garvey Ave. South West
   Covina, California  91790

   Phone:  +1 818-919-3600 email: sales@innosoft.com

ABSTRACT

   PMDF-X500 is Innosoft's implementation of the X.500 standards for
   Directory Services. PMDF-X500 is based upon the ISODE Consortium
   code-base. The core of PMDF-X500 is the Directory System Agent (DSA)
   server. This server provides directory information to Directory User
   Agents (DUA) using either OSI or TCP/IP networking protocols. Since
   PMDF-X500 is based on a widely used implementation, it interoperates
   particularly well with a whole host of X.500-based products from other
   sources.

   In order to facilitate initial loading of directory data as well as
   ongoing coordination with other directory services, PMDF-X500 includes
   tools to import from and export directory information to Entry
   Description File (EDF) files. EDF files are flat text files.
   PMDF-X500 provides directory coordination functions using EDF files
   for the following directories:

      * X.500 DSAs supporting LDAP access

      * cc:Mail

      * Digital's DDS

      * GroupWise

      * Microsoft Mail

      * PMDF  generic databases

COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs)

   OSI directory services as specified in CCITT X.500 Recommendations
   and ISO 9594 use the Directory Access Protocol (DAP) and the
   Directory System Protocol (DSP).

Top      Up      ToC       Page 139 
COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)

   PMDF-X500 does not yet support the 1993 changes to the X.500
   standard.  Support for the 1993 X.500 recommendations is planned for
   a future release of PMDF-X500.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   PMDF-X500 supports DAP and DSP accesses using Internet protocols as
   specified in [RFC 1006]. In addition, the Internet community has
   proposed two lightweight alternatives to DAP called Lightweight
   Directory Access Protocol (LDAP), which is specified in [RFC 1777],
   and Connectionless Lightweight Directory Access Protocol (CLDAP),
   which is specified in [RFC 1798]. LDAP and CLDAP, which are currently
   specified to run over TCP/IP, are much simpler protocols than DAP and
   were designed to reduce the cost of entry associated with using X.500
   protocols in client applications. PMDF-X500 includes both LDAP and
   CLDAP servers.

   The LDAP server accesses X.500 directory information using DAP to
   communicate with X.500 DSAs. PMDF-X500 provides an LDAP server which
   translates LDAP requests into DAP requests to communicate with X.500
   DSAs. CLDAP defines a very low overhead method for accessing X.500
   directory information. CLDAP is suitable for providing access to
   information that does not require access controls.

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [No information provided. -- Ed.]

INTEROPERABILITY

   PMDF-X500 interoperates with a large number of DUAs and DSAs. This is
   demonstated by the fact that PMDF-X500 is DSA used by several Internet
   White Pages Project participants. PMDF-X500 DSA interoperability
   includes at least all of the DSA that are used in the White Pages
   Project.

   PMDF-X500 is delivered with several DUAs and in addition is know to
   support the DUAs from Unisys and Digital Equipment Corporation as well
   as the publically available DUAs MaX500, Cello, Swix, and the NASA
   DUA.

PILOT CONNECTIVITY

   PMDF-X500 is used by several sites that are participants of the
   Internet White Pages Project include the Innosoft DSA.

Top      Up      ToC       Page 140 
BUGS

   [No information provided. -- Ed.]

CAVEATS AND GENERAL LIMITATIONS

   [No information provided. -- Ed.]

INTERNETWORKING ENVIRONMENT

   DAP and DSP are layered on top of the OSI protocol suite. PMDF-X500
   supports this protocol suite over multiple network transports. For a
   pure OSI protocol stack, DECnet/OSI can be used to provide the lower
   layers of the stack. In addition, PMDF-X500 supports running OSI upper
   layer protocols over a TCP/IP transport in accordance with [RFC 1006].
   It is important to note that while [RFC 1006] specifies TCP/IP as a
   transport, all of the OSI upper layer protocols are always used with
   DAP and DSP.

HARDWARE PLATFORMS

   Digital VAX systems
   Digital Alpha/AXP systems

SOFTWARE PLATFORMS

   OpenVMS/VAX
   OpenVMS/AXP
   Digital UNIX

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

Top      Up      ToC       Page 141 
AVAILABILITY

   PMDF-X500 is a commerical product that is part of the PMDF family of
   eMail Interconnect products.  PMDF-X500 requires the presence of
   PMDF-MTA, Innosoft's SMTP/MIME mailer.  PMDF-X500 and PMDF-MTA can be
   obtained from:


      Innosoft International, Inc.
      1050 East Garvey Ave. South
      West Covina, California  91790

      Phone: +1 818-919-3600
      FAX: +1 818-919-3614
      email:  sales@innosoft.com

DATE LAST UPDATED or CHECKED

   December 1995

ADDITIONAL INFORMATION and/or COMMENTS

   No information provided. -- Ed.]

Top      Up      ToC       Page 142 
NAME

   TransIT 500 Unisys Corporation

ABSTRACT

   TransIT 500 is a commercial-grade implementation of the 1993 X.500
   directory standards (ITU X.500 Directory Services and ISO 9594)
   including replication, extensible schemas and access control.
   TransIT 500 is designed for performance, scalability, conformance and
   interoperability for enterprise-wide usage and is available for
   Microsoft Windows NT, Hewlett Packard HP/UX, Unisys U6000 and as
   portable source code.  TransIT 500 is comprised of the following:

   TransIT 500 Directory Services

   TransIT 500 Directory Services is a high-performance, 1993 standards
   based Directory System Agent (DSA). TransIT 500 includes many
   features required by today's enterprise for global access and
   mission-critical applications:

      * Adheres to the 1993 ITU & ISO 9594 X.500 Directory Services
        standards

      * Full support for Replication (X.525/DISP)

      * Access controls and extensible schemas

      * Support of all X.520 attribute types & syntaxes, all X.521
        object classes & attribute sets

      * Automated loading of directory entries

      * Support for Basic Access Control and Simplified Access
        Control

      * High performance, commercial-grade operations

      * Integration with popular databases such as Microsoft SQL
        Server, Informix, and Oracle

      * Multi-platform availability

      * Authentication services

      * Support of industry standard APIs, including LDAP, DAP, DSP,
        DISP, XDS/DOM and XAP

Top      Up      ToC       Page 143 
      * High-capacity network integration with both TCP/IP (RFC 1006)
        and OSI networks.

   TransIT 500 Administrator

   TransIT 500 Administrator is an extremely powerful tool designed to
   assist administrators in all directory administration, maintenance
   and security functions.  Available for Microsoft Windows NT, Windows
   95 and Windows 3.1.1 based systems, TransIT 500 Graphical
   Administration is the first tool of its kind to provide fully
   graphical X.500 directory management.  All functions are provided and
   multiple DSAs can be managed simultaneously from a single
   administrative console:

      * Directory Service Operations

      * Directory Controls Management

      * Access Control Management

      * Schema Management & Maintenance

      * Directory Information Tree Management

      * Knowledge References & Information

      * Replication Agreements & Information

      * Logging, Tracing and System Logs

      * Directory System Configuration

      * Data Import & Export

      * Directory Backup & Restore Operations

   TransIT 500 Browser

   TransIT Browser is a powerful, graphical information retrieval tool
   designed to make navigating directories as simple as possible.  The
   Browser interface makes detailed directory searches and retrievals
   easy while the unique Directory Lookup interface provides extra
   ease-of-use for simple lookups. TransIT Browser is available for
   Microsoft Windows 3.1, Windows 95 and Windows NT systems.

      * Browse multiple directories from a single console

      * Two interfaces to directories:

Top      Up      ToC       Page 144 
         * Tree-oriented Browser

         * Tabular Directory Lookup

      * Object classes mapped to icons to enhance object recognition

      * Extensive attribute search capabilities

      * Save/Load scratchpad for search criteria & prefix criteria

      * LDAP support

      * Configurable cache to speed data delivery

   TransIT 500 Developer

   TransIT 500 Developer is a development toolkit which provides
   programming interfaces, utilities and documentation for the
   development of directory enabled applications. The Directory
   Information Tree (DIT) can be extended and re-compiled for the
   addition of application-specific information to the directory.  The
   Administration application provides for the verification and
   installation of new schemas and the maintenance of directory tree
   items. Utilities are provided for the bulk importation or exportation
   or directory information from and to external sources.

   TransIT 500 also supports user-written programs using the X/Open
   Directory Services Application Program Interface (XDS API).

COMPLIANCE with X.500- 1988

   The TransIT 500 implementation conforms to the specifications
   outlined in the ISO/IEC 9594-1 to ISO 9594-9, CCITT X.500 standards.

COMPLIANCE with X.500- 1993

   TransIT 500 makes the following claims of conformance as outlined in
   ISO/IEC 9594-5:

   Conformance by DUAs:

      Statement Requirements

         Conformance is claimed for the following operations:

            * DirectoryBind

            * DirectoryUnbind

Top      Up      ToC       Page 145 
            * Read

            * Compare

            * Abandon

            * List

            * Search

            * AddEntry

            * RemoveEntry

            * ModifyEntry

            * ModifyDN

         Conformance is claimed for the following security-levels:

            * None

            * Simple

         Conformance is claimed for the following extensions:

            * subentries

            * copyShallDo

            * extra attributes

            * useAliasOnUpdate

            * newSuperior

      Static Requirements

         The DUA supports the application contexts directoryAccessAC and
         directorySystemAC.

         The DUA conforms to the following extensions for which the DUA
         is capable of initiating:

            * subentries

            * copyShallDo

Top      Up      ToC       Page 146 
            * extra attributes

            * useAliasOnUpdate

            * newSuperior

      Dynamic Requirements

         The DUA conforms to the mapping of the  DAP services (i.e.,
         DirectoryBind,  DirectoryUnBind) onto the used services of the
         ACSE.

         The DUA conforms to the versions and rules of extensibility as
         outlined in clause 7.5.1 of X.519.

   Conformance by  DSAs:

      Statement Requirements

         The DSA supports the application contexts directoryAccessAC and
         directorySystemAC.

         The DSA does not make any claims for operational binding types.

         The DSA is capable of acting as a first-level DSA as defined in
         ITU-T Rec. X.518 ISO/IEC 9594-4.

         The DSA supports the application context directorySystemAC and
         the chained mode of operation.

         Conformance is claimed for the following security-levels:

            * None

            * Simple

         Conformance is claimed for all attribute types defined in ITU-T
         Rec. X.520 ISO/IEC 9594-6.

         Conformance is claimed for all object classes defined in ITU-T
         Rec. X.521 ISO/IEC 9594-7.

         Conformance is  claimed for the following extensions:

            * subentries

            * copyShallDo

Top      Up      ToC       Page 147 
            * extra attributes

            * useAliasOnUpdate

            * newSuperior

         Conformance is not claimed for collective attributes as defined
         in X.501 and X.511.

         Conformance is not claimed for hierarchical attributes as
         defined in X.511.

         Conformance is claimed for the following operational attribute
         types defined in X.501:

            * createTimestamp

            * modifyTimestamp

            * creatorsName

            * modifiersName

            * administrativeRole

            * subtreeSpecification

            * collectiveExclusions

            * accessControlScheme

            * prescriptiveACI

            * entryACI

            * subentryACI

            * dseType

            * myAccessPoint

            * superiorKnowledge

            * specificKnowledge

            * nonSpecificKnowledge

            * supplierKnowledge

Top      Up      ToC       Page 148 
            * consumerKnowledge

            * secondaryShadows

            * dITStructureRules

            * nameForms

            * dITContentRules

            * objectClasses

            * attributeTypes

            * matchingRules

            * matchingRuleUse

         Conformance is claimed for return of alias names as defined in
         7.7.1 of X.511 IS0/IEC 9594-3.

         Conformance is claimed for indicating that returned entry
         information is complete, as described in 7.7.6  of X.511
         ISO/IEC 9594-3.

         Conformance is claimed for modifying the object class attribute
         to add and/or remove values identifiying auxiliary object
         classes, as described in 11.3.2 of  X.511 ISO/IEC 9594-3.

         Conformance is claimed for Basic Access Control.

         Conformance is claimed for Simplified Access Control.

         Conformance is claimed for the DSA s ability to administer the
         subschema for its portion of the DIT, as defined in X.501
         ISO/IEC 9594-2.

         Conformance is claimed for all name bindings defined in X.521
         ISO/IEC 9594-7.

         Conformance is claimed for the DSA s ability to administer
         collective attributes, as defined in X.501 ISO/IEC 9594-2.

      Static requirements

         The DSA supports the application contexts directoryAccessAC and
         directorySystemAC.

Top      Up      ToC       Page 149 
         The DSA conforms to the information framework defined by X.501
         ISO/IEC 9594-2.

         The DSA conforms to the minimal knowledge requirements defined
         in ISO/IEC 959-4.

         The DSA operates as a first-level DSA and conforms to the
         requirements support of the root context as defined in X.518
         ISO/IEC 9594-4.

         The DSA supports the attributes for which conformance is
         claimed above.

         The DSA supports the object classes for which conformance is
         claimed above.

         The DSA conforms to the following extensions for which
         conformance is claimed:

            * subentries

            * copyShallDo

            * extra attributes

            * useAliasOnUpdate

            * newSuperior

         Conformance is claimed for the DSA s ability to administer the
         subschema for its portion of the DIT, as defined in X.501
         ISO/IEC 9594-2.

         Conformance is not claimed for collective attributes, as
         defined in X.501 ISO/IEC 9594-3.

         Conformance is not claimed for hierarchical attributes, as
         defined in X.501 ISO/IEC 9594-3.

         The DSA supports the operational attribute types for which
         conformance is claimed above.

         The DSA supports Basic Access Control and is capable of holding
         ACI items that conform to the definitions of Basic Access
         Control.

Top      Up      ToC       Page 150 
         The DSA supports Simplified Access Control and is capable of
         holding ACI items that conform to the definitions of Simplified
         Access Control.

      Dynamic Requirements

         The DSA conforms to the mapping onto used services as defined
         in clause 8.

         The DSA conforms to the procedures for distributed operations
         of the Directory related to referrals, as defined in X.518
         ISO/IEC 9594-4.

         The DSA supports application-context directoryAccessAC and
         conforms to the procedures of X.518 ISO/IEC 9594-4 as they
         relate to the referral  mode of the DAP.

         The DSA supports application-context directorySystemAC and
         conforms to the referral mode of operation, as  defined in
         X.518 ISO/IEC 9594-4.

         The DSA conforms to the chained mode of interaction as defined
         in X.518 ISO/IEC 9594-4.

         The DSA conforms to rules of extensibility procedures as
         defined in clause 7.5.2 of X.518 ISO/IEC 9594-4.

         The DSA supports Basic Access Control and has the capability to
         protect information within the DSA in accordance with the
         procedures of Basic Access Control.

         The DSA supports Simplified Access Control and has the
         capability to protect information within the DSA in accordance
         with the procedures of Simplified Access Control.

         Conformance is not claimed for shadowOperationalBindingID -- as
         such, conformance is not claimed for the procedures  of X.525
         ISO/IEC 9594-9 and X.501 ISO/IEC 9594-2 as they relate to DOP.

         Conformance is not claimed for specificHierarchicalBindingID --
         as such, conformance is not claimed for the procedures of X.518
         ISO/IEC 9594-9 and X.501 ISO/IEC 9594-2 as they relate to
         operational bindings.

         Conformance is not claimed for non-
         specificHierarchicalBindingID -- as such, conformance is not
         claimed for the procedures of X.518 ISO/IEC 9594-9 and  X.501
         ISO/IEC 9594-2 as they relate to operational bindings.

Top      Up      ToC       Page 151 
   Conformance by a shadow supplier:

      Statement Requirements

         The DSA supports the application contexts
         shadowSupplierInitiatedAC.

         Conformance is claimed for the following security-levels:

                           * None

                           * Simple

         Conformance is claimed for UnitofReplication.

      Static Requirements

         The DSA supports the application contexts
         shadowSupplierInitiatedAC for which conformance is claimed.

         Conformance is claimed for the operational attributes
         modifyTimestamp and createTimestamp.

      Dynamic Requirements

         The DSA conforms to the mapping onto used services as defined
         in clause 8.

         The DSA conforms to the procedures of X.525 ISO/IEC 9594-9 as
         they relate to the DISP.

   Conformance by a shadow consumer:

      Statement Requirements

         The DSA supports the application contexts
         shadowConsumerInitiatedAC.

         Conformance is claimed for the following security-levels:

            * None

            * Simple

      Static Requirements

         The DSA supports the application contexts
         shadowConsumerInitiatedAC for which conformance is claimed.

Top      Up      ToC       Page 152 
         The DSA supports operational attributes modifyTimestamp and
         createTimestamp.

         The DSA supports the copyShallDo service control.

      Dynamic Requirements

         The DSA conforms to the mapping onto used services as defined
         in clause 8.

         The DSA conforms to the procedures of X.525 ISO/IEC 9594-9 as
         they relate to  the DISP.

CONFORMANCE with PROPOSED INTERNET STANDARDS

   TransIT 500 supports the following standards: RFC-1777, RFC-1778,
   RFC-1779.

CONSISTANCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   RFCs supported include: RFC-1558.

INTEROPERABILITY

   Interoperability has been achieved with numerous directory systems.
   TransIT 500 has participated in Eurosinet internetworking
   demonstrations involving DSAs from:

      * AT&T GIS

      * Bolden James

      * Control Data

      * DEC

      * ICL

      * Nex-tel

      * Nexor

      * Siemens Nixdorf

Top      Up      ToC       Page 153 
PILOT CONNECTIVITY

   TransIT 500 is actively involved in pilot projects, including the COS
   X.500 Internetworking Project based at The Southern Company in
   Atlanta, Georgia, where interoperation was performed with directories
   from Digital, Control Data, Hewlett-Packard and Telstra.

BUGS

   TransIT 500 products are fully supported category 1 software, which
   means:

      * These products are periodically updated, revised, and
        enhanced.

      * Unisys provides software corrections for these products as
        necessary.

CAVEATS AND GENERAL LIMITATIONS

   [No information provided. -- Ed.]

INTERNETWORKING ENVIRONMENT

   [No information provided. -- Ed.]

HARDWARE PLATFORMS

   The TransIT 500 software operates on the following hardware
   platforms:

      * Unisys U6000 Series and Clearpath SMP

      * HP 9000 Series

      * 386 and above Intel platforms

SOFTWARE PLATFORMS

   The DSA is supported on any of the following platforms:

      * System V Release 4 (SVR4)

      * HP-UX

      * Windows NT

Top      Up      ToC       Page 154 
   The DUA is supported on any of the following platforms:

      * Windows 95

      * Windows for Workgroups

      * Windows NT

   Additional software required to run TransIT 500 includes Database
   software:

      * SQL Server

      * Informix

      * Oracle

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   TransIT 500 is commercially available through Unisys Corporation.
   For further information, contact the    following:

         Unisys Corporation
         Malvern Building, M.S. B221
         2476 Swedesford Road
         Paoli, PA 19301, USA
         Phone: (800) 874-8647, ext. 584
         Fax: (610) 695-5378
         e-mail:  transit@unisys.com

Top      Up      ToC       Page 155 
NAME

   waX.500

   University of Michigan

ABSTRACT

   waX.500 :: Windows Access to X.500

   waX.500 is a (currently 16-bit) DUA that run on Microsoft Windows
   (3.1, Win95, & WinNT).  It uses libldap.dll which uses the winsock
   (v1.1) interface.  It works on any vendors tcp/ip stack that I've
   seen so far (some configuration may be required).

   waX.500 was developed by the University of Michigan for use by its
   faculty, staff and students. UM's online directory is an X.500
   directory containing 50,000+ entries.

   I keep the following Web page up to date with respect to latest
   release, etc.:
      http://www-personal.umich.edu/~rsug/ldap/wax500/

COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs)

   [No information provided. -- Ed.]

COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)

   [No information provided. -- Ed.]

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [No information provided. -- Ed.]

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [No information provided. -- Ed.]

INTEROPERABILITY

   [No information provided. -- Ed.]

PILOT CONNECTIVITY

   Can see and browse anything in the world as far as I know.

Top      Up      ToC       Page 156 
BUGS

   report bugs to wax500.bugs@umich.edu

CAVEATS AND GENERAL LIMITATIONS

   [No information provided. -- Ed.]

INTERNETWORKING ENVIRONMENT

   Microsoft Windows (3.1, 95, & NT) Winsock (v1.1) tcp/ip (any vendor)

HARDWARE PLATFORMS

   Any Windows machine with internet connectivity.  Both ethernet and
   dialup PPP.

SOFTWARE PLATFORMS

   Microsoft Windows (3.1, 95, & NT) Winsock (v1.1) tcp/ip (any vendor).

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   This implementation is distributed at no cost to the user; accurate
   numbers are not available.

AVAILABILITY

   http://www-personal.umich.edu/~rsug/ldap/wax500
   ftp://terminator.rs.itd.umich.edu/ldap/wax500/wax...

DATE LAST UPDATED or CHECKED

   13 Dec 1995

ADDITIONAL INFORMATION and/or COMMENTS

   [No information provided. -- Ed.]

Top      Up      ToC       Page 157 
NAME

   X500-DS

   X500-DUA

   Bull S.A.

ABSTRACT

   X500-DS and X500-DUA are integral part of the large Bull OSI offer.
   Although based on the DCE/GDS (Distributed Computing
   Environment/Global Directory Service) of OSF, those two products may
   be installed and used without the DCE environment. Some enhancements
   have been added for the user and the management facilities. X500-DS is
   designed to implement both the DUA and the DSA functions, whilst
   X500-DUA only provides the DUA functions.

   The X500-DUA package contains:

      * The standards APIs XOM (X/Open OSI-Abstract-Data Manipulation
        API) and XDS (X/Open Directory Service API) for the
        development of portable applications,

      * A core DUA to translate all user's requests (bind, read,
        list, compare, modify, modifyRDN, search, add, remove, unbind
        ...) into the DAP protocol used for communication with
        distant DSAs,

      * The OSI standard high layers (ASN.1, ROSE, ACSE, Presentation
        and Session) for communication with the distant DSAs. The
        interface with the low layers is XTI. [RFC 1006] is supported
        under XTI or the OSI Session,

      * A DUA Cache to improve performances when accessing remote
        DSAs,

      * A powerful management application facilitating the
        configuration of the product and controlling the operations,
        logs and traces,

      * A user application for the manipulations of the database
        entries,

      * A generic tool to load and unload ASCII and binary files
        in/from distributed DSAs,

Top      Up      ToC       Page 158 
      * The support of the LDAP [RFC 1777] thanks to an LDAP Server,

      * A DUA Server that allows to use A-Window-To-Directory (refer
        to this DUA product description) on a PC.

   The X500-DS package contains:

      * All components of the X500-DUA,

      * A core DSA to process all requests received from distant DUAs
        through DAP protocol or from distant DSAs through DSP
        protocol,

      * The support of the referral, chained and multi-casting modes
        of operation, access control lists and management of
        knowledge information (for distribution, shadows and  copies
        of sub-trees),

      * The support of the simple authentication and of the DCE
        authentication,

      * A management application for managing the schema information
        (creation, deletion and modification of object classes and of
        attribute types, management of the rules of the DIT).

      * A C-ISAM database that is specially designed for high
        performances: e.g. less than 10 ms to read an entry on an
        Escala at the XOM/XDS interface.

   These two products are easely installed, configured and administered
   thanks to the System Management Interface Tool (SMIT) screens of AIX.

COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs)

   Compliant with EWOS and OIW Agreements

   Consists of both DUA and DSA implementation according to the '88
   CCITT X.500 and ISO 9594 standard. The X/Open standard XDS and XOM
   interface libraries are also provided. When the product is installed
   with the DCE environment, XDS and XOM interfaces are also used to
   access DCE/CDS (Local Cell Directory Service) transparently. A GDA
   (Global Directory Agent) serves then as the gateway between the DCE
   CDS and GDS.

COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)

   [New description field -- Ed.]

Top      Up      ToC       Page 159 
CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   Supports [RFC 1277], [RFC 1777].

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [No information provided--Ed.]

INTEROPERABILITY

   This implementation of DAP and DSP can interoperate with other X.500
   implementations from other Cebit and EUROSINET demo participants
   including IBM, HP, ICL, Siemens-Nixdorf, SUN, Marben, NEXOR, etc. It
   also interoperates with ISODE QUIPU.

PILOT CONNECTIVITY

   [No information provided--Ed.]

BUGS

   Bull S.A. provides complete software maintenance with the products.

CAVEATS AND GENERAL LIMITATIONS

   [No information provided--Ed.]

INTERNETWORKING ENVIRONMENT

   OSI TP4 with CLNP (WAN - LAN)

   OSI TP0, 2 & 4 with X.25 (WAN)

   [RFC 1006] with TCP/IP

   Either BSD sockets or XTI can be used to access the transports.

   Through XTI, both OSI and TCP/IP protocols are possible on the same
   machine, thus permitting to build a Directory Service distributed on
   OSI and TCP/IP networks.

HARDWARE PLATFORMS

   DPX/20, Escala SMP

SOFTWARE PLATFORMS

   AIX 4.1.4

Top      Up      ToC       Page 160 
NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   The release 3.1 described here is commercially available since 2 Q 96

      Please contact:

         Daniel Monges
         Tel: + (33)  76 39 79 83
         Fax: + (33)  76 39 77 70
         e-mail: D.Monges@frec.bull.fr

   Note that after October 18th 1996 (23:00), the telephon and fax numbers
      will be:

         Tel: + (33)  04 76 29 79 83
         Fax: + (33)  04 76 29 77 70

DATE LAST UPDATED or CHECKED

   April 1996

ADDITIONAL INFORMATION and/or COMMENTS

   [No information provided. -- Ed.]

Top      Up      ToC       Page 161 
4. References

   [CCITT-88] CCITT, "Data Communications Networks Directory",
   Recommendations X.500-X.521, Volume VIII Fascicle VIII.8, IXth
   Plenary Assembly, Melbourne, November 1988.

   [ITU-T-93] ITU-T,"Information Technology - Open Systems
   Interconnection - The Directory", Recommendations X.500-X.525, May
   1993.

   [NIST-88] National Institute of Standards and Technology, "Stable
   Implementation Agreements for Open Systems Interconnection
   Protocols", Version 2 Edition 1, NIST Special Publication 500-162,
   December 1988.

   [NIST-94] National Institute of Standards and Technology, "Stable
   Implementation Agreements for Open Systems Interconnection
   Protocols", Version ? Edition ?, NIST Special Publication ???-???,
   December 1994.

   [RFC 1006] Rose, M., and Cass, D., "ISO Transport Service on top of
   the TCP", STD 35, RFC 1006, Northrop Research and Technology Center,
   May 1987.

   [RFC 1070] Hagens, R., Hall, N., and Rose, M., "Use of the Internet
   as a Subnetwork for Experimentation with the OSI Network Layer", RFC
   1070, U of Wisconsin    - Madison, The Wollongong Group, February
   1993.

   [RFC 1202] Rose, M., "Directory Assistance Service", RFC 1202,
   Performance Systems International, Inc., February 1991.

   [RFC 1249] Howes, T., Smith, M., and B. Beecher, "DIXIE Protocol
   Specification", RFC 1249, University of Michigan, August 1991.

   [RFC 1274] Barker, P., and S. Kille, "The COSINE and Internet X.500
   Schema", RFC 1274, University College, London, England, November
   1991.

   [RFC 1275] Kille, S., "Replication Requirements to provide an
   Internet Directory using X.500," RFC 1275, University College,
   London, England, November 1991.

   [RFC 1276] Kille, S.,  "Replication and Distributed Operations
   extensions to provide an Internet Directory using X.500", RFC 1276,
   University College, London, England, November 1991.

Top      Up      ToC       Page 162 
   [RFC 1277] Kille, S.,  "Encoding Network Addresses to support
   operation over non-OSI lower layers", RFC 1277, University College,
   London, England, November 1991.

   [RFC 1278] Kille, S., "A string encoding of Presentation Address",
   RFC 1278, University College, London, England, November 1991.

   [RFC 1279] Kille, S., "X.500 and Domains", RFC 1279, University
   College, London, England, November 1991.

   [RFC 1484] Kille, S., "Using the OSI Directory to achieve User
   Friendly Naming", RFC 1484, ISODE Consortium, July 1993.

   [RFC 1485] S. Kille, "A String Representation of Distinguished
   Names", RFC 1485, ISODE Consortium, July 1993.

   [RFC1487] Yeong, W., Howes, T., and S. Kille, "X.500 Lightweight
   Directory Access Protocol", RFC 1487, Performance Systems
   International, University of Michigan, ISODE Consortium, July 1993.

   [RFC 1488] Howes, T., Kille, S., Yeong, W., and C. Robbins, "The
   X.500 String Representation of Standard Attribute Syntaxes", RFC
   1488, University of Michigan, ISODE Consortium, Performance Systems
   International, NeXor Ltd., July 1993.  RFC-1558

   [RFC 1558] Howes, T., "A String Representation of LDAP Search
   Filters", RFC 1558, University of Michigan, December 1993.

   [RFC 1562] Michaelson, G. and Prior, M., "Naming Guidelines for the
   AARNet X.500 Directory Service", RFC 1562, The University of
   Queensland, The University of Adelaide, December 1993.

   [RFC 1567] Mansfield, G., and Kille, S., "X.500 Directory Monitoring
   MIB", RFC 1567, AIC Systems Laboratory, ISODE Consortium, January
   1994.

   [RFC 1608] Johannsen, T., Mansfield, G., Kosters, M., and  Sataluri,
   S., "Representing IP Information in the X.500 Directory", RFC 1608,
   Dresden University, AIC Systems Laboratory, Network Solutions, Inc.,
   AT&T Bell Laboratories, March 1994.

   [RFC 1609] Mansfield, G., Johannsen, T., and Knopper, M., "Charting
   Networks in the X.500 Directory", RFC 1609, AIC Systems Laboratory,
   Dresden University, Merit Networks, Inc., March 1994.

   [RFC 1617] Barker, P., Kille, S., and Lenggenhager, T., "Naming and
   Structuring Guidelines for X.500 Directory Pilots", RFC 1617,
   University College London, ISODE Consortium, SWITCH, May 1994.

Top      Up      ToC       Page 163 
   [RFC 1777] Yeong, W., Howes, T., and Kille, S., "Lightweight
   Directory Access Protocol", RFC 1777, Performance Systems
   International, University of Michigan, ISODE Consortium, March 1995.

   [RFC 1778] Howes, T., Kille, S., Yeong, W., and Robbins, "The String
   Representation of Standard Attribute Syntaxes", RFC 1778, University
   of Michigan, ISODE Consortium, Performance Systems International,
   NeXor Ltd., March 1995.

   [RFC 1779] Kille, S., "A String Representation of Distinguished
   Names", RFC 1779, ISODE Consortium, March 1995.

   [RFC 1781] Kille, S., "Using OSI Directory to Achieve User Friendly
   Naming", RFC 1781, ISODE Consortium, March 1995.

   [RFC 1798] Young, A., "Connection-less Lightweight Directory Access
   Protocol", RFC 1798, ISODE Consortium, June 1995.

   [RFC 1801] Kille, S., "MHS Use of the X.500 Directory to support MHS
   Routing", RFC 1801, ISODE Consortium, June 1995.

   [RFC 1803] Wright, R., Getchell, Howes, T., Sataluri, S., Yee, P.,
   and Yeong, W., "Recommendations for an X.500 Production Directory
   Service", RFC 1803, Lawrence Berkeley Laboratory, Lawrence Livermore
   National Laboratory, University of Michigan, AT&T Bell Laboratories,
   NASA Ames Research Center, Performance Systems International, Inc.,
   June 1995.

   [RFC 1804] Mansfield, G., Rajeev, P., Raghavan, S., and Howes, T.,
   "Schema Publishing in X.500 Directory", RFC 1804, AIC Laboratories,
   Hughes Software Systems, Indian Institute of Technology, Madras,
   University of Michigan, June 1995.

   [RFC 1823] Howes, T. and Smith, M.,     "The LDAP Application
   Programming Interface", RFC 1823, University of Michigan, August
   1995.

Top      Up      ToC       Page 164 
5. Security Considerations

   Security issues are not discussed in this memo.

6.  Editors' Addresses

   Chris Apple
   Room 2D-104
   AT&T Laboratories
   600 Mountain Ave.
   Murray Hill, NJ 07974
   U.S.A.
   e-mail: capple@master.control.att.com
   Voice: (908) 582-2409
   FAX:   (908) 582-6113

   Ken Rossen
   MCI Systemhouse, Inc.
   10 Williamsville Road
   Hubbardston Center, MA 01452-1311
   U.S.A.
   e-mail: kenr@shl.com
   Voice: (508) 928-5368
   FAX:   (508) 928-5399