rfc1292.txt

RFC 的详细文档！

DISI Working Group				               [Page 10]

RFC 1292		     X.500 Catalog		    January 1992


   Source				 UNIX

	DCE/GDS				      Custos
	DE				      DE
	DS-520,	DS-521			      DIXIE
	Mac-ISODE			      DS-520, DS-521
	OSI-DSA				      IS X.500 DSA/DSAM, DUA
	OSI-DUA				      POD
	POD				      QUIPU
	psiwp				      SD
	QUIPU				      UCOM X.500
	ud				      ud
	VMS-ISODE			      WIN/DS
	WIN/DS				      Xdi
	Xdi				      XLU
	Xds				      XT-DUA
	xdua				      xwp [PSI]
	XLU				      xwp [UWisc]

   Sun					 Unisys

	Alliance OSI X.500		      OSI-DSA
	Custos				      OSI-DUA
	Directory 500
	DIXIE				 VMS
	QUIPU
	UCOM X.500			      DISH-VMS 2.0
	ud				      VMS-ISODE
	VTT X.500
	Xds				 X Window System
	xdua
	XT-DUA				      QUIPU
					      SD
					      WIN/DS
					      X.500 DUA	process
					      Xdi
					      Xds
					      xdua
					      XT-DUA
					      xwp [PSI]
					      xwp [UWisc]










DISI Working Group				               [Page 11]

RFC 1292		     X.500 Catalog		    January 1992


   X.25

	DCE/GDS
	Directory 500
	DISH-VMS 2.0
	HP X.500 DDS
	OSI Access and Directory
	OSI-DSA
	OSI-DUA
	QUIPU
	*UCOM X.500
	VTT X.500
	WIN/DS
	X.500 DUA process
	Xdi
	XT-DUA



































DISI Working Group				               [Page 12]

RFC 1292		     X.500 Catalog		    January 1992


3.  Implementation Descriptions

   In the following pages you will find	descriptions of	X.500 implemen-
   tations listed in alphabetical order.  In the case of name colli-
   sions, the name of the responsible organization, in square brackets,
   has been used to distinguish	the implementations.  Note that
   throughout this section, the	page header reflects the name of the
   implementation, not the date	of the document.  The descriptions fol-
   low a common	format,	as described below:

   NAME
	The name of the	X.500 implementation and the name of the respon-
	sible organization.  Implementations with a registered trademark
	indicate this by appending "(tm)", e.g., GeeWhiz(tm).

   LAST	MODIFIED
	The month and year within which	this implementation description
	was last modified.

   KEYWORDS
	A list of the keywords defined in Section 2 that have been used
	to cross reference this	implementation.

   ABSTRACT
	A brief	description of the application.	 This section may
	optionally contain a list of the pilot projects	in which the
	application is being used.

   COMPLETENESS
	A statement of compliance with respect to the 1988 CCITT Recom-
	mendations X.500-X.521 [CCITT-88], specifically	Section	9 of
	X.519, or the 1988 NIST	OIW Stable Implementation Agreements
	[NIST-88].

   INTEROPERABILITY
	A list of other	DUAs and DSAs with which this implementation can
	interoperate.

   PILOT CONNECTIVITY
	Describes 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.

   BUGS
	A warning on known problems and/or instructions	on how to report
	bugs.



DISI Working Group				               [Page 13]

RFC 1292		     X.500 Catalog		    January 1992


   CAVEATS AND GENERAL LIMITATIONS
	A warning about	possible side effects or shortcomings, e.g., 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.

   HARDWARE PLATFORMS
	A list of hardware platforms on	which this application runs, any
	additional boards or processors	required, and any special sug-
	gested or required configuration options.

   SOFTWARE PLATFORMS
	A list of operating systems, window systems, databases,	or
	unbundled software packages required to	run this application.

   AVAILABILITY
	A statement regarding the availability of the software (free or
	commercially available), a description of how to obtain	the
	software, and (optionally) a statement regarding distribution
	conditions and restrictions.





























