tech-invite   World Map     

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

RFC 1292

 
 
 

A Catalog of Available X.500 Implementations

Part 2 of 3, p. 30 to 64
Prev RFC Part       Next RFC Part

 


prevText      Top       Page 30 
   The users can have a quipurc file to configure  their  work  environ-
   ments  with  DISH. This file should reside at the SYS$LOGIN directory
   of the user and it should be called "quipurc." (in UNIX  it's  called
   .quipurc)

INTERNETWORKING ENVIRONMENT

   RFC-1006 with TCP/IP, TP0 with X.25

HARDWARE PLATFORMS

   VAX

SOFTWARE PLATFORMS

   VAX/VMS 5.3
   VAX PSI 4.2
   VMS/ULTRIX Connection 1.2

AVAILABILITY

   Executables can be freely distributed for non-commercial use.
   Transfer mode binary.
   FTP user anonymous sun.iris-dcp.es (130.206.1.2)
   FTAM, user anon
   TSEL= <0103>H
   INT-X25= 21452160234012
   IXI= 2043145100102
   ISO-CLNS= 39724F1001000000010001000113020600100200 (COSINE P4.1)
   File: /isodevms/dishVMS2.BCK.Z compress SAVE_SET file (1.6 Mbytes)
   File: /isodevms/lzdcm.exe to uncompress the file

Top       Page 31 
NAME

   DIXIE
   University of Michigan

LAST MODIFIED

   November, 1991

KEYWORDS

   Available via FTP, DUA Light Weight Client, Free, Source, UNIX, Mul-
   tiple Vendor Platform, Needs ISODE

ABSTRACT

   The DIXIE protocol is used to give X.500 access to platforms that
   have only TCP/IP access.  The DIXIE server is an intermediate proto-
   col server that communicates with Internet clients on one side using
   a text-based UDP/TCP protocol and an X.500 DSA on the other side
   using DAP.  The protocol is fully described in RFC 1246.  A subset of
   the X.500 DAP is exported to the clients through the DIXIE protocol.
   There is a DIXIE API provided in the form of a library of C-callable
   routines.

   The DIXIE protocol and server are being used by the following
   products/projects:

     UD, a simple command line white pages DUA for Unix machines (dis-
     tributed with the DIXIE server)

     maX.500, a white pages DUA for the Macintosh (available from the
     same place as the DIXIE server)

     Network monitoring of DSAs by our Network Operations Center

     Lookup and display of caller identification based on telephone
     caller ID (using ISDN).

COMPLETENESS

   The DIXIE protocol does not support access to all X.500 features and
   operations.  All DAP operations except Abandon are supported.  Gen-
   eral searches (including multiple component searches) are supported.
   The DIXIE protocol supports none and simple authentication.  A subset
   of the service controls are supported.

Top       Page 32 
INTEROPERABILITY

   The current implementation of the DIXIE server works with the QUIPU
   DSA and DAP library.

PILOT CONNECTIVITY

   The DIXIE server has been tested in the Internet and PARADISE pilots.
   It provides full DUA Connectivity subject to the limitations dis-
   cussed above under completeness.

BUGS

   There are no known outstanding bugs.  But reports should be sent to
   x500@umich.edu.

CAVEATS AND GENERAL LIMITATIONS

   None, aside from those mentioned above under completeness.

INTERNETWORKING ENVIRONMENT

   DIXIE clients use TCP or UDP to communicate with the DIXIE server.
   The DIXIE server uses RFC-1006 with TCP/IP to communicate with the
   DSA, though other transport mechanisms for DSA communication should
   be possible.

HARDWARE PLATFORMS

   The DIXIE server is known to run on Sun 3, Sun 4, and DEC 3100 plat-
   forms.  It should run on any UNIX platform.  The DIXIE library is
   known to run on the same platforms, and also on the Macintosh.

SOFTWARE PLATFORMS

   The DIXIE server and library is known to run under SunOS 3.5, SunOS
   4.1.1, Ultrix 4.1 and 4.2.  The DIXIE library also runs on the Macin-
   tosh System Software 6 or later.

AVAILABILITY

   This software is openly available.  It may be obtained by anonymous
   FTP from terminator.cc.umich.edu in the directory ~ftp/x500. Documen-
   tation on the DIXIE protocol is provided along with the source code,
   which includes source for the DIXIE server, DIXIE library, and the UD
   client.

Top       Page 33 
   This software was developed at the University of  Michigan  by  Bryan
   Beecher,  Tim  Howes, and Mark Smith of the ITD Research Systems Unix
   Group.  It is subject to the following copyright.

   Copyright (c) 1991 Regents of the University of Michigan. All rights
   reserved.  Redistribution and use in source and binary forms are per-
   mitted provided that this notice is preserved and that due credit is
   given to the University of Michigan at Ann Arbor. The name of the
   University may not be used to endorse or promote products derived
   from this software without specific prior written permission. This
   software is provided "as is" without express or implied warranty.

Top       Page 34 
NAME

   DS-520
   DS-521
   Retix

LAST MODIFIED

   November, 1991

