tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Glossaries     Architecture     IMS     UICC    |    search

RFC 2116

 
 
 

X.500 Implementations Catalog-96

Part 4 of 5, p. 105 to 129
Prev RFC Part       Next RFC Part

 


prevText      Top      Up      ToC       Page 105 
NAME

   ISOPLEX DS (tm) DSA

   ISOCOR

ABSTRACT

   ISOCOR's ISOPLEX DS Directory Services Product Family also includes:

      ISOPLEX DS Import/Export Utility for Windows
      ISOPLEX DS Navigator
      ISOPLEX DS Directory Access XDS/XOM APIs
      ISOGATE DS (tm) Oracle

   The ISOPLEX DS provides a 1988 X.500 conformant Directory System
   Agent (DSA), a Lightweight Directory Access Protocol (LDAP) daemon to
   service Directory requests via LDAP, a UNIX Directory shell user
   agent (DISH), a Motif Directory Administrator interface to configure
   the first level and subordinate DSAs, and supporting utilities to
   handle bulk loading of the Directory, maintain statistics, and
   provide logging information.

   In addition to supporting memory-based Directory Information Bases
   (DIBs), the ISOPLEX DS includes the optional configuration of
   delegate DSA processes for storing selected subtrees of the Directory
   Information Tree (DIT) in disk-based index and data files.

   The ISOPLEX DS includes a set of utilities integrating it with key
   technology. The most important of these tools is the World Wide Web
   to X.500 gateway, which supports Hyper-Text Markup Language (HTML)-
   based DUA bindings to the ISOPLEX DS DSA via the ISOPLEX DS LDAP
   daemon process.

   The ISOPLEX DS additionally provides Simple Network Management
   Protocol (SNMP) functionality that works in conjunction with an
   existing SNMP environment. The ISOPLEX DS functionality is
   specifically designed to monitor a DSA's DSP and DAP connections from
   a network managment system and uses the X.500 Directory monitoring
   Management Information Base (MIB), which is based on [RFC 1567].

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

   The ISOPLEX DS conforms to the 1988 CCITT Recommendations X.500-X.521
   as detailed in the Protocol Implementation Conformance Statements
   X.581 (1988) and X.582 (1988). It conforms in part to Version 7 of
   the NIST OIW Stable Implementation Agreements.

Top      Up      ToC       Page 106 
COMPLIANCE with X.500-1993 (applicable only for DSAs and DUAs)

   The ISOPLEX DS does not conform to the 1993 ITU-T Recommendations
   X.500-X.521.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   The ISOPLEX DS conforms with the following proposed Internet Standard
   RFCs: [RFC 1274], [RFC 1276], [RFC 1277], [RFC 1567], [RFC 1777],
   [RFC 1778], [RFC 1779], and [RFC 1798].

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   The ISOPLEX DS is consistent with the following informational and
   experimental RFCs: [RFC 1275], [RFC 1278], [RFC 1279], [RFC 1558],
   [RFC-1617], [RFC 1781], [RFC-1801], [RFC-1803], and [RFC-1804].

INTEROPERABILITY

   The ISOPLEX DS interoperates with the following systems: Control
   Data, Digital Equipment, Hewlett Packard, Marben, Nexor, The
   Wollongong Group, and Unisys.

PILOT CONNECTIVITY

   The ISOPLEX DS provides DUA Connectivity and DSA Connectivity via the
   PARADISE project in Europe and via the Internet in North America.

BUGS

   If problems arise with the ISOPLEX DS, the customer can report these
   to the relevant ISOCOR reseller or contact ISOCOR Technical Support
   directly. ISOCOR Technical Support staffs are available in two
   locations: one in the US at +1 (310) 581-8100 (phone), +1 (310) 581-
   8111 (fax), and helpdesk@isocor.com; the other in Ireland at +353 (1)
   284-3802 (phone), +353 (1) 280-0365, and helpdesk.isocor.ie.

CAVEATS AND GENERAL LIMITATIONS

   Not applicable.

INTERNETWORKING ENVIRONMENT

   Though the internetworking capability of the product depends on the
   specific hardware/software platform, the ISOPLEX DS in general
   supports the following environments:

      [RFC 1006] with TCP/IP

