SRI International
R. Wright
Lawrence Berkeley Laboratory
Editors
January 1992
A Catalog of Available X.500 Implementations
Status of this Memo
-
This emo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo s unlimited.
Abstract
-
The goal of this document is o provide information regarding the availability nd capability of implementations of X.500. Comments and critiques of this document, and new or updated descriptions of X.500 implementations are welcome. Send them to the irectory Information Services nfrastructure (DISI) Working Group (disi@merit.edu) or to the editors.
1. Introduction
-
This ocument catalogs currently available implementations of X.500, including commercial roducts and openly available offerings. It contains descriptions of Directory System Agents (DSA), Directory User gents (DUA), and DUA client applications. The atter can include such pplications as rowsers, DSA management tools, r lightweight DUAs that employ n application-level protocol to communicate with a DUA (which then in turn communicates with DSA) to support user service. Section 2 of this document ontains a listing of implementations cross referenced by keyword. This list will id in identifying particular implementations that meet our criteria. To compile this catalog, the ISI 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 the orm and content of his memo. New submissions are always elcome. Please direct input o the parties as described in the Status of this Memo section. DISI will produce new versions of this document when a suf- ficient number of changes have been received. This ill be deter- mined subjectively by the DISI chairperson.
1.1 Purpose
-
The growth of existing X.500 ilot activities (e.g., hite Pages Pilot Project) and the advent of new ilots (e.g., ARRNet Directory Services Project, NIST/GSA Pilot Project) are signals that X.500 is a viable directory service mechanism for the Internet community. A goal f DISI s to enable the continued growth of X.500 by lowering the lack-of-information barrier. This document takes one step toward that oal by roviding an easily accessible source of information on X.500 implementations.
1.2 Scope
-
This ocument contains descriptions of either commercially or freely available X.500 implementations. It oes not provide instructions on how to install, run, r manage these mplementations. Because the needs and computing environments of each organization differ astly, no recommendations are given. The descriptions and indices are provided to make the eaders ware of existing options and to enable more nformed choices.
1.3 Disclaimer
-
Implementation descriptions were written by implementors and endors, and not by the members of DISI. Although DISI has worked with the description authors to ensure readability, no guarantees can e made regarding the validity of descriptions or the value of said implementations. Caveat emptor.
1.4 Overview
-
Section 1 contains introductory information.
Section 2 contains a ist of eywords, their efinitions, and a cross reference of he X.500 implementations by these keywords.
Section 3 contains the X.500 mplementation descriptions.
Section 4 lists the editors' ddresses.
1.5 Acknowledgments
-
The creation f this atalog ould not have been possible without the efforts of the description authors and the members of the DISI Working Group. The editors thank you for your hard work and constructive eedback. A special thanks is also extended to he members of the NOCTools Working Group. The "Network anagement Tool Catalog" (RFC-1147) served as a valuable example. Bob Stine nd Bob Enger made key suggestions that enabled us to learn from their experiences. The efforts of the editors were sponsored by efense dvanced Research Projects Agency Contract Number DACA76-89-D-0002 (Field Operational X.500 Project), and U. S. Department of Energy Contract Number DE-AC03-76SF00098.
2. Keywords
-
Keywords are bbreviated attributes of the X.500 implementations. The list of keywords efined elow was derived from the implementation descriptions themselves. Implementations were indexed by a eyword ither as a result of: 1) explicit, not mplied, reference to particular capability n the implementation description text, or ) input from the implementation description author(s).
2.1 Keyword Definitions
-
This ection ontains keyword definitions. They have been organized and grouped by functional category. he definitions re ordered first alphabetically y keyword category, and second lphabetically by implementation name within keyword category.
2.1.1 Availability
-
Available via FTAM
-
mplementation is available using FTAM.
Available via FTP
-
mplementation is available using FTP.
Commercially vailable
his implementation can e purchased.
Free
vailable at no harge, lthough other restrictions may pply.
-
Potentially Unavailable
mplementation was not available at the ime this document was ritten.Source
ource code is available, potentially at an additional cost.
2.1.2 Implementation Type
-
API
mplementation comes with an application programmer's interface i.e., a set of ibraries and include files).DSA Only
mplementation consists f a DSA only. o DUA is included.
-
DSA/DUA
oth a DSA and DUA are included n this mplementation.
-
DUA Light Weight Client
-
mplementation is a DUA-like program that uses a non-OSI proto- ol to satisfy X.500 requests.
DUA Only
mplementation consists f a DUA only. o DSA is included.
2.1.3 Internetworking Environment
-
CLNP
mplementation uses OSI LNP.
OSI Transport
mplementation description specifies that OSI transport roto- ols are used but does not specify which one(s).RFC-1006
mplementation uses RFC-1006 with TCP/IP transport service.
-
X.25
mplementation uses OSI .25.
2.1.4 Pilot Connectivity
-
DUA Connectivity
he DUA an be connected to the ilot, and information on any ilot entry looked up. he DUA s able o display standard ttributes and object classes and those efined n the COSINE nd Internet Schema.DSA Connectivity
he DSA s connected to he DIT, and information in this DSA is ccessible from ny pilot DUA.
2.1.5 Miscellaneous
-
Included in ISODE
-
UAs that are part of ISODE.
Limited Functionality
urvey states that the implementation has some shortcomings or ntended lack of functionality, .g., omissions ere part of the esign to provide an easy-to-use user interface.Needs ISODE
SODE is required to compile and/or use his implementation.
-
X Window System
mplementation uses the Window System o provide its user nterface.
2.1.5 Operating nvironment
-
3Com
-
mplementation runs on a 3Com platform.
Apollo
-
mplementation runs on an Apollo platform.
Bull
-
mplementation runs on a Bull platform.
Cray
-
mplementation runs on a Cray.
DEC Ultrix
-
mplementation runs under DEC Ultrix.
HP
-
mplementation runs on an HP platform.
IBM (Non-PC and RISC)
mplementation runs on some type of IBM, which is not a C or NIX workstation.IBM PC
-
mplementation runs on a PC.
IBM RISC
-
mplementation runs on IBM's RISC UNIX workstation.
MIPS
mplementation runs on a MIPS RISC UNIX orkstation.
Macintosh
-
mplementation runs on a Macintosh.
Multiple Vendor Platforms
mplementation runs on more than one hardware platform.
-
Philips
-
mplementation runs on a Philips platform.
Siemens
-
mplementation runs on a Siemens platform.
Sun
-
mplementation runs on a Sun platform.
UNIX
-
mplementation runs on a generic UNIX platform.
Unisys
mplementation runs on a Unisys latform.
VMS
-
mplementation runs under VAX/VMS.
2.2 Implementations Indexed by eyword
-
This ection ontains an index of implementations by eyword. You can use this ist to dentify particular implementations that meet your hosen criteria. The index is rganized as follows: keywords appear in alphabetical order; implementations characterized y that eyword re listed alphabetically as well. Note that a *" is used to indicate hat the particular implementation, or feature of the mplementation, ay not be available t this ime.
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 .500 DUA process DE DISH-VMS 2.0 API DIXIE Mac-ISODE lliance OSI X.500 maX.500 ustos POD CE/GDS psiwp S-520, S-521 QUIPU P X.500 DDS ud S X.500 DSA/DSAM, DUA VMS-ISODE ac-ISODE Xdi SI Access and Directory XLU SI-DSA SI-DUA Bull UIPU COM X.500 UCOM X.500 MS-ISODE TT X.500 CLNP IN/DS Cray OSI Version 2.0 Apollo DCE/GDS HP X.500 DDS TT X.500 OSI Access and Directory OSI-DSA Available via FTAM OSI-DUA QUIPU E VTT X.500 ISH-VMS 2.0 WIN/DS OD X.500 DUA rocess UIPU Xdi LU XT-DUA Commercially vailable DSA/DUA lliance OSI X.500 Alliance OSI X.500 ray OSI Version 2.0 Cray OSI Version 2.0 CE/GDS Custos irectory 500 Directory 00 S-520, S-521 DS-520, DS-521 P X.500 DDS HP X.500 DDS S X.500 DSA/DSAM, DUA IS X.500 DSA/DSAM, DUA SI Access and Directory Mac-ISODE SI-DSA OSI Access and Directory SI-DUA QUIPU COM X.500 UCOM X.500 TT X.500 VMS-ISODE IN/DS VTT X.500 .500 DUA process WIN/DS T-DUA wp [PSI] DUA Connectivity Cray DE DS-521 ray OSI Version 2.0 OSI Access and Directory Xdi DEC Ultrix DUA Light Weight Client CE/GDS UIPU *MacDish COM X.500 DIXIE xwp [UWisc] maX.500 psiwp DSA Only ud SI-DSA DUA Only DSA Connectivity DE DISH-VMS 2.0 S-520 OSI-DUA SI Access and Directory POD psiwp SD X.500 DUA rocess Xds xdua XLU XT-DUA xwp [PSI] Free Limited Functionality wp [UWisc] Custos ustos *MacDish E POD ISH-VMS 2.0 psiwp IXIE Xds ac-ISODE xwp [PSI] aX.500 OD MIPS siwp UIPU Alliance OSI X.500 D OSI Access and Directory d QUIPU MS-ISODE di Macintosh ds dua Alliance OSI X.500 LU DIXIE Mac-ISODE HP *MacDish maX.500 lliance OSI X.500 psiwp P X.500 DDS QUIPU UIPU *UCOM X.500 COM X.500 Multiple Vendor Platforms IBM (Non-PC and RISC) Alliance OSI X.500 lliance OSI X.500 Custos DCE/GDS IBM PC DS-520, DS-521 IS X.500 DSA/DSAM, DUA lliance OSI X.500 POD UCOM X.500 QUIPU VTT X.500 SD wp [UWisc] UCOM X.500 ud IBM RISC VTT X.500 WIN/DS CE/GDS X.500 DUA rocess COM X.500 xdua XLU Included In ISODE XT-DUA xwp [PSI] OD xwp [UWisc] D Needs ISODE RFC-1006 ustos Alliance OSI X.500 E Cray OSI Version 2.0 ISH-VMS 2.0 Custos IXIE DCE/GDS ac-ISODE Directory 00 MacDish DISH-VMS 2.0 OD DS-520, DS-521 siwp IS X.500 DSA/DSAM, DUA D Mac-ISODE MS-ISODE OSI Access and Directory di *OSI-DSA ds *OSI-DUA dua POD LU QUIPU T-DUA SD wp [UWisc] UCOM X.500 VMS-ISODE OSI Transport VTT X.500 WIN/DS lliance OSI X.500 Xdi ray OSI Version 2.0 Xds ustos XLU S-520, S-521 XT-DUA S X.500 DSA/DSAM, DUA UIPU Siemens IN/DS T-DUA *UCOM X.500 Philips COM X.500 Potentially Unavailable acDish Source UNIX CE/GDS Custos E DE S-520, S-521 DIXIE ac-ISODE DS-520, DS-521 SI-DSA IS X.500 DSA/DSAM, DUA SI-DUA POD OD QUIPU siwp SD UIPU UCOM X.500 d ud MS-ISODE WIN/DS IN/DS Xdi di XLU ds XT-DUA dua xwp [PSI] LU xwp [UWisc] Sun Unisys lliance OSI X.500 OSI-DSA ustos OSI-DUA irectory 500 IXIE VMS UIPU COM X.500 DISH-VMS 2.0 d VMS-ISODE TT X.500 ds X Window System dua T-DUA QUIPU SD WIN/DS X.500 DUA rocess Xdi Xds xdua XT-DUA xwp [PSI] xwp [UWisc] X.25-
CE/GDS
irectory 500
ISH-VMS 2.0
P X.500 DDS
SI Access and Directory
SI-DSA
SI-DUA
UIPU
UCOM X.500
TT X.500
IN/DS
.500 DUA process
di
T-DUA
-
3. Implementation Descriptions
-
In the following pages you will find escriptions of .500 implemen- tations listed in alphabetical order. In the case of name colli- sions, the name of the responsible organization, in square brackets, has been used to distinguish he implementations. Note that throughout this section, the age header reflects the name of the implementation, not the date f the document. The descriptions fol- low a common ormat, s described below:
NAME
he name of the .500 implementation and the name of the respon- ible organization. Implementations with a registered trademark ndicate this by appending "(tm)", e.g., GeeWhiz(tm).LAST ODIFIED
he month and year within which his implementation description as last modified.KEYWORDS
list of the keywords defined in Section 2 that have been used o cross reference this mplementation.ABSTRACT
brief escription of the application. This section may
ptionally contain a list of the pilot projects n which the
pplication is being used.
-
COMPLETENESS
statement of compliance with respect to the 1988 CCITT Recom- endations X.500-X.521 [CCITT-88], specifically ection of .519, or the 1988 NIST IW Stable Implementation Agreements NIST-88].INTEROPERABILITY
list of other UAs and DSAs with which this implementation can nteroperate.PILOT CONNECTIVITY
escribes the level of connectivity it can offer to the ilot irectory service operational on the Internet in North America, nd to pilots co-ordinated by the PARADISE project in Europe. evels of connectivity are: Not ested, one, DUA Connectivity, nd DSA onnectivity.BUGS
warning on known problems and/or instructions n how to report ugs.CAVEATS AND GENERAL LIMITATIONS
warning about ossible side effects or shortcomings, e.g., a eature hat works on one platform but not another.INTERNETWORKING ENVIRONMENT
list of environments in which his implementation can e used, .g., RFC-1006 with TCP/IP, TP0 r TP4 with X.25.HARDWARE PLATFORMS
list of hardware platforms on hich this application runs, any dditional boards or processors equired, and any special sug- ested or required configuration options.SOFTWARE PLATFORMS
list of operating systems, window systems, databases, r
nbundled software packages required to un this application.
-
AVAILABILITY
statement regarding the availability of the software (free or ommercially available), a description of how to obtain he oftware, and (optionally) a statement regarding distribution onditions and restrictions.
NAME
-
Alliance OSI(tm) X.500
Touch Communications nc.
LAST MODIFIED
-
July, 1991
KEYWORDS
-
API, ommercially Available, SA/DUA, HP, IBM (Non-PC and RISC), MIPS, Macintosh, Multiple Vendor Platforms, OSI Transport, RFC-1006, Sun
ABSTRACT
-
Alliance OSI ncludes XDS (API), DUA, DSA and DIB all as separate components.
Touch's X.500 products have been designed for complete portability to any operating system r hardware environment. The protocols nclude DAP and DSP of the OSI X.500 pecification along with the required XDS, UA, DSA and DIB components. In addition to X.500, Touch sup- plies other OSI protocol layers including: ROSE, ACSE, Presentation, Session and any of the OSI lower layers (Transport, Network along with FC-1006). Touch also supplies ther application layer roto- cols uch as .400, FTAM, CMIP (and general network management), etc. The Alliance SI X.500 is compliant with the CITT X.500 1988 Recom- mendations. The ROSE/ACSE/Presentation/Session stack an be option- ally rovided by Touch. The DUA may represent a single user, r may represent a group of users. It may be attached to a given DSA within the ame system but is also capable of invoking operations in Touch's or ny other vendor's compliant DSA on a remote system. The binding operation requires the ser to ive a distinguished name and password in order for the Directory to dentify the user. Once an association s esta- blished the user may nvoke the following operations: READ, COMPARE, ABANDON, LIST, SEARCH, ADD_ENTRY, REMOVE_ENTRY, MODIFY_ENTRY, MODIFY_RDN. Due to the fact that ccess to the physical disk is in most ases a blocking operation synchronous) Touch has separated the atabase processing (I/O process) from the DSA protocol entity. This separa- tion llows the DSA entity to continue processing during the requent database accesses from the DSA. The DSA supports all the Directory operations as specified in the CCITT X.500 specification. Chaining, Referral and ulticasting are provided and supported n the lliance OSI SA. The DSA supports ll the ervice ontrol ptions ncluded in the operation command arguments. iltering conditions are sup- ported via the FILTER in the EARCH operation. The Alliance SI X.500 product supports all the NIST efined anda- tory .500 and X.400 bject classes and attributes. Alliance OSI .500 supports all the mandatory Directory attribute types (and their associated abstract yntaxes) in the NIST Directory implementation profile. Touch has extended the Directory and llows users to define private attributes. his means that user can util- ize the Alliance OSI irectory for a eneral urpose, user defined database activity.
Touch provides a full set of dministration and Directory management facilities.
Touch is in the process of integrating the X.500 product with the Worldtalk 400 product. Worldtalk 400 s Touch's end user X.400 mes- sage witch, roviding gateways between proprietary mail systems (SMTP, Microsoft Mail, MHS, cc:mail, tc.) and X.400. X.500 s a key component for a messaging network.
COMPLETENESS
-
Strong Authentication is not upported however Simple Authentication is supported.
INTEROPERABILITY
-
No interoperability testing has been ompleted as of et.
PILOT CONNECTIVITY
-
Numerous OEMs are using the Alliance SI X.500 product in product development as well as in pilot networks.
BUGS
-
N/A
CAVEATS ND GENERAL LIMITATIONS
-
Currently the Alliance OSI X.500 DIB as only been validated ithin a UNIX ile System. The protocol components are portable as is the interface between the DSA and the DIB.
INTERNETWORKING NVIRONMENT
-
Alliance OSI .500 can be utilized over TCP/IP and/or OSI Transport on LANs and WANs. Currently .500 has only been verified over OSI, however other Alliance OSI application layers have been configured over RFC-1006 which is available as part of the Alliance OSI pro- duct ine.
HARDWARE PLATFORMS
-
Alliance OSI as been ported o numerous platforms ranging from IBM Mainframes MVS to Apple Macintosh. For UNIX nvironments Touch has portations for 386 AT/Bus, SUN-3 and , Mips, and HP.
SOFTWARE PLATFORMS
-
As stated above, the lliance OSI product have been ported to numerous systems. In the UNIX environment the X.500 roduct xists on SUN OS 4.0 and greater, Mips RISC S, Interactive 86 and P-UX.
AVAILABILITY
-
Alliance OSI s commercially vailable from: Touch Communications nc. 250 E. Hacienda Ave Campbell, CA 5008 Sales and Information: (408) 74-2500 FAX: 408) 374-1680
NAME
-
Cray SI Version 2.0
Cray esearch Inc.
LAST MODIFIED
-
July, 1991
KEYWORDS
-
CLNP, Commercially Available, Cray, DSA/DUA, SI Transport, RFC-1006
ABSTRACT
-
The product is packaged with he Cray OSI product. It includes a DSA and DUA capable of OSI or TCP/IP connections. The implementation is based on the SODE QUIPU product.
COMPLETENESS
-
Compliance with CCITT88 plus ccess control extensions. Strong authentication not yet implemented.
INTEROPERABILITY
-
Interoperates with ISODE QUIPU based mplementations.
PILOT CONNECTIVITY
-
The software as been operated in conjunction with the White ages Pilot Project.
BUGS
-
[No information provided--Ed.]
CAVEATS ND GENERAL LIMITATIONS
-
See ISODE QUIPU limitations.
INTERNETWORKING NVIRONMENT
-
TCP/IP, TP4
HARDWARE PLATFORMS
-
Runs n UNICOS based ray machines with OS level 7.0 r greater.
SOFTWARE PLATFORMS
-
Supported for CRAY UNICOS 7.0 or greater.
AVAILABILITY
-
Commercially vailable via Cray Research Inc. Sales Representatives.
NAME
-
Custos
National Institute of Standards and Technology
LAST MODIFIED
-
November, 1991
KEYWORDS
-
API, SA/DUA, Free, Limited Functionality, Multiple Vendor Platforms, Requires ISODE, OSI Transport, RFC-1006, Sun, UNIX
ABSTRACT
-
The implementation consists of a set UA library routines, a erminal interface, and a DSA. The implementation was eveloped in C on Sun 3 workstations nder the UNIX operating system. All underlying ervices are provided y the ISODE development package. The development pack- age is also used for ncoding and decoding ASN.1 data as well as for other data manipulation services. Using the ISODE package the imple- mentation can be run ver both OSI and TCP/IP protocols. The DSA provides full support for both DAP and DSP protocols, confor- mant ith ISO 9594/CCITT X.500 standards. The DIB is aintained using a locally developed relational database system. The interface to the database system consists of a set of QL-like C functions. These are designed to allow straightforward replacement of the ocal database system with a more powerful commercial system. To achieve better per- formance several options are upported that permit loading of selected portions of he database into core. hen these options are selected data can be etrieved more quickly from in-core tables; all modifications to the IB are irectly reflected in the in-core tables and the database.
COMPLETENESS
-
To date the Read, Compare, List, Add ntry, and Remove Entry pera- tions have been implemented and are supported over both DAP and DSP; aliasing and eplication are lso supported. The version under current development (available January '92) includes imple authenti- cation, access control, and the Search operation. The modify pera- tions and Abandon are not supported and there is no support for schema checking.
INTEROPERABILITY
-
Have uccessfully interoperated with UIPU and OSIWARE over the DAP. No DSP interoperability testing has been done.
PILOT CONNECTIVITY
-
Not tested.
BUGS
-
Some esting n the near term future ill be one to ry to identify these, but presently t's not possible to give an accurate list of bugs.
CAVEATS ND GENERAL LIMITATIONS
-
No limitations on file sizes, etc. The only side effects to creating large files should be in the rea of erformance. Specifically, optimization equires loading parts of the DIB in core so greater memory requirements will be necessary for achieving better perfor- mance with a arge database. Any platform the implementation can be ported to (generally ny platform ISODE can be ported to) should sup- port ll features.
INTERNETWORKING NVIRONMENT
-
RFC-1006; TP4/CLNP (SunLink OSI) over 802 and X.25 (SunLink X.25).
HARDWARE PLATFORMS
-
It has been run on Sun-3, but there are no known reasons why t should not run on any hardware running the ISODE software.
SOFTWARE PLATFORMS
-
It requires UNIX and he ISODE software package. It's been developed and tested with ISODE version 6.0 and Sun OS ersion .1.1. ses a locally developed relational BMS that should be easily replaceable with ommercially available relational systems.
AVAILABILITY
-
While under continuing development, availability of the implementa- tion s limited to organizations making appropriate arrangements with NIST. The implementation will be publicly available hen development is completed.
NAME
-
DCE/GDS (tm)
Open oftware Foundation, Inc.
LAST MODIFIED
-
July, 1991
KEYWORDS
-
API, LNP, Commercially Available, DEC Ultrix, DSA/DUA, IBM RISC, Multiple Vendor Platforms, RFC-1006, ource, .25
ABSTRACT
-
DCE/GDS (Distributed omputing Environment/Global Directory Service) was based on he original Siemens DIR.X product. It supports ull DUA and DSA functions for globally unique identifications and for loca- tion f objects in the network. It also provides functions to answer queries (both yellow-page and white-page) about objects and attribute information. The software implements full DAP and DSP protocols specified in .519. n ASN.1 compiler and required ACSE, ROSE, presentation, session and RFC-1006 protocols mplementations re also included. The product has been uccessfully participated in X.500 Cebit Intero- perability tests at 1990 and 991 Hanover Fairs. It also intero- perates with he ISODE QUIPU .500 implementation.
COMPLETENESS
-
Compliant with EWOS Agreements which s being harmonized with OIW Agreements.
Strong authentication in X.509 is not yet implemented. (Password scheme is currently used.)
Consists of both DUA nd DSA mplementation according to the 8 CCITT X.500 and ISO 9594 standard. The X/Open standard XDS (version 1.0) and XOM (version 2.0) interface libraries are also provided. XDS and XOM interfaces are also used o access DCE/CDS (Local Cell Directory Service) transparently. A GDA (Global Directory Agent) serves as the gateway between the DCE CDS and GDS.
INTEROPERABILITY
-
This mplementation of DAP and DSP can interoperate with other X.500 implementations from ther Cebit demo participants including BM, HP, ICL, ull, Nixdorf, etc. It also interoperates with ISODE QUIPU.
PILOT CONNECTIVITY
-
[No information provided--Ed.]
BUGS
-
Problems and ug report email address: dce-defect@osf.org.
CAVEATS ND GENERAL LIMITATIONS
-
The software s highly portable without general limitations.
INTERNETWORKING NVIRONMENT
-
OSI TP4 with LNP OSI TP0, 2 & with X.25 RFC-1006 with TCP/IP
HARDWARE PLATFORMS
-
DCE/GDS runs n SNI's hardware platforms and s being ported o run on IBM RS6000, Digital DECstation, etc.
SOFTWARE PLATFORMS
-
SINIX (UNIX System V elease ) Currently being ported: OSF/1.1, AIX .1, Ultrix, etc. DCE/GDS can use either BSD sockets or XTI/TLI to access the transports.
AVAILABILITY
-
The source code license of DCE/GDS is commercially available rom:
Open oftware Foundation, Inc. 11 Cambridge enter Cambridge, MA 02142Please contact:
Jon Gossels Tel: 17-621-8763 Fax: 17-621-0631 e-mail: gossels@osf.org
NAME
-
DE
COSINE PARADISE
LAST MODIFIED
-
November, 1991
KEYWORDS
-
Available via FTAM, Available via FTP, DUA Connectivity, DUA nly, Free, Included in ISODE, Limited Functionality, Needs ISODE, ource, UNIX
ABSTRACT
-
DE (Directory Enquiries) is intended o be a imple-to-use interface, suitable for he naive user, nd suitable for running as a public access dua to provide lowest ommon denominator access to the Direc- tory. It is scrolling interface and will thus run n dumb ermi- nals, even teletypes! The user is asked to fill in up to 4 questions per query: person's name; department; organization; country. The prompts are very verbose -- the intention is hat the user should not be able get stuck, and information on how to et into the help system should always be on the screen. The elp screens (of which there are 15) are aimed at the on-technical user. Whilst the utwards appear- ance f the interface is simple, a lot of attention has being given to mapping the strings the user enters onto X.500 operations n such a way that the interface seems to do he "right thing". An important characteristic is the way the interface tries a series of searches, gradually relaxing the matching criteria from exact (in some ense), to good, through to "fuzzy". A considerable mount of configuration is possible to present the results in locally acceptable formats. DE was funded by the OSINE PARADISE roject, and DE s used s the PARADISE public access dua. ou can est the software by telnet to 128.86.8.56 and logging in as dua -- o password required.
COMPLETENESS
-
The interface is a querying engine only.
INTEROPERABILITY
-
DE is built with the SODE software (release .0). Its interopera- bility relies on the orrectness of the Quipu libraries.
PILOT CONNECTIVITY
-
The interface is in use as the COSINE Central DUA Service, and is used y a number of UK institutions as a public access dua (usually over .29). t is able to query entries in pilots throughout the world. It is not able to query for entries which are in organiza- tions beneath locality entries under ountry ntries. It is ot pos- sible to query for people who do not ork for organizations. The interface only searches for entries of the following ype: organiza- tions, organizational units, eople, oles, and rooms.
BUGS
-
Send ug reports to:
p.barker@cs.ucl.ac.uk helpdesk@paradise.ulcc.ac.uk
CAVEATS ND GENERAL LIMITATIONS
-
DE tries to cater well for the general case, t the expense of not dealing with he less typical. The main manifestation of this is that he current version will not query under localities immediately under the country level.
It is not possible to display photographs or eproduce sound ttri- butes.
INTERNETWORKING NVIRONMENT
-
Same s ISODE. ISODE supports TCP/IP, TP0, and X.25.
HARDWARE PLATFORMS
-
Should be the same as ISODE in general.
SOFTWARE PLATFORMS
-
DE requires the ISODE (current release 7.0) libraries.
AVAILABILITY
-
DE is openly vailable as part of ISODE and as part of the COSINE DUA package. Available y FTAM nd FTP, source ode freely available.
NAME
-
Directory 500(tm)
OSIware Inc.
LAST MODIFIED
-
July, 1991
KEYWORDS
-
Commercially vailable, DSA/DUA, RFC-1006, Sun, X.25
ABSTRACT
-
Full mplementation of the X.500 recommendations. Includes DUA, DSA & various utilities. ritten n ANSI-C / C, and runs n 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, etix, ICL, Nixdorf.
BUGS
-
None
CAVEATS ND GENERAL LIMITATIONS
-
None
INTERNETWORKING NVIRONMENT
-
RFC-1006 with TCP/IP TP0 with X.25
HARDWARE PLATFORMS
-
Runs n Sun-3, Sun-4
SOFTWARE PLATFORMS
-
For SunOS 4.X with Sunlink X.25 6.0
AVAILABILITY
-
Commercially vailable from:
OSIware Inc. Tel: 1-604-436-2922 4370 ominion 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, Needs SODE, RFC-1006, VMS, X.25
ABSTRACT
-
This irectory User Agent interface was ported to the VMS operating system using SODE 6.0. It is part of the results of ollaboration project called ACIDO, between RedIRIS (national network R & D in Spain) and the "Facultad de Informatica de Barcelona Universidad Politecnica de Cataluna)". The main bjective of this development was to provide access to the irectory to all those affiliated cen- tres o the Spanish National & D network using VMS achines. Any other use of his software it is no within RedIRIS objectives and therefore it s not RedIRIS responsibility.
COMPLETENESS
-
The same as DUA (QUIPU 6.1).
INTEROPERABILITY
-
QUIPU 6.1
PILOT CONNECTIVITY
-
Used n RedIRIS Directory Pilot Project to access the DSAs (QUIPU).
BUGS
-
You can report bugs to: isode@fib.upc.es
CAVEATS ND GENERAL LIMITATIONS
-
The interface is equivalent to the UNIX one except for the option -pipe which is not supported.
The users can have a uipurc ile to onfigure their work nviron- ments with ISH. This file hould reside at the SYS$LOGIN directory of the user and it should be alled "quipurc." (in UNIX it's called .quipurc)
INTERNETWORKING NVIRONMENT
-
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= 043145100102 ISO-CLNS= 39724F1001000000010001000113020600100200 (COSINE P4.1) File: /isodevms/dishVMS2.BCK.Z compress SAVE_SET file (1.6 Mbytes) File: /isodevms/lzdcm.exe to ncompress the file
NAME
-
DIXIE
University of Michigan
LAST MODIFIED
-
November, 1991
KEYWORDS
-
Available via FTP, DUA Light eight Client, Free, Source, UNIX, Mul- tiple Vendor latform, Needs SODE
ABSTRACT
-
The DIXIE protocol is used to give X.500 access to platforms hat have nly TCP/IP access. The DIXIE server is an intermediate proto- col server that communicates ith Internet clients on one side using a text-based DP/TCP rotocol and an .500 DSA on the other side using DAP. The protocol is fully described in RFC 1246. A subset of the X.500 DAP is exported to he clients through the IXIE protocol. There is a DIXIE API rovided in the orm of library of C-callable routines.
The DIXIE protocol and server are being used y the following products/projects:
-
UD, a simple command line white pages DUA for Unix achines (dis- tributed with the DIXIE server)
maX.500, a hite pages DUA or the acintosh (available from the same place s the DIXIE server) Network monitoring f DSAs y our Network Operations Center Lookup and isplay f caller identification based on telephone caller ID (using ISDN). -
COMPLETENESS
-
The DIXIE protocol does not support access to all X.500 features and operations. ll DAP perations except Abandon are supported. Gen- eral earches (including multiple component searches) are supported. The DIXIE protocol supports none and imple authentication. subset of the service controls are supported.
INTEROPERABILITY
-
The current implementation of the DIXIE server works ith the QUIPU DSA and DAP library.
PILOT CONNECTIVITY
-
The DIXIE server has een tested in the Internet and ARADISE pilots. It provides full DUA onnectivity subject to he limitations is- cussed above nder completeness.
BUGS
-
There are no nown outstanding bugs. But reports should be sent to x500@umich.edu.
CAVEATS ND GENERAL LIMITATIONS
-
None, aside from those mentioned above under ompleteness.
INTERNETWORKING NVIRONMENT
-
DIXIE clients use TCP or UDP o communicate with the IXIE server. The DIXIE server uses RFC-1006 with TCP/IP to communicate with the DSA, hough other transport mechanisms for DSA communication hould be possible.
HARDWARE PLATFORMS
-
The DIXIE server is known to un on Sun 3, Sun 4, and DEC 3100 plat- forms. It should run on any NIX platform. he DIXIE library is known to run n the same platforms, and also n the Macintosh.
SOFTWARE PLATFORMS
-
The DIXIE server and ibrary s known to run nder SunOS 3.5, SunOS 4.1.1, Ultrix 4.1 and 4.2. The DIXIE library also runs on the Macin- tosh ystem Software or later.
AVAILABILITY
-
This oftware is openly available. It may be obtained by anonymous FTP from terminator.cc.umich.edu in the directory ~ftp/x500. ocumen- tation on the DIXIE protocol s provided along with the source code, which includes source for the DIXIE server, DIXIE library, and the UD client.
This oftware was developed at the University of Michigan by Bryan Beecher, Tim Howes, and Mark Smith f the ITD Research Systems Unix Group. It is subject to the ollowing copyright. Copyright © 1991 Regents of the University f Michigan. All rights reserved. Redistribution and use in ource and binary forms re per- mitted provided that his notice is preserved and that due credit is given to the niversity of Michigan at Ann Arbor. The name of the University may not be used to endorse or promote products derived from his software without specific prior written permission. This software is provided as is" ithout xpress r implied warranty.
NAME
-
DS-520
DS-521
Retix
LAST MODIFIED
-
November, 1991
KEYWORDS
-
API, ommercially Available, SA/DUA, DUA Connectivity, DSA Connec- tivity, Multiple Vendor Platforms, OSI Transport, RFC-1006, ource, UNIX
ABSTRACT
-
DS-520 X.500 istributed Directory Services for UNIX ystem V and DS-521 X.500 irectory User Agent (DUA) for UNIX System V form an integral part of the etix OSI Networking Products family. Designed for systems vendors, ublic carriers, and other OEMs, DS-520 s a complete high-performance implementation of X.500 in ource code form, including a DUA, DSA Manager (DSAM), and DSA. S-521 represents a ubset of this product offering. It provides the DUA portal into the directory, which, for example, meets he needs of software vendors who lan to rovide pplication packages with X.500 Directory interaction capabilities. Within these two fferings, the DUA possesses two forms of interface. The first form, the DUA with User nterface, provides an interactive character-based user nter- face or users of Directory services. The user agent provides access to the Directory via asic Directory ervice equests. The second form, the DUA with Programmatic Interface provides a tandardized programmatic nterface to application programs that must access Directory information. The interface s conformant to the X/Open Object Management (XOM) and X/Open Directory ervices (XDS) stan- dards. This component provides all functionality related to Directory access and general OSI services down o the session layer. The DSAM provides an interactive character oriented user interface to Direc- tory dministrator. he DSAM provides management functions either local to or remote from a DSA. Both the DUA and the DSAM are seful in the training, management, nd manipulation of Directory entries maintaining operational and user attribute information. The DSA main- tains Directory database information nd provides users the ability to read/compare, modify, search, and anage entries within the data- base. It maintains all or fragments of the Directory nformation Base (DIB) and provides abstract service ports for DUAs and DSAs over DAP and DSP protocols respectively.
COMPLETENESS
-
DS-520 represents a complete mplementation of the 1988 X.500 Recom- mendations with the exception of strong authentication as outlined in X.509. It is onformant to NIST, EWOS, and UK GOSIP Directory pro- files. It provides session through application layer rotocol support and hence incorporates ROSE, CSE, Presentation, and ession ithin its product stack. In addition to including all the attribute types, syntaxes, and object lasses efined n X.520 and X.521, the S-520 includes support for hose specified n the 1988 X.400 Recommendation X.402, Annex . Remote on-line management of he DSA s supported by means of Network Management Forum CMIP. DS-521 represents a complete mplementation of the X/Open Object Management (OM) and X/Open Directory ervices (XDS) standards. It also ncorporates session through application layer protocol upport and thus includes ROSE, ACSE, Presentation, and Session within its product stack.
INTEROPERABILITY
-
The DS-520 has been tested to interoperate with Banyan (DAP), CDC (DSP), IBM, ICL, OSIWare, Nixdorff, Unisys (DSP), Wollongong DAP), and 3-Com (DSP).
The DS-521 subset has undergone no separate interoperability esting.
PILOT CONNECTIVITY
-
DSA Connectivity provided by he DS-520: The SA provides complete support for the X.511 Abstract Service Definition, the directoryAc- cessAC and the directorySystemAC defined in the X.519 Protocol Specifications, and the Distributed Directory defined in the .518 Procedures for the Distributed Directory. It upports all the object classes, attribute types, and attribute syntaxes defined in X.520 and X.521. It does not support the Internet DSP however. DUA Connectivity provided by oth the DS-520 nd DS-521: The UA pro- vides complete support for the X.511 bstract Service Definition and the directoryAccessAC defined in the .519 Protocol Specifications. The DUA with ser Interface supports nly a subset of the X.500 attributes and object classes defined in X.520 and X.521. The DUA with rogrammatic Interface, owever, 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 and uality ssurance engineers are generated and published in the form of weekly reports. A description and status of these PARs are rovided to customers possessing software maintenance greements.
CAVEATS ND GENERAL LIMITATIONS
-
DS-520 and DS-521 are source ode products ported to NIX System V Release 3 and 4. Makefiles to generate the system are provided for the AT&T System V, SCO, and Interactive UNIX ystems.
INTERNETWORKING NVIRONMENT
-
DS-520 and DS-521 offer two main compile time configuration options and hence internetworking configurations. In he first of these, they interface to he UNIX System Transport Library Interface (TLI). The TLI provides a path between the session layer of UNIX OSI application process and an OSI transport provider installed in the UNIX ernel. he latter transport provider may take the form f a Retix Unix LAN (LT-610) or WAN (WT-325) transport product. The second main ption utilizes he UNIX System ACSE/Presentation Library interface (APLI and the A/P Library), which provides SI ACSE and Presentation ayer services. he Retix AP-240 Presentation syntax manager product serves to map the standard Retix Presentation layer interface to he AT&T APLI. The APLI pper layers services may be provided by the Retix UL-220 roduct. UL-220 s the Retix implementa- tion f the AT&T Open Networking Platform Upper Layer Services module and includes he A/P ibrary, as well as the SI ACSE, Presentation, and Session services. DS-520 and DS-521 may also run on top of the CP/IP stack by eans of the Retix MP-120 product. MP-120 is a STREAMS based driver that implements RFC-1006 and thus llows OSI applications o run over a network based on the nternet suite of protocols (TCP/IP). Its main function provides a conversion between the TCP stream to the ata packets required by OSI Transport Class 0 protocol and vice versa. As part f this rocess, it converts TCP/IP 32-bit addresses to ex values for use with OSI applications.
HARDWARE PLATFORMS
-
Being source ode products ported to he UNIX System Release 3 and 4 operating ystem environment, DS-520 and DS-521 are hardware plat- form ndependent. They currently both have sample portations nd test configurations on various Intel 80386 platforms running Unix ystem V Release 3 and 4.
SOFTWARE PLATFORMS
-
Currently, DS-520 and DS-521 nclude eference implementations for the AT&T System V Release 4, CO UNIX System /386 Version 3.2.2, and the Interactive UNIX ystem V/386 Version 2.2 operating systems. Raima Corporation's db_Vista II Version 3.1 erves as the database engine for the Directory product.
AVAILABILITY
-
DS-520 and DS-521 are commercially available rom:
Retix 2401 olorado Avenue Santa Monica, California 90404-3563 USA Sales and Information: 310-828-3400 FAX: 310-828-2255
NAME
-
HP X.500 Distributed irectory Software
Hewlett Packard
LAST MODIFIED
-
July, 1991
KEYWORDS
-
API, LNP, Commercially Available, DSA/DUA, HP, X.25
ABSTRACT
-
HP's istributed Directory Software is a fully distributed Directory that upports both the DAP and DSP protocols, which were specified in the 1988 CCITT/ISO X.500 documents. esides mplementing the stan- dard, we have also put in proprietary access ontrol nd replication. These additional features will be migrated to the standard definition at the time that they are stable. Users are ble to efine their own attributes, objects classes and DIT structure rules. In order to make this software easy to use a et of menu driven screens have een provided. here are easy to use data access and data anagement screens. For system dministrators, hese is also a set for screens that re used to help configure the servers and manage the schema. Startup and Shutdown utilities are also included.
For application developers an X/Open-APIA XDS API is rovided, along with ome helper routines that help reduce development time. The XDS API includes he following functions:
-
-
Bind
Read
Search
Add
Remove
Unbind
Version
-
A subset of the X/Open-APIA Object Management (XOM) functions are available thru the interface. The subset are those that are eces- sary o perform the directory operations.
For bulk operations a batch interface is also available.
-
COMPLETENESS
-
This oftware implements the 988 X.500 CCITT/ISO Standard. t fully supports DAP nd DSP, minus strong authentication. By default it contains all f the X.520 Attributes nd the .521 Syntaxes and Object Classes. Additionally, the Annex B DIT Structure can e enforced.
INTEROPERABILITY
-
Interoperability testing will be undertaken as new X.500 products are introduced into the market.
PILOT CONNECTIVITY
-
[No information provided--Ed.]
BUGS
-
No major ones at this time.
CAVEATS ND GENERAL LIMITATIONS
-
This s pilot software for organizations who ish to earn about HP's X.500 offering.
INTERNETWORKING NVIRONMENT
-
TP0 or TP4 on 802.3 or X.25
HARDWARE PLATFORMS
-
HP-9000 800 Minicomputer HP-9000 300 Workstation with t least 8 M of nternal memory with M of available disk space for he software
SOFTWARE PLATFORMS
-
Distributed and Supported for HP-UX version 7.0.
AVAILABILITY
-
Limited Commercial Availability.
For more information n the U.S. call 1-800-752-0900. Outside of the U.S. lease contact your local HP Sales Office.
NAME
-
INTERACTIVE Systems' .500 DSA/DSAM
INTERACTIVE Systems' .500 DUA
INTERACTIVE Systems Corporation
LAST MODIFIED
-
July, 1991
KEYWORDS
-
API, ommercially Available, SA/DUA, Multiple Vendor Platforms, OSI Transport, RFC-1006, NIX
ABSTRACT
-
The INTERACTIVE Systems X.500 DSA/DSAM and X.500 DUA rovide com- plete implementation f the OSI X.500 Directory Systems Agent, Direc- tory ystems gent Manager, and Directory Services User Agent. These software packages allow remote access for Directory Systems Agents and include the following protocols: - Directory System rotocol (DSP) - Directory Access rotocol (DAP)- Common Management Information Protocol (CMIP)
- Remote Operations Service Element (ROSE)
- Association Control Service Element (ACSE)
- Presentation services
- BCS Session services
- DBMS and tilities
- X/Open XDS API (included n the DUA)
These products will be available in Q3 1991 in source code form only.
COMPLETENESS
-
These products provide:
- a complete implementation of the .500 distributed Directory
- a DUA with command line UI and X/Open Directory Services (XDS) API- a Multiprocess DSA with integral igh performance DBMS
- remote or local CMIP based DSA management
- a DSA manager that provides on-line DSA monitoring, ontrol, Directory schema manipulation, and UA functions - Support for all 1988 X.500, 1988 .400, and MAP/TOP 3.0 object types and the capability to add new object ypes - Conformance with IST, EWOS, and .K. GOSIP X.500 Directory pro- files
INTEROPERABILITY
-
Not available at this time.
PILOT CONNECTIVITY
-
[No information provided--Ed.]
BUGS
-
Not available at this time.
CAVEATS ND GENERAL LIMITATIONS
-
Not available at this time.
INTERNETWORKING NVIRONMENT
-
The INTERACTIVE Systems implementation of X.500 Directory Services will perate ver both RFC-1006 (in TCP/IP Based networks) and over the Retix Local Area nd Wide Area Network services.
HARDWARE PLATFORMS
-
These products are available n 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
-
Both roducts will be available in Q3 1991. or more information contact: INTERACTIVE Systems Corporation 1901 orth Naper Boulevard Naperville, IL. 60563-8895 PHONE: (708) 05-9100 extension 232 FAX: 708) 505-9133 ttn.: Jim Hancock
NAME
-
Mac-ISODE
Computer Science Department of Massey University
LAST MODIFIED
-
November, 1991
KEYWORDS
-
API, vailable via FTP, DSA/DUA, Free, Macintosh, Needs ISODE, RFC- 1006, Source
ABSTRACT
-
Mac-ISODE is reasonably complete port of ISODE version 7.0. It sits on top of Mac TCP and its development environment is PW with the GNU C compiler See entry or QUIPU/ISODE or a detailed description of the DSA/DUA.
COMPLETENESS
-
See entry for QUIPU/ISODE.
INTEROPERABILITY
-
See entry for QUIPU/ISODE.
PILOT CONNECTIVITY
-
Not tested.
BUGS
-
Macintosh related problems should be ent to Kay@massey.ac.nz.
CAVEATS ND GENERAL LIMITATIONS
-
No testing of the DSA has been done.
INTERNETWORKING NVIRONMENT
-
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 is reely available. Anonymous FTP from c-vms1.massey.ac.nz (130.123.1.4)
NAME
-
MacDish
NASA mes Research Center
LAST MODIFIED
-
July, 1991
KEYWORDS
-
DUA Light Weight Client, Limited Functionality, Macintosh, Needs ISODE, Potentially Unavailable
ABSTRACT
-
MacIntosh interface which connects to a TCP/IP port attached o dish running on UNIX or other dish-capable host. ses a point-and-click interface to implify dish access.
COMPLETENESS
-
No authentication, no modify/delete/add ability.
INTEROPERABILITY
-
Interoperates with QUIPU/dish
PILOT CONNECTIVITY
-
Being used in the White Pages Pilot Project.
BUGS
-
Not complete et, so here are some bugs (primarily formatting, win- dow management).
CAVEATS ND GENERAL LIMITATIONS
-
Not a terribly capable interface.
INTERNETWORKING NVIRONMENT
-
Pure CP/IP. Does not require OSI stack support.
HARDWARE PLATFORMS
-
MacDish runs n Macintosh computers
SOFTWARE PLATFORMS
-
MacTCP and MacOS 6.0.x.
AVAILABILITY
-
Not yet available. Contact is:
Mylene Marquez MS 233-18 NASA mes 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 Light eight Client, Free, Macintosh
ABSTRACT
-
maX.500 is a acintosh X.500 irectory application useful for displaying and modifying white pages nformation about people. It runs n top of the DIXIE protocol (described n RFC 1246). maX.500 is currently n production release 1.1 within the University f Michigan and everal ther places. Features include the bility o display and modify the following attributes: title, description, commonName, uid, mail, postalAddress, homePostalAddress, telephoneNumber, facsimileTelephoneNumber, home- Phone. Photos can also be displayed. The software also provides access to the finger rotocol. Various preferences are user- tailorable, including caching.
COMPLETENESS
-
maX.500 uses he DIXIE protocol to access X.500 and thus is subject to the same completeness restrictions as DIXIE. It provides ead, Search, and Modify capabilities.
INTEROPERABILITY
-
Works with the DIXIE erver, hich works with the QUIPU DSA and DAP library.
PILOT CONNECTIVITY
-
It has been tested (in conjunction with the DIXIE server) in oth the Internet and ARADISE pilots.
BUGS
-
No outstanding bugs are known. But reports should be sent to x500@itd.umich.edu.
CAVEATS ND GENERAL LIMITATIONS
-
maX.500 is heavily oriented to white ages information and thus gen- eral ccess to the DIXIE protocol is ot provided.
INTERNETWORKING NVIRONMENT
-
maX.500 uses he DIXIE protocol and thus TCP o communicate with the DIXIE server. The Macintosh eeds to have MacTCP installed.
HARDWARE PLATFORMS
-
Mac Plus or newer machine with one megabyte or more of memory.
SOFTWARE PLATFORMS
-
Apple System oftware 6.0 or bove (including System ), with MacTCP installed.
AVAILABILITY
-
This oftware is openly available. It may be obtained by anonymous FTP from terminator.cc.umich.edu in the directory ~ftp/x500.
This oftware was developed at the University of Michigan by ark Smith of the TD Research Systems Unix Group nd is subject to the following copyright. Copyright © 1991 Regents of the University f Michigan. All rights reserved. Redistribution and use in ource and binary forms re per- mitted provided that his notice is preserved and that due credit is given to the niversity of Michigan at Ann Arbor. The name of the University may not be used to endorse or promote products derived from his software without specific prior written permission. This software is provided as is" ithout xpress r implied warranty.
NAME
-
OSI Access and Directory
Control Data orporation
LAST MODIFIED
-
November, 1991
KEYWORDS
-
Commercially vailable, DUA Connectivity, DSA Connectivity, API, DSA/DUA, OSI LNP, RFC-1006, .25, MIPS (under Control Data's EP/IX OS).
ABSTRACT
-
OSI Access and Directory includes a QUIPU (version 6.6) based imple- mentation of irectory with enhancements including:
- TP4 CLNP onnectivity
- Directory API based on the X.400 PI
- Support for X.400 objects - Integration with ontrol ata's X.400 MHS products- Curses based user interface
- A DUA daemon that provides Directory access for applications
- Enhanced hoto attribute upport
- ACL enhancements
- DIXIE, DAD and PH.X500 support
COMPLETENESS
-
As per QUIPU.
INTEROPERABILITY
-
OSI Access and Directory can nteroperate 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.
CAVEATS ND GENERAL LIMITATIONS
-
As per QUIPU.
INTERNETWORKING NVIRONMENT
-
As per QUIPU RFC-1006 with TCP/IP, TP0 with .25) plus TP4 over CLNP.
HARDWARE PLATFORMS
-
Control Data 000 systems.
SOFTWARE PLATFORMS
-
Control Data P/IX.
AVAILABILITY
-
Commercially vailable from:
Control Data orporation Computer Products Marketing 4000 eries Networking HQW10H P.O. ox 0 Minneapolis, N 55440-4700 USA 1-800-345-6628
NAME
-
OSI-DSA
Unisys
LAST MODIFIED
-
November, 1991
KEYWORDS
-
API, LNP, Commercially Available, DSA Only, FC-1006, Source, Unisys, X.25
ABSTRACT
-
OSI-DSA provides a Directory ystem agent for controlled access to the OSI Directory Information Base. t provides full support for the joint ISO/IEC IS-9594 International standard nd CCITT X.500 ecom- mendations 1988 protocols necessary for implementing he Directory Information Base distributed cross a number f DSA's.
The product also includes an dministration User interface program, to allow a human administrator to construct and maintain the ocal Directory Information.
Specific features provided by the Directory System Agent include:
(i) Support of the directoryAccessAC and directorySystemAC application contexts (i.e. both Directory ccess Protocol (DAP) and irectory System Protocol (DSP) (ii) Bind Security levels of none and simple unprotected.-
(iii) Capability of acting as a irst level DSA.
(iv) Support for chaining and multi-casting where necessary in handling distributed operations. Also supports the return of referrals. (v) Support for all attribute ypes and syntaxes defined in X.520. Users are lso able to define their own attributes and syntaxes. (vi) Support for all the object classes and attribute sets defined in X.521. Users are also ble to efine their own object classes and attribute sets. Support is also pro- vided for NAME-BINDING specification, for defining the -
Directory nformation Tree (DIT) structure.
-
(vii) An access ontrol echanism based n the ISO access con- trol working papers to allow for controlled access and maintenance of Directory entries and attributes. (viii) Logging of errors nd significant irectory events, as well as optional trace information. (ix) The OSI-DSA utilizes the services f ROSE X.219) nd ACSE (X.217) as defined in clause 8 of .519The Administration program provides the following functions
(i) An interface to each of the basic irectory Operations of Read, Compare, List, Search, Add, odify, odifyRDN. (ii) A ump/Load utility to dump the information in the local DIB into an ASCII ile and load it again into the IB from such a file.-
(iii) Knowledge eference maintenance facilities to Add, Delete
-
Modify and Read all types f Knowledge References.
-
(iv) Facilities to control the peration of local Directory processes. (v) Control over the level of ogging nd tracing.
COMPLETENESS
-
The OSI-DSA provides ll functionality defined in, and is fully con- formant to, the joint ISO/IEC IS-9594 International standard nd CCITT X.500 Recommendations 1988, and the NIST 1988 Stable agreements on Directory ervices.
The only exception is that no support is provided for strong uthen- tication or digital signatures.
Conformance with respect to clause 9 f X.519:
(i) The DSA supports both the irectoryAccessAC and directo- rySystemAC application contexts. (ii) The DSA is capable of acting as a irst-level DSA.-
(iii) The chained mode of operation as defined in X.518 s sup-
-
-
ported.
-
(iv) Bind Security levels of none and simple unprotected are supported. (v) All attribute types and syntaxes defined in X.520 re sup- ported. Users are lso able to define their own attributes and syntaxes. (vi) All the object classes and attribute sets efined n X.521 are supported. Users are lso able to define their own object classes and attribute sets. Support is also pro- vided for NAME-BINDING specification, for defining the Directory nformation Tree (DIT) structure.-
(vii) The DSA conforms to all the static requirements defined in
-
-
clause 9.2.2 of X.519
-
(viii) The DSA conforms to all the dynamic requirements defined
in clause .2.3 of X.519
-
INTEROPERABILITY
-
The product was demonstrated t "Interop 91" n San Jose, October 1991 s part f the OSI Showcase demo involving several vendors' directory products.
Informal interoperability has been achieved against the ISODE 6.0 QUIPU Directory implementation. Interoperability testing against other vendors is in progress.
Formal interoperability testing is awaiting the soon o be completed OSInet X.500 nteroperability test suite.
PILOT CONNECTIVITY
-
Not tested.
BUGS
-
Full ustomer support is provided via your local Unisys Customer Ser- vices Organization.
CAVEATS ND GENERAL LIMITATIONS
-
Results returned via he OSI-DSA are resently limited to 32K in the current release, which is in ine with the 1988 NIST greements. Patches for the Unix .4 release may e made vailable on request to raise this limit to 1Mb. The product currently does not provide any support for replication, although development ork is n progress, based on the current ISO Draft proposal for Replication.
INTERNETWORKING NVIRONMENT
-
OSI-DSA runs ver all communications nvironments supported by the Unisys OSI stack product (see Software platforms). Currently hese support TP0, P2, TP3 and TP4 over X.25 and TP4 over LNP on 02.3 and X.25. Support for RFC1006 over TCP/IP is under development.
HARDWARE PLATFORMS
-
The product is available on all Unisys Unix 6000 Series machines.
Source code is available for ortation to non-Unisys latforms.
SOFTWARE PLATFORMS
-
The product is distributed and supported for nix System V.3 nd Unix System V.4. On Unix V.3, t requires the nisys Application Presentation ervice OSI stack software (APS), and Unisys ransport Network Service software (TNS). On Unix V.4, it requires the integrated Unisys OSI stack software product (STK). These ervices are accessed via the ROSLI (ROSE) nd APLI (ACSE) rogramming interfaces which are currently the subject of standardization efforts by XOpen and Unix International.
A runtime version of ither the Informix or Oracle relational data- base roducts is required for the Directory Information Base.
AVAILABILITY
-
Unisys Unix OSI Directory System Agent is commercially available. For information on porting to non-Unisys latforms, contact:
Socs appas Australian Centre for Unisys oftware 115 Wicks Rd North Ryde N.S.W, 2113 Australia socs@syacus.acus.oz.au Ph: 61 2 390 312 For ny other information contact your ocal Unisys marketing representative or: Unisys Corporation Corporate Marketing Mail rop B-130 Blue ell, PA 19424 USA
NAME
-
OSI-DUA
Unisys
LAST MODIFIED
-
November, 1991
KEYWORDS
-
API, LNP, Commercially Available, DUA Only, FC-1006, Source, Unisys, X.25
ABSTRACT
-
OSI-DUA is a nix C Program interface library. It allows OSI r user applications o access the services of an X.500 conformant Directory, by making calls to a ibrary f C routines. Specific features provided by this program interface ibrary re as follows: (i) Connection to any emote X.500 conformant SA via n OSI stack, or onnection to a o-resident Unisys OSI DSA via IPC mechanisms. (ii) All operations defined in he directoryAccessAC applica- tion context (Bind, UnBind, Read, ompare, Search, List, AddEntry, odifyEntry, ModifyRDN, bandon, DeleteEntry). (iii) Directory ind security levels of one and simple npro- tected. (iv) Execution f both locking and non-blocking operations. (A non-blocking call to the library will return immedi- ately, allowing for results to be btained once the opera- tion has completed) (v) Acceptance of multiple concurrent on-blocked operations on the one user session. (vi) The DUA utilizes the services of ROSE (X.219) and CSE (X.217) as defined in clause 8 of .519
COMPLETENESS
-
When ommunicating with a Remote DSA he DUA ibrary s fully confor- mant ith the Directory Access Protocol detailed in the X.500 Recommendations/IS-9594 standards.
Conformance with respect to clause 9 f X.519:
(i) All operations defined in he directoryAccessAC pplica- tion context (Bind, UnBind, Read, Compare, Search, List, AddEntry, odifyEntry, ModifyRDN, Abandon, DeleteEntry) are supported. (ii) Directory ind security levels of one and simple unpro- tected are supported. (iii) The directoryAccessAC application ontext s supported as specified n clause 7 of X.519. (iv) The DUA conforms to the mapping onto used ervices as de- fined in clause 8 f X.519.
INTEROPERABILITY
-
Informal interoperability has been achieved against the ISODE 6.0 QUIPU Directory implementation. Interoperability testing against other vendors is in progress.
Formal interoperability testing is awaiting the soon o be completed OSInet X.500 nteroperability test suite.
PILOT CONNECTIVITY
-
Not tested.
BUGS
-
Full ustomer support is provided via your local Unisys Customer Ser- vices Organisation.
CAVEATS ND GENERAL LIMITATIONS
-
The present OSI-DUA does not rovide or the automatic handling of referrals by the interface library. However interface routines are provided which allow eferrals to be cted upon by the user pplica- tion. The present OSI-DUA provides proprietary C programming interface. An XOpen XDS onformant interface is urrently under evelopment.
INTERNETWORKING NVIRONMENT
-
OSI-DUA runs ver all communications nvironments supported by the Unisys OSI stack product (see Software platforms). Currently hese support TP0, P2, TP3 and TP4 over X.25 and TP4 over LNP on 02.3 and X.25. Support for RFC1006 over TCP/IP is under development.
HARDWARE PLATFORMS
-
The product is currently available on all Unisys Unix 6000 Series machines.
Source code is available for ortation to non-Unisys latforms.
SOFTWARE PLATFORMS
-
The product is distributed and supported for nix System V.3 nd Unix System V.4. On Unix V.3, t requires the nisys Application Presentation ervice OSI stack software (APS), and Unisys ransport Network Service software (TNS). On Unix V.4, it requires the integrated Unisys OSI stack software product (STK). These ervices are accessed via the ROSLI (ROSE) nd APLI (ACSE) rogramming interfaces which are currently the subject of standardization efforts by XOpen and Unix International.
AVAILABILITY
-
Unisys Unix OSI Directory System Agent is commercially available. For information on porting to non-Unisys latforms, contact:
Socs appas Australian Centre for Unisys oftware 115 Wicks Rd North Ryde N.S.W, 2113 Australia socs@syacus.acus.oz.au Ph: 61 2 390 312For any other information contact your local nisys marketing representative or:
Unisys Corporation Corporate Marketing Mail rop B-130 Blue ell, 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 is first ttempt t a multiwindow directory tool. It offers a simplified interfaces to the basic X.500 operations f read, search, list nd modify entry. POD does not rovide ny sophisticated access to the SA. Operations are performed synchronously. The Directory is thus presented as is, i.e. a hierarchical ree of nformation, 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
-
- standard: trong authentication not implemented
INTEROPERABILITY
-
Believed to be compliant, though untested.
PILOT CONNECTIVITY
-
DUA Connectivity: POD is in use in many directory pilots, certainly including PARADISE and the Internet.
BUGS
-
Bugs o x500@brunel.ac.uk
INTERNETWORKING NVIRONMENT
-
TP0 over TCP/IP (as ISODE)
HARDWARE PLATFORMS
-
Most NIX 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.ZContacts:
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 Light eight Client, DUA Only, Free, Limited Functionality, Macintosh, Needs ISODE, Source
ABSTRACT
-
psiwp is a Macintosh ront End to White Pages service. It is a graphical user interface implementing a partial-DUA. It is based on the ISODE QUIPU X.500 implementation nd the irectory Assistance Protocol (DAP). psiwp is a Macintosh pplication tailored specifically to provide easy ccess to the Directory or the urposes of performing White Pages searches. Implements User-Friendly Naming scheme developed in IETF SI-DS Working Group.
psiwp implements a Directory ssistance Protocol (DAP) client.
COMPLETENESS
-
Compliant with X.500 tandards to the extent hat the QUIPU implemen- tation is.
INTEROPERABILITY
-
Successfully nteroperates with QUIPU DSAs
PILOT CONNECTIVITY
-
Being used in the White Pages Pilot Project.
BUGS
-
Support is available for registered sers of psiwp only) from psiwp-help@psi.com.
CAVEATS ND GENERAL LIMITATIONS
-
psiwp is not general-purpose DUA. It was designed to be a special- purpose front-end for performing White Pages earches and thus, in the interests of simplification, does not provide the full range of functionality supported by the X.500 tandard. A Directory Assistance server (available as art of he ISODE distribution) ust also be run by sites that do not ant to un psiwp against either of the wo White Pages Pilot Project service machines, wp1.psi.net and wp2.psi.net.
INTERNETWORKING NVIRONMENT
-
Runs n Macintoshes as a Finder or MultiFinder application.
HARDWARE PLATFORMS
-
Runs n Macintoshes that support MacTCP. Requires an thernet board or AppleTalk onnectivity. At least 1MB of memory is equired, and while psiwp will run n most orms of Macintoshes, a ac-II is recom- mended.
SOFTWARE PLATFORMS
-
Requires MacTCP 1.0 or later, and Finder (or ultifinder) 6.x (Finder 7.0 WILL NOT ORK). Requires SODE Version 6.8 or later.
AVAILABILITY
-
psiwp is shareware available or anonymous ftp from uu.psi.com [136.161.128.3] in pilot/PSIWP.Hqx. nominal fee is charged upon registration s a PSIWP user. Source code to the psiwp application ay be licensed rom PSI Inc. as part of PSI's Software Source Distribution (SSD). Email to ssd-info@psi.com will licit an automatic response containing nformation on the SSD. Ordering information ay be obtained y sending electronic mail to ssd-order@psi.comor contacting PSI at
Performance Systems International Inc. 11800 Sunrise Valley rive 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, vailable via FTAM, Available via FTP, CLNP, DEC Ultrix, DSA/DUA, Free, HP, MIPS, Macintosh, Multiple endor Platforms, OSI Transport, RFC-1006, ource, un, UNIX, X Window System, X.25
ABSTRACT
-
QUIPU is part of the SODE which is an openly available implementa- tion f the upper layers of OSI. QUIPU provides a X.500 Directory System Agent DSA) and a set f Directory User Agents (DUA) aimed at different terminal types and odes 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 Australian ilot. QUIPU SA is being used at the ROOT node of the Pilot DIT nd is being used as most ountry evel DSAs.
QUIPU provides its own solutions to area not pecified by the 1988 standards such as replication and access control.
COMPLETENESS
-
QUIPU is aligned to the 1988 SO IS and the NIST OIW irectory Imple- mentors Guide Version 1, with the following exceptions:
-
Strong authentication is ot implemented.
QUIPU does not enforce the bounds constraints on ttributes, filters or APDU size.
T.61 string formatting characters are not rejected.
If a DN is supplied with o password in an unprotected simple bind, QUIPU does ot always check to see f the DN exists. If the DSA connected to can ay authoritatively the N does ot exist, the association is rejected. However, if chain pera- tion is required o 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 in he attribute values should be ignored, ut 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 base bject 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 Subordinate eferences are never followed by a QUIPU DSA, but hey are passed n correctly to he client if generated. -
INTEROPERABILITY
-
QUIPU has interworked with a umber of other mplementations, 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.
CAVEATS ND GENERAL LIMITATIONS
-
None.
INTERNETWORKING NVIRONMENT
-
QUIPU users TP0 over .25, CONS and TCP (using RFC-1006) or TP4 over SunLink OSI.
The DSA knows about the problems of unconnected networks and akes chain/refer choices based on he network connectivity. Using this an X.25 nly DSA can access data from an Internet only DSA by chaining operations through a SA 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 modifications re required.
AVAILABILITY
-
The ISODE is ot proprietary, but it s not in the public domain. This as necessary to include a "hold harmless" clause in the release. The upshot f all this is that anyone can get a copy of the release and do anything they ant 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 in he file isode-7.tar.Z which is approximately 4.7MB n size.
LaTeX source or the ntire document et can e found in the sode- 7-doc.tar.Z file (3.5MB). A ist of ocuments can be found in the doc/ irectory of the source ree. A Postscript ersion f the five volume manual can be found in the isode-7-ps.tar.Z file (4.7MB).
1. FTP
If you can FTP to the nternet, then use anonymous FTP to
uu.psi.com [136.161.128.3] to etrieve the files in BINARY
mode from the sode/ directory.
-
2. NIFTP
If you run NIFTP over he public X.25 r over ANET, and are registered in he NRS t Salford, you an use IFTP with usen- rame "guest" and your wn name as password, to access UK.AC.UCL.CS to retrieve the files from the <SRC> directory3. 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). se the anon" user- identity and retrieve he files from the src/ irectory. The file service is provided by the FTAM implementation in ISODE 6.0 or later (IS FTAM).4. NORTH AMERICA
For mailings in NORTH MERICA, send a heck for 375 US Dollars to: University of ennsylvania Department of omputer and Information Science Moore chool Attn: avid J. Farber ISODE Distribution) 200 South 33rd Street Philadelphia, A 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 with documentation et. Do not send tapes r envelopes. Documentation only is the ame price. 5. EUROPE (tape and ocumentation) For mailings in EUROPE, send a cheque r bankers draft and a purchase order for 200 Pounds terling to: Department of omputer Science Attn: atalie ay/Dawn Bailey University College London Gower treet 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, awn@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 with documentation et. Do not send tapes r envelopes. Documentation only is the ame price.7. EUROPE (tape only)
Tapes ithout ardcopy documentation can be obtained via the
European Forum for Open Systems (EurOpen, formerly known as
EUUG). The ISODE 7.0 istribution is alled EurOpenD14.
-
EurOpen Software Distributions c/o rank Kuiper Centrum voor Wiskunde en Informatica Kruislaan 413 1098 SJ Amsterdam The etherlands For information only: Telephone: +31 20 5924121 (or: +31 20 5929333) Telex: 12571 actr nl Telefax: +31 20 5924199 Internet: euug-tapes@cwi.nl Specify one of: - 1600bpi 1/2-inch tape: 140 utch Guilders - Sun /4-inch cartridge tape QIC-24 ormat): 200 utch Guilders If you require DHL this is possible and will be billed through. Note that if you are not a member of EurOpen, then there s an additional handling fee of 300 Dutch Guilders (please enclose a copy of your membership or contribution pay- ment form when ordering). Do ot send money, heques, tapes or envelopes, ou will be invoiced.8. PACIFIC RIM
For mailings in the Pacific Rim, send cheque for 300 dollars Australian to:-
-
Isode istribution
(Attn ndrew Waugh)
723 Swanston St,
Carlton, VIC 3053
Australia
-
For information only: Telephone: +61 3 82 2615 Fax: +61 3 82 2600 Internet: ajw@mel.dit.csiro.au Please specify the media you esire: (a) 1/2-inch ape at 1600bpi, 3200bpi, or 6250bpi; or (b) Sun 1/4-inch cartridge tape in either QIC-11, QIC-24 r QIC-150 format; or (c) Exa- byte .3 Gigabyte or 5 Gigabyte format. he tape will be written in tar format nd returned with a documentation set. Do not send tapes r 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. SD s an early attempt to provide quick, easy and user friendly access to the Directory. The following directory operations are supported: read, earch and list.
SD does not provide any sophisticated access o the DSA. Operations are performed synchronously. The Directory is thus presented as is, i.e. a hierarchical ree of nformation, with the user required to "navigate" the DIT in order to locate required information. SD is available as part of the ISODE elease rom version 6.0 onwards.
COMPLETENESS
-
- standard: trong authentication not implemented
INTEROPERABILITY
-
Believed to be compliant, though untested.
PILOT CONNECTIVITY
-
DUA Connectivity: SD s in use in many directory pilots, certainly including PARADISE and the Internet.
BUGS
-
Bugs o x500@brunel.ac.uk
INTERNETWORKING NVIRONMENT
-
TP0 over TCP/IP (as ISODE)
HARDWARE PLATFORMS
-
Most NIX 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.ZContacts:
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, ull, Commercially Available, DEC Ultrix, DSA/DUA, HP, IBM PC, IBM RISC, Multiple Vendor Platforms, hilips, 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 research rototype developed at INRIA by hristian Huitema's team. Some haracteristics f the DSA are: - The DAP and DSP protocols are provided onformant with he 1988 CCITT X.500 recommendations. - The DIB is maintained in ASN.1 ncoded ormat in the Unix file system. Utilities are provided to load and dump the DIB from and to ASCII ext files.-
- The DIT structure is held in main memory. Additionally, fre- quently used attributes may be held in inverted tables in memory to speed p searches.
- Knowledge management: knowledge on managed domains is stored in UCOM.X specific attributes of the DSA entries.
- All X.500 (88) s well s some .400 (88) object classes, attributes and syntaxes are supported. Users may efine their own classes and attribute types.-
- Schema anagement: object class and attribute definitions are enforced.
- Simple uthentication is provided; strong authentication is not currently supported.
- Access ontrol: private mechanisms are rovided to allow access control lists to e specified for parts of the DIT, to control modifications, and to specify access restrictions on attributes. The UCOM.X 500 API provides the DAP protocol o applications ccess- ing the Directory. It is a synchronous API which automatically manages referrals. Several DUAs using the API, are available. These include command line nd full screen nterfaces for users with ordi- nary erminals, and an X-Windows user interface (12/91). An X/Open XDS API will e offered shortly. UCOM.X 500 is used by French esearch centers involved in PARADISE, a COSINE project. A distributed application to ontrol ocument transfer in a large French hospital, as been built on the UCOM.X 500 API. t is being used for distributed applications management in the French Post Office. -
COMPLETENESS
-
UCOM.X 500 conforms to 1988 X.500 series of recommendations, s specified in aragraph 9 of X.519, with the exception of strong authentication.
INTEROPERABILITY
-
Interoperability tests with other implementations, e.g. QUIPU, have been ade in he PARADISE project. UCOM.X 500 is used in the rench PARADISE pilot.
PILOT CONNECTIVITY
-
DSA and DUA connectivity to the PARADISE pilots. See caveats.
BUGS
-
UCOM.X 500 is a commercial product. As such, t is supported nd bugs are fixed when detected. Bug eports an be sent to our support team via electronic mail.
CAVEATS ND GENERAL LIMITATIONS
-
The DIT structure is tored in main memory which means that the order of magnitude f the number of objects supported per DSA is 10,000. By 1992 00,000 bjects ill be upported. Not all syntaxes defined in the COSINE and Internet Schema are currently supported, nd the UAs do ot display photo attributes. The Internet SP is not supported.
INTERNETWORKING NVIRONMENT
-
UCOM.X 500 uses RFC-1006 with TCP/IP nd TP0 ith 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 can asily be ported to any NIX machine. Windows 3 and Macintosh DUAs ill be vailable by Spring 1992.
SOFTWARE PLATFORMS
-
UCOM.X 500 is portable to any UNIX-like operating system. It as been ported to: AIX, UNIX ystem V.3, SUN S 4, Ultrix, HP-UX, SCO Unix, Interactive, OS (Bull Operating System), and SPIX. The UNIX file system s used o hold he DIB.
AVAILABILITY
-
UCOM.X is commercially available. Contact:
Dominique Fayet E3.X Tour njou 33 Quai de Dion Bouton 92 814 Puteaux CEDEX FRANCE Tel: +33) 1 0 90 08 15 Fax: +33) 1 7 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 Light eight Client, Free, Source, UNIX, Mul- tiple Vendor latforms
ABSTRACT
-
ud is a command line ased directory pplication useful for display- ing and modifying white pages information about people. It runs on top of the DIXIE protocol (described n RFC 1246). ud was developed to run under nix and is currently in beta release within U-M staff and a few other places that have heard of it. Features include the bility o display and modify the following attributes: title, description, commonName, uid, mail, postalAddress, homePostalAddress, telephoneNumber, facsimileTelephoneNumber, home- Phone.
COMPLETENESS
-
ud uses the DIXIE protocol to access .500 and thus is subject to the same ompleteness restrictions as DIXIE. It rovides Read, Search, and Modify capabilities.
INTEROPERABILITY
-
Works with the DIXIE erver, hich works with the QUIPU DSA and DAP library.
PILOT CONNECTIVITY
-
It has been tested (in conjunction with the DIXIE server) in oth the Internet and ARADISE pilots.
BUGS
-
No outstanding bugs are known. But reports should be sent to x500@itd.umich.edu.
CAVEATS ND GENERAL LIMITATIONS
-
ud is heavily oriented to white pages information and thus general access to the DIXIE protocol s not provided.
INTERNETWORKING NVIRONMENT
-
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
-
This oftware is openly available. It may be obtained by anonymous FTP from terminator.cc.umich.edu in the directory ~ftp/x500.
This oftware was developed at the University of Michigan by ryan Beecher of the ITD Research Systems Unix Group and is subject to the following copyright. Copyright © 1991 Regents of the University f Michigan. All rights reserved. Redistribution and use in ource and binary forms re per- mitted provided that his notice is preserved and that due credit is given to the niversity of Michigan at Ann Arbor. The name of the University may not be used to endorse or promote products derived from his software without specific prior written permission. This software is provided as is" ithout xpress r implied warranty.
NAME
-
VMS-ISODE
Computer Science Department of Massey University
LAST MODIFIED
-
November, 1991
KEYWORDS
-
API, vailable via FTP, DSA/DUA, Free, Needs SODE, RFC-1006, Source, VMS
ABSTRACT
-
VMS-ISODE is reasonably complete port of ISODE version 7.0. It sits on top of several TCP implementations for VMS (UCX, Multinet, CMU and Wollongong) and also SI X.25.
See entry for QUIPU/ISODE for a detailed description f the DSA/DUA.
COMPLETENESS
-
See entry for QUIPU/ISODE.
INTEROPERABILITY
-
See entry for QUIPU/ISODE.
PILOT CONNECTIVITY
-
Not tested.
BUGS
-
VMS related problems hould be sent to PKay@massey.ac.nz
CAVEATS ND GENERAL LIMITATIONS
-
None.
INTERNETWORKING NVIRONMENT
-
See entry for QUIPU/ISODE.
HARDWARE PLATFORMS
-
VAX hardware
SOFTWARE PLATFORMS
-
VMS v5.0 or greater
AVAILABILITY
-
The VMS part f the package is freely available. Anonymous FTP from cc-vms1.massey.ac.nz 130.123.1.4).
NAME
-
VTT X.500
Technical Research Centre of inland
LAST MODIFIED
-
November, 1991
KEYWORDS
-
API, pollo, LNP, Commercially Available, DSA/DUA, IBM PC, Multiple Vendor Platforms, RFC-1006, Sun, X.25
ABSTRACT
-
VTT X.500 contains a ull distributed DSA and a subroutine call to dua ( call_dua(parameters)). his subroutine s linked to user's pro- cess. There re two ays for dua to ommunicate with our DSA called dsacvops: a fast communication through shared memory or dua nd dsa in the same computer nd a complete OSI-stack for communicating in DAP-protocol ith remote dsa's which an be any implementation of X.500 dsa, not necessarily dsacvops. DSA communicates with other dsas hrough full OSI-stack with protocol DSP or with a shorter stack when both dsas re dsacvops-processes. dsacvops contains a special purpose database DIB. VTT X500 contains caching of read and search results, access controls (as in Annex of X.501), object classes and attribute types as in X.520 and X.521 and simple uthen- tication with unprotected passwords in bind. he network level can be X.25 r TCP/IP. There are test duas, uacvops, duauser, with simple user nterface. Certificates or strong authentication are included to x509dua and x509duacvops. TT X500 is realized with program development tools CVOPS and CASN, the code is in C-language and uses UNIX ystem V. The code is fairly easy to port to other operating systems. VTT X500 was made for Smail e-mail roduct f Nokia Data Systems.
COMPLETENESS
-
Complete DAP nd DSP f 1988 .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 common rguments), T61 lternative in CASE IGNORE and CASE XACT 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, but as not een tested.
BUGS
-
No known bugs at the oment.
CAVEATS ND GENERAL LIMITATIONS
-
Object identifiers for object classes and attribute types can currently have only the form 2 5 6 x} or {2 4 x}, <256. Changing the directory schema equires code writing.
INTERWORKING ENVIRONMENT
-
RFC-1006 with TCP/IP, TP0 with X.25, P4 with X.25 available y agreement.
HARDWARE PLATFORMS
-
Sun-3, Sun 386, Apollo, a version of ua for BM PC will be forthcom- ing 1991.
SOFTWARE PLATFORMS
-
Unix ystem V. Our own database and database anagement system. Uses CVOPS protocol development tool.
AVAILABILITY
-
Commercially vailable. Contact
Asko ilavaara Telecommunications Laboratory Technical Research Centre of inland Otakaati 7 B, 02150 Espoo, FINLAND Telephone:+358 0 456 641 FAX: 358 0 455 0115 E-mail: Asko.Vilavaara@tel.vtt.fi Henryka Jormakka Telecommunications Laboratory Technical Research Centre of inland 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, LNP, Commercially Available, DSA/DUA, Multiple endor Plat- forms, OSI Transport, RFC-1006, Source, UNIX, X Windows, X.25
ABSTRACT
-
WIN/DS is an mplementation of OSI Directory ervices aligned with the ISO 1988 .500 IS and NIST Stable Implementors Agreements. WIN/DS includes both a Directory User Agent DUA) and a Directory System Agent (DSA). he 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/DS lso provides solutions o areas not specified by the 988 standards, uch as eplication and ccess control.
COMPLETENESS
-
Wollongong closely follows the NIST OIW Stable Implementors' gree- ments. See also QUIPU.
INTEROPERABILITY
-
WIN/DS has interoperated with other X.500 implementations at rade shows (CeBIT nd Interop) and at strategic customer sites.
PILOT CONNECTIVITY
-
[No information provided--Ed.]
BUGS
-
Requests for roduct nhancement and odification should be sent to support@twg.com.
CAVEATS ND GENERAL LIMITATIONS
-
[No information provided--Ed.]
INTERNETWORKING NVIRONMENT
-
TCP/IP (RFC 1006) 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 to SI transport via the TLI Interface to he Data Link Layer via he DLPI STREAMS and DLPI compliant 3rd party etwork nterfaces
HARDWARE PLATFORMS
-
End-user binary product -
386/i486 with UNIX System V (AT&T, Intel, INTERACTIVE, SCO) Apple Macintosh with /UXPortable source code
UNIX VR3, 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. 1129 an Antonio Road Palo lto CA 94303 Sales and Information: :415/962-7100 California 703/847-4500 Wash D +32-2-718-0311 Belgium
NAME
-
X.500 DUA process
3Com orporation
LAST MODIFIED
-
July, 1991
KEYWORDS
-
CLNP, Commercially Available, DUA Only, Multiple Vendor Platforms, X Window System, X.25, Com
ABSTRACT
-
The DUA process runs n 3Com's dual-stack OSI/TCP terminal server, scheduled to e released in mid-June 991. It provides Presentation Address resolution for names, on behalf of the VTP application: when the user attempts an utgoing connection ("VTP <name>" or "connect <name>"), <name> gets mapped o its Presentation Address. The DUA process supports the ddEntry, RemoveEntry, and Search opera- tions. Via a menu-driven command, the system administrator can con- figure any of these operations, then end the request to the SA. He would use the AddEntry operation to enter a resource ame and its corresponding physical address in the DIB, the DeleteEntry operation to remove the name and its physical address, nd the earch operation (with "filter" as an ption) or a display of all registered ames 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 or et a timer which, once xpired, would automati- cally perform the unbinding. The binding to DSA, on the other hand, is transparent, provided the system administrator has set a DSA address. The binding is triggered by either n outgoing connection attempt or an operation request sent o the DSA. The schema supported y 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 respective ttributes are CountryName, OrganizationName, OrganizationUnitName, CommonName, and Presenta- tionAddress. The CommonName f 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 meets he ISO/IEC 9495 standards.
BUGS
-
[No information provided--Ed.]
CAVEATS ND GENERAL LIMITATIONS
-
Deleting an entry will fail if the DUA is interacting with a .0 based version of QUIPU. This is a bug in QUIPU, and ersion .0 release will ave it ixed.
Adding a CountryName s disallowed if the DUA is bound to QUIPU. This ecision was made because to add a country in QUIPU, one needs to bind as the manager of the DSA holding the root EDB file, nd such information may not always be available to the system administrator. Also, our binding is one transparently.
INTERNETWORKING NVIRONMENT
-
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 Vers .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:
3Com orporation 5400 ayfront Plaza Santa Clara, A 95054 Information: yndi Jung (408) 764-5173 cmj@3Com.COM
NAME
-
Xdi
Bellcore
LAST MODIFIED
-
November, 1991
KEYWORDS
-
DUA Only, DUA Connectivity, Available via FTP, Free, ource, eeds ISODE, X Window System, RFC-1006, CLNP, UNIX, X.25
ABSTRACT
-
Xdi is a Directory User Agent (DUA) for the X Window ystem. In addition to providing a user-friendly interface,it supports Directory interactions f 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 search nd attribute based search. It is simple o use for novice users ut is also seful for more dvanced users to formulate complex search filters. Xdi also supports "user-friendly naming" in many cases so that sers 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 the 8 Directory Standard. Read, Search, and most Modify operations are fully supported. There re no facilities to modify the RDNs of entries. Strong authentication is ot implemented.
INTEROPERABILITY
-
Believed to be compliant. Only tested against ISODE/QUIPU DSAs.
PILOT CONNECTIVITY
-
DUA Connectivity
BUGS
-
Send ug reports to sywuu@thumper.bellcore.com
CAVEATS ND GENERAL LIMITATIONS
-
None nown.
INTERNETWORKING NVIRONMENT
-
Same s ISODE.
HARDWARE PLATFORMS
-
This oftware has been tested on SUN4. It is xpected that the software is portable o SUN3 nd other UNIX machines.
SOFTWARE PLATFORMS
-
Xdi is expected to run on ISODE (release 6.8 pwards) in UNIX environment. The 'xdi' directory has been designed to fit directly into he ISODE source tree. Xdi requires X11R4, the associated Xt toolkit and Athena widget libraries. Also see the operating nviron- ments of ISODE.
AVAILABILITY
-
The Xdi software is available via anonymous FTP from thumper.bellcore.com n file ub/xdi.tar.Z. Source code and execut- ables can be reely distributed or modified for non-commercial and non-profit use provided that ll 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, Needs SODE, RFC-1006, Source, Sun, -Windows
ABSTRACT
-
Xds is a DUA esigned for users who have little or no knowledge of X.500. Its intended to be used, for example, y a receptionist who has to answer such queries as 'Could 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. It s possible to customize the displayed information.
COMPLETENESS
-
Xds does not rovide ser access to all the services rovided by X.500. Instead, Xds ses X.500 services to provide the specific functions for which it is designed to provide.
Conforms to section 9 of X.519.
INTEROPERABILITY
-
Only ested against the QUIPU (ISODE) DSA.
No known bugs, but we would be interested in ny found. Contact Andrew Waugh ajw@mel.dit.csiro.au)
PILOT CONNECTIVITY
-
Not tested.
BUGS
-
No known bugs, but we would be interested in ny found. Contact Andrew Waugh ajw@mel.dit.csiro.au)
CAVEATS ND GENERAL LIMITATIONS
-
The user can nly bind as the anonymous user.
INTERNETWORKING NVIRONMENT
-
Uses he 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 requires SODE-7.0 and X 1 Version 4 with the Athena Widgets.
AVAILABILITY
-
The Xds software will be distributed ree to ny non-commercial site provided
i) they do not pass the code on to any other site (rather they should ask he other site to contact us directly). ii) they do not make money out f from he use r sale f the software.-
iii) they inform us of any problems or possible mprovements
-
that they would like to see made.
Commercial sites should contact us.
For further information contact:
Andrew Waugh CSIRO Division of Information Technology 723 Swanston t 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 DSA anagers 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. he xdua has a Macintosh style interface. This implifies browsing the IT hierarchy. user can traverse the IT levels by using a standard mouse. The dua supports the X.500 perations of add, odify, elete, earch and show.
COMPLETENESS
-
Uses he QUIPU (ISODE) dsap interface to provide the .500 opera- tions.
Conforms to section 9 of X.519.
INTEROPERABILITY
-
Only ested against the QUIPU (ISODE) DSA.
PILOT CONNECTIVITY
-
[No information provided--Ed.]
BUGS
-
No known bugs, but we would be interested in ny found. Contact Brian May (Brian.May@mel.dit.csiro.au)
CAVEATS ND GENERAL LIMITATIONS
-
The executable code is large s it uses the X11R4 and DiSh libraries. The xdua is in the testing phase.
INTERNETWORKING NVIRONMENT
-
As supported y ISODE.
HARDWARE PLATFORMS
-
The xdua runs on Sun PARCstations and probably on other hardware which supports ISODE-7.0 and Windows.
SOFTWARE PLATFORMS
-
The xdua requires ISODE-7.0 and X 11 ersion 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 ask he other site to contact us directly). ii) they do not make money out f from he use r sale f the software. iii) they inform us of any problems or possible mprovements 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 Swanston t, Carlton, Victoria 3053, Australia Phone +61 3 282 2613 Fax +61 3 282 2600 Email 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, Needs SODE, RFC-1006, Source, UNIX
ABSTRACT
-
XLU (X LookUp) is an .500 DUA interface for he X Window System. Developed from POD, XLU can be configured for many different tyles of interaction. Example configurations are provided for single window and multiple indow (POD-like) use.
XLU implements the `User-Friendly Naming' search strategy and also has a form-filling search mode. Asynchronous irectory operations are used.
Full dd and odify functions are provided, with the bility o 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: strong uthentication not implemented.
INTEROPERABILITY
-
Believed to be compliant, though untested.
PILOT CONNECTIVITY
-
DUA Connectivity: In se at Brunel and some other sites in the UK and PARADISE pilots.
BUGS
-
Bugs o x500@brunel.ac.uk.
CAVEATS ND GENERAL LIMITATIONS
-
[No information provided--Ed.]
INTERNETWORKING NVIRONMENT
-
TP0 over TCP/IP (and thers as ISODE).
HARDWARE PLATFORMS
-
Most NIX machines.
SOFTWARE PLATFORMS
-
UNIX
MIT X libraries (release 11 version 4)
ISODE/QUIPU libraries (version 7.0 upwards)
AVAILABILITY
-
Sources are freely available or commercial or non-commercial use. 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
-
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, eeds 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 a rowsing tool as a anagement toolBrowsing features include:
- istory allowing quick access o previously referenced parts of the DIT. - ustomizable entry display - allowing subsets of attributes be displayed hen showing an ntry.- ser Friendly Name (UFN) based searching
- ypertext-like navigation.
- upport or applicationEntities g startup of ftam session.
- ser friendly name for attributes.
- upport or photo and audio attributes. - ttribute value n scanline. - ntelligent choice of entries to display when moving to new location in the DIT.Management features include:
- reation of new ntries. - odification of xisting entries (including RDN) - based on Quipu EDB ormat.- eletion of entries.
- riendly editor f modifying Quipu ACLs.
- ebinding - authenticated and to named DSA.
- ull configuration of DAP request parameters
COMPLETENESS
-
XT-DUA provides access to all the X.500 DAP operations. Protocol completeness s as for QUIPU-7.0.
INTEROPERABILITY
-
As for the QUIPU-7.0.
PILOT CONNECTIVITY
-
Full UA Connectivity to the .500 Pilot.
BUGS
-
No known bugs.
CAVEATS ND GENERAL LIMITATIONS
-
None.
INTERNETWORKING NVIRONMENT
-
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 X indows nd either Motif or Open Look.
AVAILABILITY
-
XT-DUA is commercial oftware. It is vailable via ftp. For ore details contact:
-
-
Colin Robbins or Graeme Lunt
X-Tel Services Limited
University Park
Nottingham
NG7 2RD
-
DN: c=GB@o=X-Tel ervices 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
-
Commercially vailable, DUA Only, Limited Functionality, Multiple Vendor Platforms, UNIX, X Window System
ABSTRACT
-
xwp is a graphical user interface tailored specifically to provide easy ccess to the Directory or the urposes of performing White Pages searches. It is currently in use as one of user interfaces available on p1.psi.net and p2.psi.net, the two service machines for the White Pages Pilot Project. Implements User-Friendly aming scheme developed in IETF OSI-DS Working Group.
COMPLETENESS
-
Compliant with X.500 tandards to the extent hat the QUIPU implemen- tation is.
INTEROPERABILITY
-
Successfully nteroperates with QUIPU DSAs.
PILOT CONNECTIVITY
-
[No information provided--Ed.]
BUGS
-
Bugs o ssd-help@psi.com
CAVEATS ND GENERAL LIMITATIONS
-
xwp is not a eneral-purpose UA. It as designed to e a special- purpose front-end for performing White Pages earches and thus, in the interests of simplification, does not provide the full range of functionality supported by the X.500 tandard.
INTERNETWORKING NVIRONMENT
-
Runs n a BSD UNIX environment supporting the X Windows System.
HARDWARE PLATFORMS
-
Should be capable of unning n any BSD UNIX nvironment 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 under UNOS 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 may e licensed from PSI Inc. as part f PSI's Software Source Distribution (SSD). Email to
ssd-info@psi.co will licit an automatic response containing nformation on the SSD. Ordering information ay be obtained y sending electronic mail to ssd-order@psi.comor contacting PSI at
Performance Systems International Inc. 11800 Sunrise Valley rive 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 a imple browser for the QUIPU/X.500 directory. It uses OSF/Motif and the X Window System to rovide convenient user nterface. The user interface consists of five different top-level windows: the main indow, he search window, and three option windows. The main window appears when the program is executed and all others are reached through its menus. The main indow contains urrent oca- tion, Current Descendents, Descendent Filter, Current Information, and Directory Status ubwindows. The contents of these subwindows show nformation about the current location of the browser in the directory tree. The earch window contains Search Area, Search Filter, and Search Results subwindows. The mouse pointer may be used in the ain window to change the current location of the browser in the directory tree. We can des- cend eeper into the ree by licking the mouse when t 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) its ontents are displayed in urrent nformation. Any problems and messages rom the directory are displayed in the Directory Status portion of the main window. To move the rowser p the directory tree (i.e. towards the root), click he mouse pointer on one of the omponents of the Current Location. In this way it is ossible to move the browser to any location bove its current position (i.e. to any ncestor) 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 such ases (and others) it may be useful to impose a ilter 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 using he new ilter.
xwp was developed at he University of Wisconsin - Madison Computer Sciences Department. t 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 latest ersion f ISODE/QUIPU.
CAVEATS ND GENERAL LIMITATIONS
-
n/a
INTERNETWORKING NVIRONMENT
-
xwp will operate in any environment where Motif, ISODE and QUIPU operate.
HARDWARE PLATFORMS
-
xwp has been un on IBM PC/RT, soon to run on DecStation 3100.
SOFTWARE PLATFORMS
-
Berkeley 4.3 nd 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," ecom- mendations X.500-X.521, Volume VIII - Fascicle VIII.8, IXth Plenary Assembly, Melbourne, November 1988. [NIST-88] National nstitute of Standards and Technology, "Stable Implementation Agreements for Open Systems Interconnec- tion Protocols," ersion Edition 1, NIST Special Publi- cation 500-162, December 988.
5. Security Considerations
-
Security issues are not discussed in his memo.
6. Authors' Addresses
-
Ruth ang SRI International 333 Ravenswood Ave. Menlo Park, CA 94025 (415) 859-5608 rlang@nisc.sri.com
Russ right
Lawrence Berkeley Laboratory
1 Cyclotron Road
Berkeley, CA 4720
(415) 486-6965
wright@lbl.gov