tech-invite   World Map     

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

RFC 1632

 
 
 

A Revised Catalog of Available X.500 Implementations

Part 3 of 3, p. 60 to 94
Prev RFC Part

 


prevText      Top       Page 60 
AVAILABILITY

   PathWay Messaging is commercially available from:

        The Wollongong Group, Inc.
        1129 San Antonio Road
        Palo Alto, CA 94303 USA

        Sales and Information: (415) 962 7100
        FAX: (415) 969-5547

DATE LAST UPDATED or CHECKED

   July 27th, 1993

Top       Page 61 
NAME

   PC-DUA
   NEXOR


KEYWORDS

   386, Commercially Available, DUA Connectivity, DUA Interface, IBM PC,
   LDAP, RFC-1487

ABSTRACT

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

   Features include:

   - Searching
   - Directory Browser - to enable user to identify directory entry
   - History - allowing quick access to previously referenced parts
     of the DIT.
   - User Friendly Name (UFN) based searching
   - Hypertext-like navigation.
   - Friendly names for attribute labels.
   - Intelligent choice of entries to display when moving to a new
     location in the DIT.
   - O-line hypertext help.


COMPLIANCE (applicable only for DSAs and DUAs)

   Compliant with LDAP.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   The following are supported: RFC 1487

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [No information provided--Ed.]

INTEROPERABILITY

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

Top       Page 62 
PILOT CONNECTIVITY

   Full DUA connectivity 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

   WinSock based TCP/IP stacks

HARDWARE PLATFORMS

   386 PC WITH 4MGBYTES RAM

SOFTWARE PLATFORMS

   MS WINDOWS 3.1

AVAILABILITY

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

        NEXOR
        8 Faraday Building
        Highfields Science Park
        Nottingham
        NG7 2QP
        UK

        DN:             c=GB@o=NEXOR Ltd
        Telephone:      +44 602 520500
        Fax:            +44 602 520519
        E-Mail:         sales@nexor.co.uk


DATE LAST UPDATED or CHECKED

   August 6th, 1993

Top       Page 63 
NAME

   PC-Pages
   Brunel University, UK


KEYWORDS

   DUA Connectivity, DUA Only, IBM PC, LDAP, Limited Availability,
   Multiple Vendor Platforms, OSI Transport, RFC-1006

ABSTRACT

   PC-Pages is a MS-DOS based X.500 DUA interface. It is currently only
   available for MS-Windows; a DOS character mode interface is being
   prepared.

   Features include:

   - "Form" based searching.
   - Supports the User Friendly Name (UFN) specification (RFC 1484).
   - Powerful query engine.
   - Tailorable entry display - display only those attributes required.
   - Integrates with the WhiteMail X.400 user agent. Hooks are provided
     to allow integration with other user agents.
   - Directory browsing.
   - Support for JPEG photo attributes.
   - Modify directory entries.
   - Add directory entries.
   - Delete directory entries.
   - Rebind to a configured DSA.
   - Some support for configuration of DAP service parameters.


   Two versions of PC-Pages are currently available. One supports DAP
   over CONS or DAP over RFC-1006, and has data entry and modification
   facilities.  The other supports LDAP and has a more advanced user
   interface including a tree-browser, but does not yet have data entry
   and modification.

   A version in the form or a Windows DLL (Dynamic Link Library) is
   being prepared, for incorporation into other products such as mail
   agents.

COMPLIANCE (applicable only for DSAs and DUAs)

   88 Standard compliant: Strong authentication not yet implemented.  No
   plans for support of the 1992 Standard.

Top       Page 64 
CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [No information provided--Ed.]

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [No information provided--Ed.]

INTEROPERABILITY

   Tested with Quipu 8.0.

PILOT CONNECTIVITY

   DUA Connectivity: The interface is in use in the UK Academic
   Directory Pilot.

BUGS

   Bugs should be reported to x500@brunel.ac.uk.

CAVEATS and GENERAL LIMITATIONS

   Does not support display or modification of all known attribute
   syntaxes. In particular: ACLs and O/R addresses.

INTERNETWORKING ENVIRONMENT

   RFC1006 with TCP/IP. TP4 with CONS. A NetBIOS gateway to the
   previously listed protocols. LDAP using Winsock.

HARDWARE PLATFORMS

   PC-Pages for Windows requires an IBM PC compatible with 286 or
   higher, 2mb+ memory.

SOFTWARE PLATFORMS

   Windows 3.0 or 3.1 running in Standard or Enhanced mode.  WhiteStack
   1.1, provided by the Edinburgh University Computing Service.

AVAILABILITY

   Free to UK Academic Community, and to some other communities subject
   to certain restrictions. Commercial derivatives exist.  Please send
   queries to:

Top       Page 65 
   Postal:
        Andrew Findlay
        Computing and Media Services
        Brunel University
        Cleveland Road
        Uxbridge, Middlesex
        UB8 3PH
        UK

   E-mail: x500@brunel.ac.uk.

   Fax: +44 895 32806 (Andrew Findlay)

   Telephone: +44 895 203066 (Andrew Findlay)