Top      Up      ToC       Page 107 
      TP2 over X.25, CONS (ISO 8878), APS on Async

      TP4 over CLNS, PAD (X.29) Server

HARDWARE PLATFORMS

   Hewlett Packard

   Intel 486/Pentium

   Sun

   Stratus

SOFTWARE PLATFORMS

   Hewlett Packard HP-UX v9.x/v10.x, HP OSI Transport Services 9000

   SCO v3.2.4, v3.2.5, SCO OpenDesktop, TCP/IP, IEEE 802.3, Eicon R3.1
   for X.25 networking software and hardware

   Solaris v2.4, Sunlink OSI 8.0.2, Sunlink X.25 8.0.2

   Stratus ftx v2.2, OSI Open Networking Platform (ONP), Stratus Window
   Manager 1.2 End User System, MIT X11R5 Graphics End User System, MIT
   X11R5 Graphics Fonts package, MIT X11R5 Graphics Openlook Software
   package

   Motif/X11R5 runtime support

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   The ISOPLEX DS is commercially available either directly from ISOCOR
   or from a licensed ISOCOR reseller.

DATE LAST UPDATED or CHECKED

   December 31, 1995.

ADDITIONAL INFORMATION and/or COMMENTS

   Not applicable.

Top      Up      ToC       Page 108 
NAME

   LDAP

   University of Michigan

ABSTRACT

   UM-LDAP is an implementation of the Lightweight Directory Access
   Protocol. LDAP is a draft Internet standard directory service
   protocol that runs over TCP/IP. It can be used to provide a stand-
   alone directory service, or to provide lightweight access to the
   X.500 directory.  LDAP is defined by [RFC 1777] and [RFC 1778].

   The UM-LDAP package includes the following components:

      * slapd - a stand-alone LDAP directory server

      * slurpd - a stand-alone LDAP replication server

      * ldapd - an LDAP-to-X.500 gateway server

      * centipede - an LDAP centroid generation and maintenance
        program

      * libldap - an LDAP client library

      * liblber - a lightweight BER/DER encoding/decoding library

      * ldif tools - data conversion tools for use with slapd

      * in.xfingerd - a finger-to-LDAP gateway server

      * go500 - a gopher-to-LDAP gateway server for searching

      * go500gw - a gopher-to-LDAP gateway server for searching and
        browsing

      * rcpt500 - an email-to-LDAP query responder

      * mail500 - an LDAP-capable mailer

      * fax500 - an LDAP-capable mailer that supports remote printing

      * LDAP tools - A collection of shell-based LDAP utility
        programs

Top      Up      ToC       Page 109 
   In addition, there are some contributed components:

      * web500 - an HTTP-to-LDAP gateway

      * whois++d - a WHOIS++-to-LDAP gateway

      * saucer - a simple command-line oriented client program

   The latest information about LDAP can always be found on the LDAP
   Home Page at this URL:

   http://www.umich.edu/~rsug/ldap/

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

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

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

   Since the LDAP protocol itself has not yet been updated to support
   any 1993-specific X.500 features, this implementation does support
   any 1993 features yet either.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   Believed to be compliant with:

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

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   Includes an implementation of the LDAP API, as defined in [RFC 1823].
   Search filters used within UM-LDAP comply with [RFC 1558].

INTEROPERABILITY

   The current implementation of the X.500-backended LDAP server (ldapd)
   is known to work with ISODE-based DAP libraries and the QUIPU DSA.

PILOT CONNECTIVITY

   DUA connectivity should be possible to all pilots.

Top      Up      ToC       Page 110 
BUGS

   Bug reports should be sent to bug-ldap@umich.edu.

CAVEATS AND GENERAL LIMITATIONS

   None, aside from those mentioned above under completeness.

INTERNETWORKING ENVIRONMENT

   LDAP clients use TCP to communicate with the LDAP server.  The LDAP
   server normally uses [RFC 1006] with TCP/IP to communicate with the
   DSA, though any other transport mechanism for DSA communication
   supported by ISODE should be possible.

