rfc1292.txt

RFC 的详细文档！

   VMS/ULTRIX Connection 1.2

AVAILABILITY

   Executables can be freely distributed for non-commercial use.
   Transfer mode binary.
   FTP user anonymous sun.iris-dcp.es (130.206.1.2)
   FTAM, user anon
   TSEL= <0103>H
   INT-X25= 21452160234012
   IXI=	2043145100102
   ISO-CLNS= 39724F1001000000010001000113020600100200 (COSINE P4.1)
   File: /isodevms/dishVMS2.BCK.Z compress SAVE_SET file (1.6 Mbytes)
   File: /isodevms/lzdcm.exe to	uncompress the file




















DISI Working Group				               [Page 30]

RFC 1292			 DIXIE			    January 1992


NAME

   DIXIE
   University of Michigan

LAST MODIFIED

   November, 1991

KEYWORDS

   Available via FTP, DUA Light	Weight Client, Free, Source, UNIX, Mul-
   tiple Vendor	Platform, Needs	ISODE

ABSTRACT

   The DIXIE protocol is used to give X.500 access to platforms	that
   have	only TCP/IP access.  The DIXIE server is an intermediate proto-
   col server that communicates	with Internet clients on one side using
   a text-based	UDP/TCP	protocol and an	X.500 DSA on the other side
   using DAP.  The protocol is fully described in RFC 1246.  A subset of
   the X.500 DAP is exported to	the clients through the	DIXIE protocol.
   There is a DIXIE API	provided in the	form of	a library of C-callable
   routines.

   The DIXIE protocol and server are being used	by the following
   products/projects:

     UD, a simple command line white pages DUA for Unix	machines (dis-
     tributed with the DIXIE server)

     maX.500, a	white pages DUA	for the	Macintosh (available from the
     same place	as the DIXIE server)

     Network monitoring	of DSAs	by our Network Operations Center

     Lookup and	display	of caller identification based on telephone
     caller ID (using ISDN).

COMPLETENESS

   The DIXIE protocol does not support access to all X.500 features and
   operations.	All DAP	operations except Abandon are supported.  Gen-
   eral	searches (including multiple component searches) are supported.
   The DIXIE protocol supports none and	simple authentication.	A subset
   of the service controls are supported.





DISI Working Group				               [Page 31]

RFC 1292			 DIXIE			    January 1992


INTEROPERABILITY

   The current implementation of the DIXIE server works	with the QUIPU
   DSA and DAP library.

PILOT CONNECTIVITY

   The DIXIE server has	been tested in the Internet and	PARADISE pilots.
   It provides full DUA	Connectivity subject to	the limitations	dis-
   cussed above	under completeness.

BUGS

   There are no	known outstanding bugs.	 But reports should be sent to
   [e-mail].

CAVEATS	AND GENERAL LIMITATIONS

   None, aside from those mentioned above under	completeness.

INTERNETWORKING	ENVIRONMENT

   DIXIE clients use TCP or UDP	to communicate with the	DIXIE server.
   The DIXIE server uses RFC-1006 with TCP/IP to communicate with the
   DSA,	though other transport mechanisms for DSA communication	should
   be possible.

HARDWARE PLATFORMS

   The DIXIE server is known to	run on Sun 3, Sun 4, and DEC 3100 plat-
   forms.  It should run on any	UNIX platform.	The DIXIE library is
   known to run	on the same platforms, and also	on the Macintosh.

SOFTWARE PLATFORMS

   The DIXIE server and	library	is known to run	under SunOS 3.5, SunOS
   4.1.1, Ultrix 4.1 and 4.2.  The DIXIE library also runs on the Macin-
   tosh	System Software	6 or later.

AVAILABILITY

   This	software is openly available.  It may be obtained by anonymous
   FTP from terminator.cc.umich.edu in the directory ~ftp/x500.	Documen-
   tation on the DIXIE protocol	is provided along with the source code,
   which includes source for the DIXIE server, DIXIE library, and the UD
   client.





DISI Working Group				               [Page 32]

RFC 1292			 DIXIE			    January 1992


   This	software was developed at the University of  Michigan  by  Bryan
   Beecher,  Tim  Howes, and Mark Smith	of the ITD Research Systems Unix
   Group.  It is subject to the	following copyright.

   Copyright (c) 1991 Regents of the University	of Michigan. All rights
   reserved.  Redistribution and use in	source and binary forms	are per-
   mitted provided that	this notice is preserved and that due credit is
   given to the	University of Michigan at Ann Arbor. The name of the
   University may not be used to endorse or promote products derived
   from	this software without specific prior written permission. This
   software is provided	"as is"	without	express	or implied warranty.








































DISI Working Group				               [Page 33]

RFC 1292		     DS-520, DS-521		    January 1992


NAME

   DS-520
   DS-521
   Retix

LAST MODIFIED

   November, 1991

KEYWORDS

   API,	Commercially Available,	DSA/DUA, DUA Connectivity, DSA Connec-
   tivity,  Multiple Vendor Platforms, OSI Transport, RFC-1006,	Source,
   UNIX

