Update of RFC1292
getchell@jasmine.nersc.gov (Arlene F. Getchell) Wed, 11 November 1992 01:11 UTC
Received: by merit.edu (5.65/1123-1.0) id AA27335; Tue, 10 Nov 92 20:11:04 -0500
Received: from jasmine.nersc.gov by merit.edu (5.65/1123-1.0) id AA27331; Tue, 10 Nov 92 20:11:03 -0500
Received: by jasmine.nersc.gov (4.1/LLNL-1.18) id AA01781; Tue, 10 Nov 92 17:07:28 PST
Date: Tue, 10 Nov 1992 17:07:28 -0800
From: getchell@jasmine.nersc.gov
Message-Id: <9211110107.AA01781@jasmine.nersc.gov>
To: disi
Subject: Update of RFC1292
As you know we are working on updating RFC 1292 " A Catalog of Available X.500 Implementations." We modified the survey form, after soliciting input on its format and content. We have tried to incorporate all the suggestions received. The latest version of survey form is enclosed. We would appreciate if you could take the time to look it over and bring your comments to the DISI working group meeting at the IETF. Regards, Arlene Getchell (getchell@es.net) Sri Sataluri (sri@qsun.att.com) --------------------------------cut here-------------------------------------- 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 Directory Information Services Infrastructure (DISI) 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 that did not appear in RFC1292, please fill-out this survey using one form per application suite or named application. Return completed forms by December 16, 1992 to: Arlene Getchell (getchell@es.net) or Sri Sataluri (sri@qsun.att.com) For implementations that currently appear in RFC1292, we will be contacting the original authors individually to solicit updated information. 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 DISI working group thank you for your participation! X.500 Implementation Survey Return completed forms by December 16, 1992 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 Lightweight Protocol it uses (e.g. LDAP).> COMPLIANCE: <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. State if your implementation supports any of the proposed Internet Standards specified in RFCs 1274, 1276, and 1277 (see References).> 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 pilot directory service operational on the Internet in North America, and to pilots co-ordinated by the PARADISE project in Europe. 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.> LAST MODIFIED: <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. [RFC 1274] Barker, P., and S. Kille, The COSINE and Internet X.500 Schema, 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.
- Update of RFC1292 Arlene F. Getchell