DATE LAST UPDATED or CHECKED

   March 10th, 1994

Top       Page 66 
NAME

   QuickMail/X.500 Interface (DUA Interface)
   NASA


KEYWORDS

   DUA Interface, Limited Availability, Needs ISODE, RFC-1274, Sun

ABSTRACT

   The NASA QuickMail/X.500 Interface program is a program which
   translates QuickMail name service requests into X.500 requests and
   returns the results from the DSA to the QuickMail user.  This system
   allows QuickMail users  the ability to find non-QuickMail users' or
   non-local QuickMail users' addresses, while retaining the normal
   QuickMail lookup interface.  The program speaks QuickMail name
   service protocol on one side, and DAP on the other.

COMPLIANCE (applicable only for DSAs and DUAs)

   [Same as dish] -- does not support strong authentication.  No support
   for 1992 extensions needed.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   RFC 1274 supported to the extent that we use provided schema to store
   QuickMail addresses.

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [No information provided--Ed.]

INTEROPERABILITY

   Works with Quipu (ISODE 8.0, ICR1)

PILOT CONNECTIVITY

   Connected to PSI WPPP, PARADISE.  Other projects may use data if they
   are connected to either of these DSAs.

BUGS

   No known bugs.  Default QuickMail name service lookup time out of 10
   seconds may be too fast for some DSAs to respond to.

Top       Page 67 
CAVEATS and GENERAL LIMITATIONS

   Requires the Columbia AppleTalk Package (CAP 6.0) to work.

INTERNETWORKING ENVIRONMENT

   EtherTalk or IPTalk on the Macintosh side, any ISODE supported
   environment on the X.500 side.

HARDWARE PLATFORMS

   Known to run on Sun 4/470

SOFTWARE PLATFORMS

   SunOS 4.1.1 and 4.1.3 can be used to host the package.  Additionally
   may need SunLink OSI 7.0.1, Sunlink X.25 7.0.  ISODE 8.0 or ISODE
   Consortium Release 1 needed to provide DAP support.

AVAILABILITY

   Limited availability.  For more details contact,
      Peter Yee
      MS 233-18
      NASA Ames Research Center
      Moffett Field, CA 94035-1000
      (415) 604-3812
      (415) 604-6999 (FAX)
      yee@atlas.arc.nasa.gov

DATE LAST UPDATED or CHECKED

   February 18th, 1993

Top       Page 68 
NAME

   QUIPU (ISODE Consortium Release 1.0)
   ISODE Consortium


KEYWORDS

   API, DSA Connectivity, DSA/DUA, DUA Connectivity, Free, Multiple
   Vendor Platforms, OSI Transport, RFC-1006, RFC-1274, RFC-1275, RFC-
   1276, RFC-1277, RFC-1278, RFC-1279, RFC-1484, RFC-1485, RFC-1487,
   Source, Sun, UNIX, X.25

ABSTRACT

   This implementation is a source release derived from the earlier
   openly available version of QUIPU, and will be used as base
   technology for products by a number of vendors. The release comprises
   of a DSA, and a number of sample DUAs which may be used in
   conjunction with the DSA.

COMPLIANCE (applicable only for DSAs and DUAs)

   The DSA is aligned to the 1988 ISO IS and the NIST OIW Directory
   Implementors Guide Version 1, with the following exceptions:

   - Strong authentication is not implemented (but hooks are
     provided for use with two packages).
   - QUIPU does not enforce the bounds constraints on attributes,
     filters or APDU size.
   - T.61 string formatting characters are not rejected.
   - If a DN is supplied with no password in an unprotected simple bind,
     QUIPU does not always check to see if the DN exists. If the DSA
     connected to can say authoritatively the DN does not exist, the
     association is rejected. However, if a chain operation is required
     to check the DN, the bind IS allowed.
   - When comparing attributes of UTCtime syntax, if the seconds field
     is omitted, QUIPU does not perform the match correctly (i.e., the
     seconds field in the attribute values should be ignored, but are
     not).
   - QUIPU always supplies the optional Chaining argument
     "originator" even if the CommonArgument "requestor" is used.
   - QUIPU always supplies the optional Chaining argument "target"
     even if the base object in the DAP arguments is the same.
   - The object class "without an assigned object identifier" is
     not recognised unless the "alias" object class is also present.
   - Non Specific Subordinate References are never followed by a QUIPU
     DSA, but they are passed on correctly to the client if generated.

Top       Page 69 
   Compliance with X.500(1993) standards is planned. DAP and replication
   (DISP) will be available in March 1994. Other 1993 features, with the
   exception of DOB, but including security features will be available.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   [RFC 1485], [RFC 1487], [RFC 1274], [RFC 1276], [RFC 1277].

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   [RFC 1484], [RFC 1275], [RFC 1278], [RFC 1279].

INTEROPERABILITY

   Interoperability with several other DSAs has been demonstrated in
   pilot operation and at the COS X.500 Interoperability Lab, enhancing
   interoperability results from the earler versions of QUIPU.

PILOT CONNECTIVITY

   Connectivity to the global research pilot (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 <bug-quipu@isode.com>

CAVEATS and GENERAL LIMITATIONS

   None

INTERNETWORKING ENVIRONMENT

   The IC R1.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).

Top       Page 70 
HARDWARE PLATFORMS

   Reference platform is SUN SPARC.

SOFTWARE PLATFORMS

   Reference OS is SUNOS 4.1.3. It is also known to run on various other
   UNIX platforms.

AVAILABILITY

   Available to members of the ISODE Consortium. Membership is open to
   any organisation. Also available under licence (zero cost) to all
   non-commercial research organisations. Contact:

        ISODE Consortium
        Headquarters
        PO Box 505
        London
        SW11 1DX
        UK

        Phone: +44-71-223-4062
        Fax:   +44-71-223-3846

        Email:  <ic-info@isode.com>


DATE LAST UPDATED or CHECKED

   August 11th, 1993

Top       Page 71 
NAME

   Traxis Enterprise Directory
   Angeli Systems Corporation


KEYWORDS

   API, CLNS, Commercially Available, DSA/DUA, HP, IBM PC, IBM RISC,
   Macintosh, OSI Transport, RFC-1006, RFC-1274, Sun, X.25

ABSTRACT

   The Traxis Enterprise Directory has multiple components in a three
   layer architecture. The individual components of the Traxis family
   are building blocks which can be assembled in a flexible, modular way
   to build complex systems.

   At the enterprise level, is a distributed directory stored and
   managed by Traxis Directory Engines (TDEs). At the workgroup level
   Traxis Directory Hubs (TDHs) provide the means to integrate and
   connect Traxis Directory Engines to the wide variety of real world
   applications and systems which prevail in network environments. The
   TDE and the TDH support the myriad of client applications, including
   messaging and business applications, which require services from the
   Traxis directory.

   At the desktop level, the Traxis Desktop Client (TDC) provides a
   common set of facilities which simplify and enable communications,
   object manipulation, and results management as required between the
   Traxis Directory Hub and applications. These capabilities, which
   include full access and management of the directory, are provided to
   applications through XDS++, the Traxis object oriented API. The
   Traxis Desktop Client also supports industry standard client software
   interfaces such as Microsoft MAPI, Apple OCE, CMC and VIM, through
   Compatibility Modules which map the standard API into XDS++. Through
   these APIs the Traxis Desktop Client supports applications of all
   kinds on PC, Macintosh, and UNIX systems.

   Angeli supplied Traxis applications include the Traxis Administrative
   Console management station, the Traxis Global Browser general
   directory tool, the Traxis Operator Assistance high-speed look-up,
   the Traxis Data Base Gateway, the Traxis Import Export Utility and
   more.

   The Traxis Directory Engine includes an X.500 DSA. The Traxis
   Directory Hub includes an X.500 DUA.

Top       Page 72 
COMPLIANCE (applicable only for DSAs and DUAs)

   Traxis Directory Engine DSA is CCITT-1988 compliant with extended
   security and access control. Supports access control on User, Entry,
   and Attribute levels. DIB or subtree administrative manager
   supported. Supports simple authentication with encrypted password.

   NIST OIW Stable Implementation Agreements [NIST-88] compliant.

   Support for February 14, 1993 CCITT X.500 planned. X.509 in first
   half of 1994. Replication and Administrative/Information Model in
   second half of 1994.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   Traxis conforms to RFC1274 which documents COSINE interoperability.

   LDAP (RFC 1487) is planned for inclusion in a later release of Traxis
   if market demand requires it.

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   Traxis does not conform to the QUIPU RFC Internet Proposals cited.
   As noted elsewhere, Traxis is fully compatible with QUIPU
   operationally but does not use the cited RFCs in its internal
   operations.

INTEROPERABILITY

   Traxis has been extensively tested for interoperability with ISODE
   QUIPU Version 8. Traxis Directory Engine (DSA) will serve DISH or
   other QUIPU DUAs using DAP. Traxis Directory Hub interoperates with
   QUIPU DSA. All directory access functions and their chained
   equivalents are interoperable.

PILOT CONNECTIVITY

   PARADISE DUA/DSA connectivity tested.

BUGS

   Problems may be reported to support@angeli.com.

CAVEATS and GENERAL LIMITATIONS

   None.

Top       Page 73 
INTERNETWORKING ENVIRONMENT

   Traxis Directory Hub to Traxis Directory Engine (or any DSA)
   communication via RFC1006 over TCP/IP, OSI TP4 with CLNS, and OSI TP0
   with X.25. Traxis Desktop Client to Traxis Directory Hub via SPX/IPX
   or TCP/IP. Other LAN protocols supported in 1994.

HARDWARE PLATFORMS

   Traxis Directory Hub and Traxis Directory Engine:
     Sun and PC currently supported. IBM RS/6000, HP 9000, and others in
     1994.
   Traxis Desktop Client and applications:
     PC currently supported; Macintosh in 1994.

