Last Call for X.500 Implementation Surveys

[Ruth Lang <[e-mail]>]

Folks,

We are preparing to make any final additions or modifications to the
DISI document, "A Catalog of Available X.500 Implementations."  We
will push this Internet-Draft toward FYI status before the next IETF
meeting.  The current version can be found in the internet-draft
directory as draft-ietf-disi-catalog-00.txt from the usual
distribution sites.

At this time, we'd like to solicit any last minute submissions.  Once
published as an FYI, the document will probably not be updated for at
least 6 months.

Please respond as requested below by October 31, 1991.

Thanks,

Russ Wright
Ruth Lang
-------------------------------------


		  X.500 Implementation Survey
			  October 1991

		Send submissions by October 31, 1991 to:

	   	   Ruth Lang  ([e-mail])
	   	   Russ Wright ([e-mail])


NAME
   The name of the X.500 implementation and the name of the
   responsible organization.  Fill out one form per named
   implementation.  Please indicate that the implementation has a
   registered trademark by appending "(tm)", e.g., GeeWhiz(tm).

KEYWORDS
   Please refer to the keyword glossary appended below and list those
   keywords that are appropriate to the described implementation.

ABSTRACT
   Write a brief (less than 250 words) description of the application
   and its capabilities.

COMPLETENESS
   State compliance with or describe any voids in implementation with
   respect to both the 1988 CCITT Recommendations X.500-X.521 and/or
   the 1988 NIST OIW Stable Implementation Agreements.  Specifically,
   please review and make comments with respect to Section 9 of X.519.

INTEROPERABILITY
   State which other DUAs and DSAs this implementation can
   interoperate with; also state test suite (if any) used to test
   interoperability.

PILOT CONNECTIVITY
   State the level of connectivity it 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.  Please describe connectivity in light of the
   following descriptions:

 	Not Tested: It should work in principle, but has not been
 	tested.

 	None: There is some reason why this cannot be achieved.
 
 	DUA Connectivity: The DUA can be connected to the pilot, and
 	information on any pilot entry looked up.  The DUA is able to
 	display	standard attributes and object classes and those
 	defined in the COSINE and Internet Schema.  Inability to
 	display certain attributes (e.g., photos) should be noted as a
 	caveat.  If known, it should be stated whether any pilot
 	participants are using a given DUA.
 
 	DSA Connectivity: The DSA is connected to the DIT, and
 	information in this DSA is accessible from any pilot DUA.
 	This is regarded as a minimum demonstration of the ability to
 	connect. State explicitly whether or not there is support for
	Internet DSP.

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 files and size, a feature that works on one platform but
   not another.

INTERNETWORKING ENVIRONMENT
   A list of environments in which this implementation can be used,
   e.g., RFC-1006 with TCP/IP, TP0 or TP4 with X.25.  Refer to the
   keyword glossary for more information.

HARDWARE PLATFORMS
  List hardware platforms on which this application runs, and any
  additional boards or processors required.  Include any special
  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.  In particular for DSA
   implementations, please list the DBMS used.  Include any special
   suggested or requirements configuration options.  Example:
   Distributed and supported for Sun OS version 4.0 and greater, and
   HP-UX version 7.0 and greater.  Uses Ingres as database backend.

AVAILABILITY
   State "free" or "commercially available".  Describe how software is
   acquired.  If free, 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.



			Keyword Glossary

This section contains keyword definitions.  They have been organized
and grouped by functional category.  The definitions are ordered first
alphabetically by keyword category, and second alphabetically by
implementation name within keyword category.


Availability

   Available via FTAM
        Implementation is available using FTAM.

   Available via FTP
        Implementation is available using FTP.

   Commercially Available
        This implementation can be purchased.

   Free
        Available at no charge, although other restrictions may apply.

   Potentially Unavailable
        Implementation was not available at the time this document was
        written.

   Source
        Source code is available, potentially at an additional cost.

Pilot Connectivity

   None
	There is some reason why this cannot be achieved.

   Not Tested
	 It should work in principle, but has not been tested.

   DUA Connectivity
	The DUA can be connected to the pilot, and information on any
	pilot entry looked up.  The DUA is able to display standard
	attributes and object classes and those defined in the COSINE
	and Internet Schema.

   DSA Connectivity
	The DSA is connected to the DIT, and information in this DSA
	is accessible from any pilot DUA.

   Internet DSP
	The DSA supports the Internet DSP application context as
	described by the Internet draft "Replication and Distributed
	Operations Extensions to Provide an Internet Directory Using
	X.500."
	
Implementation Type

   API
        Implementation comes with an application programmer's interface
        (i.e., a set of libraries and include files).

   DSA Only
        Implementation consists of a DSA only.  No DUA is included.

   DSA/DUA
        Both a DSA and DUA are included in this implementation.

   DUA Light Weight Client
        Implementation is a DUA-like program that uses a non-OSI proto-
        col to satisfy X.500 requests.

   DUA Only
        Implementation consists of a DUA only.  No DSA is included.

Internetworking Environment

   CLNP
        Implementation uses OSI CLNP.

   OSI Transport
        Implementation description specifies that OSI transport proto-
        cols are used but does not specify which one(s).

   RFC-1006
        Implementation uses RFC-1006 with TCP/IP transport service.

   X.25
        Implementation uses OSI X.25.

Operating Environment

   3Com
        Implementation runs on a 3Com platform.

   Apollo
        Implementation runs on an Apollo platform.

   Bull
        Implementation runs on a Bull platform.

   Cray
        Implementation runs on a Cray.

   DEC Ultrix
        Implementation runs under DEC Ultrix.

   HP
        Implementation runs on an HP platform.

   IBM (Non-PC and RISC)
        Implementation runs on some type of IBM, which is not a PC or
        UNIX workstation.

   IBM PC
        Implementation runs on a PC.

   IBM RISC
        Implementation runs on IBM's RISC UNIX workstation.

   MIPS
        Implementation runs on a MIPS RISC UNIX workstation.

   Macintosh
        Implementation runs on a Macintosh.

   Multiple Vendor Platforms
        Implementation runs on more than one hardware platform.

   Philips
        Implementation runs on a Philips platform.

   Siemans
        Implementation runs on a Siemans platform.

   Sun
        Implementation runs on a Sun platform.

   UNIX
        Implementation runs on a generic UNIX platform.

   Unisys
        Implementation runs on a Unisys platform.

   VMS
        Implementation runs under VAX/VMS.

Miscellaneous

   Included in ISODE
        DUAs that are part of ISODE.

   Limited Functionality
        Survey states that the implementation has some short commings or
        intended lack of functionality, e.g., omissions were part of the
        design to provide an easy-to-use user interface.

   Need ISODE
        ISODE is required to compile and/or use this implementation.

   X Window System
        Implementation uses the X Window System to provide its user
        interface.