Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 2116

X.500 Implementations Catalog-96

Pages: 164
FYI 11
Obsoletes:  1632
Part 2 of 5 – Pages 35 to 69
First   Prev   Next

ToP   noToC   RFC2116 - Page 35   prevText
   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 is being tested with public-domain X.500 and LDAP
   clients and servers, and with the various X.500 clients and servers
   connected to the PARADISE project, such as from the ISODE Consortium.

   Critical Angle intends to do interoperability testing with commercial
   LDAP-only servers as they become available.

PILOT CONNECTIVITY

   This product will be used to connect LDAP-only servers, such as
   University of Michigan's slapd, and many vendor's forthcoming
   commercial LDAP server products, into the PARADISE project directory,
   so that they can be accessed by LDAP and X.500 DUAs throughout the
   project.
ToP   noToC   RFC2116 - Page 36
BUGS

   Bugs reports may be sent to <bug-x500e@critical-angle.com>.

CAVEATS AND GENERAL LIMITATIONS

   X.509 certificates and revocation lists are not supported due to
   limitations in the LDAP version 2 protocol. This restriction will be
   removed once LDAP version 3 servers become generally available.

   Under Windows NT there are limitations on the number of simultaneous
   incoming connections.

INTERNETWORKING ENVIRONMENT

   This product supports RFC 1006 for DAP and DSP, and LDAP over TCP.

HARDWARE PLATFORMS

   This product will initially be available for Sun Solaris 2.5 SPARC
   and Intel, and Windows NT Server 4.0 Intel.

   Subsequent versions may be available on additional platforms.

SOFTWARE PLATFORMS

   An LDAP-based server, such as the freely-available slapd, is
   required.  It does not need to run on the same host as the X.500
   Enabler.

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   This product is licensed per-host server, and is distributed over the
   Internet.

   In addition to discounts for large deployment orders, subscription
   programs permit customers to obtain subsequent update releases at a
   substantial discount.

   Beta test evaluations are free (limited to two copies per site), and
   will expire 90 days after the start of the beta period.
ToP   noToC   RFC2116 - Page 37
DATE LAST UPDATED or CHECKED

   September 1996

ADDITIONAL INFORMATION and/or COMMENTS

   [No information provided. -- Ed.]
ToP   noToC   RFC2116 - Page 38
NAME

   cxdua

   Chromatix, Inc.  10451 Twin Rivers Rd, Suite 265 Columbia, MD 21044

ABSTRACT

   The CXDUA is a Windows 3.1 DUA that has been derrived from a highly
   portable and flexible Unix based Administrative Directory User Agent.
   The goal of the original design was to support features to assist a
   directory administrator in managing the directory.  These features
   include a highly portable GUI, Entry Templates, Entry Lists, Batch
   Operations and Directory Control Functions.

   Both the Windows and the Unix versions support strong authentication.

   The Unix DUA has been used in various DMS and NSA pilot projects.

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

   [No information provided. -- Ed.]

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

   [No information provided. -- Ed.]

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [No information provided. -- Ed.]

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [No information provided. -- Ed.]

INTEROPERABILITY

   [No information provided. -- Ed.]

PILOT CONNECTIVITY

   [No information provided. -- Ed.]

BUGS

   [No information provided. -- Ed.]
ToP   noToC   RFC2116 - Page 39
CAVEATS AND GENERAL LIMITATIONS

   [No information provided. -- Ed.]

INTERNETWORKING ENVIRONMENT

   [No information provided. -- Ed.]

HARDWARE PLATFORMS

   Windows 3.1

SOFTWARE PLATFORMS

   [No information provided. -- Ed.]

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   The software is freely available via anonymous ftp from
   ftp.chromatix.com or can be obtained  via the WEB at
   http://www.chromatix.com.  Commercial versions will be available in
   the near future.

DATE LAST UPDATED or CHECKED

   0496

ADDITIONAL INFORMATION and/or COMMENTS

   [No information provided. -- Ed.]
ToP   noToC   RFC2116 - Page 40
NAME

   Cycle (tm) LiveData (tm) (Cycle)

   Cycle Software,Inc.

ABSTRACT

   A component of the Cycle Virtual Data Highway.

   Network software product used to break down barriers between isolated
   systems.  Available separatly as Cycle LiveNet (DUA) and Cycle
   LiveNet Directory (DUA & DSA)

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

   Cycle LiveData is compliant with the 1988 NIST OIW Stable Agreements
   to the extent that implementations based on the more recent stable
   agreements are compliant.

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

   Cycle LiveData is compliant with the 1993 NIST OIW Stable Agreements.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   Unknown

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   Unknown

INTEROPERABILITY

   Not tested

PILOT CONNECTIVITY

   Not tested

BUGS

   No known bugs

