Lawrence Livermore National Laboratory
S. ataluri
AT&T Bell Laboratories
Editors
May 1994
A Revised Catalog of Available X.500 Implementations
Status of this Memo
-
This emo provides information for the Internet community. This memo does ot specify an Internet tandard of any ind. Distribution of this emo is nlimited.
Abstract
-
This ocument is the esult of a survey that athered new or pdated descriptions f currently available implementations of X.500, including commercial roducts and openly available offerings. This document is a revision of RFC 1292. We contacted each contributor in RFC 1292 and equested an update and ublished the survey template in several mailing lists and obtained new product descriptions.
This ocument contains detailed description of twenty six (26) X.500 implementations - DSAs, DUAs, and DUA interfaces.
1. Introduction
-
This ocument catalogs currently available implementations of X.500, including commercial roducts and openly available offerings. For the purposes f this urvey, e classify X.500 products as,
DSA
DSA is an OSI pplication process that provides the Directory unctionality,DUA
DUA is an OSI pplication process that represents a user in
ccessing the Directory nd uses the DAP to communicate ith a
SA, and
-
DUA Interface
DUA Interface s an application process that represents a user n accessing the Directory using either AP but upporting only subset of the AP functionality or a protocol ifferent from AP to communicate with DSA or DUA.Section 2 of his document contains a listing of implementations cross referenced by keyword. This list should aid in identifying implementations that eet your criteria.
To compile this catalog, the DS Working Group solicited input from the X.500 community by surveying several Internet mailing lists, including: iso@nic.ddn.mil, sode@nic.ddn.mil, osi-ds@cs.ucl.ac.uk, and ietf-ids@umich.edu. We also contacted many people by telephone and sent the emplate to several individuals nd mailed a floppy disk containing the survey template to a person who did not have Internet access. Readers are encouraged to submit comments regarding both the orm and content of his memo. New submissions are welcome. Please direct input to the Integrated Directory Services (IDS) Working Group (ietf-ids@umich.edu) or to the editors. IDS will roduce ew ver- sions of this document when a sufficient number of changes have been received. This will e determined by the IDS chairpersons.
1.1 Purpose
-
The Internet as experienced steady growth n X.500 piloting activities. his document hopes to provide an easily accessible source of information on X.500 implementations for those who ish to consider X.500 technology for deploying a Directory service.
1.2 Scope
-
This ocument contains descriptions of both free and ommercial X.500 implementations. It oes not provide instructions on how to nstall, run, r manage these mplementations. The descriptions and indices are provided o make he readers aware of available options and thus enable more informed hoices.
1.3 Disclaimer
-
Implementation descriptions were written by implementors and endors, and not by the editors. We worked with the description authors to ensure uniformity and readability, but can not guarantee the ccuracy or completeness of the descriptions, r the stability of the implementations.
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 has a list f references.
Section 6 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 IDS Working Group. Our special thanks to the editors of FC 1292, Ruth Lang and Russ right who helped us get started and made key suggestions that enabled us to learn from their experience. We also acknowledge and appreciate the efforts of Ken Rossen n obtaining six descriptions.
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 implied, reference to particular capability n the implementation description text, or 2) 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 FTP
-
mplementation is available using FTP.
Commercially vailable
his implementation can e purchased.
Free
vailable at no harge, lthough other restrictions may pply.
-
Limited Availability
eed to ontact rovider for terms and conditions of istribution.Source
ource code is available, potentially at an additional cost.
2.1.2 Conformance with roposed Internet Standards
-
These RFCs specify standards rack protocols or the nternet community. Implementations which conform to hese evolving proposed standards have a higher probability of interoperating with other implementations deployed on the Internet.
RFC-1274
mplementation supports FC 1274: Barker, P., and S. Kille, The OSINE and Internet X.500 Schema, University College, London, ngland, November 1991.RFC-1276
mplementation supports FC 1276: Kille, S., Replication and istributed Operations extensions to provide an nternet irectory using .500, University College, London, England, ovember 1991.RFC-1277
mplementation supports FC 1277: Kille, S., Encoding etwork
ddresses to support operation over non-OSI lower layers,
niversity College, London, England, November 1991.
-
RFC-1485
mplementation supports FC 1485: Kille, S., A String
epresentation of Distinguished ames, ISODE Consortium, July
993.
-
RFC-1487
mplementation supports FC 1487: Yeong, W., T. owes, and S.
ille, X.500 Lightweight Directory Access Protocol, July 1993.
2.1.3 Consistence with nformational and Experimental Internet FCs
-
These RFCs provide information to the Internet community and re not Internet standards. Compliance with these RFCs is not necessary for interoperability but ay enhance functionality.
RFC-1202
mplementation supports FC 1202: Rose, . T., Directory
-
-
ssistance Service. February 1991.
RFC-1249
-
mplementation supports FC 1249: Howes, T., M. mith, and B.
eecher, DIXIE Protocol pecification, University of Michigan,
ugust 1991.
-
RFC-1275
mplementation supports FC 1275: Kille, S., Replication
equirements to rovide n Internet Directory using X.500,
niversity College, London, England, November 1991.
-
RFC-1278
mplementation supports FC 1278: Kille, S., A tring encoding
f Presentation ddress, University College, London, England,
ovember 1991.
-
RFC-1279
mplementation supports FC 1279: Kille, S., X.500 and omains, niversity College, London, England, November 1991.RFC-1484
mplementation supports FC 1484: Kille, S., Using the OSI
irectory to achieve User Friendly Naming, ISODE Consortium,
uly 1993.
2.1.4 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 Interface
mplementation is a DUA-like program that uses either DAP, but
upporting only subset of the AP functionality, or uses a
rotocol different from AP to communicate with DSA or DUA.
-
DUA Only
mplementation consists f a DUA only. o DSA is included.
-
LDAP
-
UA interface program uses the Lightweight Directory Access rotocol (LDAP).
2.1.5 Internetworking Environment
-
CLNS
mplementation operates ver the OSI ConnectionLess Network ervice CLNS).OSI Transport
mplementation operates ver one or more OSI transport rotocols.RFC-1006
mplementation operates ver RFC-1006 with TCP/IP transport ervice. RFC-1006 is an Internet Standard.X.25
mplementation operates ver OSI X.25.
2.1.6 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.7 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.Motif
mplementation provides Motif-style X indow user interface.
-
Needs ISODE
SODE is required to compile and/or use his implementation.
-
OpenLook
mplementation provides n OpenLook-style X Window user nterface.X Window System
mplementation uses the Window System o provide its user nterface.
2.1.8 Operating nvironment
-
- mplementation runs on a 386-based platform.
Bull
-
mplementation runs on a Bull platform.
CDC
-
mplementation runs on a CDC MIPS platform.
DEC ULTRIX
-
mplementation runs under DEC ULTRIX.
DEC Vax OpenVMS
mplementation runs on a DEC VAX platform running OpenVMS.
-
HP
-
mplementation runs on an HP platform.
IBM PC
-
mplementation runs on a PC.
IBM RISC
-
mplementation runs on IBM's RISC UNIX workstation.
ICL
-
mplementation runs on an ICL platform.
Macintosh
-
mplementation runs on a Macintosh.
Multiple Vendor Platforms
mplementation runs on more than one hardware platform.
-
Sequent
-
mplementation runs on a Sequent platform.
SNI
-
mplementation runs on a Siemens Nixdorf platform.
Solbourne
-
mplementation runs on a Solbourne platform.
Sun
-
mplementation runs on a Sun platform.
Tandem
mplementation runs on a Tandem latform.
UNIX
-
mplementation runs on a generic UNIX platform.
Wang
-
mplementation runs on a Wang RISC platform.
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: BULL S.A. (Bull X500-DS and X500-DUA), EC X.500 DSA (DEC X.500 irectory Server), DEC X.500 Admin (DEC .500 Administration Facility), HP .500 DD (HP X.500 Distributed Directory), LDAP (University f Michigan LDAP Implementation), OSI Access & Dir OSI Access and irectory), and raxis (Traxis Enterprise Directory). 386 CLNS athWay essaging Bull S.A. C-DUA DEC X.500 SA COM X.500 DEC X.500 dmin DIR.X API HP X.500 DD HP X.500 DUA ull S.A. OSI Access & Dir ustos PathWay Messaging EC X.500 DSA Traxis EC X.500 Admin UCOM X.500 IR.X Wang OPEN/services P X.500 DD XT-DUA P X.500 DUA XT-QUIPU DAP SI Access & Dir Commercially Available UIPU raxis Bull S.A. COM X.500 DEC X.500 SA DEC X.500 dmin Available via FTP DIR.X Directory 00 ustos HP X.500 DD E HP X.500 DUA OS-DE OSI Access & Dir DAP PathWay Messaging dap-whois++ PC-DUA aX.500 Traxis di UCOM X.500 Wang OPEN/services Bull XT-DUA XT-QUIPU ull S.A. COM X.500 DEC ULTRIX T-DUA T-QUIPU DEC X.500 SA DEC X.500 dmin CDC LDAP ldap-whois++ SI Access & Dir UCOM X.500 DEC VAX OpenVMS-
-
-
-
-
-
-
-
-
DEC X.500 SA
DEC X.500 dmin
-
-
-
-
-
-
-
-
DSA Connectivity DUA Interface IR.X DE SI Access & Dir DOS-DE athWay essaging LDAP UIPU ldap-whois++ COM X.500 maX.500 T-QUIPU OSI Access & Dir Pathway Messaging DSA Only PC-DUA QuickMailDUA EC X.500 DSA Wang OPEN/services T-QUIPU DUA Only DSA/DUA DEC X.500 dmin ull S.A. HP X.500 DUA ustos MXLU IR.X PC-Pages irectory 500 Xdi P X.500 DD XLU SI Access & Dir XT-DUA athWay essaging UIPU Free raxis COM X.500 Custos ang OPEN/services DE DOS-DE DUA Connectivity LDAP ldap-whois++ IR.X maX.500 DAP MXLU aX.500 QUIPU XLU Xdi SI Access & Dir XLU athWay essaging C-DUA HP C-Pages UIPU DIR.X COM X.500 HP X.500 DD di HP X.500 DUA LU LDAP T-DUA *Traxis Wang OPEN/services XT-DUA XT-QUIPU IBM PC Limited Functionality OS-DE Custos DAP Wang OPEN/services SI Access & Dir Xdi athWay essaging C-DUA Macintosh C-Pages raxis LDAP ang OPEN/services maX.500 PathWay Messaging IBM RISC *Traxis IR.X Motif DAP Traxis DEC X.500 dmin COM X.500 MXLU ang OPEN/services UCOM X.500 T-DUA XT-DUA T-QUIPU Multiple Vendor Platforms ICL Custos XT-DUA DE T-QUIPU DOS-DE LDAP Included In ISODE MXLU PathWay Messaging E PC-Pages QUIPU LDAP UCOM X.500 Xdi E XLU OS-DE XT-DUA DAP XT-QUIPU dap-whois++ aX.500 Needs ISODE SI Access & Dir Pathway Messaging Custos C-DUA DE PC-Pages MXLU QuickMailDUA Limited Availability Xdi XLU C-Pages uickMailDUA OpenLook RFC-1249 COM X.500 OSI Access & Dir T-DUA RFC-1274 OSI Transport DE ull S.A. DEC X.500 SA ustos DEC X.500 dmin EC X.500 DSA DOS-DE EC X.500 Admin LDAP IR.X maX.500 P X.500 DD OSI Access & Dir P X.500 DUA QuickMailDUA athWay essaging QUIPU C-Pages Traxis UIPU UCOM X.500 raxis Xdi ang OPEN/services XT-DUA T-DUA XT-QUIPU T-QUIPU RFC-1275 RFC-1006 OSI Access & Dir ull S.A. QUIPU ustos EC X.500 DSA RFC-1276 EC X.500 Admin IR.X OSI Access & Dir irectory 500 QUIPU DAP XT-QUIPU SI Access & Dir athWay essaging RFC-1277 C-Pages UIPU DEC X.500 SA raxis DEC X.500 dmin COM X.500 DIR.X ang OPEN/services OSI Access & Dir T-DUA PathWay Messaging T-QUIPU QUIPU UCOM X.500 RFC-1202 XT-DUA XT-QUIPU SI Access & Dir athWay essaging RFC-1278 Sequent EC X.500 DSA EC X.500 Admin UCOM X.500 SI Access & Dir athWay essaging SNI UIPU COM X.500 DIR.X T-DUA T-QUIPU Solbourne RFC-1279 XT-DUA XT-QUIPU SI Access & Dir UIPU Source COM X.500 T-QUIPU DE LDAP RFC-1484 MXLU QUIPU E Xdi OS-DE XLU LDAP maX.500 Sun UIPU di Custos T-DUA Directory 00 T-QUIPU LDAP ldap-whois++ RFC-1485 OSI Access & Dir PathWay Messaging DAP QuickMailDUA aX.500 QUIPU UIPU Traxis T-QUIPU UCOM X.500 Xdi RFC-1487 XT-DUA XT-QUIPU E OS-DE Tandem DAP dap-whois++ UCOM X.500 aX.500 C-DUA UIPU UNIX ustos E dap-whois++ XLU UIPU COM X.500 di LU Wang ang OPEN/services X Window System XLU SI Access & Dir di LU T-DUA X.25 ull S.A. EC X.500 DSA EC X.500 Admin IR.X irectory 500 P X.500 DD P X.500 DUA SI Access & Dir athWay essaging UIPU raxis COM X.500 ang OPEN/services T-DUA T-QUIPU -
3. Implementation Descriptions
-
In the following pages you will find escriptions of .500 implementations listed in alphabetical order. In the case of name collisions, the name f the responsible organization, in square brackets, has been used to distinguish the implementations. ote that hroughout this ection, the page header reflects the name of the implementation, not the date of the document. The descriptions follow a common format, as described elow:
NAME
he name of the .500 implementation and the name of the
esponsible organization. Implementations with registered
rademark indicate this y appending "(tm)", e.g., GeeWhiz(tm).
-
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.
-
COMPLIANCE (applicable only for DSAs nd DUAs)
statement of compliance with respect to the 1988 CCITT ecommendations .500-X.521 [CCITT-88], pecifically Section 9 f X.519, or the 1988 NIST OIW Stable Implementation Agreements NIST-88].CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
statement of compliance with respect to the several proposed nternet Standards.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
statement of compliance with respect to the several nformational and experimental Internet FCs.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 uggested 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. DATE AST UPDATED or HECKED he month and year within which his implementation description as last modified.
NAME
-
X500-DS
X500-DUA
Bull .A.
KEYWORDS
-
API, ull, CLNS, Commercially Available, DSA/DUA, OSI Transport, RFC-1006, X.25
ABSTRACT
-
X500-DS and X500-DUA re integral part of the large Bull OSI ffer. Although based on the DCE/GDS (Distributed Computing Environment/Global Directory ervice) of OSF, these two products may be installed nd used without DCE environment. X500-DS is designed to implement oth the DUA and the DSA functions, whilst X500-DUA only provides the UA functions. The X500-DUA ackage ontains: - The standards APIs OM (X/Open OSI-Abstract-Data Manipulation API) and XDS (X/Open Directory Service API) for he development f portable applications, - A core DUA o translate all user's equests (bind, ead, list, compare, modify, modifyRDN, search, add, remove, unbind ...) into the DAP protocol used for communication with distant DSAs, - The OSI standard protocols ASN.1, OSE, ACSE, Presentation and Session) for communication ith the distant DSAs. The interface with the low layers of the tack being XTI. RFC-1006 is supported under XTI or the Session, - A DUA Cache to improve performances when accessing emote DSAs, - A management application for configuration f the product, controlling the operations nd managing logs and traces, - A user application or the anipulations of the database entries.The X500-DS package contains:
- All components of the X500-DUA, - A core DSA o process all requests eceived from distant DUAs through DAP protocol or from distant DSAs through DSP protocol. It upports the referral, chained and multi-casting modes of operation, ccess control lists, simple authentication, management f knowledge information (for distribution, shadows and copies of sub-trees), - A management application for managing the schema information (creation, eletion and modification of object classes and f attribute types, management of the ules of the DIT), - A C-ISAM database.
COMPLIANCE (applicable only for SAs and DUAs)
-
Compliant with EWOS and 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. he X/Open standard XDS nd XOM interface libraries are also rovided. When he product is installed with he DCE nvironment, XDS and XOM interfaces are lso used to access DCE/CDS (Local Cell Directory ervice) transparently. GDA (Global Directory Agent) serves then s the gateway between the DCE CDS and GDS.
It is planned to support full 1992 extensions in the roducts for 1995.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
[No information provided--Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
[No information provided--Ed.]
INTEROPERABILITY
-
This mplementation of DAP and DSP can interoperate with other X.500 implementations from ther Cebit demo participants including BM, HP, ICL, iemens-Nixdorf, etc. It also interoperates with ISODE QUIPU.
PILOT CONNECTIVITY
-
[No information provided--Ed.]
BUGS
-
[No information provided--Ed.]
CAVEATS ND GENERAL LIMITATIONS
-
[No information provided--Ed.]
INTERNETWORKING NVIRONMENT
-
OSI TP4 with LNP (WAN - LAN) OSI TP0, 2 & 4 ith X.25 (WAN) FC-1006 with CP/IP Either BSD sockets or XTI can be sed to ccess the transports Through XTI, both SI and CP/IP protocols are possible on the same machine, thus permitting to uild a irectory Service distributed on OSI and TCP/IP networks.
HARDWARE PLATFORMS
-
DPX/2, DPX/20
SOFTWARE PLATFORMS
-
Unix OS2, Unix BOSX, AIX
AVAILABILITY
-
- Q 93
Please contact:
Daniel Monges Tel: + (33) 76 39 75 00 ext. 7449 Fax: + (33) 76 39 78 56 e-mail: D.Monges@frec.bull.fr
DATE LAST UPDATE or CHECKED
-
November 25th, 1993
NAME
-
OSI Access and Directory Control Data ystems ncorporated.
KEYWORDS
-
API, LNS, CDC, Commercially vailable, DSA Connectivity, DSA/DUA, DUA Connectivity, DUA Interface, IBM C, LDAP, RFC-1006, RFC-1202, RFC-1249, RFC-1274, RFC-1275, RFC-1276, RFC-1277, RFC-1278, RFC-1279, Sun, Window System, X.25
ABSTRACT
-
OSI Access and Directory includes several DUAs and a UIPU based DSA (originally based on ersion .6) with enhancements. he DUA/DSA enhancements nclude: - Directory API based on the .400 API. - Support for X.400 objects including those to support MHS use of irectory to support MHS Routing. - Integration with Control Data's MailHub (X.400 MHS) products. - X Windows, urses and command line ased DUA interfaces on NIX. These interfaces support the full set of Directory perations. - Windows 3.x interface on PCs. - A DUA daemon that provides irectory access for applications. - LDAP 2.0 and 3.0 support. - Directory synchronization tools for synchronizing most PC/Mac/Dec mail directories with X.500. - Enhanced photo attribute support. - ACL enhancements. - Hash indexing for fast string search. - DIXIE, DAD nd PH.X500 support. - SNMP based onitoring and management of DSAs. Control Data ystems ffers complete ntegration services to esign, plan, install, configure, tailor and aintain X.500 services. These services may nclude he preparation f customer unique DUAs nd tools for X.500 integration, ynchronization, operational control and management. OSI Access and Directory s in production use at everal government, commercial and academic sites. Some sites are supporting Directories in excess of 120,000 entries.
COMPLIANCE (applicable only for SAs and DUAs)
-
OSI Access and Directory complies with the 1988 CCITT Recommendations X.500-X.521 [CCITT-88] and the 1988 NIST OIW table Implementation Agreements [NIST-88]. OSI Access and irectory only supports imple authentication or no uthentication. SI Access and Directory complies with all static and ynamic equirements of .519. OSI Access and Directory an act s a first-level DSA.
OSI Access and Directory will support some 1993 X.500 extensions in 1994 ith full support in 1995/1996.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
OSI Access and Directory is compliant with the following RFCs: [RFC 1274], [RFC 1276], and [RFC 1277].
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
OSI Access and Directory is compliant with the following RFCs: [RFC 1202], [RFC 1249], [RFC 1275], [RFC 1278], and [RFC 1279].
OSI Access and Directory also supports the required objects, attributes and attribute syntaxes for MHS use of Directory to support MHS Routing.
INTEROPERABILITY
-
OSI Access and Directory was ested against HP, DEC, SODE Consortium and Wollongong implementations at the COS Interoperability Test Lab in May 1993. he OSINET Interoperability Tests were used. Please refer OSINET or test results. OSI Access and Directory has also been informally tested at rade shows with implementations from UNISYS and Retix.
PILOT CONNECTIVITY
-
OSI Access and Directory is connected via DSAs and DUAs to the PSI White Pages Project. SI Access and Directory provides the base routing tree or the HS Use f Directory pilot (Longbud) on he Internet.
BUGS
-
Control Data ystems rovides complete software maintenance services with roducts.
CAVEATS nd GENERAL LIMITATIONS
-
[No information provided--Ed.]
INTERNETWORKING NVIRONMENT
-
RFC1006 with CP/IP, P4 with CNLS, TP0 with .25.
HARDWARE PLATFORMS
-
OSI Access and Directory runs on all IPS and SUN SPARC platforms. Windows based DUAs available ith OSI Access nd Directory run on Windows 3.x compatible IBM PCs.
SOFTWARE PLATFORMS
-
Distributed and supported for Sun OS ersion .1.x, Sun Solaris 2.x and Control Data EP/IX (Control Data's MIPS based OS). Other platforms are pending. TP4 connectivity on SUN OS requires SUN OSI.
AVAILABILITY
-
Commercially vailable from:
Control Data ystems nc. Network Solutions, ARH290 4201 exington Avenue North Arden Hills, H 55126-6198 U.S.A. 1-800-257-OPEN (U.S. nd Canada) 1-612-482-6736 (worldwide) FAX: -612-482-2000 (worldwide) EMAIL: info@cdc.com or s=info;p=cdc;a=attmail;c=us
DATE LAST UPDATED or CHECKED
-
November 22nd, 1993
NAME
-
Custos
National Institute of Standards and Technology
KEYWORDS
-
API, vailable via FTP, DSA/DUA, Free, Limited Functionality, Multiple Vendor Platforms, Needs 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 SPARCstations under SunOS 4.1.1. All nderlying services are rovided by the ISODE evelopment package. The development package is lso used or encoding and decoding ASN.1 ata as ell as or other data manipulation ervices. Using he ISODE package the implementation can be run over both TCP/IP and OSI protocols. The DSA provides full support for both DAP and DSP protocols, conformant with ISO 9594 / CCITT X.500 standards. The DIB is maintained using a locally developed elational database system. The interface to he database system consists of set of sql-like C functions. These are designed to allow straightforward replacement of the local atabase system ith a more powerful commercial ystem. To achieve better performance several options are supported that permit loading of selected portions of the database in core. hen these options are selected data can be retrieved more quickly from in core ables; ll modifications to the DIB are directly reflected in the in core tables and the database.
COMPLIANCE (applicable only for SAs and DUAs)
-
Custos is fully compliant with the 1988 Standard with the following omissions:
- Search request decomposition
- Modify Entry operation
- Modify RDN peration
- Abandon operation
- Strong Authentication
- Schema checkingThere are no resent lans to extend ustos to include the 1992 X.500 extensions.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
[No information provided--Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
[No information provided--Ed.]
INTEROPERABILITY
-
Have uccessfully interoperated with UIPU and OSIWARE over the DAP. No DSP interoperability testing has been done.
PILOT CONNECTIVITY
-
Limited DUA and DSA connectivity to PSI White Pages Project.
BUGS
-
Bugs ay be reported o the general discussion list, x500@osi.ncsl.nist.gov.
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 performance with a large database. Any platform the implementation can be ported to (generally any platform ISODE can be ported o) should support all features.
INTERNETWORKING NVIRONMENT
-
RFC-1006; TP4/CLNP (SunLinkOSI) over 02 and .25 (SunLink X.25).
HARDWARE PLATFORMS
-
It's nly been run on Sun 3 and SPARC, but there are o known reasons why it shouldn't run n any hardware unning he ISODE software.
SOFTWARE PLATFORMS
-
It requires UNIX and he ISODE software package. It's been developed and tested with ISODE version 7.0 and Sun OS ersion .1.1. Uses a locally developed relational BMS that should be easily replaceable with ommercially available relational systems.
AVAILABILITY
-
Custos, the NIST implementation of X.500, the OSI Directory, s available for anonymous ftp from osi.ncsl.nist.gov (129.6.48.100) using the convention user name = anonymous, assword = ident). The software is available in two orms: a tar file and a ompressed tar file. ./pub/directory/CustosRel_0.2.tar ./pub/directory/CustosRel_0.2.tar.Z Note: permissions on he directory ./pub/directory are set so that you will be able to "get" files whose names you can provide. owever, you will not e able o "ls" he contents of he directory.
DATE LAST UPDATED or CHECKED
-
March 5th, 1993
NAME
-
DE
KEYWORDS
-
Available via FTP, DUA Interface, Free, Included in ISODE, LDAP, Multiple Vendor Platforms, Needs ISODE, RFC-1274, RFC-1484, RFC-1487, Source, UNIX
ABSTRACT
-
DE (Directory Enquiries) is intended o be a imple-to-use DUA interface, suitable for the naive user, and suitable or running as a public access dua. it will work on any terminal. The user is presented with a series of (verbose) rompts sking for person's name; department; organization; country. There is extensive n-line help. The matching algorithms are such that ear matches are presented to he user before ess good matches. A lot of development as been done on the interface since it as first described in RFC1292. he most significant enhancement has been o add power searching - this allows a user to search for an entry even when they o not know the ame of he organisation in which the person works - you till have to specify the country. DE now provides FN style searching. It is now ossible to search locality entries. DE now uses slightly different search algorithms depending on hether t is accessing art of he Directory mastered by a uipu DSA - Quipu DSAs tend to use lots f replication and so encourage searching. An experimental feature is intended to ive the user ore feedback on the likely response time to a query - DE maintains a database f past nformation availability and DSA responsiveness. Translations exist into at least 4 different languages.
DE runs over SODE DAP and University of Michigan LDAP. There is a version of DE, called DOS-DE, which has been orted to DOS, and this uses DAP.
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.
COMPLIANCE (applicable only for SAs and DUAs)
-
N/A
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
[RFC 484].
INTEROPERABILITY
-
N/A
PILOT CONNECTIVITY
-
N/A (This is ore a DUA rather than an interface question). The interface is idely used in the global pilot.
BUGS
-
Doesn't handle aliases well when power searching.
Send ug reports to:
.barker@cs.ucl.ac.uk elpdesk@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 does not handle searching under localities very ell.
It is not possible to display photographs or eproduce sound attributes.
INTERNETWORKING NVIRONMENT
-
As for ISODE.
HARDWARE PLATFORMS
-
As for ISODE.
SOFTWARE PLATFORMS
-
As for ISODE.
AVAILABILITY
-
The software s openly available as part of ISODE-8.0. An enhanced version is available s part f the PARADISE roject pgrade. Both hese versions are available by TP from <ftp.paradise.ulcc.ac.uk>, as src/isode-8.tar.Z and src/isode- paradise.tar.Z. The very latest code ill be ade available with the SODE Consortium release of ISODE. It is hoped it will be freely available to all.
Contact:
elpdesk@paradise.ulcc.ac.uk .barker@cs.ucl.ac.uk
DATE LAST UPDATED or CHECKED
-
March 12th, 1993
NAME
-
DEC X.500 Directory Server
Digital Equipment Corporation
KEYWORDS
-
API, LNS, Commercially Available, DEC ULTRIX, DEC VAX OpenVMS, DSA Only, OSI Transport, FC-1006, RFC-1274, RFC-1277, RFC-1278, .25
ABSTRACT
-
The DEC X.500 Directory Server product provides a high performance Directory System Agent implemented according o the 1993 edition of ISO/IEC 9594 nd the CITT X.500 series of Recommendations.
Specific features provided include:
(1) Integrated multi-protocol support allowing concurrent DAP and DSP access over OSI and TCP/IP (using RFC1006) protocols. (2) Indexed database upports high-performance searching and sophisticated matching including pproximate match. (3) Based on he 1993 edition Extended Information Models. (4) Support for chaining and eferrals in support of distributed Directory Information Base. (5) Support for the 1993 edition Simplified Access Control scheme. (6) Configurable schema based on the 993 edition (including attributes, object classes, structure rules, name forms). (7) Support for a simple Shadowing protocol to enhance read availability. (8) Remote management facilities to configure and control DSAs and log significant events. (9) Provides he X/OPEN XDS/XOM Application Program Interface so that customers can construct their own DUA applications.For Directory User Agent facilities see the associated entry or the DEC X.500 Administration Facility
COMPLIANCE (applicable only for SAs and DUAs)
-
Conformance with respect to clause 9.2 of ISO/IEC 9594-5:1993:
(1) upports the directoryAccessAC (DAP) and directorySystemAC (DSP) pplication contexts. (2) he DSA s capable of acting as first-level DSA. (3) haining is supported. (4) ind security levels of imple (unprotected password) and none re supported. (5) ll attribute types defined in ISO/IEC 9594-6:1993 are supported xcept for 1993 dition upertypes and collective attributes and nhancedSearchGuide. Customers an define new attribute types. NIVERSAL STRING is not upported for attributed based on irectoryString. (6) ll object classes defined in ISO/IEC 9594-7:1993 are supported. ustomers can define new object lasses. (7) he following operational attributes are supported: governingStructureRule createTimestamp modifyTimestamp myAccessPoint superiorKnowledge supplierKnowledge consumerKnowledge specificKnowledge dseType PrescriptiveACI (8) ynamic odification of bject class is ermitted (9) subset of Simplified Access Control is supported. (10) ll name forms defined in ISO/IEC 9594-7:1993 are supported. ustomers can defined new name forms and structure rules. The X.500 Directory Server is compatible with and interworks ith 1988 dition UAs and DSAs. t is implemented to conform to elevant NIST IW and WOS agreements nd the .500 Implementors Guide.For details contact Digital.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
INTEROPERABILITY
-
All interoperability est results will be available on request from Digital. Interoperability testing is eing undertaken using the harmonized OSIone X.500 test uite to which both OSInet and EurOSInet have een key contributors.
PILOT CONNECTIVITY
-
Digital is actively involved n both ublic and private pilots of X.500.
BUGS
-
[No information provided--Ed.]
CAVEATS nd GENERAL LIMITATIONS
-
[No information provided--Ed.]
INTERNETWORKING NVIRONMENT
-
The DEC X.500 Directory Service V1.0 perates over:
* RFC 1006 over TCP/IP on ULTRIX platforms. * OSI TP0, TP2 and TP4 over CLNS and ONS as ppropriate on ULTRIX and OpenVMS platforms
HARDWARE PLATFORMS
-
The DEC X.500 Directory Service V1.0 uns on:
* VAX processors supported by OpenVMS
* RISC processors supported by ULTRIX
SOFTWARE PLATFORMS
-
The DEC X.500 Directory Service V1.0 uns on:
* OpenVMS/VAX V5.5-2 r later running DECnet-VAX Extensions V5.4 * ULTRIX/RISC V4.2 or later running DECnet/OSI for ULTRIX, V5.1 or
-
later.
For availability on other hardware and software platforms please contact Digital.
-
AVAILABILITY
-
The DEC X.500 Directory Service is commercially available from Digital Equipment Corporation. For further information please contact your ocal Digital office, or:
-
ail Shlansky, Product Manager:
Tel: 1 508 486 5138 email: gail.shlansky@lkg.mts.dec.com igital quipment Corporation etworks and Communications Engineering 50 King Street ittleton, MA. 01460-1289 SA -
DATE LAST UPDATED
-
August 2nd, 1993
NAME
-
DEC X.500 Administration Facility
Digital Equipment Corporation
KEYWORDS
-
API, LNS, Commercially Available, DEC ULTRIX, DEC VAX OpenVMS, DUA Only, Motif, SI Transport, RFC-1006, RFC-1274, RFC-1277, RFC-1278, X.25
ABSTRACT
-
The DEC X.500 Administration acility product provides both command line nd Motif interfaces to anage the information stored in the X.500 directory.
Specific features provided include:
(1) Multi-protocol support allowing DAP access over OSI and TCP/IP (using RFC1006) protocols. (2) Driven off the same configurable chema information as the DEC X.500 Directory Service. (3) Supports ommand ine and OSF Motif interface styles. (4) Provides ccess to all X.500 services. Specific features of he OSF otif interface nclude: (1) Supports wo ways of accessing directory nformation, either by browsing he directory tree or by searching. (2) Easy-to-use search based n customer-extensible set of predefined filters. (3) Window layouts and text fully extensible, based on the schema, to support customer-defined bject classes and attributes. (4) Easy-to-use forms based method for creating and modifying entries that simplifies use of the X.500 ervices. See also the ntry for the DEC X.500 irectory Service.
COMPLIANCE (applicable only for SAs and DUAs)
-
Conformance with respect to clause 9.1 of ISO/IEC 9594-5:1993:
(1) Supports he all perations of the directoryAccessAC application context.(2) Bind security levels of none and imple (unprotected passwords).
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
INTEROPERABILITY
-
Interoperability test results will be available on request from Digital. Interoperability testing is eing undertaken using the harmonized OSIone X.500 test uite to which both OSInet and EurOSInet have een key contributors.
PILOT CONNECTIVITY
-
Digital is actively involved n both ublic and private pilots of X.500.
BUGS
-
[No information provided--Ed.]
CAVEATS nd GENERAL LIMITATIONS
-
[No information provided--Ed.]
INTERNETWORKING NVIRONMENT
-
The DEC X.500 Administration acility operates over:
* RFC 1006 over TCP/IP on ULTRIX platforms. * OSI TP0, TP2 and TP4 over CLNS and ONS as ppropriate on ULTRIX and penVMS latforms
HARDWARE PLATFORMS
-
The DEC X.500 Administration acility V1.0 runs on:
* VAX processors supported by OpenVMS
* RISC processors supported by ULTRIX
SOFTWARE PLATFORMS
-
The DEC X.500 Administration acility V1.0 runs on:
* OpenVMS/VAX V5.5-2 r later running DECnet-VAX Extensions V5.4 * ULTRIX/RISC V4.2 or later running DECnet/OSI for ULTRIX, V5.1 or
-
later.
For availability on other hardware and software platforms please contact Digital.
-
AVAILABILITY
-
The DEC X.500 Administration acility is commercially available from Digital Equipment Corporation. For further information please contact your ocal Digital office, or:
-
ail Shlansky, Product Manager:
Tel: 1 508 486 5138 email: gail.shlansky@lkg.mts.dec.com igital quipment Corporation etworks and Communications Engineering 50 King Street ittleton, MA. 01460-1289 SA -
DATE LAST UPDATED
-
August 2nd, 1993
NAME
-
DIR.X (tm) V3.0
Siemens Nixdorf Informationssysteme AG
KEYWORDS
-
API, LNS, Commercially Available, DSA Connectivity, SA/DUA, DUA Connectivity, HP, IBM RISC, OSI Transport, RFC-1006, FC-1277, SNI, X.25
ABSTRACT
-
DIR.X is the iemens ixdorf .500 product on which the OSF DCE/GDS (Distributed omputing Environment/Global Directory Service) s based. It supports full DUA nd DSA unctionality for globally unique identification and location of objects in a network. It also provides functions to answer ueries both yellow-page and white- page) about objects and attribute information. The software implements full DAP and DSP protocols specified in X.519. The required ACSE, ROSE, resentation, Session and RFC-1006 protocol implementations are also included. It also supports RFC-1277.
Additional features include proprietary Replication and Access Control, Caching, Tree-handling utilities and (Remote) Administration.
COMPLIANCE (applicable only for SAs and DUAs)
-
Consists of both DUA nd DSA mplementations ccording to the CCITT X.500 (1988) nd ISO 594 standard. The X/Open standard APIs or XDS and XOM are provided. The XDS interface can also be used to access the OSF DCE/CDS (DCE ocal Cell Directory Service) transparently. DIR.X has been successfully conformance tested. PICS nd PCTRs are available for all tested protocols: DSA/DAP, UA/DAP, Presentation, ACSE nd Session embedded in .500.
Compliant with EWOS Agreements (which are being harmonized with OIW Agreements).
Strong authentication according to X.509 and n XDS/XOM convenience library will e included in the next ersion Q2 1994). Support for X.500 (1993) s planned for Q4 1994.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
[No information provided--Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
[No information provided--Ed.]
INTEROPERABILITY
-
This mplementation of DAP and DSP has successfully interoperated with he X.500 implementations from ICL, UNISYS, E3X nd ISODE.
PILOT CONNECTIVITY
-
Several DIR.X DSAs are connected to the European X.500 pilot etwork PARADISE. (DUA and DSA connectivity.)
BUGS
-
Problems and ug-report e-mail address: dirx-info@mch.sni.de
CAVEATS ND GENERAL LIMITATIONS
-
The software s highly portable and without any general limitations.
INTERNETWORKING NVIRONMENT
-
OSI TP4 with LNP OSI TP0, 2 4 with X.25 RFC-1006 with TCP/IP
DIR.X can use either SD sockets or XTI/TLI to access the Transport Service.
HARDWARE PLATFORMS
-
SNI's hardware platforms, IBM's RS/6000 and Hewlett Packard's HP9000 among others.
SOFTWARE PLATFORMS
-
SINIX (UNIX System V elease ), OSF/1.1, AIX 3.1, HP-UX. A port to Windows-NT is planned for Q2 994.
AVAILABILITY
-
DIR.X can be elivered as a binary product or as source to OEM customers. The DIR.X product is commercially available from:
Siemens Nixdorf Informationssysteme SNI BU BA NM 2 D-81739 Munich GermanyPlease contact:
Gianni Rabaioli Tel: 49 89 636 41095 Fax: 49 89 636 45860 e-mail: Giovanni.Rabaioli@mch.sni.de
DATE LAST UPDATED or CHECKED
-
November 26th, 1993
NAME
-
Directory 500 (tm)
OSIware / Infonet Software Solutions
KEYWORDS
-
Commercially vailable, DS/DUA, RFC-1006, Source, Sun, X.25
ABSTRACT
-
Directory 500 (D500) s a comprehensive implementation of the CCITT X.500 recommendations. D500 is comprised of two major components which are responsible for manipulating the data in the OSI Directory. They re the irectory User Agent (DUA) and the Directory System Agent (DSA). The DUA is the interface between the SI Directory and those sers wishing access to the Directory's information. Users ake their requests through the UA. When forwarding user's requests to he OSI Directory, the protocol used s known as the irectory Access Protocol (DAP). The DSA will egotiate with other, remote DSAs to obtain requested information or to update remote DIBs. DSAs use the Directory ystem Protocol (DSP) to forward and answer hese requests. he DSA upports chaining and eferrals.
COMPLIANCE (applicable only for SAs and DUAs)
-
All X.500 1988 operations are supported along with all Object Classes specified in .521 and all Attribute ypes specified n X.520. Implementation plans nclude pgrades to support the 992 extensions to X.500 in 1994. Please check with OSIware / Infonet Software Solutions for availability dates.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
[No information provided--Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
[No information provided--Ed.]
INTEROPERABILITY
-
Tested with QUIPU. Other interoperability information not available at this time.
PILOT CONNECTIVITY
-
[No information provided--Ed.]
BUGS
-
None nown at this time.
CAVEATS nd GENERAL LIMITATIONS
-
None nown at this time.
INTERNETWORKING NVIRONMENT
-
RFC1006 with CP/IP
HARDWARE PLATFORMS
-
Any Sun SPARC with 16 MB memory, 40 MB free disk Please enquire if interested in other platforms such as: SCO Unix, AIX
SOFTWARE PLATFORMS
-
Sun OS 4.1.x. Runs over TCP/IP, or X.25 (SunNet X.25 ersion required)
AVAILABILITY
-
Directory 500 is commercially as executable object code or as source code orm from:
OSIware / Infonet Software Solutions 4400 Dominion Street, Suite 210 Burnaby, BC V5G 4G3 CANADA Sales & Information: 604436-2922 Fax: 604/436-3192
DATE LAST UPDATED or CHECKED
-
November 21st, 1993
NAME
-
DOS-DE
University of Bath
KEYWORDS
-
Available via FTP, DUA Interface, Free, IBM PC, LDAP, Multiple Vendor Platforms, RFC-1274, FC-1484, RFC-1487
ABSTRACT
-
DOS-DE (DOS Directory Enquiries) is intended o be a imple-to-use DUA interface suitable for the naive ser. It is an S-DOS port of the standard NIX DE mplementation - see the entry on DE for full details. (All of the features DE are supported apart from the experimental Quality of Service' code). The user is presented with a eries of (verbose) prompts asking for person's name; department; organization; country. There is extensive on-line help. The matching algorithms are such that ear matches are presented to he user before ess good matches. `Power searching' is also vailable - this allows user to search for an ntry even when they o not know the ame of he organisation in which the person works - you still have to specify the country. DOS-DE provides UFN style searching. It s also ossible to search locality entries. DOS-DE uses slightly ifferent search algorithms depending on whether it is accessing part f the Directory mastered by a Quipu DSA - Quipu DSAs end to se lots of replication nd so encourage searching.
DOS-DE runs over the niversity of Michigan LDAP.
DE was funded by the OSINE PARADISE roject. DOS-DE was developed by Andy Powell at the University of Bath.
COMPLIANCE (applicable only for SAs and DUAs)
-
N/A
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
[RFC 484].
INTEROPERABILITY
-
N/A
PILOT CONNECTIVITY
-
N/A
BUGS
-
Doesn't handle aliases well when power searching.
Send ug reports to:
A.Powell@bath.ac.uk
CAVEATS nd GENERAL LIMITATIONS
-
DOS-DE tries o cater well for the general case, at the expense of not dealing with the ess typical. The main anifestation of this is that he current version does not handle searching under localities very ell.
It is not possible to display photographs or eproduce sound attributes.
INTERNETWORKING NVIRONMENT
-
University of Michigan LDAP.
HARDWARE PLATFORMS
-
IBM PC/AT/XT nd compatibles.
SOFTWARE PLATFORMS
-
LDAP or MS-DOS running over he NCSA Telnet tack or SUN's PCNFS version 4.1 or Novell's LAN Workplace (LWP).
AVAILABILITY
-
The software s openly available by FTP from tp.bath.ac.uk, s pub/x500/dosde.zip. The very latest code ill be ade available with the SODE Consortium release of ISODE. It is hoped it will be freely available to all.
Contact:
A.Powell@bath.ac.uk
DATE LAST UPDATED or CHECKED
-
March 18th, 1993
NAME
-
HP X.500 Distributed irectory Products
Hewlett Packard
KEYWORDS
-
API, LNS, Commercially Available, DSA/DUA, DUA only, HP, OSI Transport, X.25
ABSTRACT
-
HP X.500 Distributed irectory. Its main components are:
-
DUA, and UA Interface,
DSA and DIB support,
X.500 Address Lookup,
X/Open Application Tool Kit API (XAT) for XDS/XOM Interface, X.500 High Level PI (X5HLAPI) for XDS/XOM Interface.
HP X.500 DUA. Its main components are:
-
DUA, and UA Interface,
X.500 Address Look-up,
X/Open Application Tool Kit API (XAT) for XDS/XOM Interface, X.500 High Level PI (X5HLAPI) for XDS/XOM Interface.
HP X.500 Distributed irectory is based on the 1988 CCITT X.500 standard. HP X.500 can be used for accessing names and electronic mail ddresses for multi-vendor messaging backbone networks. P X.500 can also be used for he development f networked applications requiring distributed directory functionality.
HP OpenMail users can access he enterprise wide HP X.500 distributed directory directly from the HP OpenMail user nterface, and select X.500 addresses for mailing. P-UX Sendmail users can access electronic mail addresses from a X.500 server over a CP/IP network.
Users of non-HP e-mail systems can access data stored in the .500 Directory using X.500 Address Look-up. X.500 ddress ook-up as an easy o use interface, and phonetic search capability. HP X.500 Distributed irectory includes a complete multi-threaded DUA and DSA. The .500 DIB is built on a atabase which has been optimized for X.500 performance. HP X.500 contains full support for DAP and DSP protocols.
Data hadowing and security access control of HP X.500 Distributed Directory allow higher performance, and easier management of ts DIB database in a global nvironment.
HP X.500 Distributed irectory has menu driven administration and user nterface tools. The tools simplify directory configuration and data etrieval. It supports X/Open X.500 APIs (XDS and XOM), nd high level APIs on top of DS to allow developers o write their own X.500 based applications. HP X.500 Distributed irectory supports comprehensive tracing and logging facilities for quick iagnosis and resolution of problems. HP also rovides a rich et of troubleshooting tools to heck the interoperability of the network at various layers of he OSI tack.
-
COMPLIANCE (applicable only for SAs and DUAs)
-
HP X.500 Distributed irectory complies with he following standards: CCITT X.501: The Directory - Models CCITT X.509: The Directory - Authentications Framework* CCITT X.511: The Directory - Abstract Service Definition CCITT X.518: The Directory - Procedures for Distributed Operations CCITT X.519: The Directory - Protocol Specifications CCITT X.520: The Directory - Selected Attribute Types CCITT X.521: The Directory - Selected Object Classes CCITT X.219: Remote Operations - Model, Notation and Service Definition CCITT X.229: Remote Operations - Protocol pecifications *x.509 describes simple and strong uthentication. P X.500 Distributed Directory supports simple authentication. Strong authentication is ot supported in the current release due to limited market demand. HP X.500 Distributed irectory will comply with NIST nd EWOS directory functional rofiles. Based n factors such s market needs and NIST recommendations, HP ill implement subsets of 1992 CCITT functionality in a phased approach.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
[No information provided--Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
[No information provided--Ed.]
INTEROPERABILITY
-
HP has done some unofficial interoperability esting. HP would welcome suggestions on priorities for vendor nteroperability testing.
PILOT CONNECTIVITY
-
[No information provided--Ed.]
BUGS
-
[No information provided--Ed.]
LIMITATIONS
-
HP X.500 Distributed irectory supports up to 30 DSA onnections at one time. This limit ould be increased in the future if needed.
INTERNETWORKING NVIRONMENT
-
HP X.500 Distributed irectory resides on an SI stack, and can be used n 802.3 LAN, or X.25 CLNS or CONS environment. P is investigating implementing X.500 for he TCP/IP environment.
HARDWARE PLATFORMS
-
HP X.500 Distributed irectory is available on HP 9000 Series 800 family of high performance servers which are calable platform.
The HP X.500 ddress ook-up acility is also available for the HP 9000 eries 300 and Series 700 for customers ho have purchased the X.500 product.
SOFTWARE PLATFORMS
-
HP X.500 Distributed irectory requires the following software environment:
- HP-UX Operating System 8.0 r later
- OSI Transport Services/9000 for the Series 00
- HP an Link or HP X.25 product
- Network Tracing and Logging
- ANSI C compiler (for the HP/XDS API)
AVAILABILITY
-
HP X.500 Distributed irectory is commercial vailable. The product can be ordered through HP Sales offices. The rdering numbers are:
-
P/N J2152A
HP X.500 istributed Directory/9000 for the Series 800. Product contains SA server and DUA client.
P/N J2153A HP X.500 UA/9000 for the Series 00. Product contains nly DUA client. -
DATE LAST UPDATED or CHECKED
-
August 16th, 993.
NAME
-
University of Michigan LDAP Implementation
KEYWORDS
-
API, vailable via FTP, DEC ULTRIX, DUA Connectivity, DUA Interface, Free, HP, IBM PC, IBM RISC, LDAP, Macintosh, ultiple Vendor Platforms, RFC-1006, FC-1274, RFC-1484, RFC-1485, RFC-1487, ource, Sun
ABSTRACT
-
LDAP s the Lightweight Directory Access Protocol. It gives .500 access to platforms that have only TCP/IP access, using simplified BER encoding f many .500 data elements. LDAP is currently proposed Internet Standard. he LDAP server s an intermediate protocol server that ommunicates with Internet clients on one side using the simple TCP-based LDAP protocol and n X.500 DSA on he other side using the irectory Access Protocol (DAP). A subset of the X.500 DAP is exported to he clients through the DAP protocol.
The U-M LDAP istribution contains the following components:
- LDAP server - LDAP client library, including both synchronous and asynchronous APIs - Lightweight BER library, including n API that supports a printf/scanf-like interface - Various LDAP client programs, including a finger daemon (xfingerd), gopher to X.500 gateway (go500gw), ommand-line DUA (ud), e-mail query server (rcpt500), and an X.500 mailer (mail500)
COMPLIANCE (applicable only for SAs and DUAs)
-
The U-M LDAP istribution is complete implementation of the LDAP protocol. The LDAP protocol oes not support access o all X.500 features and perations. The operations supported are bind, earch, compare, add, delete, modify, modify DN, and abandon. Note hat read nd list operations can e emulated using the search operation. Size nd time limits ay be specified, as may alias dereferencing and searching, but all X.500 service controls are not supported.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
Preliminary support is included for [RFC 1484].
INTEROPERABILITY
-
The current implementation of the LDAP server is known to work with the QUIPU DSA and DAP library.
PILOT CONNECTIVITY
-
DUA connectivity should be possible to all pilots, though only AARNET, PARADISE, and PSI White Pages Project have actually been tried.
BUGS
-
Bug reports should be sent to bug-ldap@umich.edu.
CAVEATS nd GENERAL LIMITATIONS
-
None, aside from those mentioned above under ompleteness.
INTERNETWORKING NVIRONMENT
-
LDAP lients se TCP o communicate with the DAP server. The LDAP server normally uses FC 1006 with TCP/IP to ommunicate with the DSA, hough any other transport mechanism for DSA communication supported by SODE should be ossible.
HARDWARE PLATFORMS
-
The LDAP server is known to run on Sun 3 and un 4 platforms EC's, HP's, and RS 000's. The LDAP client libraries and some clients have been orted to the Macintosh nd the C.
SOFTWARE PLATFORMS
-
The LDAP server and clients are known to run nder and SunOS .1.x, ULTRIX, HP-UX, and AIX. The DAP client libraries also work nder Macintosh System 6.0 r higher and MS-DOS 5.0.
AVAILABILITY
-
This oftware is openly available. It may be obtained by anonymous FTP from terminator.rs.itd.umich.edu n the x500 directory. Documentation on the DAP and lightweight BER libraries is provided in the form of man pages distributed ith the source ode. More information can be obtained from ldap-support@umich.edu. This oftware was developed at the University of Michigan by im Howes with help from ark Smith and Bryan Beecher, as well as many others around the Internet. t is subject to the following copyright. Copyright © 1993 Regents of the University f Michigan. All rights reserved. Redistribution and use in ource and binary forms re permitted provided that this otice is preserved and hat due credit is given to the University of Michigan at Ann Arbor. he 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'' without express or implied warranty.
DATE LAST UPDATED OR CHECKED
-
March 13th, 1993
NAME
-
ldap-whois++
KEYWORDS
-
Available via FTP, DEC ULTRIX, DUA Interface, Free, LDAP, RFC-1487, Sun, NIX
ABSTRACT
-
ldap-whois++ s a dua interface that mplements the IETF WNILS draft whois++ proposal using the LDAP libraries developed by the University of Michigan.
COMPLIANCE (applicable only for SAs and DUAs)
-
N/A
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
IETF NILS WG Whois++ Architecture Draft.
INTEROPERABILITY
-
N/A
PILOT CONNECTIVITY
-
There are a number of servers running across he Internet.
BUGS
-
None eported.
CAVEATS nd GENERAL LIMITATIONS
-
Based on an early draft of the Whois++ Architecture Document o there may be some inconsistencies with the atest draft.
It is considered a "beta" release due to the olatility of the whois++ work. Once there is whois++ RFC then a real release will be made.
INTERNETWORKING NVIRONMENT
-
N/A
HARDWARE PLATFORMS
-
DEC RISC, SUN RISC
SOFTWARE PLATFORMS
-
ULTRIX 4.3, SunOS 4.1.x
AVAILABILITY
-
Available via anonymous ftp from ftp.adelaide.edu.au s pub/whois/whois++beta.tar.Z.
DATE LAST UPDATED or CHECKED
-
August 3rd, 1993
NAME
-
University of Michigan maX.500 Macintosh DUA nterface
KEYWORDS
-
Available via FTP, DUA Connectivity, UA Interface, Free, LDAP, Macintosh, RFC-1274,RFC-1484, RFC-1485, RFC-1487
ABSTRACT
-
maX.500 is a irectory User Agent for Apple Macintosh. It is currently at ersion .0, which uses he Lightweight irectory Access Protocol (LDAP) over CP/IP to access The Directory. maX.500 can be used o search for, view, create, delete, and modify ntries. It supports viewing of textual information, playing of audio, and viewing of black and hite (fax) and olor (JPEG) images. maX.500 is a ative Macintosh application, and as such has a riendly interface. It requires System Software version 6.0.5 or later and Apple's MacTCP control panel.
COMPLIANCE (applicable only for SAs and DUAs)
-
maX.500 works over LDAP, and s subject to LDAP's limitations. The X.500 bind, search, compare, dd, delete, abandon, and modify operations are used by maX.500. Size and time limits may be specified, as may alias dereferencing and searching.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
Preliminary support is included for [RFC 1484] (same s U-M LDAP).
INTEROPERABILITY
-
maX.500 2.0 is known o work ith the U-M LDAP server. It has been used uccessfully with the QUIPU DSA nd others.
PILOT CONNECTIVITY
-
DUA connectivity should be possible to all pilots, though only AARNET, PARADISE, and PSI White Pages Project have actually been tried.
BUGS
-
Bug reports should be sent to max500-bugs@umich.edu.
CAVEATS nd GENERAL LIMITATIONS
-
maX.500 does ot support modification of "photo" (fax), "jpegPhoto", or "audio" attributes. Modify RDN is also unsupported.
INTERNETWORKING NVIRONMENT
-
maX.500 is an LDAP client, and as such is uses TCP to communicate with he LDAP server. Apple's MacTCP control panel s required on the Macintosh.
HARDWARE PLATFORMS
-
maX.500 runs n Apple Macintosh Plus r later computers. It equires 1MB of RAM.
SOFTWARE PLATFORMS
-
maX.500 requires Apple System Software 6.0.5 r later (System 7 preferred) and MacTCP 1.1 or ater (1.1.1 preferred).
AVAILABILITY
-
This oftware is openly available. It may be obtained by anonymous FTP from terminator.rs.itd.umich.edu n the x500 directory. ore information can be obtained from ldap-support@umich.edu. This oftware was developed at the University of Michigan by ark Smith with help from im Howes and many others around the Internet. It is subject to the ollowing copyright: Copyright © 1993 egents f the University of Michigan. ll rights reserved. Redistribution and use in binary orms is permitted provided hat this notice is preserved and that due credit is given to he University of Michigan at Ann Arbor. The name of the University may ot be used to endorse or promote products derived from this oftware without specific prior ritten permission. This software is provided ``as s'' without express or implied warranty.
DATE LAST UPDATED OR CHECKED
-
July 6th, 1993
NAME
-
MXLU
Brunel University, UK
KEYWORDS
-
DUA Connectivity, DUA Only, Free, Motif, Multiple Vendor Platforms, Needs ISODE, ource, NIX, X indow System
ABSTRACT
-
MXLU Motif/X LookUp) is an X.500 DUA interface for the X Window System using otif.
Ported from the Athena widgets version, MXLU an be configured for many ifferent styles of interaction. Example configurations re provided for ingle window and multiple window use.
MXLU mplements the `User-Friendly Naming' search strategy and also has a form-filling search mode. Asynchronous irectory operations are used.
Full ser friendly add and modify functions are provided, with the ability to tailor the modify creen to present simple subsets of the available attributes.
Can also be configured as a bibliographic search tool for use with the ABDUX Project bibliographic DSAs.
COMPLIANCE (applicable only for SAs and DUAs)
-
88 Standard compliant: Strong authentication ot yet mplemented. No plans for support of he 1992 Standard.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
No plans at present.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
No plans at present.
INTEROPERABILITY
-
Tested with ISODE-8.0
PILOT CONNECTIVITY
-
DUA Connectivity: The interface is in use in he UK Academic Directory Pilot.
BUGS
-
Bugs hould be reported to x500@brunel.ac.uk.
CAVEATS nd GENERAL LIMITATIONS
-
Does ot support modification of all nown attribute yntaxes. In particular, ACLs and /R addresses are not catered for.
INTERNETWORKING NVIRONMENT
-
As ISODE.
HARDWARE PLATFORMS
-
Most NIX machines.
SOFTWARE PLATFORMS
-
UNIX
Motif 1.1 >
ISODE/QUIPU (version .0 >)
AVAILABILITY
-
Sources are freely available or commercial or non-commercial use. Binaries for unOs 4.1.3 are lso available from Brunel, to simplify installation n sites that do not already use ISODE. TP site: src.brunel.ac.uk irectory: /x500 ource code files: mxlu-1.1.tar.Z query-1.1.tar.Z inary file: mxlubin-1.1.tar.ZContacts.
Postal Address:
-
ndrew Findlay
omputing and Media Systems
runel University
leveland Road
xbridge, Middlesex
B8 3PH
K
E-mail:
-
-
x500@brunel.ac.uk.
-
Fax: 44 895 2806 (Andrew Findlay) Telephone: +44 895 203066 (Andrew Findlay)
DATE LAST UPDATED or CHECKED
-
March 10th, 1994
NAME
-
PathWay Messaging
KEYWORDS
-
386, LNS, Commercially Available, DSA Connectivity, SA/DUA, DUA Connectivity, DUA Interface, BM PC, DAP, Macintosh, Multiple Vendor Platforms, OSI Transport, RFC-1006, RFC-1202, RFC-1277, RFC-1278, Sun, .25
ABSTRACT
-
PathWay Messaging Services is a full .400 MTA and X.400-Internet gateway that ncludes an integrated X.500 DSA/DUA. It supports full DUA and DSA functions as well as full DAP and DSP protocols specified in X.519. The DSA may be used exclusively for enterprise-wide messaging, or as a general purpose X.500 DSA. The product has successfully articipated in SInet X.500 I-Lab interoperability tests. PathWay Messenger is n email application for desktop class machines with limited functionality UA Light Weight Client hat provides access (per RFC 1202, Directory Assistance Service - upport or LDAP is planned) over TCP/IP to the X.500 SA/DUA ncluded with PathWay Messaging Services.
COMPLIANCE (applicable only for SAs and DUAs)
-
PathWay Messaging Services is a complete implementation of the 1988 X.500 Recommendations with the exception of strong authentication as outlined in X.509. It is conformant o NIST, EWOS, and UK GOSIP Directory profiles. It provides network through application layer protocol support, with support for all attribute types, syntaxes, and object classes defined in X.520 and X.521. Support for 1992 extensions to X.500 is planned for future release as s support for X/Open Object Management (OM) and X/Open Directory Services (XDS) standards.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
PathWay Messaging Services' X.500 supports the following Internet Proposals: [RFC 1277].
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
PathWay Messaging Services' X.500 supports the following Internet Proposals: [RFC 1202] and [RFC 1278].
INTEROPERABILITY
-
PathWay Messaging Services has undergone successful interoperability testing with ontrol ata, DEC, HP, and the ISODE Consortium sing EurOSInet test suites.
PILOT CONNECTIVITY
-
Tested DUA and DSA connectivity with ARADISE and PSI White Pages Project.
BUGS
-
Send ug reports to:
prod-eng@twg.com
CAVEATS nd GENERAL LIMITATIONS
-
[No information provided--Ed.]
INTERNETWORKING NVIRONMENT
-
RFC1006 with CP/IP, P4 with CNLS, TP0/2 or P4 with X.25.
HARDWARE PLATFORMS
-
PathWay Messaging Services runs on all models of Sun PARC and generic 386/486 systems. PathWay Messenger (email with lightweight DUA) lso runs on Macintosh, nd on IBM PC/AT and compatibles.
SOFTWARE PLATFORMS
-
PathWay Messaging Services supports SunOS 4.1.2, Solaris 1.0.1, and SunSoft INTERACTIVE UNIX. PathWay Messenger also supports SCO, MacOS and MS-Windows.
AVAILABILITY
-
PathWay Messaging is ommercially available from:
-
he Wollongong Group, Inc.
129 San Antonio Road
alo Alto, CA 94303 USA
ales and Information: (415) 962 7100 AX: (415) 969-5547 -
DATE LAST UPDATED or CHECKED
-
July 7th, 1993
NAME
-
PC-DUA
NEXOR
KEYWORDS
-
386, ommercially Available, UA Connectivity, DUA Interface, IBM PC, LDAP, RFC-1487
ABSTRACT
-
PC-DUA provides a MS indows ased user interface to he X.500 Directory.
Features include:
- Searching - Directory Browser - to enable user o identify directory entry - History - allowing uick access to reviously referenced parts of he DIT. - User Friendly Name UFN) based searching - Hypertext-like navigation. - Friendly names for ttribute labels. - Intelligent choice f entries to display when moving to a new location in the DIT. - O-line hypertext help.
COMPLIANCE (applicable only for SAs and DUAs)
-
Compliant with LDAP.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
The following are supported: FC 1487
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
[No information provided--Ed.]
INTEROPERABILITY
-
PC-DUA has interoperated with LDAP 2.0 and 3.0 beta distributions.
PILOT CONNECTIVITY
-
Full UA connectivity to the ARADISE and PSI White Pages X.500 Pilots.
BUGS
-
No known bugs. Support is given via hone or email to "support@nexor.co.uk"
CAVEATS nd GENERAL LIMITATIONS
-
None.
INTERNETWORKING NVIRONMENT
-
WinSock based TCP/IP tacks
HARDWARE PLATFORMS
-
- PC WITH 4MGBYTES AM
SOFTWARE PLATFORMS
-
MS WINDOWS 3.1
AVAILABILITY
-
PC-DUA is commercial oftware. For more details contact:
EXOR Faraday Building ighfields Science Park ottingham G7 2QP K N: c=GB@o=NEXOR Ltd elephone: 44 602 20500 ax: +44 602 20519 -Mail: sales@nexor.co.uk
DATE LAST UPDATED or CHECKED
-
August 6th, 1993
NAME
-
PC-Pages
Brunel University, UK
KEYWORDS
-
DUA Connectivity, DUA Only, IBM PC, LDAP, Limited Availability, Multiple Vendor Platforms, OSI Transport, RFC-1006
ABSTRACT
-
PC-Pages is a MS-DOS ased X.500 DUA nterface. It is currently only available for MS-Windows; a DOS character mode interface is being prepared.
Features include:
- "Form" based searching. - Supports the User Friendly ame (UFN) specification (RFC 1484). - Powerful query engine. - Tailorable ntry display - isplay nly those attributes required. - Integrates ith the WhiteMail X.400 user agent. Hooks are provided to llow integration with other user agents. - Directory browsing. - Support for JPEG photo attributes. - Modify directory entries. - Add directory entries. - Delete directory entries. - Rebind to a configured DSA. - Some support for configuration of DAP service parameters. Two versions f PC-Pages are urrently available. One supports DAP over ONS or AP over RFC-1006, and has data ntry and modification facilities. he other supports LDAP nd has more advanced ser interface including a tree-browser, but does ot yet ave data entry and modification. A version in he form or a Windows DLL (Dynamic Link ibrary) is being prepared, for incorporation into other roducts such as mail agents.
COMPLIANCE (applicable only for SAs and DUAs)
-
88 Standard compliant: Strong authentication ot yet mplemented. No plans for support of he 1992 Standard.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
[No information provided--Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
[No information provided--Ed.]
INTEROPERABILITY
-
Tested with Quipu 8.0.
PILOT CONNECTIVITY
-
DUA Connectivity: The interface is in use in he UK Academic Directory Pilot.
BUGS
-
Bugs hould be reported to x500@brunel.ac.uk.
CAVEATS nd GENERAL LIMITATIONS
-
Does ot support display or modification of all known attribute syntaxes. In articular: ACLs and O/R addresses.
INTERNETWORKING NVIRONMENT
-
RFC1006 with CP/IP. P4 with CONS. A NetBIOS gateway to the previously listed protocols. DAP using Winsock.
HARDWARE PLATFORMS
-
PC-Pages for indows equires an IBM C compatible with 286 or higher, 2mb+ emory.
SOFTWARE PLATFORMS
-
Windows 3.0 or 3.1 running in Standard or Enhanced mode. WhiteStack 1.1, rovided by the dinburgh University Computing Service.
AVAILABILITY
-
Free o UK Academic Community, and to some other communities ubject to certain restrictions. Commercial derivatives exist. Please send queries to:
Postal:
-
ndrew Findlay
omputing and Media Services
runel University
leveland Road
xbridge, Middlesex
B8 3PH
K
E-mail:
-
-
x500@brunel.ac.uk.
-
Fax: 44 895 2806 (Andrew Findlay) Telephone: +44 895 203066 (Andrew Findlay)
DATE LAST UPDATED or CHECKED
-
March 10th, 1994
NAME
-
QuickMail/X.500 Interface (DUA Interface) NASA
KEYWORDS
-
DUA Interface, Limited Availability, eeds ISODE, RFC-1274, Sun
ABSTRACT
-
The NASA QuickMail/X.500 Interface program is a program which translates QuickMail ame service requests into X.500 requests and returns the results from the SA to the QuickMail user. This system allows QuickMail users the ability to find non-QuickMail users' or non-local QuickMail users' addresses, while retaining the normal QuickMail lookup interface. he program speaks QuickMail name service protocol on one side, and DAP on the ther.
COMPLIANCE (applicable only for SAs and DUAs)
-
[Same as dish] -- does not support strong authentication. No support for 1992 extensions needed.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
RFC 1274 supported to the extent that we use rovided schema o store QuickMail addresses.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
[No information provided--Ed.]
INTEROPERABILITY
-
Works with Quipu (ISODE 8.0, CR1)
PILOT CONNECTIVITY
-
Connected to SI WPPP, PARADISE. Other projects may se data if they are connected to either of these DSAs.
BUGS
-
No known bugs. Default QuickMail name service lookup time out of 10 seconds may be too fast for some DSAs to respond to.
CAVEATS nd GENERAL LIMITATIONS
-
Requires the olumbia AppleTalk Package (CAP .0) to ork.
INTERNETWORKING NVIRONMENT
-
EtherTalk or PTalk on the Macintosh ide, any ISODE upported environment on the X.500 side.
HARDWARE PLATFORMS
-
Known to run n Sun 4/470
SOFTWARE PLATFORMS
-
SunOS 4.1.1 and 4.1.3 can be sed to ost the package. Additionally may need SunLink OSI .0.1, Sunlink X.25 7.0. ISODE .0 or ISODE Consortium Release 1 eeded to provide DAP support.
AVAILABILITY
-
Limited availability. For more details contact,
Peter Yee MS 233-18 NASA Ames esearch Center Moffett Field, CA 4035-1000 (415) 604-3812 (415) 604-6999 (FAX) yee@atlas.arc.nasa.gov
DATE LAST UPDATED or CHECKED
-
February 18th, 1993
NAME
-
QUIPU (ISODE onsortium Release 1.0)
ISODE Consortium
KEYWORDS
-
API, SA Connectivity, DSA/DUA, DUA Connectivity, Free, Multiple Vendor Platforms, OSI Transport, RFC-1006, RFC-1274, FC-1275, RFC- 1276, RFC-1277, RFC-1278, RFC-1279, RFC-1484, RFC-1485, RFC-1487, Source, Sun, NIX, X.25
ABSTRACT
-
This mplementation is a source release derived from he earlier openly available version of QUIPU, and will be used as base technology for products by a umber of vendors. The release comprises of a SA, and a number of sample DUAs which may be used in conjunction with the SA.
COMPLIANCE (applicable only for SAs and DUAs)
-
The DSA is aligned to the 1988 ISO IS and the NIST OIW Directory Implementors uide Version 1, with the following exceptions:
- Strong authentication is not implemented (but hooks are provided for use with two packages). - QUIPU does ot enforce the ounds constraints on attributes, filters or PDU size. - T.61 string formatting characters are not rejected. - If DN is upplied with no password in an nprotected simple bind, QUIPU does ot always check to see f the DN exists. If the DSA connected to can say authoritatively the DN does not exist, the association is rejected. However, if a chain operation is required to heck the DN, the bind IS allowed. - When comparing attributes of UTCtime syntax, if the seconds field is mitted, QUIPU does not erform he match correctly (i.e., the seconds field in the attribute values should be ignored, but are not). - QUIPU always supplies the optional haining argument "originator" even if the CommonArgument "requestor" is used. - QUIPU always supplies the optional haining argument "target" even if the base object in he DAP rguments is the same. - The object lass "without an assigned object identifier" is not recognised unless the "alias" object class is also present. - Non Specific Subordinate References are never followed by a QUIPU DSA, but they are passed on correctly to the client if generated.Compliance with X.500(1993) standards is planned. DAP and replication (DISP) will be available in March 1994. Other 1993 features, ith the exception of OB, but including security features will be available.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
INTEROPERABILITY
-
Interoperability with several other DSAs has een demonstrated in pilot operation and at the COS X.500 nteroperability Lab, enhancing interoperability results from the earler versions of UIPU.
PILOT CONNECTIVITY
-
Connectivity o the global research pilot (PARADISE etc.) has been demonstrated. It is expected hat this system will be used extensively in a wide range of pilot ctivities. DUA Connectivity, and DSA Connectivity.
BUGS
-
Bugs hould be reported to <bug-quipu@isode.com>
CAVEATS nd GENERAL LIMITATIONS
-
None
INTERNETWORKING NVIRONMENT
-
The IC R1.0 release is application level code, and assumes vendor provided lower layers. It provides the following modules with support for a range of APIs to handle associated lower layers:
- RFC 1006 (vendor supplied TCP/IP using sockets or TLI) - Transport service (vendor supplied ransport, which may be ny class and use any network service. LI, XTI and various vendor-specific APIs). - TP0 (Vendor supplied X.25 or CONS using NTI and various vendor specific APIs).
HARDWARE PLATFORMS
-
Reference platform is SUN SPARC.
SOFTWARE PLATFORMS
-
Reference OS s SUNOS 4.1.3. t is also known to run n various other UNIX latforms.
AVAILABILITY
-
Available to embers f the ISODE Consortium. Membership is open to any organisation. Also available under licence (zero ost) to all non-commercial research organisations. Contact:
-
SODE Consortium
eadquarters
O Box 505
ondon
W11 1DX
K
hone: +44-71-223-4062 ax: +44-71-223-3846 mail: ic-info@isode.com> -
DATE LAST UPDATED or CHECKED
-
August 11th, 993
NAME
-
Traxis Enterprise Directory
Angeli Systems Corporation
KEYWORDS
-
API, LNS, Commercially Available, DSA/DUA, HP, IBM PC, IBM RISC, Macintosh, OSI Transport, RFC-1006, RFC-1274, Sun, X.25
ABSTRACT
-
The Traxis Enterprise Directory has multiple omponents in a hree layer architecture. The individual components of the raxis family are building locks which can be assembled in a flexible, modular way to build complex systems. At the enterprise level, is a distributed directory stored and managed by Traxis Directory Engines (TDEs). At the workgroup evel Traxis Directory Hubs (TDHs) rovide he means to integrate and connect Traxis Directory Engines to the wide ariety f real orld applications nd systems which prevail in network environments. The TDE and the TDH support the myriad of client pplications, including messaging and business applications, hich require services from the Traxis directory. At the desktop level, the Traxis Desktop Client (TDC) provides a common set of facilities which simplify and enable communications, object manipulation, nd results management as required between the Traxis Directory Hub nd applications. These apabilities, which include full ccess and management of the directory, re provided to applications hrough DS++, the Traxis object oriented API. The Traxis Desktop Client also supports industry tandard client oftware interfaces such as Microsoft API, Apple OCE, CMC and VIM, through Compatibility Modules which map the standard PI into XDS++. hrough these APIs the Traxis Desktop Client upports applications of all kinds on PC, acintosh, and UNIX systems.
Angeli supplied Traxis applications include the Traxis Administrative Console management station, the Traxis Global Browser general directory tool, the Traxis Operator Assistance high-speed look-up, the Traxis Data Base ateway, the Traxis Import Export Utility and more.
The Traxis Directory ngine includes n X.500 DSA. The Traxis Directory Hub includes an X.500 DUA.
COMPLIANCE (applicable only for SAs and DUAs)
-
Traxis Directory Engine DSA is CCITT-1988 compliant with extended security and ccess control. upports access ontrol n User, Entry, and Attribute levels. DIB or ubtree dministrative manager supported. Supports simple authentication with encrypted password.
NIST IW Stable Implementation Agreements [NIST-88] compliant.
Support for February 4, 1993 CCITT X.500 planned. X.509 in first half f 1994. Replication and Administrative/Information Model in second half of 1994.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
Traxis conforms to RFC1274 which documents COSINE interoperability.
LDAP RFC 1487) is planned for inclusion in a later release of Traxis if market demand requires it.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
Traxis does not conform to the QUIPU FC Internet Proposals cited. As noted elsewhere, Traxis is fully compatible with QUIPU operationally but does not use the cited RFCs in its nternal operations.
INTEROPERABILITY
-
Traxis has been extensively tested for interoperability with SODE QUIPU Version 8. Traxis Directory Engine (DSA) will serve DISH or other QUIPU DUAs using DAP. Traxis Directory ub interoperates with QUIPU DSA. All directory access functions and their chained equivalents are interoperable.
PILOT CONNECTIVITY
-
PARADISE DUA/DSA connectivity tested.
BUGS
-
Problems may e reported to support@angeli.com.
CAVEATS nd GENERAL LIMITATIONS
-
None.
INTERNETWORKING NVIRONMENT
-
Traxis Directory Hub o Traxis Directory Engine (or any DSA) communication via RFC1006 over TCP/IP, OSI TP4 with CLNS, and OSI TP0 with .25. Traxis Desktop Client to Traxis Directory ub via PX/IPX or TCP/IP. Other LAN rotocols supported in 1994.
HARDWARE PLATFORMS
-
Traxis Directory Hub nd Traxis Directory Engine: Sun and PC urrently supported. IBM RS/6000, HP 9000, and others in 1994. Traxis Desktop Client and applications: PC urrently supported; Macintosh in 1994.
SOFTWARE PLATFORMS
-
Traxis Directory Hub nd Traxis Directory Engine: All Sun platforms with Sun S 4.1.3 currently supported, Solaris 2.x in 1994. Industry standard PC platforms with SCO Open Desktop V3 urrently supported. Other UNIX platforms in 1994. Windows NT in 994. Traxis Desktop Client and applications: PC ith Windows 3.1 currently supported. Macintosh ystems and 7, UNIX Motif, DOS, X indows, and others planned for 994.
AVAILABILITY
-
The Traxis Enterprise Directory is commercially available from:
-
Angeli Systems Corporation
1659 Eleventh Street
Santa Monica, CA 90404
+1 310 392 3000
+1 310 392 4700 FAX
info@angeli.com
-
DATE LAST UPDATED or CHECKED
-
November 23rd, 1993
NAME
-
UCOM.X 500 (tm) - E3.X [DSA and DUA]
KEYWORDS
-
386, PI, Bull, CLNS, Commercially Available, DEC ULTRIX, DSA Connectivity, DSA/DUA, DUA Connectivity, IBM ISC, Motif, Multiple Vendor Platforms, OpenLook, RFC-1006, RFC-1274, RFC-1277, RFC-1278, RFC-1279, Sequent, Sun, Tandem, UNIX, X.25
ABSTRACT
-
UCOM.X 500 includes a Directory System Agent DSA), various directory access APIs and Directory User Agents (DUAs). UCOM.X 00 is a product based on PIZARRO, the research prototype developed at INRIA by Christian Huitema's team, and commercialized y TS-E3X, a member of the France Telecom group.
Characteristics of the DSA are:
- The DAP and DSP protocols are provided conformant with X.500 (88). - The DIB is aintained in ASN.1 encoded format in the Unix file system. Utilities re provided to oad and dump the DIB from and to SCII text files. - The DIT structure is held in main memory. Frequently used attributes may be held in inverted tables in memory to speed up searches. - Knowledge management: knowledge on anaged omains s stored in UCOM.X specific attributes f the DSA entries. - Schema: The X.500 (88), X.400 (88) nd most of the osine and Internet Schema are supported. Object class and attribute definitions are enforced. sers may define their own. - Simple authentication is provided; trong authentication and signed operations are being tested perationally through TS-E3X's participation in PASSWORD, VALUE roject ith aim to pilot a European security infrastructure for network applications. - Access control: private mechanisms re provided to llow access control lists to be specified for parts of he DIT, to control modifications, and o specify access restrictions on attributes. - Management: a UCOM.X DSA object has been defined to allow operational parameters of the DSA to be managed via DAP. Administration utilities are provided to, e.g., generate usage statistics nd periodically update he database from various data sources including a knowledge discovery tool. The product offers a language API conformant to X/Open's X/DS specification, and a ++ API for release 10/93). The DUAs include a graphical irectory browser with powerful earch functionality for OpenLook and Motif, and a full-screen curses-based interface with full DAP functionality. TS-E3X's strategy for UCOM.X500 is three-fold: Firstly, to use it as the directory service for Spheris, France Telecom's range of electronic mail products based on X.400 (88) release mid '94). Secondly, to ffer it to third parties developing specific applications sing X.500: current applications include a distributed application to control document transfer in a large French hospital and distributed applications anagement in the French Post Office; planned uses nclude ffice applications for ontrol f document circulation (workflow) and cooperative document editing. Thirdly, to offer it to telecomms operators such s France Telecom for application in network management. UCOM.X 500 is used extensively by French research centers involved in PARADISE.
COMPLIANCE (applicable only for SAs and DUAs)
-
UCOM.X 500 conforms to X.500 88) as pecified in paragraph 9 of X.519. Development of the product based on X.500 (93) is planned for '94 with elease f a product conformant o the principal extensions at the end of '94. Emphasis is being placed on the shadowing protocol, the schema and access control.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
The COSINE and Internet Schema (RFC 1274) is upported with minor exceptions.
The string representation of SAPs and their nternal encoding conforms to RFC 1277. The string representation of Ns will migrate to the nternet RFC 1485 efinition.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
RFC 1279 (X.500 and Domains) s supported. The string representation of PSAPs and heir internal encoding onforms to RFC 278. AFRO algorithme francais de echerche optimise), the search name resolution algorithm roposed by UCOM.X 500, iffers rom the UFN algorithm principally in that it attempts to ptimize by performing read perations before resorting to searches n order to exploit the name rror information.
INTEROPERABILITY
-
Through UCOM.X 500's se in the French PARADISE pilot, interoperability has een informally ut extensively ested with Quipu and other implementations. Detailed interoperability tests with Quipu, arben and Siemens/Bull DIR/X are being conducted by the PARADISE OIFP (Operational Interworking) team at INRIA Rocquencourt, France. The product s currently also undergoing formal tests for conformance to the CTS2 DSA/DAP and ACSE/Presentation/Session specifications at the French OSI conformance test centre.
PILOT CONNECTIVITY
-
DSA and DUA connectivity to the PARADISE pilot.
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 and inverted attribute tables are stored in main memory. The recommended main emory size for DSA is 1 kb per node, i.e., 10 Mb for a database of 10,000 bjects. The current recommended maximum is a atabase size of the order of 100,000 objects. Of the selected attribute types defined in X.500 (88), the searchGuide attribute is not upported ; neither are he following attributes from the Cosine and Internet Schema (RFC 1274): OtherMailbox, MailPreferenceOption and the various quality attributes. The X/DS API upports the Basic Directory Contents (BDCP), the MHS Directory User (MDUP) and the Strong uthentication (SAP) packages with inor limitations. A proprietary mechanism for defining ew classes and attributes is offered. Asynchronous operations and multiple concurrent sessions re not upported. Whilst referral may be handled automatically, continuation references are not.
INTERNETWORKING NVIRONMENT
-
UCOM.X 500 includes a transport stack for TP0 with TCP/IP (RFC 1006) and X.25. The stack as been ported o SunNet OSI for TP4 with CLNP.
HARDWARE PLATFORMS
-
UCOM.X 500 can easily be ported to any UNIX machine. t currently runs n: Sun and 4, IBM RS 000, DEC ULTRIX (Vax and Mips), 386- based PCs, Bull DPX/2 and DPX/20, Sequent, Tandem and others.
SOFTWARE PLATFORMS
-
UCOM.X 500 is portable to any UNIX-like operating system. It as been ported to: UNIX SVR3 nd SVR4, SUN OS 4, AIX, SCO Unix, Interactive Unix, ULTRIX, HP-UX, ynix (Sequent), BOS (Bull) and thers.
Ports to the ollowing are planned: OS/2 ('94), Windows 3 ('94).
The product does not ake use of an external BMS for the information base.
AVAILABILITY
-
UCOM.X is commercially available. For further information contact:
Pascal uchamp, International Sales Address: TS-E3X, Le Capitole 44, avenue des Champs Pierreux, 99029 Nanterre Cedex, France Tel: (+33) 1-46-14-50-00 Fax: (+33) 1-46-14-58-16 Email: =FR;A=atlas;P=e3x;O=e3x;OU1=paris;S=duchamp duchamp@paris.e3x.fr-
or:
Laurence Puvilland, Marketing Email: =fr;A=atlas;P=e3x;O=e3x;OU1=paris;S=puvilland puvilland@paris.e3x.fr-
or:
Ascan Woermann, R&D Email: =fr;A=atlas;P=e3x;O=e3x;S=Woermann woermann@e3x.fr -
DATE LAST UPDATED
-
July, 1993
NAME
-
Wang PEN/services (tm)
Wang aboratories, Inc.
KEYWORDS
-
CLNS, Commercially Available, DSA/DUA, DUA Interface, HP, IBM PC, IBM RISC, Limited Functionality, SI Transport, RFC-1006, Wang, X.25
ABSTRACT
-
Wang's X.500 roducts are a part of our OPEN/services product whose main eatures include the following:
X.500 directory - Contains information about rganizations, individuals, nd distribution lists. he directory is the primary vehicle by which users of OPEN/office, Wang's X.400 electronic mail product, address mail.
Authentication Services - Verifies the login ame and password of each ser logging into OPEN/services.
International support - Provides character translation tables so that users can display screens containing nternational characters and use international collating sequences.
Object management - Greatly increases the integration between OPEN/services, OPEN/office and other indows-based applications.
Activity logging - Records the activities of PEN/services. This information can be useful for monitoring the PEN/services processes and for troubleshooting.
Database management - Provides utilities that validate and reorganize the OPEN/services databases including the Directory Information Base (DIB).
OPEN/services includes a DSA, a DUA, nd a DUA interface all olled into ne product. (The DUA interface rotocol is private.) Wang PEN/services consists of two parts: software installed n a server and software installed on PC clients on a LAN. The client or end-user software enables users to log in and log out; change the login password; use the OPEN/services directory; and erform arious actions, such as open and print, on files in he Wang OPEN/applications and in certain third-party pplications including Microsoft Windows File Manager. The server consists of the DSA, the DUA, he Directory Information Base, he service administration programs such as login authentication, the database management utilities, and activity logging.
COMPLIANCE (applicable only for SAs and DUAs)
-
Wang PEN/services complies with the 988 CCITT Recommendations X.500-X.521 [CCITT-88] with the following exceptions. Whole tree searches are ot supported, nor does he product support chained adding, modifying, or deleting. Simple authentication is supported, but strong authentication is ot.
In the future, the 1992 extensions to the X.500 standard will be supported by ang OPEN/services.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
None re supported at the present time.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
None re supported at the present time.
INTEROPERABILITY
-
The interoperability f OPEN/services with other X.500 products is untested.
PILOT CONNECTIVITY
-
Pilot connectivity between OPEN/services and he AARNET project, NADF Pilot Project, NIST Pilot Project, PARADISE, nd PSI hite Pages Project has not been ttempted.
BUGS
-
To report problems with Wang PEN/services, contact your local Wang sales office, your Wang authorized reseller or call your regional support center. (In the USA, he number is 404-432-9001).
CAVEATS nd GENERAL LIMITATIONS
-
None
INTERNETWORKING NVIRONMENT
-
Wang PEN/services currently uns in he following environments: RFC1006 with CP/IP, P4 with CNLS, TP0 with .25 and SLIP.
HARDWARE PLATFORMS
-
Server Requirements Installing Wang OPEN/services Server equires the following hardware: a Wang RISC Series Server 220 or greater, or n IBM RISC System/6000(tm) with minimum of 32 B of memory, or a Hewlett- Packard 9000 eries 800 system with a minimum of 32 MB of memory. For each ystem a minimum of 20 MB of free disk space in file system is required. Client Requirements Installing OPEN/services for indows equires the following hardware: a 386/SX CPU r later, at least 4 MB f memory, a hard disk drive with t least 2.5 MB f disk pace, and a VGA monitor. A pointing device is not required to run OPEN/services but is strongly recommended. Network Requirements OPEN/services has the following network requirements: 802.3 or 802.5 LAN, etwork nterface cards NICs) to support TCP/IP on client PCs, Ethernet or token ring adapters on the servers, and optionally X.25 cards on the ervers.
SOFTWARE PLATFORMS
-
Server Requirements
Installing Wang OPEN/services Server equires the following software: AIX Operating System, release 3.2.3 or later, with bundled support for the TCP/IP protocol suite, or HP-UX Operating System, Release 9.0 or later.
Client Requirements OPEN/services for Windows requires the following software: Microsoft MS-DOS(tm) Operating ystem, elease .0 or later and Microsoft Windows 3.1 or later.
AVAILABILITY
-
Wang PEN/services is commercially available rom: Wang Laboratories, Inc. 1 ndustrial Avenue Lowell, Massachusetts 01851 Phone: 508-967-6114 FAX: 508-967-1105To obtain OPEN/services, contact your local Wang sales office, your Wang uthorized reseller or call 1-800-NEW-WANG.
DATE LAST UPDATED or CHECKED
-
December 6th, 1993
NAME
-
Xdi - DUA
Bellcore
KEYWORDS
-
Available via FTP, DUA Connectivity, UA Only, Free, imited Functionality, Multiple Vendor Platforms, Needs ISODE, RFC-1274, RFC-1484, Source, Sun, UNIX, Window System
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 of different levels of complexity. Users can select different window screens to browse, search and modify he Directory. There are two different search screens for name based search and attribute ased search. It is simple to use for novice users but is lso useful for ore advanced users to formulate complex search filters. Xdi lso supports "user-friendly naming" in any cases so that users are not required o know .500 naming format.
COMPLIANCE (applicable only for SAs and DUAs)
-
88 standard compliant: Delete and Add operations, and strong authentication not implemented. There are no acilities to modify the RDNs f entries.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
RFC 1274 is supported.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
RFC 1484 is supported.
INTEROPERABILITY
-
Believed to be interoperable ith other DSAs. Only tested against ISODE/QUIPU DSAs.
PILOT CONNECTIVITY
-
DUA Connectivity
BUGS
-
Send ug reports to sywuu@thumper.bellcore.com
CAVEATS nd GENERAL LIMITATIONS
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 7.0 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 environments f ISODE.
AVAILABILITY
-
The Xdi software is available via anonymous FTP from thumper.bellcore.com n file ub/xdi.tar.Z. Source code and executables can be freely distributed or modified for non-commercial and non-profit use provided that all opyright notices, permission and nonwarranty notice included in the software distribution emain intact.
For further information contact Sze-Ying Wuu t sywuu@thumper.bellcore.com.
DATE LAST UPDATED or CHECKED
-
March 18th, 1993
NAME
-
XLU
Brunel University, UK
KEYWORDS
-
DUA Connectivity, DUA Only, Free, Multiple Vendor Platforms, eeds ISODE, Source, UNIX, Window System
ABSTRACT
-
XLU (X LookUp) is an .500 DUA interface for he X Window System.
XLU can be configured for many different styles of interaction. Example configurations are provided for single window and multiple window use.
XLU implements the `User-Friendly Naming' search strategy and also has a form-filling search mode. Asynchronous irectory operations are used.
Full ser friendly add and modify functions are provided, with the ability to tailor the modify creen to present simple subsets of the available attributes.
COMPLIANCE (applicable only for SAs and DUAs)
-
88 Standard compliant: Strong authentication ot yet mplemented. No plans for support of he 1992 Standard.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
No plans at present.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
-
No plans at present.
INTEROPERABILITY
-
[No information provided--Ed.]
PILOT CONNECTIVITY
-
DUA Connectivity: The interface is in use in he UK Academic Directory Pilot.
BUGS
-
Bugs hould be reported to x500@brunel.ac.uk.
CAVEATS nd GENERAL LIMITATIONS
-
[No information provided--Ed.]
INTERNETWORKING NVIRONMENT
-
As ISODE.
HARDWARE PLATFORMS
-
Most NIX machines.
SOFTWARE PLATFORMS
-
UNIX
MIT X11R5 libraries
ISODE/QUIPU (version .0 >)
AVAILABILITY
-
Sources are freely available or commercial or non-commercial use. Contacts.
Postal Address:
-
ndrew Findlay
omputing and Media Systems
runel University
leveland Road
xbridge, Middlesex
B8 3PH
K
E-mail:
-
-
x500@brunel.ac.uk.
-
Fax: 44 895 2806 (Andrew Findlay) Telephone: +44 895 203066 (Andrew Findlay)
DATE LAST UPDATED or CHECKED
-
March 1st, 1993
NAME
-
XT-DUA
NEXOR
KEYWORDS
-
Bull, CLNS, Commercially Available, DUA Connectivity, DUA Only, HP, IBM RISC, ICL, Motif, Multiple Vendor Platforms, OpenLook, OSI Transport, RFC-1006, FC-1274, RFC-1277, RFC-1278, RFC-1484, Solbourne, Sun, X Window System, X.25
ABSTRACT
-
XT-DUA provides a X-Windows based user interface to the X.500 Directory. Both Motif and OpenLook styles are supported.
Browsing features include:
- Passing of ser address information to the T-MUA X.400 user agent. - History - allowing uick access to reviously referenced parts of the DIT. - Customizable entry isplay allowing subsets of attributes be displayed when showing an entry. - User Friendly Name UFN) based searching - Hypertext-like navigation. - Support for application entities e.g. startup of ftam session. - User defined name for attribute labels. - Support for photo and audio attributes. - Attribute value on canline. - Intelligent choice f entries to display when moving to a new location in the DIT.Management features include:
- Creation of new entries. - Modification of existing entries (including RDN) - ased on Quipu EDB format. - Deletion of entries. - Friendly editor of odifying Quipu CLs. - Rebinding - authenticated and to named DSA. - Full configuration f DAP request parameters
COMPLIANCE (applicable only for SAs and DUAs)
-
Compliant with X.500(88), and NIST SIA version 2 except X.509 strong authentication not implemented (under development).
NEXOR is committed to migrate XT-DUA o the 1992 standards.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
-
The following are supported: FC 1274 and RFC 1277.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
INTEROPERABILITY
-
XT-DUA has interoperated with all DSAs used in the PARADISE pilot.
PILOT CONNECTIVITY
-
Full UA connectivity to the ARADISE and PSI White Pages X.500 Pilots.
BUGS
-
No known bugs. Support is given via hone or email to "support@nexor.co.uk"
CAVEATS nd GENERAL LIMITATIONS
-
None.
INTERNETWORKING NVIRONMENT
-
OSI TP4 with LNP, OSI TP0 with X.25 r CONS, and RFC 1006 with TCP/IP
HARDWARE PLATFORMS
-
-
Sun
Solbourne
IBM RS/6000
Bull DPX 6000
HP Apollo 000
-
SOFTWARE PLATFORMS
-
-
SunOs 4.1.x
AIX 3.2
HP-UX 9.01
Windows 3.1 (over DAP)
Other ports planned include SCO Unix nd ICL RS6000.
-
AVAILABILITY
-
XT-DUA is commercial oftware. For more details contact:
T-DUA Sales EXOR Faraday Building ighfields Science Park ottingham G7 2QP K N: c=GB@o=NEXOR Ltd elephone: 44 602 20500 ax: +44 602 20519 -Mail: sales@nexor.co.uk
DATE LAST UPDATED or CHECKED
-
August 2nd, 1993
NAME
-
XT-QUIPU
NEXOR
KEYWORDS
-
Bull, CLNS, Commercially Available, DSA Connectivity, DSA Only, HP, IBM RISC, ICL, Multiple Vendor Platforms, OSI Transport, RFC-1006, RFC-1274, RFC-1276, RFC-1277, RFC-1278, RFC-1279, RFC-1484, RFC-1485, Solbourne, Sun, X.25
ABSTRACT
-
XT-QUIPU is an X.500(88) DSA. Characteristics of the DSA are:
- Full DAP access - Full DSP access - Support for X.400, .500, and RFC 1274 attributes and object classes - Approximate match based on oundex. - Flexible schema management - RFC 1276 Replication - Attribute level access control - Search and ist access control - Knowledge management mapped onto DIT - Attribute inheritance - Caching - Remote management
COMPLIANCE (applicable only for SAs and DUAs)
-
Compliant with X.500(88), and NIST SIA version 2 except X.509 strong authentication not implemented (under development).
NEXOR is committed to migrate XT-QUIPU to the 1992 standards.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL FCs
INTEROPERABILITY
-
XT-QUIPU interoperates will all DSAs sed in he PARADISE pilot.
PILOT CONNECTIVITY
-
XT-QUIPU DSAs are fully connected to he PARADISE and PSI White Pages X.500 Pilots.
BUGS
-
No known bugs. Support is given via hone or email to "support@nexor.co.uk"
CAVEATS nd GENERAL LIMITATIONS
-
None.
INTERNETWORKING NVIRONMENT
-
OSI TP4 wtih LNP OSI TP0 with .25 or ONS RFC 1006 with TCP/IP
HARDWARE PLATFORMS
-
Sun
Solbourne
IBM RS/6000
Bull PX 6000
ICL DRS/6000
HP Apollo 9000
SOFTWARE PLATFORMS
-
SunOs 4.1.x
AIX 3.2
DRS/NX 6000
HP-UX 9.01Other ports planned include SCO Unix.
AVAILABILITY
-
XT-QUIPU is commercial software. For more details contact:
T-QUIPU Sales EXOR Faraday Building ighfields Science Park ottingham G7 2QP K N: c=GB@o=NEXOR td elephone: +44 602 520500 ax: +44 602 520519 -Mail: sales@nexor.co.uk
DATE LAST UPDATED or CHECKED
-
August 2nd, 1993
4. References
-
[CCITT-88] CITT, "Data Communications Networks Directory", Recommendations .500-X.521, Volume VIII - Fascicle VIII.8, Xth Plenary Assembly, Melbourne, November 1988. [NIST-88] ational Institute of Standards nd Technology, Stable Implementation Agreements for Open Systems Interconnection rotocols", Version 2 Edition 1, NIST Special ublication 500-162, December 1988. [RFC 1202] ose, M., "Directory Assistance ervice", RFC 1202, Performance Systems International, Inc., February 1991. [RFC 1249] owes, T., Smith, M., and B. Beecher, "DIXIE Protocol Specification", FC 1249, University of ichigan, August 1991. [RFC 1274] arker, ., and . Kille, "The COSINE and Internet X.500 Schema", RFC 1274, University College, London, England, November 1991. [RFC 1275] ille, S., "Replication equirements to rovide n Internet Directory using X.500," RFC 1275, University College, London, England, November 1991. [RFC 1276] ille, S., "Replication and Distributed Operations extensions to provide an Internet Directory using X.500", FC 1276, University College, London, England, November 1991. [RFC 1277] ille, S., "Encoding Network Addresses o support operation over non-OSI lower layers", RFC 1277, University College, London, England, November 1991. [RFC 1278] ille, S., "A string encoding of Presentation Address", RFC 1278, University College, London, England, November 1991. [RFC 1279] ille, S., "X.500 and Domains", FC 1279, University College, London, England, November 1991. [RFC 1484] ille, S., "Using the OSI Directory to achieve User Friendly Naming", RFC 1484, ISODE Consortium, July 1993. [RFC 1485] . Kille, "A String Representation of Distinguished-
Names", FC 1485, ISODE onsortium, July 1993.
[RFC 1487] eong, W., Howes, T., and S. Kille, "X.500 Lightweight Directory Access Protocol", RFC 487, Performance Systems nternational, University of Michigan, ISODE Consortium, July 1993. [RFC 1488] owes, T., Kille, S., Yeong, W., and C. obbins, "The X.500 String Representation of Standard ttribute Syntaxes", RFC 1488, University f Michigan, ISODE Consortium, Performance ystems nternational, NeXor Ltd., July 1993.
-
5. Security Considerations
-
Security issues are not discussed in his memo.
6. Editors' Addresses
-
Arlene F. Getchell
Lawrence Livermore National Laboratory
National Energy Research Supercomputer Center
P.O. ox 5509, L-561
Livermore, CA 94551Phone: (510) 23-6349 EMail: getchell@es.net X.400: s=getchell;p=esnet;a= c=us; Srinivas R. Sataluri AT&T ell Laboratories Room C-429, 01 Crawfords Corner Road P.O. ox 3030 Holmdel, NJ 07733-3030 Phone: (908) 49-7782 EMail: sri@qsun.att.com