HARDWARE PLATFORMS

   The complete UM-LDAP package has been ported to a wide variety of
   UNIX systems, including: Sun3 and SPARCs running SunOS 4.1.x or
   Solaris 2.x, DECStations running Ultrix 4.3, HP 9000 series running
   HP-UX 9.05, IBM RS6000 running AIX 3.2.5, PCs running SCO, FreeBSD,
   NetBSD, or LINUX, DEC Alphas running OSF/1, and NeXTStatios running
   NeXTSTEP 3.2.  The complete package has also been ported to VMS.  In
   addition, the LDAP client libraries and some client programs have
   been ported to Apple Macintosh and PCs running MSDOS or Windows.

SOFTWARE PLATFORMS

   The complete UM-LDAP package has been ported to a wide variety of
   UNIX systems, including: SunOS 4.1.x, Solaris 2.x, Ultrix 4.3, HP-UX
   9.05, AIX 3.2.5, SCO, FreeBSD, NetBSD, LINUX, OSF/1, and NeXTSTEP
   3.2.  It has also been ported to VMS.  In addition, the LDAP client
   libraries and some clients have been ported to Macintosh (System 7),
   MSDOS (some TCP/IP stacks), and Microsoft Windows 3.1, 95, and NT.

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   Unknown; used by almost all Internet X.500 sites.