DISI Working Group				               [Page 14]

RFC 1292		   Alliance OSI	X.500		    January 1992


NAME

   Alliance OSI(tm) X.500
   Touch Communications	Inc.

LAST MODIFIED

   July, 1991

KEYWORDS

   API,	Commercially Available,	DSA/DUA, HP, IBM (Non-PC and RISC),
   MIPS, Macintosh, Multiple Vendor Platforms, OSI Transport, RFC-1006,
   Sun

ABSTRACT

   Alliance OSI	includes XDS (API), DUA, DSA and DIB all as separate
   components.

   Touch's X.500 products have been designed for complete portability to
   any operating system	or hardware environment.  The protocols	include
   DAP and DSP of the OSI X.500	specification along with the required
   XDS,	DUA, DSA and DIB components.  In addition to X.500, Touch sup-
   plies other OSI protocol layers including: ROSE, ACSE, Presentation,
   Session and any of the OSI lower layers (Transport, Network along
   with	RFC-1006).  Touch also supplies	other application layer	proto-
   cols	such as	X.400, FTAM, CMIP (and general network management), etc.

   The Alliance	OSI X.500 is compliant with the	CCITT X.500 1988 Recom-
   mendations. The ROSE/ACSE/Presentation/Session stack	can be option-
   ally	provided by Touch.

   The DUA may represent a single user,	or may represent a group of
   users.  It may be attached to a given DSA within the	same system but
   is also capable of invoking operations in Touch's or	any other
   vendor's compliant DSA on a remote system.  The binding operation
   requires the	user to	give a distinguished name and password in order
   for the Directory to	identify the user.  Once an association	is esta-
   blished the user may	invoke the following operations: READ, COMPARE,
   ABANDON, LIST, SEARCH, ADD_ENTRY, REMOVE_ENTRY, MODIFY_ENTRY,
   MODIFY_RDN.









DISI Working Group				               [Page 15]

RFC 1292		   Alliance OSI	X.500		    January 1992


   Due to the fact that	access to the physical disk is in most	cases  a
   blocking  operation	(synchronous)  Touch  has separated the	database
   processing (I/O process) from the DSA protocol entity.  This	 separa-
   tion	allows the DSA entity to continue processing during the	frequent
   database accesses from the DSA. The DSA supports  all  the  Directory
   operations  as specified in the CCITT X.500 specification.  Chaining,
   Referral and	Multicasting are provided and supported	in the	Alliance
   OSI	DSA.   The DSA supports	all the	service	control	options	included
   in the operation command arguments.	Filtering  conditions  are  sup-
   ported via the FILTER in the	SEARCH operation.

   The Alliance	OSI X.500 product supports all the NIST	defined	manda-
   tory	X.500 and X.400	object classes and attributes.

   Alliance OSI	X.500 supports all the mandatory Directory attribute
   types (and their associated abstract	syntaxes) in the NIST Directory
   implementation profile. Touch has extended the Directory and	allows
   users to define private attributes.	This means that	a user can util-
   ize the Alliance OSI	Directory for a	general	purpose, user defined
   database activity.

   Touch provides a full set of	administration and Directory management
   facilities.

   Touch is in the process of integrating the X.500 product with the
   Worldtalk 400 product. Worldtalk 400	is Touch's end user X.400 mes-
   sage	switch,	providing gateways between proprietary mail systems
   (SMTP, Microsoft Mail, MHS, cc:mail,	etc.) and X.400.  X.500	is a key
   component for a messaging network.

COMPLETENESS

   Strong Authentication is not	supported however Simple Authentication
   is supported.

INTEROPERABILITY

   No interoperability testing has been	completed as of	yet.

PILOT CONNECTIVITY

   Numerous OEMs are using the Alliance	OSI X.500 product in product
   development as well as in pilot networks.

BUGS

   N/A




DISI Working Group				               [Page 16]

RFC 1292		   Alliance OSI	X.500		    January 1992