CAVEATS AND GENERAL LIMITATIONS

   Current release supports objects of the Application Entity Object
   Class only. This limitation is being relaxed in the next release.
ToP   noToC   RFC2116 - Page 41
INTERNETWORKING ENVIRONMENT

   [RFC 1006] with TCP/IP,TP4, [RFC-1070] with IP,IPX, and NetBEUI.

HARDWARE PLATFORMS

   Runs on Microsoft Windows hardware platforms.

SOFTWARE PLATFORMS

   Windows 95, Windows NT, Windows for Workgroups

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   > 1,000

AVAILABILITY

   Commercially Available.

   Contact:

      Cycle Software,Inc.
      1212 Hancock St.
      Quincy, MA 02169

      Voice- 617-770-9594
      Fax- 617-770-9903
      E-mail cycle@livedata.com.

DATE LAST UPDATED or CHECKED

   1/96

ADDITIONAL INFORMATION and/or COMMENTS

   [No information provided. -- Ed.]
ToP   noToC   RFC2116 - Page 42
NAME

   DC X500

   Data Connection Ltd
   100 Church Street
   Enfield
   Middlesex
   EN2 6BQ
   UK

ABSTRACT

   DC X500 provides a truly scalable X.500 based enterprise directory
   server with the necessary architectural flexibility to enable
   integration with existing database and directory technologies.

   From a pure X.500 standpoint, DC X500 provides a full function
   state-of-the-art DSA implementation.

      * Architected from scratch according to the 1993 X.500
        standards (i.e. not a 1988 DSA with 1993 features grafted on)

      * Support for all the key X.500 OSI protocols:

         * Directory Access Protocol (DAP) for user access

         * Directory System Protocol (DSP) for distributed DSA
           comunications

         * Directory Information Shadowing Protocol (DISP) to support
           replication between servers to give improved performance
           in a distributed network

      * Support of the 1993 Basic Access Control and  Simplified
        Access Control models

      * Support for the key Internet  X.500 related standards:

         * integrated Lightweight DAP (LDAP)for DUA access

         * Madman MIBs for easy integration with SNMP

   The DC X500 architecture is based on Data Connection's underlying
   product architecture which has evolved since 1987 and includes:

         * genuine multi-threaded implementation
ToP   noToC   RFC2116 - Page 43
         * true  portability (the product is available on a range of
           operating systems e.g Windows NT, AIX, HP-UX. OS/2 etc and it
           is possible to port the core  technology to any
           hardware/software platform)

         * secure service recording for operation tracking and billing

         * support for system monitoring (both alarms and statistics)

   Key product features include:

         * Name resolution and integrated use of Search Indices based on
           2-3 trees leads to high performance operation evaluation
           (subsecond response times on  million entry DSAs)

         * Generic schema support based on 1993 concepts that allows
           customers to tailor the schema to meet their precise data
           structuing requirements

         * System recycle time is minimised (e.g. DC X500 can be backed
           up while running and  search indices are dynamically updated),
           helping achieve the goal of continuous (24x7) availability
           and high reliability.

         * No artificial software constraints are imposed resulting in a
           truly scalable product - assuming the availability of the
           necessary hardware DC X500 can be configured  to support
           millions of entries in a single DSA.

   DC X500 is certified for used within the Paradise Pilot project.  The
   product has also undergone interoperability testing at the EuroSInet
   interoperability workshops in Europe.

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

   From 1988 X.519

   9.2 Conformance by DSAs

   9.2.1 Statement Requirements

      a) directoryAccessAC and directorySystemAC are both supported

      b)  the DSA can act as a first level DSA

      c)  the chained mode of ooperation is supported.
ToP   noToC   RFC2116 - Page 44
      d)  security levels none and simple as supported with the
          delivered product. However, the product is architectured
          to interface to an external security module to support
          strong authentication.

      e)  DC X500 supports the selected attribute types defined
          in X.520.

      f) DC X500 supports the selected object classes defined in X.521.

   9.2.2 Static Requirements

   DC X500 supports the static requirements implied by the above
   statement.

   9.2.3 Dynamic Requirements

   DC X500 supports the dynamic requirements implied by the above
   statement.

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

   From 1993 X.519

   9.2 Conformance by DSAs

   9.2.1  Statement Requirements

   a) directoryAccessAC and directorySystemAC are both supported

   b)  n/a

   c) the DSA can act as a first level DSA

   d) the chained mode of ooperation is supported.

   e) security levels none and simple as supported with the delivered
      product. However, the product is architectured to interface to
      an external security module to support strong authentication.

   f) DC X500 supports the selected attribute types defined in X.520.
      Attributes based on the syntax DirectoryString using the
      UNIVERSAL STRING choice can be stored however the UNIVERSAL
      STRING choice cannot be used for matching rules.

   g) DC X500 supports the selected object classes defined in X.521.