KEYWORDS

   API, Commercially Available, DSA/DUA, DUA Connectivity, DSA Connec-
   tivity,  Multiple Vendor Platforms, OSI Transport, RFC-1006, Source,
   UNIX

ABSTRACT

   DS-520 X.500 Distributed Directory Services for UNIX System V and
   DS-521 X.500 Directory User Agent (DUA) for UNIX System V form an
   integral part of the Retix OSI Networking Products family.  Designed
   for systems vendors, public carriers, and other OEMs, DS-520 is a
   complete high-performance implementation of X.500 in source code
   form, including a DUA, DSA Manager (DSAM), and DSA.  DS-521
   represents a subset of this product offering. It provides the DUA
   portal into the directory, which, for example, meets the needs of
   software vendors who plan to provide application packages with X.500
   Directory interaction capabilities. Within these two offerings, the
   DUA possesses two forms of interface. The first form, the DUA with
   User Interface, provides an interactive character-based user inter-
   face for users of Directory services.  The user agent provides access
   to the Directory via basic Directory service requests. The second
   form, the DUA with Programmatic Interface provides a standardized
   programmatic interface to application programs that must access
   Directory information. The interface is conformant to the X/Open
   Object Management (XOM) and X/Open Directory Services (XDS) stan-
   dards. This component provides all functionality related to Directory
   access and general OSI services down to the session layer. The DSAM
   provides an interactive character oriented user interface to a Direc-
   tory administrator.  The DSAM provides management functions either
   local to or remote from a DSA. Both the DUA and the DSAM are useful
   in the training, management, and manipulation of Directory entries
   maintaining operational and user attribute information. The DSA main-
   tains Directory database information and provides users the ability
   to read/compare, modify, search, and manage entries within the data-
   base. It maintains all or fragments of the Directory Information Base
   (DIB) and provides abstract service ports for DUAs and DSAs over DAP
   and DSP protocols respectively.

Top       Page 35 
COMPLETENESS

   DS-520 represents a complete implementation of the 1988 X.500 Recom-
   mendations with the exception of strong authentication as outlined in
   X.509. It is conformant to NIST, EWOS, and UK GOSIP Directory pro-
   files. It provides session through application layer protocol support
   and hence incorporates ROSE, ACSE, Presentation, and Session within
   its product stack. In addition to including all the attribute types,
   syntaxes, and object classes defined in X.520 and X.521, the DS-520
   includes support for those specified in the 1988 X.400 Recommendation
   X.402, Annex A. Remote on-line management of the DSA is supported by
   means of Network Management Forum CMIP.

   DS-521 represents a complete implementation of the X/Open Object
   Management (OM) and X/Open Directory Services (XDS) standards. It
   also incorporates session through application layer protocol support
   and thus includes ROSE, ACSE, Presentation, and Session within its
   product stack.

INTEROPERABILITY

   The DS-520 has been tested to interoperate with Banyan (DAP), CDC
   (DSP), IBM, ICL, OSIWare, Nixdorff, Unisys (DSP), Wollongong (DAP),
   and 3-Com (DSP).

   The DS-521 subset has undergone no separate interoperability testing.

PILOT CONNECTIVITY

   DSA Connectivity provided by the DS-520: The DSA provides complete
   support for the X.511 Abstract Service Definition, the directoryAc-
   cessAC and the directorySystemAC defined in the X.519 Protocol
   Specifications, and the Distributed Directory defined in the X.518
   Procedures for the Distributed Directory. It supports all the object
   classes, attribute types, and attribute syntaxes defined in X.520 and
   X.521. It does not support the Internet DSP however.

   DUA Connectivity provided by both the DS-520 and DS-521: The DUA pro-
   vides complete support for the X.511 Abstract Service Definition and
   the directoryAccessAC defined in the X.519 Protocol Specifications.
   The DUA with User Interface supports only a subset of the X.500
   attributes and object classes defined in X.520 and X.521. The DUA
   with Programmatic Interface, however, does support all the object
   classes, attribute types, and attribute syntaxes defined in these two
   recommendations.

Top       Page 36 
BUGS

   Product Action Requests (PARs) stemming externally from customers and
   internally from customer service and quality assurance engineers are
   generated and published in the form of weekly reports. A description
   and status of these PARs are provided to customers possessing
   software maintenance agreements.

CAVEATS AND GENERAL LIMITATIONS

   DS-520 and DS-521 are source code products ported to UNIX System V
   Release 3 and 4. Makefiles to generate the system are provided for
   the AT&T System V, SCO, and Interactive UNIX systems.

