X.500 Survey -- Please Respond
getchell@jasmine.nersc.gov (Arlene F. Getchell) Mon, 15 February 1993 20:11 UTC
Received: by merit.edu (5.65/1123-1.0) id AA15840; Mon, 15 Feb 93 15:11:19 -0500
Received: from jasmine.nersc.gov by merit.edu (5.65/1123-1.0) id AA15836; Mon, 15 Feb 93 15:11:17 -0500
Received: by jasmine.nersc.gov (4.1/LLNL-1.18) id AA00868; Mon, 15 Feb 93 12:06:38 PST
Date: Mon, 15 Feb 1993 12:06:38 -0800
From: getchell@jasmine.nersc.gov
Message-Id: <9302152006.AA00868@jasmine.nersc.gov>
To: disi, dssig@ics.uci.edu, iso@nic.ddn.mil, isode@nic.ddn.mil, osi-ds@cs.ucl.ac.uk
Subject: X.500 Survey -- Please Respond
X.500 Implementation Survey Goal Of This Survey: To gather new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings. The Integrated Directory Services (IDS) working group of the IETF plans to update RFC1292/FYI11 "A Catalog of Available X.500 Implementations". This RFC/FYI provides information to the Internet community regarding the availability and capability of implementations of X.500. It does not specify an Internet standard. Instructions For Completing This Survey: If you are an X.500 implementor or product representative with an X.500 implementation, please fill-out this survey using one form per application suite or named application. Return completed forms by March 1, 1993 to: Arlene Getchell (getchell@es.net) or Sri Sataluri (sri@qsun.att.com) For the purposes of this survey, we classify X.500 products as, (a) DSA: A DSA is an OSI application process that provides the Directory functionality, (b) DUA: A DUA is an OSI application process that represents a user in accessing the Directory and uses the DAP to communicate with a DSA, and (c) DUA Interface: A DUA Interface is an application process that represents a user in accessing the Directory using either DAP but supporting only a subset of the DAP functionality or a protocol different from DAP to communicate with a DSA or DUA. Choose the classification that best suits your product in completing this survey. Questions regarding how to complete the survey may be sent to either Arlene Getchell (getchell@es.net) or Sri Sataluri (sri@qsun.att.com). We apologize for the duplicates received by those of you who are on some or all the mailing list recipients of this message. Please feel free to pass this survey form to others who may have something to contribute. The editors and the IDS working group thank you for your participation! X.500 Implementation Survey Return completed forms by March 1, 1993 to: Arlene Getchell (getchell@es.net) or Sri Sataluri (sri@qsun.att.com) NAME: <List the name of the X.500 implementation, DSA, DUA, or DUA interface. Fill-out one form per named implementation. Implementations with a registered trademark should show this by appending "(tm)", e.g., GeeWhiz(tm).> ABSTRACT: <Write a brief (less than 250 words) description of the application. Specify clearly whether your implementation is a DSA, DUA or a DUA Interface. If your implementation is a DUA Interface, state which Protocol it uses (e.g. LDAP).> COMPLIANCE (applicable only for DSAs and DUAs): <State compliance with respect to the 1988 CCITT Recommendations X.500-X.521 [CCITT-88], specifically Section 9 of X.519, or the 1988 NIST OIW Stable Implementation Agreements [NIST-88]. E.g., 88 Standard compliant: Search function or strong authentication not yet implemented. State if your implementation supports or plans to support the 1992 extensions to X.500. If possible, indicate the projected date when 1992 extensions will be available in your implementation.> COMPATIBILITY WITH PROPOSED INTERNET STANDARDS: <State if your implementation supports any of the Internet Proposals specified in the references [Draft 1], [Draft 2], [Draft 3], [RFC 1202], [RFC 1249], [RFC 1274], [RFC 1275], [RFC 1276], [RFC 1277], [RFC 1278], [RFC 1279].> INTEROPERABILITY: <State which other DUAs and DSAs this implementation is known to interoperate with; also state test suite (if any) used to test interoperability.> PILOT CONNECTIVITY: <Describe the level of connectivity your product can offer to the following pilot directory services projects operational world-wide, AARNET project, NADF Pilot Project, NIST Pilot Project, PARADISE, and PSI White Pages Project. Levels of connectivity are: Not Tested, None, DUA Connectivity, and DSA Connectivity.> BUGS: <Warn the reader about any known problems and/or instructions on how to report bugs.> CAVEATS and GENERAL LIMITATIONS: <Warn the reader about possible side effects or any short-comings, e.g., log file size, a feature that works on one platform but not another.> INTERNETWORKING ENVIRONMENT: <List environments in which this implementation is used. Examples: RFC1006 with TCP/IP, TP4 with CNLS, TP0 or TP4 with X.25, SLIP.> HARDWARE PLATFORMS: <List hardware platforms on which this application runs. Also list any additional boards or processors required. Include any suggested or required configuration options necessary for reasonable performance. Example: GeeWhiz runs on all models of Sun-3, Sun-4, Sun-386i, Macintosh, and on IBM PC/AT/XT and compatibles.> SOFTWARE PLATFORMS: <List operating systems, window systems, unbundled software packages, etc. including version numbers required to run this application. Include any suggested or required configuration options. Example: Distributed and supported for Sun OS version 4.0 and greater, and HP-UX version 7.0 and greater.> AVAILABILITY: <State "openly available" or "commercially available". Describe how to obtain the software. If openly available, state distribution conditions/restrictions. Include company or institution name, and point(s) of contact for distribution, technical information, sales. State postal addresses and email addresses, phone and fax numbers as applicable. Examples: 1) The "GeeWhiz DS" is commercially available from: GeeWhiz International 135 A St. ATown, CA 94123 Sales and Information: (415) 555-1212 FAX: (415) 555-1234 2) "AllKnowing" is openly available via anonymous FTP from ak.auniv.edu; file /pub/ak.tar.Z. Contact A. Professor at a_professor@auniv.edu. Source code and executables can be freely distributed for non-commercial use.> DATE LAST UPDATED or CHECKED: <State the date you completed this survey form.> REFERENCES [CCITT-88] CCITT, "Data Communications Networks Directory," Recommendations X.500-X.521, Volume VIII - Fascicle VIII.8, IXth Plenary Assembly, Melbourne, November 1988. [NIST-88] National Institute of Standards and Technology, "Stable Implementation Agreements for Open Systems Interconnection Protocols," Version 2 Edition 1, NIST Special Publication 500-162, December 1988. [Draft 1] Kille, S., A String Representation of Distinguished Names. January 1993. INTERNET-DRAFT: draft-ietf-osids-distnames-05.txt [Draft 2] Kille, S., Using the OSI Directory to achieve User Friendly Naming. January 1993. INTERNET-DRAFT: draft-ietf-osids-friendlynaming-05.txt [Draft 3] Yeong, W., T. Howes, and S. Kille, Lightweight Directory Access Protocol. January 1993. INTERNET-DRAFT: draft-ietf-osids-lightdirect-03.txt [RFC 1202] Rose, M. T., Directory Assistance Service. February 1991. [RFC 1249] Howes, T., M. Smith, and B. Beecher, DIXIE Protocol Specification, University of Michigan, August 1991. [RFC 1274] Barker, P., and S. Kille, The COSINE and Internet X.500 Schema, University College, London, England, November 1991. [RFC 1275] Kille, S., Replication Requirements to provide an Internet Directory using X.500, University College, London, England, November 1991. [RFC 1276] Kille, S., Replication and Distributed Operations extensions to provide an Internet Directory using X.500, University College, London, England, November 1991. [RFC 1277] Kille, S., Encoding Network Addresses to support operation over non-OSI lower layers, University College, London, England, November 1991. [RFC 1278] Kille, S., A string encoding of Presentation Address, University College, London, England, November 1991. [RFC 1279] Kille, S., X.500 and Domains, University College, London, England, November 1991.
- X.500 Survey -- Please Respond Arlene F. Getchell