Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 2116

X.500 Implementations Catalog-96

Pages: 164
FYI 11
Obsoletes:  1632
Part 3 of 5 – Pages 70 to 104
First   Prev   Next

ToP   noToC   RFC2116 - Page 70   prevText
      * Toolkit for application development

   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 V4.0 is fully backwards compatible with 1988 DSAs and DUAs.

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

   DIR.X V4.0 is fully backwards compatible 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
ToP   noToC   RFC2116 - Page 71
COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)

   DIR.X V4.0 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
      X.525   9594-9 Replication

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   DIR.X V4.0 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 V4.0 is compliant with the following RFCs: [RFC 1278], [RFC
   1558], [RFC 1801].

INTEROPERABILITY

   Interoperability tests have not been completed yet.

PILOT CONNECTIVITY

   [No information provided. -- Ed.]

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 V4.0 is highly portable and without any general limitation.
ToP   noToC   RFC2116 - Page 72
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)
           for X.25: X.25 board needed

      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

      Windows NT 3.51

      AIX 4.1
           for X.25: OSI/6000 needed

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

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

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   Field testing to be started in Summer 1996.
ToP   noToC   RFC2116 - Page 73
AVAILABILITY

   DIR.X V4.0 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

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 V3.1   1988 X.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 74
NAME

DIR.X-SYNC (tm) V2.0 Siemens Nixdorf Informationssysteme AG

ABSTRACT

   DIR.X-SYNC V2.0 enables the synchronization of existing e-mail
   address directories in the X.500-based DIR.X directory service. The
   standard DIR.X, DIR.X-SYNC and DIR.D (all available from Siemens
   Nixdorf) products are the foundations on which the corporate
   directory solutions can be tailored to meet the customer's needs. The
   corporate directory then becomes the universal information system
   within the company.

   The user can access corporate directory information in different
   ways:

      * Using DIR.D, SNI's Windows client for the X.500 service, PC
        users can gain easy access to the DIR.X server containing the
        corporate directory data. The data found can  be transferred
        to other applications by means of DDE, drag and drop or cut
        and paste. (See DIR.D V2.6 for further information).

      * Query by mail: Authorized users can access data stored in the
        central or distributed directory system over their own mail
        system. DIR.X-SYNC retrieves the inquiry transmitted by mail
        and directs it on to the X.500 service. The search results
        are then delivered back to the user by mail. Using a WWW
        interface based on TCL scripts

   Query by mail does not require additional software on the end system.
   Each mail system connected to the X.400 backbone (e.g. MS-Mail,
   cc:Mail etc.) can use this function. DIR.X-SYNC currently supports
   the address formats of the following e-mail systems:

      * MAIL.X-OD V2.3

      * MAIL.2000 V1.2, AKOM

      * MS-Mail

      * cc:Mail

      * Intelligent Messaging Mail (Banyan)
ToP   noToC   RFC2116 - Page 75
   The standardized ISO-10021 interface for X.400 addresses is
   supported, enabling need for extension. This means that any type of
   system capable of generating this format (e.g. WordPerfect, Lotus
   Notes) can be connected. Address acknowledgment is carried out in ISO
   format.

   Functions for the administrator:

      * Export: Addresses can be exported from local directories.
        They are delivered as mail messages in ASCII format to the
        DIR.X-SYNC server.

      * Upload: The upload server stores the exported local addresses
        in DIR.X as globally valid X.400 addresses.

      * Query by Mail: DIR.X-SYNC enables mail members to send a
        search to the DIR.X-SYNC server by e-mail. Using this
        function, authorized administrators of the synchronized
        directories can acquire copies of the corporate directory
        data.

      * Administration of the DIR.X-SYNC server with an
        administration tool which can be used via command line or a
        command file.

   Other features include:

      * Replication and distribution: In addition to the central
        solution with a single corporate directory server, DIR.X-SYNC
        also supports replicated or distributed data storage in
        DIR.X-SYNC server.

      * Authentication/Authorization: To prevent unauthorized use of
        the corporate directory system, the O/R addresses of the
        authorized administrators and users are configured by the
        DIR.X-SYNC administrator. When a query by mail or an update
        arrives, the sender address is compared with this address.

      * Logging: In the case of error, e.g. incorrect file format,
        the sender (and the administrator  configurable) are informed
        of the fault by mail. At the same time, the error message is
        saved in a log file for the DIR.X-SYNC administrator. In
        addition, a "history  file" enables the monitoring of the
        uploads that have run or are currently running

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

      DIR.X-SYNC is a directory application.
ToP   noToC   RFC2116 - Page 76
COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)

      DIR.X-SYNC is a directory application.

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

   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

   The DIR.X-SYNC server runs with SNI's mail service products MAIL.X
   V2.3 or MAIL.X V3.0.