CAVEATS	AND GENERAL LIMITATIONS

   Currently the Alliance OSI X.500 DIB	has only been validated	within a
   UNIX	File System.  The protocol components are portable as is the
   interface between the DSA and the DIB.

INTERNETWORKING	ENVIRONMENT

   Alliance OSI	X.500 can be utilized over TCP/IP and/or OSI Transport
   on LANs and WANs.  Currently	X.500 has only been verified over OSI,
   however other Alliance OSI application layers have been configured
   over	a RFC-1006 which is available as part of the Alliance OSI pro-
   duct	line.

HARDWARE PLATFORMS

   Alliance OSI	has been ported	to numerous platforms ranging from IBM
   Mainframes MVS to Apple Macintosh.  For UNIX	environments Touch has
   portations for 386 AT/Bus, SUN-3 and	4, Mips, and HP.

SOFTWARE PLATFORMS

   As stated above, the	Alliance OSI product have been ported to
   numerous systems.  In the UNIX environment the X.500	product	exists
   on SUN OS 4.0 and greater, Mips RISC	OS, Interactive	386 and	HP-UX.

AVAILABILITY

   Alliance OSI	is commercially	available from:

	   Touch Communications	Inc.
	   250 E. Hacienda Ave
	   Campbell, CA	95008
	   Sales and Information: [phone]
	   FAX:	[phone]
















DISI Working Group				               [Page 17]

RFC 1292		  Cray OSI Version 2.0		    January 1992


NAME

   Cray	OSI Version 2.0
   Cray	Research Inc.

LAST MODIFIED

   July, 1991

KEYWORDS

   CLNP, Commercially Available, Cray, DSA/DUA,	OSI Transport, RFC-1006

ABSTRACT

   The product is packaged with	the Cray OSI product. It includes a DSA
   and DUA capable of OSI or TCP/IP connections.  The implementation is
   based on the	ISODE QUIPU product.

COMPLETENESS

   Compliance with CCITT88 plus	access control extensions.  Strong
   authentication not yet implemented.

INTEROPERABILITY

   Interoperates with ISODE QUIPU based	implementations.

PILOT CONNECTIVITY

   The software	has been operated in conjunction with the White	Pages
   Pilot Project.

BUGS

   [No information provided--Ed.]

CAVEATS	AND GENERAL LIMITATIONS

   See ISODE QUIPU limitations.

INTERNETWORKING	ENVIRONMENT

   TCP/IP, TP4







DISI Working Group				               [Page 18]

RFC 1292		  Cray OSI Version 2.0		    January 1992


HARDWARE PLATFORMS

   Runs	on UNICOS based	Cray machines with OS level 7.0	or greater.

SOFTWARE PLATFORMS

   Supported for CRAY UNICOS 7.0 or greater.

AVAILABILITY

   Commercially	available via Cray Research Inc. Sales Representatives.








































DISI Working Group				               [Page 19]

RFC 1292			 Custos			    January 1992


NAME

   Custos
   National Institute of Standards and Technology

LAST MODIFIED

   November, 1991

KEYWORDS

   API,	DSA/DUA, Free, Limited Functionality, Multiple Vendor Platforms,
   Requires ISODE, OSI Transport, RFC-1006, Sun, UNIX

ABSTRACT

   The implementation consists of a set	DUA library routines, a	terminal
   interface, and a DSA. The implementation was	developed in C on Sun 3
   workstations	under the UNIX operating system. All underlying	services
   are provided	by the ISODE development package. The development pack-
   age is also used for	encoding and decoding ASN.1 data as well as for
   other data manipulation services. Using the ISODE package the imple-
   mentation can be run	over both OSI and TCP/IP protocols.

   The DSA provides full support for both DAP and DSP protocols, confor-
   mant	with ISO 9594/CCITT X.500 standards. The DIB is	maintained using
   a locally developed relational database system. The interface to the
   database system consists of a set of	SQL-like C functions.  These are