rfc2116.txt

RFC 的详细文档！

        CAXE
        Cycle
        DCX500
        DIR.D
        DXDS
        FORUM
        FX*500
        GDS
        ISODE.r3
        LDAP



Apple & Rossen               Informational                     [Page 28]

RFC 2116            X.500 Implementations Catalog-96          April 1997


        MDSA
        ORG.D
        OSIAM-88
        OSIAM-93
        waX.500

3.  Implementation Descriptions

   In the following pages you will find descriptions of X.500
   implementations listed in alphabetical order.  In the case of name
   collisions, 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
   follow a common format, as described below:

NAME

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

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.

COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs)

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

COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)

   A statement of compliance with respect to the 1993 ITU-T
   Recommendations X.500-X.521 [ITU-T-93], specifically Section 9 of
   X.519, or the 1994 NIST OIW Stable Implementation Agreements [NIST-
   94].

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   A statement of compliance with respect to the several proposed
   Internet Standards.





Apple & Rossen               Informational                     [Page 29]

RFC 2116            X.500 Implementations Catalog-96          April 1997


CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   A statement of compliance with respect to the several informational
   and experimental Internet RFCs.

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.

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 suggested
   or required configuration options.

SOFTWARE PLATFORMS

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

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   A statement regarding the number of implementations deployed in the
   field.




Apple & Rossen               Informational                     [Page 30]

RFC 2116            X.500 Implementations Catalog-96          April 1997


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.

DATE LAST UPDATED or CHECKED

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








































Apple & Rossen               Informational                     [Page 31]

RFC 2116            X.500 Implementations Catalog-96          April 1997


NAME

   A-Window-To-Directory (AWTD)

ABSTRACT

   A-Window-To-Directory is a simple-to-use DUA interface available on
   PC that provides access to the X.500 Directory Services. The
   available operations are: bind (authenticated or anonymous), read,
   list, compare, modify, modifyRDN, search, add, remove and unbind.  It
   is designed to be used with the Bull X500-DUA product and for that
   reason is able to handle any of the defined schema. The new acronyms,
   objects and attributes are automatically loaded without any
   customisation.  The interface of the application may be personalized
   in several ways, through Local Preferences stored on the PC and
   through User Settings stored on the UNIX machine that runs the Bull
   X500-DUA product.

COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs)

   A-Window-To-Directory offers all the services described in the 88
   CCITT X.500 standard.

COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)

   No

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   No

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   No

INTEROPERABILITY

   Is designed to interoperate with Bull X500-DUA and X500-DS products

PILOT CONNECTIVITY

   [No information provided. -- Ed.]

BUGS

   Bull S.A. provides complete software maintenance with the products.





Apple & Rossen               Informational                     [Page 32]

RFC 2116            X.500 Implementations Catalog-96          April 1997


CAVEATS AND GENERAL LIMITATIONS

   [No information provided. -- Ed.]

INTERNETWORKING ENVIRONMENT

   Proprietary protocol to access the Bull X500-DUA through TCP/IP
   sockets.  The product may be used on LAN (Ethernet) or WAN (X.25).

HARDWARE PLATFORMS

   386SX/DX, 486SX/DX PC Ethernet board/connection 4 MBytes RAM 3 Mbytes
   on disk

SOFTWARE PLATFORMS

   MS-DOS 5.0 Microsoft Windows 3.1 Microsoft TCP/IP stack installed,
   version 1.0

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   The product is commercially available since February 1995.

DATE LAST UPDATED or CHECKED

   November 1995

ADDITIONAL INFORMATION and/or COMMENTS

   [No information provided. -- Ed.]

















Apple & Rossen               Informational                     [Page 33]

RFC 2116            X.500 Implementations Catalog-96          April 1997


NAME

   Critical Angle X.500 Enabler

   (CAIx500e)

ABSTRACT

   The X.500 Enabler product allows an LDAP-only directory server to be
   integrated into X.500 environments, by transparently converting X.500
   DAP and DSP requests into LDAP requests.

   The initial release scheduled for 4Q96 will allow for connections
   from X.500-capable clients and servers to an LDAP-capable server, and
   will support the following features:

      * LDAP version 2, as defined in RFC 1777,

      * all attributes defined for LDAPv2, with the exception of
        certificates  and revocation lists,

      * X.500(1988) DAP and DSP protocols over TCP/IP (using  RFC
        1006),

      * the following operations: Bind (with  none or simple
        credentials), Read, Compare, List, Search, Abandon, AddEntry,
        ModifyEntry, RemoveEntry and ModifyRDN,

      * the X.500(1993) critical extensions field, to aid in
        deployments incorporating 1993 DSAs.

   This release will be available for Solaris 2.5 (SPARC and Intel) and
   Windows NT 4.0 Server (Intel).

   The product is expected to enter a public beta test period in
   September 1996.  Beta test evaluation copies will be free (limited to
   two copies per site) but will be set to expire in December 1996.

   Released versions of X.500 Enabler will be licensed per server, and
   will be distributed over the Internet.

COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs)

   The X.500 enabler accepts DAP and DSP connections.

   It supports Bind (with none or simple credentials), Read, Compare,
   List, Search, Abandon, AddEntry, ModifyEntry, RemoveEntry and
   ModifyRDN.



Apple & Rossen               Informational                     [Page 34]

RFC 2116            X.500 Implementations Catalog-96          April 1997


   It supports the attributes and object classes defined in X.520 and
   X.521.

COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)

   The X.500 Enabler will accept connections from X.500(1993) DUAs and
   DSAs.

   It supports the X.511(1993) critical extension mechanism.

   Non-critical protocol fields which do not map onto LDAPv2 are
   ignored.

   Attribute and object classes from X.520(1993) and X.521(1993) are
   supported, including collective.  Operational attributes from X.501
   are supported, with the exception of subschema.

   As LDAPv3-based servers become available, it is expected that the
   X.500 Enabler will be upgraded to map more of the X.500(1993)
   protocol onto LDAPv3.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [RFC 1006] is the supported transport service.

   The product supports the object classes and attributes defined in RFC
   1274.

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [No information provided. -- Ed.]

INTEROPERABILITY

   The X.500 Enabler