RFC 1292
A Catalog of Available X.500 Implementations
Status of this Memo 🎀
okay so this memo is just here to give the Internet community info, bestie 💖 It does not specify an Internet standard, and distribution is totally unlimited ✨
Abstract 🦋
the whole point of this doc is to share info about how available X.500 implementations are and what they can do 📚 Comments, critiques, and new or updated descriptions of X.500 implementations are super welcome 🫶 Send them to the Directory Information Services Infrastructure (DISI) Working Group at disi@merit.edu or to the editors 💌
1. Introduction ✨
so this doc catalogs the X.500 implementations that are out there right now, both commercial products and openly available ones 🌈 It describes Directory System Agents (DSA), Directory User Agents (DUA), and DUA client apps. The client apps can be things like browsers, DSA management tools, or lightweight DUAs that use an application-level protocol to talk to a DUA, which then talks to a DSA, to support user service 💅
Section 2 of this doc has a list of implementations cross referenced by keyword, which is super helpful for finding the ones that fit your criteria 🔍
to put the catalog together, the DISI Working Group surveyed the X.500 community across several Internet mailing lists, including iso@nic.ddn.mil, isode@nic.ddn.mil, osi-ds@cs.ucl.ac.uk, and disi@merit.edu 📬
readers are encouraged to send in comments about both the form and content of this memo, and new submissions are always welcome 🌸 Send your input to the parties described in the Status of this Memo section. DISI will produce new versions of this doc once a sufficient number of changes have come in 🦋 The DISI chairperson decides subjectively when that is 👑
1.1 Purpose 💜
the growth of existing X.500 pilot activities (like the White Pages Pilot Project) and new pilots (like the ARRNet Directory Services Project and the NIST/GSA Pilot Project) are signs that X.500 is a viable directory service mechanism for the Internet community 🔥 DISI wants to keep X.500 growing by lowering the lack-of-information barrier 🌱 This doc takes one step toward that goal by giving an easily accessible source of info on X.500 implementations ✨
1.2 Scope 🧚
this doc describes X.500 implementations that are either commercially or freely available 💅 It does not give instructions on how to install, run, or manage them 🙈 Every org's needs and computing environment are super different, so no recommendations are given 🫶 The descriptions and indices are there to make readers aware of their options and help them make more informed choices 🌈
1.3 Disclaimer 💀
the implementation descriptions were written by implementors and vendors, not by DISI members 😭 DISI did work with the description authors to make them readable, but no guarantees can be made about how valid the descriptions are or how valuable the implementations are 🙈 Caveat emptor 💅
1.4 Overview 🗺️
Section 1 is the intro stuff you're reading right now 🌸
Section 2 has a list of keywords, their definitions, and a cross reference of the X.500 implementations by those keywords 🦋
Section 3 has the X.500 implementation descriptions ✨
Section 4 lists the editors' addresses 💌
1.5 Acknowledgments 🙏
this catalog would not have happened without the description authors and the DISI Working Group members, so the editors say thank you for all your hard work and constructive feedback 🫶 Big shoutout to the NOCTools Working Group too! Their "Network Management Tool Catalog" (RFC-1147) was a valuable example 👑 Bob Stine and Bob Enger made key suggestions that helped the editors learn from their experiences 💜
the editors' work was sponsored by Defense Advanced Research Projects Agency Contract Number DACA76-89-D-0002 (Field Operational X.500 Project) and U. S. Department of Energy Contract Number DE-AC03-76SF00098 🎀
2. Keywords 🏷️
keywords are abbreviated attributes of the X.500 implementations 💖 The keyword list below was pulled from the implementation descriptions themselves 🔍 An implementation got indexed under a keyword either because 1) the description text explicitly, not just implied, referred to a particular capability, or 2) the implementation description author(s) suggested it 🌈
2.1 Keyword Definitions 📖
this section has the keyword definitions, organized and grouped by functional category 🦋 They're ordered first alphabetically by keyword category, and second alphabetically by implementation name within each keyword category 💅
2.1.1 Availability 🌤️
Available via FTAM Implementation is available using FTAM.
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 🎁
Potentially Unavailable Implementation was not available at the time this document was written 😭
Source Source code is available, potentially at an additional cost 💻
2.1.2 Implementation Type 🛠️
API Implementation comes with an application programmer's interface (i.e., a set 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 Light Weight Client Implementation is a DUA-like program that uses a non-OSI protocol to satisfy X.500 requests 🪶
DUA Only Implementation consists of a DUA only. No DSA is included 🙅♀️
2.1.3 Internetworking Environment 🌐
CLNP Implementation uses OSI CLNP 🛰️
OSI Transport Implementation description specifies that OSI transport protocols are used but does not specify which one(s) 🤷♀️
RFC-1006 Implementation uses RFC-1006 with TCP/IP transport service 🌈
X.25 Implementation uses OSI X.25 📡
2.1.4 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.5 Miscellaneous 🧩
Included in ISODE DUAs that are part of ISODE 🎀
Limited Functionality Survey states that the implementation has some shortcomings or intended lack of functionality, e.g., omissions were part of the design to provide an easy-to-use user interface. Not me giving the shortcomings a pass though 🙈
Needs ISODE ISODE is required to compile and/or use this implementation 🧰
X Window System Implementation uses the X Window System to provide its user interface 🪟
2.1.5 Operating Environment 💻
3Com Implementation runs on a 3Com platform.
Apollo Implementation runs on an Apollo platform.
Bull Implementation runs on a Bull platform.
Cray Implementation runs on a Cray.
DEC Ultrix Implementation runs under DEC Ultrix.
HP Implementation runs on an HP platform.
IBM (Non-PC and RISC) Implementation runs on some type of IBM, which is not a PC or UNIX workstation.
IBM PC Implementation runs on a PC.
IBM RISC Implementation runs on IBM's RISC UNIX workstation.
MIPS Implementation runs on a MIPS RISC UNIX workstation.
Macintosh Implementation runs on a Macintosh.
Multiple Vendor Platforms Implementation runs on more than one hardware platform.
Philips Implementation runs on a Philips platform.
Siemens Implementation runs on a Siemens platform.
Sun Implementation runs on a Sun platform.
UNIX Implementation runs on a generic UNIX platform.
Unisys Implementation runs on a Unisys platform.
VMS Implementation runs under VAX/VMS.
2.2. Implementations Indexed by Keyword ✨
okay so this section is basically a cheat sheet 💅 It's an index of implementations by keyword, so you can find the ones that match whatever criteria you're chasing 🔍
Keywords are in alphabetical order, and the implementations under each keyword are alphabetical too 🌸 A * means the implementation, or a feature of it, might not be available right now 🙈
for formatting, these abbreviations are used for implementation names: UWisc (University of Wisconsin), HP X.500 DDS (HP X.500 Distributed Directory Software), IS X.500 DSA/DSAM, DUA (Interactive Systems' X.500 DSA/DSAM, DUA) 🎀
3Com Available via FTP
X.500 DUA process DE
DISH-VMS 2.0
API DIXIE
Mac-ISODE
Alliance OSI X.500 maX.500
Custos POD
DCE/GDS psiwp
DS-520, DS-521 QUIPU
HP X.500 DDS ud
IS X.500 DSA/DSAM, DUA VMS-ISODE
Mac-ISODE Xdi
OSI Access and Directory XLU
OSI-DSA
OSI-DUA Bull
QUIPU
UCOM X.500 UCOM X.500
VMS-ISODE
VTT X.500 CLNP
WIN/DS
Cray OSI Version 2.0
Apollo DCE/GDS
HP X.500 DDS
VTT X.500 OSI Access and Directory
OSI-DSA
Available via FTAM OSI-DUA
QUIPU
DE VTT X.500
DISH-VMS 2.0 WIN/DS
POD X.500 DUA process
QUIPU Xdi
XLU XT-DUA
Commercially Available DSA/DUA
Alliance OSI X.500 Alliance OSI X.500
Cray OSI Version 2.0 Cray OSI Version 2.0
DCE/GDS Custos
Directory 500 Directory 500
DS-520, DS-521 DS-520, DS-521
HP X.500 DDS HP X.500 DDS
IS X.500 DSA/DSAM, DUA IS X.500 DSA/DSAM, DUA
OSI Access and Directory Mac-ISODE
OSI-DSA OSI Access and Directory
OSI-DUA QUIPU
UCOM X.500 UCOM X.500
VTT X.500 VMS-ISODE
WIN/DS VTT X.500
X.500 DUA process WIN/DS
XT-DUA
xwp [PSI] DUA Connectivity
Cray DE
DS-521
Cray OSI Version 2.0 OSI Access and Directory
Xdi
DEC Ultrix
DUA Light Weight Client
DCE/GDS
QUIPU *MacDish
UCOM X.500 DIXIE
*xwp [UWisc] maX.500
psiwp
DSA Only ud
OSI-DSA DUA Only
DSA Connectivity DE
DS-520 DISH-VMS 2.0
OSI Access and Directory OSI-DUA
POD
psiwp
SD
X.500 DUA process
Xds
xdua
XLU
XT-DUA
xwp [PSI]
Free Limited Functionality
xwp [UWisc] Custos
Custos *MacDish
DE POD
DISH-VMS 2.0 psiwp
DIXIE Xds
Mac-ISODE xwp [PSI]
maX.500
POD MIPS
psiwp
QUIPU Alliance OSI X.500
SD OSI Access and Directory
ud QUIPU
VMS-ISODE
Xdi Macintosh
Xds
xdua Alliance OSI X.500
XLU DIXIE
Mac-ISODE
HP *MacDish
maX.500
Alliance OSI X.500 psiwp
HP X.500 DDS QUIPU
QUIPU *UCOM X.500
UCOM X.500
Multiple Vendor Platforms
IBM (Non-PC and RISC) Alliance OSI X.500
Alliance OSI X.500 Custos
DCE/GDS
IBM PC DS-520, DS-521
IS X.500 DSA/DSAM, DUA
Alliance OSI X.500 POD
*UCOM X.500 QUIPU
*VTT X.500 SD
xwp [UWisc] UCOM X.500
ud
IBM RISC VTT X.500
DCE/GDS WIN/DS
UCOM X.500 X.500 DUA process
xdua
Included In ISODE XLU
POD XT-DUA
SD xwp [PSI]
xwp [UWisc]
Needs ISODE RFC-1006
Custos Alliance OSI X.500
DE Cray OSI Version 2.0
DISH-VMS 2.0 Custos
DIXIE DCE/GDS
Mac-ISODE Directory 500
*MacDish DISH-VMS 2.0
POD DS-520, DS-521
psiwp IS X.500 DSA/DSAM, DUA
SD Mac-ISODE
VMS-ISODE OSI Access and Directory
Xdi *OSI-DSA
Xds *OSI-DUA
xdua POD
XLU QUIPU
XT-DUA SD
xwp [UWisc] UCOM X.500
VMS-ISODE
OSI Transport VTT X.500
WIN/DS
Alliance OSI X.500 Xdi
Cray OSI Version 2.0 Xds
Custos XLU
DS-520, DS-521 XT-DUA
IS X.500 DSA/DSAM, DUA
QUIPU Siemens
WIN/DS
XT-DUA *UCOM X.500
Philips
UCOM X.500
Potentially Unavailable
MacDish
Source UNIX
DCE/GDS Custos
DE DE
DS-520, DS-521 DIXIE
Mac-ISODE DS-520, DS-521
OSI-DSA IS X.500 DSA/DSAM, DUA
OSI-DUA POD
POD QUIPU
psiwp SD
QUIPU UCOM X.500
ud ud
VMS-ISODE WIN/DS
WIN/DS Xdi
Xdi XLU
Xds XT-DUA
xdua xwp [PSI]
XLU xwp [UWisc]
Sun Unisys
Alliance OSI X.500 OSI-DSA
Custos OSI-DUA
Directory 500
DIXIE VMS
QUIPU
UCOM X.500 DISH-VMS 2.0
ud VMS-ISODE
VTT X.500
Xds X Window System
xdua QUIPU
XT-DUA SD
WIN/DS
X.500 DUA process
Xdi
Xds
xdua
XT-DUA
xwp [PSI]
xwp [UWisc]
X.25
DCE/GDS
Directory 500
DISH-VMS 2.0
HP X.500 DDS
OSI Access and Directory
OSI-DSA
OSI-DUA
QUIPU
*UCOM X.500
VTT X.500
WIN/DS
X.500 DUA process
Xdi
XT-DUA3. Implementation Descriptions ✨
okay so this part is the big profile section 📚 You'll find descriptions of X.500 implementations here, listed in alphabetical order 🦋 If two implementations share a name, the responsible organization goes in square brackets to tell them apart 🎀 Heads up: across this section, the page header shows the implementation's name, not the date of the document 📄
Every description follows the same template, so here's the format:
- NAME: the name of the X.500 implementation and the name of the responsible organization. Implementations with a registered trademark show it by appending "(tm)", e.g., GeeWhiz(tm). 💅
- LAST MODIFIED: the month and year when this implementation description was last modified. 🗓️
- KEYWORDS: a list of the keywords defined in Section 2 that were used to cross reference this implementation. 🔗
- ABSTRACT: a brief description of the application. This section may optionally contain a list of the pilot projects in which the application is being used. ✨
- COMPLETENESS: a statement of compliance with respect to the 1988 CCITT Recommendations X.500-X.521 [CCITT-88], specifically Section 9 of X.519, or the 1988 NIST OIW Stable Implementation Agreements [NIST-88]. 📋
- 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 operational on the Internet in North America, and to pilots coordinated by the PARADISE project in Europe. The levels of connectivity 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, e.g., a feature that works on one platform but not another. ⚠️
- INTERNETWORKING ENVIRONMENT: a list of environments in which this implementation can be used, e.g., RFC-1006 with TCP/IP, TP0 or TP4 with X.25. 🧚
- HARDWARE PLATFORMS: a list of hardware platforms this application runs on, any additional boards or processors required, and any special suggested or required configuration options. 🖥️
- SOFTWARE PLATFORMS: a list of operating systems, window systems, databases, or unbundled software packages required to run this application. 💾
- AVAILABILITY: a statement about whether the software is available (free or commercially available), a description of how to obtain it, and (optionally) a statement about distribution conditions and restrictions. 🎁
Here's the first full profile, for Alliance OSI X.500. Let's go 🔥
NAME
Alliance OSI(tm) X.500 Touch Communications Inc. 🌈
LAST MODIFIED
July, 1991 🗓️
KEYWORDS
API, Commercially Available, DSA/DUA, HP, IBM (Non-PC and RISC), MIPS, Macintosh, Multiple Vendor Platforms, OSI Transport, RFC-1006, Sun 🏷️
ABSTRACT
Okay, so Alliance OSI includes XDS (API), DUA, DSA and DIB, all as separate components. 🧩
Touch's X.500 products are designed to be completely portable to any operating system or hardware environment 💖 The protocols include DAP and DSP of the OSI X.500 specification, along with the required XDS, DUA, DSA and DIB components. On top of X.500, Touch also supplies other OSI protocol layers: ROSE, ACSE, Presentation, Session, and any of the OSI lower layers (Transport, Network, along with RFC-1006). Touch also supplies other application layer protocols such as X.400, FTAM, CMIP (and general network management), etc. 🦋
The Alliance OSI X.500 is compliant with the CCITT X.500 1988 Recommendations. The ROSE/ACSE/Presentation/Session stack can be optionally provided by Touch. ✨
The DUA may represent a single user, or it may represent a group of users. It may be attached to a given DSA within the same system, but it's also capable of invoking operations in Touch's or any other vendor's compliant DSA on a remote system 🌸 The binding operation requires the user to give a distinguished name and password so the Directory can identify the user. Once an association is established, the user may invoke the following operations: READ, COMPARE, ABANDON, LIST, SEARCH, ADD_ENTRY, REMOVE_ENTRY, MODIFY_ENTRY, MODIFY_RDN. 🔑
Here's the lowkey clever bit 🧠 Accessing the physical disk is in most cases a blocking (synchronous) operation, so Touch separated the database processing (the I/O process) from the DSA protocol entity. This separation lets the DSA entity keep processing during the frequent database accesses from the DSA. The DSA supports all the Directory operations specified in the CCITT X.500 specification. Chaining, Referral and Multicasting are provided and supported in the Alliance OSI DSA. The DSA supports all the service control options included in the operation command arguments. Filtering conditions are supported via the FILTER in the SEARCH operation. 💅
The Alliance OSI X.500 product supports all the NIST defined mandatory X.500 and X.400 object classes and attributes 📋
Alliance OSI X.500 supports all the mandatory Directory attribute types (and their associated abstract syntaxes) in the NIST Directory implementation profile. Touch has extended the Directory and allows users to define private attributes, which means a user can utilize the Alliance OSI Directory for a general purpose, user defined database activity. 🎀
Touch also provides a full set of administration and Directory management facilities 🛠️
Touch is in the process of integrating the X.500 product with the Worldtalk 400 product. Worldtalk 400 is Touch's end user X.400 message switch, providing gateways between proprietary mail systems (SMTP, Microsoft Mail, MHS, cc:mail, etc.) and X.400. X.500 is a key component for a messaging network. 📨
COMPLETENESS
Strong Authentication is not supported, however Simple Authentication is supported. 🔐
INTEROPERABILITY
No interoperability testing has been completed as of yet. 🙈
PILOT CONNECTIVITY
Numerous OEMs are using the Alliance OSI X.500 product in product development as well as in pilot networks. 🌟
BUGS
N/A 🌷
CAVEATS AND GENERAL LIMITATIONS 💅
okay so the Alliance OSI X.500 DIB has only been validated inside a UNIX File System 🗂️ the protocol components are portable, and so is the interface between the DSA and the DIB 🫶
INTERNETWORKING ENVIRONMENT 🌐
Alliance OSI X.500 can run over TCP/IP and/or OSI Transport on LANs and WANs ✨ right now X.500 has only been verified over OSI, but other Alliance OSI application layers have been set up over an RFC-1006, which comes with the Alliance OSI product line 🎀
HARDWARE PLATFORMS 🖥️
Alliance OSI has been ported to a ton of platforms, from IBM Mainframes MVS all the way to Apple Macintosh 🍎 for UNIX environments, Touch has ports for 386 AT/Bus, SUN-3 and 4, Mips, and HP 🔥
SOFTWARE PLATFORMS 💻
as I said above, the Alliance OSI product has been ported to lots of systems 💖 in the UNIX environment, the X.500 product runs on SUN OS 4.0 and greater, Mips RISC OS, Interactive 386, and HP-UX 🌸
AVAILABILITY 🛒
Alliance OSI is commercially available from:
Touch Communications Inc.
250 E. Hacienda Ave
Campbell, CA 95008
Sales and Information: (408) 374-2500
FAX: (408) 374-1680Cray OSI Version 2.0 ☁️
NAME 🏷️
Cray OSI Version 2.0 Cray Research Inc.
LAST MODIFIED 📅
July, 1991
KEYWORDS 🔑
CLNP, Commercially Available, Cray, DSA/DUA, OSI Transport, RFC-1006
ABSTRACT ✨
the product comes packaged with the Cray OSI product 💅 it includes a DSA and DUA that can run over OSI or TCP/IP connections 🦋 the implementation is based on the ISODE QUIPU product 🧚
COMPLETENESS 🎯
compliance with CCITT88 plus access control extensions, but strong authentication isn't implemented yet 🙈
INTEROPERABILITY 🫶
it interoperates with ISODE QUIPU based implementations 💜
PILOT CONNECTIVITY 🌈
the software has been operated alongside the White Pages Pilot Project ⭐
BUGS 🐛
[No information provided--Ed.]
CAVEATS AND GENERAL LIMITATIONS ⚠️
see ISODE QUIPU limitations 🔗
INTERNETWORKING ENVIRONMENT 🌐
TCP/IP, TP4
HARDWARE PLATFORMS 🖥️
runs on UNICOS based Cray machines with OS level 7.0 or greater 👑
SOFTWARE PLATFORMS 💻
supported for CRAY UNICOS 7.0 or greater 💖
AVAILABILITY 🛒
commercially available via Cray Research Inc. Sales Representatives 💅
Custos 🌸
NAME 🏷️
Custos National Institute of Standards and Technology
LAST MODIFIED 📅
November, 1991
KEYWORDS 🔑
API, DSA/DUA, Free, Limited Functionality, Multiple Vendor Platforms, Requires ISODE, OSI Transport, RFC-1006, Sun, UNIX
ABSTRACT ✨
the implementation is made up of a set of DUA library routines, a terminal interface, and a DSA 🧚 it was developed in C on Sun 3 workstations under the UNIX operating system 💻 all the underlying services come from the ISODE development package 🫶 that package is also used for encoding and decoding ASN.1 data, plus other data manipulation services 🔥 with ISODE, the implementation can run over both OSI and TCP/IP protocols 🦋
the DSA gives full support for both the 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 that database is a set of SQL-like C functions 💅 these are designed so the local database can be swapped out for a more powerful commercial system without much fuss ✨ for better performance, several options are supported that load selected portions of the database into core 🚀 when those options are on, data can be retrieved more quickly from in-core tables, and every modification to the DIB is reflected directly in both the in-core tables and the database 💜
COMPLETENESS 🎯
so far, the Read, Compare, List, Add Entry, and Remove Entry operations have been implemented and are supported over both DAP and DSP, and aliasing and replication are supported too 🌈 the version under current development (available January '92) adds simple authentication, access control, and the Search operation 💖 the modify operations and Abandon aren't supported, and there's no support for schema checking 🙈
INTERoperability 🫶
Custos has successfully interoperated with QUIPU and OSIWARE over the DAP 💅 no DSP interoperability testing has been done yet 🙈
PILOT CONNECTIVITY 🌸
not tested 🧚
BUGS 🐛
some testing will happen in the near future to try to identify bugs, but right now it's not possible to give an accurate list of them 😭
CAVEATS AND GENERAL LIMITATIONS ⚠️
no limitations on file sizes, etc. the only side effects of creating large files should be in the area of performance 🚀 specifically, optimization requires loading parts of the DIB into core, so greater memory will be needed to get 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 (SunLink OSI) over 802 and X.25 (SunLink X.25) 🦋
HARDWARE PLATFORMS 🖥️
it has been run on Sun-3, but there are no known reasons it shouldn't run on any hardware that runs the ISODE software 👑
SOFTWARE PLATFORMS 💻
it requires UNIX and the ISODE software package 🫶 it's been developed and tested with ISODE version 6.0 and Sun OS version 4.1.1 💅 it uses a locally developed relational DBMS that should be easy to replace with commercially available relational systems ✨
AVAILABILITY 🛒
while it's under continuing development, availability is limited to organizations that make appropriate arrangements with NIST 🔒 the implementation will be publicly available once development is completed 🎉
DCE/GDS (tm) 🧚
NAME 🏷️
DCE/GDS (tm) Open Software Foundation, Inc.
LAST MODIFIED 📅
July, 1991
KEYWORDS 🔑
API, CLNP, Commercially Available, DEC Ultrix, DSA/DUA, IBM RISC, Multiple Vendor Platforms, RFC-1006, Source, X.25
ABSTRACT ✨
DCE/GDS (Distributed Computing Environment/Global Directory Service) was based on the original Siemens DIR.X product 💖 it supports full DUA and DSA functions for globally unique identifications and for locating objects in the network 🌍 it also provides functions to answer queries (both yellow-page and white-page) about objects and attribute information 📖 the software implements the full DAP and DSP protocols specified in X.519 💜 an ASN.1 compiler and the required ACSE, ROSE, presentation, session, and RFC-1006 protocol implementations are included too 🔥
the product has successfully participated in the X.500 Cebit Interoperability tests at the 1990 and 1991 Hanover Fairs 🏆 it also interoperates with the ISODE QUIPU X.500 implementation 🫶
COMPLETENESS 🎯
compliant with EWOS Agreements, which are being harmonized with OIW Agreements 💅
strong authentication in X.509 isn't implemented yet (a password scheme is used for now) 🙈
it consists of both DUA and DSA implementations according to the 88 CCITT X.500 and ISO 9594 standards 👑 the X/Open standard XDS (version 1.0) and XOM (version 2.0) interface libraries are also provided ✨ XDS and XOM interfaces are also used to access DCE/CDS (Local Cell Directory Service) transparently 🦋 and a GDA (Global Directory Agent) acts as the gateway between the DCE CDS and GDS 🌈
INTEROPERABILITY 🫶
this implementation of DAP and DSP can interoperate with other X.500 implementations from other Cebit demo participants, including IBM, HP, ICL, Bull, Nixdorf, etc. 💖 it also interoperates with ISODE QUIPU 💜
PILOT CONNECTIVITY 🌸
[No information provided--Ed.]
BUGS 🐛
problems and bug report email address: dce-defect@osf.org 📧
CAVEATS AND GENERAL LIMITATIONS ⚠️
the software is highly portable without general limitations 🦋
INTERNETWORKING ENVIRONMENT 🌐
OSI TP4 with CLNP
OSI TP0, 2 & 4 with X.25
RFC-1006 with TCP/IPHARDWARE PLATFORMS 🖥️
DCE/GDS runs on SNI's hardware platforms and is being ported to run on IBM RS6000, Digital DECstation, etc. 👑
SOFTWARE PLATFORMS 💻
SINIX (UNIX System V Release 4) 🌸 currently being ported: OSF/1.1, AIX 3.1, Ultrix, etc. 🚀 DCE/GDS can use either BSD sockets or XTI/TLI to access the transports 🔌
AVAILABILITY 🛒
the source code license of DCE/GDS is commercially available from:
Open Software Foundation, Inc.
11 Cambridge Center
Cambridge, MA 02142please contact:
Jon Gossels
Tel: 617-621-8763
Fax: 617-621-0631
e-mail: gossels@osf.orgDE 🧚
NAME 🏷️
DE COSINE PARADISE
LAST MODIFIED 📅
November, 1991
KEYWORDS 🔑
Available via FTAM, Available via FTP, DUA Connectivity, DUA Only, Free, Included in ISODE, Limited Functionality, Needs ISODE, Source, UNIX
ABSTRACT ✨
DE (Directory Enquiries) is meant to be a simple-to-use interface, suitable for the naive user and for running as a public access DUA, giving lowest common denominator access to the Directory 💅 it's a scrolling interface, so it runs on dumb terminals, even teletypes! 🤭 the user is asked to fill in up to 4 questions per query: person's name, department, organization, and country 📝 the prompts are very verbose, because the user should never be able to get stuck, and info on how to get into the help system should always be on the screen 🫶 there are 15 help screens, aimed at the non-technical user 🌸
even though the outward look is simple, a lot of attention has gone into mapping the strings the user enters onto X.500 operations, so the interface seems to do the "right thing" 🔥 an important feature is the way it tries a series of searches, gradually relaxing the matching criteria from exact (in some sense), to good, through to "fuzzy" 🧠 a lot of configuration is possible for presenting results in locally acceptable formats ✨
DE was funded by the COSINE PARADISE project, and DE is used as the PARADISE public access DUA 🦋 you can test the software by telnetting to 128.86.8.56 and logging in as dua, no password required 💖
COMPLETENESS 🎯
the interface is a querying engine only 🙈
INTEROPERABILITY 🫶
DE is built with the ISODE software (release 7.0) 💜 its interoperability relies on the correctness of the Quipu libraries 🌈
PILOT CONNECTIVITY 🌍
the interface is in use as the COSINE Central DUA Service, and a number of UK institutions use it as a public access DUA (usually over X.29) 🇬🇧 it's able to query entries in pilots throughout the world ✨ it can't query for entries that are in organizations beneath locality entries under country entries 🙈 it's also not possible to query for people who don't work for organizations 😭 the interface only searches for these entry types: organizations, organizational units, people, roles, and rooms 📋
BUGS 🐛
send bug reports to:
p.barker@cs.ucl.ac.uk
helpdesk@paradise.ulcc.ac.ukCAVEATS AND GENERAL LIMITATIONS ⚠️
DE tries to cater well for the general case, at the expense of not dealing with the less typical 🎀 the main result is that the current version won't query under localities immediately under the country level 🙈
it's not possible to display photographs or reproduce sound attributes 📸
INTERNETWORKING ENVIRONMENT 🌐
same as ISODE 🦋 ISODE supports TCP/IP, TP0, and X.25 🔌
HARDWARE PLATFORMS 🖥️
should be the same as ISODE in general 👑
SOFTWARE PLATFORMS 💻
DE requires the ISODE (current release 7.0) libraries 💅
AVAILABILITY 🛒
DE is openly available as part of ISODE and as part of the COSINE DUA package 🎉 it's available by FTAM and FTP, and the source code is freely available 💖
Directory 500(tm) 🌟
NAME 🏷️
Directory 500(tm) OSIware Inc.
LAST MODIFIED 📅
July, 1991
KEYWORDS 🔑
Commercially Available, DSA/DUA, RFC-1006, Sun, X.25
ABSTRACT ✨
okay so this one is a Directory User Agent (DUA) interface that got ported to VMS 💻 using ISODE 6.0. It came out of ACIDO, a collab between RedIRIS (Spain's national network R & D crew 🇪🇸) and the "Facultad de Informatica de Barcelona (Universidad Politecnica de Cataluna)". The whole point was to give every affiliated centre on the Spanish National R & D network directory access from their VMS machines 🖥️🎀. Any other use of this software is outside RedIRIS's goals, so it's not RedIRIS's responsibility 🙅♀️.
COMPLETENESS
the same as DUA (QUIPU 6.1) 💅
INTEROPERABILITY
works with QUIPU 6.1 🔗
PILOT CONNECTIVITY
used in the RedIRIS Directory Pilot Project to reach the DSAs (QUIPU) 🌐✨
BUGS
you can report bugs to: isode@fib.upc.es 🐛
CAVEATS AND GENERAL LIMITATIONS
the interface matches the UNIX one, except the -pipe option, which isn't supported 🙅♀️
users can have a quipurc. file to set up their work environment with DISH 🌸. it should live in the user's SYS$LOGIN directory and be called "quipurc." (on UNIX it's .quipurc) 🧚
INTERNETWORKING ENVIRONMENT
- RFC-1006 with TCP/IP
- TP0 with X.25
HARDWARE PLATFORMS
VAX 🖥️
SOFTWARE PLATFORMS
- VAX/VMS 5.3
- VAX PSI 4.2
- VMS/ULTRIX Connection 1.2
AVAILABILITY
executables can be freely distributed for non-commercial use 🎁. transfer mode is binary 💾.
FTP user anonymous sun.iris-dcp.es (130.206.1.2)
FTAM, user anon
TSEL= <0103>H
INT-X25= 21452160234012
IXI= 2043145100102
ISO-CLNS= 39724F1001000000010001000113020600100200 (COSINE P4.1)
File: /isodevms/dishVMS2.BCK.Z compress SAVE_SET file (1.6 Mbytes)
File: /isodevms/lzdcm.exe to uncompress the fileNAME
DIXIE University of Michigan
LAST MODIFIED
November, 1991
KEYWORDS
Available via FTP, DUA Light Weight Client, Free, Source, UNIX, Multiple Vendor Platform, Needs ISODE
ABSTRACT
the DIXIE protocol lets platforms that only have TCP/IP access get X.500 access 🦋. the DIXIE server is an intermediate protocol server 🧚. on one side it talks to Internet clients using a text-based UDP/TCP protocol, and on the other side it talks to an X.500 DSA using DAP 💜. the protocol is fully described in RFC 1246 📖. a subset of the X.500 DAP gets exported to clients through the DIXIE protocol 🎀. there's also a DIXIE API, a library of C-callable routines 💅.
the DIXIE protocol and server are being used by these products and projects 🌈:
- UD, a simple command line white pages DUA for Unix machines (distributed with the DIXIE server)
- maX.500, a white pages DUA for the Macintosh (available from the same place as the DIXIE server)
- network monitoring of DSAs by their Network Operations Center
- lookup and display of caller identification based on telephone caller ID (using ISDN) 📞
COMPLETENESS
the DIXIE protocol doesn't support access to every X.500 feature and operation 🙈. all DAP operations except Abandon are supported ✅. general searches (including multiple component searches) are supported 🔍. the DIXIE protocol supports none and simple authentication 🔐. a subset of the service controls is supported 🎛️.
INTEROPERABILITY
the current DIXIE server works with the QUIPU DSA and DAP library 🤝.
PILOT CONNECTIVITY
the DIXIE server has been tested in the Internet and PARADISE pilots 🌍. it gives full DUA connectivity, subject to the limitations discussed above under completeness 💖.
BUGS
there are no known outstanding bugs 🙌. but reports should go to x500@umich.edu 📩.
CAVEATS AND GENERAL LIMITATIONS
none, aside from those mentioned above under completeness ✨.
INTERNETWORKING ENVIRONMENT
DIXIE clients use TCP or UDP to talk to the DIXIE server 🦋. the DIXIE server uses RFC-1006 with TCP/IP to talk to the DSA, though other transport mechanisms for DSA communication should be possible 🌸.
HARDWARE PLATFORMS
the DIXIE server is known to run on Sun 3, Sun 4, and DEC 3100 platforms 🖥️. it should run on any UNIX platform 🐧. the DIXIE library is known to run on the same platforms, and also on the Macintosh 🍓.
SOFTWARE PLATFORMS
the DIXIE server and library are known to run under SunOS 3.5, SunOS 4.1.1, Ultrix 4.1 and 4.2 👑. the DIXIE library also runs on the Macintosh System Software 6 or later 💜.
AVAILABILITY
this software is openly available 🎉. you can grab it by anonymous FTP from terminator.cc.umich.edu in the directory ~ftp/x500 🧚. documentation on the DIXIE protocol comes along with the source code, which includes source for the DIXIE server, DIXIE library, and the UD client 💅.
this software was developed at the University of Michigan by Bryan Beecher, Tim Howes, and Mark Smith of the ITD Research Systems Unix Group 🫶. it's subject to the following copyright 🔥.
Copyright (c) 1991 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.NAME
DS-520 DS-521 Retix
LAST MODIFIED
November, 1991
KEYWORDS
API, Commercially Available, DSA/DUA, DUA Connectivity, DSA Connectivity, Multiple Vendor Platforms, OSI Transport, RFC-1006, Source, UNIX
ABSTRACT
okay bestie, the DS-520 X.500 Distributed Directory Services for UNIX System V and the DS-521 X.500 Directory User Agent (DUA) for UNIX System V are an integral part of the Retix OSI Networking Products family 💼✨. they're built for systems vendors, public carriers, and other OEMs 🏢. the DS-520 is a complete, high-performance implementation of X.500 in source code form, and it includes a DUA, a DSA Manager (DSAM), and a DSA 🔥. the DS-521 is a subset of this offering, and it gives you the DUA portal into the directory 🚪. that's perfect for software vendors who want to ship application packages with X.500 Directory interaction 🎀.
inside these two offerings, the DUA comes in two forms of interface 💅. the first is the DUA with User Interface, which gives users of Directory services an interactive character-based interface 🖱️. the user agent gives access to the Directory through basic Directory service requests 📚. the second is the DUA with Programmatic Interface, which gives application programs that need Directory information a standardized programmatic interface 🧠. it conforms to the X/Open Object Management (XOM) and X/Open Directory Services (XDS) standards 🌈. this component handles all Directory access functionality and general OSI services down to the session layer 🫶.
the DSAM gives a Directory administrator an interactive, character-oriented user interface 👑. it provides management functions either local to or remote from a DSA 🌸. both the DUA and the DSAM are useful for training, managing, and manipulating Directory entries, including operational and user attribute information 🧚. the DSA maintains Directory database information and lets users read/compare, modify, search, and manage entries within the database 💜. it holds all or fragments of the Directory Information Base (DIB) and provides abstract service ports for DUAs and DSAs over DAP and DSP protocols, respectively ✨.
COMPLETENESS
the DS-520 is a complete implementation of the 1988 X.500 Recommendations, except for strong authentication as outlined in X.509 🔐. it conforms to the NIST, EWOS, and UK GOSIP Directory profiles 🌍. it provides session through application layer protocol support, so it includes ROSE, ACSE, Presentation, and Session in its product stack 🧱. on top of all the attribute types, syntaxes, and object classes defined in X.520 and X.521, the DS-520 also supports those specified in the 1988 X.400 Recommendation X.402, Annex A 💖. remote online management of the DSA is supported through Network Management Forum CMIP 🛰️.
the DS-521 is a complete implementation of the X/Open Object Management (OM) and X/Open Directory Services (XDS) standards 🎯. it also incorporates session through application layer protocol support, so ROSE, ACSE, Presentation, and Session are part of its product stack 🫶.
INTEROPERABILITY
the DS-520 has been tested to interoperate with Banyan (DAP), CDC (DSP), IBM, ICL, OSIWare, Nixdorff, Unisys (DSP), Wollongong (DAP), and 3-Com (DSP) 🤝✨.
the DS-521 subset has not undergone any separate interoperability testing 🙈.
PILOT CONNECTIVITY
DSA connectivity is provided by the DS-520 💅. the DSA gives complete support for the X.511 Abstract Service Definition, the directoryAccessAC and the directorySystemAC defined in the X.519 Protocol Specifications, and the Distributed Directory defined in the X.518 Procedures for the Distributed Directory 🧠. it supports all the object classes, attribute types, and attribute syntaxes defined in X.520 and X.521 📚. it does not support the Internet DSP, however 🙅♀️.
DUA connectivity is provided by both the DS-520 and DS-521 🦋. the DUA gives complete support for the X.511 Abstract Service Definition and the directoryAccessAC defined in the X.519 Protocol Specifications 🌸. the DUA with User Interface supports only a subset of the X.500 attributes and object classes defined in X.520 and X.521 😭. the DUA with Programmatic Interface, however, supports all the object classes, attribute types, and attribute syntaxes defined in these two recommendations 👑.
BUGS
Product Action Requests (PARs) come in from customers externally and from customer service and quality assurance engineers internally 🐛. they're generated and published as weekly reports 📅. customers with software maintenance agreements get a description and status of these PARs 🎀.
CAVEATS AND GENERAL LIMITATIONS
the DS-520 and DS-521 are source code products ported to UNIX System V Release 3 and 4 💻. makefiles to generate the system are provided for the AT&T System V, SCO, and Interactive UNIX systems 🧚.
INTERNETWORKING ENVIRONMENT ✨
okay so DS-520 and DS-521 have two main compile time configuration options, which means two internetworking setups 💅. In the first one, they plug into the UNIX System V Transport Library Interface (TLI) 🔌. The TLI gives you a path between the session layer of a UNIX OSI application process and an OSI transport provider sitting in the UNIX kernel 🧚. That transport provider can be a Retix Unix LAN (LT-610) or WAN (WT-325) transport product, and ngl that's so cute 🦋.
The second main option uses the UNIX System V ACSE/Presentation Library interface (APLI and the A/P Library), which gives you OSI ACSE and Presentation layer services 💜. The Retix AP-240 Presentation syntax manager product maps the standard Retix Presentation layer interface to the AT&T APLI 🎀. The APLI upper layer services can be provided by the Retix UL-220 product. UL-220 is the Retix implementation of the AT&T Open Networking Platform Upper Layer Services module, and it includes the A/P library as well as the OSI ACSE, Presentation, and Session services ✨.
DS-520 and DS-521 can also run on top of the TCP/IP stack through the Retix MP-120 product 🌈. MP-120 is a STREAMS based driver that implements RFC-1006, so OSI applications can run over a network based on the Internet suite of protocols (TCP/IP) 🫶. Its main job is converting between the TCP stream and the data packets required by the OSI Transport Class 0 protocol, and vice versa 🔁. As part of that process, it converts TCP/IP 32-bit addresses to hex values for use with OSI applications 🔢.
HARDWARE PLATFORMS 🌸
Because these are source code products ported to the UNIX System V Release 3 and 4 operating system environment, DS-520 and DS-521 are hardware platform independent 🧠. They currently both have sample portations and test configurations on various Intel 80386 platforms running Unix System V Release 3 and 4 💖.
SOFTWARE PLATFORMS 💅
Right now, DS-520 and DS-521 include reference implementations for the AT&T System V Release 4, SCO UNIX System V/386 Version 3.2.2, and the Interactive UNIX System V/386 Version 2.2 operating systems 👑. Raima Corporation's db_Vista III Version 3.1 is the database engine for the Directory product 🗄️.
AVAILABILITY 🦋
DS-520 and DS-521 are commercially available from:
Retix
2401 Colorado Avenue
Santa Monica, California
90404-3563 USA
Sales and Information: 310-828-3400
FAX: 310-828-2255NAME 🎀
HP X.500 Distributed Directory Software Hewlett Packard
LAST MODIFIED 🗓️
July, 1991
KEYWORDS 🏷️
API, CLNP, Commercially Available, DSA/DUA, HP, X.25
ABSTRACT ✨
HP's Distributed Directory Software is a fully distributed Directory that supports both the DAP and DSP protocols, which were specified in the 1988 CCITT/ISO X.500 documents. Besides implementing the standard, we've also put in proprietary access control and replication. These additional features will be migrated to the standard definition at the time that they are stable. Users are able to define their own attributes, objects classes and DIT structure rules.
To make this software easy to use, there's a set of menu driven screens 🖱️. There are easy to use data access and data management screens. For system administrators, there's also a set of screens to help configure the servers and manage the schema. Startup and Shutdown utilities are included too.
For application developers, an X/Open-APIA XDS API is provided, along with some helper routines that help reduce development time 🛠️. The XDS API includes the following functions:
- Bind
- Read
- Search
- Add
- Remove
- Unbind
- Version
A subset of the X/Open-APIA Object Management (XOM) functions is available through the interface. The subset is made up of the ones needed to perform the directory operations 🎯.
For bulk operations, a batch interface is also available 📦.
COMPLETENESS 💯
This software implements the 1988 X.500 CCITT/ISO Standard. It fully supports DAP and DSP, minus strong authentication. By default, it contains all of the X.520 Attributes and the X.521 Syntaxes and Object Classes. Additionally, the Annex B DIT Structure can be enforced 🔒.
INTEROPERABILITY 🤝
Interoperability testing will be undertaken as new X.500 products are introduced into the market.
PILOT CONNECTIVITY 🛰️
[No information provided--Ed.]
BUGS 🐛
No major ones at this time.
CAVEATS AND GENERAL LIMITATIONS ⚠️
This is pilot software for organizations who wish to learn about HP's X.500 offering.
INTERNETWORKING ENVIRONMENT 🌐
TP0 or TP4 on 802.3 or X.25
HARDWARE PLATFORMS 💻
HP-9000 800 Minicomputer
HP-9000 300 Workstation
with at least 8 M of internal memory
with 9 M of available disk space for the softwareSOFTWARE PLATFORMS 🧩
Distributed and Supported for HP-UX version 7.0.
AVAILABILITY 📞
Limited Commercial Availability.
For more information in the U.S., call 1-800-752-0900. Outside of the U.S., please contact your local HP Sales Office.
NAME 🎀
INTERACTIVE Systems' X.500 DSA/DSAM INTERACTIVE Systems' X.500 DUA INTERACTIVE Systems Corporation
LAST MODIFIED 🗓️
July, 1991
KEYWORDS 🏷️
API, Commercially Available, DSA/DUA, Multiple Vendor Platforms, OSI Transport, RFC-1006, UNIX
ABSTRACT ✨
The INTERACTIVE Systems X.500 DSA/DSAM and X.500 DUA provide a complete implementation of the OSI X.500 Directory Systems Agent, Directory Systems Agent Manager, and Directory Services User Agent. These software packages allow remote access for Directory Systems Agents and include the following protocols:
- Directory System Protocol (DSP)
- Directory Access Protocol (DAP)
- Common Management Information Protocol (CMIP)
- Remote Operations Service Element (ROSE)
- Association Control Service Element (ACSE)
- Presentation services
- BCS Session services
- DBMS and utilities
- X/Open XDS API (included in the DUA)
These products will be available in Q3 1991 in source code form only 💾.
COMPLETENESS 💯
These products provide:
- a complete implementation of the X.500 distributed Directory
- a DUA with command line UI and X/Open Directory Services (XDS) API
- a Multiprocess DSA with integral high performance DBMS
- remote or local CMIP based DSA management
- a DSA manager that provides on-line DSA monitoring, control, Directory schema manipulation, and DUA functions
- Support for all 1988 X.500, 1988 X.400, and MAP/TOP 3.0 object types and the capability to add new object types
- Conformance with NIST, EWOS, and U.K. GOSIP X.500 Directory profiles
INTEROPERABILITY 🤝
Not available at this time.
PILOT CONNECTIVITY 🛰️
[No information provided--Ed.]
BUGS 🐛
Not available at this time.
CAVEATS AND GENERAL LIMITATIONS ⚠️
Not available at this time.
INTERNETWORKING ENVIRONMENT 🌐
The INTERACTIVE Systems implementation of X.500 Directory Services will operate over both RFC-1006 (in TCP/IP based networks) and over the Retix Local Area and Wide Area Network services.
HARDWARE PLATFORMS 💻
These products are available in source code form only and can be ported to any UNIX-based computers.
SOFTWARE PLATFORMS 🧩
These products operate in the UNIX System V Release 3.2 and System V Release 4 operating systems.
AVAILABILITY 📞
Both products will be available in Q3 1991. For more information, contact:
INTERACTIVE Systems Corporation
1901 North Naper Boulevard
Naperville, IL. 60563-8895
PHONE: (708) 505-9100 extension 232
FAX: (708) 505-9133 Attn.: Jim HancockNAME 🎀
Mac-ISODE Computer Science Department of Massey University
LAST MODIFIED 🗓️
November, 1991
KEYWORDS 🏷️
API, Available via FTP, DSA/DUA, Free, Macintosh, Needs ISODE, RFC-1006, Source
ABSTRACT ✨
Mac-ISODE is a reasonably complete port of ISODE version 7.0. It sits on top of Mac TCP, and its development environment is MPW with the GNU C compiler. See entry for QUIPU/ISODE for a detailed description of the DSA/DUA 🍎.
COMPLETENESS 💯
See entry for QUIPU/ISODE.
INTEROPERABILITY 🤝
See entry for QUIPU/ISODE.
PILOT CONNECTIVITY 🛰️
Not tested.
BUGS 🐛
Macintosh related problems should be sent to PKay@massey.ac.nz.
CAVEATS AND GENERAL LIMITATIONS ⚠️
No testing of the DSA has been done.
INTERNETWORKING ENVIRONMENT 🌐
See entry for QUIPU/ISODE.
HARDWARE PLATFORMS 💻
Macintosh, >1Mb memory, System 6.x
SOFTWARE PLATFORMS 🧩
Macintosh, >1Mb memory, System 6.x
AVAILABILITY 📞
The Macintosh part of the package is freely available. Anonymous FTP from cc-vms1.massey.ac.nz (130.123.1.4) 🆓.
NAME 🎀
MacDish NASA Ames Research Center
LAST MODIFIED 🗓️
July, 1991
KEYWORDS 🏷️
DUA Light Weight Client, Limited Functionality, Macintosh, Needs ISODE, Potentially Unavailable
ABSTRACT ✨
MacIntosh interface which connects to a TCP/IP port attached to dish running on UNIX or other dish-capable host. Uses a point-and-click interface to simplify dish access 🐶.
COMPLETENESS 💯
No authentication, no modify/delete/add ability.
INTEROPERABILITY 🤝
Interoperates with QUIPU/dish
PILOT CONNECTIVITY 🛰️
Being used in the White Pages Pilot Project.
BUGS 🐛
Not complete yet, so there are some bugs (primarily formatting, window management).
CAVEATS AND GENERAL LIMITATIONS ⚠️
Not a terribly capable interface.
INTERNETWORKING ENVIRONMENT 🌐
Pure TCP/IP. Does not require OSI stack support.
HARDWARE PLATFORMS 💻
MacDish runs on Macintosh computers
SOFTWARE PLATFORMS 🧩
MacTCP and MacOS 6.0.x.
AVAILABILITY 📞
Not yet available. Contact is:
Mylene Marquez
MS 233-18
NASA Ames Research Center
Moffett Field, CA 94035-1000
(415) 604-3836NAME 🎀
maX.500 University of Michigan
LAST MODIFIED 🗓️
November, 1991
KEYWORDS 🏷️
Available via FTP, DUA Light Weight Client, Free, Macintosh
ABSTRACT ✨
maX.500 is a Macintosh X.500 directory application useful for displaying and modifying white pages information about people. It runs on top of the DIXIE protocol (described in RFC 1246). maX.500 is currently in production release 1.1 within the University of Michigan and several other places 🦋.
Features include the ability to display and modify the following attributes: title, description, commonName, uid, mail, postalAddress, homePostalAddress, telephoneNumber, facsimileTelephoneNumber, homePhone. Photos can also be displayed 📸. The software also provides access to the finger protocol. Various preferences are user-tailorable, including caching ⚙️.
COMPLETENESS 💯
maX.500 uses the DIXIE protocol to access X.500 and thus is subject to the same completeness restrictions as DIXIE. It provides Read, Search, and Modify capabilities.
INTEROPERABILITY 🤝
Works with the DIXIE server, which works with the QUIPU DSA and DAP library.
PILOT CONNECTIVITY 🛰️
It has been tested (in conjunction with the DIXIE server) in both the Internet and PARADISE pilots.
BUGS 🐛
No outstanding bugs are known. But reports should be sent to x500@itd.umich.edu.
CAVEATS AND GENERAL LIMITATIONS ⚠️
maX.500 is heavily oriented to white pages information, and thus general access to the DIXIE protocol is not provided.
INTERNETWORKING ENVIRONMENT 🌐
maX.500 uses the DIXIE protocol and thus TCP to communicate with the DIXIE server. The Macintosh needs to have MacTCP installed.
HARDWARE PLATFORMS 💻
Mac Plus or newer machine with one megabyte or more of memory.
SOFTWARE PLATFORMS 🧩
Apple System Software 6.0 or above (including System 7), with MacTCP installed. ok that's the whole vibe 🌈💜
AVAILABILITY
okay so this software is openly available 🦋 you can grab it with anonymous FTP from terminator.cc.umich.edu in the directory ~ftp/x500. 🧚
it was developed at the University of Michigan by Mark Smith of the ITD Research Systems Unix Group, and it's covered by the copyright below. the legal bit is important, so I kept it word for word 💅
Copyright (c) 1991 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.
NAME
OSI-DSA
Unisys
LAST MODIFIED
November, 1991
KEYWORDS
API, CLNP, Commercially Available, DSA Only, RFC-1006, Source, Unisys, X.25 💖
ABSTRACT
OSI-DSA is a Directory System agent ✨ for controlled access to the OSI Directory Information Base. It gives full support for the joint ISO/IEC IS-9594 International standard and CCITT X.500 Recommendations 1988 protocols that you need to implement a Directory Information Base spread across a bunch of DSA's. it's giving distributed 🌈
The product also comes with an Administration User interface program, so a human admin can build and maintain the local Directory Information. main character energy 👑
Specific features the Directory System Agent brings to the party:
- (i) Support of the directoryAccessAC and directorySystemAC application contexts (i.e. both Directory Access Protocol (DAP) and Directory System Protocol (DSP)
- (ii) Bind Security levels of none and simple unprotected. 🔐
- (iii) Capability of acting as a first level DSA.
- (iv) Support for chaining and multi-casting where necessary in handling distributed operations. Also supports the return of referrals. 🔁
- (v) Support for all attribute types and syntaxes defined in X.520. Users are also able to define their own attributes and syntaxes. 🎀
- (vi) Support for all the object classes and attribute sets defined in X.521. Users are also able to define their own object classes and attribute sets. Support is also provided for a NAME-BINDING specification, for defining the Directory Information Tree (DIT) structure. 🌸
- (vii) An access control mechanism based on the ISO access control working papers to allow for controlled access and maintenance of Directory entries and attributes. 🫶
- (viii) Logging of errors and significant Directory events, as well as optional trace information. 📝
- (ix) The OSI-DSA utilizes the services of ROSE (X.219) and ACSE (X.217) as defined in clause 8 of X.519 🔥
The Administration program is lowkey a whole toolkit, and it gives you the following functions:
- (i) An interface to each of the basic Directory Operations of Read, Compare, List, Search, Add, Modify, ModifyRDN.
- (ii) A Dump/Load utility to dump the information in the local DIB into an ASCII file and load it again into the DIB from such a file.
- (iii) Knowledge Reference maintenance facilities to Add, Delete Modify and Read all types of Knowledge References.
- (iv) Facilities to control the operation of local Directory processes.
- (v) Control over the level of logging and tracing.
COMPLETENESS
The OSI-DSA provides all functionality defined in, and is fully conformant to, the joint ISO/IEC IS-9594 International standard and CCITT X.500 Recommendations 1988, and the NIST 1988 Stable agreements on Directory Services. literally the full package 🎀
The only exception is that no support is provided for strong authentication or digital signatures. 💀 that's the one gap, so don't sleep on it.
Conformance with respect to clause 9 of X.519:
- (i) The DSA supports both the directoryAccessAC and directorySystemAC application contexts.
- (ii) The DSA is capable of acting as a first-level DSA.
- (iii) The chained mode of operation as defined in X.518 is supported.
- (iv) Bind Security levels of none and simple unprotected are supported.
- (v) All attribute types and syntaxes defined in X.520 are supported. Users are also able to define their own attributes and syntaxes.
- (vi) All the object classes and attribute sets defined in X.521 are supported. Users are also able to define their own object classes and attribute sets. Support is also provided for a NAME-BINDING specification, for defining the Directory Information Tree (DIT) structure.
- (vii) The DSA conforms to all the static requirements defined in clause 9.2.2 of X.519
- (viii) The DSA conforms to all the dynamic requirements defined in clause 9.2.3 of X.519
INTEROPERABILITY
The product was demonstrated at "Interop 91" in San Jose, October 1991, as part of the OSI Showcase demo with several vendors' directory products. it was a whole moment 🌟
Informal interoperability has been achieved against the ISODE 6.0 QUIPU Directory implementation. Interoperability testing against other vendors is in progress. 🤝
Formal interoperability testing is awaiting the soon to be completed OSInet X.500 interoperability test suite.
PILOT CONNECTIVITY
Not tested. 🙈
BUGS
Full customer support is provided via your local Unisys Customer Services Organization. you're never on your own, bestie 🫶
CAVEATS AND GENERAL LIMITATIONS
Results returned via the OSI-DSA are presently limited to 32K in the current release, which is in line with the 1988 NIST agreements.
Patches for the Unix V.4 release may be made available on request to raise this limit to 1Mb. 🍓
The product currently does not provide any support for replication, although development work is in progress, based on the current ISO Draft proposal for Replication. replication is coming, just not yet 🧚
INTERNETWORKING ENVIRONMENT
OSI-DSA runs over all communications environments supported by the Unisys OSI stack product (see Software platforms). Currently these support TP0, TP2, TP3 and TP4 over X.25 and TP4 over CLNP on 802.3 and X.25. Support for RFC1006 over TCP/IP is under development. 🛠️
HARDWARE PLATFORMS
The product is available on all Unisys Unix 6000 Series machines.
Source code is available for portation to non-Unisys platforms. 💜
SOFTWARE PLATFORMS
The product is distributed and supported for Unix System V.3 and Unix System V.4.
On Unix V.3, it requires the Unisys Application Presentation Service OSI stack software (APS), and Unisys Transport Network Service software (TNS). On Unix V.4, it requires the integrated Unisys OSI stack software product (STK). These services are accessed via the ROSLI (ROSE) and APLI (ACSE) programming interfaces, which are currently the subject of standardization efforts by XOpen and Unix International.
A runtime version of either the Informix or Oracle relational database products is required for the Directory Information Base.
AVAILABILITY
Unisys Unix OSI Directory System Agent is commercially available. For information on porting to non-Unisys platforms, contact:
Socs Cappas
Australian Centre for Unisys Software
115 Wicks Rd
North Ryde
N.S.W, 2113
Australia
socs@syacus.acus.oz.au
Ph: 61 2 390 1312For any other information, contact your local Unisys marketing representative or:
Unisys Corporation
Corporate Marketing
Mail Drop B-130
Blue Bell, PA 19424
USANAME
OSI-DUA
Unisys
LAST MODIFIED
November, 1991
KEYWORDS
API, CLNP, Commercially Available, DUA Only, RFC-1006, Source, Unisys, X.25 🌈
ABSTRACT
OSI-DUA is a Unix C Program interface library. 💅 It lets OSI or user applications access the services of an X.500 conformant Directory, by making calls to a library of C routines. it's so iconic
Specific features this program interface library brings are as follows:
- (i) Connection to any remote X.500 conformant DSA via an OSI stack, or connection to a co-resident Unisys OSI DSA via IPC mechanisms. 🔌
- (ii) All operations defined in the directoryAccessAC application context (Bind, UnBind, Read, Compare, Search, List, AddEntry, ModifyEntry, ModifyRDN, Abandon, DeleteEntry).
- (iii) Directory Bind security levels of none and simple unprotected.
- (iv) Execution of both blocking and non-blocking operations. (A non-blocking call to the library will return immediately, allowing for results to be obtained once the operation has completed) ⚡
- (v) Acceptance of multiple concurrent non-blocked operations on the one user session. 🦋
- (vi) The DUA utilizes the services of ROSE (X.219) and ACSE (X.217) as defined in clause 8 of X.519
COMPLETENESS
When communicating with a Remote DSA, the DUA library is fully conformant with the Directory Access Protocol detailed in the X.500 Recommendations/IS-9594 standards. ✨
Conformance with respect to clause 9 of X.519:
- (i) All operations defined in the directoryAccessAC application context (Bind, UnBind, Read, Compare, Search, List, AddEntry, ModifyEntry, ModifyRDN, Abandon, DeleteEntry) are supported.
- (ii) Directory Bind security levels of none and simple unprotected are supported.
- (iii) The directoryAccessAC application context is supported as specified in clause 7 of X.519.
- (iv) The DUA conforms to the mapping onto used services as defined in clause 8 of X.519.
INTEROPERABILITY
Informal interoperability has been achieved against the ISODE 6.0 QUIPU Directory implementation. Interoperability testing against other vendors is in progress. 🫶
Formal interoperability testing is awaiting the soon to be completed OSInet X.500 interoperability test suite.
PILOT CONNECTIVITY
Not tested. 🙈
BUGS
Full customer support is provided via your local Unisys Customer Services Organisation. 💖
CAVEATS AND GENERAL LIMITATIONS 💅
Okay bestie, so the OSI-DUA does not handle referrals automatically 🙅♀️ The interface library won't do it for you. BUT there are interface routines that let your user application act on referrals itself, which is kinda clutch ✨
The OSI-DUA has a proprietary C programming interface 💻 An XOpen XDS conformant interface is still in development 🚧
INTERNETWORKING ENVIRONMENT 🌐
OSI-DUA runs over every communications environment the Unisys OSI stack product supports (see Software platforms). Right now that means TP0, TP2, TP3 and TP4 over X.25, plus TP4 over CLNP on 802.3 and X.25. Support for RFC1006 over TCP/IP is still cooking 🍳
HARDWARE PLATFORMS 🖥️
The product is available on all Unisys Unix 6000 Series machines.
Source code is available for porting to non-Unisys platforms 💖
SOFTWARE PLATFORMS 💾
The product is distributed and supported for Unix System V.3 and Unix System V.4.
On V.3 it needs the Unisys Application Presentation Service OSI stack software (APS) and the Unisys Transport Network Service software (TNS). On V.4 it needs the integrated Unisys OSI stack software product (STK). Both are accessed through the ROSLI (ROSE) and APLI (ACSE) programming interfaces, which are currently the subject of standardization efforts by XOpen and Unix International 🤓
AVAILABILITY 🛒
The Unisys Unix OSI Directory System Agent is commercially available. For info on porting to non-Unisys platforms, contact:
Socs Cappas
Australian Centre for Unisys Software
115 Wicks Rd
North Ryde
N.S.W, 2113
Australia
socs@syacus.acus.oz.au
Ph: 61 2 390 1312For any other info, contact your local Unisys marketing representative or:
Unisys Corporation
Corporate Marketing
Mail Drop B-130
Blue Bell, PA 19424
USANAME 📛
POD
Brunel University
LAST MODIFIED 📅
November, 1991
KEYWORDS 🏷️
Available via FTAM, Available via FTP, DUA Only, Free, Included in ISODE, Limited Functionality, Multiple Vendor Platforms, Needs ISODE, RFC-1006, Source, UNIX
ABSTRACT 📝
POD (POpup Directory) is an X.500 DUA interface for the X Window System 🪟 POD is a first attempt at a multiwindow directory tool. It offers a simplified interface to the basic X.500 operations of read, search, list and modify entry.
POD does not provide any sophisticated access to the DSA. Operations are performed synchronously. The Directory is presented as-is, i.e. a hierarchical tree of information, so the user has to "navigate" the DIT to find what they need 🌳
POD is available as part of the ISODE release from version 6.0 onwards ✨
COMPLETENESS ✅
88 standard: strong authentication not implemented
INTEROPERABILITY 🤝
Believed to be compliant, though untested.
PILOT CONNECTIVITY 🛫
DUA Connectivity: POD is in use in many directory pilots, certainly including PARADISE and the Internet.
BUGS 🐛
Bugs to x500@brunel.ac.uk
INTERNETWORKING ENVIRONMENT 🌐
TP0 over TCP/IP (as ISODE)
HARDWARE PLATFORMS 🖥️
Most UNIX machines
SOFTWARE PLATFORMS 💾
UNIX
MIT X libraries (release 11 version 4)
ISODE/QUIPU libraries (version 6.7 upwards)AVAILABILITY 🛒
POD is openly available as part of the ISODE release. Sources are freely available for commercial or non-commercial use from:
src.brunel.ac.uk [134.83.128.3]Files are:
x500/pod.tar.Z
x500/sd.tar.ZContacts:
Andrew.Findlay@brunel.ac.uk +44 1 895 74000 x 2512
Damanjit.Mahl@brunel.ac.uk +44 1 895 74000 x 2946
x500@brunel.ac.ukPostal Address:
Andrew Findlay
Computer Centre
Brunel University
Cleveland Road,
Uxbridge, Middlesex
UB8 3PH
United KingdomNAME 📛
psiwp
Performance Systems International Inc.
LAST MODIFIED 📅
July, 1991
KEYWORDS 🏷️
Available via FTP, DUA Light Weight Client, DUA Only, Free, Limited Functionality, Macintosh, Needs ISODE, Source
ABSTRACT 📝
psiwp is a Macintosh Front End to the White Pages service 🍎 It's a graphical user interface implementing a partial-DUA, and it's based on the ISODE QUIPU X.500 implementation and the Directory Assistance Protocol (DAP) 💜
psiwp is a Macintosh application tailored specifically for easy access to the Directory, for performing White Pages searches. It implements the User-Friendly Naming scheme developed in the IETF OSI-DS Working Group.
psiwp implements a Directory Assistance Protocol (DAP) client.
COMPLETENESS ✅
Compliant with X.500 standards to the extent that the QUIPU implementation is.
INTEROPERABILITY 🤝
Successfully interoperates with QUIPU DSAs
PILOT CONNECTIVITY 🛫
Being used in the White Pages Pilot Project.
BUGS 🐛
Support is available (for registered users of psiwp only) from psiwp-help@psi.com.
CAVEATS AND GENERAL LIMITATIONS ⚠️
psiwp is not a general-purpose DUA. It was designed as a special-purpose front-end for White Pages searches, so in the interests of simplicity it does not provide the full range of functionality the X.500 standard supports. 🎯
A Directory Assistance server (available as part of the ISODE distribution) must also be run by sites that don't want to run psiwp against either of the two White Pages Pilot Project service machines, wp1.psi.net and wp2.psi.net.
INTERNETWORKING ENVIRONMENT 🌐
Runs on Macintoshes as a Finder or MultiFinder application.
HARDWARE PLATFORMS 🖥️
Runs on Macintoshes that support MacTCP. Requires an ethernet board or AppleTalk connectivity. At least 1MB of memory is required, and while psiwp will run on most forms of Macintosh, a Mac-II is recommended 🌟
SOFTWARE PLATFORMS 💾
Requires MacTCP 1.0 or later, and Finder (or Multifinder) 6.x. Finder 7.0 WILL NOT WORK 🚫 Requires ISODE Version 6.8 or later.
AVAILABILITY 🛒
psiwp is shareware, available for anonymous ftp from uu.psi.com [136.161.128.3] in pilot/PSIWP.Hqx. A nominal fee is charged upon registration as a PSIWP user 💸
Source code to the psiwp application may be licensed from PSI Inc. as part of PSI's Software Source Distribution (SSD). Email to:
ssd-info@psi.comwill get an automatic response containing info on the SSD. Ordering info can be obtained by emailing:
ssd-order@psi.comor by contacting PSI at:
Performance Systems International Inc.
11800 Sunrise Valley Drive
Suite 1100
Reston, Virginia 22091.
1.703.620.6651
1.800.82PSI82 (1.800.827.7482)
1.703.620.4586 (fax)NAME 📛
QUIPU
ISODE
LAST MODIFIED 📅
July, 1991
KEYWORDS 🏷️
API, Available via FTAM, Available via FTP, CLNP, DEC Ultrix, DSA/DUA, Free, HP, MIPS, Macintosh, Multiple Vendor Platforms, OSI Transport, RFC-1006, Source, Sun, UNIX, X Window System, X.25
ABSTRACT 📝
QUIPU is part of ISODE, an openly available implementation of the upper layers of OSI 🌸 QUIPU provides an X.500 Directory System Agent (DSA) and a set of Directory User Agents (DUA) aimed at different terminal types and modes of interaction
QUIPU was first publicly demonstrated at ESPRIT in November 1988. It's being used extensively in the European PARADISE project, the White Pages Pilot Project and the Australian pilot. A QUIPU DSA is being used at the ROOT node of the Pilot DIT, and is being used as most country-level DSAs 🌍
QUIPU provides its own solutions to areas not specified by the 1988 standards, such as replication and access control 🔐
COMPLETENESS ✅
QUIPU is aligned to the 1988 ISO IS and the NIST OIW Directory Implementors Guide Version 1, with the following exceptions:
- Strong authentication is not implemented.
- 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 that 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 identifieris not recognized unless thealiasobject 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.
INTEROPERABILITY 🤝
QUIPU has interworked with a number of other implementations, and has no known problems in such interworking 🎉
PILOT CONNECTIVITY 🛫
QUIPU is in use in many directory pilots, certainly including PARADISE and the White Pages Pilot Project.
BUGS 🐛
Problems should be reported to quipu-support@cs.ucl.ac.uk.
CAVEATS AND GENERAL LIMITATIONS ⚠️
None.
INTERNETWORKING ENVIRONMENT 🌐
QUIPU users TP0 over X.25, CONS and TCP (using RFC-1006), or TP4 over SunLink OSI.
The DSA knows about the problems of unconnected networks and makes chain/refer choices based on the network connectivity. Using this, an X.25-only DSA can access data from an Internet-only DSA by chaining operations through a DSA connected to both networks 🧠
HARDWARE PLATFORMS 🖥️
[No information provided--Ed.]
SOFTWARE PLATFORMS 💾
ISODE and QUIPU run on native Berkeley (4.2, 4.3) and AT&T System V, in addition to various other UNIX-like operating systems. No kernel modifications are required 🙌
AVAILABILITY 🛒
ISODE is not proprietary, but it is not in the public domain. This was necessary to include a "hold harmless" clause in the release. The upshot of all this is that anyone can get a copy of the release and do anything they want with it, but no one takes any responsibility whatsoever for any (mis)use 🫶
Skipping SD and UCOM.X 500 since those were already covered. There's no section 6.0 in this chunk, so I haven't invented one. 🎀
DISTRIBUTION SITES 📦✨
Okay so the FTP or FTAM distributions of ISODE-7.0 come as 3 files. The source and main ISODE-7.0 distribution is the file isode-7.tar.Z, which is about 4.7MB. 💖
LaTeX source for the entire document set is in the isode-7-doc.tar.Z file (3.5MB). A list of documents is in the doc/ directory of the source tree. 📚
A Postscript version of the five volume manual is in the isode-7-ps.tar.Z file (4.7MB). 🌸
1. FTP
If you can FTP to the Internet, use anonymous FTP to uu.psi.com [136.161.128.3] to grab the files in BINARY mode from the isode/ directory. 🦋
2. NIFTP
If you run NIFTP over the public X.25 or over JANET, and you're registered in the NRS at Salford, you can use NIFTP with username "guest" and your own name as the password to access UK.AC.UCL.CS and retrieve the files from the <SRC> directory. 🧚
3. FTAM on the JANET, IXI or PSS
The sources are available by FTAM from UCL over X.25 using:
JANET (DTE 00000511160013),
IXI (DTE 20433450420113) or
PSS (DTE 23421920030013)All of these use TSEL "259" (ASCII encoding). Use the "anon" user-identity and retrieve the files from the src/ directory. The file service is provided by the FTAM implementation in ISODE 6.0 or later (IS FTAM). 🫶
4. NORTH AMERICA
For mailings in NORTH AMERICA, send a check for 375 US Dollars to:
University of Pennsylvania
Department of Computer and Information Science
Moore School
Attn: David J. Farber (ISODE Distribution)
200 South 33rd Street
Philadelphia, PA 19104-6314
US
+1 215 898 8560Specify either (a) 1600bpi 1/2-inch tape, or (b) Sun 1/4-inch cartridge tape. The tape will be written in tar format and returned with a documentation set. Do not send tapes or envelopes. Documentation only is the same price. 💅
5. EUROPE (tape and documentation)
For mailings in EUROPE, send a cheque or bankers draft and a purchase order for 200 Pounds Sterling to:
Department of Computer Science
Attn: Natalie May/Dawn Bailey
University College London
Gower Street
London, WC1E 6BT
UKFor information only:
Telephone: +44 71 380 7214
Fax: +44 71 387 1397
Telex: 28722
Internet: natalie@cs.ucl.ac.uk, dawn@cs.ucl.ac.ukSpecify either (a) 1600bpi 1/2-inch tape, or (b) Sun 1/4-inch cartridge tape. The tape will be written in tar format and returned with a documentation set. Do not send tapes or envelopes. Documentation only is the same price. 🍓
7. EUROPE (tape only)
Tapes without hardcopy documentation can be obtained via the European Forum for Open Systems (EurOpen, formerly known as EUUG). The ISODE 7.0 distribution is called EurOpenD14. 🌈
EurOpen Software Distributions
c/o Frank Kuiper
Centrum voor Wiskunde en Informatica
Kruislaan 413
1098 SJ Amsterdam
The NetherlandsFor information only:
Telephone: +31 20 5924121 (or: +31 20 5929333)
Telex: 12571 mactr nl
Telefax: +31 20 5924199
Internet: euug-tapes@cwi.nlSpecify one of:
- 1600bpi 1/2-inch tape: 140 Dutch Guilders
- Sun 1/4-inch cartridge tape (QIC-24 format): 200 Dutch Guilders
If you require DHL this is possible and will be billed through. Note that if you are not a member of EurOpen, there is an additional handling fee of 300 Dutch Guilders (please enclose a copy of your membership or contribution payment form when ordering). Do not send money, cheques, tapes or envelopes, you will be invoiced. 👑
8. PACIFIC RIM
For mailings in the Pacific Rim, send a cheque for 300 dollars Australian to:
Isode Distribution
(Attn Andrew Waugh)
723 Swanston St,
Carlton, VIC 3053
AustraliaFor information only:
Telephone: +61 3 282 2615
Fax: +61 3 282 2600
Internet: ajw@mel.dit.csiro.auPlease specify the media you desire: (a) 1/2-inch tape at 1600bpi, 3200bpi, or 6250bpi; or (b) Sun 1/4-inch cartridge tape in either QIC-11, QIC-24 or QIC-150 format; or (c) Exabyte 2.3 Gigabyte or 5 Gigabyte format. The tape will be written in tar format and returned with a documentation set. Do not send tapes or envelopes. Documentation only is the same price. ✨
NAME 🦋
ud University of Michigan
LAST MODIFIED 🗓️
November, 1991
KEYWORDS 🏷️
Available via FTP, DUA Light Weight Client, Free, Source, UNIX, Multiple Vendor Platforms
ABSTRACT 💭
ud is a command line based directory app that's super useful for displaying and modifying white pages info about people. It runs on top of the DIXIE protocol (described in RFC 1246). ud was developed to run under Unix and is currently in beta release within U-M staff and a few other places that have heard of it. 🌸
Features include the ability to display and modify the following attributes: title, description, commonName, uid, mail, postalAddress, homePostalAddress, telephoneNumber, facsimileTelephoneNumber, homePhone. 💅
COMPLETENESS 🧩
ud uses the DIXIE protocol to access X.500, so it's subject to the same completeness restrictions as DIXIE. It provides Read, Search, and Modify capabilities. 🔥
INTEROPERABILITY 🤝
Works with the DIXIE server, which works with the QUIPU DSA and DAP library. 💜
PILOT CONNECTIVITY ✈️
It has been tested (in conjunction with the DIXIE server) in both the Internet and PARADISE pilots. 🌈
BUGS 🐛
No outstanding bugs are known. But reports should be sent to x500@itd.umich.edu. 🙈
CAVEATS AND GENERAL LIMITATIONS ✨
ud is heavily oriented to white pages information, so general access to the DIXIE protocol is not provided 🙈
INTERNETWORKING ENVIRONMENT 🌸
ud uses the DIXIE protocol, and thus TCP, to talk to the DIXIE server 🫶
HARDWARE PLATFORMS 💜
ud is known to run on Sun 3s, Sun 4s, and Vaxen 🖥️
SOFTWARE PLATFORMS 🍓
SunOS 3.5, SunOS 4.1.1, BSD 4.3 Unix 💻
AVAILABILITY 🦋
This software is openly available 🎉 You can grab it by anonymous FTP from terminator.cc.umich.edu in the directory ~ftp/x500.
This software was developed at the University of Michigan by Bryan Beecher of the ITD Research Systems Unix Group, and it's subject to the following copyright 📜
Copyright (c) 1991 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 💖
NAME 🎀
VMS-ISODE Computer Science Department of Massey University
LAST MODIFIED 🌈
November, 1991
KEYWORDS 🔥
API, Available via FTP, DSA/DUA, Free, Needs ISODE, RFC-1006, Source, VMS
ABSTRACT ✨
VMS-ISODE is a reasonably complete port of ISODE version 7.0 👑 It sits on top of several TCP implementations for VMS (UCX, Multinet, CMU and Wollongong) and also PSI X.25 💅
See the entry for QUIPU/ISODE for a detailed description of the DSA/DUA 🫶
COMPLETENESS 🦋
See entry for QUIPU/ISODE 💜
INTEROPERABILITY 🌸
See entry for QUIPU/ISODE 🍓
PILOT CONNECTIVITY 🙈
Not tested.
BUGS 💀
VMS related problems should be sent to PKay@massey.ac.nz 📨
CAVEATS AND GENERAL LIMITATIONS 🧚
None.
INTERNETWORKING ENVIRONMENT ⭐
See entry for QUIPU/ISODE.
HARDWARE PLATFORMS 💻
VAX hardware 🖥️
SOFTWARE PLATFORMS 🌈
VMS v5.0 or greater
AVAILABILITY 💖
The VMS part of the package is freely available 🎉 Anonymous FTP from cc-vms1.massey.ac.nz (130.123.1.4).
NAME 🦋
VTT X.500 Technical Research Centre of Finland
LAST MODIFIED 🌸
November, 1991
KEYWORDS 💅
API, Apollo, CLNP, Commercially Available, DSA/DUA, IBM PC, Multiple Vendor Platforms, RFC-1006, Sun, X.25
ABSTRACT 👑
VTT X.500 is seriously packed 🔥 It contains a full distributed DSA and a subroutine call to dua (call_dua(parameters)). That subroutine gets linked into the user's process. There are two ways for dua to talk to our DSA, called dsacvops: a fast communication through shared memory, for dua and dsa living in the same computer, and a complete OSI-stack for communicating in DAP-protocol with remote dsa's, which can be any implementation of X.500 dsa, not necessarily dsacvops. The DSA talks to other dsas through a full OSI-stack with protocol DSP, or with a shorter stack when both dsas are dsacvops-processes. dsacvops contains a special purpose database, DIB.
VTT X500 also does caching of read and search results, access controls (as in Annex F of X.501), object classes and attribute types as in X.520 and X.521, and simple authentication with unprotected passwords in bind. The network level can be X.25 or TCP/IP. There are test duas, duacvops and duauser, with a simple user interface. Certificates for strong authentication are included in x509dua and x509duacvops. VTT X500 is realized with the program development tools CVOPS and CASN. The code is in C-language and uses UNIX System V. The code is fairly easy to port to other operating systems. VTT X500 was made for the Smail e-mail product of Nokia Data Systems 🧚
COMPLETENESS 🌈
Complete DAP and DSP of 1988 X.500 Recommendations are implemented 🎀 There are the following omissions: multicasting is not implemented, strong authentication of calls to dsa (optional signing of DAP and DSP-calls, strong authentication in bind, security error, security parameters in common arguments), T61 alternative in CASE IGNORE and CASE EXACT STRING, Criteria-syntax, and TeletexTerminalIdentifier syntax 🙈
INTEROPERABILITY 💜
Interoperability with ISODE QUIPU 6.0 has been tested, but no formal test suite was used 🫶
PILOT CONNECTIVITY 🌸
Not tested: it should work in principle, but it has not been tested 🤞
BUGS 🍓
No known bugs at the moment ✨
CAVEATS AND GENERAL LIMITATIONS 💀
Object identifiers for object classes and attribute types can currently have only the form {2 5 6 x} or {2 5 4 x}, where x<256. Changing the directory schema requires code writing 😭
INTERWORKING ENVIRONMENT 🔥
RFC-1006 with TCP/IP, TP0 with X.25, and TP4 with X.25 available by agreement 🦋
HARDWARE PLATFORMS 💻
Sun-3, Sun 386, Apollo, and a version of dua for IBM PC, which will be forthcoming in 1991 🖥️
SOFTWARE PLATFORMS 🌈
Unix System V. Our own database and database management system. Uses the CVOPS protocol development tool 💅
AVAILABILITY 👑
Commercially available 💖 Contact:
Asko Vilavaara
Telecommunications Laboratory
Technical Research Centre of Finland
Otakaati 7 B, 02150 Espoo, FINLAND
Telephone: +358 0 456 5641
FAX: +358 0 455 0115
E-mail: Asko.Vilavaara@tel.vtt.fi
Henryka Jormakka
Telecommunications Laboratory
Technical Research Centre of Finland
Otakaati 7 B, 02150 Espoo, FINLAND
Telephone: + 358 0 456 5662
FAX: +358 0 455 0115
E-mail: Henryka.Jormakka@tel.vtt.fiNAME 🌸
WIN(tm)/DS The Wollongong Group, Inc.
LAST MODIFIED 💜
November, 1991
KEYWORDS 🍓
API, CLNP, Commercially Available, DSA/DUA, Multiple Vendor Platforms, OSI Transport, RFC-1006, Source, UNIX, X Windows, X.25
ABSTRACT 🎀
WIN/DS is an implementation of OSI Directory Services aligned with the ISO 1988 X.500 IS and NIST Stable Implementors Agreements 👑 WIN/DS includes both a Directory User Agent (DUA) and a Directory System Agent (DSA). The product supports all Directory Services operations, object classes and attributes. It provides support for managing the Directory Information Tree (DIT), with facilities to control structure rules and their enforcement. WIN/DS also provides solutions to areas not specified by the 1988 standards, such as replication and access control 🔥
COMPLETENESS 🦋
Wollongong closely follows the NIST OIW Stable Implementors' Agreements. See also QUIPU 💅
INTEROPERABILITY 🌈
WIN/DS has interoperated with other X.500 implementations at trade shows (CeBIT and Interop) and at strategic customer sites 🫶
PILOT CONNECTIVITY ⭐
[No information provided--Ed.]
BUGS 💖
Requests for product enhancement and modification should be sent to support@twg.com 📨
CAVEATS AND GENERAL LIMITATIONS 🙈
[No information provided--Ed.]
INTERNETWORKING ENVIRONMENT 🧚
TCP/IP (RFC 1006)
TP0
TP2
TP4
OSI TP[0/2,4] & TCP/IP dual stack gateway
Ethernet
X.25
Ethernet/X.25 gateway
ES-IS
IS-IS
Interface to OSI transport via the TLI
Interface to the Data Link Layer via the DLPI
STREAMS and DLPI compliant 3rd party network interfacesHARDWARE PLATFORMS 💻
End-user binary product:
- 386/i486 with UNIX System V (AT&T, Intel, INTERACTIVE, SCO)
- Apple Macintosh with A/UX
Portable source code:
- UNIX SVR3, SVR4, BSD
- single- or multi-processor 680x0, 880000, 386/i486
SOFTWARE PLATFORMS 🌈
See above 🍓
AVAILABILITY 👑
WIN/DS is commercially available 💰 from:
The Wollongong Group, Inc.
1129 San Antonio Road
Palo Alto
CA 94303
Sales and Information: :415/962-7100 California
703/847-4500 Wash D
+32-2-718-0311 BelgiumNAME 💅
X.500 DUA process 3Com Corporation
LAST MODIFIED 🌸
July, 1991
KEYWORDS 🔥
CLNP, Commercially Available, DUA Only, Multiple Vendor Platforms, X Window System, X.25, 3Com
ABSTRACT 🎀
The DUA process runs on 3Com's dual-stack OSI/TCP terminal server, which was scheduled to be released in mid-June 1991 ✨ It provides Presentation Address resolution for names, on behalf of the VTP application. When the user attempts an outgoing connection ("VTP <name>" or "connect <name>"), <name> gets mapped to its Presentation Address 🦋
The DUA process supports the AddEntry, RemoveEntry, and Search operations 🧚 Via a menu-driven command, the system administrator can configure any of these operations, then send the request to the DSA. They would use the AddEntry operation to enter a resource name and its corresponding physical address in the DIB, the DeleteEntry operation to remove the name and its physical address, and the Search operation (with "filter" as an option) for a display of all registered names or, given a name, a display of that name's physical address 💜
Regarding unbinding from a DSA, the system administrator could use an UnbindDSA command or set a timer which, once expired, would automatically perform the unbinding. The binding to a DSA, on the other hand, is transparent, provided the system administrator has set a DSA address. The binding is triggered by either an outgoing connection attempt or an operation request sent to the DSA ⭐
The schema supported by the DUA consists of the following sequence of object classes: Country, Organization, OrganizationalUnit (up to 3 levels of OrganizationalUnits are allowed), ApplicationProcess, and ApplicationEntity. Their respective attributes are CountryName, OrganizationName, OrganizationUnitName, CommonName, and PresentationAddress. The CommonName of the ApplicationEntity is always "vt" for VTP, and it's transparent to the system administrator 👑
COMPLETENESS 💖
Compliance with the ISO/IEC 9594 standards 🎀 Handling referrals not yet implemented 🙈 Schema supported: Country, Organization, OrganizationalUnit, ApplicationProcess, and ApplicationEntity 🌈 Authentication not supported 💀
INTEROPERABILITY 🫶
Interoperability with the ISODE QUIPU Directory Service and any DSA which strictly meets the ISO/IEC 9495 standards 🦋
BUGS 🍓
[No information provided--Ed.]
CAVEATS AND GENERAL LIMITATIONS 😭
Deleting an entry will fail if the DUA is interacting with a 6.0 based version of QUIPU. This is a bug in QUIPU, and the version 7.0 release will have it fixed 🔧
Adding a CountryName is disallowed if the DUA is bound to QUIPU. This decision was made because, to add a country in QUIPU, one needs to bind as the manager of the DSA holding the root EDB file, and such information may not always be available to the system administrator. Also, our binding is done transparently 🔥
INTERNETWORKING ENVIRONMENT 🌈
OSI environments with the complete OSI stack, supporting CLNS and TP4 🧚
HARDWARE PLATFORMS 💻
3Com's OSI/TCP CS/2000 and CS/2100 🖥️
SOFTWARE PLATFORMS 👑
The "SW/2000-OT Vers 1.0" software runs on 3Com's OSI/TCP CS/2000 and CS/2100, both stand-alone systems 💅
AVAILABILITY 🌸
The dual-stack OSI/TCP terminal server and its "SW/2000-OT Vers 1.0" software are available from:
3Com Corporation
5400 Bayfront Plaza
Santa Clara, CA 95054
Information: Cyndi Jung
(408) 764-5173
cmj@3Com.COMNAME 🦋
Xdi Bellcore
LAST MODIFIED 💜
November, 1991
KEYWORDS ✨
DUA Only, DUA Connectivity, Available via FTP, Free, Source, Needs ISODE, X Window System, RFC-1006, CLNP, UNIX, X.25
ABSTRACT ✨
Okay so Xds is a DUA made for people who know little or nothing about X.500 💅. Picture a receptionist getting asked, "Could I have the telephone number of Andrew who works in Research?" 📞 Xds is built for exactly that. The screen gets customized for the organization, and results show up as a business card 💼. You can also choose what info gets displayed 🎀.
COMPLETENESS 🙈
Xds doesn't give users access to every X.500 service. Instead, it uses X.500 services to do the specific jobs it was designed for 🧚
Conforms to section 9 of X.519.
INTEROPERABILITY 🔥
Only tested against the QUIPU (ISODE) DSA.
No known bugs 🙌 but we'd genuinely love to hear about any you find! Reach out to Andrew Waugh at ajw@mel.dit.csiro.au.
PILOT CONNECTIVITY 🌸
Not tested.
BUGS 🐞
No known bugs 🙌 but we'd love to hear about any you find! Reach out to Andrew Waugh at ajw@mel.dit.csiro.au.
CAVEATS AND GENERAL LIMITATIONS 🦋
Users can only bind as the anonymous user. That's the one big catch 👀
INTERNETWORKING ENVIRONMENT 🌈
Uses the QUIPU (ISODE 7.0) libraries.
HARDWARE PLATFORMS 💻
Xds runs on Sun SPARCstations 🌞. We haven't tested Xds on other hardware platforms, but it should run on any other hardware that supports ISODE-7.0 and X Windows.
SOFTWARE PLATFORMS 🧩
Xds requires ISODE-7.0 and X 11 Version 4 with the Athena Widgets.
AVAILABILITY 🎁
The Xds software is free to any non-commercial site, as long as:
i) they don't pass the code on to any other site (they should ask the other site to contact us directly instead) 🙅♀️
ii) they don't make money from using or selling the software 💸
iii) they tell us about any problems or possible improvements they'd like to see 🫶
Commercial sites should contact us.
For further information, contact:
Andrew Waugh
CSIRO Division of Information Technology
723 Swanston St
Carlton VIC 3053
AUSTRALIA
Phone +61 3 282 2615
Fax +61 3 282 2600
Email ajw@mel.dit.csiro.auNAME 🏷️
xdua CSIRO Division of Information Technology
LAST MODIFIED 📅
November, 1991
KEYWORDS 🔑
DUA Only, Free, Multiple Vendor Platforms, Needs ISODE, source, Sun, X Window System
ABSTRACT ✨
The xdua is a DUA designed for DSA managers who know enough X.500 to manipulate the Directory Information Tree (DIT) 🌳. It's typically used to maintain the information stored on a DSA. It has a Macintosh style interface 🍎, which makes browsing the DIT hierarchy way simpler. Users can move between DIT levels with a standard mouse 🖱️. The xdua supports the X.500 operations of add, modify, delete, search and show 💅.
COMPLETENESS 🙈
It uses the QUIPU (ISODE) dsap interface to provide the X.500 operations.
Conforms to section 9 of X.519.
INTEROPERABILITY 🔥
Only tested against the QUIPU (ISODE) DSA.
PILOT CONNECTIVITY 🌸
[No information provided--Ed.]
BUGS 🐞
No known bugs 🙌 but we'd love to hear about any you find! Reach out to Brian May at Brian.May@mel.dit.csiro.au.
CAVEATS AND GENERAL LIMITATIONS 🦋
The executable is large because it uses the X11R4 and DiSh libraries 📦. The xdua is still in the testing phase 🧪.
INTERNETWORKING ENVIRONMENT 🌈
As supported by ISODE.
HARDWARE PLATFORMS 💻
The xdua runs on Sun SPARCstations 🌞 and probably on other hardware that supports ISODE-7.0 and X Windows.
SOFTWARE PLATFORMS 🧩
The xdua requires ISODE-7.0 and X 11 Version 4 with the Athena Widgets and the Xt toolkit.
AVAILABILITY 🎁
We'll distribute it free to any non-commercial site, as long as:
i) they don't pass the code on to any other site (they should ask the other site to contact us directly instead) 🙅♀️
ii) they don't make money from using or selling the software 💸
iii) they tell us about any problems or possible improvements they'd like to see 🫶
Commercial sites should contact us directly. For further information, contact:
Brian May
CSIRO Division of Information Technology
723 Swanston St,
Carlton,
Victoria 3053,
Australia
Phone +61 3 282 2613
Fax +61 3 282 2600
Email Brian.May@mel.dit.csiro.auNAME 🏷️
XLU Brunel University
LAST MODIFIED 📅
November, 1991
KEYWORDS 🔑
Available via FTAM, Available via FTP, DUA Only, Free, Multiple Vendor Platforms, Needs ISODE, RFC-1006, Source, UNIX
ABSTRACT ✨
XLU (X LookUp) is an X.500 DUA interface for the X Window System 🪟. It was developed from POD, and it can be configured for lots of different styles of interaction 🎨. Example configurations are given for a single window and for multiple windows (POD-like) use.
XLU implements the `User-Friendly Naming' search strategy and also has a form-filling search mode 📝. Asynchronous directory operations are used ⚡.
Full add and modify functions are provided, and you can tailor the modify screen to show simple subsets of the available attributes 🎀.
At the time of writing (October 1991), XLU was in beta test 🧪.
COMPLETENESS 🙈
88 standard: strong authentication not implemented.
INTEROPERABILITY 🔥
Believed to be compliant, though untested.
PILOT CONNECTIVITY 🌸
DUA Connectivity: In use at Brunel and some other sites in the UK and PARADISE pilots 🇬🇧.
BUGS 🐞
Bugs go to x500@brunel.ac.uk.
CAVEATS AND GENERAL LIMITATIONS 🦋
[No information provided--Ed.]
INTERNETWORKING ENVIRONMENT 🌈
TP0 over TCP/IP (and others as ISODE).
HARDWARE PLATFORMS 💻
Most UNIX machines.
SOFTWARE PLATFORMS 🧩
UNIX MIT X libraries (release 11 version 4) ISODE/QUIPU libraries (version 7.0 upwards)
AVAILABILITY 🎁
Sources are freely available for commercial or non-commercial use 💖. Contacts:
Andrew.Findlay@brunel.ac.uk +44 1 895 274000 x 2512
Damanjit.Mahl@brunel.ac.uk +44 1 895 274000 x 2946
x500@brunel.ac.ukPostal Address:
Andrew Findlay
Computer Centre
Brunel University
Cleveland Road,
Uxbridge, Middlesex
UB8 3PH
United KingdomAnonymous FTP:
src.brunel.ac.uk
x500/xlu.tar.ZNAME 🏷️
XT-DUA X-Tel Services Limited
LAST MODIFIED 📅
November, 1991
KEYWORDS 🔑
DUA Only, Multiple Vendor Platforms, Needs ISODE-7.0, RFC-1006 X Window System, CLNP, X.25, OSI Transport, Sun, Unix, Commercially Available.
ABSTRACT ✨
XT-DUA gives you an X-Windows based user interface to the X.500 directory 🪟. Both Motif and OpenLook styles are supported 🎨.
XT-DUA comes in two forms:
- a browsing tool
- a management tool
Browsing features include:
- History, which gives quick access to previously referenced parts of the DIT 🕰️
- Customizable entry display, which lets you show subsets of attributes when displaying an entry 🎀
- User Friendly Name (UFN) based searching 🔍
- Hypertext-like navigation 🔗
- Support for applicationEntities, e.g. starting up an ftam session 📂
- User friendly names for attributes 🏷️
- Support for photo and audio attributes 📸
- Attribute value on the scanline ✨
- Intelligent choice of entries to display when moving to a new location in the DIT 🧠
Management features include:
- Creating new entries ➕
- Modifying existing entries (including RDN), based on the Quipu EDB format 🛠️
- Deleting entries 🗑️
- A friendly editor for modifying Quipu ACLs 💅
- Rebinding, authenticated and to a named DSA 🔐
- Full configuration of DAP request parameters ⚙️
COMPLETENESS 🙈
XT-DUA provides access to all the X.500 DAP operations. Protocol completeness is as for QUIPU-7.0.
INTEROPERABILITY 🔥
As for the QUIPU-7.0.
PILOT CONNECTIVITY 🌸
Full DUA Connectivity to the X.500 Pilot 🌍.
BUGS 🐞
No known bugs 🙌.
CAVEATS AND GENERAL LIMITATIONS 🦋
None.
INTERNETWORKING ENVIRONMENT 🌈
As for the QUIPU-7.0.
HARDWARE PLATFORMS 💻
As for the QUIPU-7.0.
SOFTWARE PLATFORMS 🧩
As for the QUIPU-7.0, with the addition of X Windows and either Motif or Open Look.
AVAILABILITY 🎁
XT-DUA is commercial software 💼. It's available via ftp. For more details, contact:
Colin Robbins or Graeme Lunt
X-Tel Services Limited
University Park
Nottingham
NG7 2RD
DN: c=GB@o=X-Tel Services Ltd
Telephone: +44 602 412648
Fax: +44 602 790278
E-Mail: x500@xtel.co.ukNAME 🏷️
xwp Performance Systems International Inc.
LAST MODIFIED 📅
July, 1991
KEYWORDS 🔑
Commercially Available, DUA Only, Limited Functionality, Multiple Vendor Platforms, UNIX, X Window System
ABSTRACT ✨
xwp is a graphical user interface tailored specifically for easy access to the Directory when you're doing White Pages searches 🔎. It's currently one of the user interfaces available on wp1.psi.net and wp2.psi.net, the two service machines for the White Pages Pilot Project 🌟. It implements the User-Friendly Naming scheme developed in the IETF OSI-DS Working Group 🧡.
COMPLETENESS 🙈
Compliant with X.500 standards to the extent that the QUIPU implementation is.
INTEROPERABILITY 🔥
Successfully interoperates with QUIPU DSAs.
PILOT CONNECTIVITY 🌸
[No information provided--Ed.]
BUGS 🐞
Bugs go to ssd-help@psi.com.
CAVEATS AND GENERAL LIMITATIONS 💅
Okay so for this one it's just n/a 🥹 nothing to limit here, periodt ✨
INTERNETWORKING ENVIRONMENT 🌐
xwp will operate in any environment where Motif, ISODE and QUIPU operate 🦋
HARDWARE PLATFORMS 🖥️
xwp has been run on IBM PC/RT, and it's soon to run on DecStation 3100 🍓
SOFTWARE PLATFORMS 💻
Berkeley 4.3 and Ultrix 3.1 ✨
AVAILABILITY 📬
Openly available in May, 1991. Contact hagens@cs.wisc.edu for more information 💌
4. References 📚
[CCITT-88]CCITT, "Data Communications Networks Directory," 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.
5. Security Considerations 🔐
Okay this one is giving tension 😭 Security issues are not discussed in this memo. That's the whole tea, bestie 💀
6. Authors' Addresses 🫶
Ruth Lang
SRI International
333 Ravenswood Ave.
Menlo Park, CA 94025
(415) 859-5608
rlang@nisc.sri.comRuss Wright
Lawrence Berkeley Laboratory
1 Cyclotron Road
Berkeley, CA 94720
(415) 486-6965
wright@lbl.gov📦 where this page comes from
- ietf: rfc1292 1992-01
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms