draft survey form

Ruth Lang <rlang@NISC.SRI.COM> Mon, 08 April 1991 23:13 UTC

Received: by merit.edu (5.65/1123-1.0) id AA25901; Mon, 8 Apr 91 19:13:25 -0400
Received: from [192.33.33.128] by merit.edu (5.65/1123-1.0) id AA25897; Mon, 8 Apr 91 19:13:22 -0400
Received: by ws28.nisc.sri.com (5.64/SRI-NISC1.1) id AA00297; Mon, 8 Apr 91 16:12:12 -0700
Message-Id: <9104082312.AA00297@ws28.nisc.sri.com>
To: disi
Cc: wright@lbl.gov, rlang@NISC.SRI.COM
Subject: draft survey form
Date: Mon, 08 Apr 91 16:12:11 PDT
From: Ruth Lang <rlang@NISC.SRI.COM>

All,

Below is a draft of the form that Russ and I have composed for use to
survey for existing X.500 implementations.  We would like to issue it
next week (on 4/15), so please send any comments to us, cc
disi@merit.edu by 4/12.  Within the next day or so, we'll send out an
accompanying note that describes the survey process -- so, if you have
any process-related questions, please hold them until you see that
note.

Please also suggest additions to list of survey recipients (by 4/12).
The present list includes:

   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
Russ Wright

---------------------------------------------

	X.500 Product and Public Domain Implementation Survey
			    April 1991

Goal Of This Survey:

Gather information from product vendors and public domain implementors
on the availability of software that implements the X.500 standard.

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 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 files and size, 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, 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.  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.>


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.

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 publically 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.
>