NetworkWorkingGroup R. Lang
Requestfor 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
Thismemo provides information for the Internet community. It does
not specify an Internet standard. Distribution of this memois
unlimited.
Abstract
The goal of this document isto provide information regarding the
availabilityand 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 theDirectory
Information ServicesInfrastrUCture (DISI) Working Group
(disi@merit.edu) or to the editors.
1. Introduction
Thisdocument catalogs currently available implementations of X.500,
including commercialproducts and openly available offerings. It
contains descriptions of Directory System Agents (DSA), Directory
UserAgents (DUA), and DUA client applications. Thelatter can
include suchapplications asbrowsers, DSA management tools,or
lightweight DUAs that employan application-level protocol to
communicate with a DUA (which then in turn communicates witha DSA)
to support user service. Section 2 of this documentcontains a
listing of implementations cross referenced by keyWord. This list
willaid in identifying particular implementations that meetyour
criteria.
To compile this catalog, theDISI 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.
Readers are encouraged to submit comments regarding both theform and
content ofthis memo. New submissions are alwayswelcome. Please
direct inputto 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. Thiswill be deter-
mined subjectively by the DISI chairperson.
1.1 Purpose
The growth of existing X.500pilot activities (e.g.,White Pages
Pilot Project) and the advent of newpilots (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
goalof DISIis to enable the continued growth of X.500 by lowering
the lack-of-information barrier. This document takes one step toward
thatgoal byproviding an easily Accessible source of information on
X.500 implementations.
1.2 Scope
Thisdocument contains descriptions of either commercially or freely
available X.500 implementations. Itdoes not provide instructions on
how to install, run,or manage theseimplementations. Because the
needs and computing environments of each organization differvastly,
no recommendations are given. The descriptions and indices are
provided to make thereadersaware of existing options and to enable
moreinformed choices.
1.3 Disclaimer
Implementation descriptions were written by implementors andvendors,
and not by the members of DISI. Although DISI has worked with the
description authors to ensure readability, no guarantees canbe 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 alist ofkeywords, theirdefinitions, and a cross
reference ofthe X.500 implementations by these keywords.
Section 3 contains the X.500implementation descriptions.
Section 4 lists the editors'addresses.
1.5 Acknowledgments
The creationof thiscatalogwould 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
constructivefeedback. A special thanks is also extended tothe
members of the NOCTools Working Group. The "NetworkManagement Tool
Catalog" (RFC-1147) served as a valuable example. Bob Stineand Bob
Enger made key suggestions that enabled us to learn from their
eXPeriences.
The efforts of the editors were sponsored byDefenseAdvanced
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 areabbreviated attributes of the X.500 implementations.
The list of keywordsdefinedbelow was derived from the
implementation descriptions themselves. Implementations were indexed
by akeywordeither as a result of: 1) explicit, notimplied,
reference toa particular capabilityin the implementation
description text, or2) input from the implementation description
author(s).
2.1 Keyword Definitions
Thissectioncontains keyword definitions. They have been organized
and grouped by functional category.The definitionsare ordered
first alphabeticallyby keyword category, and secondalphabetically
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.
CommerciallyAvailable
This implementation canbe purchased.
Free
Available at nocharge,although other restrictions mayapply.
Potentially Unavailable
Implementation was not available at thetime 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 oflibraries and include files).
DSA Only
Implementation consistsof a DSA only.No DUA is included.
DSA/DUA
Both a DSA and DUA are includedin thisimplementation.
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 consistsof a DUA only.No DSA is included.
2.1.3 Internetworking Environment
CLNP
Implementation uses OSICLNP.
OSI Transport
Implementation description specifies that OSI transportproto-
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 OSIX.25.
2.1.4 Pilot Connectivity
DUA Connectivity
The DUAcan be connected to thepilot, and information on any
pilot entry looked up.The DUAis ableto display standard
attributes and object classes and thosedefinedin the COSINE
and Internet Schema.
DSA Connectivity
The DSAis connected tothe DIT, and information in this DSA is
accessible fromany 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., omissionswere part of the
design to provide an easy-to-use user interface.
Needs ISODE
ISODE is required to compile and/or usethis implementation.
X Window System
Implementation uses theX Window Systemto provide its user
interface.
2.1.5 OperatingEnvironment
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.
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 aPC 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 UNIXworkstation.
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 Unisysplatform.
VMS
Implementation runs under VAX/VMS.
2.2 Implementations Indexed byKeyword
Thissectioncontains an index of implementations bykeyword. You
can use thislist toidentify particular implementations that meet
yourchosen criteria.
The index isorganized as follows: keywords appear in alphabetical
order; implementations characterizedby thatkeywordare listed
alphabetically as well. Note that a"*" is used to indicatethat the
particular implementation, or feature of theimplementation,may not
be availableat thistime.
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 DUAprocess
QUIPU Xdi
XLU XT-DUA
CommerciallyAvailable 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 Directory500
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 DUAprocess
Xds
xdua
XLU
XT-DUA
xwp [PSI]
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 DUAprocess
UCOM X.500 xdua
XLU
Included In ISODE XT-DUA
xwp [PSI]
POD xwp [UWisc]
SD
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 Directory500
*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
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 DUAprocess
Xdi
Xds
xdua
XT-DUA
xwp [PSI]
xwp [UWisc]
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
3. Implementation Descriptions
In the following pages you will finddescriptions ofX.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 distinguishthe implementations. Note that
throughout this section, thepage header reflects the name of the
implementation, not the dateof the document. The descriptions fol-
low a commonformat,as described below:
NAME
The name of theX.500 implementation and the name of the respon-
sible organization. Implementations with a registered trademark
indicate this by appending "(tm)", e.g., GeeWhiz(tm).
LASTMODIFIED
The month and year within whichthis implementation description
was last modified.
KEYWORDS
A list of the keywords defined in Section 2 that have been used
to cross reference thisimplementation.
ABSTRACT
A briefdescription of the application. This section may
optionally contain a list of the pilot projectsin 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], specificallySection9 of
X.519, or the 1988 NISTOIW Stable Implementation Agreements
[NIST-88].
INTEROPERABILITY
A list of otherDUAs and DSAs with which this implementation can
interoperate.
PILOT CONNECTIVITY
Describes the level of connectivity it can offer to thepilot
directory service operational on the Internet in North America,
and to pilots co-ordinated by the PARADISE project in Europe.
Levels of connectivity are: NotTested,None, DUA Connectivity,
and DSAConnectivity.
BUGS
A warning on known problems and/or instructionson how to report
bugs.
CAVEATS AND GENERAL LIMITATIONS
A warning aboutpossible side effects or shortcomings, e.g., a
featurethat works on one platform but not another.
INTERNETWORKING ENVIRONMENT
A list of environments in whichthis implementation canbe used,
e.g., RFC-1006 with TCP/IP, TP0or TP4 with X.25.
HARDWARE PLATFORMS
A list of hardware platforms onwhich this application runs, any
additional boards or processorsrequired, and any special sug-
gested or required configuration options.
SOFTWARE PLATFORMS
A list of operating systems, window systems, databases,or
unbundled software packages required torun this application.
AVAILABILITY
A statement regarding the availability of the software (free or
commercially available), a description of how to oBTainthe
software, and (optionally) a statement regarding distribution
conditions and restrictions.
NAME
Alliance OSI(tm) X.500
Touch CommunicationsInc.
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 OSIincludes XDS (API), DUA, DSA and DIB all as separate
components.
Touch's X.500 products have been designed for complete portability to
any operating systemor hardware environment. The protocolsinclude
DAP and DSP of the OSI X.500specification 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
withRFC-1006). Touch also suppliesother application layerproto-
colssuch asX.400, FTAM, CMIP (and general network management), etc.
The AllianceOSI X.500 is compliant with theCCITT X.500 1988 Recom-
mendations. The ROSE/ACSE/Presentation/Session stackcan be option-
allyprovided 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 thesame system but
is also capable of invoking operations in Touch's orany other
vendor's compliant DSA on a remote system. The binding operation
requires theuser togive a distinguished name and password in order
for the Directory toidentify the user. Once an associationis esta-
blished the user mayinvoke the following operations: READ, COMPARE,
ABANDON, LIST, SEARCH, ADD_ENTRY, REMOVE_ENTRY, MODIFY_ENTRY,
MODIFY_RDN.
Due to the fact thataccess to the physical disk is in mostcases a
blocking operation(synchronous) Touch has separated thedatabase
processing (I/O process) from the DSA protocol entity. This separa-
tionallows the DSA entity to continue processing during thefrequent
database accesses from the DSA. The DSA supports all the Directory
operations as specified in the CCITT X.500 specification. Chaining,
Referral andMulticasting are provided and supportedin theAlliance
OSIDSA. The DSA supportsall theservicecontroloptionsincluded
in the operation command arguments.Filtering conditions are sup-
ported via the FILTER in theSEARCH operation.
The AllianceOSI X.500 product supports all the NISTdefinedmanda-
toryX.500 and X.400object classes and attributes.
Alliance OSIX.500 supports all the mandatory Directory attribute
types (and their associated abstractsyntaxes) in the NIST Directory
implementation profile. Touch has extended the Directory andallows
users to define private attributes.This means thata user can util-
ize the Alliance OSIDirectory for ageneralpurpose, user defined
database activity.
Touch provides a full set ofadministration and Directory management
facilities.
Touch is in the process of integrating the X.500 product with the
Worldtalk 400 product. Worldtalk 400is Touch's end user X.400 mes-
sageswitch,providing gateways between proprietary mail systems
(SMTP, Microsoft Mail, MHS, cc:mail,etc.) and X.400. X.500is a key
component for a messaging network.
COMPLETENESS
Strong Authentication is notsupported however Simple Authentication
is supported.
INTEROPERABILITY
No interoperability testing has beencompleted as ofyet.
PILOT CONNECTIVITY
Numerous OEMs are using the AllianceOSI X.500 product in product
development as well as in pilot networks.
BUGS
N/A
CAVEATSAND GENERAL LIMITATIONS
Currently the Alliance OSI X.500 DIBhas only been validatedwithin a
UNIXFile System. The protocol components are portable as is the
interface between the DSA and the DIB.
INTERNETWORKINGENVIRONMENT
Alliance OSIX.500 can be utilized over TCP/IP and/or OSI Transport
on LANs and WANs. CurrentlyX.500 has only been verified over OSI,
however other Alliance OSI application layers have been configured
overa RFC-1006 which is available as part of the Alliance OSI pro-
ductline.
HARDWARE PLATFORMS
Alliance OSIhas been portedto numerous platforms ranging from IBM
Mainframes MVS to Apple Macintosh. For UNIXenvironments Touch has
portations for 386 AT/Bus, SUN-3 and4, Mips, and HP.
SOFTWARE PLATFORMS
As stated above, theAlliance OSI product have been ported to
numerous systems. In the UNIX environment the X.500productexists
on SUN OS 4.0 and greater, Mips RISCOS, Interactive386 andHP-UX.
AVAILABILITY
Alliance OSIis commerciallyavailable from:
Touch CommunicationsInc.
250 E. Hacienda Ave
Campbell, CA95008
Sales and Information: (408)374-2500
FAX:(408) 374-1680
NAME
CrayOSI Version 2.0
CrayResearch Inc.
LAST MODIFIED
July, 1991
KEYWORDS
CLNP, Commercially Available, Cray, DSA/DUA,OSI Transport, RFC-1006
ABSTRACT
The product is packaged withthe Cray OSI product. It includes a DSA
and DUA capable of OSI or TCP/IP connections. The implementation is
based on theISODE QUIPU product.
COMPLETENESS
Compliance with CCITT88 plusaccess control extensions. Strong
authentication not yet implemented.
INTEROPERABILITY
Interoperates with ISODE QUIPU basedimplementations.
PILOT CONNECTIVITY
The softwarehas been operated in conjunction with the WhitePages
Pilot Project.
BUGS
[No information provided--Ed.]
CAVEATSAND GENERAL LIMITATIONS
See ISODE QUIPU limitations.
INTERNETWORKINGENVIRONMENT
TCP/IP, TP4
HARDWARE PLATFORMS
Runson UNICOS basedCray machines with OS level 7.0or greater.
SOFTWARE PLATFORMS
Supported for CRAY UNICOS 7.0 or greater.
AVAILABILITY
Commerciallyavailable via Cray Research Inc. Sales Representatives.
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 setDUA library routines, aterminal
interface, and a DSA. The implementation wasdeveloped in C on Sun 3
workstationsunder the UNIX operating system. All underlyingservices
are providedby the ISODE development package. The development pack-
age is also used forencoding and decoding ASN.1 data as well as for
other data manipulation services. Using the ISODE package the imple-
mentation can be runover both OSI and TCP/IP protocols.
The DSA provides full support for both DAP and DSP protocols, confor-
mantwith ISO 9594/CCITT X.500 standards. The DIB ismaintained using
a locally developed relational database system. The interface to the
database system consists of a set ofSQL-like C functions. These are
designed to allow straightforward replacement of thelocal database
system with a more powerful commercial system. To achieve better per-
formance several options aresupported that permit loading of
selected portions ofthe database into core.When these options are
selected data can beretrieved more quickly from in-core tables; all
modifications to theDIB aredirectly reflected in the in-core tables
and the database.
COMPLETENESS
To date the Read, Compare, List, AddEntry, and Remove Entryopera-
tions have been implemented and are supported over both DAP and DSP;
aliasing andreplication arealso supported. The version under
current development (available January '92) includessimple authenti-
cation, access control, and the Search operation. The modifyopera-
tions and Abandon are not supported and there is no support for
schema checking.
INTEROPERABILITY
Havesuccessfully interoperated withQUIPU and OSIWARE over the DAP.
No DSP interoperability testing has been done.
PILOT CONNECTIVITY
Not tested.
BUGS
Sometestingin the near term futurewill bedone totry to identify
these, but presentlyit's not possible to give an accurate list of
bugs.
CAVEATSAND GENERAL LIMITATIONS
No limitations on file sizes, etc. The only side effects to creating
large files should be in thearea ofperformance. Specifically,
optimizationrequires loading parts of the DIB in core so greater
memory requirements will be necessary for achieving better perfor-
mance with alarge database. Any platform the implementation can be
ported to (generallyany platform ISODE can be ported to) should sup-
portall features.
INTERNETWORKINGENVIRONMENT
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 whyit
should not run on any hardware running the ISODE software.
SOFTWARE PLATFORMS
It requires UNIX andthe ISODE software package. It's been developed
and tested with ISODE version 6.0 and Sun OSversion4.1.1.Uses a
locally developed relationalDBMS that should be easily replaceable
withcommercially available relational systems.
AVAILABILITY
While under continuing development, availability of the implementa-
tionis limited to organizations making appropriate arrangements with
NIST. The implementation will be publicly availablewhen development
is completed.
NAME
DCE/GDS (tm)
OpenSoftware 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 (DistributedComputing Environment/Global Directory Service)
was based onthe original Siemens DIR.X product. It supportsfull DUA
and DSA functions for globally unique identifications and for loca-
tionof 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 inX.519.An ASN.1 compiler and required ACSE, ROSE,
presentation, session and RFC-1006 protocolsimplementationsare also
included.
The product has beensuccessfully participated in X.500 Cebit Intero-
perability tests at 1990 and1991 Hanover Fairs. It also intero-
perates withthe ISODE QUIPUX.500 implementation.
COMPLETENESS
Compliant with EWOS Agreements whichis being harmonized with OIW
Agreements.
Strong authentication in X.509 is not yet implemented. (Password
scheme is currently used.)
Consists of both DUAand DSAimplementation according to the88 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 usedto access DCE/CDS (Local Cell Directory
Service) transparently. A GDA (Global Directory Agent) serves as the
gateway between the DCE CDS and GDS.
INTEROPERABILITY
Thisimplementation of DAP and DSP can interoperate with other X.500
implementations fromother Cebit demo participants includingIBM, HP,
ICL,Bull, Nixdorf, etc. It also interoperates with ISODE QUIPU.
PILOT CONNECTIVITY
[No information provided--Ed.]
BUGS
Problems andbug report email address: dce-defect@osf.org.
CAVEATSAND GENERAL LIMITATIONS
The softwareis highly portable without general limitations.
INTERNETWORKINGENVIRONMENT
OSI TP4 withCLNP
OSI TP0, 2 &4 with X.25
RFC-1006 with TCP/IP
HARDWARE PLATFORMS
DCE/GDS runson SNI's hardware platforms andis being portedto run
on IBM RS6000, Digital DECstation, etc.
SOFTWARE PLATFORMS
SINIX (UNIX System VRelease4)
Currently being ported: OSF/1.1, AIX3.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 availablefrom:
OpenSoftware Foundation, Inc.
11 CambridgeCenter
Cambridge, MA 02142
Please contact:
Jon Gossels
Tel:617-621-8763
Fax:617-621-0631
e-mail: gossels@osf.org
NAME
DE
COSINE PARADISE
LAST MODIFIED
November, 1991
KEYWORDS
Available via FTAM, Available via FTP, DUA Connectivity, DUAOnly,
Free, Included in ISODE, Limited Functionality, Needs ISODE,Source,
UNIX
ABSTRACT
DE (Directory Enquiries) is intendedto be asimple-to-use interface,
suitable forthe naive user,and suitable for running as a public
access dua to provide lowestcommon denominator access to the Direc-
tory. It isa scrolling interface and will thus runon dumbtermi-
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 isthat the user should not
be able get stuck, and information on how toget into the help system
should always be on the screen. Thehelp screens (of which there are
15) are aimed at thenon-technical user. Whilst theoutwards appear-
anceof the interface is simple, a lot of attention has being given
to mapping the strings the user enters onto X.500 operationsin such
a way that the interface seems to dothe "right thing". An important
characteristic is the way the interface tries a series of searches,
gradually relaxing the matching criteria from exact (in somesense),
to good, through to "fuzzy". A considerableamount of configuration
is possible to present the results in locally acceptable formats.
DE was funded by theCOSINE PARADISEproject, and DEis usedas the
PARADISE public access dua.You cantest 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 theISODE software (release7.0). Its interopera-
bility relies on thecorrectness of the Quipu libraries.
PILOT CONNECTIVITY
The interface is in use as the COSINE Central DUA Service, and is
usedby a number of UK institutions as a public access dua (usually
overX.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 undercountryentries. It isnot pos-
sible to query for people who do notwork for organizations. The
interface only searches for entries of the followingtype: organiza-
tions, organizational units,people,roles, and rooms.
BUGS
Sendbug reports to:
p.barker@cs.ucl.ac.uk
helpdesk@paradise.ulcc.ac.uk
CAVEATSAND GENERAL LIMITATIONS
DE tries to cater well for the general case,at the expense of not
dealing withthe less typical. The main manifestation of this is
thatthe current version will not query under localities immediately
under the country level.
It is not possible to display photographs orreproduce soundattri-
butes.
INTERNETWORKINGENVIRONMENT
Sameas 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 openlyavailable as part of ISODE and as part of the COSINE DUA
package. Availableby FTAMand FTP, sourcecode freely available.
NAME
Directory 500(tm)
OSIware Inc.
LAST MODIFIED
July, 1991
KEYWORDS
CommerciallyAvailable, DSA/DUA, RFC-1006, Sun, X.25
ABSTRACT
Fullimplementation of the X.500 recommendations. Includes DUA, DSA
& various utilities.Writtenin ANSI-C / C, and runson 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
CAVEATSAND GENERAL LIMITATIONS
None
INTERNETWORKINGENVIRONMENT
RFC-1006 with TCP/IP
TP0 with X.25
HARDWARE PLATFORMS
Runson Sun-3, Sun-4
SOFTWARE PLATFORMS
For SunOS 4.X with Sunlink X.25 6.0
AVAILABILITY
Commerciallyavailable from:
OSIware Inc. Tel:+1-604-436-2922
4370Dominion Street, Suite 200 Fax:+1-604-436-3192
Burnaby, B, Canada V5G 4L7
NAME
DISH-VMS 2.0
ACIDO Project
LAST MODIFIED
July, 1991
KEYWORDS
Available via FTAM, Available via FTP, DUA Only, Free, NeedsISODE,
RFC-1006, VMS, X.25
ABSTRACT
ThisDirectory User Agent interface was ported to the VMS operating
system usingISODE 6.0. It is part of the results ofcollaboration
project called ACIDO, between RedIRIS (national network R & D in
Spain) and the "Facultad de Informatica de Barcelona(Universidad
Politecnica de Cataluna)". The mainobjective of this development
was to provide access to thedirectory to all those affiliated cen-
tresto the Spanish NationalR & D network using VMSmachines. Any
other use ofthis software it is no within RedIRIS objectives and
therefore itis not RedIRIS responsibility.
COMPLETENESS
The same as DUA (QUIPU 6.1).
INTEROPERABILITY
QUIPU 6.1
PILOT CONNECTIVITY
Usedin RedIRIS Directory Pilot Project to access the DSAs (QUIPU).
BUGS
You can report bugs to: isode@fib.upc.es
CAVEATSAND GENERAL LIMITATIONS
The interface is equivalent to the UNIX one except for the option
-pipe which is not supported.
The users can have aquipurcfile toconfigure their workenviron-
ments withDISH. This fileshould reside at the SYS$LOGIN directory
of the user and it should becalled "quipurc." (in UNIX it's called
.quipurc)
INTERNETWORKINGENVIRONMENT
RFC-1006 with TCP/IP, TP0 with X.25
HARDWARE PLATFORMS
VAX
SOFTWARE PLATFORMS
VAX/VMS 5.3
VAX PSI 4.2
VMS/ULTRIX Connection 1.2
AVAILABILITY
Executables can be freely distributed for non-commercial use.
Transfer mode binary.
FTP user anonymous sun.iris-dcp.es (130.206.1.2)
FTAM, user anon
TSEL= <0103>H
INT-X25= 21452160234012
IXI=2043145100102
ISO-CLNS= 39724F1001000000010001000113020600100200 (COSINE P4.1)
File: /isodevms/dishVMS2.BCK.Z compress SAVE_SET file (1.6 Mbytes)
File: /isodevms/lzdcm.exe touncompress the file
NAME
DIXIE
University of Michigan
LAST MODIFIED
November, 1991
KEYWORDS
Available via FTP, DUA LightWeight Client, Free, Source, UNIX, Mul-
tiple VendorPlatform, NeedsISODE
ABSTRACT
The DIXIE protocol is used to give X.500 access to platformsthat
haveonly TCP/IP access. The DIXIE server is an intermediate proto-
col server that communicateswith Internet clients on one side using
a text-basedUDP/TCPprotocol and anX.500 DSA on the other side
using DAP. The protocol is fully described in RFC1246. A subset of
the X.500 DAP is exported tothe clients through theDIXIE protocol.
There is a DIXIE APIprovided in theform ofa library of C-callable
routines.
The DIXIE protocol and server are being usedby the following
products/projects:
UD, a simple command line white pages DUA for Unixmachines (dis-
tributed with the DIXIE server)
maX.500, awhite pages DUAfor theMacintosh (available from the
same placeas the DIXIE server)
Network monitoringof DSAsby our Network Operations Center
Lookup anddisplayof caller identification based on telephone
caller ID (using ISDN).
COMPLETENESS
The DIXIE protocol does not support access to all X.500 features and
operations.All DAPoperations except Abandon are supported. Gen-
eralsearches (including multiple component searches) are supported.
The DIXIE protocol supports none andsimple authentication.A subset
of the service controls are supported.
INTEROPERABILITY
The current implementation of the DIXIE server workswith the QUIPU
DSA and DAP library.
PILOT CONNECTIVITY
The DIXIE server hasbeen tested in the Internet andPARADISE pilots.
It provides full DUAConnectivity subject tothe limitationsdis-
cussed aboveunder completeness.
BUGS
There are noknown outstanding bugs. But reports should be sent to
x500@umich.edu.
CAVEATSAND GENERAL LIMITATIONS
None, aside from those mentioned above undercompleteness.
INTERNETWORKINGENVIRONMENT
DIXIE clients use TCP or UDPto communicate with theDIXIE server.
The DIXIE server uses RFC-1006 with TCP/IP to communicate with the
DSA,though other transport mechanisms for DSA communicationshould
be possible.
HARDWARE PLATFORMS
The DIXIE server is known torun on Sun 3, Sun 4, and DEC 3100 plat-
forms. It should run on anyUNIX platform.The DIXIE library is
known to runon the same platforms, and alsoon the Macintosh.
SOFTWARE PLATFORMS
The DIXIE server andlibraryis known to rununder SunOS 3.5, SunOS
4.1.1, Ultrix 4.1 and 4.2. The DIXIE library also runs on the Macin-
toshSystem Software6 or later.
AVAILABILITY
Thissoftware is openly available. It may be obtained by anonymous
FTP from terminator.cc.umich.edu in the directory ~ftp/x500.Documen-
tation on the DIXIE protocolis provided along with the source code,
which includes source for the DIXIE server, DIXIE library, and the UD
client.
Thissoftware was developed at the University of Michigan by Bryan
Beecher, Tim Howes, and Mark Smithof the ITD Research Systems Unix
Group. It is subject to thefollowing copyright.
Copyright (c) 1991 Regents of the Universityof Michigan. All rights
reserved. Redistribution and use insource and binary formsare per-
mitted provided thatthis notice is preserved and that due credit is
given to theUniversity of Michigan at Ann Arbor. The name of the
University may not be used to endorse or promote products derived
fromthis software without specific prior written permission. This
software is provided"as is"withoutexpressor implied warranty.
NAME
DS-520
DS-521
Retix
LAST MODIFIED
November, 1991
KEYWORDS
API,Commercially Available,DSA/DUA, DUA Connectivity, DSA Connec-
tivity, Multiple Vendor Platforms, OSI Transport, RFC-1006,Source,
UNIX
ABSTRACT
DS-520 X.500Distributed Directory Services for UNIXSystem V and
DS-521 X.500Directory User Agent (DUA) for UNIX System V form an
integral part of theRetix OSI Networking Products family. Designed
for systems vendors,public carriers, and other OEMs, DS-520is a
complete high-performance implementation of X.500 insource code
form, including a DUA, DSA Manager (DSAM), and DSA.DS-521
represents asubset of this product offering. It provides the DUA
portal into the directory, which, for example, meetsthe needs of
software vendors whoplan toprovideapplication packages with X.500
Directory interaction capabilities. Within these twoofferings, the
DUA possesses two forms of interface. The first form, the DUA with
UserInterface, provides an interactive character-based userinter-
facefor users of Directory services. The user agent provides access
to the Directory viabasic Directoryservicerequests. The second
form, the DUA with Programmatic Interface provides astandardized
programmaticinterface to application programs that must access
Directory information. The interfaceis conformant to the X/Open
Object Management (XOM) and X/Open DirectoryServices (XDS) stan-
dards. This component provides all functionality related to Directory
access and general OSI services downto the session layer. The DSAM
provides an interactive character oriented user interface toa Direc-
toryadministrator.The DSAM provides management functions either
local to or remote from a DSA. Both the DUA and the DSAM areuseful
in the training, management,and manipulation of Directory entries
maintaining operational and user attribute information. The DSA main-
tains Directory database informationand provides users the ability
to read/compare, modify, search, andmanage entries within the data-
base. It maintains all or fragments of the DirectoryInformation Base
(DIB) and provides abstract service ports for DUAs and DSAs over DAP
and DSP protocols respectively.
COMPLETENESS
DS-520 represents a completeimplementation of the 1988 X.500 Recom-
mendations with the exception of strong authentication as outlined in
X.509. It isconformant to NIST, EWOS, and UK GOSIP Directory pro-
files. It provides session through application layerprotocol support
and hence incorporates ROSE,ACSE, Presentation, andSessionwithin
its product stack. In addition to including all the attribute types,
syntaxes, and objectclassesdefinedin X.520 and X.521, theDS-520
includes support forthose specifiedin the 1988 X.400 Recommendation
X.402, AnnexA. Remote on-line management ofthe DSAis supported by
means of Network Management Forum CMIP.
DS-521 represents a completeimplementation of the X/Open Object
Management (OM) and X/Open DirectoryServices (XDS) standards. It
alsoincorporates session through application layer protocolsupport
and thus includes ROSE, ACSE, Presentation, and Session within its
product stack.
INTEROPERABILITY
The DS-520 has been tested to interoperate with Banyan (DAP), CDC
(DSP), IBM, ICL, OSIWare, Nixdorff, Unisys (DSP), Wollongong(DAP),
and 3-Com (DSP).
The DS-521 subset has undergone no separate interoperabilitytesting.
PILOT CONNECTIVITY
DSA Connectivity provided bythe DS-520: TheDSA provides complete
support for the X.511 Abstract Service Definition, the directoryAc-
cessAC and the directorySystemAC defined in the X.519 Protocol
Specifications, and the Distributed Directory defined in theX.518
Procedures for the Distributed Directory. Itsupports all the object
classes, attribute types, and attribute syntaxes defined in X.520 and
X.521. It does not support the Internet DSP however.
DUA Connectivity provided byboth the DS-520and DS-521: TheDUA pro-
vides complete support for the X.511Abstract Service Definition and
the directoryAccessAC defined in theX.519 Protocol Specifications.
The DUA withUser Interface supportsonly a subset of the X.500
attributes and object classes defined in X.520 and X.521. The DUA
withProgrammatic Interface,however, does support all the object
classes, attribute types, and attribute syntaxes defined in these two
recommendations.
BUGS
Product Action Requests (PARs) stemming externally from customers and
internally from customer service andqualityassurance engineers are
generated and published in the form of weekly reports. A description
and status of these PARs areprovided to customers possessing
software maintenanceagreements.
CAVEATSAND GENERAL LIMITATIONS
DS-520 and DS-521 are sourcecode products ported toUNIX System V
Release 3 and 4. Makefiles to generate the system are provided for
the AT&T System V, SCO, and Interactive UNIXsystems.
INTERNETWORKINGENVIRONMENT
DS-520 and DS-521 offer two main compile time configuration options
and hence internetworking configurations. Inthe first of these, they
interface tothe UNIX SystemV Transport Library Interface (TLI).
The TLI provides a path between the session layer ofa UNIX OSI
application process and an OSI transport provider installed in the
UNIXkernel.The latter transport provider may take the formof a
Retix Unix LAN (LT-610) or WAN (WT-325) transport product. The second
mainoption utilizesthe UNIX SystemV ACSE/Presentation Library
interface (APLI and the A/P Library), which providesOSI ACSE and
Presentationlayer services.The Retix AP-240 Presentation syntax
manager product serves to map the standard Retix Presentation layer
interface tothe AT&T APLI. The APLIupper layers services may be
provided by the Retix UL-220product. UL-220is the Retix implementa-
tionof the AT&T Open Networking Platform Upper Layer Services module
and includesthe A/Plibrary, as well as theOSI ACSE, Presentation,
and Session services.
DS-520 and DS-521 may also run on top of theTCP/IP stack bymeans of
the Retix MP-120 product. MP-120 is a STREAMS based driver that
implements RFC-1006 and thusallows OSI applicationsto run over a
network based on theInternet suite of protocols (TCP/IP). Its main
function provides a conversion between the TCP stream to thedata
packets required by OSI Transport Class 0 protocol and vice versa. As
partof thisprocess, it converts TCP/IP 32-bit addresses tohex
values for use with OSI applications.
HARDWARE PLATFORMS
Being sourcecode products ported tothe UNIX SystemV Release 3 and
4 operatingsystem environment, DS-520 and DS-521 are hardware plat-
formindependent. They currently both have sample portationsand test
configurations on various Intel 80386 platforms running UnixSystem V
Release 3 and 4.
SOFTWARE PLATFORMS
Currently, DS-520 and DS-521includereference implementations for
the AT&T System V Release 4,SCO UNIX SystemV/386 Version 3.2.2, and
the Interactive UNIXSystem V/386 Version 2.2 operating systems.
Raima Corporation's db_VistaIII Version 3.1serves as the database
engine for the Directory product.
AVAILABILITY
DS-520 and DS-521 are commercially availablefrom:
Retix
2401Colorado Avenue
Santa Monica, California
90404-3563 USA
Sales and Information: 310-828-3400
FAX: 310-828-2255
NAME
HP X.500 DistributedDirectory Software
Hewlett Packard
LAST MODIFIED
July, 1991
KEYWORDS
API,CLNP, Commercially Available, DSA/DUA, HP, X.25
ABSTRACT
HP'sDistributed Directory Software is a fully distributed Directory
thatsupports both the DAP and DSP protocols, which were specified in
the 1988 CCITT/ISO X.500 documents.Besidesimplementing the stan-
dard, we have also put in proprietary accesscontroland replication.
These additional features will be migrated to the standard definition
at the time that they are stable. Users areable todefine their own
attributes, objects classes and DIT structure rules.
In order to make this software easy to use aset of menu driven
screens havebeen provided.There are easy to use data access and
datamanagement screens. For systemadministrators,these is also a
set for screens thatare used to help configure the servers and
manage the schema. Startup and Shutdown utilities are also included.
For application developers an X/Open-APIA XDS API isprovided, along
withsome helper routines that help reduce development time. The XDS
API includesthe following functions:
Bind
Read
Search
Add
Remove
Unbind
Version
A subset of the X/Open-APIA Object Management (XOM) functions are
available thru the interface. The subset are those that areneces-
saryto perform the directory operations.
For bulk operations a batch interface is also available.
COMPLETENESS
Thissoftware implements the1988 X.500 CCITT/ISO Standard.It fully
supports DAPand DSP, minus strong authentication. By default it
contains allof the X.520 Attributesand theX.521 Syntaxes and
Object Classes. Additionally, the Annex B DIT Structure canbe
enforced.
INTEROPERABILITY
Interoperability testing will be undertaken as new X.500 products are
introduced into the market.
PILOT CONNECTIVITY
[No information provided--Ed.]
BUGS
No major ones at this time.
CAVEATSAND GENERAL LIMITATIONS
Thisis pilot software for organizations whowish tolearn about HP's
X.500 offering.
INTERNETWORKINGENVIRONMENT
TP0 or TP4 on 802.3 or X.25
HARDWARE PLATFORMS
HP-9000 800 Minicomputer
HP-9000 300 Workstation
withat least 8 M ofinternal memory
with9 M of available disk space forthe software
SOFTWARE PLATFORMS
Distributed and Supported for HP-UX version 7.0.
AVAILABILITY
Limited Commercial Availability.
For more informationin the U.S. call 1-800-752-0900. Outside of the
U.S.please contact your local HP Sales Office.
NAME
INTERACTIVE Systems'X.500 DSA/DSAM
INTERACTIVE Systems'X.500 DUA
INTERACTIVE Systems Corporation
LAST MODIFIED
July, 1991
KEYWORDS
API,Commercially Available,DSA/DUA, Multiple Vendor Platforms, OSI
Transport, RFC-1006,UNIX
ABSTRACT
The INTERACTIVE Systems X.500 DSA/DSAM and X.500 DUAprovidea com-
plete implementationof the OSI X.500 Directory Systems Agent, Direc-
torySystemsAgent Manager, and Directory Services User Agent. These
software packages allow remote access for Directory Systems Agents
and include the following protocols:
- Directory SystemProtocol (DSP)
- Directory AccessProtocol (DAP)
- Common Management Information Protocol (CMIP)
- Remote Operations Service Element (ROSE)
- Association Control Service Element (ACSE)
- Presentation services
- BCS Session services
- DBMS andutilities
- X/Open XDS API (includedin the DUA)
These products will be available in Q3 1991 in source code form only.
COMPLETENESS
These products provide:
- a complete implementation of theX.500 distributed Directory
- a DUA with command line UI and X/Open Directory Services (XDS)
API
- a Multiprocess DSA with integralhigh performance DBMS
- remote or local CMIP based DSA management
- a DSA manager that provides on-line DSA monitoring,control,
Directory schema manipulation, andDUA functions
- Support for all 1988 X.500, 1988X.400, and MAP/TOP 3.0 object
types and the capability to add new objecttypes
- Conformance withNIST, EWOS, andU.K. GOSIP X.500 Directory pro-
files
INTEROPERABILITY
Not available at this time.
PILOT CONNECTIVITY
[No information provided--Ed.]
BUGS
Not available at this time.
CAVEATSAND GENERAL LIMITATIONS
Not available at this time.
INTERNETWORKINGENVIRONMENT
The INTERACTIVE Systems implementation of X.500 Directory Services
willoperateover both RFC-1006 (in TCP/IP Based networks) and over
the Retix Local Areaand Wide Area Network services.
HARDWARE PLATFORMS
These products are availablein source code form only and can be
ported to any UNIX-based computers.
SOFTWARE PLATFORMS
These products operate in the UNIX System V Release 3.2 and System V
Release 4 operating systems.
AVAILABILITY
Bothproducts will be available in Q3 1991.For more information
contact:
INTERACTIVE Systems Corporation
1901North Naper Boulevard
Naperville, IL. 60563-8895
PHONE: (708)505-9100 extension 232
FAX:(708) 505-9133Attn.: Jim Hancock
NAME
Mac-ISODE
Computer Science Department of Massey University
LAST MODIFIED
November, 1991
KEYWORDS
API,Available via FTP, DSA/DUA, Free, Macintosh, Needs ISODE, RFC-
1006, Source
ABSTRACT
Mac-ISODE isa reasonably complete port of ISODE version 7.0. It sits
on top of Mac TCP and its development environment isMPW with the GNU
C compiler See entryfor QUIPU/ISODEfor a detailed description of
the DSA/DUA.
COMPLETENESS
See entry for QUIPU/ISODE.
INTEROPERABILITY
See entry for QUIPU/ISODE.
PILOT CONNECTIVITY
Not tested.
BUGS
Macintosh related problems should besent toPKay@massey.ac.nz.
CAVEATSAND GENERAL LIMITATIONS
No testing of the DSA has been done.
INTERNETWORKINGENVIRONMENT
See entry for QUIPU/ISODE.
HARDWARE PLATFORMS
Macintosh, >1Mb memory, System 6.x
SOFTWARE PLATFORMS
Macintosh, >1Mb memory, System 6.x
AVAILABILITY
The Macintosh part of the package isfreely available. Anonymous FTP
fromcc-vms1.massey.ac.nz (130.123.1.4)
NAME
MacDish
NASAAmes Research Center
LAST MODIFIED
July, 1991
KEYWORDS
DUA Light Weight Client, Limited Functionality, Macintosh, Needs
ISODE, Potentially Unavailable
ABSTRACT
MacIntosh interface which connects to a TCP/IP port attachedto dish
running on UNIX or other dish-capable host.Uses a point-and-click
interface tosimplify dish access.
COMPLETENESS
No authentication, no modify/delete/add ability.
INTEROPERABILITY
Interoperates with QUIPU/dish
PILOT CONNECTIVITY
Being used in the White Pages Pilot Project.
BUGS
Not completeyet, sothere are some bugs (primarily formatting, win-
dow management).
CAVEATSAND GENERAL LIMITATIONS
Not a terribly capable interface.
INTERNETWORKINGENVIRONMENT
PureTCP/IP. Does not require OSI stack support.
HARDWARE PLATFORMS
MacDish runson Macintosh computers
SOFTWARE PLATFORMS
MacTCP and MacOS 6.0.x.
AVAILABILITY
Not yet available. Contact is:
Mylene Marquez
MS 233-18
NASAAmes Research Center
Moffett Field, CA 94035-1000
(415) 604-3836
NAME
maX.500
University of Michigan
LAST MODIFIED
November, 1991
KEYWORDS
Available via FTP, DUA LightWeight Client, Free, Macintosh
ABSTRACT
maX.500 is aMacintosh X.500directory application useful for
displaying and modifying white pagesinformation about people. It
runson top of the DIXIE protocol (describedin RFC1246). maX.500
is currentlyin production release 1.1 within the Universityof
Michigan andseveralother places.
Features include theabilityto display and modify the following
attributes: title, description, commonName, uid, mail, postalAddress,
homePostalAddress, telephoneNumber, facsimileTelephoneNumber, home-
Phone. Photos can also be displayed. The software also provides
access to the fingerprotocol. Various preferences are user-
tailorable, including caching.
COMPLETENESS
maX.500 usesthe DIXIE protocol to access X.500 and thus is subject
to the same completeness restrictions as DIXIE. It providesRead,
Search, and Modify capabilities.
INTEROPERABILITY
Works with the DIXIEserver,which works with the QUIPU DSA and DAP
library.
PILOT CONNECTIVITY
It has been tested (in conjunction with the DIXIE server) inboth the
Internet andPARADISE pilots.
BUGS
No outstanding bugs are known. But reports should be sent to
x500@itd.umich.edu.
CAVEATSAND GENERAL LIMITATIONS
maX.500 is heavily oriented to whitepages information and thus gen-
eralaccess to the DIXIE protocol isnot provided.
INTERNETWORKINGENVIRONMENT
maX.500 usesthe DIXIE protocol and thus TCPto communicate with the
DIXIE server. The Macintoshneeds to have MacTCP installed.
HARDWARE PLATFORMS
Mac Plus or newer machine with one megabyte or more of memory.
SOFTWARE PLATFORMS
Apple SystemSoftware 6.0 orabove (including System7), with MacTCP
installed.
AVAILABILITY
Thissoftware is openly available. It may be obtained by anonymous
FTP from terminator.cc.umich.edu in the directory ~ftp/x500.
Thissoftware was developed at the University of Michigan byMark
Smith of theITD Research Systems Unix Groupand is subject to the
following copyright.
Copyright (c) 1991 Regents of the Universityof Michigan. All rights
reserved. Redistribution and use insource and binary formsare per-
mitted provided thatthis notice is preserved and that due credit is
given to theUniversity of Michigan at Ann Arbor. The name of the
University may not be used to endorse or promote products derived
fromthis software without specific prior written permission. This
software is provided"as is"withoutexpressor implied warranty.
NAME
OSI Access and Directory
Control DataCorporation
LAST MODIFIED
November, 1991
KEYWORDS
CommerciallyAvailable, DUA Connectivity, DSA Connectivity, API,
DSA/DUA, OSICLNP, RFC-1006,X.25, MIPS (under Control Data's EP/IX
OS).
ABSTRACT
OSI Access and Directory includes a QUIPU (version 6.6) based imple-
mentation ofDirectory with enhancements including:
- TP4 CLNPconnectivity
- Directory API based on the X.400API
- Support for X.400 objects
- Integration withControlData's X.400 MHS products
- Curses based user interface
- A DUA daemon that provides Directory access for applications
- Enhancedphoto attributesupport
- ACL enhancements
- DIXIE, DAD and PH.X500 support
COMPLETENESS
As per QUIPU.
INTEROPERABILITY
OSI Access and Directory caninteroperate with any QUIPU based Direc-
tory. It has also been informally interoperated with RETIX and
UNISYS implementations.
PILOT CONNECTIVITY
DUA Connectivity. DSA Connectivity without InternetDSP support.
BUGS
As per QUIPU.
CAVEATSAND GENERAL LIMITATIONS
As per QUIPU.
INTERNETWORKINGENVIRONMENT
As per QUIPU(RFC-1006 with TCP/IP, TP0 withX.25) plus TP4 over
CLNP.
HARDWARE PLATFORMS
Control Data4000 systems.
SOFTWARE PLATFORMS
Control DataEP/IX.
AVAILABILITY
Commerciallyavailable from:
Control DataCorporation
Computer Products Marketing
4000Series Networking
HQW10H
P.O.Box 0
Minneapolis,MN 55440-4700
USA
1-800-345-6628
NAME
OSI-DSA
Unisys
LAST MODIFIED
November, 1991
KEYWORDS
API,CLNP, Commercially Available, DSA Only,RFC-1006, Source,
Unisys, X.25
ABSTRACT
OSI-DSA provides a DirectorySystem agent for controlled access to
the OSI Directory Information Base.It provides full support for the
joint ISO/IEC IS-9594 International standardand CCITT X.500Recom-
mendations 1988 protocols necessary for implementingthe Directory
Information Base distributedacross a numberof DSA's.
The product also includes anAdministration User interface program,
to allow a human administrator to construct and maintain thelocal
Directory Information.
Specific features provided by the Directory System Agent include:
(i) Support of the directoryAccessAC and directorySystemAC
application contexts (i.e. both DirectoryAccess Protocol
(DAP) andDirectory System Protocol (DSP)
(ii) Bind Security levels of none and simple unprotected.
(iii) Capability of acting as afirst level DSA.
(iv) Support for chaining and multi-casting where necessary in
handling distributed operations. Also supports the return
of referrals.
(v) Support for all attributetypes and syntaxes defined in
X.520. Users arealso able to define their own attributes
and syntaxes.
(vi) Support for all the object classes and attribute sets
defined in X.521. Users are alsoable todefine their own
object classes and attribute sets. Support is also pro-
vided fora NAME-BINDING specification, for defining the
DirectoryInformation Tree (DIT) structure.
(vii) An accesscontrolmechanism basedon the ISO access con-
trol working papers to allow for controlled access and
maintenance of Directory entries and attributes.
(viii) Logging of errorsand significantDirectory events, as
well as optional trace information.
(ix) The OSI-DSA utilizes the servicesof ROSE(X.219)and ACSE
(X.217) as defined in clause 8 ofX.519
The Administration program provides the following functions
(i) An interface to each of the basicDirectory Operations of
Read, Compare, List, Search, Add,Modify,ModifyRDN.
(ii) ADump/Load utility to dump the information in the local
DIB into an ASCIIfile and load it again into theDIB from
such a file.
(iii) KnowledgeReference maintenance facilities to Add, Delete
Modify and Read all typesof Knowledge References.
(iv) Facilities to control theoperation of local Directory
processes.
(v) Control over the level ofloggingand tracing.
COMPLETENESS
The OSI-DSA providesall functionality defined in, and is fully con-
formant to, the joint ISO/IEC IS-9594 International standardand
CCITT X.500 Recommendations 1988, and the NIST 1988 Stable agreements
on DirectoryServices.
The only exception is that no support is provided for strongauthen-
tication or digital signatures.
Conformance with respect to clause 9of X.519:
(i) The DSA supports both thedirectoryAccessAC and directo-
rySystemAC application contexts.
(ii) The DSA is capable of acting as afirst-level DSA.
(iii) The chained mode of operation as defined in X.518is sup-
ported.
(iv) Bind Security levels of none and simple unprotected are
supported.
(v) All attribute types and syntaxes defined in X.520are sup-
ported. Users arealso able to define their own attributes
and syntaxes.
(vi) All the object classes and attribute setsdefinedin X.521
are supported. Users arealso able to define their own
object classes and attribute sets. Support is also pro-
vided fora NAME-BINDING specification, for defining the
DirectoryInformation Tree (DIT) structure.
(vii) The DSA conforms to all the static requirements defined in
clause 9.2.2 of X.519
(viii) The DSA conforms to all the dynamic requirements defined
in clause9.2.3 of X.519
INTEROPERABILITY
The product was demonstratedat "Interop 91"in San Jose, October
1991as partof the OSI Showcase demo involving several vendors'
directory products.
Informal interoperability has been achieved against the ISODE 6.0
QUIPU Directory implementation. Interoperability testing against
other vendors is in progress.
Formal interoperability testing is awaiting the soonto be completed
OSInet X.500interoperability test suite.
PILOT CONNECTIVITY
Not tested.
BUGS
Fullcustomer support is provided via your local Unisys Customer Ser-
vices Organization.
CAVEATSAND GENERAL LIMITATIONS
Results returned viathe OSI-DSA arepresently limited to 32K in the
current release, which is inline with the 1988 NISTagreements.
Patches for the UnixV.4 release maybe madeavailable on request to
raise this limit to 1Mb.
The product currently does not provide any support for replication,
although developmentwork isin progress, based on the current ISO
Draft proposal for Replication.
INTERNETWORKINGENVIRONMENT
OSI-DSA runsover all communicationsenvironments supported by the
Unisys OSI stack product (see Software platforms). Currentlythese
support TP0,TP2, TP3 and TP4 over X.25 and TP4 overCLNP on802.3
and X.25. Support for RFC1006 over TCP/IP is under development.
HARDWARE PLATFORMS
The product is available on all Unisys Unix 6000 Series machines.
Source code is available forportation to non-Unisysplatforms.
SOFTWARE PLATFORMS
The product is distributed and supported forUnix System V.3and Unix
System V.4.
On Unix V.3,it requires theUnisys Application PresentationService
OSI stack software (APS), and UnisysTransport Network Service
software (TNS). On Unix V.4, it requires the integrated Unisys OSI
stack software product (STK). Theseservices are accessed via the
ROSLI (ROSE)and APLI (ACSE)programming interfaces which are
currently the subject of standardization efforts by XOpen and Unix
International.
A runtime version ofeither the Informix or Oracle relational data-
baseproducts is required for the Directory Information Base.
AVAILABILITY
Unisys Unix OSI Directory System Agent is commercially available. For
information on porting to non-Unisysplatforms, contact:
SocsCappas
Australian Centre for UnisysSoftware
115 Wicks Rd
North Ryde
N.S.W, 2113
Australia
socs@syacus.acus.oz.au
Ph: 61 2 3901312
Forany other information contact yourlocal Unisys marketing
representative or:
Unisys Corporation
Corporate Marketing
MailDrop B-130
BlueBell, PA 19424
USA
NAME
OSI-DUA
Unisys
LAST MODIFIED
November, 1991
KEYWORDS
API,CLNP, Commercially Available, DUA Only,RFC-1006, Source,
Unisys, X.25
ABSTRACT
OSI-DUA is aUnix C Program interface library. It allows OSIor user
applicationsto access the services of an X.500 conformant Directory,
by making calls to alibraryof C routines.
Specific features provided by this program interfacelibraryare as
follows:
(i) Connection to anyremote X.500 conformantDSA viaan OSI
stack, orconnection to aco-resident Unisys OSI DSA via
IPC mechanisms.
(ii) All operations defined inthe directoryAccessAC applica-
tion context (Bind, UnBind, Read,Compare, Search, List,
AddEntry,ModifyEntry, ModifyRDN,Abandon, DeleteEntry).
(iii) DirectoryBind security levels ofnone and simpleunpro-
tected.
(iv) Executionof bothblocking and non-blocking operations.
(A non-blocking call to the library will return immedi-
ately, allowing for results to beobtained once the opera-
tion has completed)
(v) Acceptance of multiple concurrentnon-blocked operations
on the one user session.
(vi) The DUA utilizes the services of ROSE (X.219) andACSE
(X.217) as defined in clause 8 ofX.519
COMPLETENESS
Whencommunicating with a Remote DSAthe DUAlibraryis fully confor-
mantwith the Directory Access Protocol detailed in the X.500
Recommendations/IS-9594 standards.
Conformance with respect to clause 9of X.519:
(i) All operations defined inthe directoryAccessACapplica-
tion context (Bind, UnBind, Read, Compare, Search, List,
AddEntry,ModifyEntry, ModifyRDN, Abandon, DeleteEntry)
are supported.
(ii) DirectoryBind security levels ofnone and simple unpro-
tected are supported.
(iii) The directoryAccessAC applicationcontextis supported as
specifiedin clause 7 of X.519.
(iv) The DUA conforms to the mapping onto usedservices as de-
fined in clause 8of X.519.
INTEROPERABILITY
Informal interoperability has been achieved against the ISODE 6.0
QUIPU Directory implementation. Interoperability testing against
other vendors is in progress.
Formal interoperability testing is awaiting the soonto be completed
OSInet X.500interoperability test suite.
PILOT CONNECTIVITY
Not tested.
BUGS
Fullcustomer support is provided via your local Unisys Customer Ser-
vices Organisation.
CAVEATSAND GENERAL LIMITATIONS
The present OSI-DUA does notprovidefor the automatic handling of
referrals by the interface library. However interface routines are
provided which allowreferrals to beacted upon by the userapplica-
tion.
The present OSI-DUA providesa proprietary C programming interface.
An XOpen XDSconformant interface iscurrently underdevelopment.
INTERNETWORKINGENVIRONMENT
OSI-DUA runsover all communicationsenvironments supported by the
Unisys OSI stack product (see Software platforms). Currentlythese
support TP0,TP2, TP3 and TP4 over X.25 and TP4 overCLNP on802.3
and X.25. Support for RFC1006 over TCP/IP is under development.
HARDWARE PLATFORMS
The product is currently available on all Unisys Unix 6000 Series
machines.
Source code is available forportation to non-Unisysplatforms.
SOFTWARE PLATFORMS
The product is distributed and supported forUnix System V.3and Unix
System V.4.
On Unix V.3,it requires theUnisys Application PresentationService
OSI stack software (APS), and UnisysTransport Network Service
software (TNS). On Unix V.4, it requires the integrated Unisys OSI
stack software product (STK). Theseservices are accessed via the
ROSLI (ROSE)and APLI (ACSE)programming interfaces which are
currently the subject of standardization efforts by XOpen and Unix
International.
AVAILABILITY
Unisys Unix OSI Directory System Agent is commercially available. For
information on porting to non-Unisysplatforms, contact:
SocsCappas
Australian Centre for UnisysSoftware
115 Wicks Rd
North Ryde
N.S.W, 2113
Australia
socs@syacus.acus.oz.au
Ph: 61 2 3901312
For any other information contact your localUnisys marketing
representative or:
Unisys Corporation
Corporate Marketing
MailDrop B-130
BlueBell, PA 19424
USA
NAME
POD
Brunel University
LAST MODIFIED
November, 1991
KEYWORDS
Available via FTAM, Available via FTP, DUA Only, Free, Included in
ISODE, Limited Functionality, Multiple Vendor Platforms, Needs ISODE,
RFC-1006, Source, UNIX
ABSTRACT
POD (POpup Directory) is an X.500 DUA interface for the X Window Sys-
tem. POD isa firstattemptat a multiwindow directory tool. It
offers a simplified interfaces to the basic X.500 operationsof read,
search, listand modify entry.
POD does notprovideany sophisticated access to theDSA. Operations
are performed synchronously. The Directory is thus presented as is,
i.e. a hierarchicaltree ofinformation, with the user required to
"navigate" the DIT in order to locate required information.
POD is available as part of the ISODE release from version 6.0
onwards.
COMPLETENESS
88 standard:strong authentication not implemented
INTEROPERABILITY
Believed to be compliant, though untested.
PILOT CONNECTIVITY
DUA Connectivity: POD is in use in many directory pilots, certainly
including PARADISE and the Internet.
BUGS
Bugsto x500@brunel.ac.uk
INTERNETWORKINGENVIRONMENT
TP0 over TCP/IP (as ISODE)
HARDWARE PLATFORMS
MostUNIX machines
SOFTWARE PLATFORMS
UNIX
MIT X libraries (release 11 version 4)
ISODE/QUIPU libraries (version 6.7 upwards)
AVAILABILITY
Openly available as part of the ISODE release. Sources are freely
available for commercial or non-commercial use from:
src.brunel.ac.uk [134.83.128.3]
Files are:
x500/pod.tar.Z
x500/sd.tar.Z
Contacts:
Andrew.Findlay@brunel.ac.uk +44 1 895 74000 x 2512
Damanjit.Mahl@brunel.ac.uk +44 1 895 74000 x 2946
x500@brunel.ac.uk
Postal Address:
Andrew Findlay
Computer Centre
Brunel University
Cleveland Road,
Uxbridge, Middlesex
UB8 3PH
United Kingdom
NAME
psiwp
Performance Systems International Inc.
LAST MODIFIED
July, 1991
KEYWORDS
Available via FTP, DUA LightWeight Client, DUA Only, Free, Limited
Functionality, Macintosh, Needs ISODE, Source
ABSTRACT
psiwp is a MacintoshFront End to White Pages service. It is a
graphical user interface implementing a partial-DUA. It is based on
the ISODE QUIPU X.500 implementationand theDirectory Assistance
Protocol (DAP).
psiwp is a Macintoshapplication tailored specifically to provide
easyaccess to the Directoryfor thepurposes of performing White
Pages searches. Implements User-Friendly Naming scheme developed in
IETFOSI-DS Working Group.
psiwp implements a DirectoryAssistance Protocol (DAP) client.
COMPLETENESS
Compliant with X.500standards to the extentthat the QUIPU implemen-
tation is.
INTEROPERABILITY
Successfullyinteroperates with QUIPU DSAs
PILOT CONNECTIVITY
Being used in the White Pages Pilot Project.
BUGS
Support is available(for registeredusers of psiwp only) from
psiwp-help@psi.com.
CAVEATSAND GENERAL LIMITATIONS
psiwp is nota general-purpose DUA. It was designed to be a special-
purpose front-end for performing White Pagessearches and thus, in
the interests of simplification, does not provide the full range of
functionality supported by the X.500standard. A Directory Assistance
server (available aspart ofthe ISODE distribution)must also be run
by sites that do notwant torun psiwp against either of thetwo
White Pages Pilot Project service machines, wp1.psi.net and
wp2.psi.net.
INTERNETWORKINGENVIRONMENT
Runson Macintoshes as a Finder or MultiFinder application.
HARDWARE PLATFORMS
Runson Macintoshes that support MacTCP. Requires anethernet board
or AppleTalkconnectivity. At least 1MB of memory isrequired, and
while psiwp will runon mostforms of Macintoshes, aMac-II is recom-
mended.
SOFTWARE PLATFORMS
Requires MacTCP 1.0 or later, and Finder (orMultifinder) 6.x (Finder
7.0 WILL NOTWORK). RequiresISODE Version 6.8 or later.
AVAILABILITY
psiwp is shareware availablefor anonymous ftp from uu.psi.com
[136.161.128.3] in pilot/PSIWP.Hqx.A nominal fee is charged upon
registrationas a PSIWP user.
Source code to the psiwp applicationmay be licensedfrom PSI Inc.
as part of PSI's Software Source Distribution (SSD). Email to
ssd-info@psi.com
willelicit an automatic response containinginformation on the SSD.
Ordering informationmay be obtainedby sending electronic mail to
ssd-order@psi.com
or contacting PSI at
Performance Systems International Inc.
11800 Sunrise ValleyDrive
Suite 1100
Reston, Virginia 22091.
1.703.620.6651
1.800.82PSI82 (1.800.827.7482)
1.703.620.4586 (fax)
NAME
QUIPU
ISODE
LAST MODIFIED
July, 1991
KEYWORDS
API,Available via FTAM, Available via FTP, CLNP, DEC Ultrix,
DSA/DUA, Free, HP, MIPS, Macintosh, MultipleVendor Platforms, OSI
Transport, RFC-1006,Source,Sun, UNIX, X Window System, X.25
ABSTRACT
QUIPU is part of theISODE which is an openly available implementa-
tionof the upper layers of OSI. QUIPU provides a X.500 Directory
System Agent(DSA) and a setof Directory User Agents (DUA) aimed at
different terminal types andmodes of interaction
QUIPU was first publicly demonstrated at ESPRIT in November 1988.
QUIPU is being used extensively in the European PARADISE project, the
White Pages Pilot Project and the Australianpilot.A QUIPUDSA is
being used at the ROOT node of the Pilot DITand is being used as
mostcountrylevel DSAs.
QUIPU provides its own solutions to area notspecified by the 1988
standards such as replication and access control.
COMPLETENESS
QUIPU is aligned to the 1988ISO IS and the NIST OIWDirectory Imple-
mentors Guide Version 1, with the following exceptions:
Strong authentication isnot implemented.
QUIPU does not enforce the bounds constraints onattributes,
filters or APDU size.
T.61 string formatting characters are not rejected.
If a DN is supplied withno password in an unprotected simple
bind, QUIPU doesnot always check to seeif the DN exists. If
the DSA connected to cansay authoritatively theDN doesnot
exist, the association is rejected. However, ifa chainopera-
tion is requiredto check the DN, the bind IS allowed.
When comparing attributes of UTCtime syntax, if the seconds field
is omitted, QUIPU does not perform the match correctly (i.e., the
seconds field inthe attribute values should be ignored,but are
not).
QUIPU always supplies the optional Chaining argument ``origina-
tor'' even if the CommonArgument``requestor'' is used.
QUIPU always supplies the optional Chaining argument ``target''
even if the baseobject in the DAP arguments is the same.
The object class``without an assigned object identifier'' is not
recognized unless the ``alias'' object class is also present.
Non Specific SubordinateReferences are never followed by a QUIPU
DSA, butthey are passedon correctly tothe client if generated.
INTEROPERABILITY
QUIPU has interworked with anumber of otherimplementations, and has
no know problems in such interworking.
PILOT CONNECTIVITY
QUIPU is in use in many directory pilots, certainly including PARAD-
ISE and the White Pages Pilot Project.
BUGS
Problems should be reported to quipu-support@cs.ucl.ac.uk.
CAVEATSAND GENERAL LIMITATIONS
None.
INTERNETWORKINGENVIRONMENT
QUIPU users TP0 overX.25, CONS and TCP (using RFC-1006) or TP4 over
SunLink OSI.
The DSA knows about the problems of unconnected networks andmakes
chain/refer choices based onthe network connectivity. Using this an
X.25only DSA can access data from an Internet only DSA by chaining
operations through aDSA connected to both networks.
HARDWARE PLATFORMS
[No information provided--Ed.]
SOFTWARE PLATFORMS
The ISODE and QUIPU runs on native Berkeley (4.2, 4.3) and AT&T Sys-
tem V, in addition to various other UNIX-like operating systems. No
kernel modificationsare required.
AVAILABILITY
The ISODE isnot proprietary, but itis not in the public domain.
Thiswas necessary to include a "hold harmless" clause in the
release. The upshotof all this is that anyone can get a copy of the
release and do anything theywant with it, but no one takes any
responsibility whatsoever for any (mis)use.
DISTRIBUTION SITES
The FTP or FTAM distributions of ISODE-7.0 consists of 3 files. The
source and main ISODE-7.0 distribution is inthe file isode-7.tar.Z
which is approximately 4.7MBin size.
LaTeX sourcefor theentire documentset canbe found in theisode-
7-doc.tar.Z file (3.5MB). Alist ofdocuments can be found in the
doc/directory of the sourcetree.
A Postscriptversionof the five volume manual can be found in the
isode-7-ps.tar.Z file (4.7MB).
1. FTP
If you can FTP to theInternet, then use anonymous FTP to
uu.psi.com [136.161.128.3] toretrieve the files in BINARY
mode from theisode/ directory.
2. NIFTP
If you run NIFTP overthe public X.25or overJANET, and are
registered inthe NRSat Salford, youcan useNIFTP with usen-
rame "guest" and yourown name as password, to access
UK.AC.UCL.CS to retrieve the files from the <SRC> directory
3. FTAM on the JANET, IXI or PSS
The sources are available by FTAM from UCL over X.25 using
JANET(DTE 00000511160013),
IXI(DTE 20433450420113) or
PSS(DTE 23421920030013)
all with TSEL"259" (ASCII encoding).Use the"anon" user-
identity and retrievethe files from the src/directory. The
file service is provided by the FTAM implementation in ISODE
6.0 or later (IS FTAM).
4. NORTH AMERICA
For mailings in NORTHAMERICA, send acheck for 375 US Dollars
to:
University ofPennsylvania
Department ofComputer and Information Science
MooreSchool
Attn:David J. Farber(ISODE Distribution)
200 South 33rd Street
PhilaDelphia,PA 19104-6314
US
+1 215 898 8560
Specify either (a) 1600bpi 1/2-inch tape, or (b) Sun 1/4-inch
cartridge tape. The tape will be written in tar format and
returned witha documentationset. Do not send tapesor
envelopes. Documentation only is thesame price.
5. EUROPE (tape anddocumentation)
For mailings in EUROPE, send a chequeor bankers draft and a
purchase order for 200 PoundsSterling to:
Department ofComputer Science
Attn:NatalieMay/Dawn Bailey
University College London
GowerStreet
London, WC1E 6BT
UK
For information only:
Telephone: +44 71 380 7214
Fax: +44 71 387 1397
Telex: 28722
Internet: natalie@cs.ucl.ac.uk,dawn@cs.ucl.ac.uk
Specify either (a) 1600bpi 1/2-inch tape, or (b) Sun 1/4-inch
cartridge tape. The tape will be written in tar format and
returned witha documentationset. Do not send tapesor
envelopes. Documentation only is thesame price.
7. EUROPE (tape only)
Tapeswithouthardcopy documentation can be obtained via the
European Forum for Open Systems (EurOpen, formerly known as
EUUG). The ISODE 7.0distribution iscalled EurOpenD14.
EurOpen Software Distributions
c/oFrank Kuiper
Centrum voor Wiskunde en Informatica
Kruislaan 413
1098 SJ Amsterdam
TheNetherlands
For information only:
Telephone: +31 20 5924121 (or: +31 20 5929333)
Telex: 12571mactr nl
Telefax: +31 20 5924199
Internet: euug-tapes@cwi.nl
Specify one of:
- 1600bpi 1/2-inch tape: 140Dutch Guilders
- Sun1/4-inch cartridge tape(QIC-24format):
200Dutch Guilders
If you require DHL this is possible and will be billed
through. Note that if you are not a member of EurOpen, then
thereis an additional handling fee of 300 Dutch Guilders
(please enclose a copy of your membership or contribution pay-
ment form when ordering). Donot send money,cheques, tapes
or envelopes,you will be invoiced.
8. PACIFIC RIM
For mailings in the Pacific Rim, senda cheque for 300 dollars
Australian to:
IsodeDistribution
(AttnAndrew Waugh)
723 Swanston St,
Carlton, VIC 3053
Australia
For information only:
Telephone: +61 3282 2615
Fax: +61 3282 2600
Internet: ajw@mel.dit.csiro.au
Please specify the media youdesire: (a) 1/2-inchtape at
1600bpi, 3200bpi, or 6250bpi; or (b) Sun 1/4-inch cartridge
tape in either QIC-11, QIC-24or QIC-150 format; or (c) Exa-
byte2.3 Gigabyte or 5 Gigabyte format.The tape will be
written in tar formatand returned with a documentation set.
Do not send tapesor envelopes. Documentation only is the
same price.
NAME
SD
Brunel University
LAST MODIFIED
November, 1991
KEYWORDS
DUA Only, Free, Included in ISODE, Multiple Vendor Platforms, Needs
ISODE, RFC-1006, UNIX, X Window System
ABSTRACT
SD (Screen Directory) is an X.500 DUA interface for character mapped
screens. SDis an early attempt to provide quick, easy and user
friendly access to the Directory. The following directory operations
are supported: read,search and list.
SD does not provide any sophisticated accessto the DSA. Operations
are performed synchronously. The Directory is thus presented as is,
i.e. a hierarchicaltree ofinformation, with the user required to
"navigate" the DIT in order to locate required information.
SD is available as part of the ISODEreleasefrom version 6.0
onwards.
COMPLETENESS
88 standard:strong authentication not implemented
INTEROPERABILITY
Believed to be compliant, though untested.
PILOT CONNECTIVITY
DUA Connectivity: SDis in use in many directory pilots, certainly
including PARADISE and the Internet.
BUGS
Bugsto x500@brunel.ac.uk
INTERNETWORKINGENVIRONMENT
TP0 over TCP/IP (as ISODE)
HARDWARE PLATFORMS
MostUNIX machines
SOFTWARE PLATFORMS
UNIX
BSD curses library
ISODE/QUIPU libraries (version 6.7 upwards)
AVAILABILITY
Openly available as part of the ISODE release. Sources are freely
available for commercial or non-commercial use from:
src.brunel.ac.uk [134.83.128.3]
Files are:
x500/pod.tar.Z
x500/sd.tar.Z
Contacts:
Andrew.Findlay@brunel.ac.uk +44 1 895 74000 x 2512
Damanjit.Mahl@brunel.ac.uk +44 1 895 74000 x 2946
x500@brunel.ac.uk
Postal Address:
Andrew Findlay
Computer Centre
Brunel University
Cleveland Road,
Uxbridge, Middlesex
UB8 3PH
United Kingdom
NAME
UCOM.X 500 (tm)
E3.X
LAST MODIFIED
November, 1991
KEYWORDS
API,Bull, Commercially Available, DEC Ultrix, DSA/DUA, HP, IBM PC,
IBM RISC, Multiple Vendor Platforms,Philips, RFC-1006, Siemens, Sun,
UNIX, X.25
ABSTRACT
UCOM.X 500 includes a Directory System Agent(DSA), a directory
access API, and a set of Directory User Agents (DUAs) for different
terminal types. UCOM.X 500 is a commercial product based on PIZARRO,
the researchprototype developed at INRIA byChristian Huitema's
team.
Somecharacteristicsof the DSA are:
- The DAP and DSP protocols are providedconformant withthe 1988
CCITT X.500 recommendations.
- The DIB is maintained in ASN.1encodedformat in the Unix file
system. Utilities are provided to load and dump the DIB from and
to ASCIItext files.
- The DIT structure is held in main memory. Additionally, fre-
quently used attributes may be held in inverted tables in memory
to speedup searches.
- Knowledge management: knowledge on managed domains is stored in
UCOM.X specific attributes of the DSA entries.
- All X.500 (88)as wellas someX.400 (88) object classes,
attributes and syntaxes are supported. Users maydefine their own
classes and attribute types.
- Schemamanagement: object class and attribute definitions are
enforced.
- Simpleauthentication is provided; strong authentication is not
currently supported.
- Accesscontrol: private mechanisms areprovided to allow access
control lists tobe specified for parts of the DIT, to control
modifications, and to specify access restrictions on attributes.
The UCOM.X 500 API provides the DAP protocolto applicationsaccess-
ing the Directory. It is a synchronous API which automatically
manages referrals. Several DUAs using the API, are available. These
include command lineand full screeninterfaces for users with ordi-
naryterminals, and an X-Windows user interface (12/91). An X/Open
XDS API willbe offered shortly.
UCOM.X 500 is used by Frenchresearch centers involved in PARADISE, a
COSINE project. A distributed application tocontroldocument
transfer in a large French hospital,has been built on the UCOM.X 500
API.It is being used for distributed applications management in the
French Post Office.
COMPLETENESS
UCOM.X 500 conforms to 1988 X.500 series of recommendations,as
specified inparagraph 9 of X.519, with the exception of strong
authentication.
INTEROPERABILITY
Interoperability tests with other implementations, e.g. QUIPU, have
beenmade inthe PARADISE project. UCOM.X 500 is used in theFrench
PARADISE pilot.
PILOT CONNECTIVITY
DSA and DUA connectivity to the PARADISE pilots. See caveats.
BUGS
UCOM.X 500 is a commercial product. As such,it is supportedand bugs
are fixed when detected. Bugreportscan be sent to our support team
via electronic mail.
CAVEATSAND GENERAL LIMITATIONS
The DIT structure isstored in main memory which means that the order
of magnitudeof the number of objects supported per DSA is 10,000. By
1992100,000objectswill besupported.
Not all syntaxes defined in the COSINE and Internet Schema are
currently supported,and theDUAs donot display photo attributes.
The InternetDSP is not supported.
INTERNETWORKINGENVIRONMENT
UCOM.X 500 uses RFC-1006 with TCP/IPand TP0with X.25.
HARDWARE PLATFORMS
UCOM.X 500 runs on: Sun 3, Sun 4, IBM RS 6000, Philips P 9000, DEC
machines, Bull DPX 2000, HP 9000/300, Siemens IN 6000 and 386-based
PCs. It caneasily be ported to anyUNIX machine.
Windows 3 and Macintosh DUAswill beavailable by Spring 1992.
SOFTWARE PLATFORMS
UCOM.X 500 is portable to any UNIX-like operating system. Ithas been
ported to: AIX, UNIXSystem V.3, SUNOS 4, Ultrix, HP-UX, SCO Unix,
Interactive,BOS (Bull Operating System), and SPIX.
The UNIX file systemis usedto holdthe DIB.
AVAILABILITY
UCOM.X is commercially available. Contact:
Dominique Fayet
E3.X
TourAnjou
33 Quai de Dion Bouton
92 814 Puteaux CEDEX
FRANCE
Tel:(+33) 140 90 08 15
Fax:(+33) 147 74 58 87
Philippe Brun
C=fr;A=atlas;P=e3x;O=e3x;S=Brun
phb@e3x.fr
NAME
ud
University of Michigan
LAST MODIFIED
November, 1991
KEYWORDS
Available via FTP, DUA LightWeight Client, Free, Source, UNIX, Mul-
tiple VendorPlatforms
ABSTRACT
ud is a command linebased directoryapplication useful for display-
ing and modifying white pages information about people. It runs on
top of the DIXIE protocol (describedin RFC1246). ud was developed
to run underUnix and is currently in beta release within U-M staff
and a few other places that have heard of it.
Features include theabilityto display and modify the following
attributes: title, description, commonName, uid, mail, postalAddress,
homePostalAddress, telephoneNumber, facsimileTelephoneNumber, home-
Phone.
COMPLETENESS
ud uses the DIXIE protocol to accessX.500 and thus is subject to the
samecompleteness restrictions as DIXIE. Itprovides Read, Search,
and Modify capabilities.
INTEROPERABILITY
Works with the DIXIEserver,which works with the QUIPU DSA and DAP
library.
PILOT CONNECTIVITY
It has been tested (in conjunction with the DIXIE server) inboth the
Internet andPARADISE pilots.
BUGS
No outstanding bugs are known. But reports should be sent to
x500@itd.umich.edu.
CAVEATSAND GENERAL LIMITATIONS
ud is heavily oriented to white pages information and thus general
access to the DIXIE protocolis not provided.
INTERNETWORKINGENVIRONMENT
ud uses the DIXIE protocol and thus TCP to communicate with the DIXIE
server.
HARDWARE PLATFORMS
ud is known to run on Sun 3s, Sun 4s, and Vaxen.
SOFTWARE PLATFORMS
SunOS 3.5, SunOS 4.1.1, BSD 4.3 Unix.
AVAILABILITY
Thissoftware is openly available. It may be obtained by anonymous
FTP from terminator.cc.umich.edu in the directory ~ftp/x500.
Thissoftware was developed at the University of Michigan byBryan
Beecher of the ITD Research Systems Unix Group and is subject to the
following copyright.
Copyright (c) 1991 Regents of the Universityof Michigan. All rights
reserved. Redistribution and use insource and binary formsare per-
mitted provided thatthis notice is preserved and that due credit is
given to theUniversity of Michigan at Ann Arbor. The name of the
University may not be used to endorse or promote products derived
fromthis software without specific prior written permission. This
software is provided"as is"withoutexpressor implied warranty.
NAME
VMS-ISODE
Computer Science Department of Massey University
LAST MODIFIED
November, 1991
KEYWORDS
API,Available via FTP, DSA/DUA, Free, NeedsISODE, RFC-1006, Source,
VMS
ABSTRACT
VMS-ISODE isa reasonably complete port of ISODE version 7.0. It sits
on top of several TCP implementations for VMS (UCX, Multinet, CMU and
Wollongong) and alsoPSI X.25.
See entry for QUIPU/ISODE for a detailed descriptionof the DSA/DUA.
COMPLETENESS
See entry for QUIPU/ISODE.
INTEROPERABILITY
See entry for QUIPU/ISODE.
PILOT CONNECTIVITY
Not tested.
BUGS
VMS related problemsshould be sent to PKay@massey.ac.nz
CAVEATSAND GENERAL LIMITATIONS
None.
INTERNETWORKINGENVIRONMENT
See entry for QUIPU/ISODE.
HARDWARE PLATFORMS
VAX hardware
SOFTWARE PLATFORMS
VMS v5.0 or greater
AVAILABILITY
The VMS partof the package is freely available. Anonymous FTP from
cc-vms1.massey.ac.nz(130.123.1.4).
NAME
VTT X.500
Technical Research Centre ofFinland
LAST MODIFIED
November, 1991
KEYWORDS
API,Apollo,CLNP, Commercially Available, DSA/DUA, IBM PC, Multiple
Vendor Platforms, RFC-1006, Sun, X.25
ABSTRACT
VTT X.500 contains afull distributed DSA and a subroutine call to
dua ( call_dua(parameters)).This subroutineis linked to user's pro-
cess. Thereare twoways for dua tocommunicate with our DSA called
dsacvops: a fast communication through shared memoryfor duaand dsa
in the same computerand a complete OSI-stack for communicating in
DAP-protocolwith remote dsa's whichcan be any implementation of
X.500 dsa, not necessarily dsacvops. DSA communicates with other
dsasthrougha full OSI-stack with protocol DSP or with a shorter
stack when both dsasare dsacvops-processes. dsacvops contains a
special purpose database DIB. VTT X500 contains caching of read and
search results, access controls (as in AnnexF of X.501), object
classes and attribute types as in X.520 and X.521 and simpleauthen-
tication with unprotected passwords in bind.The network level can be
X.25or TCP/IP. There are test duas,duacvops, duauser, witha simple
userinterface. Certificatesfor strong authentication are included
to x509dua and x509duacvops.VTT X500 is realized with program
development tools CVOPS and CASN, the code is in C-language and uses
UNIXSystem V. The code is fairly easy to port to other operating
systems. VTT X500 was made for Smail e-mailproductof Nokia Data
Systems.
COMPLETENESS
Complete DAPand DSPof 1988X.500 Recommendations are implemented.
There are the following omissions: multicasting is not implemented,
strong authentication of calls to dsa (optional signing of DAP and
DSP-calls, strong authentication in bind, security error, security
parameters in commonarguments), T61alternative in CASE IGNORE and
CASEEXACT STRING, Criteria-syntax, TeletexTerminalIdentifier syntax.
INTEROPERABILITY
Interoperability with ISODE QUIPU 6.0 has been tested, no formal test
suite was used.
PILOT CONNECTIVITY
Not tested: It should work in principle, buthas notbeen tested.
BUGS
No known bugs at themoment.
CAVEATSAND GENERAL LIMITATIONS
Object identifiers for object classes and attribute types can
currently have only the form{2 5 6 x} or {25 4 x},x<256. Changing
the directory schemarequires code writing.
INTERWORKING ENVIRONMENT
RFC-1006 with TCP/IP, TP0 with X.25,TP4 with X.25 availableby
agreement.
HARDWARE PLATFORMS
Sun-3, Sun 386, Apollo, a version ofdua forIBM PC will be forthcom-
ing 1991.
SOFTWARE PLATFORMS
UnixSystem V. Our own database and databasemanagement system. Uses
CVOPS protocol development tool.
AVAILABILITY
Commerciallyavailable. Contact
AskoVilavaara
Telecommunications Laboratory
Technical Research Centre ofFinland
Otakaati 7 B, 02150 Espoo, FINLAND
Telephone:+358 0 4565641
FAX:+358 0 455 0115
E-mail: Asko.Vilavaara@tel.vtt.fi
Henryka Jormakka
Telecommunications Laboratory
Technical Research Centre ofFinland
Otakaati 7 B, 02150 Espoo, FINLAND
Telephone:+ 358 0 456 5662
FAX:+358 0 455 0115
E-mail: Henryka.Jormakka@tel.vtt.fi
NAME
WIN(tm)/DS
The Wollongong Group, Inc.
LAST MODIFIED
November, 1991
KEYWORDS
API,CLNP, Commercially Available, DSA/DUA, MultipleVendor Plat-
forms, OSI Transport, RFC-1006, Source, UNIX, X Windows, X.25
ABSTRACT
WIN/DS is animplementation of OSI DirectoryServices aligned with
the ISO 1988X.500 IS and NIST Stable Implementors Agreements. WIN/DS
includes both a Directory User Agent(DUA) and a Directory System
Agent (DSA).The product supports all Directory Services operations,
object classes and attributes. It provides support for managing the
Directory Information Tree (DIT) with facilities to control structure
rules and their enforcement. WIN/DSalso provides solutionsto areas
not specified by the1988 standards,such asreplication andaccess
control.
COMPLETENESS
Wollongong closely follows the NIST OIW Stable Implementors'Agree-
ments. See also QUIPU.
INTEROPERABILITY
WIN/DS has interoperated with other X.500 implementations attrade
shows (CeBITand Interop) and at strategic customer sites.
PILOT CONNECTIVITY
[No information provided--Ed.]
BUGS
Requests forproductenhancement andmodification should be sent to
support@twg.com.
CAVEATSAND GENERAL LIMITATIONS
[No information provided--Ed.]
INTERNETWORKINGENVIRONMENT
TCP/IP (RFC1006)
TP0
TP2
TP4
OSI TP[0/2,4] & TCP/IP dual stack gateway
Ethernet
X.25
Ethernet/X.25 gateway
ES-IS
IS-IS
Interface toOSI transport via the TLI
Interface tothe Data Link Layer viathe DLPI
STREAMS and DLPI compliant 3rd partynetworkinterfaces
HARDWARE PLATFORMS
End-user binary product -
386/i486 with UNIX System V (AT&T, Intel, INTERACTIVE, SCO)
Apple Macintosh withA/UX
Portable source code-
UNIXSVR3, SVR4, BSD
single- or mutli-processor 680x0, 880000, 386/i486
SOFTWARE PLATFORMS
See above.
AVAILABILITY
WIN/DS is commercially available from:
The Wollongong Group, Inc.
1129San Antonio Road
PaloAlto
CA 94303
Sales and Information: :415/962-7100 California
703/847-4500 Wash D
+32-2-718-0311 Belgium
NAME
X.500 DUA process
3ComCorporation
LAST MODIFIED
July, 1991
KEYWORDS
CLNP, Commercially Available, DUA Only, Multiple Vendor Platforms, X
Window System, X.25,3Com
ABSTRACT
The DUA process runson 3Com's dual-stack OSI/TCP terminal server,
scheduled tobe released in mid-June1991. It provides Presentation
Address resolution for names, on behalf of the VTP application: when
the user attempts anoutgoing connection ("VTP <name>" or "connect
<name>"), <name> gets mappedto its Presentation Address.
The DUA process supports theAddEntry, RemoveEntry, and Search opera-
tions. Via a menu-driven command, the system administrator can con-
figure any of these operations, thensend the request to theDSA. He
would use the AddEntry operation to enter a resourcename and its
corresponding physical address in the DIB, the DeleteEntry operation
to remove the name and its physical address,and theSearch operation
(with "filter" as anoption)for a display of all registerednames
or, given a name, a display of the name's physical address.
Regarding unbinding from a DSA, the system administrator could use an
UnbindDSA command orset a timer which, onceexpired, would automati-
cally perform the unbinding. The binding toa DSA, on the other
hand, is transparent, provided the system administrator has set a DSA
address. The binding is triggered by eitheran outgoing connection
attempt or an operation request sentto the DSA.
The schema supportedby the DUA consists of the following sequence of
object classes: Country, Organization, OrganizationalUnit (up to 3
levels of OrganizationalUnits are allowed), ApplicationProcess, and
ApplicationEntity. Their respectiveattributes are CountryName,
OrganizationName, OrganizationUnitName, CommonName, and Presenta-
tionAddress. The CommonNameof the ApplicationEntity is always "vt"
for VTP and is transparent to the system administrator.
COMPLETENESS
Compliance with the ISO/IEC 9594 standards.
Handling referrals not yet implemented.
Schema supported: Country, Organization, OrganizationalUnit,
ApplicationProcess, and ApplicationEntity.
Authentication not supported.
INTEROPERABILITY
Interoperability with the ISODE QUIPU Directory Service and any DSA
which strictly meetsthe ISO/IEC 9495 standards.
BUGS
[No information provided--Ed.]
CAVEATSAND GENERAL LIMITATIONS
Deleting an entry will fail if the DUA is interacting with a6.0
based version of QUIPU. This is a bug in QUIPU, andversion7.0
release willhave itfixed.
Adding a CountryNameis disallowed if the DUA is bound to QUIPU.
Thisdecision was made because to add a country in QUIPU, one needs
to bind as the manager of the DSA holding the root EDB file,and such
information may not always be available to the system administrator.
Also, our binding isdone transparently.
INTERNETWORKINGENVIRONMENT
OSI environments with the complete OSI stack, supporting CLNS and
TP4.
HARDWARE PLATFORMS
3Com's OSI/TCP CS/2000 and CS/2100.
SOFTWARE PLATFORMS
The "SW/2000-OT Vers1.0" software runs on 3Com's OSI/TCP CS/2000 and
CS/2100, both stand-alone systems.
AVAILABILITY
The dual-stack OSI/TCP terminal server and its "SW/2000-OT Vers 1.0"
software is available from:
3ComCorporation
5400Bayfront Plaza
Santa Clara,CA 95054
Information:Cyndi Jung
(408) 764-5173
cmj@3Com.COM
NAME
Xdi
Bellcore
LAST MODIFIED
November, 1991
KEYWORDS
DUA Only, DUA Connectivity, Available via FTP, Free,Source,Needs
ISODE, X Window System, RFC-1006, CLNP, UNIX, X.25
ABSTRACT
Xdi is a Directory User Agent (DUA) for the X WindowSystem. In
addition to providing a user-friendly interface,it supports Directory
interactionsof different levels of complexity. Users can select dif-
ferent window screens to browse, search and modify the Directory.
There are two different search screens for name based searchand
attribute based search. It is simpleto use for novice usersbut is
alsouseful for moreadvanced users to formulate complex search
filters. Xdi also supports "user-friendly naming" in many cases so
thatusers are not required to know X.500 naming format.
COMPLETENESS
The Xdi interface does not support accesses to Delete and Add DAP
operations as in the88 Directory Standard. Read, Search, and most
Modify operations are fully supported. Thereare no facilities to
modify the RDNs of entries. Strong authentication isnot implemented.
INTEROPERABILITY
Believed to be compliant. Only tested against ISODE/QUIPU DSAs.
PILOT CONNECTIVITY
DUA Connectivity
BUGS
Sendbug reports to sywuu@thumper.bellcore.com
CAVEATSAND GENERAL LIMITATIONS
Noneknown.
INTERNETWORKINGENVIRONMENT
Sameas ISODE.
HARDWARE PLATFORMS
Thissoftware has been tested on SUN4. It isexpected that the
software is portableto SUN3and other UNIX machines.
SOFTWARE PLATFORMS
Xdi is expected to run on ISODE (release 6.8upwards) in UNIX
environment. The 'xdi' directory has been designed to fit directly
intothe ISODE source tree. Xdi requires X11R4, the associated Xt
toolkit and Athena widget libraries. Also see the operatingenviron-
ments of ISODE.
AVAILABILITY
The Xdi software is available via anonymous FTP from
thumper.bellcore.comin filepub/xdi.tar.Z. Source code and execut-
ables can befreely distributed or modified for non-commercial and
non-profit use provided thatall copyright notices, permission and
nonwarranty notice included in the software distribution remain
intact.
For further information contactSze-Ying Wuu at
sywuu@thumper.bellcore.com.
NAME
Xds
CSIRO Division of Information Technology
LAST MODIFIED
November, 1991
KEYWORDS
Dua only, Free, Limited Functionality, NeedsISODE, RFC-1006, Source,
Sun,X-Windows
ABSTRACT
Xds is a DUAdesigned for users who have little or no knowledge of
X.500. Its intended to be used, for example,by a receptionist who
has to answer such queries as 'CouldI have the telephone number of
Andrew who works in Research?'. The display is customized for the
particular organization and the results of the search are presented
in the format of a business card. Itis possible to customize the
displayed information.
COMPLETENESS
Xds does notprovideuser access to all the servicesprovided by
X.500. Instead, Xdsuses X.500 services to provide the specific
functions for which it is designed to provide.
Conforms to section 9 of X.519.
INTEROPERABILITY
Onlytested against the QUIPU (ISODE) DSA.
No known bugs, but we would be interested inany found. Contact
Andrew Waugh(ajw@mel.dit.csiro.au)
PILOT CONNECTIVITY
Not tested.
BUGS
No known bugs, but we would be interested inany found. Contact
Andrew Waugh(ajw@mel.dit.csiro.au)
CAVEATSAND GENERAL LIMITATIONS
The user canonly bind as the anonymous user.
INTERNETWORKINGENVIRONMENT
Usesthe QUIPU (ISODE 7.0) libraries.
HARDWARE PLATFORMS
Xds runs on Sun SPARCstations. We have not tested Xds on other
hardware platforms, but it should run on other hardware which sup-
ports ISODE-7.0 and X Windows.
SOFTWARE PLATFORMS
Xds requiresISODE-7.0 and X11 Version 4 with the Athena Widgets.
AVAILABILITY
The Xds software will be distributedfree toany non-commercial site
provided
i) they do not pass the code on to any other site (rather they
should askthe other site to contact us directly).
ii) they do not make money outof fromthe useor saleof the
software.
iii) they inform us of any problems or possibleimprovements
that they would like to see made.
Commercial sites should contact us.
For further information contact:
Andrew Waugh
CSIRO Division of Information Technology
723 SwanstonSt
Carlton VIC 3053
AUSTRALIA
Phone +61 3 282 2615
Fax +61 3 282 2600
Email ajw@mel.dit.csiro.au
NAME
xdua
CSIRO Division of Information Technology
LAST MODIFIED
November, 1991
KEYWORDS
DUA Only, Free, Multiple Vendor Platforms, Needs ISODE, source, Sun,
X Window System
ABSTRACT
The xdua is a DUA designed to be used by DSAmanagers who have suffi-
cient X.500 knowledge to manipulate the Directory Information Tree
(DIT). It's typical use is to maintain the information stored on a
DSA.The xdua has a Macintosh style interface. Thissimplifies
browsing theDIT hierarchy.A user can traverse theDIT levels by
using a standard mouse. Thexdua supports the X.500operations of
add,modify,delete,search and show.
COMPLETENESS
Usesthe QUIPU (ISODE) dsap interface to provide theX.500 opera-
tions.
Conforms to section 9 of X.519.
INTEROPERABILITY
Onlytested against the QUIPU (ISODE) DSA.
PILOT CONNECTIVITY
[No information provided--Ed.]
BUGS
No known bugs, but we would be interested inany found. Contact Brian
May (
Brian.May@mel.dit.csiro.au)
CAVEATSAND GENERAL LIMITATIONS
The executable code is largeas it uses the X11R4 and DiSh libraries.
The xdua is in the testing phase.
INTERNETWORKINGENVIRONMENT
As supportedby ISODE.
HARDWARE PLATFORMS
The xdua runs on SunSPARCstations and probably on other hardware
which supports ISODE-7.0 andX Windows.
SOFTWARE PLATFORMS
The xdua requires ISODE-7.0 and X 11Version4 with the Athena Widg-
ets and the Xt toolkit.
AVAILABILITY
We will distribute it free to any non-commercial site provided
i) they do not pass the code on to any other site (rather they
should askthe other site to contact us directly).
ii) they do not make money outof fromthe useor saleof the
software.
iii) they inform us of any problems or possibleimprovements
that they would like to see made.
Commercial sites should contact us directly. For further information
contact:
Brian May
CSIRO Division of Information Technology
723 SwanstonSt,
Carlton,
Victoria 3053,
Australia
Phone +61 3 282 2613
Fax +61 3 282 2600
Brian.May@mel.dit.csiro.au
NAME
XLU
Brunel University
LAST MODIFIED
November, 1991
KEYWORDS
Available via FTAM, Available via FTP, DUA Only, Free, Multiple Ven-
dor Platforms, NeedsISODE, RFC-1006, Source, UNIX
ABSTRACT
XLU (X LookUp) is anX.500 DUA interface forthe X Window System.
Developed from POD, XLU can be configured for many differentstyles
of interaction. Example configurations are provided for single window
and multiplewindow (POD-like) use.
XLU implements the `User-Friendly Naming' search strategy and also
has a form-filling search mode. Asynchronousdirectory operations are
used.
Fulladd andmodify functions are provided, with theabilityto
tailor the modify screen to present simple subsets of the available
attribute.
At the time of writing (October 1991) XLU was in beta test.
COMPLETENESS
88 standard: strongauthentication not implemented.
INTEROPERABILITY
Believed to be compliant, though untested.
PILOT CONNECTIVITY
DUA Connectivity: Inuse at Brunel and some other sites in the UK and
PARADISE pilots.
BUGS
Bugsto x500@brunel.ac.uk.
CAVEATSAND GENERAL LIMITATIONS
[No information provided--Ed.]
INTERNETWORKINGENVIRONMENT
TP0 over TCP/IP (andothers as ISODE).
HARDWARE PLATFORMS
MostUNIX machines.
SOFTWARE PLATFORMS
UNIX
MIT X libraries (release 11 version 4)
ISODE/QUIPU libraries (version 7.0 upwards)
AVAILABILITY
Sources are freely availablefor commercial or non-commercial use.
Contacts:
Andrew.Findlay@brunel.ac.uk +44 1 895274000 x 2512
Damanjit.Mahl@brunel.ac.uk +44 1 895274000 x 2946
x500@brunel.ac.uk
Postal Address:
Andrew Findlay
Computer Centre
Brunel University
Cleveland Road,
Uxbridge, Middlesex
UB8 3PH
United Kingdom
Anonymous FTP:
src.brunel.ac.uk
x500/xlu.tar.Z
NAME
XT-DUA
X-Tel Services Limited
LAST MODIFIED
November, 1991
KEYWORDS
DUA Only, Multiple Vendor Platforms,Needs ISODE-7.0, RFC-1006 X Win-
dow System, CLNP, X.25, OSI Transport, Sun, Unix, Commercially Avail-
able.
ABSTRACT
XT-DUA provides a X-Windows based user interface to the X.500 direc-
tory. Both Motif and OpenLook styles are supported.
XT-DUA is available in two forms:
as abrowsing tool
as amanagement tool
Browsing features include:
-History- allowing quick accessto previously referenced parts
of the DIT.
-Customizable entry display - allowing subsets of attributes be
displayedwhen showing anentry.
-User Friendly Name (UFN) based searching
-Hypertext-like navigation.
-Supportfor applicationEntitieseg startup of ftam session.
-User friendly name for attributes.
-Supportfor photo and audio attributes.
-Attribute valueon scanline.
-Intelligent choice of entries to display when moving toa new
location in the DIT.
Management features include:
-Creation of newentries.
-Modification ofexisting entries (including RDN) - based on
Quipu EDBformat.
-Deletion of entries.
-Friendly editorof modifying Quipu ACLs.
-Rebinding - authenticated and to named DSA.
-Full configuration of DAP request parameters
COMPLETENESS
XT-DUA provides access to all the X.500 DAP operations. Protocol
completenessis as for QUIPU-7.0.
INTEROPERABILITY
As for the QUIPU-7.0.
PILOT CONNECTIVITY
FullDUA Connectivity to theX.500 Pilot.
BUGS
No known bugs.
CAVEATSAND GENERAL LIMITATIONS
None.
INTERNETWORKINGENVIRONMENT
As for the QUIPU-7.0.
HARDWARE PLATFORMS
As for the QUIPU-7.0.
SOFTWARE PLATFORMS
As for the QUIPU-7.0, with the addition of XWindowsand either Motif
or Open Look.
AVAILABILITY
XT-DUA is commercialsoftware. It isavailable via ftp. Formore
details contact:
Colin Robbins or Graeme Lunt
X-Tel Services Limited
University Park
Nottingham
NG7 2RD
DN: c=GB@o=X-TelServices Ltd
Telephone: +44 602 412648
Fax: +44 602 790278
E-Mail: x500@xtel.co.uk
NAME
xwp
Performance Systems International Inc.
LAST MODIFIED
July, 1991
KEYWORDS
CommerciallyAvailable, DUA Only, Limited Functionality, Multiple
Vendor Platforms, UNIX, X Window System
ABSTRACT
xwp is a graphical user interface tailored specifically to provide
easyaccess to the Directoryfor thepurposes of performing White
Pages searches. It is currently in use as one of user interfaces
available onwp1.psi.net andwp2.psi.net, the two service machines
for the White Pages Pilot Project. Implements User-FriendlyNaming
scheme developed in IETF OSI-DS Working Group.
COMPLETENESS
Compliant with X.500standards to the extentthat the QUIPU implemen-
tation is.
INTEROPERABILITY
Successfullyinteroperates with QUIPU DSAs.
PILOT CONNECTIVITY
[No information provided--Ed.]
BUGS
Bugsto ssd-help@psi.com
CAVEATSAND GENERAL LIMITATIONS
xwp is not ageneral-purposeDUA. Itwas designed tobe a special-
purpose front-end for performing White Pagessearches and thus, in
the interests of simplification, does not provide the full range of
functionality supported by the X.500standard.
INTERNETWORKINGENVIRONMENT
Runsin a BSD UNIX environment supporting the X Windows System.
HARDWARE PLATFORMS
Should be capable ofrunningin any BSD UNIXenvironment that sup-
ports the X Windows system. No special hardware required beyond that
required to support X Windows, BSD UNIX and the ISODE.
SOFTWARE PLATFORMS
Tested underSUNOS 3.x and 4.x; should run under most variants of BSD
UNIX. Requires X Windows Release 3 or later.
AVAILABILITY
xwp is a commercial product that maybe licensed from PSI Inc. as
partof PSI's Software Source Distribution (SSD). Email to
ssd-info@psi.co
willelicit an automatic response containinginformation on the SSD.
Ordering informationmay be obtainedby sending electronic mail to
ssd-order@psi.com
or contacting PSI at
Performance Systems International Inc.
11800 Sunrise ValleyDrive
Suite 1100
Reston, Virginia 22091.
1.703.620.6651
1.800.82PSI82 (1.800.827.7482)
1.703.620.4586 (fax)
NAME
xwp
University of Wisconsin
LAST MODIFIED
July, 1991
KEYWORDS
Free, IBM PC, Multiple Vendor Platforms, Needs ISODE, UNIX, X Window
System
ABSTRACT
The xwp program is asimple browser for the QUIPU/X.500 directory.
It uses OSF/Motif and the X Window System toprovidea convenient
userinterface.
The user interface consists of five different top-level windows: the
mainwindow,the search window, and three option windows. The main
window appears when the program is executed and all others are
reached through its menus. The mainwindow containsCurrentLoca-
tion, Current Descendents, Descendent Filter, Current Information,
and Directory Statussubwindows. The contents of these subwindows
showinformation about the current location of the browser in the
directory tree. Thesearch window contains Search Area, Search
Filter, and Search Results subwindows.
The mouse pointer may be used in themain window to change the
current location of the browser in the directory tree. We can des-
cenddeeper into thetree byclicking the mouse whenit points to a
member of the Current Descendents list. Doing this "moves" the
browser to this new (one level deeper) location in the directory
tree. This causes the main window to be updated as follows:(1) the
selected descendent becomes the new Current Location, (2) its descen-
dents are listed in Current Descendents, and(3) itscontents are
displayed inCurrentInformation. Any problems and messagesfrom the
directory are displayed in the Directory Status portion of the main
window. To move thebrowserup the directory tree (i.e. towards the
root), clickthe mouse pointer on one of thecomponents of the
Current Location. In this way it ispossible to move the browser to
any locationabove its current position (i.e. to anyancestor) in one
mouse click. Doing this causes the main window to be updated as dis-
cussed above. Due to directory-imposed limits, it may not always be
possible to display all the descendents of the current position. In
suchcases (and others) it may be useful to impose afilter on the
descendents to be listed. To do this, position the mouse pointer in
the Descendent Filter box and use the keyboard to type in the desired
filter expression. Typing <RETURN> in this box causes the Current
Descendents list to be updated usingthe newfilter.
xwp was developed atthe University of Wisconsin - Madison Computer
Sciences Department.It is used in conjunction with the ECI mail user
agent project. xwp was written by Robert Lazarus, III.
COMPLETENESS
n/a
INTEROPERABILITY
xwp currently operates with ISODE version 6.0
PILOT CONNECTIVITY
[No information provided--Ed.]
BUGS
xwp should be upgraded to the latestversionof ISODE/QUIPU.
CAVEATSAND GENERAL LIMITATIONS
n/a
INTERNETWORKINGENVIRONMENT
xwp will operate in any environment where Motif, ISODE and QUIPU
operate.
HARDWARE PLATFORMS
xwp has beenrun on IBM PC/RT, soon to run on DecStation 3100.
SOFTWARE PLATFORMS
Berkeley 4.3and Ultrix 3.1
AVAILABILITY
Openly available in May, 1991. Contact hagens@cs.wisc.edu for more
information.
4. References
[CCITT-88] CCITT, "Data Communications Networks Directory,"Recom-
mendations X.500-X.521, Volume VIII - Fascicle VIII.8,
IXth Plenary Assembly, Melbourne, November 1988.
[NIST-88] NationalInstitute of Standards and Technology, "Stable
Implementation Agreements for Open Systems Interconnec-
tion Protocols,"Version2 Edition 1, NIST Special Publi-
cation 500-162, December1988.
5. Security Considerations
Security issues are not discussed inthis memo.
6. Authors' Addresses
RuthLang
SRI International
333 Ravenswood Ave.
Menlo Park, CA 94025
(415) 859-5608
rlang@nisc.sri.com
RussWright
Lawrence Berkeley Laboratory
1 Cyclotron Road
Berkeley, CA94720
(415) 486-6965
wright@lbl.gov
