Tech-invite3GPPspaceIETFspace
959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 1292

A Catalog of Available X.500 Implementations

Pages: 103
Obsoleted by:  1632
Part 1 of 3 – Pages 1 to 29
None   None   Next

ToP   noToC   RFC1292 - Page 1
Network Working Group                                            R. Lang
Request for Comments: 1292                             SRI International
FYI: 11                                                        R. Wright
                                            Lawrence Berkeley Laboratory
                                                                 Editors
                                                            January 1992


             A Catalog of Available X.500 Implementations

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard.  Distribution of this memo is
   unlimited.

Abstract

   The goal of this document is to provide information regarding the
   availability and capability of implementations of X.500.  Comments
   and critiques of this document, and new or updated descriptions of
   X.500 implementations are welcome.  Send them to the Directory
   Information Services Infrastructure (DISI) Working Group
   (disi@merit.edu) or to the editors.

1.  Introduction

   This document catalogs currently available implementations of X.500,
   including commercial products and openly available offerings.  It
   contains descriptions of Directory System Agents (DSA), Directory
   User Agents (DUA), and DUA client applications.  The latter can
   include such applications as browsers, DSA management tools, or
   lightweight DUAs that employ an application-level protocol to
   communicate with a DUA (which then in turn communicates with a DSA)
   to support user service.  Section 2 of this document contains a
   listing of implementations cross referenced by keyword.  This list
   will aid in identifying particular implementations that meet your
   criteria.

   To compile this catalog, the DISI Working Group solicited input from
   the X.500 community by surveying several Internet mailing lists,
   including: iso@nic.ddn.mil, isode@nic.ddn.mil, osi-ds@cs.ucl.ac.uk,
   and disi@merit.edu.
ToP   noToC   RFC1292 - Page 2
   Readers are encouraged to submit comments regarding both the form and
   content  of  this  memo.  New submissions are always welcome.  Please
   direct input to the parties as described in the Status of  this  Memo
   section.  DISI will produce new versions of this document when a suf-
   ficient number of changes have been received.  This  will  be  deter-
   mined subjectively by the DISI chairperson.

1.1  Purpose

   The growth of existing X.500 pilot activities (e.g., White Pages
   Pilot Project) and the advent of new pilots (e.g., ARRNet Directory
   Services Project, NIST/GSA Pilot Project) are signals that X.500 is a
   viable directory service mechanism for the Internet community.  A
   goal of DISI is to enable the continued growth of X.500 by lowering
   the lack-of-information barrier.  This document takes one step toward
   that goal by providing an easily accessible source of information on
   X.500 implementations.

1.2  Scope

   This document contains descriptions of either commercially or freely
   available X.500 implementations.  It does not provide instructions on
   how to install, run, or manage these implementations.  Because the
   needs and computing environments of each organization differ vastly,
   no recommendations are given.  The descriptions and indices are
   provided to make the readers aware of existing options and to enable
   more informed choices.

1.3 Disclaimer

   Implementation descriptions were written by implementors and vendors,
   and not by the members of DISI.  Although DISI has worked with the
   description authors to ensure readability, no guarantees can be made
   regarding the validity of descriptions or the value of said
   implementations.  Caveat emptor.

1.4  Overview

   Section 1 contains introductory information.

   Section 2 contains a list of keywords, their definitions, and a cross
   reference of the X.500 implementations by these keywords.

   Section 3 contains the X.500 implementation descriptions.

   Section 4 lists the editors' addresses.
ToP   noToC   RFC1292 - Page 3
1.5  Acknowledgments

   The creation of this catalog would not have been possible without the
   efforts of the description authors and the members of the DISI
   Working Group.  The editors thank you for your hard work and
   constructive feedback.  A special thanks is also extended to the
   members of the NOCTools Working Group.  The "Network Management Tool
   Catalog" (RFC-1147) served as a valuable example.  Bob Stine and Bob
   Enger made key suggestions that enabled us to learn from their
   experiences.

   The efforts of the editors were sponsored by Defense Advanced
   Research Projects Agency Contract Number DACA76-89-D-0002 (Field
   Operational X.500 Project), and U. S. Department of Energy Contract
   Number DE-AC03-76SF00098.

2.  Keywords

   Keywords are abbreviated attributes of the X.500 implementations.
   The list of keywords defined below was derived from the
   implementation descriptions themselves.  Implementations were indexed
   by a keyword either as a result of: 1) explicit, not implied,
   reference to a particular capability in the implementation
   description text, or 2) input from the implementation description
   author(s).

