You are here: irt.org | RFCs | RFC1632 [ previous next ]
NetworkWorkingGroup A.Getchell Requestfor Comments: 1632 Lawrence Livermore National Laboratory FYI: 11 S.Sataluri Obsoletes: 1292 AT&T Bell Laboratories Category: Informational Editors May 1994 A Revised Catalog of Available X.500 Implementations Status of this Memo Thismemo provides information for the Internet community. This memo doesnot specify an Internetstandard of anykind. Distribution of thismemo isunlimited. Abstract Thisdocument is theresult of a survey thatgathered new orupdated descriptionsof currently available implementations of X.500, including commercialproducts and openly available offerings. This document is a revision of RFC 1292. We contacted each contributor in RFC 1292 andrequested an update andpublished the survey template in several mailing lists and obtained new product descriptions. Thisdocument contains detailed description of twenty six (26) X.500 implementations - DSAs, DUAs, and DUA interfaces. 1. Introduction Thisdocument catalogs currently available implementations of X.500, including commercialproducts and openly available offerings. For the purposesof thissurvey,we classify X.500 products as, DSA A DSA is an OSIapplication process that provides the Directory functionality, DUA A DUA is an OSIapplication process that represents a user in accessing the Directoryand uses the DAP to communicatewith a DSA, and DUA Interface A DUA Interfaceis an application process that represents a user in accessing the Directory using eitherDAP butsupporting only a subset of theDAP functionality or a protocoldifferent from DAP to communicate witha DSA or DUA. IDS Working Group [Page 1]
RFC 1632 X.500 CatalogMay 1994 Section 2 ofthis document contains a listing of implementations cross referenced by keyword. This list should aid in identifying implementations thatmeet your criteria. To compile this catalog, theIDS Working Group solicited input from the X.500 community by surveying several Internet mailing lists, including: iso@nic.ddn.mil,isode@nic.ddn.mil, osi-ds@cs.ucl.ac.uk, and ietf-ids@umich.edu. We also contacted many people by telephone and sent thetemplate to several individualsand mailed a floppy disk containing the survey template to a person who did not have Internet access. Readers are encouraged to submit comments regarding both theform and content ofthis memo. New submissions are welcome. Please direct input to the Integrated Directory Services (IDS) Working Group (ietf-ids@umich.edu) or to the editors. IDS willproducenew ver- sions of this document when a sufficient number of changes have been received. This willbe determined by the IDS chairpersons. 1.1 Purpose The Internethas experienceda steady growthin X.500 piloting activities.This document hopes to provide an easily accessible source of information on X.500 implementations for those whowish to consider X.500 technology for deploying a Directory service. 1.2 Scope Thisdocument contains descriptions of both free andcommercial X.500 implementations. Itdoes not provide instructions on how toinstall, run,or manage theseimplementations. The descriptions and indices are providedto makethe readers aware of available options and thus enable more informedchoices. 1.3 Disclaimer Implementation descriptions were written by implementors andvendors, and not by the editors. We worked with the description authors to ensure uniformity and readability, but can not guarantee theaccuracy or completeness of the descriptions,or the stability of the implementations. 1.4 Overview Section 1 contains introductory information. Section 2 contains alist ofkeywords, theirdefinitions, and a cross reference ofthe X.500 implementations by these keywords. IDS Working Group [Page 2]
RFC 1632 X.500 CatalogMay 1994 Section 3 contains the X.500implementation descriptions. Section 4 has a listof references. Section 6 lists the editors'addresses. 1.5 Acknowledgments The creationof thiscatalogwould not have been possible without the efforts of the description authors and the members of the IDS Working Group. Our special thanks to the editors ofRFC 1292, Ruth Lang and RussWright who helped us get started and made key suggestions that enabled us to learn from their experience. We also acknowledge and appreciate the efforts of Ken Rossenin obtaining six descriptions. 2. Keywords Keywords areabbreviated attributes of the X.500 implementations. The list of keywordsdefinedbelow was derived from the implementation descriptions themselves. Implementations were indexed by akeywordeither as a result of: (1) explicit, not implied, reference toa particular capabilityin the implementation description text, or(2) input from the implementation description author(s). 2.1 Keyword Definitions Thissectioncontains keyword definitions. They have been organized and grouped by functional category.The definitionsare ordered first alphabeticallyby keyword category, and secondalphabetically by implementation name within keyword category. 2.1.1 Availability Available via FTP Implementation is available using FTP. CommerciallyAvailable This implementation canbe purchased. Free Available at nocharge,although other restrictions mayapply. Limited Availability Need tocontactprovider for terms and conditions of distribution. IDS Working Group [Page 3]
RFC 1632 X.500 CatalogMay 1994 Source Source code is available, potentially at an additional cost. 2.1.2 Conformance withProposed Internet Standards These RFCs specify standardstrack protocolsfor theInternet community. Implementations which conform tothese evolving proposed standards have a higher probability of interoperating with other implementations deployed on the Internet. RFC-1274 Implementation supportsRFC 1274: Barker, P., and S. Kille, The COSINE and Internet X.500 Schema, University College, London, England, November 1991. RFC-1276 Implementation supportsRFC 1276: Kille, S., Replication and Distributed Operations extensions to provide anInternet Directory usingX.500, University College, London, England, November 1991. RFC-1277 Implementation supportsRFC 1277: Kille, S., EncodingNetwork Addresses to support operation over non-OSI lower layers, University College, London, England, November 1991. RFC-1485 Implementation supportsRFC 1485: Kille, S., A String Representation of DistinguishedNames, ISODE Consortium, July 1993. RFC-1487 Implementation supportsRFC 1487: Yeong, W., T.Howes, and S. Kille, X.500 Lightweight Directory Access Protocol, July 1993. 2.1.3 Consistence withInformational and Experimental InternetRFCs These RFCs provide information to the Internet community andare not Internet standards. Compliance with these RFCs is not necessary for interoperability butmay enhance functionality. RFC-1202 Implementation supportsRFC 1202: Rose,M. T., Directory IDS Working Group [Page 4]
RFC 1632 X.500 CatalogMay 1994 Assistance Service. February 1991. RFC-1249 Implementation supportsRFC 1249: Howes, T., M.Smith, and B. Beecher, DIXIE ProtocolSpecification, University of Michigan, August 1991. RFC-1275 Implementation supportsRFC 1275: Kille, S., Replication Requirements toprovidean Internet Directory using X.500, University College, London, England, November 1991. RFC-1278 Implementation supportsRFC 1278: Kille, S., Astring encoding of PresentationAddress, University College, London, England, November 1991. RFC-1279 Implementation supportsRFC 1279: Kille, S., X.500 andDomains, University College, London, England, November 1991. RFC-1484 Implementation supportsRFC 1484: Kille, S., Using the OSI Directory to achieve User Friendly Naming, ISODE Consortium, July 1993. 2.1.4 Implementation Type API Implementation comes with an application programmer's interface (i.e., a set oflibraries and include files). DSA Only Implementation consistsof a DSA only.No DUA is included. DSA/DUA Both a DSA and DUA are includedin thisimplementation. DUA Interface Implementation is a DUA-like program that uses either DAP, but supporting onlya subset of theDAP functionality, or uses a protocol different fromDAP to communicate witha DSA or DUA. DUA Only Implementation consistsof a DUA only.No DSA is included. IDS Working Group [Page 5]
RFC 1632 X.500 CatalogMay 1994 LDAP DUA interface program uses the Lightweight Directory Access Protocol (LDAP). 2.1.5 Internetworking Environment CLNS Implementation operatesover the OSI ConnectionLess Network Service(CLNS). OSI Transport Implementation operatesover one or more OSI transport protocols. RFC-1006 Implementation operatesover RFC-1006 with TCP/IP transport service. RFC-1006 is an Internet Standard. X.25 Implementation operatesover OSI X.25. 2.1.6 Pilot Connectivity DUA Connectivity The DUAcan be connected to thepilot, and information on any pilot entry looked up.The DUAis ableto display standard attributes and object classes and thosedefinedin the COSINE and Internet Schema. DSA Connectivity The DSAis connected tothe DIT, and information in this DSA is accessible fromany pilot DUA. 2.1.7 Miscellaneous Included in ISODE DUAs that are part of ISODE. Limited Functionality Survey states that the implementation has some shortcomings or intended lack of functionality,e.g., omissionswere part of the design to provide an easy-to-use user interface. IDS Working Group [Page 6]
RFC 1632 X.500 CatalogMay 1994 Motif Implementation providesa Motif-style XWindow user interface. Needs ISODE ISODE is required to compile and/or usethis implementation. OpenLook Implementation providesan OpenLook-style X Window user interface. X Window System Implementation uses theX Window Systemto provide its user interface. 2.1.8 OperatingEnvironment 386 Implementation runs on a 386-based platform. Bull Implementation runs on a Bull platform. CDC Implementation runs on a CDC MIPS platform. DEC ULTRIX Implementation runs under DEC ULTRIX. DEC Vax OpenVMS Implementation runs on a DEC VAX platform running OpenVMS. HP Implementation runs on an HP platform. IBM PC Implementation runs on a PC. IBM RISC Implementation runs on IBM's RISC UNIX workstation. ICL Implementation runs on an ICL platform. Macintosh Implementation runs on a Macintosh. IDS Working Group [Page 7]
RFC 1632 X.500 CatalogMay 1994 Multiple Vendor Platforms Implementation runs on more than one hardware platform. Sequent Implementation runs on a Sequent platform. SNI Implementation runs on a Siemens Nixdorf platform. Solbourne Implementation runs on a Solbourne platform. Sun Implementation runs on a Sun platform. Tandem Implementation runs on a Tandemplatform. UNIX Implementation runs on a generic UNIX platform. Wang Implementation runs on a Wang RISC platform. 2.2 Implementations Indexed byKeyword Thissectioncontains an index of implementations bykeyword. You can use thislist toidentify particular implementations that meet yourchosen criteria. The index isorganized as follows: keywords appear in alphabetical order; implementations characterizedby thatkeywordare listed alphabetically as well. Note that a"*" is used to indicatethat the particular implementation, or feature of theimplementation,may not be availableat thistime. For formatting purposes, we have used the following abbreviations for implementation names: BULL S.A. (Bull X500-DS and X500-DUA),DEC X.500 DSA (DEC X.500Directory Server), DEC X.500 Admin (DECX.500 Administration Facility), HPX.500 DD (HP X.500 Distributed Directory), LDAP (Universityof Michigan LDAP Implementation), OSI Access & Dir(OSI Access andDirectory), andTraxis (Traxis Enterprise Directory). IDS Working Group [Page 8]
RFC 1632 X.500 CatalogMay 1994 386 CLNS PathWayMessaging Bull S.A. PC-DUA DEC X.500DSA UCOM X.500 DEC X.500Admin DIR.X API HP X.500 DD HP X.500 DUA Bull S.A. OSI Access & Dir Custos PathWay Messaging DEC X.500 DSA Traxis DEC X.500 Admin UCOM X.500 DIR.X Wang OPEN/services HP X.500 DD XT-DUA HP X.500 DUA XT-QUIPU LDAP OSI Access & Dir Commercially Available QUIPU Traxis Bull S.A. UCOM X.500 DEC X.500DSA DEC X.500Admin Available via FTP DIR.X Directory500 Custos HP X.500 DD DE HP X.500 DUA DOS-DE OSI Access & Dir LDAP PathWay Messaging ldap-whois++ PC-DUA maX.500 Traxis Xdi UCOM X.500 Wang OPEN/services Bull XT-DUA XT-QUIPU Bull S.A. UCOM X.500 DEC ULTRIX XT-DUA XT-QUIPU DEC X.500DSA DEC X.500Admin CDC LDAP ldap-whois++ OSI Access & Dir UCOM X.500 DEC VAX OpenVMS DEC X.500DSA DEC X.500Admin IDS Working Group [Page 9]
RFC 1632 X.500 CatalogMay 1994 DSA Connectivity DUA Interface DIR.X DE OSI Access & Dir DOS-DE PathWayMessaging LDAP QUIPU ldap-whois++ UCOM X.500 maX.500 XT-QUIPU OSI Access & Dir Pathway Messaging DSA Only PC-DUA QuickMailDUA DEC X.500 DSA Wang OPEN/services XT-QUIPU DUA Only DSA/DUA DEC X.500Admin Bull S.A. HP X.500 DUA Custos MXLU DIR.X PC-Pages Directory 500 Xdi HP X.500 DD XLU OSI Access & Dir XT-DUA PathWayMessaging QUIPU Free Traxis UCOM X.500 Custos Wang OPEN/services DE DOS-DE DUA Connectivity LDAP ldap-whois++ DIR.X maX.500 LDAP MXLU maX.500 QUIPU MXLU Xdi OSI Access & Dir XLU PathWayMessaging PC-DUA HP PC-Pages QUIPU DIR.X UCOM X.500 HP X.500 DD Xdi HP X.500 DUA XLU LDAP XT-DUA *Traxis Wang OPEN/services XT-DUA XT-QUIPU IDS Working Group [Page 10]
RFC 1632 X.500 CatalogMay 1994 IBM PC Limited Functionality DOS-DE Custos LDAP Wang OPEN/services OSI Access & Dir Xdi PathWayMessaging PC-DUA Macintosh PC-Pages Traxis LDAP Wang OPEN/services maX.500 PathWay Messaging IBM RISC *Traxis DIR.X Motif LDAP *Traxis DEC X.500Admin UCOM X.500 MXLU Wang OPEN/services UCOM X.500 XT-DUA XT-DUA XT-QUIPU Multiple Vendor Platforms ICL Custos *XT-DUA DE XT-QUIPU DOS-DE LDAP Included In ISODE MXLU PathWay Messaging DE PC-Pages QUIPU LDAP UCOM X.500 Xdi DE XLU DOS-DE XT-DUA LDAP XT-QUIPU ldap-whois++ maX.500 Needs ISODE OSI Access & Dir *Pathway Messaging Custos PC-DUA DE *PC-Pages MXLU QuickMailDUA Limited Availability Xdi XLU PC-Pages QuickMailDUA IDS Working Group [Page 11]
RFC 1632 X.500 CatalogMay 1994 OpenLook RFC-1249 UCOM X.500 OSI Access & Dir XT-DUA RFC-1274 OSI Transport DE Bull S.A. DEC X.500DSA Custos DEC X.500Admin DEC X.500 DSA DOS-DE DEC X.500 Admin LDAP DIR.X maX.500 HP X.500 DD OSI Access & Dir HP X.500 DUA QuickMailDUA PathWayMessaging QUIPU PC-Pages Traxis QUIPU UCOM X.500 Traxis Xdi Wang OPEN/services XT-DUA XT-DUA XT-QUIPU XT-QUIPU RFC-1275 RFC-1006 OSI Access & Dir Bull S.A. QUIPU Custos DEC X.500 DSA RFC-1276 DEC X.500 Admin DIR.X OSI Access & Dir Directory 500 QUIPU LDAP XT-QUIPU OSI Access & Dir PathWayMessaging RFC-1277 PC-Pages QUIPU DEC X.500DSA Traxis DEC X.500Admin UCOM X.500 DIR.X Wang OPEN/services OSI Access & Dir XT-DUA PathWay Messaging XT-QUIPU QUIPU UCOM X.500 RFC-1202 XT-DUA XT-QUIPU OSI Access & Dir PathWayMessaging IDS Working Group [Page 12]
RFC 1632 X.500 CatalogMay 1994 RFC-1278 Sequent DEC X.500 DSA DEC X.500 Admin UCOM X.500 OSI Access & Dir PathWayMessaging SNI QUIPU UCOM X.500 DIR.X XT-DUA XT-QUIPU Solbourne RFC-1279 XT-DUA XT-QUIPU OSI Access & Dir QUIPU Source UCOM X.500 XT-QUIPU DE LDAP RFC-1484 MXLU QUIPU DE Xdi DOS-DE XLU *LDAP *maX.500 Sun QUIPU Xdi Custos XT-DUA Directory500 XT-QUIPU LDAP ldap-whois++ RFC-1485 OSI Access & Dir PathWay Messaging LDAP QuickMailDUA maX.500 QUIPU QUIPU Traxis XT-QUIPU UCOM X.500 Xdi RFC-1487 XT-DUA XT-QUIPU DE DOS-DE Tandem LDAP ldap-whois++ UCOM X.500 maX.500 PC-DUA QUIPU IDS Working Group [Page 13]
RFC 1632 X.500 CatalogMay 1994 UNIX Custos DE ldap-whois++ MXLU QUIPU UCOM X.500 Xdi XLU Wang Wang OPEN/services X Window System MXLU OSI Access & Dir Xdi XLU XT-DUA X.25 Bull S.A. DEC X.500 DSA DEC X.500 Admin DIR.X Directory 500 HP X.500 DD HP X.500 DUA OSI Access & Dir PathWayMessaging QUIPU Traxis UCOM X.500 Wang OPEN/services XT-DUA XT-QUIPU IDS Working Group [Page 14]
RFC 1632 X.500 CatalogMay 1994 3. Implementation Descriptions In the following pages you will finddescriptions ofX.500 implementations listed in alphabetical order. In the case of name collisions, the nameof the responsible organization, in square brackets, has been used to distinguish the implementations.Note thatthroughout thissection, the page header reflects the name of the implementation, not the date of the document. The descriptions follow a common format, as describedbelow: NAME The name of theX.500 implementation and the name of the responsible organization. Implementations witha registered trademark indicate thisby appending "(tm)", e.g., GeeWhiz(tm). KEYWORDS A list of the keywords defined in Section 2 that have been used to cross reference thisimplementation. ABSTRACT A briefdescription of the application. This section may optionally contain a list of the pilot projectsin which the application is being used. COMPLIANCE (applicable only for DSAsand DUAs) A statement of compliance with respect to the 1988 CCITT RecommendationsX.500-X.521 [CCITT-88],specifically Section 9 of X.519, or the 1988 NIST OIW Stable Implementation Agreements [NIST-88]. CONFORMANCE WITH PROPOSED INTERNET STANDARDS A statement of compliance with respect to the several proposed Internet Standards. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs A statement of compliance with respect to the several informational and experimental InternetRFCs. INTEROPERABILITY A list of otherDUAs and DSAs with which this implementation can interoperate. PILOT CONNECTIVITY Describes the level of connectivity it can offer to thepilot directory service operational on the Internet in North America, and to pilots co-ordinated by the PARADISE project in Europe. Levels of connectivity are: NotTested,None, DUA Connectivity, and DSAConnectivity. IDS Working Group [Page 15]
RFC 1632 X.500 CatalogMay 1994 BUGS A warning on known problems and/or instructionson how to report bugs. CAVEATS AND GENERAL LIMITATIONS A warning aboutpossible side effects or shortcomings, e.g., a featurethat works on one platform but not another. INTERNETWORKING ENVIRONMENT A list of environments in whichthis implementation canbe used, e.g., RFC-1006 with TCP/IP, TP0or TP4 with X.25. HARDWARE PLATFORMS A list of hardware platforms onwhich this application runs, any additional boards or processorsrequired, and any special suggested or required configuration options. SOFTWARE PLATFORMS A list of operating systems, window systems, databases,or unbundled software packages required torun this application. AVAILABILITY A statement regarding the availability of the software (free or commercially available), a description of how to obtainthe software, and (optionally) a statement regarding distribution conditions and restrictions. DATELAST UPDATED orCHECKED The month and year within whichthis implementation description was last modified. IDS Working Group [Page 16]
RFC 1632 X.500 Catalog Bull S.A. NAME X500-DS X500-DUA BullS.A. KEYWORDS API,Bull, CLNS, Commercially Available, DSA/DUA, OSI Transport, RFC-1006, X.25 ABSTRACT X500-DS and X500-DUAare integral part of the large Bull OSIoffer. Although based on the DCE/GDS (Distributed Computing Environment/Global DirectoryService) of OSF, these two products may be installedand used without DCE environment. X500-DS is designed to implementboth the DUA and the DSA functions, whilst X500-DUA only provides theDUA functions. The X500-DUApackagecontains: - The standards APIsXOM (X/Open OSI-Abstract-Data Manipulation API) and XDS (X/Open Directory Service API) forthe developmentof portable applications, - A core DUAto translate all user'srequests (bind,read, list, compare, modify, modifyRDN, search, add, remove, unbind ...) into the DAP protocol used for communication with distant DSAs, - The OSI standard protocols(ASN.1,ROSE, ACSE, Presentation and Session) for communicationwith the distant DSAs. The interface with the low layers of thestack being XTI. RFC-1006 is supported under XTI or the Session, - A DUA Cache to improve performances when accessingremote DSAs, - A management application for configurationof the product, controlling the operationsand managing logs and traces, - A user applicationfor themanipulations of the database entries. The X500-DS package contains: - All components of the X500-DUA, - A core DSAto process all requestsreceived from distant DUAs through DAP protocol or from distant DSAs through DSP protocol. Itsupports the referral, chained and multi-casting modes of operation,access control lists, simple authentication, managementof knowledge information (for distribution, shadows and copies of sub-trees), IDS Working Group [Page 17]
RFC 1632 X.500 Catalog Bull S.A. - A management application for managing the schema information (creation,deletion and modification of object classes andof attribute types, management of therules of the DIT), - A C-ISAM database. COMPLIANCE (applicable only forDSAs and DUAs) Compliant with EWOS and OIW Agreements Strong authentication in X.509 is not yet implemented. (Password scheme is currently used.) Consists of both DUAand DSAimplementation according to the88 CCITT X.500 and ISO 9594 standard.The X/Open standard XDSand XOM interface libraries are alsoprovided. Whenthe product is installed withthe DCEenvironment, XDS and XOM interfaces arealso used to access DCE/CDS (Local Cell DirectoryService) transparently.A GDA (Global Directory Agent) serves thenas the gateway between the DCE CDS and GDS. It is planned to support full 1992 extensions in theproducts for 1995. CONFORMANCE WITH PROPOSED INTERNET STANDARDS [No information provided--Ed.] CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs [No information provided--Ed.] INTEROPERABILITY Thisimplementation of DAP and DSP can interoperate with other X.500 implementations fromother Cebit demo participants includingIBM, HP, ICL,Siemens-Nixdorf, etc. It also interoperates with ISODE QUIPU. PILOT CONNECTIVITY [No information provided--Ed.] BUGS [No information provided--Ed.] IDS Working Group [Page 18]
RFC 1632 X.500 Catalog Bull S.A. CAVEATSAND GENERAL LIMITATIONS [No information provided--Ed.] INTERNETWORKINGENVIRONMENT OSI TP4 withCLNP (WAN - LAN) OSI TP0, 2 & 4with X.25 (WAN)RFC-1006 withTCP/IP Either BSD sockets or XTI can beused toaccess the transports Through XTI, bothOSI andTCP/IP protocols are possible on the same machine, thus permitting tobuild aDirectory Service distributed on OSI and TCP/IP networks. HARDWARE PLATFORMS DPX/2, DPX/20 SOFTWARE PLATFORMS UnixBOS2, Unix BOSX, AIX AVAILABILITY 4 Q 93 Please contact: Daniel Monges Tel: + (33) 76 39 75 00 ext. 7449 Fax: + (33) 76 39 78 56 e-mail: D.Monges@frec.bull.fr DATE LAST UPDATE or CHECKED November 25th, 1993 IDS Working Group [Page 19]
RFC 1632 X.500 Catalog Control Data Systems Inc. NAME OSI Access and Directory Control DataSystemsIncorporated. KEYWORDS API,CLNS, CDC, CommerciallyAvailable, DSA Connectivity, DSA/DUA, DUA Connectivity, DUA Interface, IBMPC, LDAP, RFC-1006, RFC-1202, RFC-1249, RFC-1274, RFC-1275, RFC-1276, RFC-1277, RFC-1278, RFC-1279, Sun,X Window System, X.25 ABSTRACT OSI Access and Directory includes several DUAs and aQUIPU based DSA (originally based onversion6.6) with enhancements.The DUA/DSA enhancementsinclude: - Directory API based on theX.400 API. - Support for X.400 objects including those to support MHS use ofDirectory to support MHS Routing. - Integration with Control Data's MailHub (X.400 MHS) products. - X Windows,curses and command linebased DUA interfaces onUNIX. These interfaces support the full set of Directoryoperations. - Windows 3.x interface on PCs. - A DUA daemon that providesDirectory access for applications. - LDAP 2.0 and 3.0 support. - Directory synchronization tools for synchronizing most PC/Mac/Dec mail directories with X.500. - Enhanced photo attribute support. - ACL enhancements. - Hash indexing for fast string search. - DIXIE, DADand PH.X500 support. - SNMP basedmonitoring and management of DSAs. Control DataSystemsoffers completeintegration services todesign, plan, install, configure, tailor andmaintain X.500 services. These services mayincludethe preparationof customer unique DUAsand tools for X.500 integration,synchronization, operational control and management. OSI Access and Directoryis in production use atseveral government, commercial and academic sites. Some sites are supporting Directories in excess of 120,000 entries. IDS Working Group [Page 20]
RFC 1632 X.500 Catalog Control Data Systems Inc. COMPLIANCE (applicable only forDSAs and DUAs) OSI Access and Directory complies with the 1988 CCITT Recommendations X.500-X.521 [CCITT-88] and the 1988 NIST OIWStable Implementation Agreements [NIST-88]. OSI Access andDirectory only supportssimple authentication or noauthentication.OSI Access and Directory complies with all static anddynamicrequirements ofX.519. OSI Access and Directorycan actas a first-level DSA. OSI Access and Directory will support some 1993 X.500 extensions in 1994with full support in 1995/1996. CONFORMANCE WITH PROPOSED INTERNET STANDARDS OSI Access and Directory is compliant with the following RFCs: [RFC 1274], [RFC 1276], and [RFC 1277]. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs OSI Access and Directory is compliant with the following RFCs: [RFC 1202], [RFC 1249], [RFC 1275], [RFC 1278], and [RFC 1279]. OSI Access and Directory also supports the required objects, attributes and attribute syntaxes for MHS use of Directory to support MHS Routing. INTEROPERABILITY OSI Access and Directory wastested against HP, DEC,ISODE Consortium and Wollongong implementations at the COS Interoperability Test Lab in May 1993.The OSINET Interoperability Tests were used. Please refer OSINETfor test results. OSI Access and Directory has also been informally tested attrade shows with implementations from UNISYS and Retix. PILOT CONNECTIVITY OSI Access and Directory is connected via DSAs and DUAs to the PSI White Pages Project.OSI Access and Directory provides the base routing treefor theMHS Useof Directory pilot (Longbud) onthe Internet. BUGS Control DataSystemsprovides complete software maintenance services withproducts. IDS Working Group [Page 21]
RFC 1632 X.500 Catalog Control Data Systems Inc. CAVEATSand GENERAL LIMITATIONS [No information provided--Ed.] INTERNETWORKINGENVIRONMENT RFC1006 withTCP/IP,TP4 with CNLS, TP0 withX.25. HARDWARE PLATFORMS OSI Access and Directory runs on allMIPS and SUN SPARC platforms. Windows based DUAs availablewith OSI Accessand Directory run on Windows 3.x compatible IBM PCs. SOFTWARE PLATFORMS Distributed and supported for Sun OSversion4.1.x, Sun Solaris 2.x and Control Data EP/IX (Control Data's MIPS based OS). Other platforms are pending. TP4 connectivity on SUN OS requires SUN OSI. AVAILABILITY Commerciallyavailable from: Control DataSystemsInc. Network Solutions, ARH290 4201Lexington Avenue North Arden Hills,MH 55126-6198 U.S.A. 1-800-257-OPEN (U.S.and Canada) 1-612-482-6736 (worldwide) FAX:1-612-482-2000 (worldwide) EMAIL: info@cdc.com or s=info;p=cdc;a=attmail;c=us DATE LAST UPDATED or CHECKED November 22nd, 1993 IDS Working Group [Page 22]
RFC 1632 X.500 Catalog Custos NAME Custos National Institute of Standards and Technology KEYWORDS API,Available via FTP, DSA/DUA, Free, Limited Functionality, Multiple Vendor Platforms, Needs ISODE, OSI Transport, RFC-1006, Sun, UNIX ABSTRACT The implementation consists of a setDUA library routines, aterminal interface, and a DSA. The implementation wasdeveloped in C on Sun SPARCstations under SunOS 4.1.1. Allunderlying services areprovided by the ISODEdevelopment package. The development package isalso usedfor encoding and decoding ASN.1data aswell asfor other data manipulationservices. Usingthe ISODE package the implementation can be run over both TCP/IP and OSI protocols. The DSA provides full support for both DAP and DSP protocols, conformant with ISO 9594 / CCITT X.500 standards. The DIB is maintained using a locally developedrelational database system. The interface tothe database system consists ofa set of sql-like C functions. These are designed to allow straightforward replacement of the localdatabase systemwith a more powerful commercialsystem. To achieve better performance several options are supported that permit loading of selected portions of the database in core.When these options are selected data can be retrieved more quickly from in coretables;all modifications to the DIB are directly reflected in the in core tables and the database. COMPLIANCE (applicable only forDSAs and DUAs) Custos is fully compliant with the 1988 Standard with the following omissions: - Search request decomposition - Modify Entry operation - Modify RDNoperation - Abandon operation - Strong Authentication - Schema checking IDS Working Group [Page 23]
RFC 1632 X.500 Catalog Custos There are nopresentplans to extendCustos to include the 1992 X.500 extensions. CONFORMANCE WITH PROPOSED INTERNET STANDARDS [No information provided--Ed.] CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs [No information provided--Ed.] INTEROPERABILITY Havesuccessfully interoperated withQUIPU and OSIWARE over the DAP. No DSP interoperability testing has been done. PILOT CONNECTIVITY Limited DUA and DSA connectivity to PSI White Pages Project. BUGS Bugsmay be reportedto the general discussion list, x500@osi.ncsl.nist.gov. CAVEATSand GENERAL LIMITATIONS No limitations on file sizes, etc. The only side effects to creating large files should be in thearea ofperformance. Specifically, optimizationrequires loading parts of the DIB in core so greater memory requirements will be necessary for achieving better performance with a large database. Any platform the implementation can be ported to (generally any platform ISODE can be portedto) should support all features. INTERNETWORKINGENVIRONMENT RFC-1006; TP4/CLNP (SunLinkOSI) over802 andX.25 (SunLink X.25). HARDWARE PLATFORMS It'sonly been run on Sun 3 and SPARC, but there areno known reasons why it shouldn't runon any hardwarerunningthe ISODE software. IDS Working Group [Page 24]
RFC 1632 X.500 Catalog Custos SOFTWARE PLATFORMS It requires UNIX andthe ISODE software package. It's been developed and tested with ISODE version 7.0 and Sun OSversion4.1.1. Uses a locally developed relationalDBMS that should be easily replaceable withcommercially available relational systems. AVAILABILITY Custos, the NIST implementation of X.500, the OSI Directory,is available for anonymous ftp from osi.ncsl.nist.gov (129.6.48.100) using the convention(user name = anonymous,password = ident). The software is available in twoforms: a tar file and acompressed tar file. ./pub/directory/CustosRel_0.2.tar ./pub/directory/CustosRel_0.2.tar.Z Note: permissions onthe directory ./pub/directory are set so that you will be able to "get" files whose names you can provide.However, you will notbe ableto "ls"the contents ofthe directory. DATE LAST UPDATED or CHECKED March 5th, 1993 IDS Working Group [Page 25]
RFC 1632 X.500 Catalog DE NAME DE KEYWORDS Available via FTP, DUA Interface, Free, Included in ISODE, LDAP, Multiple Vendor Platforms, Needs ISODE, RFC-1274, RFC-1484, RFC-1487, Source, UNIX ABSTRACT DE (Directory Enquiries) is intendedto be asimple-to-use DUA interface, suitable for the naive user, and suitablefor running as a public access dua. it will work on any terminal. The user is presented with a series of (verbose)promptsasking for person's name; department; organization; country. There is extensiveon-line help. The matching algorithms are such thatnear matches are presented tothe user beforeless good matches. A lot of developmenthas been done on the interface since itwas first described in RFC1292.The most significant enhancement has beento add power searching - this allows a user to search for an entry even when theydo not know thename ofthe organisation in which the person works - youstill have to specify the country. DE now providesUFN style searching. It is nowpossible to search locality entries. DE now uses slightly different search algorithms depending onwhetherit is accessingpart ofthe Directory mastered by aQuipu DSA - Quipu DSAs tend to use lotsof replication and so encourage searching. An experimental feature is intended togive the usermore feedback on the likely response time to a query - DE maintains a databaseof pastinformation availability and DSA responsiveness. Translations exist into at least 4 different languages. DE runs overISODE DAP and University of Michigan LDAP. There is a version of DE, called DOS-DE, which has beenported to DOS, and this usesLDAP. DE was funded by theCOSINE PARADISEproject, and DEis usedas the PARADISE public access dua.You cantest the software by telnet to 128.86.8.56 and logging in as dua --no password required. COMPLIANCE (applicable only forDSAs and DUAs) N/A IDS Working Group [Page 26]
RFC 1632 X.500 Catalog DE CONFORMANCE WITH PROPOSED INTERNET STANDARDS [RFC1274] and [RFC 1487] CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs [RFC1484]. INTEROPERABILITY N/A PILOT CONNECTIVITY N/A (This ismore a DUA rather than an interface question). The interface iswidely used in the global pilot. BUGS Doesn't handle aliases well when power searching. Sendbug reports to: p.barker@cs.ucl.ac.uk helpdesk@paradise.ulcc.ac.uk CAVEATSand GENERAL LIMITATIONS DE tries to cater well for the general case,at the expense of not dealing withthe less typical. The main manifestation of this is thatthe current version does not handle searching under localities verywell. It is not possible to display photographs orreproduce sound attributes. INTERNETWORKINGENVIRONMENT As for ISODE. HARDWARE PLATFORMS As for ISODE. SOFTWARE PLATFORMS As for ISODE. IDS Working Group [Page 27]
RFC 1632 X.500 Catalog DE AVAILABILITY The softwareis openly available as part of ISODE-8.0. An enhanced version is availableas partof the PARADISEprojectupgrade. Boththese versions are available byFTP from <ftp.paradise.ulcc.ac.uk>, as src/isode-8.tar.Z and src/isode- paradise.tar.Z. The very latest codewill bemade available with theISODE Consortium release of ISODE. It is hoped it will be freely available to all. Contact: helpdesk@paradise.ulcc.ac.uk p.barker@cs.ucl.ac.uk DATE LAST UPDATED or CHECKED March 12th, 1993 IDS Working Group [Page 28]
RFC 1632 X.500 Catalog DEC DSA NAME DEC X.500 Directory Server Digital Equipment Corporation KEYWORDS API,CLNS, Commercially Available, DEC ULTRIX, DEC VAX OpenVMS, DSA Only, OSI Transport,RFC-1006, RFC-1274, RFC-1277, RFC-1278,X.25 ABSTRACT The DEC X.500 Directory Server product provides a high performance Directory System Agent implemented accordingto the 1993 edition of ISO/IEC 9594and theCCITT X.500 series of Recommendations. Specific features provided include: (1) Integrated multi-protocol support allowing concurrent DAP and DSP access over OSI and TCP/IP (using RFC1006) protocols. (2) Indexed databasesupports high-performance searching and sophisticated matching includingapproximate match. (3) Based onthe 1993 edition Extended Information Models. (4) Support for chaining andreferrals in support ofa distributed Directory Information Base. (5) Support for the 1993 edition Simplified Access Control scheme. (6) Configurable schema based on the1993 edition (including attributes, object classes, structure rules, name forms). (7) Support for a simple Shadowing protocol to enhance read availability. (8) Remote management facilities to configure and control DSAs and log significant events. (9) Providesthe X/OPEN XDS/XOM Application Program Interface so that customers can construct their own DUA applications. For Directory User Agent facilities see the associated entryfor the DEC X.500 Administration Facility COMPLIANCE (applicable only forDSAs and DUAs) Conformance with respect to clause 9.2 of ISO/IEC 9594-5:1993: (1)Supports the directoryAccessAC (DAP) and directorySystemAC (DSP) application contexts. (2)The DSAis capable of acting asa first-level DSA. (3)Chaining is supported. IDS Working Group [Page 29]
RFC 1632 X.500 Catalog DEC DSA (4)Bind security levels ofsimple (unprotected password) and none are supported. (5)All attribute types defined in ISO/IEC 9594-6:1993 are supported except for 1993editionsupertypes and collective attributes and EnhancedSearchGuide. Customerscan define new attribute types. UNIVERSAL STRING is notsupported for attributed based on DirectoryString. (6)All object classes defined in ISO/IEC 9594-7:1993 are supported. Customers can define new objectclasses. (7)The following operational attributes are supported: governingStructureRule createTimestamp modifyTimestamp myAccessPoint superiorKnowledge supplierKnowledge consumerKnowledge specificKnowledge dseType PrescriptiveACI (8)Dynamicmodification ofobject class ispermitted (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 interworkswith 1988editionDUAs and DSAs.It is implemented to conform torelevant NISTOIW andEWOS agreementsand theX.500 Implementors Guide. For details contact Digital. CONFORMANCE WITH PROPOSED INTERNET STANDARDS Supports RFC1006, RFC 1274,and RFC1277. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs RFC 1278. INTEROPERABILITY All interoperabilitytest results will be available on request from Digital. Interoperability testing isbeing undertaken using the harmonized OSIone X.500 testsuite to which both OSInet and EurOSInet havebeen key contributors. IDS Working Group [Page 30]
RFC 1632 X.500 Catalog DEC DSA PILOT CONNECTIVITY Digital is actively involvedin bothpublic and private pilots of X.500. BUGS [No information provided--Ed.] CAVEATSand GENERAL LIMITATIONS [No information provided--Ed.] INTERNETWORKINGENVIRONMENT The DEC X.500 Directory Service V1.0operates over: * RFC 1006 over TCP/IP on ULTRIX platforms. * OSI TP0, TP2 and TP4 over CLNS andCONS asappropriate on ULTRIX and OpenVMS platforms HARDWARE PLATFORMS The DEC X.500 Directory Service V1.0runs on: * VAX processors supported by OpenVMS * RISC processors supported by ULTRIX SOFTWARE PLATFORMS The DEC X.500 Directory Service V1.0runs on: * OpenVMS/VAX V5.5-2or 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 yourlocal Digital office, or: IDS Working Group [Page 31]
RFC 1632 X.500 Catalog DEC DSA Gail Shlansky, Product Manager: Tel:+1 508 486 5138 email: gail.shlansky@lkg.mts.dec.com DigitalEquipment Corporation Networks and Communications Engineering 550 King Street Littleton, MA. 01460-1289 USA DATE LAST UPDATED August 2nd, 1993 IDS Working Group [Page 32]
RFC 1632 X.500 Catalog DEC X.500 Admin.Facility 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 AdministrationFacility product provides both command lineand Motif interfaces tomanage 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 configurableschema information as the DEC X.500 Directory Service. (3) Supportscommandline and OSF Motif interface styles. (4) Providesaccess to all X.500 services. Specific features ofthe OSFMotif interfaceinclude: (1) Supportstwo ways of accessing directoryinformation, either by browsingthe directory tree or by searching. (2) Easy-to-use search basedon customer-extensible set of predefined filters. (3) Window layouts and text fully extensible, based on the schema, to support customer-definedobject classes and attributes. (4) Easy-to-use forms based method for creating and modifying entries that simplifies use of the X.500services. See also theentry for the DEC X.500Directory Service. COMPLIANCE (applicable only forDSAs and DUAs) Conformance with respect to clause 9.1 of ISO/IEC 9594-5:1993: (1) Supportsthe alloperations of the directoryAccessAC application context. IDS Working Group [Page 33]
RFC 1632 X.500 Catalog DEC X.500 Admin.Facility (2) Bind security levels of none andsimple (unprotected passwords). CONFORMANCE WITH PROPOSED INTERNET STANDARDS Supports RFC1006, RFC 1274,and RFC1277. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs RFC 1278. INTEROPERABILITY Interoperability test results will be available on request from Digital. Interoperability testing isbeing undertaken using the harmonized OSIone X.500 testsuite to which both OSInet and EurOSInet havebeen key contributors. PILOT CONNECTIVITY Digital is actively involvedin bothpublic and private pilots of X.500. BUGS [No information provided--Ed.] CAVEATSand GENERAL LIMITATIONS [No information provided--Ed.] INTERNETWORKINGENVIRONMENT The DEC X.500 AdministrationFacility operates over: * RFC 1006 over TCP/IP on ULTRIX platforms. * OSI TP0, TP2 and TP4 over CLNS andCONS asappropriate on ULTRIX andOpenVMSplatforms HARDWARE PLATFORMS The DEC X.500 AdministrationFacility V1.0 runs on: * VAX processors supported by OpenVMS * RISC processors supported by ULTRIX IDS Working Group [Page 34]
RFC 1632 X.500 Catalog DEC X.500 Admin.Facility SOFTWARE PLATFORMS The DEC X.500 AdministrationFacility V1.0 runs on: * OpenVMS/VAX V5.5-2or 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 AdministrationFacility is commercially available from Digital Equipment Corporation. For further information please contact yourlocal Digital office, or: Gail Shlansky, Product Manager: Tel:+1 508 486 5138 email: gail.shlansky@lkg.mts.dec.com DigitalEquipment Corporation Networks and Communications Engineering 550 King Street Littleton, MA. 01460-1289 USA DATE LAST UPDATED August 2nd, 1993 IDS Working Group [Page 35]
RFC 1632 X.500 Catalog DIR.X 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 theSiemensNixdorfX.500 product on which the OSF DCE/GDS (DistributedComputing Environment/Global Directory Service)is based. It supports full DUAand DSAfunctionality for globally unique identification and location of objects in a network. It also provides functions to answerqueries(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 forDSAs and DUAs) Consists of both DUAand DSAimplementationsaccording to the CCITT X.500 (1988)and ISO9594 standard. The X/Open standard APIsfor XDS and XOM are provided. The XDS interface can also be used to access the OSF DCE/CDS (DCElocal Cell Directory Service) transparently. DIR.X has been successfully conformance tested. PICSand PCTRs are available for all tested protocols: DSA/DAP,DUA/DAP, Presentation, ACSEand Session embedded inX.500. Compliant with EWOS Agreements (which are being harmonized with OIW Agreements). Strong authentication according to X.509 andan XDS/XOM convenience library willbe included in the nextversion(Q2 1994). Support for X.500 (1993)is planned for Q4 1994. IDS Working Group [Page 36]
RFC 1632 X.500 Catalog DIR.X CONFORMANCE WITH PROPOSED INTERNET STANDARDS [No information provided--Ed.] CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs [No information provided--Ed.] INTEROPERABILITY Thisimplementation of DAP and DSP has successfully interoperated withthe X.500 implementations from ICL, UNISYS, E3Xand ISODE. PILOT CONNECTIVITY Several DIR.X DSAs are connected to the European X.500 pilotnetwork PARADISE. (DUA and DSA connectivity.) BUGS Problems andbug-report e-mail address: dirx-info@mch.sni.de CAVEATSAND GENERAL LIMITATIONS The softwareis highly portable and without any general limitations. INTERNETWORKINGENVIRONMENT OSI TP4 withCLNP OSI TP0, 2& 4 with X.25 RFC-1006 with TCP/IP DIR.X can use eitherBSD 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 VRelease4), OSF/1.1, AIX 3.1, HP-UX. A port to Windows-NT is planned for Q21994. AVAILABILITY DIR.X can bedelivered as a binary product or as source to OEM customers. The DIR.X product is commercially available from: IDS Working Group [Page 37]
RFC 1632 X.500 Catalog DIR.X Siemens Nixdorf Informationssysteme SNI BU BA NM12 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 IDS Working Group [Page 38]
RFC 1632 X.500 Catalog Directory 500 NAME Directory 500 (tm) OSIware / Infonet Software Solutions KEYWORDS CommerciallyAvailable, 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. Theyare theDirectory User Agent (DUA) and the Directory System Agent (DSA). The DUA is the interface between theOSI Directory and thoseusers wishing access to the Directory's information. Usersmake their requests through theDUA. When forwarding user's requests tothe OSI Directory, the protocol usedis known as theDirectory Access Protocol (DAP). The DSA willnegotiate with other, remote DSAs to obtain requested information or to update remote DIBs. DSAs use the DirectorySystem Protocol (DSP) to forward and answerthese requests.The DSAsupports chaining andreferrals. COMPLIANCE (applicable only forDSAs and DUAs) All X.500 1988 operations are supported along with all Object Classes specified inX.521 and all AttributeTypes specifiedin X.520. Implementation plansincludeupgrades to support the1992 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 EXPERIMENTALRFCs [No information provided--Ed.] IDS Working Group [Page 39]
RFC 1632 X.500 Catalog Directory 500 INTEROPERABILITY Tested with QUIPU. Other interoperability information not available at this time. PILOT CONNECTIVITY [No information provided--Ed.] BUGS Noneknown at this time. CAVEATSand GENERAL LIMITATIONS Noneknown at this time. INTERNETWORKINGENVIRONMENT RFC1006 withTCP/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.25Version7 required) AVAILABILITY Directory 500 is commercially as executable object code or as source codeform 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 IDS Working Group [Page 40]
RFC 1632 X.500 Catalog DOS-DE 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 intendedto be asimple-to-use DUA interface suitable for the naiveuser. It is anMS-DOS port of the standardUNIX DEimplementation - 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 aseries of (verbose) prompts asking for person's name; department; organization; country. There is extensive on-line help. The matching algorithms are such thatnear matches are presented tothe user beforeless good matches. `Power searching' is alsoavailable - this allowsa user to search for anentry even when theydo not know thename ofthe organisation in which the person works - you still have to specify the country. DOS-DE provides UFN style searching. Itis alsopossible to search locality entries. DOS-DE uses slightlydifferent search algorithms depending on whether it is accessing partof the Directory mastered by a Quipu DSA - Quipu DSAstend touse lots of replicationand so encourage searching. DOS-DE runs over theUniversity of Michigan LDAP. DE was funded by theCOSINE PARADISEproject. DOS-DE was developed by Andy Powell at the University of Bath. COMPLIANCE (applicable only forDSAs and DUAs) N/A CONFORMANCE WITH PROPOSED INTERNET STANDARDS [RFC1274] and [RFC 1487] CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs [RFC1484]. IDS Working Group [Page 41]
RFC 1632 X.500 Catalog DOS-DE INTEROPERABILITY N/A PILOT CONNECTIVITY N/A BUGS Doesn't handle aliases well when power searching. Sendbug reports to: A.Powell@bath.ac.uk CAVEATSand GENERAL LIMITATIONS DOS-DE triesto cater well for the general case, at the expense of not dealing with theless typical. The mainmanifestation of this is thatthe current version does not handle searching under localities verywell. It is not possible to display photographs orreproduce sound attributes. INTERNETWORKINGENVIRONMENT University of Michigan LDAP. HARDWARE PLATFORMS IBM PC/AT/XTand compatibles. SOFTWARE PLATFORMS LDAPfor MS-DOS running overthe NCSA Telnetstack or SUN's PCNFS version 4.1 or Novell's LAN Workplace (LWP). AVAILABILITY The softwareis openly available by FTP fromftp.bath.ac.uk,as pub/x500/dosde.zip. The very latest codewill bemade available with theISODE Consortium release of ISODE. It is hoped it will be freely available to all. Contact: IDS Working Group [Page 42]
RFC 1632 X.500 Catalog DOS-DE A.Powell@bath.ac.uk DATE LAST UPDATED or CHECKED March 18th, 1993 IDS Working Group [Page 43]
RFC 1632 X.500 Catalog HP X.500 Dist. Dir.Products NAME HP X.500 DistributedDirectory Products Hewlett Packard KEYWORDS API,CLNS, Commercially Available, DSA/DUA, DUA only, HP, OSI Transport, X.25 ABSTRACT HP X.500 DistributedDirectory. Its main components are: DUA, andDUA Interface, DSA and DIB support, X.500 Address Lookup, X/Open Application Tool Kit API (XAT) for XDS/XOM Interface, X.500 High LevelAPI (X5HLAPI) for XDS/XOM Interface. HP X.500 DUA. Its main components are: DUA, andDUA Interface, X.500 Address Look-up, X/Open Application Tool Kit API (XAT) for XDS/XOM Interface, X.500 High LevelAPI (X5HLAPI) for XDS/XOM Interface. HP X.500 DistributedDirectory is based on the 1988 CCITT X.500 standard. HP X.500 can be used for accessing names and electronic mailaddresses for multi-vendor messaging backbone networks.HP X.500 can also be used forthe developmentof networked applications requiring distributed directory functionality. HP OpenMail users can accessthe enterprise wide HP X.500 distributed directory directly from the HP OpenMail userinterface, and select X.500 addresses for mailing.HP-UX Sendmail users can access electronic mail addresses from a X.500 server over aTCP/IP network. Users of non-HP e-mail systems can access data stored in theX.500 Directory using X.500 Address Look-up. X.500AddressLook-uphas an easyto use interface, and phonetic search capability. HP X.500 DistributedDirectory includes a complete multi-threaded DUA and DSA. TheX.500 DIB is built on adatabase which has been optimized for X.500 performance. HP X.500 contains full support for DAP and DSP protocols. IDS Working Group [Page 44]
RFC 1632 X.500 Catalog HP X.500 Dist. Dir.Products DataShadowing and security access control of HP X.500 Distributed Directory allow higher performance, and easier management ofits DIB database in a globalenvironment. HP X.500 DistributedDirectory has menu driven administration and userinterface tools. The tools simplify directory configuration and dataretrieval. It supports X/Open X.500 APIs (XDS and XOM),and high level APIs on top ofXDS to allow developersto write their own X.500 based applications. HP X.500 DistributedDirectory supports comprehensive tracing and logging facilities for quickdiagnosis and resolution of problems. HP alsoprovides a richset of troubleshooting tools tocheck the interoperability of the network at various layers ofthe OSIstack. COMPLIANCE (applicable only forDSAs and DUAs) HP X.500 DistributedDirectory complies withthe 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 - ProtocolSpecifications *x.509 describes simple and strongauthentication.HP X.500 Distributed Directory supports simple authentication. Strong authentication isnot supported in the current release due to limited market demand. HP X.500 DistributedDirectory will comply with NISTand EWOS directory functionalprofiles. Basedon factors suchas market needs and NIST recommendations, HPwill implement subsets of 1992 CCITT functionality in a phased approach. CONFORMANCE WITH PROPOSED INTERNET STANDARDS [No information provided--Ed.] CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs [No information provided--Ed.] IDS Working Group [Page 45]
RFC 1632 X.500 Catalog HP X.500 Dist. Dir.Products INTEROPERABILITY HP has done some unofficial interoperabilitytesting. HP would welcome suggestions on priorities for vendorinteroperability testing. PILOT CONNECTIVITY [No information provided--Ed.] BUGS [No information provided--Ed.] LIMITATIONS HP X.500 DistributedDirectory supports up to 30 DSAconnections at one time. This limitcould be increased in the future if needed. INTERNETWORKINGENVIRONMENT HP X.500 DistributedDirectory resides on anOSI stack, and can be usedin 802.3 LAN, or X.25 CLNS or CONS environment.HP is investigating implementing X.500 forthe TCP/IP environment. HARDWARE PLATFORMS HP X.500 DistributedDirectory is available on HP 9000 Series 800 family of high performance servers which arescalable platform. The HP X.500AddressLook-upfacility is also available for the HP 9000Series 300 and Series 700 for customerswho have purchased the X.500 product. SOFTWARE PLATFORMS HP X.500 DistributedDirectory requires the following software environment: - HP-UX Operating System 8.0or later - OSI Transport Services/9000 for the Series800 - HPLan Link or HP X.25 product - Network Tracing and Logging - ANSI C compiler (for the HP/XDS API) IDS Working Group [Page 46]
RFC 1632 X.500 Catalog HP X.500 Dist. Dir.Products AVAILABILITY HP X.500 DistributedDirectory is commercialavailable. The product can be ordered through HP Sales offices. Theordering numbers are: P/N J2152A HP X.500Distributed Directory/9000 for the Series 800. Product containsDSA server and DUA client. P/N J2153A HP X.500DUA/9000 for the Series800. Product containsonly DUA client. DATE LAST UPDATED or CHECKED August 16th,1993. IDS Working Group [Page 47]
RFC 1632 X.500 Catalog Univ. of Mich. LDAP Imple. 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 LDAPis the Lightweight Directory Access Protocol. It givesX.500 access to platforms that have only TCP/IP access, using simplified BER encodingof manyX.500 data elements. LDAP is currentlya proposed Internet Standard.The LDAP serveris an intermediate protocol server thatcommunicates with Internet clients on one side using the simple TCP-based LDAP protocol andan X.500 DSA onthe other side using theDirectory Access Protocol (DAP). A subset of the X.500 DAP is exported tothe clients through theLDAP protocol. The U-M LDAPdistribution contains the following components: - LDAP server - LDAP client library, including both synchronous and asynchronous APIs - Lightweight BER library, includingan 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 forDSAs and DUAs) The U-M LDAPdistribution isa complete implementation of the LDAP protocol. The LDAP protocoldoes not support accessto all X.500 features andoperations. The operations supported are bind,search, compare, add, delete, modify, modifyRDN, and abandon. Notethat readand list operations canbe emulated using the search operation. Sizeand time limitsmay be specified, as may alias dereferencing and searching, but all X.500 service controls are not supported. IDS Working Group [Page 48]
RFC 1632 X.500 Catalog Univ. of Mich. LDAP Imple. CONFORMANCE WITH PROPOSED INTERNET STANDARDS Compliant with [RFC 1485], [RFC 1487], and [RFC 1274]. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs 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. CAVEATSand GENERAL LIMITATIONS None, aside from those mentioned above undercompleteness. INTERNETWORKINGENVIRONMENT LDAPclientsuse TCPto communicate with theLDAP server. The LDAP server normally usesRFC 1006 with TCP/IP tocommunicate with the DSA,though any other transport mechanism for DSA communication supported byISODE should bepossible. HARDWARE PLATFORMS The LDAP server is known to run on Sun 3 andSun 4 platformsDEC's, HP's, and RS6000's. The LDAP client libraries and some clients have beenported to the Macintoshand thePC. SOFTWARE PLATFORMS The LDAP server and clients are known to rununder and SunOS4.1.x, ULTRIX, HP-UX, and AIX. TheLDAP client libraries also workunder Macintosh System 6.0or higher and MS-DOS 5.0. IDS Working Group [Page 49]
RFC 1632 X.500 Catalog Univ. of Mich. LDAP Imple. AVAILABILITY Thissoftware is openly available. It may be obtained by anonymous FTP from terminator.rs.itd.umich.eduin the x500 directory. Documentation on theLDAP and lightweight BER libraries is provided in the form of man pages distributedwith the sourcecode. More information can be obtained from ldap-support@umich.edu. Thissoftware was developed at the University of Michigan byTim Howes with help fromMark 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 Universityof Michigan. All rights reserved. Redistribution and use insource and binary formsare permitted provided that thisnotice is preserved andthat 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 fromthis 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 IDS Working Group [Page 50]
RFC 1632 X.500 Catalog ldap-whois++ NAME ldap-whois++ KEYWORDS Available via FTP, DEC ULTRIX, DUA Interface, Free, LDAP, RFC-1487, Sun,UNIX ABSTRACT ldap-whois++is a dua interface thatimplements the IETF WNILS draft whois++ proposal using the LDAP libraries developed by the University of Michigan. COMPLIANCE (applicable only forDSAs and DUAs) N/A CONFORMANCE WITH PROPOSED INTERNET STANDARDS RFC 1487 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs IETFWNILS WG Whois++ Architecture Draft. INTEROPERABILITY N/A PILOT CONNECTIVITY There are a number of servers running acrossthe Internet. BUGS Nonereported. CAVEATSand GENERAL LIMITATIONS Based on an early draft of the Whois++ Architecture Documentso there may be some inconsistencies with thelatest draft. It is considered a "beta" release due to thevolatility of the whois++ work. Once there isa whois++ RFC then a real release will be made. IDS Working Group [Page 51]
RFC 1632 X.500 Catalog ldap-whois++ INTERNETWORKINGENVIRONMENT 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.auas pub/whois/whois++beta.tar.Z. DATE LAST UPDATED or CHECKED August 3rd, 1993 IDS Working Group [Page 52]
RFC 1632 X.500 Catalog maX.500 NAME University of Michigan maX.500 Macintosh DUAInterface KEYWORDS Available via FTP, DUA Connectivity,DUA Interface, Free, LDAP, Macintosh, RFC-1274,RFC-1484, RFC-1485, RFC-1487 ABSTRACT maX.500 is aDirectory User Agent for Apple Macintosh. It is currently atversion2.0, which usesthe LightweightDirectory Access Protocol (LDAP) overTCP/IP to access The Directory. maX.500 can be usedto search for, view, create, delete, and modifyentries. It supports viewing of textual information, playing of audio, and viewing of black andwhite (fax) andcolor (JPEG) images. maX.500 is anative Macintosh application, and as such has afriendly interface. It requires System Software version 6.0.5 or later and Apple's MacTCP control panel. COMPLIANCE (applicable only forDSAs and DUAs) maX.500 works over LDAP, andis 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 EXPERIMENTALRFCs Preliminary support is included for [RFC 1484] (sameas U-M LDAP). INTEROPERABILITY maX.500 2.0 is knownto workwith the U-M LDAP server. It has been usedsuccessfully with the QUIPU DSAand others. PILOT CONNECTIVITY DUA connectivity should be possible to all pilots, though only AARNET, PARADISE, and PSI White Pages Project have actually been tried. IDS Working Group [Page 53]
RFC 1632 X.500 Catalog maX.500 BUGS Bug reports should be sent to max500-bugs@umich.edu. CAVEATSand GENERAL LIMITATIONS maX.500 doesnot support modification of "photo" (fax), "jpegPhoto", or "audio" attributes. Modify RDN is also unsupported. INTERNETWORKINGENVIRONMENT maX.500 is an LDAP client, and as such is uses TCP to communicate withthe LDAP server. Apple's MacTCP control panelis required on the Macintosh. HARDWARE PLATFORMS maX.500 runson Apple Macintosh Plusor later computers. Itrequires 1MB of RAM. SOFTWARE PLATFORMS maX.500 requires Apple System Software 6.0.5or later (System 7 preferred) and MacTCP 1.1 orlater (1.1.1 preferred). AVAILABILITY Thissoftware is openly available. It may be obtained by anonymous FTP from terminator.rs.itd.umich.eduin the x500 directory.More information can be obtained from ldap-support@umich.edu. Thissoftware was developed at the University of Michigan byMark Smith with help fromTim Howes and many others around the Internet. It is subject to thefollowing copyright: Copyright (c) 1993Regentsof the University of Michigan.All rights reserved. Redistribution and use in binaryforms is permitted providedthat this notice is preserved and that due credit is given tothe University of Michigan at Ann Arbor. The name of the University maynot be used to endorse or promote products derived from thissoftware without specific priorwritten permission. This software is provided ``asis'' without express or implied warranty. DATE LAST UPDATED OR CHECKED July26th, 1993 IDS Working Group [Page 54]
RFC 1632 X.500 Catalog MXLU NAME MXLU Brunel University, UK KEYWORDS DUA Connectivity, DUA Only, Free, Motif, Multiple Vendor Platforms, Needs ISODE,Source,UNIX, XWindow System ABSTRACT MXLU(Motif/X LookUp) is an X.500 DUA interface for the X Window System usingMotif. Ported from the Athena widgets version, MXLUcan be configured for manydifferent styles of interaction. Example configurationsare provided forsingle window and multiple window use. MXLUimplements the `User-Friendly Naming' search strategy and also has a form-filling search mode. Asynchronousdirectory operations are used. Fulluser friendly add and modify functions are provided, with the ability to tailor the modifyscreen 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 forDSAs and DUAs) 88 Standard compliant: Strong authenticationnot yetimplemented. No plans for support ofthe 1992 Standard. CONFORMANCE WITH PROPOSED INTERNET STANDARDS No plans at present. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs No plans at present. INTEROPERABILITY Tested with ISODE-8.0 IDS Working Group [Page 55]
RFC 1632 X.500 Catalog MXLU PILOT CONNECTIVITY DUA Connectivity: The interface is in use inthe UK Academic Directory Pilot. BUGS Bugsshould be reported to x500@brunel.ac.uk. CAVEATSand GENERAL LIMITATIONS Doesnot support modification of allknown attributesyntaxes. In particular, ACLs andO/R addresses are not catered for. INTERNETWORKINGENVIRONMENT As ISODE. HARDWARE PLATFORMS MostUNIX machines. SOFTWARE PLATFORMS UNIX Motif 1.1 > ISODE/QUIPU (version8.0 >) AVAILABILITY Sources are freely availablefor commercial or non-commercial use. Binaries forSunOs 4.1.3 arealso available from Brunel, to simplify installationon 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 IDS Working Group [Page 56]
RFC 1632 X.500 Catalog MXLU UK E-mail: x500@brunel.ac.uk. Fax:+44 89532806 (Andrew Findlay) Telephone: +44 895 203066 (Andrew Findlay) DATE LAST UPDATED or CHECKED March 10th, 1994 IDS Working Group [Page 57]
RFC 1632 X.500 Catalog PathWay Messaging 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 fullX.400 MTA and X.400-Internet gateway thatincludes 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 successfullyparticipated inOSInet X.500 I-Lab interoperability tests. PathWay Messenger isan email application for desktop class machines witha limited functionalityDUA Light Weight Clientthat provides access (per RFC 1202, Directory Assistance Service -supportfor LDAP is planned) over TCP/IP to the X.500DSA/DUAincluded with PathWay Messaging Services. COMPLIANCE (applicable only forDSAs 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 conformantto 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 asis 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]. IDS Working Group [Page 58]
RFC 1632 X.500 Catalog PathWay Messaging CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs PathWay Messaging Services' X.500 supports the following Internet Proposals: [RFC 1202] and [RFC 1278]. INTEROPERABILITY PathWay Messaging Services has undergone successful interoperability testing withControlData, DEC, HP, and the ISODE Consortiumusing EurOSInet test suites. PILOT CONNECTIVITY Tested DUA and DSA connectivity withPARADISE and PSI White Pages Project. BUGS Sendbug reports to: prod-eng@twg.com CAVEATSand GENERAL LIMITATIONS [No information provided--Ed.] INTERNETWORKINGENVIRONMENT RFC1006 withTCP/IP,TP4 with CNLS, TP0/2 orTP4 with X.25. HARDWARE PLATFORMS PathWay Messaging Services runs on all models of SunSPARC 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. IDS Working Group [Page 59]
RFC 1632 X.500 Catalog PathWay Messaging AVAILABILITY PathWay Messaging iscommercially available from: The Wollongong Group, Inc. 1129 San Antonio Road Palo Alto, CA 94303 USA Sales and Information: (415) 962 7100 FAX: (415) 969-5547 DATE LAST UPDATED or CHECKED July27th, 1993 IDS Working Group [Page 60]
RFC 1632 X.500 Catalog PC-DUA NAME PC-DUA NEXOR KEYWORDS 386,Commercially Available,DUA Connectivity, DUA Interface, IBM PC, LDAP, RFC-1487 ABSTRACT PC-DUA provides a MSWindowsbased user interface tothe X.500 Directory. Features include: - Searching - Directory Browser - to enable userto identify directory entry - History - allowingquick access topreviously referenced parts ofthe DIT. - User Friendly Name(UFN) based searching - Hypertext-like navigation. - Friendly names forattribute labels. - Intelligent choiceof entries to display when moving to a new location in the DIT. - O-line hypertext help. COMPLIANCE (applicable only forDSAs and DUAs) Compliant with LDAP. CONFORMANCE WITH PROPOSED INTERNET STANDARDS The following are supported:RFC 1487 CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs [No information provided--Ed.] INTEROPERABILITY PC-DUA has interoperated with LDAP 2.0 and 3.0 beta distributions. IDS Working Group [Page 61]
RFC 1632 X.500 Catalog PC-DUA PILOT CONNECTIVITY FullDUA connectivity to thePARADISE and PSI White Pages X.500 Pilots. BUGS No known bugs. Support is given viaphone or email to "support@nexor.co.uk" CAVEATSand GENERAL LIMITATIONS None. INTERNETWORKINGENVIRONMENT WinSock based TCP/IPstacks HARDWARE PLATFORMS 386 PC WITH 4MGBYTESRAM SOFTWARE PLATFORMS MS WINDOWS 3.1 AVAILABILITY PC-DUA is commercialsoftware. For more details contact: NEXOR 8 Faraday Building Highfields Science Park Nottingham NG7 2QP UK DN:c=GB@o=NEXOR Ltd Telephone:+44 602520500 Fax:+44 602520519 E-Mail:sales@nexor.co.uk DATE LAST UPDATED or CHECKED August 6th, 1993 IDS Working Group [Page 62]
RFC 1632 X.500 CatalogPC-Pages NAME PC-Pages Brunel University, UK KEYWORDS DUA Connectivity, DUA Only, IBM PC, LDAP, Limited Availability, Multiple Vendor Platforms, OSI Transport, RFC-1006 ABSTRACT PC-Pages is a MS-DOSbased X.500 DUAinterface. It is currently only available for MS-Windows; a DOS character mode interface is being prepared. Features include: - "Form" based searching. - Supports the User FriendlyName (UFN) specification (RFC 1484). - Powerful query engine. - Tailorableentry display -displayonly those attributes required. - Integrateswith the WhiteMail X.400 user agent. Hooks are provided toallow integration with other user agents. - Directory browsing. - Support for JPEG photo attributes. - Modify directory entries. - Add directory entries. - Delete directory entries. - Rebind to a configured DSA. - Some support for configuration of DAP service parameters. Two versionsof PC-Pages arecurrently available. One supports DAP overCONS orDAP over RFC-1006, and has dataentry and modification facilities.The other supports LDAPand hasa more advanceduser interface including a tree-browser, but doesnot yethave data entry and modification. A version inthe form or a Windows DLL (Dynamic LinkLibrary) is being prepared, for incorporation into otherproducts such as mail agents. COMPLIANCE (applicable only forDSAs and DUAs) 88 Standard compliant: Strong authenticationnot yetimplemented. No plans for support ofthe 1992 Standard. IDS Working Group [Page 63]
RFC 1632 X.500 CatalogPC-Pages CONFORMANCE WITH PROPOSED INTERNET STANDARDS [No information provided--Ed.] CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs [No information provided--Ed.] INTEROPERABILITY Tested with Quipu 8.0. PILOT CONNECTIVITY DUA Connectivity: The interface is in use inthe UK Academic Directory Pilot. BUGS Bugsshould be reported to x500@brunel.ac.uk. CAVEATSand GENERAL LIMITATIONS Doesnot support display or modification of all known attribute syntaxes. Inparticular: ACLs and O/R addresses. INTERNETWORKINGENVIRONMENT RFC1006 withTCP/IP.TP4 with CONS. A NetBIOS gateway to the previously listed protocols.LDAP using Winsock. HARDWARE PLATFORMS PC-Pages forWindowsrequires an IBMPC compatible with 286 or higher, 2mb+memory. SOFTWARE PLATFORMS Windows 3.0 or 3.1 running in Standard or Enhanced mode. WhiteStack 1.1,provided by theEdinburgh University Computing Service. AVAILABILITY Freeto UK Academic Community, and to some other communitiessubject to certain restrictions. Commercial derivatives exist. Please send queries to: IDS Working Group [Page 64]
RFC 1632 X.500 CatalogPC-Pages Postal: Andrew Findlay Computing and Media Services Brunel University Cleveland Road Uxbridge, Middlesex UB8 3PH UK E-mail: x500@brunel.ac.uk. Fax:+44 89532806 (Andrew Findlay) Telephone: +44 895 203066 (Andrew Findlay) DATE LAST UPDATED or CHECKED March 10th, 1994 IDS Working Group [Page 65]
RFC 1632 X.500 Catalog QuickMail NAME QuickMail/X.500 Interface (DUA Interface) NASA KEYWORDS DUA Interface, Limited Availability,Needs ISODE, RFC-1274, Sun ABSTRACT The NASA QuickMail/X.500 Interface program is a program which translates QuickMailname service requests into X.500 requests and returns the results from theDSA to the QuickMail user. This system allows QuickMail users the ability to find non-QuickMail users' or non-local QuickMail users' addresses, while retaining the normal QuickMail lookup interface.The program speaks QuickMail name service protocol on one side, and DAP on theother. COMPLIANCE (applicable only forDSAs and DUAs) [Same as dish] -- does not support strong authentication. No support for 1992 extensions needed. CONFORMANCE WITH PROPOSED INTERNET STANDARDS RFC 1274 supported to the extent that we useprovided schemato store QuickMail addresses. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs [No information provided--Ed.] INTEROPERABILITY Works with Quipu (ISODE 8.0,ICR1) PILOT CONNECTIVITY Connected toPSI WPPP, PARADISE. Other projects mayuse data if they are connected to either of these DSAs. BUGS No known bugs. Default QuickMail name service lookup time out of 10 seconds may be too fast for some DSAs to respond to. IDS Working Group [Page 66]
RFC 1632 X.500 Catalog QuickMail CAVEATSand GENERAL LIMITATIONS Requires theColumbia AppleTalk Package (CAP6.0) towork. INTERNETWORKINGENVIRONMENT EtherTalk orIPTalk on the Macintoshside, any ISODEsupported environment on the X.500 side. HARDWARE PLATFORMS Known to runon Sun 4/470 SOFTWARE PLATFORMS SunOS 4.1.1 and 4.1.3 can beused tohost the package. Additionally may need SunLink OSI7.0.1, Sunlink X.25 7.0. ISODE8.0 or ISODE Consortium Release 1needed to provide DAP support. AVAILABILITY Limited availability. For more details contact, Peter Yee MS 233-18 NASA AmesResearch Center Moffett Field, CA94035-1000 (415) 604-3812 (415) 604-6999 (FAX) yee@atlas.arc.nasa.gov DATE LAST UPDATED or CHECKED February 18th, 1993 IDS Working Group [Page 67]
RFC 1632 X.500 Catalog QUIPU (ISODE Con. Rel. 1.0) NAME QUIPU (ISODEConsortium Release 1.0) ISODE Consortium KEYWORDS API,DSA Connectivity, DSA/DUA, DUA Connectivity, Free, Multiple Vendor Platforms, OSI Transport, RFC-1006, RFC-1274,RFC-1275, RFC- 1276, RFC-1277, RFC-1278, RFC-1279, RFC-1484, RFC-1485, RFC-1487, Source, Sun,UNIX, X.25 ABSTRACT Thisimplementation is a source release derived fromthe earlier openly available version of QUIPU, and will be used as base technology for products by anumber of vendors. The release comprises of aDSA, and a number of sample DUAs which may be used in conjunction with theDSA. COMPLIANCE (applicable only forDSAs and DUAs) The DSA is aligned to the 1988 ISO IS and the NIST OIW Directory ImplementorsGuide Version 1, with the following exceptions: - Strong authentication is not implemented (but hooks are provided for use with two packages). - QUIPU doesnot enforce thebounds constraints on attributes, filters orAPDU size. - T.61 string formatting characters are not rejected. - Ifa DN issupplied with no password in anunprotected simple bind, QUIPU doesnot always check to seeif the DN exists. If the DSA connected to can say authoritatively the DN does not exist, the association is rejected. However, if a chain operation is required tocheck the DN, the bind IS allowed. - When comparing attributes of UTCtime syntax, if the seconds field isomitted, QUIPU does notperformthe match correctly (i.e., the seconds field in the attribute values should be ignored, but are not). - QUIPU always supplies the optionalChaining argument "originator" even if the CommonArgument "requestor" is used. - QUIPU always supplies the optionalChaining argument "target" even if the base object inthe DAParguments is the same. - The objectclass "without an assigned object identifier" is not recognised unless the "alias" object class is also present. - Non Specific Subordinate References are never followed by a QUIPU DSA, but they are passed on correctly to the client if generated. IDS Working Group [Page 68]
RFC 1632 X.500 Catalog QUIPU (ISODE Con. Rel. 1.0) Compliance with X.500(1993) standards is planned. DAP and replication (DISP) will be available in March 1994. Other 1993 features,with the exception ofDOB, but including security features will be available. CONFORMANCE WITH PROPOSED INTERNET STANDARDS [RFC1485], [RFC 1487], [RFC1274], [RFC 1276], [RFC1277]. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs [RFC1484], [RFC 1275], [RFC1278], [RFC 1279]. INTEROPERABILITY Interoperability with several other DSAs hasbeen demonstrated in pilot operation and at the COS X.500Interoperability Lab, enhancing interoperability results from the earler versions ofQUIPU. PILOT CONNECTIVITY Connectivityto the global research pilot (PARADISE etc.) has been demonstrated. It is expectedthat this system will be used extensively in a wide range of pilotactivities. DUA Connectivity, and DSA Connectivity. BUGS Bugsshould be reported to <bug-quipu@isode.com> CAVEATSand GENERAL LIMITATIONS None INTERNETWORKINGENVIRONMENT The IC R1.0 release is application level code, and assumes vendor provided lower layers. It provides the following modules with support for a range of APIs to handle associated lower layers: - RFC 1006 (vendor supplied TCP/IP using sockets or TLI) - Transport service (vendor suppliedtransport, which may beany class and use any network service.TLI, XTI and various vendor-specific APIs). - TP0 (Vendor supplied X.25 or CONS using NTI and various vendor specific APIs). IDS Working Group [Page 69]
RFC 1632 X.500 Catalog QUIPU (ISODE Con. Rel. 1.0) HARDWARE PLATFORMS Reference platform is SUN SPARC. SOFTWARE PLATFORMS Reference OSis SUNOS 4.1.3.It is also known to runon various other UNIXplatforms. AVAILABILITY Available tomembersof the ISODE Consortium. Membership is open to any organisation. Also available under licence (zerocost) to all non-commercial research organisations. Contact: ISODE Consortium Headquarters PO Box 505 London SW11 1DX UK Phone: +44-71-223-4062 Fax: +44-71-223-3846 Email:<ic-info@isode.com> DATE LAST UPDATED or CHECKED August 11th,1993 IDS Working Group [Page 70]
RFC 1632 X.500 Catalog Traxis Enterprise Directory NAME Traxis Enterprise Directory Angeli Systems Corporation KEYWORDS API,CLNS, Commercially Available, DSA/DUA, HP, IBM PC, IBM RISC, Macintosh, OSI Transport, RFC-1006, RFC-1274, Sun, X.25 ABSTRACT The Traxis Enterprise Directory has multiplecomponents in athree layer architecture. The individual components of theTraxis family are buildingblocks which can be assembled in a flexible, modular way to build complex systems. At the enterprise level, is a distributed directory stored and managed by Traxis Directory Engines (TDEs). At the workgrouplevel Traxis Directory Hubs (TDHs)providethe means to integrate and connect Traxis Directory Engines to the widevarietyof realworld applicationsand systems which prevail in network environments. The TDE and the TDH support the myriad of clientapplications, including messaging and business applications,which require services from the Traxis directory. At the desktop level, the Traxis Desktop Client (TDC) provides a common set of facilities which simplify and enable communications, object manipulation,and results management as required between the Traxis Directory Huband applications. Thesecapabilities, which include fullaccess and management of the directory,are provided to applicationsthroughXDS++, the Traxis object oriented API. The Traxis Desktop Client also supports industrystandard clientsoftware interfaces such as MicrosoftMAPI, Apple OCE, CMC and VIM, through Compatibility Modules which map the standardAPI into XDS++.Through these APIs the Traxis Desktop Clientsupports applications of all kinds on PC,Macintosh, and UNIX systems. Angeli supplied Traxis applications include the Traxis Administrative Console management station, the Traxis Global Browser general directory tool, the Traxis Operator Assistance high-speed look-up, the Traxis Data BaseGateway, the Traxis Import Export Utility and more. The Traxis DirectoryEngine includesan X.500 DSA. The Traxis Directory Hub includes an X.500 DUA. IDS Working Group [Page 71]
RFC 1632 X.500 Catalog Traxis Enterprise Directory COMPLIANCE (applicable only forDSAs and DUAs) Traxis Directory Engine DSA is CCITT-1988 compliant with extended security andaccess control.Supports accesscontrolon User, Entry, and Attribute levels. DIB orsubtreeadministrative manager supported. Supports simple authentication with encrypted password. NISTOIW Stable Implementation Agreements [NIST-88] compliant. Support for February14, 1993 CCITT X.500 planned. X.509 in first halfof 1994. Replication and Administrative/Information Model in second half of 1994. CONFORMANCE WITH PROPOSED INTERNET STANDARDS Traxis conforms to RFC1274 which documents COSINE interoperability. LDAP(RFC 1487) is planned for inclusion in a later release of Traxis if market demand requires it. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs Traxis does not conform to the QUIPURFC Internet Proposals cited. As noted elsewhere, Traxis is fully compatible with QUIPU operationally but does not use the cited RFCs in itsinternal operations. INTEROPERABILITY Traxis has been extensively tested for interoperability withISODE QUIPU Version 8. Traxis Directory Engine (DSA) will serve DISH or other QUIPU DUAs using DAP. Traxis DirectoryHub interoperates with QUIPU DSA. All directory access functions and their chained equivalents are interoperable. PILOT CONNECTIVITY PARADISE DUA/DSA connectivity tested. BUGS Problems maybe reported to support@angeli.com. CAVEATSand GENERAL LIMITATIONS None. IDS Working Group [Page 72]
RFC 1632 X.500 Catalog Traxis Enterprise Directory INTERNETWORKINGENVIRONMENT Traxis Directory Hubto Traxis Directory Engine (or any DSA) communication via RFC1006 over TCP/IP, OSI TP4 with CLNS, and OSI TP0 withX.25. Traxis Desktop Client to Traxis DirectoryHub viaSPX/IPX or TCP/IP. Other LANprotocols supported in 1994. HARDWARE PLATFORMS Traxis Directory Huband Traxis Directory Engine: Sun and PCcurrently supported. IBM RS/6000, HP 9000, and others in 1994. Traxis Desktop Client and applications: PCcurrently supported; Macintosh in 1994. SOFTWARE PLATFORMS Traxis Directory Huband Traxis Directory Engine: All Sun platforms with SunOS 4.1.3 currently supported, Solaris 2.x in 1994. Industry standard PC platforms with SCO Open Desktop V3currently supported. Other UNIX platforms in 1994. Windows NT in1994. Traxis Desktop Client and applications: PCwith Windows 3.1 currently supported. MacintoshSystems6 and 7, UNIX Motif, DOS, XWindows, and others planned for1994. AVAILABILITY The Traxis Enterprise Directory is commercially available from: Angeli Systems Corporation 1659 Eleventh Street Santa Monica, CA 90404 +1 310 392 3000 +1 310 392 4700 FAX info@angeli.com DATE LAST UPDATED or CHECKED November 23rd, 1993 IDS Working Group [Page 73]
RFC 1632 X.500 Catalog UCOM.X 500 NAME UCOM.X 500 (tm) - E3.X [DSA and DUA] KEYWORDS 386,API, Bull, CLNS, Commercially Available, DEC ULTRIX, DSA Connectivity, DSA/DUA, DUA Connectivity, IBMRISC, Motif, Multiple Vendor Platforms, OpenLook, RFC-1006, RFC-1274, RFC-1277, RFC-1278, RFC-1279, Sequent, Sun, Tandem, UNIX, X.25 ABSTRACT UCOM.X 500 includes a Directory System Agent(DSA), various directory access APIs and Directory User Agents (DUAs). UCOM.X500 is a product based on PIZARRO, the research prototype developed at INRIA by Christian Huitema's team, and commercializedby TS-E3X, a member of the France Telecom group. Characteristics of the DSA are: - The DAP and DSP protocols are provided conformant with X.500 (88). - The DIB ismaintained in ASN.1 encoded format in the Unix file system. Utilitiesare provided toload and dump the DIB from and toASCII text files. - The DIT structure is held in main memory. Frequently used attributes may be held in inverted tables in memory to speed up searches. - Knowledge management: knowledge onmanageddomainsis stored in UCOM.X specific attributesof the DSA entries. - Schema: The X.500 (88), X.400 (88)and most of theCosine and Internet Schema are supported. Object class and attribute definitions are enforced.Users may define their own. - Simple authentication is provided;strong authentication and signed operations are being testedoperationally through TS-E3X's participation in PASSWORD,a VALUEprojectwith aim to pilot a European security infrastructure for network applications. - Access control: private mechanismsare provided toallow access control lists to be specified for parts ofthe DIT, to control modifications, andto specify access restrictions on attributes. - Management: a UCOM.X DSA object has been defined to allow operational parameters of the DSA to be managed via DAP. Administration utilities are provided to, e.g., generate usage statisticsand periodically updatethe database from various data sources including a knowledge discovery tool. The product offers aC language API conformant to X/Open's X/DS IDS Working Group [Page 74]
RFC 1632 X.500 Catalog UCOM.X 500 specification, and aC++ API(for release 10/93). The DUAs include a graphicaldirectory browser with powerfulsearch functionality for OpenLook and Motif, and a full-screen curses-based interface with full DAP functionality. TS-E3X's strategy for UCOM.X500 is three-fold: Firstly, to use it as the directory service for Spheris, France Telecom's range of electronic mail products based on X.400 (88)(release mid '94). Secondly, tooffer it to third parties developing specific applicationsusing X.500: current applications include a distributed application to control document transfer in a large French hospital and distributed applicationsmanagement in the French Post Office; planned usesincludeoffice applications forcontrolof document circulation (workflow) and cooperative document editing. Thirdly, to offer it to telecomms operators suchas France Telecom for application in network management. UCOM.X 500 is used extensively by French research centers involved in PARADISE. COMPLIANCE (applicable only forDSAs and DUAs) UCOM.X 500 conforms to X.500(88) asspecified in paragraph 9 of X.519. Development of the product based on X.500 (93) is planned for '94 withreleaseof a product conformantto the principal extensions at the end of '94. Emphasis is being placed on the shadowing protocol, the schema and access control. CONFORMANCE WITH PROPOSED INTERNET STANDARDS The COSINE and Internet Schema (RFC 1274) issupported with minor exceptions. The string representation ofPSAPs and theirinternal encoding conforms to RFC 1277. The string representation ofDNs will migrate to theInternet RFC 1485definition. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs RFC 1279 (X.500 and Domains)is supported. The string representation of PSAPs andtheir internal encodingconforms to RFC1278. AFRO(algorithme francais derecherche optimise), the search/ name resolution algorithmproposed by UCOM.X 500,differsfrom the UFN algorithm principally in that it attempts tooptimize by performing IDS Working Group [Page 75]
RFC 1632 X.500 Catalog UCOM.X 500 readoperations before resorting to searchesin order to exploit the nameerror information. INTEROPERABILITY Through UCOM.X 500'suse in the French PARADISE pilot, interoperability hasbeen informallybut extensivelytested with Quipu and other implementations. Detailed interoperability tests with Quipu,Marben and Siemens/Bull DIR/X are being conducted by the PARADISE OIFP (Operational Interworking) team at INRIA Rocquencourt, France. The productis currently also undergoing formal tests for conformance to the CTS2 DSA/DAP and ACSE/Presentation/Session specifications at the French OSI conformance test centre. PILOT CONNECTIVITY DSA and DUA connectivity to the PARADISE pilot. BUGS UCOM.X 500 is a commercial product. As such,it is supportedand bugs are fixed when detected. Bugreportscan be sent to our support team via electronic mail. CAVEATSAND GENERAL LIMITATIONS The DIT structure and inverted attribute tables are stored in main memory. The recommended mainmemory size fora DSA is 1 kb per node, i.e., 10 Mb for a database of 10,000objects. The current recommended maximum is adatabase size of the order of 100,000 objects. Of the selected attribute types defined in X.500 (88), the searchGuide attribute is notsupported ; neither arethe following attributes from the Cosine and Internet Schema (RFC 1274): OtherMailbox, MailPreferenceOption and the various quality attributes. The X/DS APIsupports the Basic Directory Contents (BDCP), the MHS Directory User (MDUP) and the StrongAuthentication (SAP) packages withminor limitations. A proprietary mechanism for definingnew classes and attributes is offered. Asynchronous operations and multiple concurrent sessionsare notsupported. Whilst referral may be handled automatically, continuation references are not. IDS Working Group [Page 76]
RFC 1632 X.500 Catalog UCOM.X 500 INTERNETWORKINGENVIRONMENT UCOM.X 500 includes a transport stack for TP0 with TCP/IP (RFC 1006) and X.25. The stackhas been portedto SunNet OSI for TP4 with CLNP. HARDWARE PLATFORMS UCOM.X 500 can easily be ported to any UNIX machine.It currently runson: Sun3 and 4, IBM RS6000, DEC ULTRIX (Vax and Mips), 386- based PCs, Bull DPX/2 and DPX/20, Sequent, Tandem and others. SOFTWARE PLATFORMS UCOM.X 500 is portable to any UNIX-like operating system. Ithas been ported to: UNIX SVR3and SVR4, SUN OS 4, AIX, SCO Unix, Interactive Unix, ULTRIX, HP-UX,Dynix (Sequent), BOS (Bull) andothers. Ports to thefollowing are planned: OS/2 ('94), Windows 3 ('94). The product does notmake use of an externalDBMS for the information base. AVAILABILITY UCOM.X is commercially available. For further information contact: PascalDuchamp, International Sales Address: TS-E3X, Le Capitole 44, avenue des Champs Pierreux, 99029 Nanterre Cedex, France Tel: (+33) 1-46-14-50-00 Fax: (+33) 1-46-14-58-16 Email:C=FR;A=atlas;P=e3x;O=e3x;OU1=paris;S=duchamp duchamp@paris.e3x.fr or: Laurence Puvilland, Marketing Email:C=fr;A=atlas;P=e3x;O=e3x;OU1=paris;S=puvilland puvilland@paris.e3x.fr or: Ascan Woermann, R&D Email:C=fr;A=atlas;P=e3x;O=e3x;S=Woermann woermann@e3x.fr DATE LAST UPDATED July, 1993 IDS Working Group [Page 77]
RFC 1632 X.500 Catalog Wang OPEN/services NAME WangOPEN/services (tm) WangLaboratories, Inc. KEYWORDS CLNS, Commercially Available, DSA/DUA, DUA Interface, HP, IBM PC, IBM RISC, Limited Functionality,OSI Transport, RFC-1006, Wang, X.25 ABSTRACT Wang's X.500products are a part of our OPEN/services product whose mainfeatures include the following: X.500 directory - Contains information aboutorganizations, individuals,and distribution lists.The directory is the primary vehicle by which users of OPEN/office, Wang's X.400 electronic mail product, address mail. Authentication Services - Verifies the loginname and password of eachuser logging into OPEN/services. International support - Provides character translation tables so that users can display screens containinginternational characters and use international collating sequences. Object management - Greatly increases the integration between OPEN/services, OPEN/office and otherWindows-based applications. Activity logging - Records the activities ofOPEN/services. This information can be useful for monitoring theOPEN/services processes and for troubleshooting. Database management - Provides utilities that validate and reorganize the OPEN/services databases including the Directory Information Base (DIB). OPEN/services includes a DSA, a DUA,and a DUA interface allrolled intoone product. (The DUA interfaceprotocol is private.) WangOPEN/services consists of two parts: software installedon a server and software installed on PC clients on a LAN. The client or end-user software enables users to log in and log out; change the login password; use the OPEN/services directory; andperformvarious actions, such as open and print, on files inthe Wang OPEN/applications and in certain third-partyapplications including IDS Working Group [Page 78]
RFC 1632 X.500 Catalog Wang OPEN/services Microsoft Windows File Manager. The server consists of the DSA, the DUA,the Directory Information Base,the service administration programs such as login authentication, the database management utilities, and activity logging. COMPLIANCE (applicable only forDSAs and DUAs) WangOPEN/services complies with the1988 CCITT Recommendations X.500-X.521 [CCITT-88] with the following exceptions. Whole tree searches arenot supported, nor doesthe product support chained adding, modifying, or deleting. Simple authentication is supported, but strong authentication isnot. In the future, the 1992 extensions to the X.500 standard will be supported byWang OPEN/services. CONFORMANCE WITH PROPOSED INTERNET STANDARDS Noneare supported at the present time. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs Noneare supported at the present time. INTEROPERABILITY The interoperabilityof OPEN/services with other X.500 products is untested. PILOT CONNECTIVITY Pilot connectivity between OPEN/services andthe AARNET project, NADF Pilot Project, NIST Pilot Project, PARADISE,and PSIWhite Pages Project has not beenattempted. BUGS To report problems with WangOPEN/services, contact your local Wang sales office, your Wang authorized reseller or call your regional support center. (In the USA,the number is 404-432-9001). CAVEATSand GENERAL LIMITATIONS None IDS Working Group [Page 79]
RFC 1632 X.500 Catalog Wang OPEN/services INTERNETWORKINGENVIRONMENT WangOPEN/services currentlyruns inthe following environments: RFC1006 withTCP/IP,TP4 with CNLS, TP0 withX.25 and SLIP. HARDWARE PLATFORMS Server Requirements Installing Wang OPEN/services Serverrequires the following hardware: a Wang RISC Series Server 220 or greater, oran IBM RISC System/6000(tm) witha minimum of 32MB of memory, or a Hewlett- Packard 9000Series 800 system with a minimum of 32 MB of memory. For eachsystem a minimum of 20 MB of free disk space ina file system is required. Client Requirements Installing OPEN/services forWindowsrequires the following hardware: a 386/SX CPUor later, at least 4 MBof memory, a hard disk drive withat least 2.5 MBof diskspace, and a VGA monitor. A pointing device is not required to run OPEN/services but is strongly recommended. Network Requirements OPEN/services has the following network requirements: 802.3 or 802.5 LAN,networkinterface cards(NICs) to support TCP/IP on client PCs, Ethernet or token ring adapters on the servers, and optionally X.25 cards on theservers. SOFTWARE PLATFORMS Server Requirements Installing Wang OPEN/services Serverrequires the following software: AIX Operating System, release 3.2.3 or later, with bundled support for the TCP/IP protocol suite, or HP-UX Operating System, Release 9.0 or later. Client Requirements OPEN/services for Windows requires the following software: Microsoft MS-DOS(tm) OperatingSystem,Release5.0 or later and Microsoft Windows 3.1 or later. IDS Working Group [Page 80]
RFC 1632 X.500 Catalog Wang OPEN/services AVAILABILITY WangOPEN/services is commercially availablefrom: Wang Laboratories, Inc. 1Industrial Avenue Lowell, Massachusetts 01851 Phone: 508-967-6114 FAX: 508-967-1105 To obtain OPEN/services, contact your local Wang sales office, your Wangauthorized reseller or call 1-800-NEW-WANG. DATE LAST UPDATED or CHECKED December 6th, 1993 IDS Working Group [Page 81]
RFC 1632 X.500 Catalog Xdi NAME Xdi - DUA Bellcore KEYWORDS Available via FTP, DUA Connectivity,DUA Only, Free,Limited Functionality, Multiple Vendor Platforms, Needs ISODE, RFC-1274, RFC-1484, Source, Sun, UNIX,X Window System ABSTRACT Xdi is a Directory User Agent (DUA) for the X WindowSystem. In addition to providing a user-friendly interface, it supports Directory interactions of different levels of complexity. Users can select different window screens to browse, search and modifythe Directory. There are two different search screens for name based search and attributebased search. It is simple to use for novice users but isalso useful formore advanced users to formulate complex search filters. Xdialso supports "user-friendly naming" inmany cases so that users are not requiredto knowX.500 naming format. COMPLIANCE (applicable only forDSAs and DUAs) 88 standard compliant: Delete and Add operations, and strong authentication not implemented. There are nofacilities to modify the RDNsof entries. CONFORMANCE WITH PROPOSED INTERNET STANDARDS RFC 1274 is supported. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs RFC 1484 is supported. INTEROPERABILITY Believed to be interoperablewith other DSAs. Only tested against ISODE/QUIPU DSAs. PILOT CONNECTIVITY DUA Connectivity IDS Working Group [Page 82]
RFC 1632 X.500 Catalog Xdi BUGS Sendbug reports to sywuu@thumper.bellcore.com CAVEATSand GENERAL LIMITATIONS INTERNETWORKINGENVIRONMENT Sameas ISODE. HARDWARE PLATFORMS Thissoftware has been tested on SUN4. It isexpected that the software is portableto SUN3and other UNIX machines. SOFTWARE PLATFORMS Xdi is expected to run on ISODE (release 7.0upwards) in UNIX environment. The 'xdi' directory has been designed to fit directly intothe ISODE source tree. Xdi requires X11R4, the associated Xt toolkit and Athena widget libraries. Also see the operating environmentsof ISODE. AVAILABILITY The Xdi software is available via anonymous FTP from thumper.bellcore.comin filepub/xdi.tar.Z. Source code and executables can be freely distributed or modified for non-commercial and non-profit use provided that allcopyright notices, permission and nonwarranty notice included in the software distributionremain intact. For further information contact Sze-Ying Wuuat sywuu@thumper.bellcore.com. DATE LAST UPDATED or CHECKED March 18th, 1993 IDS Working Group [Page 83]
RFC 1632 X.500 Catalog XLU NAME XLU Brunel University, UK KEYWORDS DUA Connectivity, DUA Only, Free, Multiple Vendor Platforms,Needs ISODE, Source, UNIX,X Window System ABSTRACT XLU (X LookUp) is anX.500 DUA interface forthe X Window System. XLU can be configured for many different styles of interaction. Example configurations are provided for single window and multiple window use. XLU implements the `User-Friendly Naming' search strategy and also has a form-filling search mode. Asynchronousdirectory operations are used. Fulluser friendly add and modify functions are provided, with the ability to tailor the modifyscreen to present simple subsets of the available attributes. COMPLIANCE (applicable only forDSAs and DUAs) 88 Standard compliant: Strong authenticationnot yetimplemented. No plans for support ofthe 1992 Standard. CONFORMANCE WITH PROPOSED INTERNET STANDARDS No plans at present. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs No plans at present. INTEROPERABILITY [No information provided--Ed.] IDS Working Group [Page 84]
RFC 1632 X.500 Catalog XLU PILOT CONNECTIVITY DUA Connectivity: The interface is in use inthe UK Academic Directory Pilot. BUGS Bugsshould be reported to x500@brunel.ac.uk. CAVEATSand GENERAL LIMITATIONS [No information provided--Ed.] INTERNETWORKINGENVIRONMENT As ISODE. HARDWARE PLATFORMS MostUNIX machines. SOFTWARE PLATFORMS UNIX MIT X11R5 libraries ISODE/QUIPU (version8.0 >) AVAILABILITY Sources are freely availablefor commercial or non-commercial use. 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 89532806 (Andrew Findlay) Telephone: +44 895 203066 (Andrew Findlay) IDS Working Group [Page 85]
RFC 1632 X.500 Catalog XLU DATE LAST UPDATED or CHECKED March 1st, 1993 IDS Working Group [Page 86]
RFC 1632 X.500 Catalog XT-DUA NAME XT-DUA NEXOR KEYWORDS Bull, CLNS, Commercially Available, DUA Connectivity, DUA Only, HP, IBM RISC, ICL, Motif, Multiple Vendor Platforms, OpenLook, OSI Transport, RFC-1006,RFC-1274, RFC-1277, RFC-1278, RFC-1484, Solbourne, Sun, X Window System, X.25 ABSTRACT XT-DUA provides a X-Windows based user interface to the X.500 Directory. Both Motif and OpenLook styles are supported. Browsing features include: - Passing ofuser address information to theXT-MUA X.400 user agent. - History - allowingquick access topreviously referenced parts of the DIT. - Customizable entrydisplay- allowing subsets of attributes be displayed when showing an entry. - User Friendly Name(UFN) based searching - Hypertext-like navigation. - Support for application entities e.g. startup of ftam session. - User defined name for attribute labels. - Support for photo and audio attributes. - Attribute value onscanline. - Intelligent choiceof entries to display when moving to a new location in the DIT. Management features include: - Creation of new entries. - Modification of existing entries (including RDN) -based on Quipu EDB format. - Deletion of entries. - Friendly editor ofmodifying QuipuACLs. - Rebinding - authenticated and to named DSA. - Full configurationof DAP request parameters IDS Working Group [Page 87]
RFC 1632 X.500 Catalog XT-DUA COMPLIANCE (applicable only forDSAs and DUAs) Compliant with X.500(88), and NIST SIA version 2 except X.509 strong authentication not implemented (under development). NEXOR is committed to migrate XT-DUAto the 1992 standards. CONFORMANCE WITH PROPOSED INTERNET STANDARDS The following are supported:RFC 1274 and RFC 1277. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs The following are supported:UFN [RFC 1484] and RFC 1278. INTEROPERABILITY XT-DUA has interoperated with all DSAs used in the PARADISE pilot. PILOT CONNECTIVITY FullDUA connectivity to thePARADISE and PSI White Pages X.500 Pilots. BUGS No known bugs. Support is given viaphone or email to "support@nexor.co.uk" CAVEATSand GENERAL LIMITATIONS None. INTERNETWORKINGENVIRONMENT OSI TP4 withCLNP, OSI TP0 with X.25or CONS, and RFC 1006 with TCP/IP HARDWARE PLATFORMS Sun Solbourne IBM RS/6000 Bull DPX 6000 HP Apollo9000 IDS Working Group [Page 88]
RFC 1632 X.500 Catalog XT-DUA SOFTWARE PLATFORMS SunOs 4.1.x AIX 3.2 HP-UX 9.01 Windows 3.1 (overLDAP) Other ports planned include SCO Unixand ICLDRS6000. AVAILABILITY XT-DUA is commercialsoftware. For more details contact: XT-DUA Sales NEXOR 8 Faraday Building Highfields Science Park Nottingham NG7 2QP UK DN:c=GB@o=NEXOR Ltd Telephone:+44 602520500 Fax:+44 602520519 E-Mail:sales@nexor.co.uk DATE LAST UPDATED or CHECKED August 2nd, 1993 IDS Working Group [Page 89]
RFC 1632 X.500 CatalogXT-QUIPU NAME XT-QUIPU NEXOR KEYWORDS Bull, CLNS, Commercially Available, DSA Connectivity, DSA Only, HP, IBM RISC, ICL, Multiple Vendor Platforms, OSI Transport, RFC-1006, RFC-1274, RFC-1276, RFC-1277, RFC-1278, RFC-1279, RFC-1484, RFC-1485, Solbourne, Sun, X.25 ABSTRACT XT-QUIPU is an X.500(88) DSA. Characteristics of the DSA are: - Full DAP access - Full DSP access - Support for X.400,X.500, and RFC 1274 attributes and object classes - Approximate match based onSoundex. - Flexible schema management - RFC 1276 Replication - Attribute level access control - Search andlist access control - Knowledge management mapped onto DIT - Attribute inheritance - Caching - Remote management COMPLIANCE (applicable only forDSAs and DUAs) Compliant with X.500(88), and NIST SIA version 2 except X.509 strong authentication not implemented (under development). NEXOR is committed to migrate XT-QUIPU to the 1992 standards. CONFORMANCE WITH PROPOSED INTERNET STANDARDS The following are supported:String DN format [RFC 1485], RFC 1274, RFC 1276, and RFC 1277. CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTALRFCs The following are supported:UFN [RFC 1484],RFC 1278, and RFC 1279. IDS Working Group [Page 90]
RFC 1632 X.500 CatalogXT-QUIPU INTEROPERABILITY XT-QUIPU interoperates will all DSAsused inthe PARADISE pilot. PILOT CONNECTIVITY XT-QUIPU DSAs are fully connected tothe PARADISE and PSI White Pages X.500 Pilots. BUGS No known bugs. Support is given viaphone or email to "support@nexor.co.uk" CAVEATSand GENERAL LIMITATIONS None. INTERNETWORKINGENVIRONMENT OSI TP4 wtihCLNP OSI TP0 withX.25 orCONS RFC 1006 with TCP/IP HARDWARE PLATFORMS Sun Solbourne IBM RS/6000 BullDPX 6000 ICL DRS/6000 HP Apollo 9000 SOFTWARE PLATFORMS SunOs 4.1.x AIX 3.2 DRS/NX 6000 HP-UX 9.01 Other ports planned include SCO Unix. AVAILABILITY XT-QUIPU is commercial software. For more details contact: IDS Working Group [Page 91]
RFC 1632 X.500 CatalogXT-QUIPU XT-QUIPU Sales NEXOR 8 Faraday Building Highfields Science Park Nottingham NG7 2QP UK DN: c=GB@o=NEXORLtd Telephone: +44 602 520500 Fax: +44 602 520519 E-Mail: sales@nexor.co.uk DATE LAST UPDATED or CHECKED August 2nd, 1993 IETF IDS Working Group [Page 92]
INTERNET-DRAFT March 1994 4. References [CCITT-88]CCITT, "Data Communications Networks Directory", RecommendationsX.500-X.521, Volume VIII - Fascicle VIII.8,IXth Plenary Assembly, Melbourne, November 1988. [NIST-88]National Institute of Standardsand Technology,"Stable Implementation Agreements for Open Systems InterconnectionProtocols", Version 2 Edition 1, NIST SpecialPublication 500-162, December 1988. [RFC 1202]Rose, M., "Directory AssistanceService", RFC 1202, Performance Systems International, Inc., February 1991. [RFC 1249]Howes, T., Smith, M., and B. Beecher, "DIXIE Protocol Specification",RFC 1249, University ofMichigan, August 1991. [RFC 1274]Barker,P., andS. Kille, "The COSINE and Internet X.500 Schema", RFC 1274, University College, London, England, November 1991. [RFC 1275]Kille, S., "ReplicationRequirements toprovidean Internet Directory using X.500," RFC 1275, University College, London, England, November 1991. [RFC 1276]Kille, S., "Replication and Distributed Operations extensions to provide an Internet Directory using X.500",RFC 1276, University College, London, England, November 1991. [RFC 1277]Kille, S., "Encoding Network Addressesto support operation over non-OSI lower layers", RFC 1277, University College, London, England, November 1991. [RFC 1278]Kille, S., "A string encoding of Presentation Address", RFC 1278, University College, London, England, November 1991. [RFC 1279]Kille, S., "X.500 and Domains",RFC 1279, University College, London, England, November 1991. [RFC 1484]Kille, S., "Using the OSI Directory to achieve User Friendly Naming", RFC 1484, ISODE Consortium, July 1993. [RFC 1485]S. Kille, "A String Representation of Distinguished IETF IDS Working Group [Page 93]
INTERNET-DRAFT March 1994 Names",RFC 1485, ISODEConsortium, July 1993. [RFC 1487]Yeong, W., Howes, T., and S. Kille, "X.500 Lightweight Directory Access Protocol", RFC1487, Performance SystemsInternational, University of Michigan, ISODE Consortium, July 1993. [RFC 1488]Howes, T., Kille, S., Yeong, W., and C.Robbins, "The X.500 String Representation of StandardAttribute Syntaxes", RFC 1488, Universityof Michigan, ISODE Consortium, PerformanceSystemsInternational, NeXor Ltd., July 1993. 5. Security Considerations Security issues are not discussed inthis memo. 6. Editors' Addresses Arlene F. Getchell Lawrence Livermore National Laboratory National Energy Research Supercomputer Center P.O.Box 5509, L-561 Livermore, CA 94551 Phone: (510)423-6349 EMail: getchell@es.net X.400: s=getchell;p=esnet;a=;c=us; Srinivas R. Sataluri AT&TBell Laboratories Room1C-429,101 Crawfords Corner Road P.O.Box 3030 Holmdel, NJ 07733-3030 Phone: (908)949-7782 EMail: sri@qsun.att.com IETF IDS Working Group [Page 94]