SOFTWARE PLATFORMS

   Traxis Directory Hub and Traxis Directory Engine:
     All Sun platforms with Sun OS 4.1.3 currently supported, Solaris
     2.x in 1994. Industry standard PC platforms with SCO Open Desktop
     V3 currently supported.  Other UNIX platforms in 1994. Windows NT
     in 1994.
   Traxis Desktop Client and applications:
     PC with Windows 3.1 currently supported. Macintosh Systems 6 and 7,
     UNIX Motif, DOS, X Windows, and others planned for 1994.

AVAILABILITY

   The Traxis Enterprise Directory is commercially available from:

      Angeli Systems Corporation
      1659 Eleventh Street
      Santa Monica, CA 90404
      +1 310 392 3000
      +1 310 392 4700 FAX

      info@angeli.com

DATE LAST UPDATED or CHECKED

   November 23rd, 1993

Top       Page 74 
NAME

   UCOM.X 500 (tm) - E3.X [DSA and DUA]


KEYWORDS

   386, API, Bull, CLNS, Commercially Available, DEC ULTRIX, DSA
   Connectivity, DSA/DUA, DUA Connectivity, IBM RISC, Motif, Multiple
   Vendor Platforms, OpenLook, RFC-1006, RFC-1274, RFC-1277, RFC-1278,
   RFC-1279, Sequent, Sun, Tandem, UNIX, X.25

ABSTRACT

   UCOM.X 500 includes a Directory System Agent (DSA), various directory
   access APIs and Directory User Agents (DUAs). UCOM.X 500 is a product
   based on PIZARRO, the research prototype developed at INRIA by
   Christian Huitema's team, and commercialized by TS-E3X, 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.
   - 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
     UCOM.X specific attributes of the DSA entries.
   - 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 are being tested operationally through TS-E3X's
     participation in PASSWORD, a VALUE project with aim to pilot a
     European security infrastructure for network applications.
   - Access control: private mechanisms are provided to allow access
     control lists to be specified for parts of the DIT, to control
     modifications, and to specify access restrictions on attributes.
   - Management: a UCOM.X DSA object has been defined to allow
     operational parameters of the DSA to be managed via DAP.
     Administration utilities are provided to, e.g., generate usage
     statistics and periodically update the database from various data
     sources including a knowledge discovery tool.


   The product offers a C language API conformant to X/Open's X/DS