INTERNETWORKING ENVIRONMENT

   [No information provided. -- Ed.]

HARDWARE PLATFORMS

   SNI platforms (RM200/300/400/600, MX300i/500i)

   HP 9000

SOFTWARE PLATFORMS

   SINIX 5.42

   HP-UX 10.0
ToP   noToC   RFC2116 - Page 77
NUMBER OF IMPLEMENTATIONS IN THE FIELD

   100

AVAILABILITY

   DIR.X-SYNC V2.0 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
      DIR.D V2.6   LDAP browser for information retrieval
      ORG.D V2.1   Full administrative LDAP browser
ToP   noToC   RFC2116 - Page 78
NAME

   DX500 OpenDirectory(tm)

   Datacraft Australia Pty Ltd

ABSTRACT

   DX500 OpenDirectory is a family of carrier grade, version 1993 X.500
   conformant products

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)

   See WEB page:  http://www.datacraft.com.au/dx500ovr.html for up to
   date details.

   PICS are available upon request.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [No information provided. -- Ed.]

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [No information provided. -- Ed.]

INTEROPERABILITY

   OpenDirectory DSA supports:

      * DX-plorer, 93 full DAP stack, [RFC 1006] client over Winsock

      * ISOPRO 1.5+ messaging clients
      * ISOPRO for MAPI messaging clients
      * ISOPLEX Navigator
      * ISOPLEX Management Centre
      * ISOPLEX DS
      * ISOPLEX Web Gateway

      * Uni of Mich. - WAX500

      * Quipu emulation mode
ToP   noToC   RFC2116 - Page 79
PILOT CONNECTIVITY

   [No information provided. -- Ed.]

BUGS

   [No information provided. -- Ed.]

CAVEATS AND GENERAL LIMITATIONS

   [No information provided. -- Ed.]

INTERNETWORKING ENVIRONMENT

   [No information provided. -- Ed.]

HARDWARE PLATFORMS

   [No information provided. -- Ed.]

SOFTWARE PLATFORMS

   [No information provided. -- Ed.]

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   The software is commercially available from Datacraft, or its
   distributors.

DATE LAST UPDATED or CHECKED

   March, 96

ADDITIONAL INFORMATION and/or COMMENTS

   Capable of supporting a million entries, with subsecond response
   time, on small Unix, with 32 mgbytes of ram, due to a unique
   patented meta-data design.
ToP   noToC   RFC2116 - Page 80
NAME

   Forum LOOK'UP (tm)

   Telis Systemes & Communications

ABSTRACT

   Forum LOOK'UP (tm) is a Corporate directory solution based on the
   X.500 recommendations. It includes:

      * a Directory System Agent (DSA),

      * Directory User Agents (DUAs).

      * local network connections

      * remote workstation access

      * a WEB and videotex access

      * data  updating tools

      * a directory editing tool

   Forum LOOK'UP is a product based on PIZARRO, the research prototype
   developed at INRIA by Christian Huitema's team, and commercialized by
   Telis, a member of the France Telecom group.

   Characteristics of the DSA are:

      * The DAP and DSP protocols are provided conformant with X.500
        (88).

      * The DIB is maintained in ASN.1 encoded format in the Unix
        file system.

      * Utilities are provided to load and dump the DIB from and to
        ASCII text files.

      * As an option, an ORACLE V7 database can also be used.

      * The DIT structure is held in main memory. Frequently used
        attributes may be held in inverted tables in memory to speed
        up searches.

      * Knowledge management: knowledge on managed domains is stored
        in Forum LOOK'UP specific attributes of the DSA entries.
ToP   noToC   RFC2116 - Page 81
      * Schema: The X.500 (88), X.400 (88) and most of the Cosine and
        Internet Schema are supported. Object class and attribute
        definitions are enforced. Users may define their own.

      * Simple authentication is provided strong authentication and
        signed operations have been tested operationally through
        Telis's participation in PASSWORD, a VALUE project with aim
        to pilot a European security infrastructure for network
        applications.

      * Access control : the DSA offers a mechanism defined by Telis
        that is functionally equivalent to a profile of the X500 '93
        access control mechanism. The mechanism is based on the
        notion of administrative domains (autonomous and semi-
        autonomous). A domain defines the user groups (categories)
        and their access rights (consult, modify) to specified
        attribute types. The access rights are defined in
        prescriptive and entry ACI attributes.

      * Phonetic searches : administrators may specify a language
        (English, French, ...) for a subtree of the DIT. Approximate
        (phonetic) searches will then be carried out in the given
        language. The software loads a rule database to which new
        languages and new rules may be added easily.

      * Management: a Forum LOOK'UP DSA object has been defined to
        allow operational parameters of the DSA to be managed via
        DAP. Forum LOOK'UP conforms to X.500 (88) as specified in
        poaragraph 9 of X.519 Administration tools are provided :

      * to generate usage statistics automatically and distribute
        these by mail to administrators

      * to replicate subtrees of the DIT to other FORUM LOOK'UP
        DSAs and automatically update shadow copies,

      * to extract hardcopy listings from the database in an Excel
        compatible format for "paper" directories, all the
        management tasks are performed through a GUI (X/Motif).

      * The GUI includes a "dashboard" for monitoring of servers and
        the hardware they are installed on.

      * The DUAs include a graphical directory browser with powerful
        search functionality for PCs and Macintosh.
