As per Relevance of the word available, we have this rfc below:
Network Working Group R.
Request for Comments: 1292 SRI
FYI: 11 R.
Lawrence Berkeley
January 1992
A Catalog of Available X.500
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard. Distribution of this memo
unlimited
The goal of this document is to provide information regarding
availability and capability of implementations of X.500.
and critiques of this document, and new or updated descriptions
X.500 implementations are welcome. Send them to the
Information Services Infrastructure (DISI) Working
(disi@merit.edu) or to the editors
1.
This document catalogs currently available implementations of X.500,
including commercial products and openly available offerings.
contains descriptions of Directory System Agents (DSA),
User Agents (DUA), and DUA client applications. The latter
include such applications as browsers, DSA management tools,
lightweight DUAs that employ an application-level protocol
communicate with a DUA (which then in turn communicates with a DSA
to support user service. Section 2 of this document contains
listing of implementations cross referenced by keyword. This
will aid in identifying particular implementations that meet
criteria
To compile this catalog, the DISI Working Group solicited input
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
DISI Working Group [Page 1]
RFC 1292 X.500 Catalog January 1992
Readers are encouraged to submit comments regarding both the form
content of this memo. New submissions are always welcome.
direct input to the parties as described in the Status of this
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
The growth of existing X.500 pilot activities (e.g., White
Pilot Project) and the advent of new pilots (e.g., ARRNet
Services Project, NIST/GSA Pilot Project) are signals that X.500 is
viable directory service mechanism for the Internet community.
goal of DISI is to enable the continued growth of X.500 by
the lack-of-information barrier. This document takes one step
that goal by providing an easily accessible source of information
X.500 implementations
1.2
This document contains descriptions of either commercially or
available X.500 implementations. It does not provide instructions
how to install, run, or manage these implementations. Because
needs and computing environments of each organization differ vastly
no recommendations are given. The descriptions and indices
provided to make the readers aware of existing options and to
more informed choices
1.3
Implementation descriptions were written by implementors and vendors
and not by the members of DISI. Although DISI has worked with
description authors to ensure readability, no guarantees can be
regarding the validity of descriptions or the value of
implementations. Caveat emptor
1.4
Section 1 contains introductory information
Section 2 contains a list of keywords, their definitions, and a
reference of the X.500 implementations by these keywords
Section 3 contains the X.500 implementation descriptions
Section 4 lists the editors' addresses
DISI Working Group [Page 2]
RFC 1292 X.500 Catalog January 1992
1.5
The creation of this catalog would not have been possible without
efforts of the description authors and the members of the
Working Group. The editors thank you for your hard work
constructive feedback. A special thanks is also extended to
members of the NOCTools Working Group. The "Network Management
Catalog" (RFC-1147) served as a valuable example. Bob Stine and
Enger made key suggestions that enabled us to learn from
experiences
The efforts of the editors were sponsored by Defense
Research Projects Agency Contract Number DACA76-89-D-0002 (
Operational X.500 Project), and U. S. Department of Energy
Number DE-AC03-76SF00098.
2.
Keywords are abbreviated attributes of the X.500 implementations
The list of keywords defined below was derived from
implementation descriptions themselves. Implementations were
by a keyword either as a result of: 1) explicit, not implied
reference to a particular capability in the
description text, or 2) input from the implementation
author(s).
2.1 Keyword
This section contains keyword definitions. They have been
and grouped by functional category. The definitions are
first alphabetically by keyword category, and second
by implementation name within keyword category
2.1.1
Available via
Implementation is available using FTAM
Available via
Implementation is available using FTP
Commercially
This implementation can be purchased
Available at no charge, although other restrictions may apply
DISI Working Group [Page 3]
RFC 1292 X.500 Catalog January 1992
Potentially
Implementation was not available at the time this document
written
Source code is available, potentially at an additional cost
2.1.2 Implementation
Implementation comes with an application programmer's
(i.e., a set of libraries and include files).
DSA
Implementation consists of a DSA only. No DUA is included
DSA/
Both a DSA and DUA are included in this implementation
DUA Light Weight
Implementation is a DUA-like program that uses a non-OSI proto
col to satisfy X.500 requests
DUA
Implementation consists of a DUA only. No DSA is included
2.1.3 Internetworking
Implementation uses OSI CLNP
OSI
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.
DISI Working Group [Page 4]
RFC 1292 X.500 Catalog January 1992
2.1.4 Pilot
DUA
The DUA can be connected to the pilot, and information on
pilot entry looked up. The DUA is able to display
attributes and object classes and those defined in the
and Internet Schema
DSA
The DSA is connected to the DIT, and information in this DSA
accessible from any pilot DUA
2.1.5
Included in
DUAs that are part of ISODE
Limited
Survey states that the implementation has some shortcomings
intended lack of functionality, e.g., omissions were part of
design to provide an easy-to-use user interface
Needs
ISODE is required to compile and/or use this implementation
X Window
Implementation uses the X Window System to provide its
interface
2.1.5 Operating
3
Implementation runs on a 3Com platform
Implementation runs on an Apollo platform
Implementation runs on a Bull platform
Implementation runs on a Cray
DISI Working Group [Page 5]
RFC 1292 X.500 Catalog January 1992
DEC
Implementation runs under DEC Ultrix
Implementation runs on an HP platform
IBM (Non-PC and RISC
Implementation runs on some type of IBM, which is not a PC
UNIX workstation
IBM
Implementation runs on a PC
IBM
Implementation runs on IBM's RISC UNIX workstation
Implementation runs on a MIPS RISC UNIX workstation
Implementation runs on a Macintosh
Multiple Vendor
Implementation runs on more than one hardware platform
Implementation runs on a Philips platform
Implementation runs on a Siemens platform
Implementation runs on a Sun platform
Implementation runs on a generic UNIX platform
Implementation runs on a Unisys platform
Implementation runs under VAX/VMS
2.2 Implementations Indexed by
This section contains an index of implementations by keyword.
can use this list to identify particular implementations that
your chosen criteria
DISI Working Group [Page 6]
RFC 1292 X.500 Catalog January 1992
The index is organized as follows: keywords appear in
order; implementations characterized by that keyword are
alphabetically as well. Note that a "*" is used to indicate that
particular implementation, or feature of the implementation, may
be available at this time
For formatting purposes, we have used the following abbreviations
implementation names: UWisc (University of Wisconsin), HP X.500
(HP X.500 Distributed Directory Software), IS X.500 DSA/DSAM
DUA(Interactive Systems' X.500 DSA/DSAM, DUA).
3Com Available via
X.500 DUA process
DISH-VMS 2.0
API
Mac-
Alliance OSI X.500 maX.500
Custos
DCE/GDS
DS-520, DS-521
HP X.500 DDS
IS X.500 DSA/DSAM, DUA VMS-
Mac-ISODE
OSI Access and Directory
OSI-
OSI-DUA
UCOM X.500 UCOM X.500
VMS-
VTT X.500
WIN/
Cray OSI Version 2.0
Apollo DCE/
HP X.500
VTT X.500 OSI Access and
OSI-
Available via FTAM OSI-
DE VTT X.500
DISH-VMS 2.0 WIN/
POD X.500 DUA
QUIPU
XLU XT-
DISI Working Group [Page 7]
RFC 1292 X.500 Catalog January 1992
Commercially Available DSA/
Alliance OSI X.500 Alliance OSI X.500
Cray OSI Version 2.0 Cray OSI Version 2.0
DCE/GDS
Directory 500 Directory 500
DS-520, DS-521 DS-520, DS-521
HP X.500 DDS HP X.500
IS X.500 DSA/DSAM, DUA IS X.500 DSA/DSAM,
OSI Access and Directory Mac-
OSI-DSA OSI Access and
OSI-DUA
UCOM X.500 UCOM X.500
VTT X.500 VMS-
WIN/DS VTT X.500
X.500 DUA process WIN/
XT-
xwp [PSI] DUA
Cray
DS-521
Cray OSI Version 2.0 OSI Access and
DEC
DUA Light Weight
DCE/
QUIPU *
UCOM X.500
*xwp [UWisc] maX.500
DSA Only
OSI-DSA DUA
DSA Connectivity
DISH-VMS 2.0
DS-520 OSI-
OSI Access and Directory
X.500 DUA
XT-
xwp [PSI
DISI Working Group [Page 8]
RFC 1292 X.500 Catalog January 1992
Free Limited
xwp [UWisc]
Custos *
DE
DISH-VMS 2.0
DIXIE
Mac-ISODE xwp [PSI
maX.500
POD
QUIPU Alliance OSI X.500
SD OSI Access and
ud
VMS-
Xdi
xdua Alliance OSI X.500
XLU
Mac-
HP *
maX.500
Alliance OSI X.500
HP X.500 DDS
QUIPU *UCOM X.500
UCOM X.500
Multiple Vendor
IBM (Non-PC and RISC
Alliance OSI X.500
Alliance OSI X.500
DCE/
IBM PC DS-520, DS-521
IS X.500 DSA/DSAM,
Alliance OSI X.500
*UCOM X.500
*VTT X.500
xwp [UWisc] UCOM X.500
IBM RISC VTT X.500
WIN/
DCE/GDS X.500 DUA
UCOM X.500
Included In ISODE XT-
xwp [PSI
POD xwp [UWisc
DISI Working Group [Page 9]
RFC 1292 X.500 Catalog January 1992
Needs ISODE RFC-1006
Custos Alliance OSI X.500
DE Cray OSI Version 2.0
DISH-VMS 2.0
DIXIE DCE/
Mac-ISODE Directory 500
*MacDish DISH-VMS 2.0
POD DS-520, DS-521
psiwp IS X.500 DSA/DSAM,
SD Mac-
VMS-ISODE OSI Access and
Xdi *OSI-
Xds *OSI-
xdua
XLU
XT-DUA
xwp [UWisc] UCOM X.500
VMS-
OSI Transport VTT X.500
WIN/
Alliance OSI X.500
Cray OSI Version 2.0
Custos
DS-520, DS-521 XT-
IS X.500 DSA/DSAM,
QUIPU
WIN/
XT-DUA *UCOM X.500
UCOM X.500
Potentially
DISI Working Group [Page 10]
RFC 1292 X.500 Catalog January 1992
Source
DCE/GDS
DE
DS-520, DS-521
Mac-ISODE DS-520, DS-521
OSI-DSA IS X.500 DSA/DSAM,
OSI-DUA
POD
psiwp
QUIPU UCOM X.500
ud
VMS-ISODE WIN/
WIN/DS
Xdi
Xds XT-
xdua xwp [PSI
XLU xwp [UWisc
Sun
Alliance OSI X.500 OSI-
Custos OSI-
Directory 500
DIXIE
UCOM X.500 DISH-VMS 2.0
ud VMS-
VTT X.500
Xds X Window
XT-DUA
WIN/
X.500 DUA
XT-
xwp [PSI
xwp [UWisc
DISI Working Group [Page 11]
RFC 1292 X.500 Catalog January 1992
X.25
DCE/
Directory 500
DISH-VMS 2.0
HP X.500
OSI Access and
OSI-
OSI-
*UCOM X.500
VTT X.500
WIN/
X.500 DUA
XT-
DISI Working Group [Page 12]
RFC 1292 X.500 Catalog January 1992
3. Implementation
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
throughout this section, the page header reflects the name of
implementation, not the date of the document. The descriptions fol
low a common format, as described below
The name of the X.500 implementation and the name of the respon
sible organization. Implementations with a registered
indicate this by appending "(tm)", e.g., GeeWhiz(tm).
LAST
The month and year within which this implementation
was last modified
A list of the keywords defined in Section 2 that have been
to cross reference this implementation
A brief description of the application. This section
optionally contain a list of the pilot projects in which
application is being used
A statement of compliance with respect to the 1988 CCITT Recom
mendations X.500-X.521 [CCITT-88], specifically Section 9
X.519, or the 1988 NIST OIW Stable Implementation
[NIST-88].
A list of other DUAs and DSAs with which this implementation
interoperate
PILOT
Describes the level of connectivity it can offer to the
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
A warning on known problems and/or instructions on how to
bugs
DISI Working Group [Page 13]
RFC 1292 X.500 Catalog January 1992
CAVEATS AND GENERAL
A warning about possible side effects or shortcomings, e.g.,
feature that works on one platform but not another
INTERNETWORKING
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
A list of hardware platforms on which this application runs,
additional boards or processors required, and any special sug
gested or required configuration options
SOFTWARE
A list of operating systems, window systems, databases,
unbundled software packages required to run this application
A statement regarding the availability of the software (free
commercially available), a description of how to obtain
software, and (optionally) a statement regarding
conditions and restrictions
DISI Working Group [Page 14]
RFC 1292 Alliance OSI X.500 January 1992
Alliance OSI(tm) X.500
Touch Communications Inc
LAST
July, 1991
API, Commercially Available, DSA/DUA, HP, IBM (Non-PC and RISC),
MIPS, Macintosh, Multiple Vendor Platforms, OSI Transport, RFC-1006,
Alliance OSI includes XDS (API), DUA, DSA and DIB all as
components
Touch's X.500 products have been designed for complete portability
any operating system or hardware environment. The protocols
DAP and DSP of the OSI X.500 specification along with the
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
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
users. It may be attached to a given DSA within the same system
is also capable of invoking operations in Touch's or any
vendor's compliant DSA on a remote system. The binding
requires the user to give a distinguished name and password in
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
DISI Working Group [Page 15]
RFC 1292 Alliance OSI X.500 January 1992
Due to the fact that access to the physical disk is in most cases
blocking operation (synchronous) Touch has separated the
processing (I/O process) from the DSA protocol entity. This separa
tion allows the DSA entity to continue processing during the
database accesses from the DSA. The DSA supports all the
operations as specified in the CCITT X.500 specification. Chaining
Referral and Multicasting are provided and supported in the
OSI DSA. The DSA supports all the service control options
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
types (and their associated abstract syntaxes) in the NIST
implementation profile. Touch has extended the Directory and
users to define private attributes. This means that a user can util
ize the Alliance OSI Directory for a general purpose, user
database activity
Touch provides a full set of administration and Directory
facilities
Touch is in the process of integrating the X.500 product with
Worldtalk 400 product. Worldtalk 400 is Touch's end user X.400 mes
sage switch, providing gateways between proprietary mail
(SMTP, Microsoft Mail, MHS, cc:mail, etc.) and X.400. X.500 is a
component for a messaging network
Strong Authentication is not supported however Simple
is supported
No interoperability testing has been completed as of yet
PILOT
Numerous OEMs are using the Alliance OSI X.500 product in
development as well as in pilot networks
N/
DISI Working Group [Page 16]
RFC 1292 Alliance OSI X.500 January 1992
CAVEATS AND GENERAL
Currently the Alliance OSI X.500 DIB has only been validated within
UNIX File System. The protocol components are portable as is
interface between the DSA and the DIB
INTERNETWORKING
Alliance OSI X.500 can be utilized over TCP/IP and/or OSI
on LANs and WANs. Currently X.500 has only been verified over OSI
however other Alliance OSI application layers have been
over a RFC-1006 which is available as part of the Alliance OSI pro
duct line
HARDWARE
Alliance OSI has been ported to numerous platforms ranging from
Mainframes MVS to Apple Macintosh. For UNIX environments Touch
portations for 386 AT/Bus, SUN-3 and 4, Mips, and HP
SOFTWARE
As stated above, the Alliance OSI product have been ported
numerous systems. In the UNIX environment the X.500 product
on SUN OS 4.0 and greater, Mips RISC OS, Interactive 386 and HP-UX
Alliance OSI is commercially available from
Touch Communications Inc
250 E. Hacienda
Campbell, CA 95008
Sales and Information: (408) 374-2500
FAX: (408) 374-1680
DISI Working Group [Page 17]
RFC 1292 Cray OSI Version 2.0 January 1992
Cray OSI Version 2.0
Cray Research Inc
LAST
July, 1991
CLNP, Commercially Available, Cray, DSA/DUA, OSI Transport, RFC-1006
The product is packaged with the Cray OSI product. It includes a
and DUA capable of OSI or TCP/IP connections. The implementation
based on the ISODE QUIPU product
Compliance with CCITT88 plus access control extensions.
authentication not yet implemented
Interoperates with ISODE QUIPU based implementations
PILOT
The software has been operated in conjunction with the White
Pilot Project
[No information provided--Ed.]
CAVEATS AND GENERAL
See ISODE QUIPU limitations
INTERNETWORKING
TCP/IP, TP
DISI Working Group [Page 18]
RFC 1292 Cray OSI Version 2.0 January 1992
HARDWARE
Runs on UNICOS based Cray machines with OS level 7.0 or greater
SOFTWARE
Supported for CRAY UNICOS 7.0 or greater
Commercially available via Cray Research Inc. Sales Representatives
DISI Working Group [Page 19]
RFC 1292 Custos January 1992
National Institute of Standards and
LAST
November, 1991
API, DSA/DUA, Free, Limited Functionality, Multiple Vendor Platforms
Requires ISODE, OSI Transport, RFC-1006, Sun,
The implementation consists of a set DUA library routines, a
interface, and a DSA. The implementation was developed in C on Sun 3
workstations under the UNIX operating system. All underlying
are provided by the ISODE development package. The development pack
age is also used for encoding and decoding ASN.1 data as well as
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
a locally developed relational database system. The interface to
database system consists of a set of SQL-like C functions. These
designed to allow straightforward replacement of the local
system with a more powerful commercial system. To achieve better per
formance several options are supported that permit loading
selected portions of the database into core. When these options
selected data can be retrieved more quickly from in-core tables;
modifications to the DIB are directly reflected in the in-core
and the database
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
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
schema checking
DISI Working Group [Page 20]
RFC 1292 Custos January 1992
Have successfully interoperated with QUIPU and OSIWARE over the DAP
No DSP interoperability testing has been done
PILOT
Not tested
Some testing in the near term future will be done to try to
these, but presently it's not possible to give an accurate list
bugs
CAVEATS AND GENERAL
No limitations on file sizes, etc. The only side effects to
large files should be in the area of performance. Specifically
optimization requires loading parts of the DIB in core so
memory requirements will be necessary for achieving better perfor
mance with a large database. Any platform the implementation can
ported to (generally any platform ISODE can be ported to) should sup
port all features
INTERNETWORKING
RFC-1006; TP4/CLNP (SunLink OSI) over 802 and X.25 (SunLink X.25).
HARDWARE
It has been run on Sun-3, but there are no known reasons why
should not run on any hardware running the ISODE software
SOFTWARE
It requires UNIX and the ISODE software package. It's been
and tested with ISODE version 6.0 and Sun OS version 4.1.1. Uses
locally developed relational DBMS that should be easily
with commercially available relational systems
While under continuing development, availability of the implementa
tion is limited to organizations making appropriate arrangements
NIST. The implementation will be publicly available when
is completed
DISI Working Group [Page 21]
RFC 1292 DCE/GDS January 1992
DCE/GDS (tm
Open Software Foundation, Inc
LAST
July, 1991
API, CLNP, Commercially Available, DEC Ultrix, DSA/DUA, IBM RISC
Multiple Vendor Platforms, RFC-1006, Source, X.25
DCE/GDS (Distributed Computing Environment/Global Directory Service
was based on the original Siemens DIR.X product. It supports full
and DSA functions for globally unique identifications and for loca
tion of objects in the network. It also provides functions to
queries (both yellow-page and white-page) about objects and
information. The software implements full DAP and DSP
specified in X.519. An ASN.1 compiler and required ACSE, ROSE
presentation, session and RFC-1006 protocols implementations are
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
Compliant with EWOS Agreements which is being harmonized with
Agreements
Strong authentication in X.509 is not yet implemented. (
scheme is currently used.)
Consists of both DUA and DSA implementation according to the 88
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
XOM interfaces are also used to access DCE/CDS (Local Cell
Service) transparently. A GDA (Global Directory Agent) serves as
gateway between the DCE CDS and GDS
DISI Working Group [Page 22]
RFC 1292 DCE/GDS January 1992
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
[No information provided--Ed.]
Problems and bug report email address: dce-defect@osf.org
CAVEATS AND GENERAL
The software is highly portable without general limitations
INTERNETWORKING
OSI TP4 with
OSI TP0, 2 & 4 with X.25
RFC-1006 with TCP/
HARDWARE
DCE/GDS runs on SNI's hardware platforms and is being ported to
on IBM RS6000, Digital DECstation, etc
SOFTWARE
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
The source code license of DCE/GDS is commercially available from
Open Software Foundation, Inc
11 Cambridge
Cambridge, MA 02142
DISI Working Group [Page 23]
RFC 1292 DCE/GDS January 1992
Please contact
Jon
Tel: 617-621-8763
Fax: 617-621-0631
e-mail: gossels@osf.
DISI Working Group [Page 24]
RFC 1292 DE January 1992
COSINE
LAST
November, 1991
Available via FTAM, Available via FTP, DUA Connectivity, DUA Only
Free, Included in ISODE, Limited Functionality, Needs ISODE, Source
DE (Directory Enquiries) is intended to be a simple-to-use interface
suitable for the naive user, and suitable for running as a
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
per query: person's name; department; organization; country.
prompts are very verbose -- the intention is that the user should
be able get stuck, and information on how to get into the help
should always be on the screen. The help screens (of which there
15) are aimed at the non-technical user. Whilst the outwards appear
ance of the interface is simple, a lot of attention has being
to mapping the strings the user enters onto X.500 operations in
a way that the interface seems to do the "right thing". An
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
is possible to present the results in locally acceptable formats
DE was funded by the COSINE PARADISE project, and DE is used as
PARADISE public access dua. You can test the software by telnet
128.86.8.56 and logging in as dua -- no password required
The interface is a querying engine only
DE is built with the ISODE software (release 7.0). Its interopera
bility relies on the correctness of the Quipu libraries
DISI Working Group [Page 25]
RFC 1292 DE January 1992
PILOT
The interface is in use as the COSINE Central DUA Service, and
used by a number of UK institutions as a public access dua (
over X.29). It is able to query entries in pilots throughout
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.
interface only searches for entries of the following type: organiza
tions, organizational units, people, roles, and rooms
Send bug reports to
p.barker@cs.ucl.ac.
helpdesk@paradise.ulcc.ac.
CAVEATS AND GENERAL
DE tries to cater well for the general case, at the expense of
dealing with the less typical. The main manifestation of this
that the current version will not query under localities
under the country level
It is not possible to display photographs or reproduce sound attri
butes
INTERNETWORKING
Same as ISODE. ISODE supports TCP/IP, TP0, and X.25.
HARDWARE
Should be the same as ISODE in general
SOFTWARE
DE requires the ISODE (current release 7.0) libraries
DE is openly available as part of ISODE and as part of the COSINE
package. Available by FTAM and FTP, source code freely available
DISI Working Group [Page 26]
RFC 1292 Directory 500 January 1992
Directory 500(tm
OSIware Inc
LAST
July, 1991
Commercially Available, DSA/DUA, RFC-1006, Sun, X.25
Full implementation of the X.500 recommendations. Includes DUA,
& various utilities. Written in ANSI-C / C, and runs on the Unix sys
tem
All DAP and DSP operations implemented. Strong authentication
yet implemented. Schema contains all of X.520, X.521, QUIPU & NYSER
Net definitions
Interworks with QUIPU, Nist, Retix, ICL, Nixdorf
CAVEATS AND GENERAL
INTERNETWORKING
RFC-1006 with TCP/
TP0 with X.25
HARDWARE
Runs on Sun-3, Sun-4
DISI Working Group [Page 27]
RFC 1292 Directory 500 January 1992
SOFTWARE
For SunOS 4.X with Sunlink X.25 6.0
Commercially available from
OSIware Inc. Tel: +1-604-436-2922
4370 Dominion Street, Suite 200 Fax: +1-604-436-3192
Burnaby, B, Canada V5G 4L
DISI Working Group [Page 28]
RFC 1292 DISH-VMS 2.0 January 1992
DISH-VMS 2.0
ACIDO
LAST
July, 1991
Available via FTAM, Available via FTP, DUA Only, Free, Needs ISODE
RFC-1006, VMS, X.25
This Directory User Agent interface was ported to the VMS
system using ISODE 6.0. It is part of the results of
project called ACIDO, between RedIRIS (national network R & D
Spain) and the "Facultad de Informatica de Barcelona (
Politecnica de Cataluna)". The main objective of this
was to provide access to the directory to all those affiliated cen
tres to the Spanish National R & D network using VMS machines.
other use of this software it is no within RedIRIS objectives
therefore it is not RedIRIS responsibility
The same as DUA (QUIPU 6.1).
QUIPU 6.1
PILOT
Used in RedIRIS Directory Pilot Project to access the DSAs (QUIPU).
You can report bugs to: isode@fib.upc.
CAVEATS AND GENERAL
The interface is equivalent to the UNIX one except for the
-pipe which is not supported
DISI Working Group [Page 29]
RFC 1292 DISH-VMS 2.0 January 1992
The users can have a quipurc file to configure their work environ
ments with DISH. This file should reside at the SYS$LOGIN
of the user and it should be called "quipurc." (in UNIX it's
.quipurc
INTERNETWORKING
RFC-1006 with TCP/IP, TP0 with X.25
HARDWARE
SOFTWARE
VAX/VMS 5.3
VAX PSI 4.2
VMS/ULTRIX Connection 1.2
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
TSEL= <0103>
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
DISI Working Group [Page 30]
RFC 1292 DIXIE January 1992
University of
LAST
November, 1991
Available via FTP, DUA Light Weight Client, Free, Source, UNIX, Mul
tiple Vendor Platform, Needs
The DIXIE protocol is used to give X.500 access to platforms
have only TCP/IP access. The DIXIE server is an intermediate proto
col server that communicates with Internet clients on one side
a text-based UDP/TCP protocol and an X.500 DSA on the other
using DAP. The protocol is fully described in RFC 1246. A subset
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-
routines
The DIXIE protocol and server are being used by the
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
same place as the DIXIE server
Network monitoring of DSAs by our Network Operations
Lookup and display of caller identification based on
caller ID (using ISDN).
The DIXIE protocol does not support access to all X.500 features
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
of the service controls are supported
DISI Working Group [Page 31]
RFC 1292 DIXIE January 1992
The current implementation of the DIXIE server works with the
DSA and DAP library
PILOT
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
There are no known outstanding bugs. But reports should be sent
x500@umich.edu
CAVEATS AND GENERAL
None, aside from those mentioned above under completeness
INTERNETWORKING
DIXIE clients use TCP or UDP to communicate with the DIXIE server
The DIXIE server uses RFC-1006 with TCP/IP to communicate with
DSA, though other transport mechanisms for DSA communication
be possible
HARDWARE
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
known to run on the same platforms, and also on the Macintosh
SOFTWARE
The DIXIE server and library is known to run under SunOS 3.5,
4.1.1, Ultrix 4.1 and 4.2. The DIXIE library also runs on the Macin
tosh System Software 6 or later
This software is openly available. It may be obtained by
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
client
DISI Working Group [Page 32]
RFC 1292 DIXIE January 1992
This software was developed at the University of Michigan by
Beecher, Tim Howes, and Mark Smith of the ITD Research Systems
Group. It is subject to the following copyright
Copyright (c) 1991 Regents of the University of Michigan. All
reserved. Redistribution and use in source and binary forms are per
mitted provided that this notice is preserved and that due credit
given to the University of Michigan at Ann Arbor. The name of
University may not be used to endorse or promote products
from this software without specific prior written permission.
software is provided "as is" without express or implied warranty
DISI Working Group [Page 33]
RFC 1292 DS-520, DS-521 January 1992
DS-520
DS-521
LAST
November, 1991
API, Commercially Available, DSA/DUA, DUA Connectivity, DSA Connec
tivity, Multiple Vendor Platforms, OSI Transport, RFC-1006, Source
DS-520 X.500 Distributed Directory Services for UNIX System V
DS-521 X.500 Directory User Agent (DUA) for UNIX System V form
integral part of the Retix OSI Networking Products family.
for systems vendors, public carriers, and other OEMs, DS-520 is
complete high-performance implementation of X.500 in source
form, including a DUA, DSA Manager (DSAM), and DSA. DS-521
represents a subset of this product offering. It provides the
portal into the directory, which, for example, meets the needs
software vendors who plan to provide application packages with X.500
Directory interaction capabilities. Within these two offerings,
DUA possesses two forms of interface. The first form, the DUA
User Interface, provides an interactive character-based user inter
face for users of Directory services. The user agent provides
to the Directory via basic Directory service requests. The
form, the DUA with Programmatic Interface provides a
programmatic interface to application programs that must
Directory information. The interface is conformant to the X/
Object Management (XOM) and X/Open Directory Services (XDS) stan
dards. This component provides all functionality related to
access and general OSI services down to the session layer. The
provides an interactive character oriented user interface to a Direc
tory administrator. The DSAM provides management functions
local to or remote from a DSA. Both the DUA and the DSAM are
in the training, management, and manipulation of Directory
maintaining operational and user attribute information. The DSA main
tains Directory database information and provides users the
to read/compare, modify, search, and manage entries within the data
base. It maintains all or fragments of the Directory Information
(DIB) and provides abstract service ports for DUAs and DSAs over
and DSP protocols respectively
DISI Working Group [Page 34]
RFC 1292 DS-520, DS-521 January 1992
DS-520 represents a complete implementation of the 1988 X.500 Recom
mendations with the exception of strong authentication as outlined
X.509. It is conformant to NIST, EWOS, and UK GOSIP Directory pro
files. It provides session through application layer protocol
and hence incorporates ROSE, ACSE, Presentation, and Session
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
X.402, Annex A. Remote on-line management of the DSA is supported
means of Network Management Forum CMIP
DS-521 represents a complete implementation of the X/Open
Management (OM) and X/Open Directory Services (XDS) standards.
also incorporates session through application layer protocol
and thus includes ROSE, ACSE, Presentation, and Session within
product stack
The DS-520 has been tested to interoperate with Banyan (DAP),
(DSP), IBM, ICL, OSIWare, Nixdorff, Unisys (DSP), Wollongong (DAP),
and 3-Com (DSP).
The DS-521 subset has undergone no separate interoperability testing
PILOT
DSA Connectivity provided by the DS-520: The DSA provides
support for the X.511 Abstract Service Definition, the directoryAc
cessAC and the directorySystemAC defined in the X.519
Specifications, and the Distributed Directory defined in the X.518
Procedures for the Distributed Directory. It supports all the
classes, attribute types, and attribute syntaxes defined in X.520
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
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
with Programmatic Interface, however, does support all the
classes, attribute types, and attribute syntaxes defined in these
recommendations
DISI Working Group [Page 35]
RFC 1292 DS-520, DS-521 January 1992
Product Action Requests (PARs) stemming externally from customers
internally from customer service and quality assurance engineers
generated and published in the form of weekly reports. A
and status of these PARs are provided to customers
software maintenance agreements
CAVEATS AND GENERAL
DS-520 and DS-521 are source code products ported to UNIX System
Release 3 and 4. Makefiles to generate the system are provided
the AT&T System V, SCO, and Interactive UNIX systems
INTERNETWORKING
DS-520 and DS-521 offer two main compile time configuration
and hence internetworking configurations. In the first of these,
interface to the UNIX System V Transport Library Interface (TLI).
The TLI provides a path between the session layer of a UNIX
application process and an OSI transport provider installed in
UNIX kernel. The latter transport provider may take the form of
Retix Unix LAN (LT-610) or WAN (WT-325) transport product. The
main option utilizes the UNIX System V ACSE/Presentation
interface (APLI and the A/P Library), which provides OSI ACSE
Presentation layer services. The Retix AP-240 Presentation
manager product serves to map the standard Retix Presentation
interface to the AT&T APLI. The APLI upper layers services may
provided by the Retix UL-220 product. UL-220 is the Retix implementa
tion of the AT&T Open Networking Platform Upper Layer Services
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
the Retix MP-120 product. MP-120 is a STREAMS based driver
implements RFC-1006 and thus allows OSI applications to run over
network based on the Internet suite of protocols (TCP/IP). Its
function provides a conversion between the TCP stream to the
packets required by OSI Transport Class 0 protocol and vice versa.
part of this process, it converts TCP/IP 32-bit addresses to
values for use with OSI applications
DISI Working Group [Page 36]
RFC 1292 DS-520, DS-521 January 1992
HARDWARE
Being source code products ported to the UNIX System V Release 3
4 operating system environment, DS-520 and DS-521 are hardware plat
form independent. They currently both have sample portations and
configurations on various Intel 80386 platforms running Unix System
Release 3 and 4.
SOFTWARE
Currently, DS-520 and DS-521 include reference implementations
the AT&T System V Release 4, SCO UNIX System V/386 Version 3.2.2,
the Interactive UNIX System V/386 Version 2.2 operating systems
Raima Corporation's db_Vista III Version 3.1 serves as the
engine for the Directory product
DS-520 and DS-521 are commercially available from
2401 Colorado
Santa Monica,
90404-3563
Sales and Information: 310-828-3400
FAX: 310-828-2255
DISI Working Group [Page 37]
RFC 1292 HP DDS January 1992
HP X.500 Distributed Directory
Hewlett
LAST
July, 1991
API, CLNP, Commercially Available, DSA/DUA, HP, X.25
HP's Distributed Directory Software is a fully distributed
that supports both the DAP and DSP protocols, which were specified
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
at the time that they are stable. Users are able to define their
attributes, objects classes and DIT structure rules
In order to make this software easy to use a set of menu
screens have been provided. There are easy to use data access
data management screens. For system administrators, these is also
set for screens that are used to help configure the servers
manage the schema. Startup and Shutdown utilities are also included
For application developers an X/Open-APIA XDS API is provided,
with some helper routines that help reduce development time. The
API includes the following functions
A subset of the X/Open-APIA Object Management (XOM) functions
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
DISI Working Group [Page 38]
RFC 1292 HP DDS January 1992
This software implements the 1988 X.500 CCITT/ISO Standard. It
supports DAP and DSP, minus strong authentication. By default
contains all of the X.520 Attributes and the X.521 Syntaxes
Object Classes. Additionally, the Annex B DIT Structure can
enforced
Interoperability testing will be undertaken as new X.500 products
introduced into the market
PILOT
[No information provided--Ed.]
No major ones at this time
CAVEATS AND GENERAL
This is pilot software for organizations who wish to learn about HP'
X.500 offering
INTERNETWORKING
TP0 or TP4 on 802.3 or X.25
HARDWARE
HP-9000 800
HP-9000 300
with at least 8 M of internal
with 9 M of available disk space for the
SOFTWARE
Distributed and Supported for HP-UX version 7.0.
Limited Commercial Availability
For more information in the U.S. call 1-800-752-0900. Outside of
U.S. please contact your local HP Sales Office
DISI Working Group [Page 39]
RFC 1292 INTERACTIVE Systems January 1992
INTERACTIVE Systems' X.500 DSA/
INTERACTIVE Systems' X.500
INTERACTIVE Systems
LAST
July, 1991
API, Commercially Available, DSA/DUA, Multiple Vendor Platforms,
Transport, RFC-1006,
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.
software packages allow remote access for Directory Systems
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
- BCS Session
- DBMS and
- X/Open XDS API (included in the DUA
These products will be available in Q3 1991 in source code form only
DISI Working Group [Page 40]
RFC 1292 INTERACTIVE Systems January 1992
These products provide
- a complete implementation of the X.500 distributed
- a DUA with command line UI and X/Open Directory Services (XDS
- a Multiprocess DSA with integral high performance
- remote or local CMIP based DSA
- a DSA manager that provides on-line DSA monitoring, control
Directory schema manipulation, and DUA
- Support for all 1988 X.500, 1988 X.400, and MAP/TOP 3.0
types and the capability to add new object
- Conformance with NIST, EWOS, and U.K. GOSIP X.500 Directory pro
Not available at this time
PILOT
[No information provided--Ed.]
Not available at this time
CAVEATS AND GENERAL
Not available at this time
INTERNETWORKING
The INTERACTIVE Systems implementation of X.500 Directory
will operate over both RFC-1006 (in TCP/IP Based networks) and
the Retix Local Area and Wide Area Network services
HARDWARE
These products are available in source code form only and can
ported to any UNIX-based computers
DISI Working Group [Page 41]
RFC 1292 INTERACTIVE Systems January 1992
SOFTWARE
These products operate in the UNIX System V Release 3.2 and System
Release 4 operating systems
Both products will be available in Q3 1991. For more
contact
INTERACTIVE Systems
1901 North Naper
Naperville, IL. 60563-8895
PHONE: (708) 505-9100 extension 232
FAX: (708) 505-9133 Attn.: Jim
DISI Working Group [Page 42]
RFC 1292 Mac-ISODE January 1992
Mac-
Computer Science Department of Massey
LAST
November, 1991
API, Available via FTP, DSA/DUA, Free, Macintosh, Needs ISODE, RFC
1006,
Mac-ISODE is a reasonably complete port of ISODE version 7.0. It
on top of Mac TCP and its development environment is MPW with the
C compiler See entry for QUIPU/ISODE for a detailed description
the DSA/DUA
See entry for QUIPU/ISODE
See entry for QUIPU/ISODE
PILOT
Not tested
Macintosh related problems should be sent to PKay@massey.ac.nz
CAVEATS AND GENERAL
No testing of the DSA has been done
INTERNETWORKING
See entry for QUIPU/ISODE
DISI Working Group [Page 43]
RFC 1292 Mac-ISODE January 1992
HARDWARE
Macintosh, >1Mb memory, System 6.
SOFTWARE
Macintosh, >1Mb memory, System 6.
The Macintosh part of the package is freely available. Anonymous
from cc-vms1.massey.ac.nz (130.123.1.4)
DISI Working Group [Page 44]
RFC 1292 MacDish January 1992
NASA Ames Research
LAST
July, 1991
DUA Light Weight Client, Limited Functionality, Macintosh,
ISODE, Potentially
MacIntosh interface which connects to a TCP/IP port attached to
running on UNIX or other dish-capable host. Uses a point-and-
interface to simplify dish access
No authentication, no modify/delete/add ability
Interoperates with QUIPU/
PILOT
Being used in the White Pages Pilot Project
Not complete yet, so there are some bugs (primarily formatting, win
dow management).
CAVEATS AND GENERAL
Not a terribly capable interface
INTERNETWORKING
Pure TCP/IP. Does not require OSI stack support
DISI Working Group [Page 45]
RFC 1292 MacDish January 1992
HARDWARE
MacDish runs on Macintosh
SOFTWARE
MacTCP and MacOS 6.0.x
Not yet available. Contact is
Mylene
MS 233-18
NASA Ames Research
Moffett Field, CA 94035-1000
(415) 604-3836
DISI Working Group [Page 46]
RFC 1292 maX.500 January 1992
maX.500
University of
LAST
November, 1991
Available via FTP, DUA Light Weight Client, Free,
maX.500 is a Macintosh X.500 directory application useful
displaying and modifying white pages information about people.
runs on top of the DIXIE protocol (described in RFC 1246). maX.500
is currently in production release 1.1 within the University
Michigan and several other places
Features include the ability to display and modify the
attributes: title, description, commonName, uid, mail, postalAddress
homePostalAddress, telephoneNumber, facsimileTelephoneNumber, home
Phone. Photos can also be displayed. The software also
access to the finger protocol. Various preferences are user
tailorable, including caching
maX.500 uses the DIXIE protocol to access X.500 and thus is
to the same completeness restrictions as DIXIE. It provides Read
Search, and Modify capabilities
Works with the DIXIE server, which works with the QUIPU DSA and
library
PILOT
It has been tested (in conjunction with the DIXIE server) in both
Internet and PARADISE pilots
No outstanding bugs are known. But reports should be sent
x500@itd.umich.edu
DISI Working Group [Page 47]
RFC 1292 maX.500 January 1992
CAVEATS AND GENERAL
maX.500 is heavily oriented to white pages information and thus gen
eral access to the DIXIE protocol is not provided
INTERNETWORKING
maX.500 uses the DIXIE protocol and thus TCP to communicate with
DIXIE server. The Macintosh needs to have MacTCP installed
HARDWARE
Mac Plus or newer machine with one megabyte or more of memory
SOFTWARE
Apple System Software 6.0 or above (including System 7), with
installed
This software is openly available. It may be obtained by
FTP from terminator.cc.umich.edu in the directory ~ftp/x500.
This software was developed at the University of Michigan by
Smith of the ITD Research Systems Unix Group and is subject to
following copyright
Copyright (c) 1991 Regents of the University of Michigan. All
reserved. Redistribution and use in source and binary forms are per
mitted provided that this notice is preserved and that due credit
given to the University of Michigan at Ann Arbor. The name of
University may not be used to endorse or promote products
from this software without specific prior written permission.
software is provided "as is" without express or implied warranty
DISI Working Group [Page 48]
RFC 1292 OSI Access and Directory January 1992
OSI Access and
Control Data
LAST
November, 1991
Commercially Available, DUA Connectivity, DSA Connectivity, API
DSA/DUA, OSI CLNP, RFC-1006, X.25, MIPS (under Control Data's EP/
OS).
OSI Access and Directory includes a QUIPU (version 6.6) based imple
mentation of Directory with enhancements including
- TP4 CLNP
- Directory API based on the X.400
- Support for X.400
- Integration with Control Data's X.400 MHS
- Curses based user
- A DUA daemon that provides Directory access for
- Enhanced photo attribute
- ACL
- DIXIE, DAD and PH.X500
As per QUIPU
OSI Access and Directory can interoperate with any QUIPU based Direc
tory. It has also been informally interoperated with RETIX
UNISYS implementations
DISI Working Group [Page 49]
RFC 1292 OSI Access and Directory January 1992
PILOT
DUA Connectivity. DSA Connectivity without InternetDSP support
As per QUIPU
CAVEATS AND GENERAL
As per QUIPU
INTERNETWORKING
As per QUIPU (RFC-1006 with TCP/IP, TP0 with X.25) plus TP4
CLNP
HARDWARE
Control Data 4000 systems
SOFTWARE
Control Data EP/IX
Commercially available from
Control Data
Computer Products
4000 Series
HQW10
P.O. Box 0
Minneapolis, MN 55440-4700
1-800-345-6628
DISI Working Group [Page 50]
RFC 1292 OSI-DSA January 1992
OSI-
LAST
November, 1991
API, CLNP, Commercially Available, DSA Only, RFC-1006, Source
Unisys, X.25
OSI-DSA provides a Directory System agent for controlled access
the OSI Directory Information Base. It provides full support for
joint ISO/IEC IS-9594 International standard and CCITT X.500 Recom
mendations 1988 protocols necessary for implementing the
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
Directory Information
Specific features provided by the Directory System Agent include
(i) Support of the directoryAccessAC and
application contexts (i.e. both Directory Access
(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
handling distributed operations. Also supports the
of referrals
(v) Support for all attribute types and syntaxes defined
X.520. Users are also able to define their own
and syntaxes
(vi) Support for all the object classes and attribute
defined in X.521. Users are also able to define their
object classes and attribute sets. Support is also pro
vided for a NAME-BINDING specification, for 