ToP   noToC   RFC2116 - Page 45
   h) DC X500 supports the following extensions

         subentries                         Y
         copyShallDo                        Y
         attributeSizeLimit                 Y
         extraAttributes                    Y
         modifyRightsRequest                N
         pagedResultsRequest                N
         matchedValuesOnly                  N
         extendedFilter                     N
         targetSystem                       N
         useAliasOnUpdate                   Y
         newSuperior                        Y

   i) DC X500 does not support collective attributes

   j) DC X500 does not support hierarchical attributes

   k) DC X500 supports the following operational attributes

         Directory Operational Attributes:

         structural object class
         governing structural rule
         create timestamp
         modify timestamp
         creators name
         modifiers name

         prescriptive ACI
         entry ACI
         subentry ACI

         DSA Operational Attributes:

         myAccessPoint
         superiorKnowledge
         supplierKnowledge (*)
         consumerKnowledge(*)
         secondaryShadows (*)

         * - supported using local proprietary extension

         Distributed Operation Attributes (dsa-shared):

            specificKnowledge
            nonSpecificKnowledge
ToP   noToC   RFC2116 - Page 46
   l) DC X500 supports return of alias names

   m) DC X500 supports indicating that returned entry information is
      complete

   n) DC X500 supports modifying the object class attribute to add
      and/or remove values identifying auxiliary object classes

   o) DC X500 supports Basic Access Control

   p) DC X500 supports Simplified Access Control

   q) DC X500 does not support subschema administration as defined
      in X.501.

   r) DC X500 supports the name binding defined in X.521

   s)  DC X500 cannot administer collective attributes.

   9.2.2 Static Requirements

   DC X500 supports the static requirements implied by the above
   statement.

   9.2.3 Dynamic Requirements

   DC X500 supports the dynamic requirements implied by the above
   statement.

   9.3 Conformance By Shadow Supplier

   9.3.1  Statement Requirements

   a) shadowSupplierInitiatedAC and shadowConsumerInitiatedAC
      are supported.

   b) security levels none and simple as supported with the delivered
      product. However, the product is architectured to interface to
      an external security module to support strong authentication.

   c) DC X500 supports the following UnitOfReplication:

         * Entry filtering on object class is supported

         * Selection/Exclusion of attributes via a  AttributeSelection
           is not supported
ToP   noToC   RFC2116 - Page 47
         * Inclusion of subordinate knowledge in the replicated area is
           supported

         * Inclusion of extended knowledge in addition to subordinate
           knowledge is supported

   9.3.2  Static Requirements

   a) DC X500 supports the shadowSupplierInitiatedAC and
      shadowConsumerInitiatedAC

   b) DC X500 provides support for modifyTimestamp and createTimestamp
      operational attributes

   9.3.3  Dynamic Requirements

   a) DC X500 conforms to the mapping onto used services defined
      in clause 8

   b) DC X500 conforms to the procedures of X.525 as they relate
      to DISP.


   9.4 Conformance by a Shadow Consumer

   9.4.1  Statement Requirements

   a) shadowSupplierInitiatedAC and shadowConsumerInitiatedAC
      are supported.

   b) security levels none and simple as supported with the delivered
      product. However, the product is architectured to interface to
      an external security module to support strong authentication.

   c) DC X500 can act as a secondary supplier.

   d) DC X500 does not support shadowing o overlapping units
      of replication. (Overlapping Administration Points
      are supported though).

   9.4.2  Static Requirements

   a) DC X500 supports both shadowSupplierInitiatedAC and
      shadowConsumerInitiatedAC.

   b) DC X500 supports the modifyTimestamp and createTimestamp
      operational attributes.
ToP   noToC   RFC2116 - Page 48
   c) DC X500 supports the copyShallDo service element

   9.4.3  Dynamic Requirements

   a) DC X500 conforms to the mapping onto used services defined
      in clause 8

   b) DC X500 conforms to the procedures of X.525 as they relate
      to DISP.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [No information provided. -- Ed.]

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [No information provided. -- Ed.]

INTEROPERABILITY

   DC X500 has interoperated with the following implementations:

      DUAs:

         ICL
         SNI
         Net-tel
         Bull
         AT&T
         CDC
         Digital
         ICL
         Nexor

      DSAs:

         SNI
         ICL
         AT&T
         CDC
         Digital
         ICL
         Net-tel
         Nexor
ToP   noToC   RFC2116 - Page 49
PILOT CONNECTIVITY

   DC X500 has been tested and approved for connectivity to the PARADISE
   pilot project.

BUGS

   [No information provided. -- Ed.]

CAVEATS AND GENERAL LIMITATIONS

   [No information provided. -- Ed.]

INTERNETWORKING ENVIRONMENT

   DC X500 supports the following network connectivity:


         * [RFC 1006] with TCP/IP

         * TP0 with X.25

HARDWARE PLATFORMS

   DC X500 is a portable product

SOFTWARE PLATFORMS

   DC X500 is a portable product.  It is available on the following
   plaforms:

         * UNIX, including

           * IBM AIX

           * HP UX

           * Sun Solaris

           * Windows NT

           * OS/2.

   Porting to further UNIX platforms is very straightforward, in
   particular where existing transport services are available. Other
   proprietary systems (such as Novell's Netware, Digital's VMS or fault
   tolerant or mainframe environments) can also be supported if
   required.
ToP   noToC   RFC2116 - Page 50
NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   DC X500 is commercially available.

   For further details, please contact:

   Nigel Ratcliffe Data Connection Ltd 100 Church Street Enfield
   Middlesex EN2 6BQ UK

   Tel: +44 181 366 1177

   E-mail: nr@datcon.co.uk

DATE LAST UPDATED or CHECKED

   February 1996

ADDITIONAL INFORMATION and/or COMMENTS

   Data Connection provides a whole series of directory applications,
   including a corporate telephone directory, e-mail synchronisation,
   security services, groupware directory integration and a directory
   publishing application.  These can be accessed by Windows
   applications or standard web browsers.

   Further information can be found at http://www.datcon.co.uk.
ToP   noToC   RFC2116 - Page 51
NAME

   DE

ABSTRACT

   DE (Directory Enquiries) is intended to be a simple-to-use DUA
   interface, suitable for the naive user, and suitable for running as a
   public access dua.  it will work on any terminal.  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.

   There have been a few minor enhancements since the description in
   [RFC 1632].  The power searching feature still sets DE apart from
   most other DUAs - 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.  DE also allows UFN
   style searching.  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.  DE incorporates a QOS feature where it
   maintains a database of past information availability and DSA
   responsiveness.  Translations exist into at least 4 different
   languages.

   DE runs over ISODE DAP and University of Michigan LDAP.  There is a
   version of DE, called DOS-DE, which has been ported to DOS, and this
   uses LDAP.

   DE was funded by the COSINE PARADISE project, and DE is used as the
   PARADISE public access dua. You can test the software by telnet to
   directory.ja.net and logging in as dua -- no password required.

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

   N/A

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

   [No information provided -- Ed.]

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [RFC 1274] and [RFC 1487] Yes and yes
ToP   noToC   RFC2116 - Page 52
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [RFC 1484].  yes

INTEROPERABILITY

   N/A

PILOT CONNECTIVITY

   The interface is widely used in the publicly accessible PARADISE
   directory.

BUGS

   Doesn't handle aliases well when power searching.

   Send bug reports to:

   p.barker@cs.ucl.ac.uk

CAVEATS AND GENERAL LIMITATIONS

   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 can handle photographs and reproduce sound attributes if these are
   dealt with by ancillary programs.

INTERNETWORKING ENVIRONMENT

   [RFC 1006] with TCP/IP, TP0 or TP4 with X.25, and LDAP.

HARDWARE PLATFORMS

   UNIX + DOS platforms

   SOFTWARE PLATFORMS

   UNIX + DOS

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]
ToP   noToC   RFC2116 - Page 53
AVAILABILITY

   The software is freely available from

   ftp://cs.ucl.ac.uk/dirpilot/de-7.0.tar.Z

   The DOS version is freely available.  Look in the following
   directory:

   ftp://ftp.bath.ac.uk/pub/x500/dosde7/

DATE LAST UPDATED or CHECKED

   March 96

ADDITIONAL INFORMATION and/or COMMENTS

   [No Information Provided -- Ed.]
ToP   noToC   RFC2116 - Page 54
NAME

   Digital X.500 Directory Server Digital Equipment Corporation

   This single entry covers a number of different products

ABSTRACT

   The Digital X.500 Directory Services product set includes a directory
   server product and a variety directory user agents, as well as a
   directory synchronizer utility.

   The Digital X.500 Directory Server product provides a high
   performance DSA implemented according to the 1993 edition of the
   standard. The InfoBroker Server product extends this to provide the
   server component for LDAP and WWW user agents.  Features of these
   servers include:

         * Integrated multi-protocol support allowing concurrent DAP,
           DSP, DISP and DOP access over OSI and TCP/IP (using [RFC
           1006]) protocols.

         * Indexed database (DIB) to support high-performance searching
           and sophisticated matching including approximate match.

         * A DIB based on the 1993 edition Extended Information Models.

         * Support for chaining and referrals in support of a
           distributed DIB

         * Support for the 1993 edition Basic Access Control scheme.

         * Configurable schema based on the 1993 edition (including
           attributes, object classes, structure rules, name forms).

         * Support for 1993 edition Shadowing using the DISP and DOP
           protocol, including both incremental and on-change features
           for high performance.

         * Remote management to control DSAs and log significant events.

         * Support for the LDAP protocols using the InfoBroker Server
           product across either TCP/IP  or DECnet transport protocols.

         * A Look-up Daemon that accepts requests from Web Browsers,
           allowing access to the directory from any web browser.

         * Both X/OPEN XDS/XOM and LDAP APIs.
ToP   noToC   RFC2116 - Page 55
         * An award winning documentation set.

   The Digital X.500 Administration Facility, X.500 Information Manager
   and InfoBroker Client products provide MS-Windows, Motif and command
   line interfaces to access and manage the information stored in the
   X.500 directory, including:

         * Support for different ways of accessing the directory, either
           by browsing or searching based on an  extensible set of
           filters.

         * Support for bulk load, unload and reload of entries.

         * Driven off the same configurable schema information as the
           DSA allowing extensibility of window layouts and text to
           support customer-defined object classes and attributes.

   The Synchronizer-500 is an X.500 DUA which:

   * Enables bi-directional synchronization between X.500 and
     virtually ANY other non-X.500 directory facilitating common
     management.

   * Maps incoming data into X.500 using flexible configuration
     files

   * Facilitates creation of a multivendor electronic mail
     database, creating addresses in the appropriate syntax for
     any mail system.

   * Provides uniqueness checking on mnemonic O/R addresses,
     preventing address duplication

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

   The Digital X.500 Directory Services products are based on the 1993
   edition standard. They are compatible with, and interwork with, 1988
   edition DUAs and DSAs, and are implemented to conform to relevant
   NIST OIW and EWOS agreements and the X.500 Implementors Guide.

   OSTC conformance testing (1988 DUA/DAP, DSA/DAP) has been completed
   and registered successfully.

   The X.500 Directory Server is registered as conformant to US-GOSIP.
ToP   noToC   RFC2116 - Page 56
COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)

   Conformance with respect to clause 9.2 of ISO/IEC 9594-5:1993:

         * Supports the  directoryAccessAC (DAP) and directorySystemAC
           (DSP) application contexts.

         * The DSA is capable of acting as a first-level DSA.

         * Chaining is supported.

         * Bind security levels of simple (unprotected password) and
           none are supported.

         * Supports the shadowSupplierInitiatedAC and
           shadowConsumerInitiatedAC in both synchronous and
           asynchronous variants (DISP protocol) and the
           directoryOperationalBindingManagementAC (DOP protocol) for
           shadowing

         * All attribute types defined in ISO/IEC 9594-6:1993 are
           supported except for 1993 edition supertypes and collective
           attributes and EnhancedSearchGuide. Customers can define new
           attribute types.  UNIVERSAL STRING is not supported for
           attributes based on DirectoryString.

         * All object classes defined in ISO/IEC 9594-7:1993 are
           supported.  Customers can define new object classes.

         * The following operational attributes  are supported:

            governingStructureRule      myAccessPoint
            modifyTimestamp             supplierKnowledge
            superiorKnowledge           specificKnowledge
            consumerKnowledge           prescriptiveACI
            dseType                     entryACI
            createTimestamp

         * Dynamic modification of object class is permitted

         * Basic Access Control is supported with some restrictions.

         * All name forms defined in ISO/IEC 9594-7:1993 are supported.
           Customers can defined new name forms and structure rules.
ToP   noToC   RFC2116 - Page 57
CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   The InfoBroker products support the V1 and V2 LDAP protocols for easy
   integration into LDAP-compliant client and server environments.

   Standards supported include [RFC 1006], [RFC 1274], [RFC 1277], [RFC
   1777], [RFC 1779].

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   RFCs supported include [RFC 1278], [RFC 1558]

INTEROPERABILITY

   Digital has performed X.500 interoperability testing at various
   Eurosinet and OSInet events, during the COS Pilot activity and in-
   house.  In addition, Digital's products were part of the EEMA
   Interoperability Demonstration in Amsterdam 1995.

   Digital has achieved successful DAP and DSP interworking with a
   number of vendors. In the a recent Eurosinet Interoperability event,
   tests were performed against:

            AT&T                           ISOCOR
            Control Data Systems           NET-TEL Computer Systems Ltd
            DCL (Data Connection Ltd)      NEXOR
            ICL                            SNI (Siemens Nixdorf)

   In addition, previous interoperability tests have been performed
   against:

            Hewlett Packard        Telstra
            ISODE Consortium       UNISYS
            QUIPU

   Digital has performed limited successful 1993 DISP (Replication)
   interworking with two vendors at a Eurosinet Interoperability event.
   These were:

      ICL                         NEXOR

   All interoperability test results will be available on request from
   Digital.

PILOT CONNECTIVITY

   Digital is actively involved in both public and private pilots of
   X.500.
ToP   noToC   RFC2116 - Page 58
BUGS

   Digital provides complete software maintenance services with products
   on a worldwide basis.

CAVEATS AND GENERAL LIMITATIONS

   None

INTERNETWORKING ENVIRONMENT

   The Digital X.500 Services products operate over:

         * [RFC 1006] over TCP/IP

         * OSI TP0, TP2 and TP4 over CLNS and CONS as appropriate

         * TCP/IP or DECnet transport protocols to communicate with an
           LDAP server.

HARDWARE PLATFORMS

   The Digital X.500 Directory Service products run on:

         * Alpha processors supported by Digital UNIX

         * Alpha and VAX processors supported by OpenVMS

SOFTWARE PLATFORMS

   The Digital X.500 Directory Service products currently run on:

         * Digital UNIX running DECnet/OSI

         * OpenVMS/AXP running DECnet/OSI

         * OpenVMS/VAX running DECnet/OSI

   For the latest availability on these and other other hardware and
   software platforms please contact Digital.

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]
ToP   noToC   RFC2116 - Page 59
AVAILABILITY

   The Digital X.500 Directory Service products are commercially
   available from Digital Equipment Corporation.  For further
   information please contact your local Digital office and quote SPD
   numbers 40.77.XX, 53.32.XX, 53.33.XX and 60.43.XX, or contact one of:

      Ian Gunn, Product Manager:           Nick Tatham, Engineering
      Manager:
      Tel: +1 603 881 0762                 Tel: +44 1734 203635
      Email: ian.gunn@zko.mts.dec.com      Email:
      nick.tatham@reo.mts.dec.com
      Digital Equipment Corporation        Digital Equipment Co. Ltd
      Corporate Software Engineering       Corporate Software
      Engineering
      110 Spit Brook Road                  PO Box 121
      Nashua, NH. 03062-2698               Reading, RG2 0TU
      USA                                  UK

DATE LAST UPDATED or CHECKED

   13th November 1995

ADDITIONAL INFORMATION and/or COMMENTS

   None
ToP   noToC   RFC2116 - Page 60
NAME

   DIR.D(tm) V2.6
   Siemens Nixdorf Informationssysteme AG

ABSTRACT

   DIR.D V2.6 is Siemens Nixdorf's directory browser product. Through
   its file manager like user interface only retrieval operations are
   supported. The DDE interface also allows for modification operations.
   DIR.D is an MS-Windows application acting as an LDAP client.

   Among others, DIR.D has the following features:

            * Graphical representation of the DIT

            * Tree browsing

            * Simple and complex searches, including approximate search

            * Adaptable to any directory schema

            * Configurable user interface

            * Automatic unbind after idle time

            * Anonymous and simple unprotected bind

            * Tight integration with SNI's X.400 user agent MAIL.D and
            CIT
              product ComfoPhone

            * Data transfer to Windows applications via clipboard, file,
              Drag&Drop, and DDE

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

   DIR.D V2.6 is an LDAP client.

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

   DIR.D V2.6 is an LDAP client.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   DIR.D V2.6 is compliant with the following RFCs: [RFC 1777], [RFC
   1778], [RFC 1779].
ToP   noToC   RFC2116 - Page 61
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   DIR.D V2.6 is compliant with the following RFCs: [RFC 1278], [RFC
   1558].

INTEROPERABILITY

   DIR.D V2.6 is based on University of Michigan's LDAP implementation
   V3.0. It can interoperate with any LDAP server.

PILOT CONNECTIVITY

   DIR.D V2.6 is used to browse in the European NameFLOW-PARADISE pilot
   network.

BUGS

   To report bugs and/or to retrieve additional information on SNI's
   directory products please send mail to infoline-
   com@s41.mch1.x400scn.sni.de.

CAVEATS AND GENERAL LIMITATIONS

   DIR.D V2.6 was designed for information retrieval.

INTERNETWORKING ENVIRONMENT

   LDAP with TCP/IP

HARDWARE PLATFORMS

   PC (Intel)

SOFTWARE PLATFORMS

   Windows 3.1 + Winsockets Windows for Workgroups 3.11 +
   Winsockets
   Windows 95
   Windows NT 3.5
   OS/2 3.0 + Windows for OS/2 +
   Winsockets

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   > 10,000
ToP   noToC   RFC2116 - Page 62
AVAILABILITY

   DIR.D V2.6 can be delivered as a binary product. It is commercially
   available from:

            Siemens Nixdorf Informationssysteme AG
            ASW BA COM 1
            D-81730 Munich
            Germany

   Please contact

            Giovanni Rabaioli
            Voice:    +49/89-636-41095
            Fax: +49/89-636-42552
            Mail:     Giovanni.Rabaioli@mch.sni.de