ToP   noToC   RFC2116 - Page 82
COMPLIANCE with X.500-1988 (applicable only for DSAs and DUAs)

   Forum LOOK'UP conforms to X.500 (88) as specified in paragraph 9 of
   X.519

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

   [No information provided. -- Ed.]

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [RFC 1274], [RFC 1277], [RFC 1778], [RFC 1779] are supported

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [RFC 1278], [RFC 1279] are supported

INTEROPERABILITY

   Through the use of Forum LOOK'UP in the French Paradise pilot,
   interoperability has been informally but extensively tested with
   Quipu, Marben, SNI DIR/X.

PILOT CONNECTIVITY

   DSA connectivity to the PARADISE pilot.

BUGS

   Forum LOOK'UP is a commercial product. As such, it is supported and
   bugs are fixed when detected.

   Bug reports can be sent to our support team via electronic mail.

CAVEATS AND GENERAL LIMITATIONS

      * The DIT structure and inverted attribute tables are stored in
        main memory.

      * The recommended main memory size for a DSA is 1kb per node,
        i.e., 10 Mb for a database of 10,000 objects.

      * The current recommended maximum for the proprietary database
        (based on the Unix file system) is a database size of the order
        of 100,000 objects.

      * For a larger database one unique server (up to 300,000 objects),
        the use of the Oracle database is recommended
ToP   noToC   RFC2116 - Page 83
      * Of the selected attribute types defined in X.500 (88), the
        searchGuide attribute is not supported

      * neither are the following attributes from the Cosine and
        Internet Schema [RFC 1274]: OtherMailbox, MailPreferenceOption
        and the various quality attributes.

INTERNETWORKING ENVIRONMENT

   Forum LOOK'UP includes a transport stack for TP0 with TCP/IP [RFC
   1006] and X.25. The stack has been ported to SunNet OSI for TP4 with
   CLNP.

   DUAs on a LAN (Novell Netware, Microsoft Lan Manager, IBM Lan Server)
   can access the DSA without the need for IP on every Workstation. A
   module (called SOLO server) available on Novell, OS/2 and UNIX allows
   to have an IP or X.25 stack only on the file server. It is in charge
   of forwarding the request to a DSA.

   A direct access (DUA / DSA) through IP, X.25, PSTN or ISDN is also
   available.

HARDWARE PLATFORMS

   Forum LOOK'UP can easily be ported to any UNIX machine.

   It currently runs on: Sun Solaris and Hewlett Packard.

   A port on IBM AIX is to be completed.

SOFTWARE PLATFORMS

   The Forum LOOK'UP server is portable to any UNIX-like operating
   system.  X/Motif is the interface used for management.

   The DUAs are available on Windows and Macintosh.

   ORACLE V7 can be used as a database (option).

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   30 servers
ToP   noToC   RFC2116 - Page 84
AVAILABILITY

   Forum LOOK'UP is commercially available. For further information
   contact:

         Laurence Puvilland, Product manager
         Email: C=fr A=atlas P=telis-sc O=telis-sc OU1=paris S=puvilland
         laurence.puvilland@paris.telis-sc.fr

         or:

         Ascan Woermann, X.500 development manager
         Email: C=fr A=atlas P=telis-sc O=telis-sc OU1=sophia S=Woermann
         ascan.woermann@sophia.telis-sc.fr

DATE LAST UPDATED or CHECKED

   April 1996

ADDITIONAL INFORMATION and/or COMMENTS

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

   FX*500

   Firefox International Limited

