RFC 1632
A Revised Catalog of Available X.500 Implementations
RFC 1632: A Revised Catalog of Available X.500 Implementations 💖
Okay bestie, this is RFC 1632 🦋 It's an FYI doc (FYI 11 if you're counting 🧚) from the Network Working Group, published May 1994. The authors are A. Getchell of Lawrence Livermore National Laboratory and S. Sataluri of AT&T Bell Laboratories, and both are listed as Editors. It's in the Informational category, so it gives info to the Internet community and is not an Internet standard. It obsoletes RFC 1292 (so 1292 is officially retired, this is the glow-up 💅) and doesn't update anything else.
Status of This Memo ✨
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
Abstract 📚
This document is the result of a survey that gathered new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings. It's a revision of RFC 1292. The team contacted each contributor from RFC 1292 and asked for an update, posted the survey template to several mailing lists, and collected new product descriptions 🙌
This document has detailed descriptions of twenty six (26) X.500 implementations: DSAs, DUAs, and DUA interfaces. 🎀
1. Introduction 🦋
This document catalogs currently available implementations of X.500, both commercial products and openly available offerings. For the purposes of this survey, X.500 products are sorted into three groups:
- DSA: A DSA is an OSI application process that provides the Directory functionality.
- DUA: A DUA is an OSI application process that represents a user in accessing the Directory and uses the DAP to communicate with a DSA.
- DUA Interface: A DUA Interface is an application process that represents a user in accessing the Directory using either DAP but supporting only a subset of the DAP functionality, or a protocol different from DAP to communicate with a DSA or DUA.
Section 2 of this document has a listing of implementations cross referenced by keyword. This list should help you find implementations that match your criteria 🔍
To put this catalog together, the IDS Working Group asked the X.500 community for input by surveying several Internet mailing lists, including iso@nic.ddn.mil, isode@nic.ddn.mil, osi-ds@cs.ucl.ac.uk, and ietf-ids@umich.edu. They also called lots of people, sent the template to several individuals, and mailed a floppy disk with the survey template to a person who didn't have Internet access 💾
Readers are encouraged to send comments about both the form and content of this memo. New submissions are welcome! Please send input to the Integrated Directory Services (IDS) Working Group (ietf-ids@umich.edu) or to the editors. IDS will produce new versions of this document once a sufficient number of changes have been received. The IDS chairpersons decide when that happens 👑
1.1. Purpose
The Internet has seen steady growth in X.500 piloting activities 📈 This document aims to be an easy-to-reach source of information on X.500 implementations for anyone thinking about X.500 technology for deploying a Directory service.
1.2. Scope
This document describes both free and commercial X.500 implementations. It does not explain how to install, run, or manage these implementations. The descriptions and indices are there to make readers aware of their options so they can make more informed choices 🧠
1.3. Disclaimer
Implementation descriptions were written by implementors and vendors, not by the editors. The editors worked with the description authors to keep things uniform and readable, but they cannot guarantee the accuracy or completeness of the descriptions, or the stability of the implementations. Read with a grain of salt, bestie 🧂
1.4. Overview
Section 1 contains introductory information.
Section 2 contains a list of keywords, their definitions, and a cross reference of the X.500 implementations by these keywords.
Section 3 contains the X.500 implementation descriptions.
Section 4 has a list of references.
Section 6 lists the editors' addresses.
1.5. Acknowledgments 🫶
This catalog would not have happened without the description authors and the members of the IDS Working Group. Huge thanks to the editors of RFC 1292, Ruth Lang and Russ Wright, who helped them get started and made key suggestions so the team could learn from their experience. They also appreciated the efforts of Ken Rossen, who got six descriptions 🌸
2. Keywords 🏷️
Keywords are abbreviated attributes of the X.500 implementations. The keyword list below was built from the implementation descriptions themselves. Implementations were tagged with a keyword either because of (1) an explicit, not implied, reference to a particular capability in the implementation description text, or (2) input from the implementation description author(s) 💅
2.1. Keyword Definitions
This section contains keyword definitions, organized into functional categories. The definitions are sorted first alphabetically by keyword category, then alphabetically by implementation name within each keyword category. ✨
2.1.1. Availability
Available via FTP: Implementation is available using FTP.Commercially Available: This implementation can be purchased. 💰Free: Available at no charge, although other restrictions may apply.Limited Availability: You need to contact the provider for terms and conditions of distribution.Source: Source code is available, potentially at an additional cost.
2.1.2. Conformance with Proposed Internet Standards
These RFCs specify standards track protocols for the Internet community. Implementations that conform to these evolving proposed standards have a higher probability of interoperating with other implementations deployed on the Internet 🤝
RFC-1274: Implementation supports RFC 1274: Barker, P., and S. Kille, The COSINE and Internet X.500 Schema, University College, London, England, November 1991.RFC-1276: Implementation supports RFC 1276: Kille, S., Replication and Distributed Operations extensions to provide an Internet Directory using X.500, University College, London, England, November 1991.RFC-1277: Implementation supports RFC 1277: Kille, S., Encoding Network Addresses to support operation over non-OSI lower layers, University College, London, England, November 1991.RFC-1485: Implementation supports RFC 1485: Kille, S., A String Representation of Distinguished Names, ISODE Consortium, July 1993.RFC-1487: Implementation supports RFC 1487: Yeong, W., T. Howes, and S. Kille, X.500 Lightweight Directory Access Protocol, July 1993.
2.1.3. Consistence with Informational and Experimental Internet RFCs
These RFCs give information to the Internet community and are not Internet standards. Complying with these RFCs isn't necessary for interoperability, but it may enhance functionality 🌈
RFC-1202: Implementation supports RFC 1202: Rose, M. T., Directory Assistance Service. February 1991.RFC-1249: Implementation supports RFC 1249: Howes, T., M. Smith, and B. Beecher, DIXIE Protocol Specification, University of Michigan, August 1991.RFC-1275: Implementation supports RFC 1275: Kille, S., Replication Requirements to provide an Internet Directory using X.500, University College, London, England, November 1991.RFC-1278: Implementation supports RFC 1278: Kille, S., A string encoding of Presentation Address, University College, London, England, November 1991.RFC-1279: Implementation supports RFC 1279: Kille, S., X.500 and Domains, University College, London, England, November 1991.RFC-1484: Implementation supports RFC 1484: Kille, S., Using the OSI Directory to achieve User Friendly Naming, ISODE Consortium, July 1993.
2.1.4. Implementation Type 🧩
API: Implementation comes with an application programmer's interface (i.e., a set of libraries and include files).DSA Only: Implementation consists of a DSA only. No DUA is included.DSA/DUA: Both a DSA and DUA are included in this implementation.DUA Interface: Implementation is a DUA-like program that uses either DAP, but supporting only a subset of the DAP functionality, or uses a protocol different from DAP to communicate with a DSA or DUA.DUA Only: Implementation consists of a DUA only. No DSA is included.LDAP: DUA interface program uses the Lightweight Directory Access Protocol (LDAP).
2.1.5. Internetworking Environment 🌐
CLNS: Implementation operates over the OSI ConnectionLess Network Service (CLNS).OSI Transport: Implementation operates over one or more OSI transport protocols.RFC-1006: Implementation operates over RFC-1006 with TCP/IP transport service. RFC-1006 is an Internet Standard. 🔥X.25: Implementation operates over OSI X.25.
2.1.6. Pilot Connectivity 🔌
DUA Connectivity: The DUA can be connected to the pilot, and information on any pilot entry can be looked up. The DUA is able to display standard attributes and object classes, and those defined in the COSINE and Internet Schema.DSA Connectivity: The DSA is connected to the DIT, and information in this DSA is accessible from any pilot DUA.
2.1.7. Miscellaneous 🎈
Included in ISODE: DUAs that are part of ISODE.Limited Functionality: Survey states that the implementation has some shortcomings or an intended lack of functionality, e.g., omissions were part of the design to provide an easy-to-use user interface.Motif: Implementation provides a Motif-style X Window user interface.Needs ISODE: ISODE is required to compile and/or use this implementation.OpenLook: Implementation provides an OpenLook-style X Window user interface.X Window System: Implementation uses the X Window System to provide its user interface.
2.1.8. Operating Environment 💻
386: Implementation runs on a 386-based platform.Bull: Implementation runs on a Bull platform.CDC: Implementation runs on a CDC MIPS platform.DEC ULTRIX: Implementation runs under DEC ULTRIX.DEC Vax OpenVMS: Implementation runs on a DEC VAX platform running OpenVMS.HP: Implementation runs on an HP platform.IBM PC: Implementation runs on a PC.IBM RISC: Implementation runs on IBM's RISC UNIX workstation.ICL: Implementation runs on an ICL platform.Macintosh: Implementation runs on a Macintosh. 🍓Multiple Vendor Platforms: Implementation runs on more than one hardware platform.Sequent: Implementation runs on a Sequent platform.SNI: Implementation runs on a Siemens Nixdorf platform.Solbourne: Implementation runs on a Solbourne platform.Sun: Implementation runs on a Sun platform.Tandem: Implementation runs on a Tandem platform.UNIX: Implementation runs on a generic UNIX platform.Wang: Implementation runs on a Wang RISC platform.
2.2. Implementations Indexed by Keyword ✨
okay bestie, this is the index, so if you're hunting for a specific implementation that matches your vibe (your criteria 💅), start here 🧚. Keywords are sorted alphabetically, and so are the implementations under each one. A * means that implementation, or a feature of it, might not be around right now 🙈.
For formatting purposes, the implementation names get shortened like this:
- BULL S.A. = Bull X500-DS and X500-DUA
- DEC X.500 DSA = DEC X.500 Directory Server
- DEC X.500 Admin = DEC X.500 Administration Facility
- HP X.500 DD = HP X.500 Distributed Directory
- LDAP = University of Michigan LDAP Implementation
- OSI Access & Dir = OSI Access and Directory
- Traxis = Traxis Enterprise Directory
386 CLNS
PathWay Messaging Bull S.A.
PC-DUA DEC X.500 DSA
UCOM X.500 DEC X.500 Admin
DIR.X
API HP X.500 DD
HP X.500 DUA
Bull S.A. OSI Access & Dir
Custos PathWay Messaging
DEC X.500 DSA Traxis
DEC X.500 Admin UCOM X.500
DIR.X Wang OPEN/services
HP X.500 DD XT-DUA
HP X.500 DUA XT-QUIPU
LDAP
OSI Access & Dir Commercially Available
QUIPU
Traxis Bull S.A.
UCOM X.500 DEC X.500 DSA
DEC X.500 Admin
Available via FTP DIR.X
Directory 500
Custos HP X.500 DD
DE HP X.500 DUA
DOS-DE OSI Access & Dir
LDAP PathWay Messaging
ldap-whois++ PC-DUA
maX.500 Traxis
Xdi UCOM X.500
Wang OPEN/services
Bull XT-DUA
XT-QUIPU
Bull S.A.
UCOM X.500 DEC ULTRIX
XT-DUA
XT-QUIPU DEC X.500 DSA
DEC X.500 Admin
CDC LDAP
ldap-whois++
OSI Access & Dir UCOM X.500
DEC VAX OpenVMS
DEC X.500 DSA
DEC X.500 Admin
DSA Connectivity DUA Interface
DIR.X DE
OSI Access & Dir DOS-DE
PathWay Messaging LDAP
QUIPU ldap-whois++
UCOM X.500 maX.500
XT-QUIPU OSI Access & Dir
Pathway Messaging
DSA Only PC-DUA
QuickMailDUA
DEC X.500 DSA Wang OPEN/services
XT-QUIPU
DUA Only
DSA/DUA
DEC X.500 Admin
Bull S.A. HP X.500 DUA
Custos MXLU
DIR.X PC-Pages
Directory 500 Xdi
HP X.500 DD XLU
OSI Access & Dir XT-DUA
PathWay Messaging
QUIPU Free
Traxis
UCOM X.500 Custos
Wang OPEN/services DE
DOS-DE
DUA Connectivity LDAP
ldap-whois++
DIR.X maX.500
LDAP MXLU
maX.500 QUIPU
MXLU Xdi
OSI Access & Dir XLU
PathWay Messaging
PC-DUA HP
PC-Pages
QUIPU DIR.X
UCOM X.500 HP X.500 DD
Xdi HP X.500 DUA
XLU LDAP
XT-DUA *Traxis
Wang OPEN/services
XT-DUA
XT-QUIPU
IBM PC Limited Functionality
DOS-DE Custos
LDAP Wang OPEN/services
OSI Access & Dir Xdi
PathWay Messaging
PC-DUA Macintosh
PC-Pages
Traxis LDAP
Wang OPEN/services maX.500
PathWay Messaging
IBM RISC *Traxis
DIR.X Motif
LDAP
*Traxis DEC X.500 Admin
UCOM X.500 MXLU
Wang OPEN/services UCOM X.500
XT-DUA XT-DUA
XT-QUIPU
Multiple Vendor Platforms
ICL
Custos
*XT-DUA DE
XT-QUIPU DOS-DE
LDAP
Included In ISODE MXLU
PathWay Messaging
DE PC-Pages
QUIPU
LDAP UCOM X.500
Xdi
DE XLU
DOS-DE XT-DUA
LDAP XT-QUIPU
ldap-whois++
maX.500 Needs ISODE
OSI Access & Dir
*Pathway Messaging Custos
PC-DUA DE
*PC-Pages MXLU
QuickMailDUA
Limited Availability Xdi
XLU
PC-Pages
QuickMailDUA
OpenLook RFC-1249
UCOM X.500 OSI Access & Dir
XT-DUA
RFC-1274
OSI Transport
DE
Bull S.A. DEC X.500 DSA
Custos DEC X.500 Admin
DEC X.500 DSA DOS-DE
DEC X.500 Admin LDAP
DIR.X maX.500
HP X.500 DD OSI Access & Dir
HP X.500 DUA QuickMailDUA
PathWay Messaging QUIPU
PC-Pages Traxis
QUIPU UCOM X.500
Traxis Xdi
Wang OPEN/services XT-DUA
XT-DUA XT-QUIPU
XT-QUIPU
RFC-1275
RFC-1006
OSI Access & Dir
Bull S.A. QUIPU
Custos
DEC X.500 DSA RFC-1276
DEC X.500 Admin
DIR.X OSI Access & Dir
Directory 500 QUIPU
LDAP XT-QUIPU
OSI Access & Dir
PathWay Messaging RFC-1277
PC-Pages
QUIPU DEC X.500 DSA
Traxis DEC X.500 Admin
UCOM X.500 DIR.X
Wang OPEN/services OSI Access & Dir
XT-DUA PathWay Messaging
XT-QUIPU QUIPU
UCOM X.500
RFC-1202 XT-DUA
XT-QUIPU
OSI Access & Dir
PathWay Messaging
RFC-1278 Sequent
DEC X.500 DSA
DEC X.500 Admin UCOM X.500
OSI Access & Dir
PathWay Messaging SNI
QUIPU
UCOM X.500 DIR.X
XT-DUA
XT-QUIPU Solbourne
RFC-1279 XT-DUA
XT-QUIPU
OSI Access & Dir
QUIPU Source
UCOM X.500
XT-QUIPU DE
LDAP
RFC-1484 MXLU
QUIPU
DE Xdi
DOS-DE XLU
*LDAP
*maX.500 Sun
QUIPU
Xdi Custos
XT-DUA Directory 500
XT-QUIPU LDAP
ldap-whois++
RFC-1485 OSI Access & Dir
PathWay Messaging
LDAP QuickMailDUA
maX.500 QUIPU
QUIPU Traxis
XT-QUIPU UCOM X.500
Xdi
RFC-1487 XT-DUA
XT-QUIPU
DE
DOS-DE Tandem
LDAP
ldap-whois++ UCOM X.500
maX.500
PC-DUA
QUIPU
UNIX
Custos
DE
ldap-whois++
MXLU
QUIPU
UCOM X.500
Xdi
XLU
Wang
Wang OPEN/services
X Window System
MXLU
OSI Access & Dir
Xdi
XLU
XT-DUA
X.25
Bull S.A.
DEC X.500 DSA
DEC X.500 Admin
DIR.X
Directory 500
HP X.500 DD
HP X.500 DUA
OSI Access & Dir
PathWay Messaging
QUIPU
Traxis
UCOM X.500
Wang OPEN/services
XT-DUA
XT-QUIPU3. Implementation Descriptions 🎀
okay so in the following pages you'll find descriptions of X.500 implementations, listed alphabetically 📚. If two implementations share a name, the name of the responsible organization goes in square brackets to tell them apart 💅. Heads up: throughout this section, the page header shows the name of the implementation, not the date of the document 🙈.
Every description follows the same format, and here's the breakdown:
- NAME: the name of the X.500 implementation plus the name of the responsible organization. If an implementation has a registered trademark, you'll see "(tm)" appended, like
GeeWhiz(tm)✨. - KEYWORDS: a list of the keywords defined in Section 2 that were used to cross-reference this implementation 🔥.
- ABSTRACT: a quick description of the application. This part may optionally include a list of the pilot projects where the application is being used 🌈.
- COMPLIANCE (only for DSAs and DUAs): a statement of compliance with the 1988 CCITT Recommendations X.500-X.521 [CCITT-88], specifically Section 9 of X.519, or with the 1988 NIST OIW Stable Implementation Agreements [NIST-88] 💜.
- CONFORMANCE WITH PROPOSED INTERNET STANDARDS: a statement of compliance with the several proposed Internet Standards 🦋.
- CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs: a statement of compliance with the several informational and experimental Internet RFCs 🌸.
- INTEROPERABILITY: a list of other DUAs and DSAs that this implementation can interoperate with 🫶.
- PILOT CONNECTIVITY: describes the level of connectivity it can offer to the pilot directory service running on the Internet in North America, and to pilots coordinated by the PARADISE project in Europe. The connectivity levels are: Not Tested, None, DUA Connectivity, and DSA Connectivity 🍓.
- BUGS: a warning about known problems and/or instructions on how to report bugs 😭.
- CAVEATS AND GENERAL LIMITATIONS: a warning about possible side effects or shortcomings, like a feature that works on one platform but not another 👑.
- INTERNETWORKING ENVIRONMENT: a list of environments where this implementation can be used, e.g., RFC-1006 with TCP/IP, TP0 or TP4 with X.25 ⭐.
- HARDWARE PLATFORMS: a list of the hardware platforms this application runs on, any extra boards or processors required, and any special suggested or required configuration options 🌈.
- SOFTWARE PLATFORMS: a list of the operating systems, window systems, databases, or unbundled software packages needed to run this application 💖.
- AVAILABILITY: a statement about whether the software is free or commercially available, a description of how to get it, and (optionally) a statement about distribution conditions and restrictions 🧚.
- DATE LAST UPDATED or CHECKED: the month and year when this implementation description was last modified 🎀.
NAME ✨
X500-DS X500-DUA Bull S.A.
KEYWORDS 💅
API, Bull, CLNS, Commercially Available, DSA/DUA, OSI Transport, RFC-1006, X.25
ABSTRACT 🔥
okay so X500-DS and X500-DUA are an integral part of the big Bull OSI offer 💼. They're based on the DCE/GDS (Distributed Computing Environment/Global Directory Service) of OSF, but these two products can be installed and used without a DCE environment 🌸. X500-DS is designed to implement both the DUA and the DSA functions, whilst X500-DUA only provides the DUA functions 🦋.
The X500-DUA package contains:
- The standards APIs XOM (X/Open OSI-Abstract-Data Manipulation API) and XDS (X/Open Directory Service API), for building portable applications 💖.
- A core DUA that translates all of the user's requests (bind, read, list, compare, modify, modifyRDN, search, add, remove, unbind ...) into the DAP protocol used to talk to distant DSAs 🧚.
- The OSI standard protocols (ASN.1, ROSE, ACSE, Presentation and Session) for communicating with the distant DSAs. The interface with the low layers of the stack is XTI. RFC-1006 is supported under XTI or the Session 🌈.
- A DUA Cache to improve performance when accessing remote DSAs ⭐.
- A management application for configuring the product, controlling operations, and managing logs and traces 👑.
- A user application for manipulating database entries 🍓.
The X500-DS package contains:
- All components of the X500-DUA 💜.
- A core DSA that processes all requests received from distant DUAs through the DAP protocol or from distant DSAs through the DSP protocol. It supports the referral, chained and multi-casting modes of operation, access control lists, simple authentication, and management of knowledge information (for distribution, shadows and copies of sub-trees) 🔥.
- A management application for managing schema information (creation, deletion and modification of object classes and of attribute types, and management of the rules of the DIT) 🫶.
- A C-ISAM database 🎀.
COMPLIANCE (applicable only for DSAs and DUAs) 💖
okay bestie, first up is the Bull one 🫶 it's compliant with the EWOS and OIW Agreements ✨
Strong authentication in X.509 is not yet implemented. The password scheme is what's used right now 🔐
It's a full DUA and DSA implementation that follows the 88 CCITT X.500 and ISO 9594 standard, and it ships with the X/Open XDS and XOM interface libraries too 📚 When it's installed with the DCE environment, XDS and XOM are also used to reach DCE/CDS (Local Cell Directory Service) transparently 🪄 A GDA (Global Directory Agent) acts as the gateway between the DCE CDS and GDS, so it's basically the bridge bestie 🌉
It's planned to support the full 1992 extensions in the products for 1995 🗓️
CONFORMANCE WITH PROPOSED INTERNET STANDARDS 🌸
[No information provided--Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 🦋
[No information provided--Ed.]
INTEROPERABILITY 🤝
this DAP and DSP implementation can interoperate with other X.500 implementations from other Cebit demo participants, including IBM, HP, ICL, Siemens-Nixdorf, etc. 💅 It also interoperates with ISODE QUIPU 🔥
PILOT CONNECTIVITY 🧚
[No information provided--Ed.]
BUGS 🙈
[No information provided--Ed.]
CAVEATS AND GENERAL LIMITATIONS 🍓
[No information provided--Ed.]
INTERNETWORKING ENVIRONMENT 🌈
the networking setup is giving a lot 😭 OSI TP4 with CLNP (WAN - LAN), OSI TP0, 2 & 4 with X.25 (WAN), and RFC-1006 with TCP/IP. You can use either BSD sockets or XTI to access the transports. Through XTI, both OSI and TCP/IP protocols are possible on the same machine, which means you can build a Directory Service spread across OSI and TCP/IP networks ✨
HARDWARE PLATFORMS 💻
DPX/2, DPX/20
SOFTWARE PLATFORMS 🖥️
Unix BOS2, Unix BOSX, AIX
AVAILABILITY 🎀
4 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.frDATE LAST UPDATE or CHECKED 📅
November 25th, 1993
NAME 🏷️
OSI Access and Directory Control Data Systems Incorporated.
KEYWORDS 🔑
API, CLNS, CDC, Commercially Available, DSA Connectivity, DSA/DUA, DUA Connectivity, DUA Interface, IBM PC, LDAP, RFC-1006, RFC-1202, RFC-1249, RFC-1274, RFC-1275, RFC-1276, RFC-1277, RFC-1278, RFC-1279, Sun, X Window System, X.25
ABSTRACT ✨
OSI Access and Directory includes several DUAs and a QUIPU based DSA (originally based on version 6.6) with enhancements. The DUA/DSA enhancements include:
- Directory API based on the X.400 API.
- Support for X.400 objects including those to support MHS use of Directory to support MHS Routing.
- Integration with Control Data's MailHub (X.400 MHS) products.
- X Windows, curses and command line based DUA interfaces on UNIX. These interfaces support the full set of Directory operations.
- Windows 3.x interface on PCs.
- A DUA daemon that provides Directory 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 and PH.X500 support.
- SNMP based monitoring and management of DSAs.
Control Data Systems offers complete integration services to design, plan, install, configure, tailor and maintain X.500 services. These services may include the preparation of customer unique DUAs and tools for X.500 integration, synchronization, operational control and management. OSI Access and Directory is in production use at several government, commercial and academic sites. Some sites are supporting Directories in excess of 120,000 entries 🚀
COMPLIANCE (applicable only for DSAs and DUAs) 💅
OSI Access and Directory complies with the 1988 CCITT Recommendations X.500-X.521 [CCITT-88] and the 1988 NIST OIW Stable Implementation Agreements [NIST-88]. It only supports simple authentication or no authentication. It also complies with all static and dynamic requirements of X.519, and it can act as a first-level DSA 🫶
OSI Access and Directory will support some 1993 X.500 extensions in 1994, with 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 RFCs 🦋
OSI Access and Directory is compliant with the following RFCs: [RFC 1202], [RFC 1249], [RFC 1275], [RFC 1278], and [RFC 1279].
It also supports the required objects, attributes and attribute syntaxes for MHS use of Directory to support MHS Routing 🧠
INTEROPERABILITY 🤝
OSI Access and Directory was tested against HP, DEC, ISODE Consortium and Wollongong implementations at the COS Interoperability Test Lab in May 1993. The OSINET Interoperability Tests were used. Please refer to OSINET for test results. It has also been informally tested at trade 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. It also provides the base routing tree for the MHS Use of Directory pilot (Longbud) on the Internet 🌍
BUGS 🙈
Control Data Systems provides complete software maintenance services with products 🛠️
CAVEATS and GENERAL LIMITATIONS 🍓
[No information provided--Ed.]
INTERNETWORKING ENVIRONMENT 🌈
RFC1006 with TCP/IP, TP4 with CNLS, TP0 with X.25.
HARDWARE PLATFORMS 💻
OSI Access and Directory runs on all MIPS and SUN SPARC platforms. Windows based DUAs available with OSI Access and Directory run on Windows 3.x compatible IBM PCs.
SOFTWARE PLATFORMS 🖥️
Distributed and supported for Sun OS version 4.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 available from:
Control Data Systems Inc.
Network Solutions, ARH290
4201 Lexington Avenue North
Arden Hills, MH 55126-6198 U.S.A.
1-800-257-OPEN (U.S. and Canada)
1-612-482-6736 (worldwide)
FAX: 1-612-482-2000 (worldwide)
EMAIL: info@cdc.com
or
s=info;p=cdc;a=attmail;c=usDATE LAST UPDATED or CHECKED 📅
November 22nd, 1993
NAME 🏷️
Custos National Institute of Standards and Technology
KEYWORDS 🔑
API, Available 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 of DUA library routines, a terminal interface, and a DSA. It was developed in C on Sun SPARCstations under SunOS 4.1.1. All underlying services are provided by the ISODE development package. That package is also used for encoding and decoding ASN.1 data, as well as for other data manipulation services. Using the 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 relational database system. The interface to the database system consists of a set of sql-like C functions. These are designed to allow straightforward replacement of the local database system with a more powerful commercial system. To achieve better performance, several options are supported that permit loading of selected portions of the database in core. When these options are selected, data can be retrieved more quickly from in core tables. All modifications to the DIB are directly reflected in the in core tables and the database 💜
COMPLIANCE (applicable only for DSAs and DUAs) 💅
Custos is fully compliant with the 1988 Standard, with the following omissions:
- Search request decomposition
- Modify Entry operation
- Modify RDN operation
- Abandon operation
- Strong Authentication
- Schema checking
There are no present plans to extend Custos to include the 1992 X.500 extensions 🥲
CONFORMANCE WITH PROPOSED INTERNET STANDARDS 🌸
[No information provided--Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 🦋
[No information provided--Ed.]
INTEROPERABILITY 🤝
Custos has successfully interoperated with QUIPU and OSIWARE over the DAP. No DSP interoperability testing has been done yet 👀
PILOT CONNECTIVITY 🧚
Limited DUA and DSA connectivity to PSI White Pages Project.
BUGS 🙈
Bugs may be reported to the general discussion list, x500@osi.ncsl.nist.gov.
CAVEATS and GENERAL LIMITATIONS 🍓
No limitations on file sizes, etc. The only side effects to creating large files should be in the area of performance. Specifically, optimization requires loading parts of the DIB in core, so greater memory requirements will be necessary for achieving better performance with a large database. Any platform the implementation can be ported to (generally any platform ISODE can be ported to) should support all features 🧩
INTERNETWORKING ENVIRONMENT 🌈
RFC-1006; TP4/CLNP (SunLinkOSI) over 802 and X.25 (SunLink X.25).
HARDWARE PLATFORMS 💻
It's only been run on Sun 3 and SPARC, but there are no known reasons why it shouldn't run on any hardware running the ISODE software 🤷♀️
SOFTWARE PLATFORMS 🖥️
It requires UNIX and the ISODE software package. It's been developed and tested with ISODE version 7.0 and Sun OS version 4.1.1. It uses a locally developed relational DBMS that should be easily replaceable with commercially available relational systems 💫
AVAILABILITY 🎀
Custos, the NIST implementation of X.500, the OSI Directory, is available for anonymous ftp from osi.ncsl.nist.gov (129.6.48.100) using the convention (user name = anonymous, password = ident). The software is available in two forms: a tar file and a compressed tar file.
./pub/directory/CustosRel_0.2.tar
./pub/directory/CustosRel_0.2.tar.ZNote: permissions on the directory ./pub/directory are set so that you will be able to "get" files whose names you can provide. However, you will not be able to "ls" the contents of the 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
The DEC X.500 Directory Server product is a high performance Directory System Agent. It's built to the 1993 edition of ISO/IEC 9594 and the CCITT X.500 series of Recommendations, so it's giving proper standards energy ✨
Here's what it can do 💅
- Integrated multi-protocol support, so DAP and DSP access run side by side over OSI and TCP/IP (using RFC1006) 🦋
- An indexed database for fast searching and sophisticated matching, including approximate match 🔥
- Based on the 1993 edition Extended Information Models 📚
- Support for chaining and referrals, so a distributed Directory Information Base works together 🌈
- Support for the 1993 edition Simplified Access Control scheme 🔐
- A configurable schema based on the 1993 edition (including attributes, object classes, structure rules, name forms) 🎀
- Support for a simple Shadowing protocol to boost read availability 💜
- Remote management facilities to configure and control DSAs and log significant events 🛠️
- The X/OPEN XDS/XOM Application Program Interface, so customers can build their own DUA applications 👑
For Directory User Agent facilities, check out the associated entry for the DEC X.500 Administration Facility 🧚
COMPLIANCE (applicable only for DSAs and DUAs)
Conformance with respect to clause 9.2 of ISO/IEC 9594-5:1993:
- Supports the
directoryAccessAC(DAP) anddirectorySystemAC(DSP) application contexts 🫶 - The DSA is capable of acting as a first-level DSA 🍓
- Chaining is supported 🔗
- Bind security levels of simple (unprotected password) and none are supported 🔓
- All attribute types defined in
ISO/IEC 9594-6:1993are supported, except for 1993 edition supertypes and collective attributes andEnhancedSearchGuide. Customers can define new attribute types.UNIVERSAL STRINGis not supported for attributes based onDirectoryString🙈 - All object classes defined in
ISO/IEC 9594-7:1993are supported. Customers can define new object classes 💖 - The following operational attributes are supported:
governingStructureRule
createTimestamp
modifyTimestamp
myAccessPoint
superiorKnowledge
supplierKnowledge
consumerKnowledge
specificKnowledge
dseType
PrescriptiveACI- Dynamic modification of object class is permitted ✨
- A subset of Simplified Access Control is supported 🌸
- All name forms defined in
ISO/IEC 9594-7:1993are supported. Customers can define new name forms and structure rules 🎀
The X.500 Directory Server is compatible with, and interworks with, 1988 edition DUAs and DSAs. It's implemented to conform to relevant NIST OIW and EWOS agreements and the X.500 Implementors Guide 📖
For details, contact Digital 💌
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
Supports RFC 1006, RFC 1274, and RFC 1277 💯
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
RFC 1278 🧁
INTEROPERABILITY
All interoperability test results will be available on request from Digital. Interoperability testing is being undertaken using the harmonized OSIone X.500 test suite, to which both OSInet and EurOSInet have been key contributors 🤝
PILOT CONNECTIVITY
Digital is actively involved in both public and private pilots of X.500 🌍
BUGS
[No information provided--Ed.]
CAVEATS and GENERAL LIMITATIONS
[No information provided--Ed.]
INTERNETWORKING ENVIRONMENT
The DEC X.500 Directory Service V1.0 operates over:
- RFC 1006 over TCP/IP on ULTRIX platforms 🌐
- OSI TP0, TP2 and TP4 over CLNS and CONS, as appropriate, on ULTRIX and OpenVMS platforms 🔌
HARDWARE PLATFORMS
The DEC X.500 Directory Service V1.0 runs on:
- VAX processors supported by OpenVMS 🖥️
- RISC processors supported by ULTRIX 💻
SOFTWARE PLATFORMS
The DEC X.500 Directory Service V1.0 runs on:
- OpenVMS/VAX V5.5-2 or 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 local Digital office, or:
Gail Shlansky, Product Manager:
Tel: +1 508 486 5138
email: gail.shlansky@lkg.mts.dec.com
Digital Equipment Corporation
Networks and Communications Engineering
550 King Street
Littleton, MA. 01460-1289
USADATE LAST UPDATED
August 2nd, 1993 🗓️
NAME
DEC X.500 Administration Facility Digital Equipment Corporation 🏷️
KEYWORDS
API, CLNS, Commercially Available, DEC ULTRIX, DEC VAX OpenVMS, DUA Only, Motif, OSI Transport, RFC-1006, RFC-1274, RFC-1277, RFC-1278, X.25 🔑
ABSTRACT
The DEC X.500 Administration Facility product gives you both a command line and a Motif interface for managing the information stored in the X.500 directory. It's giving full control 🫧
Here's what it brings to the table:
- Multi-protocol support, so DAP access works over OSI and TCP/IP (using RFC1006) 🌸
- It's driven off the same configurable schema information as the DEC X.500 Directory Service 💅
- It supports command line and OSF Motif interface styles 🎀
- It provides access to all X.500 services 🔥
Specific features of the OSF Motif interface include:
- Two ways of accessing directory information: browsing the directory tree, or searching 🌳
- Easy-to-use search based on a customer-extensible set of predefined filters 🔍
- Window layouts and text that are fully extensible, based on the schema, so they support customer-defined object classes and attributes 🪟
- An easy-to-use, forms-based method for creating and modifying entries, which simplifies use of the X.500 services 📝
See also the entry for the DEC X.500 Directory Service 🧚
COMPLIANCE (applicable only for DSAs and DUAs)
Conformance with respect to clause 9.1 of ISO/IEC 9594-5:1993:
- Supports all operations of the
directoryAccessACapplication context 🫶 - Bind security levels of none and simple (unprotected passwords) 🔓
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
Supports RFC 1006, RFC 1274, and RFC 1277 💯
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
RFC 1278 🧁
INTEROPERABILITY
Interoperability test results will be available on request from Digital. Interoperability testing is being undertaken using the harmonized OSIone X.500 test suite, to which both OSInet and EurOSInet have been key contributors 🤝
PILOT CONNECTIVITY
Digital is actively involved in both public and private pilots of X.500 🌍
BUGS
[No information provided--Ed.]
CAVEATS and GENERAL LIMITATIONS
[No information provided--Ed.]
INTERNETWORKING ENVIRONMENT
The DEC X.500 Administration Facility operates over:
- RFC 1006 over TCP/IP on ULTRIX platforms 🌐
- OSI TP0, TP2 and TP4 over CLNS and CONS, as appropriate, on ULTRIX and OpenVMS platforms 🔌
HARDWARE PLATFORMS
The DEC X.500 Administration Facility V1.0 runs on:
- VAX processors supported by OpenVMS 🖥️
- RISC processors supported by ULTRIX 💻
SOFTWARE PLATFORMS
The DEC X.500 Administration Facility V1.0 runs on:
- OpenVMS/VAX V5.5-2 or 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 Facility is commercially available from Digital Equipment Corporation. For further information, please contact your local Digital office, or:
Gail Shlansky, Product Manager:
Tel: +1 508 486 5138
email: gail.shlansky@lkg.mts.dec.com
Digital Equipment Corporation
Networks and Communications Engineering
550 King Street
Littleton, MA. 01460-1289
USADATE LAST UPDATED
August 2nd, 1993 🗓️
NAME
DIR.X (tm) V3.0 Siemens Nixdorf Informationssysteme AG 🏷️
KEYWORDS
API, CLNS, Commercially Available, DSA Connectivity, DSA/DUA, DUA Connectivity, HP, IBM RISC, OSI Transport, RFC-1006, RFC-1277, SNI, X.25 🔑
ABSTRACT ✨
okay bestie, Directory 500 (D500) is a comprehensive implementation of the CCITT X.500 recommendations 💅 it's built from two major components that handle the data in the OSI Directory: the Directory User Agent (DUA) and the Directory System Agent (DSA) 🫶
The DUA is the interface between the OSI Directory and the people who want to access its information. Users make their requests through the DUA 💖 When the DUA forwards those requests to the OSI Directory, the protocol it uses is the Directory Access Protocol (DAP) ✨
The DSA negotiates with other, remote DSAs to get requested information or to update remote DIBs 🦋 DSAs use the Directory System Protocol (DSP) to forward and answer these requests. The DSA also supports chaining and referrals. iconic 👑
COMPLIANCE (applicable only for DSAs and DUAs)
All X.500 1988 operations are supported 💅 along with all Object Classes specified in X.521 and all Attribute Types specified in X.520 🎀
Implementation plans include upgrades to support the 1992 extensions to X.500 in 1994 🌸 Please check with OSIware / Infonet Software Solutions for availability dates, because they're the ones who know 🧚
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
[No information provided--Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
[No information provided--Ed.]
INTEROPERABILITY
Tested with QUIPU ✨ Other interoperability information is not available at this time 🙈
PILOT CONNECTIVITY
[No information provided--Ed.]
BUGS
None known at this time 🌈
CAVEATS and GENERAL LIMITATIONS
None known at this time 💜
INTERNETWORKING ENVIRONMENT
RFC1006 with TCP/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 Version 7 required) 🍓
AVAILABILITY
Directory 500 is commercially available as executable object code or as source code form from:
OSIware / Infonet Software Solutions
4400 Dominion Street, Suite 210
Burnaby, BC V5G 4G3
CANADA
Sales & Information: 604436-2922
Fax: 604/436-3192DATE 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, RFC-1484, RFC-1487
ABSTRACT
DOS-DE (DOS Directory Enquiries) is meant to be a simple-to-use DUA interface for the naive user 🌼 It's an MS-DOS port of the standard UNIX DE implementation. See the entry on DE for full details. (All of the features of DE are supported apart from the experimental `Quality of Service' code.)
The user is shown a series of (verbose) prompts asking for the person's name, department, organization and country. There's extensive on-line help 🧸 The matching algorithms are set up so near matches are shown to the user before less good matches. `Power searching' is also available. This lets a user search for an entry even when they don't know the name of the organisation the person works for. You still have to specify the country. DOS-DE provides UFN style searching, and it's also possible to search locality entries 🔍 DOS-DE uses slightly different search algorithms depending on whether it's accessing part of the Directory mastered by a Quipu DSA, because Quipu DSAs tend to use lots of replication and so encourage searching 🫧
DOS-DE runs over the University of Michigan LDAP 💖
DE was funded by the COSINE PARADISE project. DOS-DE was developed by Andy Powell at the University of Bath 🎓
COMPLIANCE (applicable only for DSAs and DUAs)
N/A
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
[RFC 1484].
INTEROPERABILITY
N/A
PILOT CONNECTIVITY
N/A
BUGS
Doesn't handle aliases well when power searching 🙈
Send bug reports to:
A.Powell@bath.ac.uk
CAVEATS and GENERAL LIMITATIONS
DOS-DE tries to cater well for the general case, at the expense of not dealing with the less typical. The main manifestation of this is that the current version doesn't handle searching under localities very well 😭
It's not possible to display photographs or reproduce sound attributes 📸
INTERNETWORKING ENVIRONMENT
University of Michigan LDAP.
HARDWARE PLATFORMS
IBM PC/AT/XT and compatibles 💻
SOFTWARE PLATFORMS
LDAP for MS-DOS running over the NCSA Telnet stack, or SUN's PCNFS version 4.1, or Novell's LAN Workplace (LWP) 🌸
AVAILABILITY
The software is openly available by FTP from ftp.bath.ac.uk, as pub/x500/dosde.zip. 📂
The very latest code will be made available with the ISODE Consortium release of ISODE. It's 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 Directory Products Hewlett Packard
KEYWORDS
API, CLNS, Commercially Available, DSA/DUA, DUA only, HP, OSI Transport, X.25 💼
ABSTRACT
HP X.500 Distributed Directory. Its main components are:
DUA, and DUA Interface,
DSA and DIB support,
X.500 Address Lookup,
X/Open Application Tool Kit API (XAT) for XDS/XOM Interface,
X.500 High Level API (X5HLAPI) for XDS/XOM Interface.HP X.500 DUA. Its main components are:
DUA, and DUA Interface,
X.500 Address Look-up,
X/Open Application Tool Kit API (XAT) for XDS/XOM Interface,
X.500 High Level API (X5HLAPI) for XDS/XOM Interface.HP X.500 Distributed Directory is based on the 1988 CCITT X.500 standard 🎀 HP X.500 can be used for accessing names and electronic mail addresses for multi-vendor messaging backbone networks. It can also be used for developing networked applications that need distributed directory functionality ✨
HP OpenMail users can access the enterprise-wide HP X.500 distributed directory directly from the HP OpenMail user interface, and select X.500 addresses for mailing 💌 HP-UX Sendmail users can access electronic mail addresses from an X.500 server over a TCP/IP network 🦋
Users of non-HP e-mail systems can access data stored in the X.500 Directory using X.500 Address Look-up. X.500 Address Look-up has an easy-to-use interface and phonetic search capability 🔤
HP X.500 Distributed Directory includes a complete multi-threaded DUA and DSA 🧵 The X.500 DIB is built on a database that has been optimized for X.500 performance. HP X.500 contains full support for DAP and DSP protocols 💅
Data Shadowing and security access control of HP X.500 Distributed Directory allow higher performance and easier management of its DIB database in a global environment 🌍
HP X.500 Distributed Directory has menu-driven administration and user interface tools 🖱️ The tools simplify directory configuration and data retrieval. It supports X/Open X.500 APIs (XDS and XOM), plus high-level APIs on top of XDS so developers can write their own X.500-based applications 👑
HP X.500 Distributed Directory supports comprehensive tracing and logging facilities for quick diagnosis and resolution of problems. HP also provides a rich set of troubleshooting tools to check the interoperability of the network at various layers of the OSI stack 🛠️
COMPLIANCE (applicable only for DSAs and DUAs)
HP X.500 Distributed Directory complies with the 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 Specifications
*x.509 describes simple and strong authentication. HP X.500
Distributed Directory supports simple authentication. Strong
authentication is not supported in the current release due to
limited market demand.HP X.500 Distributed Directory will comply with NIST and EWOS directory functional profiles 📋 Based on factors such as market needs and NIST recommendations, HP will implement subsets of 1992 CCITT functionality in a phased approach 🌈
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
[No information provided--Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 🎀
Okay so the U-M LDAP one has preliminary support for [RFC 1484] baked in 🧚. It's a baby step, but it counts!
INTEROPERABILITY 🔥
The LDAP server (current implementation) is known to work with the QUIPU DSA and DAP library. Iconic pairing, no cap 💅
PILOT CONNECTIVITY 🌈
DUA connectivity should be possible to all pilots 🦋 Only AARNET, PARADISE, and PSI White Pages Project have actually been tried, though, so that's the honest tea.
BUGS 🐞
Bug reports go to bug-ldap@umich.edu 💌
CAVEATS and GENERAL LIMITATIONS 💀
None, aside from those mentioned above under completeness. Lowkey the only catch is what we already talked about 🫶
INTERNETWORKING ENVIRONMENT 🌸
LDAP clients use TCP to talk to the LDAP server ✨ The LDAP server normally uses RFC 1006 with TCP/IP to talk to the DSA, though any other transport mechanism for DSA communication supported by ISODE should be possible. The way that flexibility just slays 💅
HARDWARE PLATFORMS 💜
The LDAP server is known to run on Sun 3 and Sun 4 platforms, DEC's, HP's, and RS 6000's 🍓 The LDAP client libraries and some clients have been ported to the Macintosh and the PC.
SOFTWARE PLATFORMS 👑
The LDAP server and clients are known to run under SunOS 4.1.x, ULTRIX, HP-UX, and AIX. The LDAP client libraries also work under Macintosh System 6.0 or higher and MS-DOS 5.0. Main character energy for real 😭
AVAILABILITY ⭐
This software is openly available, bestie 🎀 You can grab it with anonymous FTP from terminator.rs.itd.umich.edu in the x500 directory. Documentation on the LDAP and lightweight BER libraries comes as man pages distributed with the source code. For more info, hit up ldap-support@umich.edu 💌
This software was developed at the University of Michigan by Tim Howes with help from Mark Smith and Bryan Beecher, as well as many others around the Internet. It is subject to the following copyright:
Copyright (c) 1993 Regents of the University of Michigan. All rights reserved. Redistribution and use in source and binary forms are permitted provided that this notice is preserved and that due credit is given to the University of Michigan at Ann Arbor. The name of the University may not be used to endorse or promote products derived from this 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, UNIX
ABSTRACT ✨
ldap-whois++ is a dua interface that implements the IETF WNILS draft whois++ proposal using the LDAP libraries developed by the University of Michigan. Two things, one slay 🦋
COMPLIANCE (applicable only for DSAs and DUAs) 🙈
N/A
CONFORMANCE WITH PROPOSED INTERNET STANDARDS 🌟
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 🌷
IETF WNILS WG Whois++ Architecture Draft.
INTEROPERABILITY 🫧
N/A
PILOT CONNECTIVITY 🌐
There are a number of servers running across the Internet.
BUGS 🪲
None reported. Honestly iconic behaviour 🥹
CAVEATS and GENERAL LIMITATIONS ⚠️
Based on an early draft of the Whois++ Architecture Document, so there may be some inconsistencies with the latest draft. Be aware of that, babe 🫶
It is considered a "beta" release due to the volatility of the whois++ work. Once there is a whois++ RFC, then a real release will be made. Not me saying "beta" like it's a whole vibe 💅
INTERNETWORKING ENVIRONMENT 🌙
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 as pub/whois/whois++beta.tar.Z.
DATE LAST UPDATED or CHECKED 🗓️
August 3rd, 1993
NAME 🍎
University of Michigan maX.500 Macintosh DUA Interface
KEYWORDS 🏷️
Available via FTP, DUA Connectivity, DUA Interface, Free, LDAP, Macintosh, RFC-1274, RFC-1484, RFC-1485, RFC-1487
ABSTRACT ✨
maX.500 is a Directory User Agent for Apple Macintosh. It is currently at version 2.0, which uses the Lightweight Directory Access Protocol (LDAP) over TCP/IP to access The Directory. maX.500 can be used to search for, view, create, delete, and modify entries. It supports viewing of textual information, playing of audio, and viewing of black and white (fax) and color (JPEG) images. 📸
maX.500 is a native Macintosh application, and as such has a friendly interface. It requires System Software version 6.0.5 or later and Apple's MacTCP control panel. Friendly UI era 🫶
COMPLIANCE (applicable only for DSAs and DUAs) 🧾
maX.500 works over LDAP, and is subject to LDAP's limitations. The X.500 bind, search, compare, add, 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 🎯
Compliant with [RFC 1485], [RFC 1487], and [RFC 1274].
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 🌱
Preliminary support is included for [RFC 1484] (same as U-M LDAP).
INTEROPERABILITY 🤝
maX.500 2.0 is known to work with the U-M LDAP server. It has been used successfully with the QUIPU DSA and others. Team player 🫶
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 and GENERAL LIMITATIONS 💀
maX.500 does not support modification of "photo" (fax), "jpegPhoto", or "audio" attributes. Modify RDN is also unsupported. Not gonna lie, that's a lil sad 🥺
INTERNETWORKING ENVIRONMENT 🌸
maX.500 is an LDAP client, and as such uses TCP to communicate with the LDAP server. Apple's MacTCP control panel is required on the Macintosh.
HARDWARE PLATFORMS 🍎
maX.500 runs on Apple Macintosh Plus or later computers. It requires 1MB of RAM.
SOFTWARE PLATFORMS 💜
maX.500 requires Apple System Software 6.0.5 or later (System 7 preferred) and MacTCP 1.1 or later (1.1.1 preferred). Pick the newest, periodt 💅
AVAILABILITY ⭐
This software is openly available. It may be obtained by anonymous FTP from terminator.rs.itd.umich.edu in the x500 directory. More information can be obtained from ldap-support@umich.edu 💌
This software was developed at the University of Michigan by Mark Smith with help from Tim Howes and many others around the Internet. It is subject to the following copyright:
Copyright (c) 1993 Regents of the University of Michigan. All rights reserved. Redistribution and use in binary forms is permitted provided that this notice is preserved and that due credit is given to the University of Michigan at Ann Arbor. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. This software is provided ``as is'' without express or implied warranty.
DATE LAST UPDATED OR CHECKED 📅
July 26th, 1993
NAME 🏫
MXLU Brunel University, UK
KEYWORDS 🏷️
DUA Connectivity, DUA Only, Free, Motif, Multiple Vendor Platforms, Needs ISODE, Source, UNIX, X Window System
ABSTRACT ✨
MXLU (Motif/X LookUp) is an X.500 DUA interface for the X Window System using Motif.
Ported from the Athena widgets version, MXLU can be configured for many different styles of interaction. Example configurations are provided for single window and multiple window use. 🪟
MXLU implements the `User-Friendly Naming' search strategy and also has a form-filling search mode. Asynchronous directory operations are used. 🔍
Full user friendly add and modify functions are provided, with the ability to tailor the modify screen 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 DSAs and DUAs) 🧾
88 Standard compliant: Strong authentication not yet implemented. No plans for support of the 1992 Standard.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS 🎯
No plans at present.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 🌱
No plans at present.
INTEROPERABILITY 🤝
Tested with ISODE-8.0
PILOT CONNECTIVITY 🦋
DUA Connectivity: The interface is in use in the UK Academic Directory Pilot.
BUGS
okay bestie, bug reports go to prod-eng@twg.com 📮✨ the entry literally says "Send bug reports to:" so that's your inbox 💅
CAVEATS and GENERAL LIMITATIONS
nothing to see here 🙈 the entry just says [No information provided--Ed.]
INTERNETWORKING ENVIRONMENT
the networking lineup is giving 🦋 RFC1006 with TCP/IP, TP4 with CNLS, TP0/2 or TP4 with X.25.
HARDWARE PLATFORMS
PathWay Messaging Services runs on all models of Sun SPARC and generic 386/486 systems. PathWay Messenger (the email app with the lightweight DUA) also runs on Macintosh, and 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 commercially available from:
The Wollongong Group, Inc.
1129 San Antonio Road
Palo Alto, CA 94303 USA
Sales and Information: (415) 962 7100
FAX: (415) 969-5547DATE LAST UPDATED or CHECKED
July 27th, 1993 📅
NAME
PC-DUA NEXOR
KEYWORDS
386, Commercially Available, DUA Connectivity, DUA Interface, IBM PC, LDAP, RFC-1487
ABSTRACT
PC-DUA gives you a MS Windows based user interface to the X.500 Directory. it's so pretty 🎀
Features include:
- Searching 🔍
- Directory Browser - to enable user to identify directory entry
- History - allowing quick access to previously referenced parts of the DIT.
- User Friendly Name (UFN) based searching
- Hypertext-like navigation.
- Friendly names for attribute labels.
- Intelligent choice of entries to display when moving to a new location in the DIT.
- O-line hypertext help.
COMPLIANCE (applicable only for DSAs and DUAs)
Compliant with LDAP ✨
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
The following are supported: RFC 1487 🦋
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
[No information provided--Ed.] 🙈
INTERACTIVE INTEROPERABILITY
PC-DUA has interoperated with LDAP 2.0 and 3.0 beta distributions 🤝
INTEROPERABILITY
PC-DUA has interoperated with LDAP 2.0 and 3.0 beta distributions 🤝
PILOT CONNECTIVITY
Full DUA connectivity to the PARADISE and PSI White Pages X.500 Pilots. 🌈
BUGS
No known bugs, periodt 💅 Support is given via phone or email to "support@nexor.co.uk"
CAVEATS and GENERAL LIMITATIONS
None. 💖
INTERNETWORKING ENVIRONMENT
WinSock based TCP/IP stacks
HARDWARE PLATFORMS
386 PC WITH 4MGBYTES RAM
SOFTWARE PLATFORMS
MS WINDOWS 3.1
AVAILABILITY
PC-DUA is commercial software. For more details contact:
NEXOR
8 Faraday Building
Highfields Science Park
Nottingham
NG7 2QP
UK
DN: c=GB@o=NEXOR Ltd
Telephone: +44 602 520500
Fax: +44 602 520519
E-Mail: sales@nexor.co.ukDATE 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 based X.500 DUA interface. 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 Name (UFN) specification (RFC 1484).
- Powerful query engine.
- Tailorable entry display - display only those attributes required.
- Integrates with the WhiteMail X.400 user agent. Hooks are provided to allow 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 of PC-Pages are currently available. One supports DAP over CONS or DAP over RFC-1006, and has data entry and modification facilities. The other supports LDAP and has a more advanced user interface including a tree-browser, but does not yet have data entry and modification.
A version in the form of a Windows DLL (Dynamic Link Library) is being prepared, for incorporation into other products such as mail agents. 🧚
COMPLIANCE (applicable only for DSAs and DUAs)
88 Standard compliant: Strong authentication not yet implemented. No plans for support of the 1992 Standard.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
[No information provided--Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
[No information provided--Ed.]
INTEROPERABILITY
Tested with Quipu 8.0 🫶
PILOT CONNECTIVITY
DUA Connectivity: The interface is in use in the UK Academic Directory Pilot. 🎓
BUGS
Bugs should be reported to x500@brunel.ac.uk.
CAVEATS and GENERAL LIMITATIONS
Does not support display or modification of all known attribute syntaxes. In particular: ACLs and O/R addresses.
INTERNETWORKING ENVIRONMENT
RFC1006 with TCP/IP. TP4 with CONS. A NetBIOS gateway to the previously listed protocols. LDAP using Winsock.
HARDWARE PLATFORMS
PC-Pages for Windows requires an IBM PC compatible with 286 or higher, 2mb+ memory.
SOFTWARE PLATFORMS
Windows 3.0 or 3.1 running in Standard or Enhanced mode. WhiteStack 1.1, provided by the Edinburgh University Computing Service.
AVAILABILITY
Free to UK Academic Community, and to some other communities subject to certain restrictions. Commercial derivatives exist. Please send queries to:
Postal:
Andrew Findlay
Computing and Media Services
Brunel University
Cleveland Road
Uxbridge, Middlesex
UB8 3PH
UK
E-mail: x500@brunel.ac.uk.
Fax: +44 895 32806 (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, Needs ISODE, RFC-1274, Sun
ABSTRACT
The NASA QuickMail/X.500 Interface program is a program which translates QuickMail name service requests into X.500 requests and returns the results from the DSA 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. The program speaks QuickMail name service protocol on one side, and DAP on the other. 🛰️
COMPLIANCE (applicable only for DSAs 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 provided schema to store QuickMail addresses.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
[No information provided--Ed.]
INTEROPERABILITY
Works with Quipu (ISODE 8.0, ICR1) 🤝
PILOT CONNECTIVITY
Connected to PSI WPPP, PARADISE. Other projects may use 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 and GENERAL LIMITATIONS
Requires the Columbia AppleTalk Package (CAP 6.0) to work.
INTERNETWORKING ENVIRONMENT
EtherTalk or IPTalk on the Macintosh side, any ISODE supported environment on the X.500 side.
HARDWARE PLATFORMS
Known to run on Sun 4/470
SOFTWARE PLATFORMS
SunOS 4.1.1 and 4.1.3 can be used to host the package. Additionally may need SunLink OSI 7.0.1, Sunlink X.25 7.0. ISODE 8.0 or ISODE Consortium Release 1 needed to provide DAP support.
AVAILABILITY
Limited availability. For more details contact,
Peter Yee
MS 233-18
NASA Ames Research Center
Moffett Field, CA 94035-1000
(415) 604-3812
(415) 604-6999 (FAX)
yee@atlas.arc.nasa.govDATE LAST UPDATED or CHECKED
February 18th, 1993 🚀
NAME
QUIPU (ISODE Consortium Release 1.0) ISODE Consortium
KEYWORDS
API, DSA Connectivity, DSA/DUA, DUA Connectivity, Free, Multiple Vendor Platforms, OSI Transport, RFC-1006, RFC-1274, RFC-1275, RFC-1276, RFC-1277, RFC-1278, RFC-1279, RFC-1484, RFC-1485, RFC-1487, Source, Sun, UNIX, X.25
ABSTRACT
This implementation is a source release derived from the earlier openly available version of QUIPU, and will be used as base technology for products by a number of vendors. The release comprises of a DSA, and a number of sample DUAs which may be used in conjunction with the DSA. 💜
COMPLIANCE (applicable only for DSAs and DUAs) 💖
okay so the DSA is lined up with the 1988 ISO IS and the NIST OIW Directory Implementors Guide Version 1, but there are a few exceptions, bestie 🙈
- Strong authentication is not implemented (but hooks are provided for use with two packages).
- QUIPU does not enforce the bounds constraints on attributes, filters or APDU size.
- T.61 string formatting characters are not rejected.
- If a DN is supplied with no password in an unprotected simple bind, QUIPU does not always check to see if 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 check the DN, the bind IS allowed.
- When comparing attributes of UTCtime syntax, if the seconds field is omitted, QUIPU does not perform the match correctly (i.e., the seconds field in the attribute values should be ignored, but are not).
- QUIPU always supplies the optional Chaining argument
originatoreven if the CommonArgumentrequestoris used. - QUIPU always supplies the optional Chaining argument
targeteven if the base object in the DAP arguments is the same. - The object class "without an assigned object identifier" is not recognised unless the
aliasobject 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, with the exception of DOB, but including security features will be available ✨
CONFORMANCE WITH PROPOSED INTERNET STANDARDS 🎀
[RFC 1485], [RFC 1487], [RFC 1274], [RFC 1276], [RFC 1277].
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 🦋
[RFC 1484], [RFC 1275], [RFC 1278], [RFC 1279].
INTEROPERABILITY 🫶
Interoperability with several other DSAs has been demonstrated in pilot operation and at the COS X.500 Interoperability Lab, enhancing interoperability results from the earler versions of QUIPU. 👑
PILOT CONNECTIVITY 🌈
Connectivity to the global research pilot (PARADISE etc.) has been demonstrated. It is expected that this system will be used extensively in a wide range of pilot activities. DUA Connectivity, and DSA Connectivity.
BUGS 🐛
Bugs should be reported to <bug-quipu@isode.com> 💅
CAVEATS and GENERAL LIMITATIONS 🧚
None
INTERNETWORKING ENVIRONMENT 🌐
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 transport, which may be any class and use any network service. TLI, 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 is SUNOS 4.1.3. It is also known to run on various other UNIX platforms.
AVAILABILITY 🎁
Available to members of the ISODE Consortium. Membership is open to any organisation. Also available under licence (zero cost) to all non-commercial research organisations. Contact:
ISODE Consortium
Headquarters
PO Box 505
London
SW11 1DX
UK
Phone: +44-71-223-4062
Fax: +44-71-223-3846
Email: <ic-info@isode.com>DATE LAST UPDATED or CHECKED 📅
August 11th, 1993
NAME 🏷️
Traxis Enterprise Directory Angeli Systems Corporation
KEYWORDS 🔑
API, CLNS, Commercially Available, DSA/DUA, HP, IBM PC, IBM RISC, Macintosh, OSI Transport, RFC-1006, RFC-1274, Sun, X.25
ABSTRACT ✨
okay the Traxis Enterprise Directory has multiple components in a three layer architecture, and the individual components of the Traxis family are building blocks you can put together in a flexible, modular way to build complex systems. It's giving LEGO, but make it networking 🧱
At the enterprise level, there is a distributed directory stored and managed by Traxis Directory Engines (TDEs). At the workgroup level, Traxis Directory Hubs (TDHs) provide the means to integrate and connect Traxis Directory Engines to the wide variety of real world applications and systems which prevail in network environments. The TDE and the TDH support the myriad of client applications, including messaging and business applications, which 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, and results management as required between the Traxis Directory Hub and applications. These capabilities, which include full access and management of the directory, are provided to applications through XDS++, the Traxis object oriented API. The Traxis Desktop Client also supports industry standard client software interfaces such as Microsoft MAPI, Apple OCE, CMC and VIM, through Compatibility Modules which map the standard API into XDS++. Through these APIs the Traxis Desktop Client supports applications of all kinds on PC, Macintosh, 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 Gateway, the Traxis Import Export Utility and more. 🌸
The Traxis Directory Engine includes an X.500 DSA. The Traxis Directory Hub includes an X.500 DUA. 🦋
COMPLIANCE (applicable only for DSAs and DUAs) 💖
Traxis Directory Engine DSA is CCITT-1988 compliant with extended security and access control. It supports access control on User, Entry, and Attribute levels. DIB or subtree administrative manager supported. It supports simple authentication with encrypted password.
NIST OIW Stable Implementation Agreements [NIST-88] compliant. 🔥
Support for February 14, 1993 CCITT X.500 planned. X.509 in first half of 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 RFCs 🦋
Traxis does not conform to the QUIPU RFC Internet Proposals cited. As noted elsewhere, Traxis is fully compatible with QUIPU operationally but does not use the cited RFCs in its internal operations. 🫶
INTEROPERABILITY 🫶
Traxis has been extensively tested for interoperability with ISODE QUIPU Version 8. The Traxis Directory Engine (DSA) will serve DISH or other QUIPU DUAs using DAP. Traxis Directory Hub interoperates with QUIPU DSA. All directory access functions and their chained equivalents are interoperable. 👑
PILOT CONNECTIVITY 🌈
PARADISE DUA/DSA connectivity tested. ⭐
BUGS 🐛
Problems may be reported to support@angeli.com.
CAVEATS and GENERAL LIMITATIONS 🧚
None.
INTERNETWORKING ENVIRONMENT 🌐
Traxis Directory Hub to Traxis Directory Engine (or any DSA) communication via RFC1006 over TCP/IP, OSI TP4 with CLNS, and OSI TP0 with X.25. Traxis Desktop Client to Traxis Directory Hub via SPX/IPX or TCP/IP. Other LAN protocols supported in 1994. 🌍
HARDWARE PLATFORMS 💻
Traxis Directory Hub and Traxis Directory Engine: Sun and PC currently supported. IBM RS/6000, HP 9000, and others in 1994.
Traxis Desktop Client and applications: PC currently supported; Macintosh in 1994.
SOFTWARE PLATFORMS 🍓
Traxis Directory Hub and Traxis Directory Engine: All Sun platforms with Sun OS 4.1.3 currently supported, Solaris 2.x in 1994. Industry standard PC platforms with SCO Open Desktop V3 currently supported. Other UNIX platforms in 1994. Windows NT in 1994.
Traxis Desktop Client and applications: PC with Windows 3.1 currently supported. Macintosh Systems 6 and 7, UNIX Motif, DOS, X Windows, and others planned for 1994.
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.comDATE LAST UPDATED or CHECKED 📅
November 23rd, 1993
NAME 🏷️
UCOM.X 500 (tm) - E3.X [DSA and DUA]
KEYWORDS 🔑
386, API, Bull, CLNS, Commercially Available, DEC ULTRIX, DSA Connectivity, DSA/DUA, DUA Connectivity, IBM RISC, 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 500 is a product based on PIZARRO, the research prototype developed at INRIA by Christian Huitema's team, and commercialized by 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 maintained in ASN.1 encoded format in the Unix file system. Utilities are provided to load and dump the DIB from and to ASCII 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 managed domains is stored in UCOM.X specific attributes of the DSA entries.
- Schema: The X.500 (88), X.400 (88) and most of the Cosine and Internet Schema are supported. Object class and attribute definitions are enforced. Users may define their own.
- Simple authentication is provided; strong authentication and signed operations are being tested operationally through TS-E3X's participation in PASSWORD, a VALUE project with aim to pilot a European security infrastructure for network applications.
- Access control: private mechanisms are provided to allow access control lists to be specified for parts of the DIT, to control modifications, and to 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 and periodically update the database from various data sources including a knowledge discovery tool.
The product offers a C language API conformant to X/Open's X/DS specification, and a C++ API (for release 10/93). 💜
The DUAs include a graphical directory browser with powerful search 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 offer it to third parties developing specific applications using X.500: current applications include a distributed application to control document transfer in a large French hospital and distributed applications management in the French Post Office; planned uses include office applications for control of document circulation (workflow) and cooperative document editing. Thirdly, to offer it to telecomms operators such as France Telecom for application in network management. UCOM.X 500 is used extensively by French research centers involved in PARADISE. 🚀
COMPLIANCE (applicable only for DSAs and DUAs) 💅
Okay so this one only applies to DSAs and DUAs, bestie 🫶. UCOM.X 500 conforms to X.500 (88) as specified in paragraph 9 of X.519 ✨
Development of the X.500 (93) product is planned for '94, with a release conformant to the principal extensions at the end of '94 🌸. The focus is on the shadowing protocol, the schema and access control. It's giving roadmap energy 🗺️
CONFORMANCE WITH PROPOSED INTERNET STANDARDS 🎀
The COSINE and Internet Schema (RFC 1274) is supported with minor exceptions 💜.
The string representation of PSAPs and their internal encoding conforms to RFC 1277 ✨.
The string representation of DNs will migrate to the Internet RFC 1485 definition 🦋.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 🌈
RFC 1279 (X.500 and Domains) is supported. The string representation of PSAPs and their internal encoding conforms to RFC 1278 💅.
AFRO (algorithme francais de recherche optimise) is the search and name resolution algorithm proposed by UCOM.X 500. It differs from the UFN algorithm mainly because it tries to optimize by doing read operations before it resorts to searches, so it can make use of the name error information 🧚. Smart, right? 🙈
INTEROPERABILITY 🔥
Through UCOM.X 500's use in the French PARADISE pilot, interoperability has been informally but extensively tested with Quipu and other implementations 💖.
Detailed interoperability tests with Quipu, Marben and Siemens/Bull DIR/X are being run by the PARADISE OIFP (Operational Interworking) team at INRIA Rocquencourt, France 👑.
The product is also currently 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, so it's supported and bugs get fixed when they're detected 💅. Bug reports can be sent to the support team by electronic mail 💌.
CAVEATS AND GENERAL LIMITATIONS ⚠️
The DIT structure and inverted attribute tables are stored in main memory. The recommended main memory size for a DSA is 1 kb per node, i.e., 10 Mb for a database of 10,000 objects. The current recommended maximum is a database size on the order of 100,000 objects 🍓.
Of the selected attribute types defined in X.500 (88), the searchGuide attribute is not supported 🙅♀️. Neither are these attributes from the Cosine and Internet Schema (RFC 1274): OtherMailbox, MailPreferenceOption and the various quality attributes 💀.
The X/DS API supports the Basic Directory Contents (BDCP), the MHS Directory User (MDUP) and the Strong Authentication (SAP) packages, with minor limitations 🌸. A proprietary mechanism for defining new classes and attributes is offered. Asynchronous operations and multiple concurrent sessions are not supported 😭. Referral may be handled automatically, but continuation references are not 🔥.
INTERNETWORKING ENVIRONMENT 🌐
UCOM.X 500 includes a transport stack for TP0 with TCP/IP (RFC 1006) and X.25. The stack has been ported to SunNet OSI for TP4 with CLNP 🦋.
HARDWARE PLATFORMS 💻
UCOM.X 500 can easily be ported to any UNIX machine ✨. It currently runs on: Sun 3 and 4, IBM RS 6000, 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 has been ported to: UNIX SVR3 and SVR4, SUN OS 4, AIX, SCO Unix, Interactive Unix, ULTRIX, HP-UX, Dynix (Sequent), BOS (Bull) and others 🌈.
Ports to the following are planned: OS/2 ('94), Windows 3 ('94) 🎀.
The product does not make use of an external DBMS for the information base 💅.
AVAILABILITY 🛍️
UCOM.X is commercially available. For further info, contact:
Pascal Duchamp, 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: C=FR;A=atlas;P=e3x;O=e3x;OU1=paris;S=duchamp
duchamp@paris.e3x.fr
or: Laurence Puvilland, Marketing
Email: C=fr;A=atlas;P=e3x;O=e3x;OU1=paris;S=puvilland
puvilland@paris.e3x.fr
or: Ascan Woermann, R&D
Email: C=fr;A=atlas;P=e3x;O=e3x;S=Woermann
woermann@e3x.frDATE LAST UPDATED 📅
July, 1993 🕰️
NAME 🏷️
Wang OPEN/services (tm) Wang Laboratories, Inc.
KEYWORDS 🔑
CLNS, Commercially Available, DSA/DUA, DUA Interface, HP, IBM PC, IBM RISC, Limited Functionality, OSI Transport, RFC-1006, Wang, X.25 💜
ABSTRACT 📖
Wang's X.500 products are part of our OPEN/services product, and its main features include the following ✨:
X.500 directory: contains information about organizations, individuals, and distribution lists. The 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 name and password of each user logging into OPEN/services 🔐.
International support: provides character translation tables so users can display screens containing international characters and use international collating sequences 🌍.
Object management: greatly increases the integration between OPEN/services, OPEN/office and other Windows-based applications 🧩.
Activity logging: records the activities of OPEN/services. This info can be useful for monitoring the OPEN/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, and a DUA interface, all rolled into one product. (The DUA interface protocol is private 🤫.)
Wang OPEN/services consists of two parts: software installed on a server and software installed on PC clients on a LAN. The client or end-user software lets users log in and log out, change the login password, use the OPEN/services directory, and perform various actions, such as open and print, on files in the Wang OPEN/applications and in certain third-party applications, including Microsoft Windows File Manager 🖥️. The server consists of the DSA, the DUA, the Directory Information Base, the service administration programs such as login authentication, the database management utilities, and activity logging 🏰.
COMPLIANCE (applicable only for DSAs and DUAs) 💅
Wang OPEN/services complies with the 1988 CCITT Recommendations X.500-X.521 [CCITT-88], with the following exceptions 🙃. Whole tree searches are not supported, nor does the product support chained adding, modifying, or deleting. Simple authentication is supported, but strong authentication is not 🔓.
In the future, the 1992 extensions to the X.500 standard will be supported by Wang OPEN/services 🔮.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS 🎀
None are supported at the present time 🥲.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 🌈
None are supported at the present time 🥲.
INTEROPERABILITY 🔥
The interoperability of OPEN/services with other X.500 products is untested 🧪.
PILOT CONNECTIVITY ✨
Pilot connectivity between OPEN/services and the AARNET project, NADF Pilot Project, NIST Pilot Project, PARADISE, and PSI White Pages Project has not been attempted 🙈.
BUGS 🐛
To report problems with Wang OPEN/services, contact your local Wang sales office, your Wang authorized reseller, or call your regional support center. (In the USA, the number is 404-432-9001.) 📞
CAVEATS and GENERAL LIMITATIONS ⚠️
None 🌟
INTERNETWORKING ENVIRONMENT 🌐
Wang OPEN/services currently runs in the following environments: RFC1006 with TCP/IP, TP4 with CNLS, TP0 with X.25 and SLIP 🦋.
HARDWARE PLATFORMS 💻
Server Requirements
Installing Wang OPEN/services Server requires the following hardware: a Wang RISC Series Server 220 or greater, or an IBM RISC System/6000(tm) with a minimum of 32 MB of memory, or a Hewlett-Packard 9000 Series 800 system with a minimum of 32 MB of memory. For each system, a minimum of 20 MB of free disk space in a file system is required 🏗️.
Client Requirements
Installing OPEN/services for Windows requires the following hardware: a 386/SX CPU or later, at least 4 MB of memory, a hard disk drive with at least 2.5 MB of disk space, and a VGA monitor. A pointing device is not required to run OPEN/services, but it is strongly recommended 🖱️.
Network Requirements
OPEN/services has the following network requirements: 802.3 or 802.5 LAN, network interface cards (NICs) to support TCP/IP on client PCs, Ethernet or token ring adapters on the servers, and optionally X.25 cards on the servers 🕸️.
SOFTWARE PLATFORMS 🧩
Server Requirements
Installing Wang OPEN/services Server requires 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 System, Release 5.0 or later, and Microsoft Windows 3.1 or later 🪟.
AVAILABILITY 🛍️
Wang OPEN/services is commercially available from:
Wang Laboratories, Inc.
1 Industrial Avenue
Lowell, Massachusetts 01851
Phone: 508-967-6114
FAX: 508-967-1105To obtain OPEN/services, contact your local Wang sales office, your Wang authorized 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, DUA Only, Free, Limited Functionality, Multiple Vendor Platforms, Needs ISODE, RFC-1274, RFC-1484, Source, Sun, UNIX, X Window System 💖
ABSTRACT 📖
Xdi is a Directory User Agent (DUA) for the X Window System 🪟. On top of a user-friendly interface, it supports Directory interactions of different levels of complexity. Users can select different window screens to browse, search and modify the Directory. There are two different search screens, one for name-based search and one for attribute-based search. It's simple enough for novice users, but it's also useful for more advanced users who want to formulate complex search filters 🧠. Xdi also supports "user-friendly naming" in many cases, so users don't need to know the X.500 naming format 🎀.
COMPLIANCE (applicable only for DSAs and DUAs) 💅
88 standard compliant: Delete and Add operations are supported, but strong authentication is not implemented. There are no facilities to modify the RDNs of entries 🙈.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS 🎀
RFC 1274 is supported ✨.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 🌈
RFC 1484 is supported 🦋.
INTEROPERABILITY 🔥
Believed to be interoperable with other DSAs. Only tested against ISODE/QUIPU DSAs 🧪.
PILOT CONNECTIVITY ✨
DUA Connectivity 🔌
BUGS 🐛
Send bug reports to sywuu@thumper.bellcore.com 📨
CAVEATS and GENERAL LIMITATIONS ⚠️
(Empty in the original.)
INTERNETWORKING ENVIRONMENT 🌐
Same as ISODE 🦋.
HARDWARE PLATFORMS 💻
This software has been tested on SUN4. It is expected that the software is portable to SUN3 and other UNIX machines 🖥️.
SOFTWARE PLATFORMS 🧩
Xdi is expected to run on ISODE (release 7.0 upwards) in a UNIX environment. The 'xdi' directory has been designed to fit directly into the ISODE source tree. Xdi requires X11R4, the associated Xt toolkit and Athena widget libraries. Also see the operating environments of ISODE 🌸.
AVAILABILITY ✨
Sources are freely available for commercial or non-commercial use 🎀 Here's who to ping:
Contacts 💌
Postal Address:
Andrew Findlay
Computing and Media Systems
Brunel University
Cleveland Road
Uxbridge, Middlesex
UB8 3PH
UK
E-mail: x500@brunel.ac.uk.
Fax: +44 895 32806 (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, RFC-1274, RFC-1277, RFC-1278, RFC-1484,
Solbourne, Sun, X Window System, X.25ABSTRACT 🌸
XT-DUA gives you an X-Windows based user interface to the X.500 Directory 🪟 Both Motif and OpenLook styles are supported, so you get to pick your vibe 💅
Browsing features are giving a lot:
- Passing of user address information to the XT-MUA X.400 user agent.
- History - allowing quick access to previously referenced parts of the DIT.
- Customizable entry display - 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 scanline.
- Intelligent choice of 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) - based on Quipu EDB format.
- Deletion of entries.
- Friendly editor of modifying Quipu ACLs.
- Rebinding - authenticated and to named DSA.
- Full configuration of DAP request parameters
COMPLIANCE (applicable only for DSAs 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 to the 1992 standards.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS 🌐
The following are supported: RFC 1274 and RFC 1277.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 🦋
The following are supported: UFN [RFC 1484] and RFC 1278.
INTEROPERABILITY 🫶
XT-DUA has interoperated with all DSAs used in the PARADISE pilot.
PILOT CONNECTIVITY 🧚
Full DUA connectivity to the PARADISE and PSI White Pages X.500 Pilots.
BUGS 🙈
No known bugs. Support is given via phone or email to "support@nexor.co.uk"
CAVEATS and GENERAL LIMITATIONS 💀
None.
INTERNETWORKING ENVIRONMENT 🌈
OSI TP4 with CLNP, OSI TP0 with X.25 or CONS, and RFC 1006 with TCP/IP
HARDWARE PLATFORMS 🖥️
- Sun
- Solbourne
- IBM RS/6000
- Bull DPX 6000
- HP Apollo 9000
SOFTWARE PLATFORMS 💾
- SunOs 4.1.x
- AIX 3.2
- HP-UX 9.01
- Windows 3.1 (over LDAP)
Other ports planned include SCO Unix and ICL DRS6000.
AVAILABILITY 🛒
XT-DUA is commercial software. For more details contact:
XT-DUA Sales
NEXOR
8 Faraday Building
Highfields Science Park
Nottingham
NG7 2QP
UK
DN: c=GB@o=NEXOR Ltd
Telephone: +44 602 520500
Fax: +44 602 520519
E-Mail: sales@nexor.co.ukDATE 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.25ABSTRACT 🌸
XT-QUIPU is an X.500(88) DSA. Here are its characteristics:
- Full DAP access
- Full DSP access
- Support for X.400, X.500, and RFC 1274 attributes and object classes
- Approximate match based on Soundex.
- Flexible schema management
- RFC 1276 Replication
- Attribute level access control
- Search and list access control
- Knowledge management mapped onto DIT
- Attribute inheritance
- Caching
- Remote management
COMPLIANCE (applicable only for DSAs 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 🌐
The following are supported: String DN format [RFC 1485], RFC 1274, RFC 1276, and RFC 1277.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs 🦋
The following are supported: UFN [RFC 1484], RFC 1278, and RFC 1279.
INTEROPERABILITY 🫶
XT-QUIPU interoperates with all DSAs used in the PARADISE pilot.
PILOT CONNECTIVITY 🧚
XT-QUIPU DSAs are fully connected to the PARADISE and PSI White Pages X.500 Pilots.
BUGS 🙈
No known bugs. Support is given via phone or email to "support@nexor.co.uk"
CAVEATS and GENERAL LIMITATIONS 💀
None.
INTERNETWORKING ENVIRONMENT 🌈
OSI TP4 wtih CLNP
OSI TP0 with X.25 or CONS
RFC 1006 with TCP/IPHARDWARE PLATFORMS 🖥️
- Sun
- Solbourne
- IBM RS/6000
- Bull DPX 6000
- ICL DRS/6000
- HP Apollo 9000
SOFTWARE PLATFORMS 💾
- SunOs 4.1.x
- AIX 3.2
- DRS/NX 6000
- HP-UX 9.01
Other ports planned include SCO Unix.
AVAILABILITY 🛒
XT-QUIPU is commercial software. For more details contact:
XT-QUIPU Sales
NEXOR
8 Faraday Building
Highfields Science Park
Nottingham
NG7 2QP
UK
DN: c=GB@o=NEXOR Ltd
Telephone: +44 602 520500
Fax: +44 602 520519
E-Mail: sales@nexor.co.ukDATE LAST UPDATED or CHECKED 📅
August 2nd, 1993
4. References 📚
[CCITT-88]CCITT, "Data Communications Networks Directory", Recommendations X.500-X.521, Volume VIII - Fascicle VIII.8, IXth Plenary Assembly, Melbourne, November 1988.[NIST-88]National Institute of Standards and Technology, "Stable Implementation Agreements for Open Systems Interconnection Protocols", Version 2 Edition 1, NIST Special Publication 500-162, December 1988.[RFC 1202]Rose, M., "Directory Assistance Service", RFC 1202, Performance Systems International, Inc., February 1991.[RFC 1249]Howes, T., Smith, M., and B. Beecher, "DIXIE Protocol Specification", RFC 1249, University of Michigan, August 1991.[RFC 1274]Barker, P., and S. Kille, "The COSINE and Internet X.500 Schema", RFC 1274, University College, London, England, November 1991.[RFC 1275]Kille, S., "Replication Requirements to provide an Internet Directory using X.500," RFC 1275, University College, London, England, November 1991.[RFC 1276]Kille, S., "Replication and Distributed Operations extensions to provide an Internet Directory using X.500", RFC 1276, University College, London, England, November 1991.[RFC 1277]Kille, S., "Encoding Network Addresses to support operation over non-OSI lower layers", RFC 1277, University College, London, England, November 1991.[RFC 1278]Kille, S., "A string encoding of Presentation Address", RFC 1278, University College, London, England, November 1991.[RFC 1279]Kille, S., "X.500 and Domains", RFC 1279, University College, London, England, November 1991.[RFC 1484]Kille, S., "Using the OSI Directory to achieve User Friendly Naming", RFC 1484, ISODE Consortium, July 1993.[RFC 1485]S. Kille, "A String Representation of Distinguished Names", RFC 1485, ISODE Consortium, July 1993.[RFC 1487]Yeong, W., Howes, T., and S. Kille, "X.500 Lightweight Directory Access Protocol", RFC 1487, Performance Systems International, University of Michigan, ISODE Consortium, July 1993.[RFC 1488]Howes, T., Kille, S., Yeong, W., and C. Robbins, "The X.500 String Representation of Standard Attribute Syntaxes", RFC 1488, University of Michigan, ISODE Consortium, Performance Systems International, NeXor Ltd., July 1993.
5. Security Considerations 🔐
Plot twist: this memo does not discuss security issues at all 💀
Security issues are not discussed in this memo.
6. Editors' Addresses 💌
Arlene F. Getchell
Lawrence Livermore National Laboratory
National Energy Research Supercomputer Center
P.O. Box 5509, L-561
Livermore, CA 94551
Phone: (510) 423-6349
EMail: getchell@es.net
X.400: s=getchell;p=esnet;a= ;c=us;Srinivas R. Sataluri
AT&T Bell Laboratories
Room 1C-429, 101 Crawfords Corner Road
P.O. Box 3030
Holmdel, NJ 07733-3030
Phone: (908) 949-7782
EMail: sri@qsun.att.com📦 where this page comes from
- ietf: rfc1632 1994-05
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms