rfc1632.txt

中、英文RFC文档大全打包下载完全版 .

   Protocol (DAP).

   The DSA will	negotiate with other, remote DSAs to obtain requested
   information or to update remote DIBs. DSAs use the Directory	System
   Protocol (DSP) to forward and answer	these requests.	The DSA	supports
   chaining and	referrals.

COMPLIANCE (applicable only for	DSAs and DUAs)

   All X.500 1988 operations are supported along with all Object Classes
   specified in	X.521 and all Attribute	Types specified	in X.520.

   Implementation plans	include	upgrades to support the	1992 extensions
   to X.500 in 1994. Please check with OSIware / Infonet Software
   Solutions for availability dates.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [No information provided--Ed.]

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL	RFCs

   [No information provided--Ed.]






IDS Working Group				               [Page 39]

RFC 1632		     X.500 Catalog		   Directory 500


INTEROPERABILITY

   Tested with QUIPU. Other interoperability information not available
   at this time.

PILOT CONNECTIVITY

   [No information provided--Ed.]

BUGS

   None	known at this time.

CAVEATS	and GENERAL LIMITATIONS

   None	known at this time.

INTERNETWORKING	ENVIRONMENT

   RFC1006 with	TCP/IP

HARDWARE PLATFORMS

   Any Sun SPARC with 16 MB memory, 40 MB free disk Please enquire if
   interested in other platforms such as: SCO Unix, AIX

SOFTWARE PLATFORMS

   Sun OS 4.1.x. Runs over TCP/IP, or X.25 (SunNet X.25	Version	7
   required)

AVAILABILITY

   Directory 500 is commercially as executable object code or as source
   code	form from:
	 OSIware / Infonet Software Solutions
	 4400 Dominion Street, Suite 210
	 Burnaby, BC  V5G 4G3
	 CANADA

	 Sales & Information: 604436-2922
	 Fax:  [phone]

DATE LAST UPDATED or CHECKED

   November 21st, 1993





IDS Working Group				               [Page 40]

RFC 1632		     X.500 Catalog			  DOS-DE


NAME

   DOS-DE
   University of Bath


KEYWORDS

   Available via FTP, DUA Interface, Free, IBM PC, LDAP, Multiple Vendor
   Platforms, RFC-1274,	RFC-1484, RFC-1487

ABSTRACT

   DOS-DE (DOS Directory Enquiries) is intended	to be a	simple-to-use
   DUA interface suitable for the naive	user.  It is an	MS-DOS port of
   the standard	UNIX DE	implementation - see the entry on DE for full
   details.  (All of the features DE are supported apart from the
   experimental	`Quality of Service' code).

   The user is presented with a	series of (verbose) prompts asking for
   person's name; department; organization; country.  There is extensive
   on-line help.  The matching algorithms are such that	near matches are
   presented to	the user before	less good matches.  `Power searching' is
   also	available - this allows	a user to search for an	entry even when
   they	do not know the	name of	the organisation in which the person
   works - you still have to specify the country.  DOS-DE provides UFN
   style searching.  It	is also	possible to search locality entries.
   DOS-DE uses slightly	different search algorithms depending on whether
   it is accessing part	of the Directory mastered by a Quipu DSA - Quipu
   DSAs	tend to	use lots of replication	and so encourage searching.

   DOS-DE runs over the	University of Michigan LDAP.

   DE was funded by the	COSINE PARADISE	project.  DOS-DE was developed
   by Andy Powell at the University of Bath.

COMPLIANCE (applicable only for	DSAs and DUAs)

   N/A

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [RFC	1274] and [RFC 1487]

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL	RFCs

   [RFC	1484].




IDS Working Group				               [Page 41]

RFC 1632		     X.500 Catalog			  DOS-DE


INTEROPERABILITY

   N/A

PILOT CONNECTIVITY

   N/A

BUGS

   Doesn't handle aliases well when power searching.

   Send	bug reports to:

	      [e-mail]

CAVEATS	and GENERAL LIMITATIONS

   DOS-DE tries	to cater well for the general case, at the expense of
   not dealing with the	less typical.  The main	manifestation of this is
   that	the current version does not handle searching under localities
   very	well.

   It is not possible to display photographs or	reproduce sound
   attributes.

INTERNETWORKING	ENVIRONMENT

   University of Michigan LDAP.

HARDWARE PLATFORMS

   IBM PC/AT/XT	and compatibles.

SOFTWARE PLATFORMS

   LDAP	for MS-DOS running over	the NCSA Telnet	stack or SUN's PCNFS
   version 4.1 or Novell's LAN Workplace (LWP).

AVAILABILITY

   The software	is openly available by FTP from	ftp.bath.ac.uk,	as
   pub/x500/dosde.zip.

   The very latest code	will be	made available with the	ISODE Consortium
   release of ISODE.  It is hoped it will be freely available to all.

   Contact:



IDS Working Group				               [Page 42]

RFC 1632		     X.500 Catalog			  DOS-DE


	      [e-mail]

DATE LAST UPDATED or CHECKED

   March 18th, 1993














































IDS Working Group				               [Page 43]

RFC 1632		     X.500 Catalog  HP X.500 Dist. Dir.	Products


NAME

   HP X.500 Distributed	Directory Products
   Hewlett Packard


KEYWORDS

   API,	CLNS, Commercially Available, DSA/DUA, DUA only, HP, OSI
   Transport, X.25

ABSTRACT

   HP X.500 Distributed	Directory. Its main components are:

       DUA, and	DUA Interface,
       DSA and DIB support,
       X.500 Address Lookup,
       X/Open Application Tool Kit API (XAT) for XDS/XOM Interface,
       X.500 High Level	API (X5HLAPI) for XDS/XOM Interface.

   HP X.500 DUA. Its main components are:

       DUA, and	DUA Interface,
       X.500 Address Look-up,
       X/Open Application Tool Kit API (XAT) for XDS/XOM Interface,
       X.500 High Level	API (X5HLAPI) for XDS/XOM Interface.

   HP X.500 Distributed	Directory is based on the 1988 CCITT X.500
   standard.  HP X.500 can be used for accessing names and electronic
   mail	addresses for multi-vendor messaging backbone networks.	HP X.500
   can also be used for	the development	of networked applications
   requiring distributed directory functionality.

   HP OpenMail users can access	the enterprise wide HP X.500 distributed
   directory directly from the HP OpenMail user	interface, and select
   X.500 addresses for mailing.	HP-UX Sendmail users can access
   electronic mail addresses from a X.500 server over a	TCP/IP network.

   Users of non-HP e-mail systems can access data stored in the	X.500
   Directory using X.500 Address Look-up. X.500	Address	Look-up	has an
   easy	to use interface, and phonetic search capability.

   HP X.500 Distributed	Directory includes a complete multi-threaded DUA
   and DSA. The	X.500 DIB is built on a	database which has been
   optimized for X.500 performance. HP X.500 contains full support for
   DAP and DSP protocols.




IDS Working Group				               [Page 44]

RFC 1632		     X.500 Catalog  HP X.500 Dist. Dir.	Products


   Data	Shadowing and security access control of HP X.500 Distributed
   Directory allow higher performance, and easier management of	its DIB
   database in a global	environment.

   HP X.500 Distributed	Directory has menu driven administration and
   user	interface tools. The tools simplify directory configuration and
   data	retrieval. It supports X/Open X.500 APIs (XDS and XOM),	and high
   level APIs on top of	XDS to allow developers	to write their own X.500
   based applications.

   HP X.500 Distributed	Directory supports comprehensive tracing and
   logging facilities for quick	diagnosis and resolution of problems. HP
   also	provides a rich	set of troubleshooting tools to	check the
   interoperability of the network at various layers of	the OSI	stack.

COMPLIANCE (applicable only for	DSAs and DUAs)

   HP X.500 Distributed	Directory complies with	the following standards:

     CCITT X.501:  The Directory - Models
     CCITT X.509:  The Directory - Authentications Framework*
     CCITT X.511:  The Directory - Abstract Service Definition
     CCITT X.518:  The Directory - Procedures for Distributed Operations
     CCITT X.519:  The Directory - Protocol Specifications
     CCITT X.520:  The Directory - Selected Attribute Types
     CCITT X.521:  The Directory - Selected Object Classes
     CCITT X.219:  Remote Operations - Model, Notation and Service
   Definition
     CCITT X.229:  Remote Operations - Protocol	Specifications

     *x.509 describes simple and strong	authentication.	HP X.500
      Distributed Directory supports simple authentication. Strong
      authentication is	not supported in the current release due to
      limited market demand.

   HP X.500 Distributed	Directory will comply with NIST	and EWOS
   directory functional	profiles. Based	on factors such	as market needs
   and NIST recommendations, HP	will implement subsets of 1992 CCITT
   functionality in a phased approach.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [No information provided--Ed.]

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL	RFCs

   [No information provided--Ed.]




IDS Working Group				               [Page 45]

RFC 1632		     X.500 Catalog  HP X.500 Dist. Dir.	Products


INTEROPERABILITY

   HP has done some unofficial interoperability	testing. HP would
   welcome suggestions on priorities for vendor	interoperability
   testing.

PILOT CONNECTIVITY

   [No information provided--Ed.]

BUGS

   [No information provided--Ed.]

LIMITATIONS

   HP X.500 Distributed	Directory supports up to 30 DSA	connections at
   one time. This limit	could be increased in the future if needed.

INTERNETWORKING	ENVIRONMENT

   HP X.500 Distributed	Directory resides on an	OSI stack, and can be
   used	in 802.3 LAN, or X.25 CLNS or CONS environment.	HP is
   investigating implementing X.500 for	the TCP/IP environment.

HARDWARE PLATFORMS

   HP X.500 Distributed	Directory is available on HP 9000 Series 800
   family of high performance servers which are	scalable platform.

   The HP X.500	Address	Look-up	facility is also available for the HP
   9000	Series 300 and Series 700 for customers	who have purchased the
   X.500 product.

SOFTWARE PLATFORMS

   HP X.500 Distributed	Directory requires the following software
   environment:

   - HP-UX Operating System 8.0	or later
   - OSI Transport Services/9000 for the Series	800
   - HP	Lan Link or HP X.25 product
   - Network Tracing and Logging
   - ANSI C compiler (for the HP/XDS API)







IDS Working Group				               [Page 46]

RFC 1632		     X.500 Catalog  HP X.500 Dist. Dir.	Products


AVAILABILITY

   HP X.500 Distributed	Directory is commercial	available. The product
   can be ordered through HP Sales offices. The	ordering numbers are:

       P/N J2152A
       HP X.500	Distributed Directory/9000 for the Series 800.
       Product contains	DSA server and DUA client.

       P/N J2153A
       HP X.500	DUA/9000 for the Series	800.
       Product contains	only DUA client.

DATE LAST UPDATED or CHECKED

   August 16th,	1993.



































IDS Working Group				               [Page 47]

RFC 1632		     X.500 Catalog    Univ. of Mich. LDAP Imple.


NAME


   University of Michigan LDAP Implementation


KEYWORDS

   API,	Available via FTP, DEC ULTRIX, DUA Connectivity, DUA Interface,
   Free, HP, IBM PC, IBM RISC, LDAP, Macintosh,	Multiple Vendor
   Platforms, RFC-1006,	RFC-1274, RFC-1484, RFC-1485, RFC-1487,	Source,
   Sun

ABSTRACT

   LDAP	is the Lightweight Directory Access Protocol.  It gives	X.500
   access to platforms that have only TCP/IP access, using simplified
   BER encoding	of many	X.500 data elements.  LDAP is currently	a
   proposed Internet Standard.	The LDAP server	is an intermediate
   protocol server that	communicates with Internet clients on one side
   using the simple TCP-based LDAP protocol and	an X.500 DSA on	the
   other side using the	Directory Access Protocol (DAP).  A subset of
   the X.500 DAP is exported to	the clients through the	LDAP protocol.

   The U-M LDAP	distribution contains the following components:

   - LDAP server
   - LDAP client library, including both synchronous and asynchronous APIs
   - Lightweight BER library, including	an API that supports
     a printf/scanf-like interface
   - Various LDAP client programs, including a finger daemon (xfingerd),
     gopher to X.500 gateway (go500gw),	command-line DUA (ud), e-mail
     query server (rcpt500), and an X.500 mailer (mail500)


COMPLIANCE (applicable only for	DSAs and DUAs)

   The U-M LDAP	distribution is	a complete implementation of the LDAP
   protocol.  The LDAP protocol	does not support access	to all X.500
   features and	operations.  The operations supported are bind,	search,
   compare, add, delete, modify, modify	RDN, and abandon.  Note	that
   read	and list operations can	be emulated using the search operation.
   Size	and time limits	may be specified, as may alias dereferencing and
   searching, but all X.500 service controls are not supported.







IDS Working Group				               [Page 48]

RFC 1632		     X.500 Catalog    Univ. of Mich. LDAP Imple.


CONFORMANC