ABSTRACT

   FX*500 is a core component of Firefoxs product suite for mail,
   messaging and directories.

   FX*500 provides a Directory System Agent (DSA) which adheres to the
   latest 1993 X.500 standards.

   FX*500 may be used in conjunction with the Firefox FX*400 messaging
   products or may be combined with a range of Directory User Agent and
   Gateway products in order to satisfy a broad range of directory
   requirements.

   FX*500 affords unique integration opportunities with Novell's NetWare
   Directory Service (NDS) by offering the option of true dynamic
   directory integration between NDS and X.500.

   FX*500 provides support for key features of the X.500 1993 standard
   while continuing to support interworking with 1988 based directory
   user agents and system agents. The main 1993 features of X.500
   supported by FX*500 are:

      * Basic Access Control

      * The 1993 DSA Information Model

      * Replication and Shadowing

   In summary, FX*500 supports:

      * 1988 and 1993 X.500 Directory Access Protocol (DAP)

      * 1988 and 1993 X.500 Directory System Protocol (DSP)

      * 1993 X.500 Directory Information Shadowing Protocol (DISP)

      * 1993 Basic (or Simplified) Access Control

      * the Lightweight Directory Access Protocol (LDAP), as defined
        by [RFC 1777]
ToP   noToC   RFC2116 - Page 86
      * configuration of knowledge information for distributed
        operation using 1993 operational attributes

      * local management services, including a knowledge
        configuration application and extensive diagnostic facilities

      * an extended set of management applications

      * operation in a wide variety of network environments including
        connectivity over X.25, TCP/IP [RFC 1006] and OSI LANs.

      * an application developer's toolkit

   The optional application developer's toolkit includes:

      * the X/Open Directory Services (XDS) API to support directory
        user agent applications

      * a Gateway (G-XDS) API which is based on a simplified version
        of the XDS API syntax and allows developers to implement
        gateways to existing/ proprietary directory databases

      * a Network Management Interface (NMI) to support management
        applications and integration with management services.

   FX*500 is delivered with a schema defined to support the Common Use
   and MHS (X.402) Schemas defined by UK GOSIP V4. The subschema for
   FX*500 can be modified by the customer and updated dynamically.

   FX*500 provides for search optimisation by supporting keyed search
   whereby specific attributes can be identified as 'keyed' through
   local configuration data. This optimisation avoids the need to do a
   "brute force" search which requires a traversal of all the nodes of a
   subtree. Approximate match search filters are also supported by using
   a phonetic search based on the "Soundex" algorithm.

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

   FX*500 meets both the static and dynamic requirements implied by
   section 9.2 of X.519 1988.

   From section 9.2 of X.519 1988 regarding DSA conformance:

      * FX*500 supports both the directoryAccessAC and
        directorySystemAC application contexts.

      * The FX*500 DSA can act as a first level DSA
ToP   noToC   RFC2116 - Page 87
      * The chained mode of operation is supported.

      * The security levels "none" and "simple" are supported, the
        "strong" security level can be supported with the addition of
        an appropriate security module.

      * The attribute types defined in X.520 and the object classes
        defined in X.521 are supported.

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

   FX*500 meets both the static and dynamic requirements implied by
   sections 9.2, 9.3 and 9.4 of X.519 1993 regarding the conformance of
   DSA, Shadow Supplier and Shadow Consumer.

   From section 9.2 of X.519 1993 regarding DSA conformance:

      * FX*500 supports both the directoryAccessAC and
        directorySystemAC application contexts

      * the FX*500 DSA can act as a first level DSA

      * the chained mode of operation is supported.

      * the security levels "none" and "simple" are supported, the
        "strong" security level can be supported with the addition of
        an appropriate security module.

      * the selected attribute types defined in X.520 are supported.
        The UNIVERSAL STRING choice for DirectoryString is supported
        but cannot be used for matching rules.

      * the selected object classes defined in X.521 are supported.

      * FX*500 supports the following 1993 extensions to the DAP and
        DSP protocols:

         * subentries

         * copyShallDo

         * attributeSizeLimit

         * extraAttributes

         * useAliasOnUpdate

         * newSuperior
ToP   noToC   RFC2116 - Page 88
      * FX*500 supports the following operational attributes:

         * structural object class

         * governing structural rule

         * create timestamp

         * modify timestamp

         * creators name

         * modifiers name

         * prescriptive ACI

         * entry ACI

         * subentry ACI

         * myAccessPoint

         * superiorKnowledge

         * supplierKnowledge (supported by local mechanism)

         * consumerKnowledge (supported by local mechanism)

         * secondaryShadows (supported by local mechanism)

         * specificKnowledge

         * nonSpecificKnowledge

      * FX*500 supports return of alias names and indication that
        returned entry information is complete

      * support is given to modifying the object class attribute to
        add and/or remove values identifying auxiliary object classes

      * FX*500 supports both Basic Access Control and Simplified
        Access Control

      * FX*500 supports the name bindings defined in X.521
ToP   noToC   RFC2116 - Page 89
   From section 9.3 and 9.4 of X.519 1993 regarding conformance of a
   Shadow Supplier and Shadow Consumer respectively:

      * FX*500 supports the shadowSupplierInitiatedAC and
        shadowConsumerInitiatedAC application contexts

      * the security levels "none" and "simple" are supported, the
        "strong" security level can be supported with the addition of
        an appropriate security module.

      * FX*500 supports the following UnitOfReplication:

         * Entry filtering on object class

         * Inclusion of subordinate knowledge in the replicated area

         * Inclusion of extended knowledge in addition to subordinate
           knowledge

      * FX*500 can act as a secondary shadow supplier.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   Supports [RFC 1274], [RFC 1567],[RFC 1777],[RFC 1778],[RFC 1779]

   FX*500 maintains statistics that are a superset of those defined by
   [RFC 1567] "X.500 Directory Monitoring MIB".

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [No information provided. -- Ed.]

INTEROPERABILITY

   Firefox are members of EurOSInet and test FX*500 by direct links with
   other members and at interoperability workshops.

PILOT CONNECTIVITY

   Firefox are participating in the NameFLOW-Paradise project, which is
   the successor to the Paradise European X.500 directory pilot.

BUGS

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

   [No information provided. -- Ed.]

INTERNETWORKING ENVIRONMENT

   FX*500 utilises the Firefox FX*STACK product to provide an OSI stack
   for use over local or wide-area networks.  This enables the X.500
   DAP, DSP and DISP protocols operate over a range of different network
   types. The current network options are:

      * OSI LANs are supported by Transport Class 4 over CLNP (ISO
        8473), including the ES-IS routing protocol.

      * X.25 networks are supported in either a Connection-Oriented
        Network Service (CONS) or a Connection-Less Network Service
        (CLNS) environment.

         * For CONS, Transport Classes 0, 2 and 4 are supported over
           X.25(1984).

         * For CLNS, Transport Class 4 is supported over CLNP (ISO
           8473) utilising X.25 as a subnetwork.

      * TCP/IP networks are supported by an implementation of [RFC
        1006], which supports Transport Class 0 over TCP/IP.

HARDWARE PLATFORMS

   Intel 386, 486, Pentium

SOFTWARE PLATFORMS

   FX*500 is available on NetWare 3.12 and 4.1, UnixWare 1.1.

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   FX*500 is commercially available.
ToP   noToC   RFC2116 - Page 91
   For further details please contact:

         Keith Vallance
         Product Manager
         Firefox International Limited
         668 Hitchin Road
         Stopsley
         Bedfordshire LU2 7UH
         UK

         Tel:    +44 (0)1582 29007
         Fax:    +44 (0)1582 29107
         email: keithv@firefox.co.uk

         Ken Sanofsky
         Firefox (U.S.) Inc.
         Seventh Floor
         2099 Gateway Place
         San Jose
         CA 95110-1017

         Tel:    +1 408 321 8344
         Fax:    +1 408 321 8311
         email: kens@firefox.com

DATE LAST UPDATED or CHECKED

   April 1996

ADDITIONAL INFORMATION and/or COMMENTS

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

   Global Directory Server

   Control Data Systems, Inc.

ABSTRACT

   Control Data's X.500 implementation, called the Global Directory
   Server, is compliant with the 1993 ITU-T Recommendations X.500-X.521,
   except for DOP, schema publication, and non-specific subordinate
   references. Features include:

      * 1993 administrative framework

         * 1993 operational attributes

         * 1993 reference structure

         * 1993 distributed operations

         * 1993 incremental and full replication including:

           * Supplier or consumer initiated

           * Periodic (by update interval) or onchange replication

           * Complete subtree specification to select replicated
             area

           * Reference replication

         * 1993 basic access control including:

           * Prescriptive, entry and subentry ACI supported

           * Item first and user first specification

           * All user classes supported including users by subtree
             specification

           * Access control by entry, attribute, and attribute value

           * All priority levels supported

         * 1993 collective attributes

         * 1993 hierarchical attributes
ToP   noToC   RFC2116 - Page 93
         * 1993 operational extensions

         * 1993 modifyDN operation

         * Full interoperability with "quipu" implementations including:

           * quipu replication for designated portions of DIT

           * quipu reference model for designated portions of DIT

           * enhanced quipu access controls (ACLs)

           * quipu operational attributes for designated portions of
             DIT

           * Can "automatically" migrate quipu DIT to 1993 DIT:

           * Migration process is dynamic, can occur while DSA is
             operating

           * Process preserves quipu attributes if desired

      Also:

         * Directory API based on the X.400 API

         * Support for X.400 objects including those to support MHS use
           of directory to support MHS routing

         * Integration with Control Data's Mail*Hub standards-based E-
           mail and directory integration products

         * DUA interfaces that support the full set of directory
           operations

         * A DUA daemon that provides directory access for applications

         * Directory synchronization tools for synchronizing
           PC/Mac/DEC/IBM mail directories and other sources of
           information, such as human resources databases, with X.500

         * Hash indexing for fast string search

         * dixie, dad, finger, whois, and ph.x500 support

         * SNMP based monitoring and management of DSAs

         * Support for DAP, LDAP, DSP, and DISP