Top       Page 75 
   specification, and a C++ API (for release 10/93).

   The DUAs include a graphical directory browser with powerful search
   functionality for OpenLook and Motif, and a full-screen curses-based
   interface with full DAP functionality.

   TS-E3X's strategy for UCOM.X500 is three-fold: Firstly, to use it as
   the directory service for Spheris, France Telecom's range of
   electronic mail products based on X.400 (88) (release mid '94).
   Secondly, to offer it to third parties developing specific
   applications using X.500: current applications include a distributed
   application to control document transfer in a large French hospital
   and distributed applications management in the French Post Office;
   planned uses include office applications for control of document
   circulation (workflow) and cooperative document editing. Thirdly, to
   offer it to telecomms operators such as France Telecom for
   application in network management. UCOM.X 500 is used extensively by
   French research centers involved in PARADISE.

COMPLIANCE (applicable only for DSAs and DUAs)

   UCOM.X 500 conforms to X.500 (88) as specified in paragraph 9 of
   X.519.

   Development of the product based on X.500 (93) is planned for '94
   with release of a product conformant to the principal extensions at
   the end of '94. Emphasis is being placed on the shadowing protocol,
   the schema and access control.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   The COSINE and Internet Schema (RFC 1274) is supported with minor
   exceptions.

   The string representation of PSAPs and their internal encoding
   conforms to RFC 1277.

   The string representation of DNs will migrate to the Internet RFC
   1485 definition.

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   RFC 1279 (X.500 and Domains) is supported. The string representation
   of PSAPs and their internal encoding conforms to RFC 1278.

   AFRO (algorithme francais de recherche optimise), the search / name
   resolution algorithm proposed by UCOM.X 500, differs from the UFN
   algorithm principally in that it attempts to optimize by performing

Top       Page 76 
   read operations before resorting to searches in order to exploit the
   name error information.

INTEROPERABILITY

   Through UCOM.X 500's use in the French PARADISE pilot,
   interoperability has been informally but extensively tested with
   Quipu and other implementations.

   Detailed interoperability tests  with Quipu, Marben and  Siemens/Bull
   DIR/X are being conducted by  the PARADISE OIFP (Operational
   Interworking) team at INRIA Rocquencourt, France.

   The product  is currently also undergoing  formal tests for
   conformance to the CTS2  DSA/DAP and  ACSE/Presentation/Session
   specifications  at the  French OSI conformance test centre.


PILOT CONNECTIVITY

   DSA and DUA connectivity to the PARADISE pilot.

BUGS

   UCOM.X 500 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 1 kb per node,
   i.e., 10 Mb for a database of 10,000 objects. The current recommended
   maximum is a database size of the order of 100,000 objects.

   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.

   The X/DS API supports the Basic Directory Contents (BDCP), the MHS
   Directory User (MDUP) and the Strong Authentication (SAP) packages
   with minor limitations. A proprietary mechanism for defining new
   classes and attributes is offered. Asynchronous operations and
   multiple concurrent sessions are not supported. Whilst referral may
   be handled automatically, continuation references are not.

Top       Page 77 
INTERNETWORKING ENVIRONMENT

   UCOM.X 500 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.

HARDWARE PLATFORMS

   UCOM.X 500 can easily be ported to any UNIX machine. It currently
   runs on: Sun 3 and 4, IBM RS 6000, DEC ULTRIX (Vax and Mips), 386-
   based PCs, Bull DPX/2 and DPX/20, Sequent, Tandem and others.

SOFTWARE PLATFORMS

   UCOM.X 500 is portable to any UNIX-like operating system. It has been
   ported to: UNIX SVR3 and SVR4, SUN OS 4, AIX, SCO Unix, Interactive
   Unix, ULTRIX, HP-UX, Dynix (Sequent), BOS (Bull) and others.

   Ports to the following are planned: OS/2 ('94), Windows 3 ('94).

   The product does not make use of an external DBMS for the information
   base.

AVAILABILITY

   UCOM.X is commercially available. For further information contact:

         Pascal Duchamp, International Sales

         Address: TS-E3X, Le Capitole 44, avenue des Champs Pierreux,
                           99029 Nanterre Cedex, France
         Tel:      (+33) 1-46-14-50-00
         Fax:      (+33) 1-46-14-58-16
         Email: C=FR;A=atlas;P=e3x;O=e3x;OU1=paris;S=duchamp
                duchamp@paris.e3x.fr

     or: Laurence Puvilland, Marketing
         Email: C=fr;A=atlas;P=e3x;O=e3x;OU1=paris;S=puvilland
                puvilland@paris.e3x.fr

     or: Ascan Woermann, R&D
         Email: C=fr;A=atlas;P=e3x;O=e3x;S=Woermann
                woermann@e3x.fr


DATE LAST UPDATED

   July, 1993

Top       Page 78 
NAME

   Wang OPEN/services (tm)
   Wang Laboratories, Inc.


KEYWORDS

   CLNS, Commercially Available, DSA/DUA, DUA Interface, HP, IBM PC, IBM
   RISC, Limited Functionality, OSI Transport, RFC-1006, Wang, X.25

ABSTRACT

   Wang's X.500 products are a part of our OPEN/services product whose
   main features include the following:

   X.500 directory - Contains information about organizations,
   individuals, and distribution lists. The directory is the primary
   vehicle by which users of OPEN/office, Wang's X.400 electronic mail
   product, address mail.

   Authentication Services - Verifies the login name and password of
   each user logging into OPEN/services.

   International support - Provides character translation tables so that
   users can display screens containing international characters and use
   international collating sequences.

   Object management - Greatly increases the integration between
   OPEN/services, OPEN/office and other Windows-based applications.

   Activity logging - Records the activities of OPEN/services. This
   information can be useful for monitoring the OPEN/services processes
   and for troubleshooting.

   Database management - Provides utilities that validate and reorganize
   the OPEN/services databases including the Directory Information Base
   (DIB).

   OPEN/services includes a DSA, a DUA, and a DUA interface all rolled
   into one product. (The DUA interface protocol is private.)

   Wang OPEN/services consists of two parts: software installed on a
   server and software installed on PC clients on a LAN. The client or
   end-user software enables users to log in and log out; change the
   login password; use the OPEN/services directory; and perform various
   actions, such as open and print, on files in the Wang
   OPEN/applications and in certain third-party applications including

Top       Page 79 
   Microsoft Windows File Manager. The server consists of the DSA, the
   DUA, the Directory Information Base, the service administration
   programs such as login authentication, the database management
   utilities, and activity logging.

COMPLIANCE (applicable only for DSAs and DUAs)

   Wang OPEN/services complies with the 1988 CCITT Recommendations
   X.500-X.521 [CCITT-88] with the following exceptions. Whole tree
   searches are not supported, nor does the product support chained
   adding, modifying, or deleting. Simple authentication is supported,
   but strong authentication is not.

   In the future, the 1992 extensions to the X.500 standard will be
   supported by Wang OPEN/services.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   None are supported at the present time.

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   None are supported at the present time.

INTEROPERABILITY

   The interoperability of OPEN/services with other X.500 products is
   untested.

PILOT CONNECTIVITY

   Pilot connectivity between OPEN/services and the AARNET project, NADF
   Pilot Project, NIST Pilot Project, PARADISE, and PSI White Pages
   Project has not been attempted.

BUGS

   To report problems with Wang OPEN/services, contact your local Wang
   sales office, your Wang authorized reseller or call your regional
   support center. (In the USA, the number is 404-432-9001).

CAVEATS and GENERAL LIMITATIONS

   None

Top       Page 80 
INTERNETWORKING ENVIRONMENT

   Wang OPEN/services currently runs in the following environments:
   RFC1006 with TCP/IP, TP4 with CNLS, TP0 with X.25 and SLIP.

HARDWARE PLATFORMS

   Server Requirements

   Installing Wang OPEN/services Server requires the following hardware:
   a Wang RISC Series Server 220 or greater, or an IBM RISC
   System/6000(tm) with a minimum of 32 MB of memory, or a Hewlett-
   Packard 9000 Series 800 system with a minimum of 32 MB of memory. For
   each system a minimum of 20 MB of free disk space in a file system is
   required.

   Client Requirements

   Installing OPEN/services for Windows requires the following hardware:
   a 386/SX CPU or later, at least 4 MB of memory, a hard disk drive
   with at least 2.5 MB of disk space, and a VGA monitor. A pointing
   device is not required to run OPEN/services but is strongly
   recommended.

   Network Requirements

   OPEN/services has the following network requirements: 802.3 or 802.5
   LAN, network interface cards (NICs) to support TCP/IP on client PCs,
   Ethernet or token ring adapters on the servers, and optionally X.25
   cards on the servers.

SOFTWARE PLATFORMS

   Server Requirements

   Installing Wang OPEN/services Server requires the following software:
   AIX Operating System, release 3.2.3 or later, with bundled support
   for the TCP/IP protocol suite, or HP-UX Operating System, Release 9.0
   or later.

   Client Requirements

   OPEN/services for Windows requires the following software: Microsoft
   MS-DOS(tm) Operating System, Release 5.0 or later and Microsoft
   Windows 3.1 or later.

Top       Page 81 
AVAILABILITY

   Wang OPEN/services is commercially available from:

      Wang Laboratories, Inc.
      1 Industrial Avenue
      Lowell, Massachusetts 01851
      Phone: 508-967-6114
      FAX: 508-967-1105

   To obtain OPEN/services, contact your local Wang sales office, your
   Wang authorized reseller or call 1-800-NEW-WANG.

DATE LAST UPDATED or CHECKED

   December 6th, 1993

Top       Page 82 
NAME

   Xdi - DUA
   Bellcore


KEYWORDS

   Available via FTP, DUA Connectivity, DUA Only, Free, Limited
   Functionality, Multiple Vendor Platforms, Needs ISODE, RFC-1274,
   RFC-1484, Source, Sun, UNIX, X Window System

ABSTRACT

   Xdi is a Directory User Agent (DUA) for the X Window System.  In
   addition to providing a user-friendly interface, it supports
   Directory interactions of different levels of complexity. Users can
   select different window screens to browse, search and modify the
   Directory.  There are two different search screens for name based
   search and attribute based search. It is simple to use for novice
   users but is also useful for more advanced users to formulate complex
   search filters.  Xdi also supports "user-friendly naming" in many
   cases so that users are not required to know X.500 naming format.


COMPLIANCE (applicable only for DSAs and DUAs)

   88 standard compliant: Delete and Add operations, and strong
   authentication not implemented. There are no facilities to modify the
   RDNs of entries.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   RFC 1274 is supported.

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   RFC 1484 is supported.

INTEROPERABILITY

   Believed to be interoperable with other DSAs. Only tested against
   ISODE/QUIPU DSAs.

PILOT CONNECTIVITY

   DUA Connectivity

Top       Page 83 
BUGS

   Send bug reports to sywuu@thumper.bellcore.com

CAVEATS and GENERAL LIMITATIONS


INTERNETWORKING ENVIRONMENT

   Same as ISODE.

HARDWARE PLATFORMS

   This software has been tested on SUN4. It is expected that the
   software is portable to SUN3 and other UNIX machines.

SOFTWARE PLATFORMS

   Xdi is expected to run on ISODE (release 7.0 upwards) in UNIX
   environment.  The 'xdi' directory has been designed to fit directly
   into the ISODE source tree. Xdi requires X11R4, the associated Xt
   toolkit and Athena widget libraries.  Also see the operating
   environments of ISODE.

AVAILABILITY

   The Xdi software is available via anonymous FTP from
   thumper.bellcore.com in file pub/xdi.tar.Z. Source code and
   executables can be freely distributed or modified for non-commercial
   and non-profit use provided that all copyright notices, permission
   and nonwarranty notice included in the software distribution remain
   intact.

   For further information contact Sze-Ying Wuu at
   sywuu@thumper.bellcore.com.

DATE LAST UPDATED or CHECKED

   March 18th, 1993

Top       Page 84 
NAME

   XLU
   Brunel University, UK


KEYWORDS

   DUA Connectivity, DUA Only, Free, Multiple Vendor Platforms, Needs
   ISODE, Source, UNIX, X Window System


ABSTRACT

   XLU (X LookUp) is an X.500 DUA interface for the X Window System.

   XLU can be configured for many different styles of interaction.
   Example configurations are provided for single window and multiple
   window use.

   XLU implements the `User-Friendly Naming' search strategy and also
   has a form-filling search mode. Asynchronous directory operations are
   used.

   Full user friendly add and modify functions are provided, with the
   ability to tailor the modify screen to present simple subsets of the
   available attributes.

COMPLIANCE (applicable only for DSAs and DUAs)

   88 Standard compliant: Strong authentication not yet implemented.  No
   plans for support of the 1992 Standard.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   No plans at present.

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   No plans at present.

INTEROPERABILITY

   [No information provided--Ed.]

Top       Page 85 
PILOT CONNECTIVITY

   DUA Connectivity: The interface is in use in the UK Academic
   Directory Pilot.

BUGS

   Bugs should be reported to x500@brunel.ac.uk.

CAVEATS and GENERAL LIMITATIONS

   [No information provided--Ed.]

INTERNETWORKING ENVIRONMENT

   As ISODE.

HARDWARE PLATFORMS

   Most UNIX machines.

SOFTWARE PLATFORMS

   UNIX
   MIT X11R5 libraries
   ISODE/QUIPU (version 8.0 >)

AVAILABILITY

   Sources are freely available for commercial or non-commercial use.
   Contacts.

   Postal Address:
        Andrew Findlay
        Computing and Media Systems
        Brunel University
        Cleveland Road
        Uxbridge, Middlesex
        UB8 3PH
        UK

   E-mail: x500@brunel.ac.uk.

   Fax: +44 895 32806 (Andrew Findlay)

   Telephone: +44 895 203066 (Andrew Findlay)

Top       Page 86 
DATE LAST UPDATED or CHECKED

   March 1st, 1993

Top       Page 87 
NAME

   XT-DUA
   NEXOR


KEYWORDS

   Bull, CLNS, Commercially Available, DUA Connectivity, DUA Only, HP,
   IBM RISC, ICL, Motif, Multiple Vendor Platforms, OpenLook, OSI
   Transport, RFC-1006, RFC-1274, RFC-1277, RFC-1278, RFC-1484,
   Solbourne, Sun, X Window System, X.25

ABSTRACT

   XT-DUA provides a X-Windows based user interface to the X.500
   Directory.  Both Motif and OpenLook styles are supported.

   Browsing features include:

   - Passing of user address information to the XT-MUA X.400 user agent.
   - History - allowing quick access to previously referenced parts of
     the DIT.
   - Customizable entry display - allowing subsets of attributes be
     displayed when showing an entry.
   - User Friendly Name (UFN) based searching
   - Hypertext-like navigation.
   - Support for application entities e.g. startup of ftam session.
   - User defined name for attribute labels.
   - Support for photo and audio attributes.
   - Attribute value on scanline.
   - Intelligent choice of entries to display when moving to a new
     location in the DIT.


   Management features include:

   - Creation of new entries.
   - Modification of existing entries (including RDN) - based on
     Quipu EDB format.
   - Deletion of entries.
   - Friendly editor of modifying Quipu ACLs.
   - Rebinding - authenticated and to named DSA.
   - Full configuration of DAP request parameters

Top       Page 88 
COMPLIANCE (applicable only for DSAs and DUAs)

   Compliant with X.500(88), and NIST SIA version 2 except X.509 strong
   authentication not implemented (under development).

   NEXOR is committed to migrate XT-DUA to the 1992 standards.

CONFORMANCE WITH PROPOSED INTERNET STANDARDS

   The following are supported: RFC 1274 and RFC 1277.

CONSISTENCE WITH INFORMATIONAL AND EXPERIMENTAL RFCs

   The following are supported: UFN [RFC 1484] and RFC 1278.

INTEROPERABILITY

   XT-DUA has interoperated with all DSAs used in the PARADISE pilot.

PILOT CONNECTIVITY

   Full DUA connectivity 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 with CLNP, OSI TP0 with X.25 or CONS, and RFC 1006 with
   TCP/IP

HARDWARE PLATFORMS

      Sun
      Solbourne
      IBM RS/6000
      Bull DPX 6000
      HP Apollo 9000

Top       Page 89 
SOFTWARE PLATFORMS

      SunOs 4.1.x
      AIX 3.2
      HP-UX 9.01
      Windows 3.1 (over LDAP)

   Other ports planned include SCO Unix and ICL DRS6000.

AVAILABILITY

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

        XT-DUA Sales
        NEXOR
        8 Faraday Building
        Highfields Science Park
        Nottingham
        NG7 2QP
        UK

        DN:             c=GB@o=NEXOR Ltd
        Telephone:      +44 602 520500
        Fax:            +44 602 520519
        E-Mail:         sales@nexor.co.uk


DATE LAST UPDATED or CHECKED

   August 2nd, 1993

Top       Page 90 
NAME

   XT-QUIPU
   NEXOR


KEYWORDS

   Bull, CLNS, Commercially Available, DSA Connectivity, DSA Only, HP,
   IBM RISC, ICL, Multiple Vendor Platforms, OSI Transport, RFC-1006,
   RFC-1274, RFC-1276, RFC-1277, RFC-1278, RFC-1279, RFC-1484, RFC-1485,
   Solbourne, Sun, X.25

ABSTRACT

   XT-QUIPU is an X.500(88) DSA.  Characteristics of the DSA are:

   - Full DAP access
   - Full DSP access
   - Support for X.400, X.500, and RFC 1274 attributes and
     object classes
   - Approximate match based on Soundex.
   - Flexible schema management
   - RFC 1276 Replication
   - Attribute level access control
   - Search and list access control
   - Knowledge management mapped onto DIT
   - Attribute inheritance
   - Caching
   - Remote management


COMPLIANCE (applicable only for DSAs and DUAs)

   Compliant with X.500(88), and NIST SIA version 2 except X.509 strong
   authentication not implemented (under development).

   NEXOR is committed to migrate XT-QUIPU to the 1992 standards.

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 1484], RFC 1278, and RFC 1279.

Top       Page 91 
INTEROPERABILITY

   XT-QUIPU interoperates will all DSAs used in the PARADISE pilot.

PILOT CONNECTIVITY

   XT-QUIPU DSAs are 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
   Solbourne
   IBM RS/6000
   Bull DPX 6000
   ICL DRS/6000
   HP Apollo 9000

SOFTWARE PLATFORMS

   SunOs 4.1.x
   AIX 3.2
   DRS/NX 6000
   HP-UX 9.01

   Other ports planned include SCO Unix.

AVAILABILITY

   XT-QUIPU is commercial software.  For more details contact:

Top       Page 92 
        XT-QUIPU Sales
        NEXOR
        8 Faraday Building
        Highfields Science Park
        Nottingham
        NG7 2QP
        UK

        DN:        c=GB@o=NEXOR Ltd
        Telephone: +44 602 520500
        Fax:       +44 602 520519
        E-Mail:    sales@nexor.co.uk


DATE LAST UPDATED or CHECKED

   August 2nd, 1993

Top       Page 93 
4. References


    [CCITT-88]  CCITT, "Data Communications Networks Directory",
                Recommendations X.500-X.521, Volume VIII - Fascicle
                VIII.8, IXth Plenary Assembly, Melbourne, November 1988.

    [NIST-88]   National Institute of Standards and Technology, "Stable
                Implementation Agreements for Open Systems
                Interconnection Protocols", Version 2 Edition 1, NIST
                Special Publication 500-162, December 1988.

    [RFC 1202]  Rose, M., "Directory Assistance Service", RFC 1202,
                Performance Systems International, Inc., February 1991.

    [RFC 1249]  Howes, T., Smith, M., and B. Beecher, "DIXIE Protocol
                Specification", RFC 1249, University of Michigan, August
                1991.

    [RFC 1274]  Barker, P., and S. Kille, "The COSINE and Internet X.500
                Schema", RFC 1274, University College, London, England,
                November 1991.

    [RFC 1275]  Kille, S., "Replication Requirements to provide an
                Internet Directory using X.500," RFC 1275, University
                College, London, England, November 1991.

    [RFC 1276]  Kille, S.,  "Replication and Distributed Operations
                extensions to provide an Internet Directory using
                X.500", RFC 1276, University College, London, England,
                November 1991.

    [RFC 1277]  Kille, S.,  "Encoding Network Addresses to support
                operation over non-OSI lower layers", RFC 1277,
                University College, London, England, November 1991.

    [RFC 1278]  Kille, S., "A string encoding of Presentation Address",
                RFC 1278, University College, London, England, November
                1991.

    [RFC 1279]  Kille, S., "X.500 and Domains", RFC 1279, University
                College, London, England, November 1991.

    [RFC 1484]  Kille, S., "Using the OSI Directory to achieve User
                Friendly Naming", RFC 1484, ISODE Consortium, July 1993.

    [RFC 1485]  S. Kille, "A String Representation of Distinguished

Top       Page 94 
                Names", RFC 1485, ISODE Consortium, July 1993.

    [RFC 1487]  Yeong, W., Howes, T., and S. Kille, "X.500 Lightweight
                Directory Access Protocol", RFC 1487, Performance
                Systems International, University of Michigan, ISODE
                Consortium, July 1993.

    [RFC 1488]  Howes, T., Kille, S., Yeong, W., and C. Robbins, "The
                X.500 String Representation of Standard Attribute
                Syntaxes", RFC 1488, University of Michigan, ISODE
                Consortium, Performance Systems International, NeXor
                Ltd., July 1993.

5. Security Considerations

   Security issues are not discussed in this memo.

6.  Editors' Addresses

   Arlene F. Getchell
   Lawrence Livermore National Laboratory
   National Energy Research Supercomputer Center
   P.O. Box 5509, L-561
   Livermore, CA 94551

   Phone: (510) 423-6349
   EMail: getchell@es.net
   X.400: s=getchell;p=esnet;a= ;c=us;


   Srinivas R. Sataluri
   AT&T Bell Laboratories
   Room 1C-429, 101 Crawfords Corner Road
   P.O. Box 3030
   Holmdel, NJ 07733-3030

   Phone: (908) 949-7782
   EMail: sri@qsun.att.com