INTERNETWORKING ENVIRONMENT

   DS-520 and DS-521 offer two main compile time configuration options
   and hence internetworking configurations. In the first of these, they
   interface to the UNIX System V Transport Library Interface (TLI).
   The TLI provides a path between the session layer of a UNIX OSI
   application process and an OSI transport provider installed in the
   UNIX kernel. The latter transport provider may take the form of a
   Retix Unix LAN (LT-610) or WAN (WT-325) transport product. The second
   main option utilizes the UNIX System V ACSE/Presentation Library
   interface (APLI and the A/P Library), which provides OSI ACSE and
   Presentation layer services. The Retix AP-240 Presentation syntax
   manager product serves to map the standard Retix Presentation layer
   interface to the AT&T APLI. The APLI upper layers services may be
   provided by the Retix UL-220 product. UL-220 is the Retix implementa-
   tion of the AT&T Open Networking Platform Upper Layer Services module
   and includes the A/P library, as well as the OSI ACSE, Presentation,
   and Session services.

   DS-520 and DS-521 may also run on top of the TCP/IP stack by means of
   the Retix MP-120 product. MP-120 is a STREAMS based driver that
   implements RFC-1006 and thus allows OSI applications to run over a
   network based on the Internet suite of protocols (TCP/IP). Its main
   function provides a conversion between the TCP stream to the data
   packets required by OSI Transport Class 0 protocol and vice versa. As
   part of this process, it converts TCP/IP 32-bit addresses to hex
   values for use with OSI applications.

Top       Page 37 
HARDWARE PLATFORMS

   Being source code products ported to the UNIX System V Release 3  and
   4  operating system environment, DS-520 and DS-521 are hardware plat-
   form independent. They currently both have sample portations and test
   configurations on various Intel 80386 platforms running Unix System V
   Release 3 and 4.

SOFTWARE PLATFORMS

   Currently, DS-520 and DS-521 include reference implementations for
   the AT&T System V Release 4, SCO UNIX System V/386 Version 3.2.2, and
   the Interactive UNIX System V/386 Version 2.2 operating systems.
   Raima Corporation's db_Vista III Version 3.1 serves as the database
   engine for the Directory product.

AVAILABILITY

   DS-520 and DS-521 are commercially available from:

           Retix
           2401 Colorado Avenue
           Santa Monica, California
           90404-3563 USA

           Sales and Information:  310-828-3400
           FAX:                    310-828-2255

Top       Page 38 
NAME

   HP X.500 Distributed Directory Software
   Hewlett Packard

LAST MODIFIED

   July, 1991

KEYWORDS

   API, CLNP, Commercially Available, DSA/DUA, HP, X.25

ABSTRACT

   HP's Distributed Directory Software is a fully distributed Directory
   that supports both the DAP and DSP protocols, which were specified in
   the 1988 CCITT/ISO X.500 documents.  Besides implementing the stan-
   dard, we have also put in proprietary access control and replication.
   These additional features will be migrated to the standard definition
   at the time that they are stable.  Users are able to define their own
   attributes, objects classes and DIT structure rules.

   In order to make this software easy to use a set of menu driven
   screens have been provided.  There are easy to use data access and
   data management screens.  For system administrators, these is also a
   set for screens that are used to help configure the servers and
   manage the schema. Startup and Shutdown utilities are also included.

   For application developers an X/Open-APIA XDS API is provided, along
   with some helper routines that help reduce development time.  The XDS
   API includes the following functions:

           Bind
           Read
           Search
           Add
           Remove
           Unbind
           Version

   A subset of the X/Open-APIA Object Management (XOM) functions are
   available thru the interface.  The subset are those that are neces-
   sary to perform the directory operations.

   For bulk operations a batch interface is also available.

Top       Page 39 
COMPLETENESS

   This software implements the 1988 X.500 CCITT/ISO Standard.  It fully
   supports DAP and DSP, minus strong authentication.  By default it
   contains all of the X.520 Attributes and the X.521 Syntaxes and
   Object Classes.  Additionally, the Annex B DIT Structure can be
   enforced.

INTEROPERABILITY

   Interoperability testing will be undertaken as new X.500 products are
   introduced into the market.

PILOT CONNECTIVITY

   [No information provided--Ed.]

BUGS

   No major ones at this time.

CAVEATS AND GENERAL LIMITATIONS

   This is pilot software for organizations who wish to learn about HP's
   X.500 offering.

INTERNETWORKING ENVIRONMENT

   TP0 or TP4 on 802.3 or X.25

HARDWARE PLATFORMS

   HP-9000 800     Minicomputer
   HP-9000 300     Workstation
                   with at least 8 M of internal memory
                   with 9 M of available disk space for the software

SOFTWARE PLATFORMS

   Distributed and Supported for HP-UX version 7.0.

AVAILABILITY

   Limited Commercial Availability.

   For more information in the U.S. call 1-800-752-0900.  Outside of the
   U.S. please contact your local HP Sales Office.

Top       Page 40 
NAME

   INTERACTIVE Systems' X.500 DSA/DSAM
   INTERACTIVE Systems' X.500 DUA
   INTERACTIVE Systems Corporation

LAST MODIFIED

   July, 1991

KEYWORDS

   API, Commercially Available, DSA/DUA, Multiple Vendor Platforms, OSI
   Transport, RFC-1006, UNIX