2.1  Keyword Definitions

   This section contains keyword definitions.  They have been organized
   and grouped by functional category.  The definitions are ordered
   first alphabetically by keyword category, and second alphabetically
   by implementation name within keyword category.


2.1.1  Availability


   Available via FTAM
        Implementation is available using FTAM.

   Available via FTP
        Implementation is available using FTP.

   Commercially Available
        This implementation can be purchased.

   Free
        Available at no charge, although other restrictions may apply.
ToP   noToC   RFC1292 - Page 4
   Potentially Unavailable
        Implementation was not available at the time this document was
        written.

   Source
        Source code is available, potentially at an additional cost.


2.1.2  Implementation Type


   API
        Implementation comes with an application programmer's interface
        (i.e., a set of libraries and include files).

   DSA Only
        Implementation consists of a DSA only.  No DUA is included.

   DSA/DUA
        Both a DSA and DUA are included in this implementation.

   DUA Light Weight Client
        Implementation is a DUA-like program that uses a non-OSI proto-
        col to satisfy X.500 requests.

   DUA Only
        Implementation consists of a DUA only.  No DSA is included.


2.1.3  Internetworking Environment


   CLNP
        Implementation uses OSI CLNP.

   OSI Transport
        Implementation description specifies that OSI transport proto-
        cols are used but does not specify which one(s).

   RFC-1006
        Implementation uses RFC-1006 with TCP/IP transport service.

   X.25
        Implementation uses OSI X.25.
ToP   noToC   RFC1292 - Page 5
2.1.4  Pilot Connectivity


   DUA Connectivity
        The DUA can be connected to the pilot, and information on any
        pilot entry looked up.  The DUA is able to display standard
        attributes and object classes and those defined in the COSINE
        and Internet Schema.

   DSA Connectivity
        The DSA is connected to the DIT, and information in this DSA is
        accessible from any pilot DUA.


2.1.5  Miscellaneous


   Included in ISODE
        DUAs that are part of ISODE.

   Limited Functionality
        Survey states that the implementation has some shortcomings or
        intended lack of functionality, e.g., omissions were part of the
        design to provide an easy-to-use user interface.

   Needs ISODE
        ISODE is required to compile and/or use this implementation.

   X Window System
        Implementation uses the X Window System to provide its user
        interface.


2.1.5 Operating Environment


   3Com
        Implementation runs on a 3Com platform.

   Apollo
        Implementation runs on an Apollo platform.

   Bull
        Implementation runs on a Bull platform.

   Cray
        Implementation runs on a Cray.
ToP   noToC   RFC1292 - Page 6
   DEC Ultrix
        Implementation runs under DEC Ultrix.

   HP
        Implementation runs on an HP platform.

   IBM (Non-PC and RISC)
        Implementation runs on some type of IBM, which is not a PC or
        UNIX workstation.

   IBM PC
        Implementation runs on a PC.

   IBM RISC
        Implementation runs on IBM's RISC UNIX workstation.

   MIPS
        Implementation runs on a MIPS RISC UNIX workstation.

   Macintosh
        Implementation runs on a Macintosh.

   Multiple Vendor Platforms
        Implementation runs on more than one hardware platform.

   Philips
        Implementation runs on a Philips platform.

   Siemens
        Implementation runs on a Siemens platform.

   Sun
        Implementation runs on a Sun platform.

   UNIX
        Implementation runs on a generic UNIX platform.

   Unisys
        Implementation runs on a Unisys platform.

   VMS
        Implementation runs under VAX/VMS.

2.2  Implementations Indexed by Keyword

   This section contains an index of implementations by keyword.  You
   can use this list to identify particular implementations that meet
   your chosen criteria.
