RFC 1632
A Revised Catalog of Available X.500 Implementations
(4) Bind security levels of simple (unprotected password) and none
are supported.
(5) All attribute types defined in ISO/IEC 9594-6:1993 are supported
except for 1993 edition supertypes and collective attributes and
EnhancedSearchGuide. Customers can define new attribute types.
UNIVERSAL STRING is not supported for attributed based on
DirectoryString.
(6) All object classes defined in ISO/IEC 9594-7:1993 are supported.
Customers can define new object classes.
(7) The following operational attributes are supported:
governingStructureRule
createTimestamp
modifyTimestamp
myAccessPoint
superiorKnowledge
supplierKnowledge
consumerKnowledge
specificKnowledge
dseType
PrescriptiveACI
(8) Dynamic modification of object class is permitted
(9) A subset of Simplified Access Control is supported.
(10) All name forms defined in ISO/IEC 9594-7:1993 are supported.
Customers can defined new name forms and structure rules.
The X.500 Directory Server is compatible with and interworks with
1988 edition DUAs and DSAs. It is implemented to conform to relevant
NIST OIW and EWOS agreements and the X.500 Implementors Guide.
For details contact Digital.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
Supports RFC 1006, RFC 1274, and RFC 1277.
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
RFC 1278.
INTEROPERABILITY
All interoperability test results will be available on request from
Digital. Interoperability testing is being undertaken using the
harmonized OSIone X.500 test suite to which both OSInet and EurOSInet
have been key contributors.
PILOT CONNECTIVITY Digital is actively involved in both public and private pilots of X.500. BUGS [No information provided--Ed.] CAVEATS and GENERAL LIMITATIONS [No information provided--Ed.] INTERNETWORKING ENVIRONMENT The DEC X.500 Directory Service V1.0 operates over: * RFC 1006 over TCP/IP on ULTRIX platforms. * OSI TP0, TP2 and TP4 over CLNS and CONS as appropriate on ULTRIX and OpenVMS platforms HARDWARE PLATFORMS The DEC X.500 Directory Service V1.0 runs on: * VAX processors supported by OpenVMS * RISC processors supported by ULTRIX SOFTWARE PLATFORMS The DEC X.500 Directory Service V1.0 runs on: * OpenVMS/VAX V5.5-2 or later running DECnet-VAX Extensions V5.4 * ULTRIX/RISC V4.2 or later running DECnet/OSI for ULTRIX, V5.1 or later. For availability on other hardware and software platforms please contact Digital. AVAILABILITY The DEC X.500 Directory Service is commercially available from Digital Equipment Corporation. For further information please contact your local Digital office, or:
Gail Shlansky, Product Manager:
Tel: +1 508 486 5138
email: gail.shlansky@lkg.mts.dec.com
Digital Equipment Corporation
Networks and Communications Engineering
550 King Street
Littleton, MA. 01460-1289
USA
DATE LAST UPDATED
August 2nd, 1993
NAME DEC X.500 Administration Facility Digital Equipment Corporation KEYWORDS API, CLNS, Commercially Available, DEC ULTRIX, DEC VAX OpenVMS, DUA Only, Motif, OSI Transport, RFC-1006, RFC-1274, RFC-1277, RFC-1278, X.25 ABSTRACT The DEC X.500 Administration Facility product provides both command line and Motif interfaces to manage the information stored in the X.500 directory. Specific features provided include: (1) Multi-protocol support allowing DAP access over OSI and TCP/IP (using RFC1006) protocols. (2) Driven off the same configurable schema information as the DEC X.500 Directory Service. (3) Supports command line and OSF Motif interface styles. (4) Provides access to all X.500 services. Specific features of the OSF Motif interface include: (1) Supports two ways of accessing directory information, either by browsing the directory tree or by searching. (2) Easy-to-use search based on customer-extensible set of predefined filters. (3) Window layouts and text fully extensible, based on the schema, to support customer-defined object classes and attributes. (4) Easy-to-use forms based method for creating and modifying entries that simplifies use of the X.500 services. See also the entry for the DEC X.500 Directory Service. COMPLIANCE (applicable only for DSAs and DUAs) Conformance with respect to clause 9.1 of ISO/IEC 9594-5:1993: (1) Supports the all operations of the directoryAccessAC application context.
(2) Bind security levels of none and simple (unprotected passwords). CONFORMANCE WITH PROPOSED INTERNET STANDARDS Supports RFC 1006, RFC 1274, and RFC 1277. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs RFC 1278. INTEROPERABILITY Interoperability test results will be available on request from Digital. Interoperability testing is being undertaken using the harmonized OSIone X.500 test suite to which both OSInet and EurOSInet have been key contributors. PILOT CONNECTIVITY Digital is actively involved in both public and private pilots of X.500. BUGS [No information provided--Ed.] CAVEATS and GENERAL LIMITATIONS [No information provided--Ed.] INTERNETWORKING ENVIRONMENT The DEC X.500 Administration Facility operates over: * RFC 1006 over TCP/IP on ULTRIX platforms. * OSI TP0, TP2 and TP4 over CLNS and CONS as appropriate on ULTRIX and OpenVMS platforms HARDWARE PLATFORMS The DEC X.500 Administration Facility V1.0 runs on: * VAX processors supported by OpenVMS * RISC processors supported by ULTRIX
SOFTWARE PLATFORMS
The DEC X.500 Administration Facility V1.0 runs on:
* OpenVMS/VAX V5.5-2 or later running DECnet-VAX Extensions V5.4
* ULTRIX/RISC V4.2 or later running DECnet/OSI for ULTRIX, V5.1 or
later.
For availability on other hardware and software platforms please
contact Digital.
AVAILABILITY
The DEC X.500 Administration Facility is commercially available from
Digital Equipment Corporation. For further information please
contact your local Digital office, or:
Gail Shlansky, Product Manager:
Tel: +1 508 486 5138
email: gail.shlansky@lkg.mts.dec.com
Digital Equipment Corporation
Networks and Communications Engineering
550 King Street
Littleton, MA. 01460-1289
USA
DATE LAST UPDATED
August 2nd, 1993
NAME DIR.X (tm) V3.0 Siemens Nixdorf Informationssysteme AG KEYWORDS API, CLNS, Commercially Available, DSA Connectivity, DSA/DUA, DUA Connectivity, HP, IBM RISC, OSI Transport, RFC-1006, RFC-1277, SNI, X.25 ABSTRACT DIR.X is the Siemens Nixdorf X.500 product on which the OSF DCE/GDS (Distributed Computing Environment/Global Directory Service) is based. It supports full DUA and DSA functionality for globally unique identification and location of objects in a network. It also provides functions to answer queries (both yellow-page and white- page) about objects and attribute information. The software implements full DAP and DSP protocols specified in X.519. The required ACSE, ROSE, Presentation, Session and RFC-1006 protocol implementations are also included. It also supports RFC-1277. Additional features include proprietary Replication and Access Control, Caching, Tree-handling utilities and (Remote) Administration. COMPLIANCE (applicable only for DSAs and DUAs) Consists of both DUA and DSA implementations according to the CCITT X.500 (1988) and ISO 9594 standard. The X/Open standard APIs for XDS and XOM are provided. The XDS interface can also be used to access the OSF DCE/CDS (DCE local Cell Directory Service) transparently. DIR.X has been successfully conformance tested. PICS and PCTRs are available for all tested protocols: DSA/DAP, DUA/DAP, Presentation, ACSE and Session embedded in X.500. Compliant with EWOS Agreements (which are being harmonized with OIW Agreements). Strong authentication according to X.509 and an XDS/XOM convenience library will be included in the next version (Q2 1994). Support for X.500 (1993) is planned for Q4 1994.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS [No information provided--Ed.] CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs [No information provided--Ed.] INTEROPERABILITY This implementation of DAP and DSP has successfully interoperated with the X.500 implementations from ICL, UNISYS, E3X and ISODE. PILOT CONNECTIVITY Several DIR.X DSAs are connected to the European X.500 pilot network PARADISE. (DUA and DSA connectivity.) BUGS Problems and bug-report e-mail address: dirx-info@mch.sni.de CAVEATS AND GENERAL LIMITATIONS The software is highly portable and without any general limitations. INTERNETWORKING ENVIRONMENT OSI TP4 with CLNP OSI TP0, 2 & 4 with X.25 RFC-1006 with TCP/IP DIR.X can use either BSD sockets or XTI/TLI to access the Transport Service. HARDWARE PLATFORMS SNI's hardware platforms, IBM's RS/6000 and Hewlett Packard's HP9000 among others. SOFTWARE PLATFORMS SINIX (UNIX System V Release 4), OSF/1.1, AIX 3.1, HP-UX. A port to Windows-NT is planned for Q2 1994. AVAILABILITY DIR.X can be delivered as a binary product or as source to OEM customers. The DIR.X product is commercially available from:
Siemens Nixdorf Informationssysteme
SNI BU BA NM 12
D-81739 Munich
Germany
Please contact:
Gianni Rabaioli
Tel: +49 89 636 41095
Fax: +49 89 636 45860
e-mail: Giovanni.Rabaioli@mch.sni.de
DATE LAST UPDATED or CHECKED
November 26th, 1993
NAME Directory 500 (tm) OSIware / Infonet Software Solutions KEYWORDS Commercially Available, DS/DUA, RFC-1006, Source, Sun, X.25 ABSTRACT Directory 500 (D500) is a comprehensive implementation of the CCITT X.500 recommendations. D500 is comprised of two major components which are responsible for manipulating the data in the OSI Directory. They are the Directory User Agent (DUA) and the Directory System Agent (DSA). The DUA is the interface between the OSI Directory and those users wishing access to the Directory's information. Users make their requests through the DUA. When forwarding user's requests to the OSI Directory, the protocol used is known as the Directory Access Protocol (DAP). The DSA will negotiate with other, remote DSAs to obtain requested information or to update remote DIBs. DSAs use the Directory System Protocol (DSP) to forward and answer these requests. The DSA supports chaining and referrals. COMPLIANCE (applicable only for DSAs and DUAs) All X.500 1988 operations are supported along with all Object Classes specified in X.521 and all Attribute Types specified in X.520. Implementation plans include upgrades to support the 1992 extensions to X.500 in 1994. Please check with OSIware / Infonet Software Solutions for availability dates. CONFORMANCE WITH PROPOSED INTERNET STANDARDS [No information provided--Ed.] CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs [No information provided--Ed.]
INTEROPERABILITY Tested with QUIPU. Other interoperability information not available at this time. PILOT CONNECTIVITY [No information provided--Ed.] BUGS None known at this time. CAVEATS and GENERAL LIMITATIONS None known at this time. INTERNETWORKING ENVIRONMENT RFC1006 with TCP/IP HARDWARE PLATFORMS Any Sun SPARC with 16 MB memory, 40 MB free disk Please enquire if interested in other platforms such as: SCO Unix, AIX SOFTWARE PLATFORMS Sun OS 4.1.x. Runs over TCP/IP, or X.25 (SunNet X.25 Version 7 required) AVAILABILITY Directory 500 is commercially as executable object code or as source code form from: OSIware / Infonet Software Solutions 4400 Dominion Street, Suite 210 Burnaby, BC V5G 4G3 CANADA Sales & Information: 604436-2922 Fax: 604/436-3192 DATE LAST UPDATED or CHECKED November 21st, 1993
NAME DOS-DE University of Bath KEYWORDS Available via FTP, DUA Interface, Free, IBM PC, LDAP, Multiple Vendor Platforms, RFC-1274, RFC-1484, RFC-1487 ABSTRACT DOS-DE (DOS Directory Enquiries) is intended to be a simple-to-use DUA interface suitable for the naive user. It is an MS-DOS port of the standard UNIX DE implementation - see the entry on DE for full details. (All of the features DE are supported apart from the experimental `Quality of Service' code). The user is presented with a series of (verbose) prompts asking for person's name; department; organization; country. There is extensive on-line help. The matching algorithms are such that near matches are presented to the user before less good matches. `Power searching' is also available - this allows a user to search for an entry even when they do not know the name of the organisation in which the person works - you still have to specify the country. DOS-DE provides UFN style searching. It is also possible to search locality entries. DOS-DE uses slightly different search algorithms depending on whether it is accessing part of the Directory mastered by a Quipu DSA - Quipu DSAs tend to use lots of replication and so encourage searching. DOS-DE runs over the University of Michigan LDAP. DE was funded by the COSINE PARADISE project. DOS-DE was developed by Andy Powell at the University of Bath. COMPLIANCE (applicable only for DSAs and DUAs) N/A CONFORMANCE WITH PROPOSED INTERNET STANDARDS [RFC 1274] and [RFC 1487] CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs [RFC 1484].
INTEROPERABILITY
N/A
PILOT CONNECTIVITY
N/A
BUGS
Doesn't handle aliases well when power searching.
Send bug reports to:
A.Powell@bath.ac.uk
CAVEATS and GENERAL LIMITATIONS
DOS-DE tries to cater well for the general case, at the expense of
not dealing with the less typical. The main manifestation of this is
that the current version does not handle searching under localities
very well.
It is not possible to display photographs or reproduce sound
attributes.
INTERNETWORKING ENVIRONMENT
University of Michigan LDAP.
HARDWARE PLATFORMS
IBM PC/AT/XT and compatibles.
SOFTWARE PLATFORMS
LDAP for MS-DOS running over the NCSA Telnet stack or SUN's PCNFS
version 4.1 or Novell's LAN Workplace (LWP).
AVAILABILITY
The software is openly available by FTP from ftp.bath.ac.uk, as
pub/x500/dosde.zip.
The very latest code will be made available with the ISODE Consortium
release of ISODE. It is hoped it will be freely available to all.
Contact:
A.Powell@bath.ac.uk
DATE LAST UPDATED or CHECKED
March 18th, 1993
NAME
HP X.500 Distributed Directory Products
Hewlett Packard
KEYWORDS
API, CLNS, Commercially Available, DSA/DUA, DUA only, HP, OSI
Transport, X.25
ABSTRACT
HP X.500 Distributed Directory. Its main components are:
DUA, and DUA Interface,
DSA and DIB support,
X.500 Address Lookup,
X/Open Application Tool Kit API (XAT) for XDS/XOM Interface,
X.500 High Level API (X5HLAPI) for XDS/XOM Interface.
HP X.500 DUA. Its main components are:
DUA, and DUA Interface,
X.500 Address Look-up,
X/Open Application Tool Kit API (XAT) for XDS/XOM Interface,
X.500 High Level API (X5HLAPI) for XDS/XOM Interface.
HP X.500 Distributed Directory is based on the 1988 CCITT X.500
standard. HP X.500 can be used for accessing names and electronic
mail addresses for multi-vendor messaging backbone networks. HP X.500
can also be used for the development of networked applications
requiring distributed directory functionality.
HP OpenMail users can access the enterprise wide HP X.500 distributed
directory directly from the HP OpenMail user interface, and select
X.500 addresses for mailing. HP-UX Sendmail users can access
electronic mail addresses from a X.500 server over a TCP/IP network.
Users of non-HP e-mail systems can access data stored in the X.500
Directory using X.500 Address Look-up. X.500 Address Look-up has an
easy to use interface, and phonetic search capability.
HP X.500 Distributed Directory includes a complete multi-threaded DUA
and DSA. The X.500 DIB is built on a database which has been
optimized for X.500 performance. HP X.500 contains full support for
DAP and DSP protocols.
Data Shadowing and security access control of HP X.500 Distributed
Directory allow higher performance, and easier management of its DIB
database in a global environment.
HP X.500 Distributed Directory has menu driven administration and
user interface tools. The tools simplify directory configuration and
data retrieval. It supports X/Open X.500 APIs (XDS and XOM), and high
level APIs on top of XDS to allow developers to write their own X.500
based applications.
HP X.500 Distributed Directory supports comprehensive tracing and
logging facilities for quick diagnosis and resolution of problems. HP
also provides a rich set of troubleshooting tools to check the
interoperability of the network at various layers of the OSI stack.
COMPLIANCE (applicable only for DSAs and DUAs)
HP X.500 Distributed Directory complies with the following standards:
CCITT X.501: The Directory - Models
CCITT X.509: The Directory - Authentications Framework*
CCITT X.511: The Directory - Abstract Service Definition
CCITT X.518: The Directory - Procedures for Distributed Operations
CCITT X.519: The Directory - Protocol Specifications
CCITT X.520: The Directory - Selected Attribute Types
CCITT X.521: The Directory - Selected Object Classes
CCITT X.219: Remote Operations - Model, Notation and Service
Definition
CCITT X.229: Remote Operations - Protocol Specifications
*x.509 describes simple and strong authentication. HP X.500
Distributed Directory supports simple authentication. Strong
authentication is not supported in the current release due to
limited market demand.
HP X.500 Distributed Directory will comply with NIST and EWOS
directory functional profiles. Based on factors such as market needs
and NIST recommendations, HP will implement subsets of 1992 CCITT
functionality in a phased approach.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS
[No information provided--Ed.]
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs
[No information provided--Ed.]
INTEROPERABILITY HP has done some unofficial interoperability testing. HP would welcome suggestions on priorities for vendor interoperability testing. PILOT CONNECTIVITY [No information provided--Ed.] BUGS [No information provided--Ed.] LIMITATIONS HP X.500 Distributed Directory supports up to 30 DSA connections at one time. This limit could be increased in the future if needed. INTERNETWORKING ENVIRONMENT HP X.500 Distributed Directory resides on an OSI stack, and can be used in 802.3 LAN, or X.25 CLNS or CONS environment. HP is investigating implementing X.500 for the TCP/IP environment. HARDWARE PLATFORMS HP X.500 Distributed Directory is available on HP 9000 Series 800 family of high performance servers which are scalable platform. The HP X.500 Address Look-up facility is also available for the HP 9000 Series 300 and Series 700 for customers who have purchased the X.500 product. SOFTWARE PLATFORMS HP X.500 Distributed Directory requires the following software environment: - HP-UX Operating System 8.0 or later - OSI Transport Services/9000 for the Series 800 - HP Lan Link or HP X.25 product - Network Tracing and Logging - ANSI C compiler (for the HP/XDS API)
AVAILABILITY
HP X.500 Distributed Directory is commercial available. The product
can be ordered through HP Sales offices. The ordering numbers are:
P/N J2152A
HP X.500 Distributed Directory/9000 for the Series 800.
Product contains DSA server and DUA client.
P/N J2153A
HP X.500 DUA/9000 for the Series 800.
Product contains only DUA client.
DATE LAST UPDATED or CHECKED
August 16th, 1993.
NAME University of Michigan LDAP Implementation KEYWORDS API, Available via FTP, DEC ULTRIX, DUA Connectivity, DUA Interface, Free, HP, IBM PC, IBM RISC, LDAP, Macintosh, Multiple Vendor Platforms, RFC-1006, RFC-1274, RFC-1484, RFC-1485, RFC-1487, Source, Sun ABSTRACT LDAP is the Lightweight Directory Access Protocol. It gives X.500 access to platforms that have only TCP/IP access, using simplified BER encoding of many X.500 data elements. LDAP is currently a proposed Internet Standard. The LDAP server is an intermediate protocol server that communicates with Internet clients on one side using the simple TCP-based LDAP protocol and an X.500 DSA on the other side using the Directory Access Protocol (DAP). A subset of the X.500 DAP is exported to the clients through the LDAP protocol. The U-M LDAP distribution contains the following components: - LDAP server - LDAP client library, including both synchronous and asynchronous APIs - Lightweight BER library, including an API that supports a printf/scanf-like interface - Various LDAP client programs, including a finger daemon (xfingerd), gopher to X.500 gateway (go500gw), command-line DUA (ud), e-mail query server (rcpt500), and an X.500 mailer (mail500) COMPLIANCE (applicable only for DSAs and DUAs) The U-M LDAP distribution is a complete implementation of the LDAP protocol. The LDAP protocol does not support access to all X.500 features and operations. The operations supported are bind, search, compare, add, delete, modify, modify RDN, and abandon. Note that read and list operations can be emulated using the search operation. Size and time limits may be specified, as may alias dereferencing and searching, but all X.500 service controls are not supported.
CONFORMANCE WITH PROPOSED INTERNET STANDARDS Compliant with [RFC 1485], [RFC 1487], and [RFC 1274]. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs Preliminary support is included for [RFC 1484]. INTEROPERABILITY The current implementation of the LDAP server is known to work with the QUIPU DSA and DAP library. PILOT CONNECTIVITY DUA connectivity should be possible to all pilots, though only AARNET, PARADISE, and PSI White Pages Project have actually been tried. BUGS Bug reports should be sent to bug-ldap@umich.edu. CAVEATS and GENERAL LIMITATIONS None, aside from those mentioned above under completeness. INTERNETWORKING ENVIRONMENT LDAP clients use TCP to communicate with the LDAP server. The LDAP server normally uses RFC 1006 with TCP/IP to communicate with the DSA, though any other transport mechanism for DSA communication supported by ISODE should be possible. HARDWARE PLATFORMS The LDAP server is known to run on Sun 3 and Sun 4 platforms DEC's, HP's, and RS 6000's. The LDAP client libraries and some clients have been ported to the Macintosh and the PC. SOFTWARE PLATFORMS The LDAP server and clients are known to run under and SunOS 4.1.x, ULTRIX, HP-UX, and AIX. The LDAP client libraries also work under Macintosh System 6.0 or higher and MS-DOS 5.0.
AVAILABILITY This software is openly available. It may be obtained by anonymous FTP from terminator.rs.itd.umich.edu in the x500 directory. Documentation on the LDAP and lightweight BER libraries is provided in the form of man pages distributed with the source code. More information can be obtained from ldap-support@umich.edu. This software was developed at the University of Michigan by Tim Howes with help from Mark Smith and Bryan Beecher, as well as many others around the Internet. It is subject to the following copyright. Copyright (c) 1993 Regents of the University of Michigan. All rights reserved. Redistribution and use in source and binary forms are permitted provided that this notice is preserved and that due credit is given to the University of Michigan at Ann Arbor. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. This software is provided ``as is'' without express or implied warranty. DATE LAST UPDATED OR CHECKED March 13th, 1993
NAME ldap-whois++ KEYWORDS Available via FTP, DEC ULTRIX, DUA Interface, Free, LDAP, RFC-1487, Sun, UNIX ABSTRACT ldap-whois++ is a dua interface that implements the IETF WNILS draft whois++ proposal using the LDAP libraries developed by the University of Michigan. COMPLIANCE (applicable only for DSAs and DUAs) N/A CONFORMANCE WITH PROPOSED INTERNET STANDARDS RFC 1487 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs IETF WNILS WG Whois++ Architecture Draft. INTEROPERABILITY N/A PILOT CONNECTIVITY There are a number of servers running across the Internet. BUGS None reported. CAVEATS and GENERAL LIMITATIONS Based on an early draft of the Whois++ Architecture Document so there may be some inconsistencies with the latest draft. It is considered a "beta" release due to the volatility of the whois++ work. Once there is a whois++ RFC then a real release will be made.
INTERNETWORKING ENVIRONMENT N/A HARDWARE PLATFORMS DEC RISC, SUN RISC SOFTWARE PLATFORMS ULTRIX 4.3, SunOS 4.1.x AVAILABILITY Available via anonymous ftp from ftp.adelaide.edu.au as pub/whois/whois++beta.tar.Z. DATE LAST UPDATED or CHECKED August 3rd, 1993
NAME University of Michigan maX.500 Macintosh DUA Interface KEYWORDS Available via FTP, DUA Connectivity, DUA Interface, Free, LDAP, Macintosh, RFC-1274,RFC-1484, RFC-1485, RFC-1487 ABSTRACT maX.500 is a Directory User Agent for Apple Macintosh. It is currently at version 2.0, which uses the Lightweight Directory Access Protocol (LDAP) over TCP/IP to access The Directory. maX.500 can be used to search for, view, create, delete, and modify entries. It supports viewing of textual information, playing of audio, and viewing of black and white (fax) and color (JPEG) images. maX.500 is a native Macintosh application, and as such has a friendly interface. It requires System Software version 6.0.5 or later and Apple's MacTCP control panel. COMPLIANCE (applicable only for DSAs and DUAs) maX.500 works over LDAP, and is subject to LDAP's limitations. The X.500 bind, search, compare, add, delete, abandon, and modify operations are used by maX.500. Size and time limits may be specified, as may alias dereferencing and searching. CONFORMANCE WITH PROPOSED INTERNET STANDARDS Compliant with [RFC 1485], [RFC 1487], and [RFC 1274]. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs Preliminary support is included for [RFC 1484] (same as U-M LDAP). INTEROPERABILITY maX.500 2.0 is known to work with the U-M LDAP server. It has been used successfully with the QUIPU DSA and others. PILOT CONNECTIVITY DUA connectivity should be possible to all pilots, though only AARNET, PARADISE, and PSI White Pages Project have actually been tried.
BUGS
Bug reports should be sent to max500-bugs@umich.edu.
CAVEATS and GENERAL LIMITATIONS
maX.500 does not support modification of "photo" (fax), "jpegPhoto",
or "audio" attributes. Modify RDN is also unsupported.
INTERNETWORKING ENVIRONMENT
maX.500 is an LDAP client, and as such is uses TCP to communicate
with the LDAP server. Apple's MacTCP control panel is required on
the Macintosh.
HARDWARE PLATFORMS
maX.500 runs on Apple Macintosh Plus or later computers. It requires
1MB of RAM.
SOFTWARE PLATFORMS
maX.500 requires Apple System Software 6.0.5 or later (System 7
preferred) and MacTCP 1.1 or later (1.1.1 preferred).
AVAILABILITY
This software is openly available. It may be obtained by anonymous
FTP from terminator.rs.itd.umich.edu in the x500 directory. More
information can be obtained from ldap-support@umich.edu.
This software was developed at the University of Michigan by Mark
Smith with help from Tim Howes and many others around the Internet.
It is subject to the following copyright:
Copyright (c) 1993 Regents of the University of Michigan. All
rights reserved. Redistribution and use in binary forms is
permitted provided that this notice is preserved and that due
credit is given to the University of Michigan at Ann Arbor. The
name of the University may not be used to endorse or promote
products derived from this software without specific prior written
permission. This software is provided ``as is'' without express or
implied warranty.
DATE LAST UPDATED OR CHECKED
July 26th, 1993
NAME MXLU Brunel University, UK KEYWORDS DUA Connectivity, DUA Only, Free, Motif, Multiple Vendor Platforms, Needs ISODE, Source, UNIX, X Window System ABSTRACT MXLU (Motif/X LookUp) is an X.500 DUA interface for the X Window System using Motif. Ported from the Athena widgets version, MXLU can be configured for many different styles of interaction. Example configurations are provided for single window and multiple window use. MXLU implements the `User-Friendly Naming' search strategy and also has a form-filling search mode. Asynchronous directory operations are used. Full user friendly add and modify functions are provided, with the ability to tailor the modify screen to present simple subsets of the available attributes. Can also be configured as a bibliographic search tool for use with the ABDUX Project bibliographic DSAs. COMPLIANCE (applicable only for DSAs and DUAs) 88 Standard compliant: Strong authentication not yet implemented. No plans for support of the 1992 Standard. CONFORMANCE WITH PROPOSED INTERNET STANDARDS No plans at present. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs No plans at present. INTEROPERABILITY Tested with ISODE-8.0
PILOT CONNECTIVITY
DUA Connectivity: The interface is in use in the UK Academic
Directory Pilot.
BUGS
Bugs should be reported to x500@brunel.ac.uk.
CAVEATS and GENERAL LIMITATIONS
Does not support modification of all known attribute syntaxes. In
particular, ACLs and O/R addresses are not catered for.
INTERNETWORKING ENVIRONMENT
As ISODE.
HARDWARE PLATFORMS
Most UNIX machines.
SOFTWARE PLATFORMS
UNIX
Motif 1.1 >
ISODE/QUIPU (version 8.0 >)
AVAILABILITY
Sources are freely available for commercial or non-commercial use.
Binaries for SunOs 4.1.3 are also available from Brunel, to simplify
installation on sites that do not already use ISODE.
FTP site: src.brunel.ac.uk
Directory: /x500
Source code files: mxlu-1.1.tar.Z query-1.1.tar.Z
Binary file: mxlubin-1.1.tar.Z
Contacts.
Postal Address:
Andrew Findlay
Computing and Media Systems
Brunel University
Cleveland Road
Uxbridge, Middlesex
UB8 3PH
UK
E-mail: x500@brunel.ac.uk.
Fax: +44 895 32806 (Andrew Findlay)
Telephone: +44 895 203066 (Andrew Findlay)
DATE LAST UPDATED or CHECKED
March 10th, 1994
NAME PathWay Messaging KEYWORDS 386, CLNS, Commercially Available, DSA Connectivity, DSA/DUA, DUA Connectivity, DUA Interface, IBM PC, LDAP, Macintosh, Multiple Vendor Platforms, OSI Transport, RFC-1006, RFC-1202, RFC-1277, RFC-1278, Sun, X.25 ABSTRACT PathWay Messaging Services is a full X.400 MTA and X.400-Internet gateway that includes an integrated X.500 DSA/DUA. It supports full DUA and DSA functions as well as full DAP and DSP protocols specified in X.519. The DSA may be used exclusively for enterprise-wide messaging, or as a general purpose X.500 DSA. The product has successfully participated in OSInet X.500 I-Lab interoperability tests. PathWay Messenger is an email application for desktop class machines with a limited functionality DUA Light Weight Client that provides access (per RFC 1202, Directory Assistance Service - support for LDAP is planned) over TCP/IP to the X.500 DSA/DUA included with PathWay Messaging Services. COMPLIANCE (applicable only for DSAs and DUAs) PathWay Messaging Services is a complete implementation of the 1988 X.500 Recommendations with the exception of strong authentication as outlined in X.509. It is conformant to NIST, EWOS, and UK GOSIP Directory profiles. It provides network through application layer protocol support, with support for all attribute types, syntaxes, and object classes defined in X.520 and X.521. Support for 1992 extensions to X.500 is planned for future release as is support for X/Open Object Management (OM) and X/Open Directory Services (XDS) standards. CONFORMANCE WITH PROPOSED INTERNET STANDARDS PathWay Messaging Services' X.500 supports the following Internet Proposals: [RFC 1277].
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs PathWay Messaging Services' X.500 supports the following Internet Proposals: [RFC 1202] and [RFC 1278]. INTEROPERABILITY PathWay Messaging Services has undergone successful interoperability testing with Control Data, DEC, HP, and the ISODE Consortium using EurOSInet test suites. PILOT CONNECTIVITY Tested DUA and DSA connectivity with PARADISE and PSI White Pages Project. BUGS Send bug reports to: prod-eng@twg.com CAVEATS and GENERAL LIMITATIONS [No information provided--Ed.] INTERNETWORKING ENVIRONMENT RFC1006 with TCP/IP, TP4 with CNLS, TP0/2 or TP4 with X.25. HARDWARE PLATFORMS PathWay Messaging Services runs on all models of Sun SPARC and generic 386/486 systems. PathWay Messenger (email with lightweight DUA) also runs on Macintosh, and on IBM PC/AT and compatibles. SOFTWARE PLATFORMS PathWay Messaging Services supports SunOS 4.1.2, Solaris 1.0.1, and SunSoft INTERACTIVE UNIX. PathWay Messenger also supports SCO, MacOS and MS-Windows.
(next page on part 3)