ToP   noToC   RFC2116 - Page 94
         * Can be browsed via standard World Wide Web browsers

   Control Data Systems offers complete integration services to design,
   plan, install, configure, tailor and maintain X.500 services. These
   services may include the preparation of customer unique DUAs and
   tools for X.500 integration, synchronization, operational control and
   management.

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

   The Global Directory Server complies with the 1988 CCITT
   Recommendations X.500-X.521 [CCITT-88] and the 1988 NIST OIW Stable
   Implementation Agreements [NIST-88].  It also complies with all
   static and dynamic requirements of X.519.

   The Global Directory Server also provides:

      * Full interoperability with "quipu" implementations including:

         * quipu replication for designated portions of DIT

         * quipu reference model for designated portions of DIT

         * enhanced quipu access controls (ACLs)

         * quipu operational attributes for designated portions of
           DIT

      * Can "automatically" migrate quipu DIT to 1993 DIT:

         * Migration process is dynamic, can occur while DSA is
           operating

         * Process preserves quipu attributes if desired

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

   The Global Directory Server complies with the 1993 ITU-T
   Recommendations X.500-X.521, except for DOP, schema publication, and
   non-specific subordinate references. It also complies with the 1994
   NIST OIW Stable Implementation Agreements. And it complies with all
   static and dynamic requirements of X.519.  Compliance features:

      * 1993 administrative framework

      * 1993 operational attributes

      * 1993 reference structure
ToP   noToC   RFC2116 - Page 95
      * 1993 distributed operations

      * 1993 incremental and full replication including:

         * Supplier or consumer initiated

         * Periodic (by update interval) or onchange replication

         * Complete subtree specification to select replicated area

         * Reference replication

      * 1993 basic access control including:

         * Prescriptive, entry and subentry ACI supported

         * Item first and user first specification

         * All user classes supported including users by subtree
           specification

         * Access control by entry, attribute and attribute value

         * All priority levels supported

      * 1993 collective attributes

      * 1993 hierarchical attributes

      * 1993 operational extensions

      * 1993 modifyDN operation

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   Global Directory Server is compliant with the following RFCs: [RFC
   1274], [RFC 1276], [RFC 1277], [RFC 1567], [RFC 1778], [RFC 1777],
   [RFC 1779]

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   Global Directory Server is compliant with the following RFCs: [RFC
   1202], [RFC 1249], [RFC 1275], [RFC 1278], [RFC 1279], [RFC 1558],
   [RFC 1562], [RFC 1617], [RFC 1781], [RFC 1801], [RFC 1802], [RFC
   1803], [RFC 1836], [RFC 1837], [RFC 1838]
ToP   noToC   RFC2116 - Page 96
INTEROPERABILITY

   Control Data X.500 has successfully interoperated with other X.500
   implementations including those from HP, DEC, ESL, ISODE Consortium,
   Telstra, ICL, Marben (HP), Nexor, Unisys, and Siemens.

PILOT CONNECTIVITY

   Control Data's X,500 implementation interoperates with other
   implementations in the Internet X.500 pilots. It also provides the
   base routing tree for the MHS Use of the Directory pilot (Longbud) on
   the Internet.

BUGS

   Control Data provides complete software maintenance services with
   products.

CAVEATS AND GENERAL LIMITATIONS

   None.

INTERNETWORKING ENVIRONMENT

   [RFC 1006] with TCP/IP, TP4 with CLNS, TP0 with X.25.

HARDWARE PLATFORMS

   Global Directory Server is supported on UNIX for SUN SPARC, HP 9000,
   and IBM RS/6000 platforms, and on Windows NT for Intel platforms.
   Other platforms are pending.

SOFTWARE PLATFORMS

   Distributed and supported for SUN Solaris 2.x, HP-UX 10.x, IBM AIX
   4.x, and Windows NT.

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   Product was introduced in December 1995. 5 implementations in the
   field to date.
ToP   noToC   RFC2116 - Page 97
AVAILABILITY
   Commercially available from:

         Control Data Systems Inc.
         Electronic Commerce Solutions, ARH290
         4201 Lexington Avenue   North
         Arden Hills, MN 55126-6198 U.S.A.

         1-800-257-OPEN (U.S. and Canada)
         1-612-482-6736 (worldwide)
         FAX: 1-612-482-2000 (worldwide)
         EMAIL: info@cdc.com
           or
         s=info p=cdc a=attmail c=us