ABSTRACT

   DS-520 X.500	Distributed Directory Services for UNIX	System V and
   DS-521 X.500	Directory User Agent (DUA) for UNIX System V form an
   integral part of the	Retix OSI Networking Products family.  Designed
   for systems vendors,	public carriers, and other OEMs, DS-520	is a
   complete high-performance implementation of X.500 in	source code
   form, including a DUA, DSA Manager (DSAM), and DSA.	DS-521
   represents a	subset of this product offering. It provides the DUA
   portal into the directory, which, for example, meets	the needs of
   software vendors who	plan to	provide	application packages with X.500
   Directory interaction capabilities. Within these two	offerings, the
   DUA possesses two forms of interface. The first form, the DUA with
   User	Interface, provides an interactive character-based user	inter-
   face	for users of Directory services.  The user agent provides access
   to the Directory via	basic Directory	service	requests. The second
   form, the DUA with Programmatic Interface provides a	standardized
   programmatic	interface to application programs that must access
   Directory information. The interface	is conformant to the X/Open
   Object Management (XOM) and X/Open Directory	Services (XDS) stan-
   dards. This component provides all functionality related to Directory
   access and general OSI services down	to the session layer. The DSAM
   provides an interactive character oriented user interface to	a Direc-
   tory	administrator.	The DSAM provides management functions either
   local to or remote from a DSA. Both the DUA and the DSAM are	useful
   in the training, management,	and manipulation of Directory entries
   maintaining operational and user attribute information. The DSA main-
   tains Directory database information	and provides users the ability
   to read/compare, modify, search, and	manage entries within the data-
   base. It maintains all or fragments of the Directory	Information Base
   (DIB) and provides abstract service ports for DUAs and DSAs over DAP
   and DSP protocols respectively.



DISI Working Group				               [Page 34]

RFC 1292		     DS-520, DS-521		    January 1992


COMPLETENESS

   DS-520 represents a complete	implementation of the 1988 X.500 Recom-
   mendations with the exception of strong authentication as outlined in
   X.509. It is	conformant to NIST, EWOS, and UK GOSIP Directory pro-
   files. It provides session through application layer	protocol support
   and hence incorporates ROSE,	ACSE, Presentation, and	Session	within
   its product stack. In addition to including all the attribute types,
   syntaxes, and object	classes	defined	in X.520 and X.521, the	DS-520
   includes support for	those specified	in the 1988 X.400 Recommendation
   X.402, Annex	A. Remote on-line management of	the DSA	is supported by
   means of Network Management Forum CMIP.

   DS-521 represents a complete	implementation of the X/Open Object
   Management (OM) and X/Open Directory	Services (XDS) standards. It
   also	incorporates session through application layer protocol	support
   and thus includes ROSE, ACSE, Presentation, and Session within its
   product stack.

INTEROPERABILITY

   The DS-520 has been tested to interoperate with Banyan (DAP), CDC
   (DSP), IBM, ICL, OSIWare, Nixdorff, Unisys (DSP), Wollongong	(DAP),
   and 3-Com (DSP).

   The DS-521 subset has undergone no separate interoperability	testing.

PILOT CONNECTIVITY

   DSA Connectivity provided by	the DS-520: The	DSA provides complete
   support for the X.511 Abstract Service Definition, the directoryAc-
   cessAC and the directorySystemAC defined in the X.519 Protocol
   Specifications, and the Distributed Directory defined in the	X.518
   Procedures for the Distributed Directory. It	supports all the object
   classes, attribute types, and attribute syntaxes defined in X.520 and
   X.521. It does not support the Internet DSP however.

   DUA Connectivity provided by	both the DS-520	and DS-521: The	DUA pro-
   vides complete support for the X.511	Abstract Service Definition and
   the directoryAccessAC defined in the	X.519 Protocol Specifications.
   The DUA with	User Interface supports	only a subset of the X.500
   attributes and object classes defined in X.520 and X.521. The DUA
   with	Programmatic Interface,	however, does support all the object
   classes, attribute types, and attribute syntaxes defined in these two
   recommendations.






DISI Working Group				               [Page 35]

RFC 1292		     DS-520, DS-521		    January 1992


BUGS

   Product Action Requests (PARs) stemming externally from customers and
   internally from customer service and	quality	assurance engineers are
   generated and published in the form of weekly reports. A description
   and status of these PARs are	provided to customers possessing
   software maintenance	agreements.

CAVEATS	AND GENERAL LIMITATIONS

   DS-520 and DS-521 are source	code products ported to	UNIX System V
   Release 3 and 4. Makefiles to generate the system are provided for
   the AT&T System V, SCO, and Interactive UNIX	systems.