ABSTRACT

   The INTERACTIVE Systems X.500 DSA/DSAM and X.500 DUA provide a com-
   plete implementation of the OSI X.500 Directory Systems Agent, Direc-
   tory Systems Agent Manager, and Directory Services User Agent. These
   software packages allow remote access for Directory Systems Agents
   and include the following protocols:

     - Directory System Protocol (DSP)

     - Directory Access Protocol (DAP)

     - Common Management Information Protocol (CMIP)

     - Remote Operations Service Element (ROSE)

     - Association Control Service Element (ACSE)

     - Presentation services

     - BCS Session services

     - DBMS and utilities

     - X/Open XDS API (included in the DUA)

   These products will be available in Q3 1991 in source code form only.

Top       Page 41 
COMPLETENESS

   These products provide:

     - a complete implementation of the X.500 distributed Directory

     - a DUA with command line UI and X/Open  Directory  Services  (XDS)
     API

     - a Multiprocess DSA with integral high performance DBMS

     - remote or local CMIP based DSA management

     - a DSA manager that  provides  on-line  DSA  monitoring,  control,
     Directory schema manipulation, and DUA functions

     - Support for all 1988 X.500, 1988 X.400, and  MAP/TOP  3.0  object
     types and the capability to add new object types

     - Conformance with NIST, EWOS, and U.K. GOSIP X.500 Directory  pro-
     files

INTEROPERABILITY

   Not available at this time.

PILOT CONNECTIVITY

   [No information provided--Ed.]

BUGS

   Not available at this time.

CAVEATS AND GENERAL LIMITATIONS

   Not available at this time.

INTERNETWORKING ENVIRONMENT

   The INTERACTIVE Systems implementation of X.500 Directory Services
   will operate over both RFC-1006 (in TCP/IP Based networks) and over
   the Retix Local Area and Wide Area Network services.

HARDWARE PLATFORMS

   These products are available in source code form only and can be
   ported to any UNIX-based computers.

Top       Page 42 
SOFTWARE PLATFORMS

   These products operate in the UNIX System V Release 3.2 and System V
   Release 4 operating systems.

AVAILABILITY

   Both products will be available in Q3 1991.  For more information
   contact:

           INTERACTIVE Systems Corporation
           1901 North Naper Boulevard
           Naperville, IL.  60563-8895
           PHONE: (708) 505-9100 extension 232
           FAX: (708) 505-9133  Attn.: Jim Hancock

Top       Page 43 
NAME

   Mac-ISODE
   Computer Science Department of Massey University

LAST MODIFIED

   November, 1991

KEYWORDS

   API, Available via FTP, DSA/DUA, Free, Macintosh, Needs ISODE, RFC-
   1006, Source

ABSTRACT

   Mac-ISODE is a reasonably complete port of ISODE version 7.0. It sits
   on top of Mac TCP and its development environment is MPW with the GNU
   C compiler See entry for QUIPU/ISODE for a detailed description of
   the DSA/DUA.

COMPLETENESS

   See entry for QUIPU/ISODE.

INTEROPERABILITY

   See entry for QUIPU/ISODE.

PILOT CONNECTIVITY

   Not tested.

BUGS

   Macintosh related problems should be sent to PKay@massey.ac.nz.

CAVEATS AND GENERAL LIMITATIONS

   No testing of the DSA has been done.

INTERNETWORKING ENVIRONMENT

   See entry for QUIPU/ISODE.

Top       Page 44 
HARDWARE PLATFORMS

   Macintosh, >1Mb memory, System 6.x

SOFTWARE PLATFORMS

   Macintosh, >1Mb memory, System 6.x

AVAILABILITY

   The Macintosh part of the package is freely available.  Anonymous FTP
   from cc-vms1.massey.ac.nz (130.123.1.4)

Top       Page 45 
NAME

   MacDish
   NASA Ames Research Center

LAST MODIFIED

   July, 1991

KEYWORDS

   DUA Light Weight Client, Limited Functionality, Macintosh, Needs
   ISODE, Potentially Unavailable

ABSTRACT

   MacIntosh interface which connects to a TCP/IP port attached to dish
   running on UNIX or other dish-capable host.  Uses a point-and-click
   interface to simplify dish access.

COMPLETENESS

   No authentication, no modify/delete/add ability.

INTEROPERABILITY

   Interoperates with QUIPU/dish

PILOT CONNECTIVITY

   Being used in the White Pages Pilot Project.

BUGS

   Not complete yet, so there are some bugs (primarily formatting, win-
   dow management).

CAVEATS AND GENERAL LIMITATIONS

   Not a terribly capable interface.

INTERNETWORKING ENVIRONMENT

   Pure TCP/IP.  Does not require OSI stack support.

Top       Page 46 
HARDWARE PLATFORMS

   MacDish runs on Macintosh computers

SOFTWARE PLATFORMS

   MacTCP and MacOS 6.0.x.

AVAILABILITY

   Not yet available.  Contact is:

           Mylene Marquez
           MS 233-18
           NASA Ames Research Center
           Moffett Field, CA 94035-1000
           (415) 604-3836

Top       Page 47 
NAME

   maX.500
   University of Michigan

LAST MODIFIED

   November, 1991

KEYWORDS

   Available via FTP, DUA Light Weight Client, Free, Macintosh