DATE LAST UPDATED or CHECKED

   July 1996

ADDITIONAL INFORMATION and/or COMMENTS

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

   i500 Enterprise Directory Server

   ICL

ABSTRACT

   ICL's i500 Enterprise Directory Server (simply termed "i500") is a
   high performance X.500 distributed Directory system providing
   features such as:

      * multi-protocol support covering 1993-edition DAP, DSP and
        DISP plus LDAP and WWW client access

      * dynamically configurable schema (object classes, attributes,
        structure rules etc.) including support for user-defined
        schema items and auxiliary object classes

      * a scalable, disk-based database incorporating configurable
        indexing facilities to enable rapid, large-scale searching,
        including approximate matching

      * storage of a variety of information types including text,
        image and sound

      * the capabaility to operate as a "first-level" DSA

      * 1993-edition replication of information (both primary and
        secondary shadowing using DISP and supporting total refresh,
        incremental or on-change updates)

      * information security, using X.509 authentication techniques
        together with either 1993-edition Basic or Simplified Access
        Controls

      * gateway facilities to enable X.500, LDAP and WWW client
        access to non-X.500 based information

      * a variety of APIs and associated development toolkits
        including LDAP and X/Open XDS/XOM Directory access APIs

      * support of the [RFC 1567] "MADMAN" systems management MIB

      * a Windows (3.11, 95 or NT) based management station
ToP   noToC   RFC2116 - Page 99
COMPLIANCE withX.500-1988 (applicable only forDSAs and DUAs)

   i500 is compliant with the 1993-edition of X.500 and interoperates
   with 1988-edition DUAs and DSAs.

COMPLIANCE withX.500-1993 (applicable only forDSAs and DUAs)

   i500 is compliant with the 1993-edition of X.500 and is implemented
   in-line with the ISO/ITU-T Directory Implementor's Guide and the
   emerging 1993 International Standardized Profiles (ISPs) being
   produced by the NIST OIW, EWOS and AOW workshops.

   Full Protocol Implementation Conformance Statements (PICS) are
   available on request to either:

      i500@reston.icl.com or k.richardson@man0523.wins.icl.co.uk

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   i500 supports a variety of proposed Internet standards and in
   particular, [RFC 1274] (schema), [RFC 1567] (MIB) and [RFC 1777]
   (LDAP).

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   i500 is developed in-line with any necessary informational and
   experimental RFCs, e.g.[RFC 1278] and [RFC 1558] are supported.

INTEROPERABILITY

   ICL are members of EuroSInet and EEMA. As such, i500 is regularly
   tested for interoperability at EuroSInet workshops and has also been
   included in public demonstrations of X.500 interoperability at EEMA
   annual exhibitions. Other X.500 products with which i500 has been
   proven to interoperate include those from the following vendors:

   * Boldon-James

   * Control Data

   * DCL

   * Digital

   * ISOCOR

   * ISODE
ToP   noToC   RFC2116 - Page 100
   * Net-Tel

   * NeXor

   * SNI

   * Unisys

   * WorldTalk

PILOT CONNECTIVITY

   i500 operates within the Internet PARADISE network controlled by
   DANTE.

BUGS

   No known bugs. World-wide software maintenance services are provided
   with primary support desks based in North America and Europe.

CAVEATSAND GENERAL LIMITATIONS

   None.

INTERNETWORKING ENVIRONMENT

   TCP/IP for LDAP and WWW client (HTTP) access
   TCP/IP with [RFC 1006]
   OSI TP0, TP2, TP3, (X.25, CONS) and TP4 (CLNP)

HARDWARE PLATFORMS

   HP, Intel PC, ICL, SUN, Pyramid and platforms which support UNIXWARE
   2.0

SOFTWARE PLATFORMS

   HP UX-9.04 and 10.0, Windows NT 3.51, ICL DRS/NX 7, SUN Solaris 2.4
   and 2.5, Pyramid OSx, UNIXWARE 2.0

NUMBER OF IMPLEMENTATIONS IN THE FIELD

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

   i500 is commercially available from ICL High Performance Systems.
   For further information please contact either:

   i500 Marketing Manager,  or   David Longley (i500 Business Manager),
   ICL Inc.,                     ICL,
   11490 Commerce Park Drive,    Wenlock Way,
   Suite 500,                    West Gorton,
   Reston,                       Manchester,
   VA 22091-1532 USA             M12 5DR, UK

   Tel.   +1 703 648 3300        Tel.   +44 (0)161 223 1301 ext.2832
   Fax.   +1 703 648 3350        Fax.   +44 (0)161 223 0482
   I/net. i500@reston.icl.com    I/net.
                                 d.c.longley@man0505.wins.icl.co.uk


   Information on i500 is also provided at
   http://www.icl.com/hps/i500.html.