ToP   noToC   RFC1292 - Page 7
   The index is organized as follows: keywords appear in alphabetical
   order; implementations characterized by that keyword are listed
   alphabetically as well.  Note that a "*" is used to indicate that the
   particular implementation, or feature of the implementation, may not
   be available at this time.

   For formatting purposes, we have used the following abbreviations for
   implementation names: UWisc (University of Wisconsin), HP X.500 DDS
   (HP X.500 Distributed Directory Software), IS X.500 DSA/DSAM,
   DUA(Interactive Systems' X.500 DSA/DSAM, DUA).


   3Com                                  Available via FTP

        X.500 DUA process                     DE
                                              DISH-VMS 2.0
   API                                        DIXIE
                                              Mac-ISODE
        Alliance OSI X.500                    maX.500
        Custos                                POD
        DCE/GDS                               psiwp
        DS-520, DS-521                        QUIPU
        HP X.500 DDS                          ud
        IS X.500 DSA/DSAM, DUA                VMS-ISODE
        Mac-ISODE                             Xdi
        OSI Access and Directory              XLU
        OSI-DSA
        OSI-DUA                          Bull
        QUIPU
        UCOM X.500                            UCOM X.500
        VMS-ISODE
        VTT X.500                        CLNP
        WIN/DS
                                              Cray OSI Version 2.0
   Apollo                                     DCE/GDS
                                              HP X.500 DDS
        VTT X.500                             OSI Access and Directory
                                              OSI-DSA
   Available via FTAM                         OSI-DUA
                                              QUIPU
        DE                                    VTT X.500
        DISH-VMS 2.0                          WIN/DS
        POD                                   X.500 DUA process
        QUIPU                                 Xdi
        XLU                                   XT-DUA
ToP   noToC   RFC1292 - Page 8
   Commercially Available                DSA/DUA

        Alliance OSI X.500                    Alliance OSI X.500
        Cray OSI Version 2.0                  Cray OSI Version 2.0
        DCE/GDS                               Custos
        Directory 500                         Directory 500
        DS-520, DS-521                        DS-520, DS-521
        HP X.500 DDS                          HP X.500 DDS
        IS X.500 DSA/DSAM, DUA                IS X.500 DSA/DSAM, DUA
        OSI Access and Directory              Mac-ISODE
        OSI-DSA                               OSI Access and Directory
        OSI-DUA                               QUIPU
        UCOM X.500                            UCOM X.500
        VTT X.500                             VMS-ISODE
        WIN/DS                                VTT X.500
        X.500 DUA process                     WIN/DS
        XT-DUA
        xwp [PSI]                        DUA Connectivity

   Cray                                       DE
                                              DS-521
        Cray OSI Version 2.0                  OSI Access and Directory
                                              Xdi
   DEC Ultrix
                                         DUA Light Weight Client
        DCE/GDS
        QUIPU                                 *MacDish
        UCOM X.500                            DIXIE
        *xwp [UWisc]                          maX.500
                                              psiwp
   DSA Only                                   ud

        OSI-DSA                          DUA Only

   DSA Connectivity                           DE
                                              DISH-VMS 2.0
        DS-520                                OSI-DUA
        OSI Access and Directory              POD
                                              psiwp
                                              SD
                                              X.500 DUA process
                                              Xds
                                              xdua
                                              XLU
                                              XT-DUA
                                              xwp [PSI]
ToP   noToC   RFC1292 - Page 9
   Free                                  Limited Functionality

        xwp [UWisc]                           Custos
        Custos                                *MacDish
        DE                                    POD
        DISH-VMS 2.0                          psiwp
        DIXIE                                 Xds
        Mac-ISODE                             xwp [PSI]
        maX.500
        POD                              MIPS
        psiwp
        QUIPU                                 Alliance OSI X.500
        SD                                    OSI Access and Directory
        ud                                    QUIPU
        VMS-ISODE
        Xdi                              Macintosh
        Xds
        xdua                                  Alliance OSI X.500
        XLU                                   DIXIE
                                              Mac-ISODE
   HP                                         *MacDish
                                              maX.500
        Alliance OSI X.500                    psiwp
        HP X.500 DDS                          QUIPU
        QUIPU                                 *UCOM X.500
        UCOM X.500
                                         Multiple Vendor Platforms
   IBM (Non-PC and RISC)
                                              Alliance OSI X.500
        Alliance OSI X.500                    Custos
                                              DCE/GDS
   IBM PC                                     DS-520, DS-521
                                              IS X.500 DSA/DSAM, DUA
        Alliance OSI X.500                    POD
        *UCOM X.500                           QUIPU
        *VTT X.500                            SD
        xwp [UWisc]                           UCOM X.500
                                              ud
   IBM RISC                                   VTT X.500
                                              WIN/DS
        DCE/GDS                               X.500 DUA process
        UCOM X.500                            xdua
                                              XLU
   Included In ISODE                          XT-DUA
                                              xwp [PSI]
        POD                                   xwp [UWisc]
        SD
ToP   noToC   RFC1292 - Page 10
   Needs ISODE                           RFC-1006

        Custos                                Alliance OSI X.500
        DE                                    Cray OSI Version 2.0
        DISH-VMS 2.0                          Custos
        DIXIE                                 DCE/GDS
        Mac-ISODE                             Directory 500
        *MacDish                              DISH-VMS 2.0
        POD                                   DS-520, DS-521
        psiwp                                 IS X.500 DSA/DSAM, DUA
        SD                                    Mac-ISODE
        VMS-ISODE                             OSI Access and Directory
        Xdi                                   *OSI-DSA
        Xds                                   *OSI-DUA
        xdua                                  POD
        XLU                                   QUIPU
        XT-DUA                                SD
        xwp [UWisc]                           UCOM X.500
                                              VMS-ISODE
   OSI Transport                              VTT X.500
                                              WIN/DS
        Alliance OSI X.500                    Xdi
        Cray OSI Version 2.0                  Xds
        Custos                                XLU
        DS-520, DS-521                        XT-DUA
        IS X.500 DSA/DSAM, DUA
        QUIPU                            Siemens
        WIN/DS
        XT-DUA                                *UCOM X.500

   Philips

        UCOM X.500

   Potentially Unavailable

        MacDish
ToP   noToC   RFC1292 - Page 11
   Source                                UNIX

        DCE/GDS                               Custos
        DE                                    DE
        DS-520, DS-521                        DIXIE
        Mac-ISODE                             DS-520, DS-521
        OSI-DSA                               IS X.500 DSA/DSAM, DUA
        OSI-DUA                               POD
        POD                                   QUIPU
        psiwp                                 SD
        QUIPU                                 UCOM X.500
        ud                                    ud
        VMS-ISODE                             WIN/DS
        WIN/DS                                Xdi
        Xdi                                   XLU
        Xds                                   XT-DUA
        xdua                                  xwp [PSI]
        XLU                                   xwp [UWisc]

   Sun                                   Unisys

        Alliance OSI X.500                    OSI-DSA
        Custos                                OSI-DUA
        Directory 500
        DIXIE                            VMS
        QUIPU
        UCOM X.500                            DISH-VMS 2.0
        ud                                    VMS-ISODE
        VTT X.500
        Xds                              X Window System
        xdua
        XT-DUA                                QUIPU
                                              SD
                                              WIN/DS
                                              X.500 DUA process
                                              Xdi
                                              Xds
                                              xdua
                                              XT-DUA
                                              xwp [PSI]
                                              xwp [UWisc]
ToP   noToC   RFC1292 - Page 12
   X.25

        DCE/GDS
        Directory 500
        DISH-VMS 2.0
        HP X.500 DDS
        OSI Access and Directory
        OSI-DSA
        OSI-DUA
        QUIPU
        *UCOM X.500
        VTT X.500
        WIN/DS
        X.500 DUA process
        Xdi
        XT-DUA
ToP   noToC   RFC1292 - Page 13
3.  Implementation Descriptions

   In the following pages you will find descriptions of X.500 implemen-
   tations listed in alphabetical order.  In the case of name colli-
   sions, the name of the responsible organization, in square brackets,
   has been used to distinguish the implementations.  Note that
   throughout this section, the page header reflects the name of the
   implementation, not the date of the document.  The descriptions fol-
   low a common format, as described below:

   NAME
        The name of the X.500 implementation and the name of the respon-
        sible organization.  Implementations with a registered trademark
        indicate this by appending "(tm)", e.g., GeeWhiz(tm).

   LAST MODIFIED
        The month and year within which this implementation description
        was last modified.

   KEYWORDS
        A list of the keywords defined in Section 2 that have been used
        to cross reference this implementation.

   ABSTRACT
        A brief description of the application.  This section may
        optionally contain a list of the pilot projects in which the
        application is being used.

   COMPLETENESS
        A statement of compliance with respect to the 1988 CCITT Recom-
        mendations X.500-X.521 [CCITT-88], specifically Section 9 of
        X.519, or the 1988 NIST OIW Stable Implementation Agreements
        [NIST-88].

   INTEROPERABILITY
        A list of other DUAs and DSAs with which this implementation can
        interoperate.

   PILOT CONNECTIVITY
        Describes the level of connectivity it can offer to the pilot
        directory service operational on the Internet in North America,
        and to pilots co-ordinated by the PARADISE project in Europe.
        Levels of connectivity are: Not Tested, None, DUA Connectivity,
        and DSA Connectivity.

   BUGS
        A warning on known problems and/or instructions on how to report
        bugs.
ToP   noToC   RFC1292 - Page 14
   CAVEATS AND GENERAL LIMITATIONS
        A warning about possible side effects or shortcomings, e.g., a
        feature that works on one platform but not another.

   INTERNETWORKING ENVIRONMENT
        A list of environments in which this implementation can be used,
        e.g., RFC-1006 with TCP/IP, TP0 or TP4 with X.25.

   HARDWARE PLATFORMS
        A list of hardware platforms on which this application runs, any
        additional boards or processors required, and any special sug-
        gested or required configuration options.

   SOFTWARE PLATFORMS
        A list of operating systems, window systems, databases, or
        unbundled software packages required to run this application.

   AVAILABILITY
        A statement regarding the availability of the software (free or
        commercially available), a description of how to obtain the
        software, and (optionally) a statement regarding distribution
        conditions and restrictions.
ToP   noToC   RFC1292 - Page 15
NAME

   Alliance OSI(tm) X.500
   Touch Communications Inc.

LAST MODIFIED

   July, 1991

KEYWORDS

   API, Commercially Available, DSA/DUA, HP, IBM (Non-PC and RISC),
   MIPS, Macintosh, Multiple Vendor Platforms, OSI Transport, RFC-1006,
   Sun

ABSTRACT

   Alliance OSI includes XDS (API), DUA, DSA and DIB all as separate
   components.

   Touch's X.500 products have been designed for complete portability to
   any operating system or hardware environment.  The protocols include
   DAP and DSP of the OSI X.500 specification along with the required
   XDS, DUA, DSA and DIB components.  In addition to X.500, Touch sup-
   plies other OSI protocol layers including: ROSE, ACSE, Presentation,
   Session and any of the OSI lower layers (Transport, Network along
   with RFC-1006).  Touch also supplies other application layer proto-
   cols such as X.400, FTAM, CMIP (and general network management), etc.

   The Alliance OSI X.500 is compliant with the CCITT X.500 1988 Recom-
   mendations. The ROSE/ACSE/Presentation/Session stack can be option-
   ally provided by Touch.

   The DUA may represent a single user, or may represent a group of
   users.  It may be attached to a given DSA within the same system but
   is also capable of invoking operations in Touch's or any other
   vendor's compliant DSA on a remote system.  The binding operation
   requires the user to give a distinguished name and password in order
   for the Directory to identify the user.  Once an association is esta-
   blished the user may invoke the following operations: READ, COMPARE,
   ABANDON, LIST, SEARCH, ADD_ENTRY, REMOVE_ENTRY, MODIFY_ENTRY,
   MODIFY_RDN.
ToP   noToC   RFC1292 - Page 16
   Due to the fact that access to the physical disk is in most  cases  a
   blocking  operation  (synchronous)  Touch  has separated the database
   processing (I/O process) from the DSA protocol entity.  This  separa-
   tion allows the DSA entity to continue processing during the frequent
   database accesses from the DSA. The DSA supports  all  the  Directory
   operations  as specified in the CCITT X.500 specification.  Chaining,
   Referral and Multicasting are provided and supported in the  Alliance
   OSI  DSA.   The DSA supports all the service control options included
   in the operation command arguments.  Filtering  conditions  are  sup-
   ported via the FILTER in the SEARCH operation.

   The Alliance OSI X.500 product supports all the NIST defined manda-
   tory X.500 and X.400 object classes and attributes.

   Alliance OSI X.500 supports all the mandatory Directory attribute
   types (and their associated abstract syntaxes) in the NIST Directory
   implementation profile. Touch has extended the Directory and allows
   users to define private attributes.  This means that a user can util-
   ize the Alliance OSI Directory for a general purpose, user defined
   database activity.

   Touch provides a full set of administration and Directory management
   facilities.

   Touch is in the process of integrating the X.500 product with the
   Worldtalk 400 product. Worldtalk 400 is Touch's end user X.400 mes-
   sage switch, providing gateways between proprietary mail systems
   (SMTP, Microsoft Mail, MHS, cc:mail, etc.) and X.400.  X.500 is a key
   component for a messaging network.

COMPLETENESS

   Strong Authentication is not supported however Simple Authentication
   is supported.

INTEROPERABILITY

   No interoperability testing has been completed as of yet.

PILOT CONNECTIVITY

   Numerous OEMs are using the Alliance OSI X.500 product in product
   development as well as in pilot networks.

BUGS

   N/A
ToP   noToC   RFC1292 - Page 17
CAVEATS AND GENERAL LIMITATIONS

   Currently the Alliance OSI X.500 DIB has only been validated within a
   UNIX File System.  The protocol components are portable as is the
   interface between the DSA and the DIB.

INTERNETWORKING ENVIRONMENT

   Alliance OSI X.500 can be utilized over TCP/IP and/or OSI Transport
   on LANs and WANs.  Currently X.500 has only been verified over OSI,
   however other Alliance OSI application layers have been configured
   over a RFC-1006 which is available as part of the Alliance OSI pro-
   duct line.

HARDWARE PLATFORMS

   Alliance OSI has been ported to numerous platforms ranging from IBM
   Mainframes MVS to Apple Macintosh.  For UNIX environments Touch has
   portations for 386 AT/Bus, SUN-3 and 4, Mips, and HP.

SOFTWARE PLATFORMS

   As stated above, the Alliance OSI product have been ported to
   numerous systems.  In the UNIX environment the X.500 product exists
   on SUN OS 4.0 and greater, Mips RISC OS, Interactive 386 and HP-UX.

AVAILABILITY

   Alliance OSI is commercially available from:

           Touch Communications Inc.
           250 E. Hacienda Ave
           Campbell, CA 95008
           Sales and Information: (408) 374-2500
           FAX: (408) 374-1680
ToP   noToC   RFC1292 - Page 18
NAME

   Cray OSI Version 2.0
   Cray Research Inc.

LAST MODIFIED

   July, 1991

KEYWORDS

   CLNP, Commercially Available, Cray, DSA/DUA, OSI Transport, RFC-1006

ABSTRACT

   The product is packaged with the Cray OSI product. It includes a DSA
   and DUA capable of OSI or TCP/IP connections.  The implementation is
   based on the ISODE QUIPU product.

COMPLETENESS

   Compliance with CCITT88 plus access control extensions.  Strong
   authentication not yet implemented.

INTEROPERABILITY

   Interoperates with ISODE QUIPU based implementations.

PILOT CONNECTIVITY

   The software has been operated in conjunction with the White Pages
   Pilot Project.

BUGS

   [No information provided--Ed.]

CAVEATS AND GENERAL LIMITATIONS

   See ISODE QUIPU limitations.

INTERNETWORKING ENVIRONMENT

   TCP/IP, TP4
ToP   noToC   RFC1292 - Page 19
HARDWARE PLATFORMS

   Runs on UNICOS based Cray machines with OS level 7.0 or greater.

SOFTWARE PLATFORMS

   Supported for CRAY UNICOS 7.0 or greater.

AVAILABILITY

   Commercially available via Cray Research Inc. Sales Representatives.
ToP   noToC   RFC1292 - Page 20
NAME

   Custos
   National Institute of Standards and Technology

LAST MODIFIED

   November, 1991

KEYWORDS

   API, DSA/DUA, Free, Limited Functionality, Multiple Vendor Platforms,
   Requires ISODE, OSI Transport, RFC-1006, Sun, UNIX

ABSTRACT

   The implementation consists of a set DUA library routines, a terminal
   interface, and a DSA. The implementation was developed in C on Sun 3
   workstations under the UNIX operating system. All underlying services
   are provided by the ISODE development package. The development pack-
   age is also used for encoding and decoding ASN.1 data as well as for
   other data manipulation services. Using the ISODE package the imple-
   mentation can be run over both OSI and TCP/IP protocols.

   The DSA provides full support for both DAP and DSP protocols, confor-
   mant with ISO 9594/CCITT X.500 standards. The DIB is maintained using
   a locally developed relational database system. The interface to the
   database system consists of a set of SQL-like C functions.  These are
   designed to allow straightforward replacement of the local database
   system with a more powerful commercial system. To achieve better per-
   formance several options are supported that permit loading of
   selected portions of the database into core. When these options are
   selected data can be retrieved more quickly from in-core tables; all
   modifications to the DIB are directly reflected in the in-core tables
   and the database.

COMPLETENESS

   To date the Read, Compare, List, Add Entry, and Remove Entry opera-
   tions have been implemented and are supported over both DAP and DSP;
   aliasing and replication are also supported.  The version under
   current development (available January '92) includes simple authenti-
   cation, access control, and the Search operation. The modify opera-
   tions and Abandon are not supported and there is no support for
   schema checking.
ToP   noToC   RFC1292 - Page 21
INTEROPERABILITY

   Have successfully interoperated with QUIPU and OSIWARE over the DAP.
   No DSP interoperability testing has been done.

PILOT CONNECTIVITY

   Not tested.

BUGS

   Some testing in the near term future will be done to try to identify
   these, but presently it's not possible to give an accurate list of
   bugs.

CAVEATS AND GENERAL LIMITATIONS

   No limitations on file sizes, etc. The only side effects to creating
   large files should be in the area of performance. Specifically,
   optimization requires loading parts of the DIB in core so greater
   memory requirements will be necessary for achieving better perfor-
   mance with a large database.  Any platform the implementation can be
   ported to (generally any platform ISODE can be ported to) should sup-
   port all features.

INTERNETWORKING ENVIRONMENT

   RFC-1006; TP4/CLNP (SunLink OSI) over 802 and X.25 (SunLink X.25).

HARDWARE PLATFORMS

   It has been run on Sun-3, but there are no known reasons why it
   should not run on any hardware running the ISODE software.

SOFTWARE PLATFORMS

   It requires UNIX and the ISODE software package.  It's been developed
   and tested with ISODE version 6.0 and Sun OS version 4.1.1.  Uses a
   locally developed relational DBMS that should be easily replaceable
   with commercially available relational systems.

AVAILABILITY

   While under continuing development, availability of the implementa-
   tion is limited to organizations making appropriate arrangements with
   NIST.  The implementation will be publicly available when development
   is completed.
ToP   noToC   RFC1292 - Page 22
NAME

   DCE/GDS (tm)
   Open Software Foundation, Inc.

LAST MODIFIED

   July, 1991

KEYWORDS

   API, CLNP, Commercially Available, DEC Ultrix, DSA/DUA, IBM RISC,
   Multiple Vendor Platforms, RFC-1006, Source, X.25

ABSTRACT

   DCE/GDS (Distributed Computing Environment/Global Directory Service)
   was based on the original Siemens DIR.X product. It supports full DUA
   and DSA functions for globally unique identifications and for loca-
   tion of objects in the network. It also provides functions to answer
   queries (both yellow-page and white-page) about objects and attribute
   information.  The software implements full DAP and DSP protocols
   specified in X.519.  An ASN.1 compiler and required ACSE, ROSE,
   presentation, session and RFC-1006 protocols implementations are also
   included.

   The product has been successfully participated in X.500 Cebit Intero-
   perability tests at 1990 and 1991 Hanover Fairs. It also intero-
   perates with the ISODE QUIPU X.500 implementation.

COMPLETENESS

   Compliant with EWOS Agreements which is being harmonized with OIW
   Agreements.

   Strong authentication in X.509 is not yet implemented. (Password
   scheme is currently used.)

   Consists of both DUA and DSA implementation according to the 88 CCITT
   X.500 and ISO 9594 standard.  The X/Open standard XDS (version 1.0)
   and XOM (version 2.0) interface libraries are also provided.  XDS and
   XOM interfaces are also used to access DCE/CDS (Local Cell Directory
   Service) transparently. A GDA (Global Directory Agent) serves as the
   gateway between the DCE CDS and GDS.
ToP   noToC   RFC1292 - Page 23
INTEROPERABILITY

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

PILOT CONNECTIVITY

   [No information provided--Ed.]

BUGS

   Problems and bug report email address: dce-defect@osf.org.

CAVEATS AND GENERAL LIMITATIONS

   The software is highly portable without general limitations.

INTERNETWORKING ENVIRONMENT

   OSI TP4 with CLNP
   OSI TP0, 2 & 4 with X.25
   RFC-1006 with TCP/IP

HARDWARE PLATFORMS

   DCE/GDS runs on SNI's hardware platforms and is being ported to run
   on IBM RS6000, Digital DECstation, etc.

SOFTWARE PLATFORMS

   SINIX (UNIX System V Release 4)
   Currently being ported: OSF/1.1, AIX 3.1, Ultrix, etc.
   DCE/GDS can use either BSD sockets or XTI/TLI to access the transports.

AVAILABILITY

   The source code license of DCE/GDS is commercially available from:

           Open Software Foundation, Inc.
           11 Cambridge Center
           Cambridge, MA 02142
ToP   noToC   RFC1292 - Page 24
   Please contact:

           Jon Gossels
           Tel: 617-621-8763
           Fax: 617-621-0631
           e-mail: gossels@osf.org
ToP   noToC   RFC1292 - Page 25
NAME

   DE
   COSINE PARADISE

LAST MODIFIED

   November, 1991

KEYWORDS

   Available via FTAM, Available via FTP, DUA Connectivity, DUA Only,
   Free, Included in ISODE, Limited Functionality, Needs ISODE, Source,
   UNIX

ABSTRACT

   DE (Directory Enquiries) is intended to be a simple-to-use interface,
   suitable for the naive user, and suitable for running as a public
   access dua to provide lowest common denominator access to the Direc-
   tory.  It is a scrolling interface and will thus run on dumb termi-
   nals, even teletypes!  The user is asked to fill in up to 4 questions
   per query: person's name; department; organization; country.  The
   prompts are very verbose -- the intention is that the user should not
   be able get stuck, and information on how to get into the help system
   should always be on the screen.  The help screens (of which there are
   15) are aimed at the non-technical user.  Whilst the outwards appear-
   ance of the interface is simple, a lot of attention has being given
   to mapping the strings the user enters onto X.500 operations in such
   a way that the interface seems to do the "right thing".  An important
   characteristic is the way the interface tries a series of searches,
   gradually relaxing the matching criteria from exact (in some sense),
   to good, through to "fuzzy".  A considerable amount of configuration
   is possible to present the results in locally acceptable formats.

   DE was funded by the COSINE PARADISE project, and DE is used as the
   PARADISE public access dua.  You can test the software by telnet to
   128.86.8.56 and logging in as dua -- no password required.

COMPLETENESS

   The interface is a querying engine only.

INTEROPERABILITY

   DE is built with the ISODE software (release 7.0).  Its interopera-
   bility relies on the correctness of the Quipu libraries.
ToP   noToC   RFC1292 - Page 26
PILOT CONNECTIVITY

   The interface is in use as the COSINE Central DUA Service, and is
   used by a number of UK institutions as a public access dua (usually
   over X.29).  It is able to query entries in pilots throughout the
   world.  It is not able to query for entries which are in organiza-
   tions beneath locality entries under country entries.  It is not pos-
   sible to query for people who do not work for organizations.  The
   interface only searches for entries of the following type: organiza-
   tions, organizational units, people, roles, and rooms.

BUGS

   Send bug reports to:

           p.barker@cs.ucl.ac.uk
           helpdesk@paradise.ulcc.ac.uk

CAVEATS AND GENERAL LIMITATIONS

   DE tries to cater well for the general case, at the expense of not
   dealing with the less typical.  The main manifestation of this is
   that the current version will not query under localities immediately
   under the country level.

   It is not possible to display photographs or reproduce sound attri-
   butes.

INTERNETWORKING ENVIRONMENT

   Same as ISODE.  ISODE supports TCP/IP, TP0, and X.25.

HARDWARE PLATFORMS

   Should be the same as ISODE in general.

SOFTWARE PLATFORMS

   DE requires the ISODE (current release 7.0) libraries.

AVAILABILITY

   DE is openly available as part of ISODE and as part of the COSINE DUA
   package.   Available by FTAM and FTP, source code freely available.
ToP   noToC   RFC1292 - Page 27
NAME

   Directory 500(tm)
   OSIware Inc.

LAST MODIFIED

   July, 1991

KEYWORDS

   Commercially Available, DSA/DUA, RFC-1006, Sun, X.25

ABSTRACT

   Full implementation of the X.500 recommendations.  Includes DUA, DSA
   & various utilities. Written in ANSI-C / C, and runs on the Unix sys-
   tem.

COMPLETENESS

   All DAP and DSP operations implemented.  Strong authentication not
   yet implemented.  Schema contains all of X.520, X.521, QUIPU & NYSER-
   Net definitions.

INTEROPERABILITY

   Interworks with QUIPU, Nist, Retix, ICL, Nixdorf.

BUGS

   None

CAVEATS AND GENERAL LIMITATIONS

   None

INTERNETWORKING ENVIRONMENT

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

HARDWARE PLATFORMS

   Runs on Sun-3, Sun-4
ToP   noToC   RFC1292 - Page 28
SOFTWARE PLATFORMS

   For SunOS 4.X with Sunlink X.25 6.0

AVAILABILITY

   Commercially available from:

           OSIware Inc.                            Tel: +1-604-436-2922
           4370 Dominion Street, Suite 200         Fax: +1-604-436-3192
           Burnaby, B, Canada V5G 4L7
ToP   noToC   RFC1292 - Page 29
NAME

   DISH-VMS 2.0
   ACIDO Project

LAST MODIFIED

   July, 1991

KEYWORDS

   Available via FTAM, Available via FTP, DUA Only, Free, Needs ISODE,
   RFC-1006, VMS, X.25

ABSTRACT

   This Directory User Agent interface was ported to the VMS operating
   system using ISODE 6.0. It is part of the results of collaboration
   project called ACIDO, between RedIRIS (national network R & D in
   Spain) and the "Facultad de Informatica de Barcelona (Universidad
   Politecnica de Cataluna)".  The main objective of this development
   was to provide access to the directory to all those affiliated cen-
   tres to the Spanish National R & D network using VMS machines. Any
   other use of this software it is no within RedIRIS objectives and
   therefore it is not RedIRIS responsibility.

COMPLETENESS

   The same as DUA (QUIPU 6.1).

INTEROPERABILITY

   QUIPU 6.1

PILOT CONNECTIVITY

   Used in RedIRIS Directory Pilot Project to access the DSAs (QUIPU).

BUGS

   You can report bugs to: isode@fib.upc.es

CAVEATS AND GENERAL LIMITATIONS

   The interface is equivalent to the UNIX one except for the option
   -pipe which is not supported.


(next page on part 2)

Next Section