revised x.500 survey
wright@lbl.gov (Russ Wright) Fri, 12 April 1991 22:41 UTC
Received: by merit.edu (5.65/1123-1.0) id AA06221; Fri, 12 Apr 91 18:41:02 -0400
Received: from lbl.gov by merit.edu (5.65/1123-1.0) id AA06202; Fri, 12 Apr 91 18:40:46 -0400
Received: from Mac-mailer (b50b-cnr9.lbl.gov) by lbl.gov (4.1/1.39) id AA11515; Fri, 12 Apr 91 15:40:48 PDT
Message-Id: <9104122240.AA11515@lbl.gov>
Date: Fri, 12 Apr 1991 15:40:41 -0000
From: wright@lbl.gov
To: disi
Subject: revised x.500 survey
Folks, Enclosed is a revised draft that has been modified on the basis of comments received through 4/11/91. Please read it and send any last comments or suggestions to Russ and Ruth by 4/15. We will distribute the survey on 4/16. The survey recipient list includes: disi@merit.edu iso@nic.ddn.mil isode@nic.ddn.mil osi-ds@cs.ucl.ac.uk David Goodman <D.Goodman@cs.ucl.ac.uk> Thanks! Ruth Lang (rlang@nisc.sri.com) Russ Wright (wright@lbl.gov) --------------------------------------------- X.500 Implementation Survey April 1991 Goal Of This Survey: To gather information regarding currently available implementations of X.500 including products, public domain and openly available implementations. The Directory Information Services Infrastructure (DISI) working group of IETF will produce an RFC/FYI that identifies existing implementations of the X.500 standard. This RFC/FYI will provide information to the Internet community regarding the availability and capability of X.500 implementations. It will not specify a standard, list IAB policy, or list IAB recommendations. It will be similar in intent, nature, and scope to the Network Management Tools Catalog (RFC 1147/FYI 2). Instructions For Completing This Survey: If you are an X.500 implementor or product representative, please fill-out this survey using one form per application suite or named application. Return completed forms by April 26, 1991 to: Ruth Lang (rlang@nisc.sri.com) Russ Wright (wright@lbl.gov) Questions regarding how to complete the survey may also be sent to either Ruth Lang or Russ Wright. The authors and the DISI working group thank you for your participation! X.500 Product and Public Domain Implementation Survey April 1991 Return completed forms by April 26, 1991 to: Ruth Lang (rlang@nisc.sri.com) Russ Wright (wright@lbl.gov) NAME: <List the name of the X.500 implementation, DSA, DUA, or DUA interface process. Fill-out one form per named implementation. If commercial, indicate name trademark by "(tm)", e.g., GeeWhiz(tm).> ABSTRACT: <Write a brief (less than 250 words) description of the application. Include a list of Pilot projects in which the application is being used.> COMPLETENESS: <State compliance with or describe any voids in implementation with respect to both the '88 standard and the 88 OIW Implementation Agreements. E.g., '88 Standard: Search function or strong authentication not yet implemented.> INTEROPERABILITY: <State which other DUAs and DSAs this implementation can interoperate with; also state test suite (if any) used to test interoperability.> BUGS: <Warn the reader about any problems and/or advertise bug report email address.> CAVEATS and GENERAL LIMITATIONS: <Warn the reader about possible side effects, any short comings, e.g., log file size and disk space requirements, a feature that works on one platform but not another.> INTERNETWORKING ENVIRONMENT: <List environments in which this implementation is used. Examples: RFC 1006 with TCP/IP, TP0 or TP4 with X.25.> HARDWARE PLATFORMS: <List hardware platforms this application runs on. Also list any additional boards or processors required. Include any suggested or required configuration options. Example: GeeWhiz run on all models of Sun-3, Sun-4, Sun-386i, and on IBM PC/AT/XT and compatibles.> SOFTWARE PLATFORMS: <List operating systems, window systems, unbundled software packages, etc. including version numbers. 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 software is acquired. 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.
- revised x.500 survey Russ Wright