ABSTRACT

   maX.500 is a Macintosh X.500 directory application useful for
   displaying and modifying white pages information about people.  It
   runs on top of the DIXIE protocol (described in RFC 1246).  maX.500
   is currently in production release 1.1 within the University of
   Michigan and several other places.

   Features include the ability to display and modify the following
   attributes: title, description, commonName, uid, mail, postalAddress,
   homePostalAddress, telephoneNumber, facsimileTelephoneNumber, home-
   Phone.  Photos can also be displayed.  The software also provides
   access to the finger protocol.  Various preferences are user-
   tailorable, including caching.

COMPLETENESS

   maX.500 uses the DIXIE protocol to access X.500 and thus is subject
   to the same completeness restrictions as DIXIE.  It provides Read,
   Search, and Modify capabilities.

INTEROPERABILITY

   Works with the DIXIE server, which works with the QUIPU DSA and DAP
   library.

PILOT CONNECTIVITY

   It has been tested (in conjunction with the DIXIE server) in both the
   Internet and PARADISE pilots.

BUGS

   No outstanding bugs are known.  But reports should be sent to
   x500@itd.umich.edu.

Top       Page 48 
CAVEATS AND GENERAL LIMITATIONS

   maX.500 is heavily oriented to white pages information and thus gen-
   eral access to the DIXIE protocol is not provided.

INTERNETWORKING ENVIRONMENT

   maX.500 uses the DIXIE protocol and thus TCP to communicate with the
   DIXIE server.  The Macintosh needs to have MacTCP installed.

HARDWARE PLATFORMS

   Mac Plus or newer machine with one megabyte or more of memory.

SOFTWARE PLATFORMS

   Apple System Software 6.0 or above (including System 7), with MacTCP
   installed.

AVAILABILITY

   This software is openly available.  It may be obtained by anonymous
   FTP from terminator.cc.umich.edu in the directory ~ftp/x500.

   This software was developed at the University of Michigan by Mark
   Smith of the ITD Research Systems Unix Group and is subject to the
   following copyright.

   Copyright (c) 1991 Regents of the University of Michigan.  All rights
   reserved.  Redistribution and use in source and binary forms are per-
   mitted provided that this notice is preserved and that due credit is
   given to the University of Michigan at Ann Arbor. The name of the
   University may not be used to endorse or promote products derived
   from this software without specific prior written permission. This
   software is provided "as is" without express or implied warranty.

Top       Page 49 
NAME

   OSI Access and Directory
   Control Data Corporation

LAST MODIFIED

   November, 1991

KEYWORDS

   Commercially Available, DUA Connectivity, DSA Connectivity, API,
   DSA/DUA, OSI CLNP, RFC-1006, X.25, MIPS (under Control Data's EP/IX
   OS).

ABSTRACT

   OSI Access and Directory includes a QUIPU (version 6.6) based imple-
   mentation of Directory with enhancements including:

     - TP4 CLNP connectivity

     - Directory API based on the X.400 API

     - Support for X.400 objects

     - Integration with Control Data's X.400 MHS products

     - Curses based user interface

     - A DUA daemon that provides Directory access for applications

     - Enhanced photo attribute support

     - ACL enhancements

     - DIXIE, DAD and PH.X500 support

COMPLETENESS

   As per QUIPU.

INTEROPERABILITY

   OSI Access and Directory can interoperate with any QUIPU based Direc-
   tory.  It has also been informally interoperated with RETIX and
   UNISYS implementations.

Top       Page 50 
PILOT CONNECTIVITY

   DUA Connectivity.  DSA Connectivity without InternetDSP support.

BUGS

   As per QUIPU.

CAVEATS AND GENERAL LIMITATIONS

   As per QUIPU.

INTERNETWORKING ENVIRONMENT

   As per QUIPU (RFC-1006 with TCP/IP, TP0 with X.25) plus TP4 over
   CLNP.

HARDWARE PLATFORMS

   Control Data 4000 systems.

SOFTWARE PLATFORMS

   Control Data EP/IX.

AVAILABILITY

   Commercially available from:

           Control Data Corporation
           Computer Products Marketing
           4000 Series Networking
           HQW10H
           P.O. Box 0
           Minneapolis, MN 55440-4700
           USA

           1-800-345-6628

Top       Page 51 
NAME

   OSI-DSA
   Unisys

LAST MODIFIED

   November, 1991

KEYWORDS

   API, CLNP, Commercially Available, DSA Only, RFC-1006, Source,
   Unisys, X.25