DATE LAST UPDATED or CHECKED

   April 1996

ADDITIONAL INFORMATION and/or COMMENTS

   The following X.500 products are also part of SNI's X.500 product
   family:

            DIR.X V4.0    1993 X.500 Directory Service
            DIR.X V3.1    1988 X.500 Directory Service
            ORG.D V2.1    Full administrative LDAP  browser
            DIR.X-SYNC    V2.0 Directory synchronization
ToP   noToC   RFC2116 - Page 63
NAME

   DIR.X (tm) V3.1 Siemens Nixdorf Informationssysteme AG

ABSTRACT

   DIR.X V3.1 is Siemens Nixdorf's Directory Service product compliant
   with the 1988 ITU-T X.500 recommendations. Siemens Nixdorf has
   supplied its Directory Service product as the GDS (Global Directory
   Service) component to OSF DCE.  However, DIR.X V3.1 has a number of
   features and enhancements which are not available in the GDS
   component of OSF DCE.

   DIR.X V3.1 is a distributed, replicated Directory Service. It
   consists of DSA, DUA and a tools package including comfortable
   administration and management utilities. DIR.X implements the
   protocol stack ranging from LDAP, DAP, DSP over ACSE, ROSE,
   Presentation, Session down to [RFC 1006]. On transport layer it
   supports TCP/IP and OSI LAN/WAN protocols.

   Data stored by DIR.X can be accessed via

      * the MS-Windows user interfaces DIR.D/ORG.D which are
        available as separate products from Siemens Nixdorf

      * any third-party LDAP or DAP browser

      * directory applications using the standardized X/Open XDS/XOM
        APIs (Directory Service / OSI Abstract Data Manipulation).
        The Siemens Nixdorf implementation was the first to gain
        XPG4-certification.

      * a command-line administration program

      * a menu-driven administration  program

      * WWW

      * a shell interface

      * the Query-by-mail interface of SNI's directory
        synchronization product DIR.X-SYNC

   DIR.X enables

      * The storage of globally-unique, tree-like name structures
        which can be mapped onto organizations.
ToP   noToC   RFC2116 - Page 64
      * The use of several alternative names (aliases) for one and
        the same directory entry.

      * Search queries that allow the user to select objects on the
        basis of specific attributes and their values, as with a
        "Yellow Pages" telephone directory

      * Treemanagement functions which can cover entire subtrees.

      * The creation and automatic updating of copies ("shadows")
        from remote computers.

      * Access protection at attribute level, which regulates access
        on an object-specific basis.

      * The storage of unstructured attributes (graphics, pixels).

   The tools package of DIR.X V3.1 includes:

      * gdssetup: A simple-to-use tool for the generation and
        initialization of a directory configuration.

      * gdshdsch: Enables the directory administrator to modify the
        directory schema off-line.

      * X.500 MIB access via SNMP

      * gdscp: A TCL based administration tool for UNIX clients with
        full XDS functionality

      * gdshd: A powerful import/export tool

   Additional features include:

      * support for ISO 8859-1 characters

      * dynamic schema modifications

      * caching.
ToP   noToC   RFC2116 - Page 65
COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs)

   DIR.X V3.1 fully complies with the following ITU-T recommendations
   and ISO/IEC standards:

            ITU-T   ISO/IEC   Title
            X.500    9594-1 Overview of Concepts, Models, and Services
            X.501    9594-2 Models
            X.511    9594-3 Abstract Service Definition
            X.518    9594-4 Procedures for Distributed Operations
            X.519    9594-5 Protocol Specifications
            X.520    9594-6 Selected Attribute Types
            X.521    9594-7 Selected Object Classes
            X.509    9594-8 Authentication  Framework

   DIR.X V3.1 was successfully conformance tested by the OSI Test
   Laboratory of Siemens Nixdorf. The OSI Test Laboratory is accredited
   by BAPT/DEKITZ (registration number TTI-P-G055/92-40). Test reports,
   PICS per X.581/X.582 and PIXITs are available for all tested
   protocols: DSA/DAP, DUA/DAP, Presentation, ACSE, and Session embedded
   in X.500.

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

   DIR.X V3.1 is not compliant with the 1993 ITU-T recommendations.
   Please refer to the DIR.X V4.0 implementation description.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   DIR.X V3.1 is compliant with the following RFCs: [RFC 1274], [RFC
   1277], [RFC 1565], [RFC 1567], [RFC 1777], [RFC 1778], [RFC 1779].

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   DIR.X V3.1 is compliant with the following RFCs: [RFC 1278], [RFC
   1558], [RFC 1801].