INTERNETWORKING	ENVIRONMENT

   DS-520 and DS-521 offer two main compile time configuration options
   and hence internetworking configurations. In	the first of these, they
   interface to	the UNIX System	V Transport Library Interface (TLI).
   The TLI provides a path between the session layer of	a UNIX OSI
   application process and an OSI transport provider installed in the
   UNIX	kernel.	The latter transport provider may take the form	of a
   Retix Unix LAN (LT-610) or WAN (WT-325) transport product. The second
   main	option utilizes	the UNIX System	V ACSE/Presentation Library
   interface (APLI and the A/P Library), which provides	OSI ACSE and
   Presentation	layer services.	The Retix AP-240 Presentation syntax
   manager product serves to map the standard Retix Presentation layer
   interface to	the AT&T APLI. The APLI	upper layers services may be
   provided by the Retix UL-220	product. UL-220	is the Retix implementa-
   tion	of the AT&T Open Networking Platform Upper Layer Services module
   and includes	the A/P	library, as well as the	OSI ACSE, Presentation,
   and Session services.

   DS-520 and DS-521 may also run on top of the	TCP/IP stack by	means of
   the Retix MP-120 product. MP-120 is a STREAMS based driver that
   implements RFC-1006 and thus	allows OSI applications	to run over a
   network based on the	Internet suite of protocols (TCP/IP). Its main
   function provides a conversion between the TCP stream to the	data
   packets required by OSI Transport Class 0 protocol and vice versa. As
   part	of this	process, it converts TCP/IP 32-bit addresses to	hex
   values for use with OSI applications.










DISI Working Group				               [Page 36]

RFC 1292		     DS-520, DS-521		    January 1992


HARDWARE PLATFORMS

   Being source	code products ported to	the UNIX System	V Release 3  and
   4  operating	system environment, DS-520 and DS-521 are hardware plat-
   form	independent. They currently both have sample portations	and test
   configurations on various Intel 80386 platforms running Unix	System V
   Release 3 and 4.

SOFTWARE PLATFORMS

   Currently, DS-520 and DS-521	include	reference implementations for
   the AT&T System V Release 4,	SCO UNIX System	V/386 Version 3.2.2, and
   the Interactive UNIX	System V/386 Version 2.2 operating systems.
   Raima Corporation's db_Vista	III Version 3.1	serves as the database
   engine for the Directory product.

AVAILABILITY

   DS-520 and DS-521 are commercially available	from:

	   Retix
	   2401	Colorado Avenue
	   Santa Monica, California
	   90404-3563 USA

	   Sales and Information:  310-828-3400
	   FAX:			   [phone]
























DISI Working Group				               [Page 37]

RFC 1292			 HP DDS			    January 1992


NAME

   HP X.500 Distributed	Directory Software
   Hewlett Packard

LAST MODIFIED

   July, 1991

KEYWORDS

   API,	CLNP, Commercially Available, DSA/DUA, HP, X.25

ABSTRACT

   HP's	Distributed Directory Software is a fully distributed Directory
   that	supports both the DAP and DSP protocols, which were specified in
   the 1988 CCITT/ISO X.500 documents.	Besides	implementing the stan-
   dard, we have also put in proprietary access	control	and replication.
   These additional features will be migrated to the standard definition
   at the time that they are stable.  Users are	able to	define their own
   attributes, objects classes and DIT structure rules.

   In order to make this software easy to use a	set of menu driven
   screens have	been provided.	There are easy to use data access and
   data	management screens.  For system	administrators,	these is also a
   set for screens that	are used to help configure the servers and
   manage the schema. Startup and Shutdown utilities are also included.

   For application developers an X/Open-APIA XDS API is	provided, along
   with	some helper routines that help reduce development time.	 The XDS
   API includes	the following functions:

	   Bind
	   Read
	   Search
	   Add
	   Remove
	   Unbind
	   Version

   A subset of the X/Open-APIA Object Management (XOM) functions are
   available thru the interface.  The subset are those that are	neces-
   sary	to perform the directory operations.

   For bulk operations a batch interface is also available.





DISI Working Group				               [Page 38]

RFC 1292			 HP DDS			    January 1992


COMPLETENESS

   This	software implements the	1988 X.500 CCITT/ISO Standard.	It fully
   supports DAP	and DSP, minus strong authentication.  By default it
   contains all	of the X.520 Attributes	and the	X.521 Syntaxes and
   Object Classes.  Additionally, the Annex B DIT Structure can	be
   enforced.

INTEROPERABILITY

   Interoperability testing will be undertaken as new X.500 products are
   introduced into the market.

PILOT CONNECTIVITY

   [No information provided--Ed.]

BUGS

   No major ones at this time.

CAVEATS	AND GENERAL LIMITATIONS

   This	is pilot software for organizations who	wish to	learn about HP's
   X.500 offering.

INTERNETWORKING	ENVIRONMENT

   TP0 or TP4 on 802.3 or X.25

HARDWARE PLATFORMS

   HP-9000 800	   Minicomputer
   HP-9000 300	   Workstation
		   with	at least 8 M of	internal memory
		   with	9 M of available disk space for	the software

SOFTWARE PLATFORMS

   Distributed and Supported for HP-UX version 7.0.

AVAILABILITY

   Limited Commercial Availability.

   For more information	in the U.S. call 1-800-752-0900.  Outside of the
   U.S.	please contact your local HP Sales Office.




DISI Working Group				               [Page 39]

RFC 1292		  INTERACTIVE Systems		    January 1992


NAME

   INTERACTIVE Systems'	X.500 DSA/DSAM
   INTERACTIVE Systems'	X.500 DUA
   INTERACTIVE Systems Corporation