ABSTRACT

   OSI-DSA provides a Directory System agent for controlled access to
   the OSI Directory Information Base.  It provides full support for the
   joint ISO/IEC IS-9594 International standard and CCITT X.500 Recom-
   mendations 1988 protocols necessary for implementing the Directory
   Information Base distributed across a number of DSA's.

   The product also includes an Administration User interface program,
   to allow a human administrator to construct and maintain the local
   Directory Information.

   Specific features provided by the Directory System Agent include:

       (i)    Support of the directoryAccessAC and directorySystemAC
              application contexts (i.e. both Directory Access Protocol
              (DAP) and Directory System Protocol (DSP)

       (ii)   Bind Security levels of none and simple unprotected.

       (iii)  Capability of acting as a first level DSA.

       (iv)   Support for chaining and multi-casting where necessary in
              handling distributed operations. Also supports the return
              of referrals.

       (v)    Support for all attribute types and syntaxes defined in
              X.520.  Users are also able to define their own attributes
              and syntaxes.

       (vi)   Support for all the object classes and attribute sets
              defined in X.521.  Users are also able to define their own
              object classes and attribute sets.  Support is also pro-
              vided for a NAME-BINDING specification, for defining the

Top       Page 52 
              Directory Information Tree (DIT) structure.

       (vii)  An access control mechanism based on the ISO  access  con-
              trol  working  papers  to  allow for controlled access and
              maintenance of Directory entries and attributes.

       (viii) Logging of errors and significant Directory events, as
              well as optional trace information.

       (ix)   The OSI-DSA utilizes the services of ROSE (X.219) and ACSE
              (X.217) as defined in clause 8 of X.519

   The Administration program provides the following functions

       (i)    An interface to each of the basic Directory Operations of
              Read, Compare, List, Search, Add, Modify, ModifyRDN.

       (ii)   A Dump/Load utility to dump the information in the local
              DIB into an ASCII file and load it again into the DIB from
              such a file.

       (iii)  Knowledge Reference maintenance facilities to Add, Delete
              Modify and Read all types of Knowledge References.

       (iv)   Facilities to control the operation of local Directory
              processes.

       (v)    Control over the level of logging and tracing.

COMPLETENESS

   The OSI-DSA provides all functionality defined in, and is fully con-
   formant to, the joint ISO/IEC IS-9594 International standard and
   CCITT X.500 Recommendations 1988, and the NIST 1988 Stable agreements
   on Directory Services.

   The only exception is that no support is provided for strong authen-
   tication or digital signatures.

   Conformance with respect to clause 9 of X.519:

       (i)    The DSA supports both the directoryAccessAC and directo-
              rySystemAC application contexts.

       (ii)   The DSA is capable of acting as a first-level DSA.

       (iii)  The chained mode of operation as defined in X.518 is sup-
              ported.

Top       Page 53 
       (iv)   Bind Security levels of none and simple unprotected are
              supported.

       (v)    All attribute types and syntaxes defined in X.520 are sup-
              ported. Users are also able to define their own attributes
              and syntaxes.

       (vi)   All the object classes and attribute sets defined in X.521
              are supported.  Users are also able to define their own
              object classes and attribute sets.  Support is also pro-
              vided for a NAME-BINDING specification, for defining the
              Directory Information Tree (DIT) structure.

       (vii)  The DSA conforms to all the static requirements defined in
              clause 9.2.2 of X.519

       (viii) The DSA conforms to all the dynamic requirements defined
              in clause 9.2.3 of X.519

INTEROPERABILITY

   The product was demonstrated at "Interop 91" in San Jose, October
   1991 as part of the OSI Showcase demo involving several vendors'
   directory products.

   Informal interoperability has been achieved against the ISODE 6.0
   QUIPU Directory implementation.  Interoperability testing against
   other vendors is in progress.

   Formal interoperability testing is awaiting the soon to be completed
   OSInet X.500 interoperability test suite.

PILOT CONNECTIVITY

   Not tested.

BUGS

   Full customer support is provided via your local Unisys Customer Ser-
   vices Organization.

CAVEATS AND GENERAL LIMITATIONS

   Results returned via the OSI-DSA are presently limited to 32K in the
   current release, which is in line with the 1988 NIST agreements.

   Patches for the Unix V.4 release may be made available on request to
   raise this limit to 1Mb.

Top       Page 54 
   The product currently does not provide any support for replication,
   although development work is in progress, based on the current ISO
   Draft proposal for Replication.

INTERNETWORKING ENVIRONMENT

   OSI-DSA runs over all communications environments supported by the
   Unisys OSI stack product (see Software platforms). Currently these
   support TP0, TP2, TP3 and TP4 over X.25 and TP4 over CLNP on 802.3
   and X.25.  Support for RFC1006 over TCP/IP is under development.

HARDWARE PLATFORMS

   The product is available on all Unisys Unix 6000 Series machines.

   Source code is available for portation to non-Unisys platforms.

SOFTWARE PLATFORMS

   The product is distributed and supported for Unix System V.3 and Unix
   System V.4.

   On Unix V.3, it requires the Unisys Application Presentation Service
   OSI stack software (APS), and Unisys Transport Network Service
   software (TNS).  On Unix V.4, it requires the integrated Unisys OSI
   stack software product (STK).  These services are accessed via the
   ROSLI (ROSE) and APLI (ACSE) programming interfaces which are
   currently the subject of standardization efforts by XOpen and Unix
   International.

   A runtime version of either the Informix or Oracle relational data-
   base products is required for the Directory Information Base.

AVAILABILITY

   Unisys Unix OSI Directory System Agent is commercially available. For
   information on porting to non-Unisys platforms, contact:

           Socs Cappas
           Australian Centre for Unisys Software
           115 Wicks Rd
           North Ryde
           N.S.W, 2113
           Australia
           socs@syacus.acus.oz.au
           Ph: 61 2 390 1312

Top       Page 55 
   For  any  other  information  contact  your  local  Unisys  marketing
   representative or:

           Unisys Corporation
           Corporate Marketing
           Mail Drop B-130
           Blue Bell,  PA 19424
           USA

Top       Page 56 
NAME

   OSI-DUA
   Unisys

LAST MODIFIED

   November, 1991

KEYWORDS

   API, CLNP, Commercially Available, DUA Only, RFC-1006, Source,
   Unisys, X.25

ABSTRACT

   OSI-DUA is a Unix C Program interface library. It allows OSI or user
   applications to access the services of an X.500 conformant Directory,
   by making calls to a library of C routines.

   Specific features provided by this program interface library are as
   follows:

       (i)    Connection to any remote X.500 conformant DSA via an OSI
              stack, or connection to a co-resident Unisys OSI DSA via
              IPC mechanisms.

       (ii)   All operations defined in the directoryAccessAC applica-
              tion context (Bind, UnBind, Read, Compare, Search, List,
              AddEntry, ModifyEntry, ModifyRDN, Abandon, DeleteEntry).

       (iii)  Directory Bind security levels of none and simple unpro-
              tected.

       (iv)   Execution of both blocking and non-blocking operations.
              (A non-blocking call to the library will return immedi-
              ately, allowing for results to be obtained once the opera-
              tion has completed)

       (v)    Acceptance of multiple concurrent non-blocked operations
              on the one user session.

       (vi)   The DUA utilizes the services of ROSE (X.219) and ACSE
              (X.217) as defined in clause 8 of X.519

Top       Page 57 
COMPLETENESS

   When communicating with a Remote DSA the DUA library is fully confor-
   mant with the Directory Access Protocol detailed in the X.500
   Recommendations/IS-9594 standards.

   Conformance with respect to clause 9 of X.519:

       (i)    All operations defined in the  directoryAccessAC  applica-
              tion  context  (Bind, UnBind, Read, Compare, Search, List,
              AddEntry, ModifyEntry,  ModifyRDN,  Abandon,  DeleteEntry)
              are supported.

       (ii)   Directory Bind security levels of none and  simple  unpro-
              tected are supported.

       (iii)  The directoryAccessAC application context is supported  as
              specified in clause 7 of X.519.

       (iv)   The DUA conforms to the mapping onto used services as  de-
              fined in clause 8 of X.519.

INTEROPERABILITY

   Informal interoperability has been achieved against the ISODE 6.0
   QUIPU Directory implementation.  Interoperability testing against
   other vendors is in progress.

   Formal interoperability testing is awaiting the soon to be completed
   OSInet X.500 interoperability test suite.

PILOT CONNECTIVITY

   Not tested.

BUGS

   Full customer support is provided via your local Unisys Customer Ser-
   vices Organisation.

Top       Page 58 
CAVEATS AND GENERAL LIMITATIONS

   The present OSI-DUA does not provide for the  automatic  handling  of
   referrals  by  the  interface library. However interface routines are
   provided which allow referrals to be acted upon by the user  applica-
   tion.

   The present OSI-DUA provides a proprietary C  programming  interface.
   An XOpen XDS conformant interface is currently under development.

INTERNETWORKING ENVIRONMENT

   OSI-DUA runs over all communications environments supported by the
   Unisys OSI stack product (see Software platforms). Currently these
   support TP0, TP2, TP3 and TP4 over X.25 and TP4 over CLNP on 802.3
   and X.25.  Support for RFC1006 over TCP/IP is under development.

HARDWARE PLATFORMS

   The product is currently available on all Unisys Unix 6000 Series
   machines.

   Source code is available for portation to non-Unisys platforms.

SOFTWARE PLATFORMS

   The product is distributed and supported for Unix System V.3 and Unix
   System V.4.

   On Unix V.3, it requires the Unisys Application Presentation Service
   OSI stack software (APS), and Unisys Transport Network Service
   software (TNS).  On Unix V.4, it requires the integrated Unisys OSI
   stack software product (STK).  These services are accessed via the
   ROSLI (ROSE) and APLI (ACSE) programming interfaces which are
   currently the subject of standardization efforts by XOpen and Unix
   International.

AVAILABILITY

   Unisys Unix OSI Directory System Agent is commercially available. For
   information on porting to non-Unisys platforms, contact:

Top       Page 59 
           Socs Cappas
           Australian Centre for Unisys Software
           115 Wicks Rd
           North Ryde
           N.S.W, 2113
           Australia
           socs@syacus.acus.oz.au
           Ph: 61 2 390 1312

   For any other information contact your local Unisys marketing
   representative or:

           Unisys Corporation
           Corporate Marketing
           Mail Drop B-130
           Blue Bell, PA  19424
           USA

Top       Page 60 
NAME

   POD
   Brunel University

LAST MODIFIED

   November, 1991

KEYWORDS

   Available via FTAM, Available via FTP, DUA Only, Free, Included in
   ISODE, Limited Functionality, Multiple Vendor Platforms, Needs ISODE,
   RFC-1006, Source, UNIX

ABSTRACT

   POD (POpup Directory) is an X.500 DUA interface for the X Window Sys-
   tem.  POD is a first attempt at a multiwindow directory tool. It
   offers a simplified interfaces to the basic X.500 operations of read,
   search, list and modify entry.

   POD does not provide any sophisticated access to the DSA.  Operations
   are performed synchronously.  The Directory is thus presented as is,
   i.e.  a hierarchical tree of information, with the user required to
   "navigate" the DIT in order to locate required information.

   POD is available as part of the ISODE release from version 6.0
   onwards.

COMPLETENESS

   88 standard: strong authentication not implemented

INTEROPERABILITY

   Believed to be compliant, though untested.

PILOT CONNECTIVITY

   DUA Connectivity: POD is in use in many directory pilots, certainly
   including PARADISE and the Internet.

BUGS

   Bugs to x500@brunel.ac.uk

Top       Page 61 
INTERNETWORKING ENVIRONMENT

   TP0 over TCP/IP (as ISODE)

HARDWARE PLATFORMS

   Most UNIX machines

SOFTWARE PLATFORMS

   UNIX
   MIT X libraries (release 11 version 4)
   ISODE/QUIPU libraries (version 6.7 upwards)

AVAILABILITY

   Openly available as part of the ISODE release.  Sources are freely
   available for commercial or non-commercial use from:

           src.brunel.ac.uk [134.83.128.3]

   Files are:

           x500/pod.tar.Z
           x500/sd.tar.Z

   Contacts:

           Andrew.Findlay@brunel.ac.uk     +44 1 895 74000 x 2512
           Damanjit.Mahl@brunel.ac.uk      +44 1 895 74000 x 2946
           x500@brunel.ac.uk

   Postal Address:

           Andrew Findlay
           Computer Centre
           Brunel University
           Cleveland Road,
           Uxbridge, Middlesex
           UB8 3PH
           United Kingdom

Top       Page 62 
NAME

   psiwp
   Performance Systems International Inc.

LAST MODIFIED

   July, 1991

KEYWORDS

   Available via FTP, DUA Light Weight Client, DUA Only, Free, Limited
   Functionality, Macintosh, Needs ISODE, Source

ABSTRACT

   psiwp is a Macintosh Front End to White Pages service.  It is a
   graphical user interface implementing a partial-DUA.  It is based on
   the ISODE QUIPU X.500 implementation and the Directory Assistance
   Protocol (DAP).

   psiwp is a Macintosh application tailored specifically to provide
   easy access to the Directory for the purposes of performing White
   Pages searches.  Implements User-Friendly Naming scheme developed in
   IETF OSI-DS Working Group.

   psiwp implements a Directory Assistance Protocol (DAP) client.

COMPLETENESS

   Compliant with X.500 standards to the extent that the QUIPU implemen-
   tation is.

INTEROPERABILITY

   Successfully interoperates with QUIPU DSAs

PILOT CONNECTIVITY

   Being used in the White Pages Pilot Project.

BUGS

   Support is available (for registered users of psiwp only) from
   psiwp-help@psi.com.

Top       Page 63 
CAVEATS AND GENERAL LIMITATIONS

   psiwp is not a general-purpose DUA. It was designed to be a special-
   purpose front-end for performing White Pages searches and thus, in
   the interests of simplification, does not provide the full range of
   functionality supported by the X.500 standard. A Directory Assistance
   server (available as part of the ISODE distribution) must also be run
   by sites that do not want to run psiwp against either of the two
   White Pages Pilot Project service machines, wp1.psi.net and
   wp2.psi.net.

INTERNETWORKING ENVIRONMENT

   Runs on Macintoshes as a Finder or MultiFinder application.

HARDWARE PLATFORMS

   Runs on Macintoshes that support MacTCP. Requires an ethernet board
   or AppleTalk connectivity. At least 1MB of memory is required, and
   while psiwp will run on most forms of Macintoshes, a Mac-II is recom-
   mended.

SOFTWARE PLATFORMS

   Requires MacTCP 1.0 or later, and Finder (or Multifinder) 6.x (Finder
   7.0 WILL NOT WORK). Requires ISODE Version 6.8 or later.

AVAILABILITY

   psiwp is shareware available for anonymous ftp from uu.psi.com
   [136.161.128.3] in pilot/PSIWP.Hqx.  A nominal fee is charged upon
   registration as a PSIWP user.

   Source code to the psiwp application may be licensed from PSI Inc.
   as part of PSI's Software Source Distribution (SSD).  Email to

           ssd-info@psi.com

   will elicit an automatic response containing information on the SSD.
   Ordering information may be obtained by sending electronic mail to

           ssd-order@psi.com

   or contacting PSI at

Top       Page 64 
           Performance Systems International Inc.
           11800 Sunrise Valley Drive
           Suite 1100
           Reston, Virginia 22091.

           1.703.620.6651
           1.800.82PSI82 (1.800.827.7482)
           1.703.620.4586 (fax)


Next RFC Part