INTEROPERABILITY

   DIR.X V3.1 can interoperate with:

         * OSF DCE Global Directory Service (GDS)

         * ISODE Consortium Quipu V8.0

         * ISODE Consortium 93 DSA R3.0

         * AT&T  OpenDirectory 2.0.1
ToP   noToC   RFC2116 - Page 66
         * Bull X.500-DS and X.500-DUA

         * Control Data MailHub 2.4

         * Data Connection DC X500 V1

         * Digital DEC X.500 Directory Services V2.0

         * ICL I500 DSA V5.2

         * ISOCOR ISOPLEX DS V1.00

         * NET-TEL RouteFinder 500 DSA 1.0

         * NEXOR Messageware Directory Server V0.9

         * Olivetti UX_X500 V1.1

         * Unisys TransIT X.500 V7.1

PILOT CONNECTIVITY

   Several DIR.X V3.1 DSAs and DUAs are connected to the European
   NameFLOW- PARADISE pilot network.

BUGS

   To report bugs and/or to retrieve additional information on SNI's
   directory products please send mail to infoline-
   com@s41.mch1.x400scn.sni.de.

CAVEATS AND GENERAL LIMITATIONS

   DIR.X V3.1 is highly portable and without any general limitation.
   SNMP support is available for SNI platforms only.

INTERNETWORKING ENVIRONMENT

   [RFC 1006] with TCP/IP
   OSI TP0, TP2 with X.25
   OSI TP4 with CLNP
   OSI TP4 with CONS (LAN)

HARDWARE PLATFORMS

         SNI platforms (RM200/300/400/600, Pyramid Nile
              100/150, MX300i/500i) for X.25: X.25 board needed
ToP   noToC   RFC2116 - Page 67
         IBM RS/6000
              for X.25: X.25 board needed

         HP 9000
              for X.25: X.25 board needed

         Sun Sparc
              no X.25 board needed (X.25 can use the serial line)

         PC (Intel)
              for X.25: X.25 board needed

SOFTWARE PLATFORMS

         SINIX 5.42 + CMX + XTI
              for X.25: WAN-CCP needed

         Pyramid Nile 100/150 DC/OSx1.1

         Unixware

         AIX 3.2
              for X.25: OSI/6000 needed

         HP-UX 9.01
              for X.25: OTS 9000 needed

         Solaris 2.3
              for X.25: SunLink X.25 and SunLink OSI needed

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   100 and growing

AVAILABILITY

   DIR.X V3.1 can be delivered as a binary product or as source to OEM
   customers.  It is commercially available from:

         Siemens Nixdorf Informationssysteme AG ASW BA COM 1 D-
         81730 Munich Germany

   Please contact

         Giovanni Rabaioli
         Voice:    +49/89-636-41095
         Fax:      +49/89-636-42552
         Mail:     Giovanni.Rabaioli@mch.sni.de
ToP   noToC   RFC2116 - Page 68
DATE LAST UPDATED or CHECKED

   April 1996

ADDITIONAL INFORMATION and/or COMMENTS

   The following X.500 products are also part of SNI's X.500 product
   family:

      DIR.X V4.0    1993X.500 Directory Service
      DIR.D V2.6    LDAP browser for information retrieval
      ORG.D V2.1    Full administrative LDAP browser
      DIR.X-SYNC V2.0 Directory synchronization
ToP   noToC   RFC2116 - Page 69
NAME

   DIR.X (tm) V4.0 Siemens Nixdorf Informationssysteme AG

ABSTRACT

   DIR.X V4.0 is Siemens Nixdorf's Directory Service product compliant
   with the 1993 ITU-T X.500 recommendations. The implementation
   incorporates SNI's experience of 10 years development, support and
   maintenance of the DIR.X products conformant to the 1988 Directory
   Standards, and has the following main features:

      * It conforms to the 1993 Directory standards, with particular
        emphasis on the requirements for interoperability with other
        X.500 implementations

      * The implementation is scaleable: it handles small-scale
        workgroup directories as well as very large directories for
        backbone solutions in large organisations

      * The implementation is extensible: new functionality can
        easily be incorporated

      * Existing databases and proprietary directory services can be
        accessed or integrated with the implementation.

      * Particular emphasis is placed on ease of administration of
        the Directory Service a service based on DIR.X V4.0 can be
        administered effectively from a central site, including the
        management of configuration and monitoring options

      * The implementation has a high throughput performing well not
        only on small systems, but also on high-performance backend
        servers, handling hundreds of requests in parallel on a
        multiprocessor machine.

   DIR.X V4.0 is a distributed, replicated Directory Service. It
   consists of:

      * DSA

      * DUA

      * Command-line DUA using a TCL (Tool Control Language) shell
        interface (dirxcp)

      * Management centre (dirxadm)


(next page on part 3)

Next Section