DATE LAST UPDATED or CHECKED

   July 29, 1996

ADDITIONAL INFORMATION and/or COMMENTS

      None.
ToP   noToC   RFC2116 - Page 102
NAME

   ISODE Consortium Release 3.0 X.500(1993) Directory ISODE Consortium
   Ltd.

ABSTRACT

   This implementation is a source release of an X.500(1993) Directory
   System Agent (DSA). It has been designed an implemented as an X.500
   1993 DSA not as a 1988 DSA with '93 extensions.  Emphasis has been
   placed on providing support for a flexible information model, access
   control, X.509 security features, and standard replication.

   The 1993 DSA offers a strong technical foundation on which to build
   an information and messaging infrastructure that relies on robust and
   scalable directory services. The implementation of this DSA
   incorporates the experience gained through the development, support,
   and maintenance of the earlier QUIPU, as well as operational
   experience and standards support.

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

   The DSA is aligned to the 1988 ISO IS and the NIST OIW Directory
   Implementors Guide Version 1. X.500(1993) features such as
   replication, access control, as well as X.509 certification are also
   available.  Interoperability testing with other DSAs has been
   performed.

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

   Please contact the ISODE Consortium if you wish to obtain our
   protocol information conformance statements. PICS may also be
   available from member organizations for their binary products.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [RFC 1781],[RFC 1779],[RFC 1778],[RFC 1777], [RFC 1274], [RFC 1277].

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [RFC 1838], [RFC 1837], [RFC 1836],[RFC 1801], [RFC 1275], [RFC
   1278], [RFC 1279].
ToP   noToC   RFC2116 - Page 103
INTEROPERABILITY

   Interoperability with several other DSAs has been demonstrated in
   pilot operation and at Eurosinet in October 1995.

   At Eurosinet, X.500 interoperability testing used the X.500 DAP
   (Directory Access) and DSP (Directory System) protocols. Successful
   testing was done between the ISODE Consortium X.500(1993) DSA and
   DSAs from four other vendors including Siemens-Nixdorf and Bull. The
   ISODE Consortium was the only vendor to bring an X.500(93) compliant
   DSA to the workshop for the scheduled X.500(93) testing.

PILOT CONNECTIVITY

   Connectivity to the global research pilots (PARADISE etc.) has been
   demonstrated. It is expected that this system will be used
   extensively in a wide range of pilot activities.  DUA Connectivity,
   and DSA Connectivity.

BUGS

   Bugs should be reported to the ISODE Consortium via email.

CAVEATS AND GENERAL LIMITATIONS

   None

INTERNETWORKING ENVIRONMENT

   The IC R3.0 release is application level code, and assumes vendor
   provided lower layers. It provides the following modules with support
   for a range of APIs to handle associated lower layers:

      * [RFC 1006] (vendor supplied TCP/IP using sockets or TLI)

      * Transport service (vendor supplied transport, which may be
        any class and use any network service. TLI, XTI and various
        vendor-specific APIs).

      * TP0 (Vendor supplied X.25 or CONS using NTI and various
        vendor specific APIs).

HARDWARE PLATFORMS

   Reference platform is SUN SPARC Solaris 2.  The software has been
   ported to various other platforms by the IC and by member
   organizations.  Contact the ISODE Consortium for a complete member
   product list.
ToP   noToC   RFC2116 - Page 104
SOFTWARE PLATFORMS

   Reference OS is Solaris 2.3/2.4. It is also known to run on various
   other UNIX platforms. Contact the ISODE Consortium for a complete
   member product list.

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   Available to members of the ISODE Consortium. Membership is open to
   any organisation. An earlier version of the source release is
   available under licence (zero cost) to universities and equivalent
   educational institutions.

   Contact:

      ISODE Consortium
      The Dome, The Square
      Richmond
      TW9 1DT
      UK

      Phone: +44-181-332-9091
      Fax:   +44-181-332-9019

      Email: <ic-info@isode.com>

DATE LAST UPDATED or CHECKED

   January 1996

ADDITIONAL INFORMATION and/or COMMENTS

   More information may be obtained by contacting the ISODE Consortium,
   or by visiting our WWW site, http://www.isode.com/

   Our X.400 address is s=ic-info; o=ISODE Consortium; p=ISODE;
   a=MAILNET; c=FI


(next page on part 4)

Next Section