AVAILABILITY

   This software is openly available for all to use.  It may be obtained
   by anonymous FTP from terminator.rs.itd.umich.edu in the /ldap/
   directory (URL: ftp://terminator.rs.itd.umich.edu/ldap/).  The latest
   information about LDAP can always be found on the LDAP Home Page at
   this URL:

      http://www.umich.edu/~rsug/ldap/

Top      Up      ToC       Page 111 
   Send e-mail to ldap-support@umich.edu for additional assistance.

   This software was developed at the University of Michigan by Tim
   Howes with help from Mark Smith, Bryan Beecher, Gordon Good, Steve
   Rothwell, Lance Sloan as well as many others around the Internet. It
   is subject to the following copyright:

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

DATE LAST UPDATED or CHECKED

   December 1995

ADDITIONAL INFORMATION and/or COMMENTS

   [No Information Provided -- Ed.]

Top      Up      ToC       Page 112 
NAME

   maX.500 :: Macintosh DUA Interface

   University of Michigan

ABSTRACT

   maX.500 is a Directory User Agent (client) for Apple Macintosh.  It
   is widely used within Paradise and other Internet X.500 pilots.
   maX.500 supports searching, browsing, and modifying directory
   entries.  Display of textual information, playing of audio, and
   viewing of both black-and-white (fax) and color (JPEG) images are
   supported.  Communication with directory servers is via the
   Lightweight Directory Access Protocol (LDAP) over TCP/IP.  maX.500
   works both with standalone LDAP directory servers (such as slapd) and
   with X.500-backended LDAP servers (such as ldapd).

   maX.500 is a native Macintosh application, and has a friendly
   interface.  It requires System Software version 6.0.5 or later and
   Apple's MacTCP or Open Transport TCP/IP networking. The current
   version of maX.500 is 2.0.2, although version 2.1 is in beta test.

   The latest information about maX.500 can always be found on the
   maX.500 Home Page at this URL:
   http://www.umich.edu/~rsug/ldap/max500/

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

   maX.500 works over LDAP, and is subject to LDAP's limitations.  The
   bind, search, compare, add, delete, abandon, modify, and modifyrdn
   operations are all used by maX.500. Size and time limits may be
   specified, as may alias dereferencing control.

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

   maX.500 currently uses LDAP as defined in [RFC 1777], which does not
   support any 1993-specific X.500 features.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

      Believed to be compliant with:

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

Top      Up      ToC       Page 113 
CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   Search filters comply with [RFC 1558].

   Uses the LDAP API, as defined in [RFC 1823].

INTEROPERABILITY

   maX.500 is known to work with the U-M LDAP servers (ldapd and slapd).
   It has also been tested with other commerical LDAP servers, such as
   Control Data's server.  maX.500 has been used with a wide variety of
   DSAs (always through an LDAP server).

PILOT CONNECTIVITY

   DUA connectivity should be possible to all pilots.

BUGS

   Bug reports should be sent to max500-bugs@umich.edu.

CAVEATS AND GENERAL LIMITATIONS

   maX.500 does not support modification of "photo" (fax), "jpegPhoto",
   or "audio" attributes.  Versions of maX.500 before 2.1 did not
   support a fully functional browse facility.

INTERNETWORKING ENVIRONMENT

   maX.500 is an LDAP client, and as such is uses TCP to communicate
   with the LDAP server.  Apple's MacTCP control panel or Open Transport
   TCP/IP networking is required.

HARDWARE PLATFORMS

   maX.500 runs on Apple Macintosh Plus or later Macintosh computers,
   including PowerMacs. It requires 600K of free RAM.

SOFTWARE PLATFORMS

   maX.500 requires Apple System Software 6.0.5 or later (System 7
   preferred) and MacTCP 1.1 or later (2.0.6 preferred).  maX.500 2.1,
   which is currently in beta test, will run natively on the PowerMac
   and use the native Open Transport networking interface if it is
   installed.

Top      Up      ToC       Page 114 
NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   This software is openly available for all to use.  It may be obtained
   by anonymous FTP from terminator.rs.itd.umich.edu in the /ldap/max500
   directory (URL: ftp://terminator.rs.itd.umich.edu/ldap/max500).  The
   latest information about maX.500 can always be found on the maX.500
   Home Page at this URL:

      http://www.umich.edu/~rsug/ldap/max500/

   Send e-mail to max500@umich.edu for additional assistance.

   This software was developed at the University of Michigan by Mark
   Smith with help from Tim Howes and many others around the Internet.
   It is subject to the following copyright:

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

DATE LAST UPDATED or CHECKED

   December 1995

ADDITIONAL INFORMATION and/or COMMENTS

   [No Information Provided -- Ed.]

Top      Up      ToC       Page 115 
NAME

   Messageware DSA

   NEXOR

ABSTRACT

   Messageware DSA is a high performance X.500(93) DSA. Characteristics
   of the DSA are:

      * DAP access

      * DISP for replication and shadowing information

      * DSP access

      * LDAP

      * Full 1993 Basic and Simple Access Control

      * Support for X.400, X.500, and [RFC 1274] attributes and
        object classes

      * Approximate match based on Soundex.

      * Flexible schema management

      * Anti-trawling access  control

      * Knowledge management mapped onto DIT

      * Attribute inheritance

      * Remote management

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

   Messageware DSA is an X.500 1993 compliant DSA

   XT-QUIPU is a X.500 1988 compliant DSA conforming to NIST SIA version
   2.

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

   Messageware DSA isn X.500 1993 compliant DSA implementing standard
   access control, replication and shadowing, X.509, for a full
   conformance statement see the NEXOR web site(http://www.nexor.com).

Top      Up      ToC       Page 116 
CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   The following are supported: String DN format [RFC 1485], [RFC 1274],
   [RFC 1276], and [RFC 1277].

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   The following are supported: UFN [RFC 1781], [RFC 1278], and [RFC
   1279].

INTEROPERABILITY

   Messagware DSA has been extensively interoperability tested at
   Eurosinet workshops and at the EEMA X.500 demonstration.  Other
   vendors DSAs/DUAs interoperated with include:

   ICL, Control Data, Unisys, Digital, Isocor, DCL, SNI, Boldon James

   It is also in operation with DSAs used in the PARADISE and other
   pilot projects.

PILOT CONNECTIVITY

   Messageware DSA is fully connected to the PARADISE and PSI White
   Pages X.500 Pilots.

BUGS

   No known bugs.  Support is given via phone or email to
   "support@nexor.co.uk"

CAVEATS AND GENERAL LIMITATIONS

   None.

INTERNETWORKING ENVIRONMENT

   OSI TP4 wtih CLNP
   OSI TP0 with X.25 or CONS
   [RFC 1006] with TCP/IP

HARDWARE PLATFORMS

      Sun: SunOS
           Solaris
           X86
      IBM RS/6000: AIX
      HP 9000

Top      Up      ToC       Page 117 
   It is available on a number of other UNIX platforms

SOFTWARE PLATFORMS

   SunOs 4.1.3 Solaris 2.4     AIX 3.2 DRS/NX 6000 HP-UX 9.01

   Other software platforms are    available.

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   Messageware DSA is available from NEXOR and NEXOR partners. For more
   details contact:

      NEXOR
      PO Box 132
      Nottingham
      NG7 2UU
      UK

      DN:        c=GB@o=NEXOR Ltd
      Telephone: +44 115 952 0510
      Fax:       +44 115 952 0519
      E-Mail:    info@nexor.co.uk

DATE LAST UPDATED or CHECKED

   Dec 95

ADDITIONAL INFORMATION and/or COMMENTS

      [No Information Provided--Ed.]

Top      Up      ToC       Page 118 
NAME

   MESSAGEWARE PC-DUA

   NEXOR

ABSTRACT

   PC-DUA provides a MS Windows based user interface to the X.500
   Directory.

      Features include:

      o Modify - allows users and administrators alike to add, change or
        delete directory entries

      o Searching - powerful searching tool so specific information can
        be quickly located. Also lists close matches

      o Highly flexible - can be customised to suit an organisations
        particular requirements

      o Directory Browser - to enable user to identify directory entries

      o History - allowing quick access to previously referenced parts
        of the DIT.

      o User Friendly Name (UFN) based searching

      o Hypertext-like navigation.

      o Friendly names for attribute labels.

      o Intelligent choice of entries to display when moving to a new
        location in the DIT.

      o On-line hypertext help.

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

   Compliant with LDAP 3.

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

   Compliant with 1993 versions of ITU X.500/ISO 9594 services and
   protocols

Top      Up      ToC       Page 119 
CONFORMANCE WITH PROPOSED INTERNET STANDARDS

      The following are supported:    [RFC 1006]
                                      [RFC 1202]
                                      [RFC 1274]
                                      [RFC 1277]
                                      [RFC 1777]

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [No information provided--Ed.]

INTEROPERABILITY

   PC-DUA has interoperated with LDAP 2.0 and 3.0 distributions.

   Eurosinet Workshop:

      SNI, CDS, AT&T, ICL, Digital, ISOCOR, UNISYS and QUIPU.

PILOT CONNECTIVITY

   Full DUA connectivity to the NADF, PARADISE and PSI White Pages X.500
   Pilots.

BUGS

   No known bugs.  Support is given via phone or email to
   "support@nexor.co.uk"

CAVEATS AND GENERAL LIMITATIONS

   None.

INTERNETWORKING ENVIRONMENT

   WinSock based TCP/IP stacks

HARDWARE PLATFORMS

   386 PC or greater WITH 4MGBYTES RAM

SOFTWARE PLATFORMS

   MS WINDOWS 3.1
   Windows NT
   Windows95

Top      Up      ToC       Page 120 
NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   PC-DUA is commercial software.  For more details contact:

      NEXOR
      PO Box 132
      Nottingham
      NG7 2UU
      UK

      DN: c=GB@o=NEXOR Ltd
      Telephone: +44 (0) 115 952 0510
      Fax:  +44 (0) 115 952 0519
      E-Mail:  info@nexor.co.uk

DATE LAST UPDATED or CHECKED

   Dec 95

ADDITIONAL INFORMATION and/or COMMENTS

   [No Information Provided--Ed.]

Top      Up      ToC       Page 121 
NAME

   NonStop Directory Services (NSDS)
   Tandem Computers, Inc.

ABSTRACT

   The Tandem NonStop Directory Services (NSDS) product provides a
   distributed open directory service on Tandem platforms.  It is an
   industrial strength implementation incorporating the Tandem product
   fundementals of resilience, linear extensibility, fault-tolerance, and
   continuous availability. NSDS runs on the NonStop Kernel Guardian
   Personality which includes support for Tandem system characteristics
   such as data integrity, process persistence, and server classes.  NSDS
   supports access over X.25 WAN, LAN and TCP/IP networks.

   NSDS is a port of OSF's DCE GDS Reference Implementation, with Tandem
   enhancements including 1993 X.500 Simplified Access Control. Tandem
   server class management provides fault events, tracing, accounting and
   configuration services for NSDS. TM/MP (Transaction Management) is
   used to protect all file operations that affect the integrity of the
   directory entries in the DIB.

   Major Features Include:

      * X/Open Directory Services (XDS) API and X/Open Object
        Management (XOM) interface in conformance with X/Open CAE
        Specifications, and an additional Tandem extension package

      * 1988 Edition X.500 Conformant DAP and DSP, capable of inter-
        operating with 1993 Edition DUA or DSA implementations

      * Simplified Access Control as specified in the 1993 edition of
        the X.500 standard.

      * Unprotected Simple Authentication (name and password in
        clear)

      * Character set support for T61 Printables, IA5 and Teletex
        Strings

      * The DSA-SC server class performs the functions of a DSA.
        Multiple processes are used for fault tolerance and load
        balancing.

      * The DUA-ACCESS server class handles communications between
        local applications and remote DSA's using DAP across an OSI
        stack.

Top      Up      ToC       Page 122 
      * The DSA-ACCESS server class handles communications from
        remote DUAs or DSAs to the DSA-SC server class using the
        Tandem OSI stack implementation which includes [RFC 1006]
        support for TCP/IP networks.

      * The DSA-CHAIN server class handles chaining communications
        between the DSA-SC server class and remote DSAs.

      * NSDS GUI Viewer supports administration/management of an NSDS
        DIB on a PC Windows workstation.  The NSDS GUI Viewer is
        supported by a persistent server process on the Tandem
        NonStop Kernel.  The  GUI Viewer allows a directory entry and
        a complete set of attributes and values to be inserted
        anywhere in the directory tree (DIT), to be deleted or
        changed, read or searched based on distinguished name
        components, with or without wild-card.

      * NSDS SCRIPTOR allows customers to explore features of the XDS
        programmatic interface in advance of writing their XOM/XDS
        application. NSDS SCRIPTOR is a menu-driven batch interface
        to XDS functions.

      * A BulkUnload/BulkLoad utility allows a branch of the DIB to
        be dumped to an editable flat file and restored from that
        file.  The flat file can be modified before being bulk-loaded
        into a DIB which may conform to a different schema
        definition.

      * Support for the LDAP protocol.

      * Messaging-Based Directory Query (MDQ) provides a text-based
        query interface to the directory from an X.400 messaging
        system, such as Tandem OSI/MHS, via the XAPIA compliant GPI
        interface.

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

   NSDS complies with the '88 CCITT X.500 and ISO 9594 standard, and
   part of '93 X.500 standard.

   NSDS DSA and DUA are compliant with OIW Agreements, with the
   following features yet to be implemented:

      * Strong Authentication               (Sections 6.6.2 and 8.4e)

      * Priority Service Control            (Section 7.4)

Top      Up      ToC       Page 123 
      * Digital Signature, Replication and Shadowing  (Sections 8.8-
        8.12)

      * Authentication                      (Sections 9.1.7 and 14.1-
        14.2)

      * Directory Trace Information         (Section 9.2.2)

      * Abandon and ROSE operation class 2  (Section 10.1)

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

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

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

      * Chaining is supported.

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

      * All attribute types defined in ISO/IEC 9594-6:1993 are supported
        except for collective attributes and enhancedSearchGuide.
        Customer defined attributes can also be added. UNIVERSAL STRING
        is not supported.

      * All object classes defined in ISO/IEC 9594-7:1993 are supported.
        Customer defined object classes can be also be added.

      * Name forms defined in ISO/IEC 9594-7:1993 are all supported.
        Customer defined name forms can also be added.

      * Simplified Access Control is supported.

      * Support for collective attributes is not provided.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [RFC 1277], [RFC 1777], [RFC 1779], [RFC 1778]

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [RFC 1279]

Top      Up      ToC       Page 124 
INTEROPERABILITY

   NSDS DSAs interoperate with various 1988 X.500 and 1993 X.500
   conformant DUAs with unrecognized features of the incoming 1993-based
   request ignored.

PILOT CONNECTIVITY None at the present time.

BUGS

   Information is provided with the production installation guide.

CAVEATS AND GENERAL LIMITATIONS

   The OSF/DCE "GDS Extension Package" is not supported by NSDS. A
   Tandem "NDS Extension Package" is provided to support 1993 Simplified
   Access Control.

INTERNETWORKING ENVIRONMENT

   The underlying protocols carrying DAP and DSP protocols are provided
   by OSI higher layer stack over X.25, LAN and/or TCP/IP via [RFC-
   1006].

HARDWARE PLATFORMS

   Tandem NonStop Himalaya Systems

SOFTWARE PLATFORMS

   D30.02 NonStop Kernel.  The operator's GUI runs under Microsoft
   Windows 3.1 or later.

NUMBER OF IMPLEMENTATIONS IN THE FIELD

   [No information provided. -- Ed.]

AVAILABILITY

   The NSDS Rev 1.0 production version has been available since October
   1995.

Top      Up      ToC       Page 125 
   For more details, please contact:

      Don S. Jones
      NSDS Product Manager
      Phone: (408) 285-6480
      Fax:   (408) 285-6004
      e-mail: JONES_S_DON@TANDEM.COM

DATE LAST UPDATE or CHECKED

   July 1996.

ADDITIONAL INFORMATION and/or COMMENTS

   None.

Top      Up      ToC       Page 126 
NAME

   ORG.D (tm) V2.0 / V2.1

   Siemens Nixdorf Informationssysteme AG

ABSTRACT

   ORG.D V2.0 is Siemens Nixdorf's administrative directory client
   product. Through its file manager like user interface retrieval and
   DIT administration operations are supported. ORG.D offers a DDE
   interface and with ORG.D V2.1 additionally OLE / OCX / MAPI interfaces
   are supported.  ORG.D V2.1 is an MS-Windows application acting as an
   LDAP client.

   Among others, ORG.D has the following features:

      * Comprehensive, simple-to-use search and positioning options

      * complex searches, including approximate search

      * Several databases visible at the same time in an interface

      * Private address books: available on every desktop

      * Optional use of distribution lists and private address book

      * Support for MS-Word mail merge by means of special export
        format

      * adaptable print listings and comfortable list&label
        functionality

      * customizing tool in order to adapt to any directory schema

      * Configurable user interface

      * Automatic unbind after idle time

      * Anonymous and simple unprotected bind

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

      * Central administration of distribution lists/groups

      * "Domain administrators" with limited rights defined only for
        home site/department

Top      Up      ToC       Page 127 
      * Direct modification / creation of DIT entries from the user
        interface

      * Choice of a proposal list when new employee data is added

   Tight integration in SNI4s X.400/SMTP-MIME mail service and CIT
   products

      * DDE connection and drag&drop data transfer to SNI's X.400
        user agent MAIL.D and SNI4s CIT product ComfoPhone

      * Setting up and administering mailboxes on remote mailbox
        servers

      * Central administration of server addresses and logon data

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

   ORG.D V2.1 is an LDAP client.

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

   ORG.D V2.1 is an LDAP client.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   ORG.D V2.1 is compliant with the following RFCs: [RFC 1777], [RFC
   1778], [RFC 1779].

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

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

INTEROPERABILITY

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

PILOT CONNECTIVITY

   In future ORG.D will be used to browse in the European NameFLOW-
   PARADISE pilot network. Currently SNI's directory client product DIR.D
   V2.6 is used to browse in the European NameFLOW-PARADISE pilot
   network.

Top      Up      ToC       Page 128 
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

   [No information provided. -- Ed.]

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

   Field testing is to be started in Spring 1996.

AVAILABILITY

   ORG.D V2.0 / V2.1 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

Top      Up      ToC       Page 129 
DATE LAST UPDATED or CHECKED

   April 1996

ADDITIONAL INFORMATION and/or COMMENTS

   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
   DIR.X-SYNC V2.0     Directory synchronization


Next RFC Part