Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 1292

A Catalog of Available X.500 Implementations

Pages: 103
Obsoleted by:  1632
Part 3 of 3 – Pages 65 to 103
First   Prev   None

ToP   noToC   RFC1292 - Page 65   prevText
NAME

   QUIPU
   ISODE

LAST MODIFIED

   July, 1991

KEYWORDS

   API, Available via FTAM, Available via FTP, CLNP, DEC Ultrix,
   DSA/DUA, Free, HP, MIPS, Macintosh, Multiple Vendor Platforms, OSI
   Transport, RFC-1006, Source, Sun, UNIX, X Window System, X.25

ABSTRACT

   QUIPU is part of the ISODE which is an openly available implementa-
   tion of the upper layers of OSI.  QUIPU provides a X.500 Directory
   System Agent (DSA) and a set of Directory User Agents (DUA) aimed at
   different terminal types and modes of interaction

   QUIPU was first publicly demonstrated at ESPRIT in November 1988.
   QUIPU is being used extensively in the European PARADISE project, the
   White Pages Pilot Project and the Australian pilot.  A QUIPU DSA is
   being used at the ROOT node of the Pilot DIT and is being used as
   most country level DSAs.

   QUIPU provides its own solutions to area not specified by the 1988
   standards such as replication and access control.

COMPLETENESS

   QUIPU is aligned to the 1988 ISO IS and the NIST OIW Directory Imple-
   mentors Guide Version 1, with the following exceptions:

       Strong authentication is not implemented.

       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 opera-
       tion is required to check the DN, the bind IS allowed.
ToP   noToC   RFC1292 - Page 66
       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 ``origina-
       tor'' 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
       recognized 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.

INTEROPERABILITY

   QUIPU has interworked with a number of other implementations, and has
   no know problems in such interworking.

PILOT CONNECTIVITY

   QUIPU is in use in many directory pilots, certainly including PARAD-
   ISE and the White Pages Pilot Project.

BUGS

   Problems should be reported to quipu-support@cs.ucl.ac.uk.

CAVEATS AND GENERAL LIMITATIONS

   None.

INTERNETWORKING ENVIRONMENT

   QUIPU users TP0 over X.25, CONS and TCP (using RFC-1006) or TP4 over
   SunLink OSI.

   The DSA knows about the problems of unconnected networks and makes
   chain/refer choices based on the network connectivity.  Using this an
   X.25 only DSA can access data from an Internet only DSA by chaining
   operations through a DSA connected to both networks.
ToP   noToC   RFC1292 - Page 67
HARDWARE PLATFORMS

   [No information provided--Ed.]

SOFTWARE PLATFORMS

   The ISODE and QUIPU runs on native Berkeley (4.2, 4.3) and AT&T Sys-
   tem V, in addition to various other UNIX-like operating systems.  No
   kernel modifications are required.

AVAILABILITY

   The ISODE is not proprietary, but it is not in the public domain.
   This was necessary to include a "hold harmless" clause in the
   release.  The upshot of all this is that anyone can get a copy of the
   release and do anything they want with it, but no one takes any
   responsibility whatsoever for any (mis)use.

DISTRIBUTION SITES

   The FTP or FTAM distributions of ISODE-7.0 consists of 3 files. The
   source and main ISODE-7.0 distribution is in the file isode-7.tar.Z
   which is approximately 4.7MB in size.

   LaTeX source for the entire document set can be found in the isode-
   7-doc.tar.Z file (3.5MB).  A list of documents can be found in the
   doc/ directory of the source tree.

   A Postscript version of the five volume manual can be found in the
   isode-7-ps.tar.Z file (4.7MB).

   1.  FTP
          If you can FTP to the Internet, then use anonymous FTP to
          uu.psi.com [136.161.128.3] to retrieve the files in BINARY
          mode from the isode/ directory.

   2.  NIFTP
          If you run NIFTP over the public X.25 or over JANET, and are
          registered in the NRS at Salford, you can use NIFTP with usen-
          rame "guest" and your own name as password, to access
          UK.AC.UCL.CS to retrieve the files from the <SRC> directory

   3.  FTAM on the JANET, IXI or PSS
          The sources are available by FTAM from UCL over X.25 using

                  JANET (DTE 00000511160013),
                  IXI   (DTE 20433450420113) or
                  PSS   (DTE 23421920030013)
ToP   noToC   RFC1292 - Page 68
          all with TSEL "259" (ASCII encoding). Use the "anon" user-
          identity and retrieve the files from the src/ directory. The
          file service is provided by the FTAM implementation in ISODE
          6.0 or later (IS FTAM).


   4.  NORTH AMERICA
          For mailings in NORTH AMERICA, send a check for 375 US Dollars
          to:

                  University of Pennsylvania
                  Department of Computer and Information Science
                  Moore School
                  Attn: David J. Farber (ISODE Distribution)
                  200 South 33rd Street
                  Philadelphia, PA 19104-6314
                  US
                  +1 215 898 8560


          Specify either (a) 1600bpi 1/2-inch tape, or (b) Sun 1/4-inch
          cartridge tape.  The tape will be written in tar format and
          returned with a documentation set.  Do not send tapes or
          envelopes.  Documentation only is the same price.

   5.  EUROPE (tape and documentation)
          For mailings in EUROPE, send a cheque or bankers draft and a
          purchase order for 200 Pounds Sterling to:

                  Department of Computer Science
                  Attn: Natalie May/Dawn Bailey
                  University College London
                  Gower Street
                  London, WC1E 6BT
                  UK

             For information only:
                  Telephone:      +44 71 380 7214
                  Fax:            +44 71 387 1397
                  Telex:          28722
                  Internet:       natalie@cs.ucl.ac.uk, dawn@cs.ucl.ac.uk


          Specify either (a) 1600bpi 1/2-inch tape, or (b) Sun 1/4-inch
          cartridge tape.  The tape will be written in tar format and
          returned with a documentation set.  Do not send tapes or
          envelopes.  Documentation only is the same price.
ToP   noToC   RFC1292 - Page 69
   7.  EUROPE (tape only)
          Tapes without hardcopy documentation can be obtained via the
          European Forum for Open Systems (EurOpen, formerly known as
          EUUG).  The ISODE 7.0 distribution is called EurOpenD14.

                    EurOpen Software Distributions
                    c/o Frank Kuiper
                    Centrum voor Wiskunde en Informatica
                    Kruislaan 413
                    1098 SJ  Amsterdam
                    The Netherlands

             For information only:
                    Telephone:    +31 20 5924121 (or: +31 20 5929333)
                    Telex:        12571 mactr nl
                    Telefax:      +31 20 5924199
                    Internet:     euug-tapes@cwi.nl

             Specify one of:
                  - 1600bpi 1/2-inch tape:  140 Dutch Guilders
                  - Sun 1/4-inch cartridge tape (QIC-24 format):
                                            200 Dutch Guilders


          If you require DHL this is possible and will be billed
          through.  Note that if you are not a member of EurOpen, then
          there is an additional handling fee of 300 Dutch Guilders
          (please enclose a copy of your membership or contribution pay-
          ment form when ordering).  Do not send money, cheques, tapes
          or envelopes, you will be invoiced.

   8.  PACIFIC RIM
          For mailings in the Pacific Rim, send a cheque for 300 dollars
          Australian to:

                  Isode Distribution
                  (Attn Andrew Waugh)
                  723 Swanston St,
                  Carlton, VIC 3053
                  Australia

              For information only:
                  Telephone:      +61 3 282 2615
                  Fax:            +61 3 282 2600
                  Internet:       ajw@mel.dit.csiro.au
ToP   noToC   RFC1292 - Page 70
          Please specify the media you  desire:  (a)  1/2-inch  tape  at
          1600bpi,  3200bpi,  or  6250bpi; or (b) Sun 1/4-inch cartridge
          tape in either QIC-11, QIC-24 or QIC-150 format; or  (c)  Exa-
          byte  2.3  Gigabyte  or  5  Gigabyte format.  The tape will be
          written in tar format and returned with a  documentation  set.
          Do  not  send  tapes  or envelopes.  Documentation only is the
          same price.
ToP   noToC   RFC1292 - Page 71
NAME

   SD
   Brunel University

LAST MODIFIED

   November, 1991

KEYWORDS

   DUA Only, Free, Included in ISODE, Multiple Vendor Platforms, Needs
   ISODE, RFC-1006, UNIX, X Window System

ABSTRACT

   SD (Screen Directory) is an X.500 DUA interface for character mapped
   screens.  SD is an early attempt to provide quick, easy and user
   friendly access to the Directory.  The following directory operations
   are supported: read, search and list.

   SD does not provide any sophisticated access to the DSA.  Operations
   are performed synchronously.  The Directory is thus presented as is,
   i.e.  a hierarchical tree of information, with the user required to
   "navigate" the DIT in order to locate required information.

   SD is available as part of the ISODE release from version 6.0
   onwards.

COMPLETENESS

   88 standard: strong authentication not implemented

INTEROPERABILITY

   Believed to be compliant, though untested.

PILOT CONNECTIVITY

   DUA Connectivity: SD is in use in many directory pilots, certainly
   including PARADISE and the Internet.

BUGS

   Bugs to x500@brunel.ac.uk
ToP   noToC   RFC1292 - Page 72
INTERNETWORKING ENVIRONMENT

   TP0 over TCP/IP (as ISODE)

HARDWARE PLATFORMS

   Most UNIX machines

SOFTWARE PLATFORMS

   UNIX
   BSD curses library
   ISODE/QUIPU libraries (version 6.7 upwards)

AVAILABILITY

   Openly available as part of the ISODE release. Sources are freely
   available for commercial or non-commercial use from:

           src.brunel.ac.uk [134.83.128.3]

   Files are:

           x500/pod.tar.Z
           x500/sd.tar.Z

   Contacts:

           Andrew.Findlay@brunel.ac.uk     +44 1 895 74000 x 2512
           Damanjit.Mahl@brunel.ac.uk      +44 1 895 74000 x 2946
           x500@brunel.ac.uk

   Postal Address:

           Andrew Findlay
           Computer Centre
           Brunel University
           Cleveland Road,
           Uxbridge, Middlesex
           UB8 3PH
           United Kingdom
ToP   noToC   RFC1292 - Page 73
NAME

   UCOM.X 500 (tm)
   E3.X

LAST MODIFIED

   November, 1991

KEYWORDS

   API, Bull, Commercially Available, DEC Ultrix, DSA/DUA, HP, IBM PC,
   IBM RISC, Multiple Vendor Platforms, Philips, RFC-1006, Siemens, Sun,
   UNIX, X.25

ABSTRACT

   UCOM.X 500 includes a Directory System Agent (DSA), a directory
   access API, and a set of Directory User Agents (DUAs) for different
   terminal types. UCOM.X 500 is a commercial product based on PIZARRO,
   the research prototype developed at INRIA by Christian Huitema's
   team.

   Some characteristics of the DSA are:

       - The DAP and DSP protocols are provided conformant with the 1988
       CCITT X.500 recommendations.

       - 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. Additionally, fre-
       quently 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.

       - All X.500 (88) as well as some X.400 (88) object classes,
       attributes and syntaxes are supported. Users may define their own
       classes and attribute types.

       - Schema management: object class and attribute definitions are
       enforced.

       - Simple authentication is provided; strong authentication is not
       currently supported.
ToP   noToC   RFC1292 - Page 74
       - 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.

   The UCOM.X 500 API provides the DAP protocol to applications access-
   ing the Directory. It is a synchronous API which automatically
   manages referrals. Several DUAs using the API, are available. These
   include command line and full screen interfaces for users with ordi-
   nary terminals, and an X-Windows user interface (12/91). An X/Open
   XDS API will be offered shortly.

   UCOM.X 500 is used by French research centers involved in PARADISE, a
   COSINE project. A distributed application to control document
   transfer in a large French hospital, has been built on the UCOM.X 500
   API. It is being used for distributed applications management in the
   French Post Office.

COMPLETENESS

   UCOM.X 500 conforms to 1988 X.500 series of recommendations, as
   specified in paragraph 9 of X.519, with the exception of strong
   authentication.

INTEROPERABILITY

   Interoperability tests with other implementations, e.g. QUIPU, have
   been made in the PARADISE project. UCOM.X 500 is used in the French
   PARADISE pilot.

PILOT CONNECTIVITY

   DSA and DUA connectivity to the PARADISE pilots.  See caveats.

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 is stored in main memory which means that the order
   of magnitude of the number of objects supported per DSA is 10,000. By
   1992 100,000 objects will be supported.

   Not all syntaxes defined in the COSINE and Internet Schema are
   currently supported, and the DUAs do not display photo attributes.
   The Internet DSP is not supported.
ToP   noToC   RFC1292 - Page 75
INTERNETWORKING ENVIRONMENT

   UCOM.X 500 uses RFC-1006 with TCP/IP and TP0 with X.25.

HARDWARE PLATFORMS

   UCOM.X 500 runs on: Sun 3, Sun 4, IBM RS 6000, Philips P 9000, DEC
   machines, Bull DPX 2000, HP 9000/300, Siemens IN 6000 and 386-based
   PCs.  It can easily be ported to any UNIX machine.

   Windows 3 and Macintosh DUAs will be available by Spring 1992.

SOFTWARE PLATFORMS

   UCOM.X 500 is portable to any UNIX-like operating system. It has been
   ported to: AIX, UNIX System V.3, SUN OS 4, Ultrix, HP-UX, SCO Unix,
   Interactive, BOS (Bull Operating System), and SPIX.

   The UNIX file system is used to hold the DIB.

AVAILABILITY

   UCOM.X is commercially available.  Contact:

           Dominique Fayet
           E3.X
           Tour Anjou
           33 Quai de Dion Bouton
           92 814 Puteaux CEDEX
           FRANCE

           Tel: (+33) 1 40 90 08 15
           Fax: (+33) 1 47 74 58 87

           Philippe Brun
           C=fr;A=atlas;P=e3x;O=e3x;S=Brun
           phb@e3x.fr
ToP   noToC   RFC1292 - Page 76
NAME

   ud
   University of Michigan

LAST MODIFIED

   November, 1991

KEYWORDS

   Available via FTP, DUA Light Weight Client, Free, Source, UNIX, Mul-
   tiple Vendor Platforms

ABSTRACT

   ud is a command line based directory application useful for display-
   ing and modifying white pages information about people.  It runs on
   top of the DIXIE protocol (described in RFC 1246).  ud was developed
   to run under Unix and is currently in beta release within U-M staff
   and a few other places that have heard of it.

   Features include the ability to display and modify the following
   attributes: title, description, commonName, uid, mail, postalAddress,
   homePostalAddress, telephoneNumber, facsimileTelephoneNumber, home-
   Phone.

COMPLETENESS

   ud uses the DIXIE protocol to access X.500 and thus is subject to the
   same completeness restrictions as DIXIE.  It provides Read, Search,
   and Modify capabilities.

INTEROPERABILITY

   Works with the DIXIE server, which works with the QUIPU DSA and DAP
   library.

PILOT CONNECTIVITY

   It has been tested (in conjunction with the DIXIE server) in both the
   Internet and PARADISE pilots.

BUGS

   No outstanding bugs are known.  But reports should be sent to
   x500@itd.umich.edu.
ToP   noToC   RFC1292 - Page 77
CAVEATS AND GENERAL LIMITATIONS

   ud is heavily oriented to white pages information and thus general
   access to the DIXIE protocol is not provided.

INTERNETWORKING ENVIRONMENT

   ud uses the DIXIE protocol and thus TCP to communicate with the DIXIE
   server.

HARDWARE PLATFORMS

   ud is known to run on Sun 3s, Sun 4s, and Vaxen.

SOFTWARE PLATFORMS

   SunOS 3.5, SunOS 4.1.1, BSD 4.3 Unix.

AVAILABILITY

   This software is openly available.  It may be obtained by anonymous
   FTP from terminator.cc.umich.edu in the directory ~ftp/x500.

   This software was developed at the University of Michigan by Bryan
   Beecher of the ITD Research Systems Unix Group and is subject to the
   following copyright.

   Copyright (c) 1991 Regents of the University of Michigan.  All rights
   reserved.  Redistribution and use in source and binary forms are per-
   mitted 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.
ToP   noToC   RFC1292 - Page 78
NAME

   VMS-ISODE
   Computer Science Department of Massey University

LAST MODIFIED

   November, 1991

KEYWORDS

   API, Available via FTP, DSA/DUA, Free, Needs ISODE, RFC-1006, Source,
   VMS

ABSTRACT

   VMS-ISODE is a reasonably complete port of ISODE version 7.0. It sits
   on top of several TCP implementations for VMS (UCX, Multinet, CMU and
   Wollongong) and also PSI X.25.

   See entry for QUIPU/ISODE for a detailed description of the DSA/DUA.

COMPLETENESS

   See entry for QUIPU/ISODE.

INTEROPERABILITY

   See entry for QUIPU/ISODE.

PILOT CONNECTIVITY

   Not tested.

BUGS

   VMS related problems should be sent to PKay@massey.ac.nz

CAVEATS AND GENERAL LIMITATIONS

   None.

INTERNETWORKING ENVIRONMENT

   See entry for QUIPU/ISODE.
ToP   noToC   RFC1292 - Page 79
HARDWARE PLATFORMS

   VAX hardware

SOFTWARE PLATFORMS

   VMS v5.0 or greater

AVAILABILITY

   The VMS part of the package is freely available.  Anonymous FTP from
   cc-vms1.massey.ac.nz (130.123.1.4).
ToP   noToC   RFC1292 - Page 80
NAME

   VTT X.500
   Technical Research Centre of Finland

LAST MODIFIED

   November, 1991

KEYWORDS

   API, Apollo, CLNP, Commercially Available, DSA/DUA, IBM PC, Multiple
   Vendor Platforms, RFC-1006, Sun, X.25

ABSTRACT

   VTT X.500 contains a full distributed DSA and a subroutine call to
   dua ( call_dua(parameters)). This subroutine is linked to user's pro-
   cess.  There are two ways for dua to communicate with our DSA called
   dsacvops: a fast communication through shared memory for dua and dsa
   in the same computer and a complete OSI-stack for communicating in
   DAP-protocol with remote dsa's which can be any implementation of
   X.500 dsa, not necessarily dsacvops.  DSA communicates with other
   dsas through a full OSI-stack with protocol DSP or with a shorter
   stack when both dsas are dsacvops-processes.  dsacvops contains a
   special purpose database DIB. VTT X500 contains caching of read and
   search results, access controls (as in Annex F of X.501), object
   classes and attribute types as in X.520 and X.521 and simple authen-
   tication with unprotected passwords in bind. The network level can be
   X.25 or TCP/IP. There are test duas, duacvops, duauser, with a simple
   user interface. Certificates for strong authentication are included
   to x509dua and x509duacvops. VTT X500 is realized with program
   development tools CVOPS and CASN, the code is in C-language and uses
   UNIX System V. The code is fairly easy to port to other operating
   systems.  VTT X500 was made for Smail e-mail product of Nokia Data
   Systems.

COMPLETENESS

   Complete DAP and DSP of 1988 X.500 Recommendations are implemented.
   There are the following omissions: multicasting is not implemented,
   strong authentication of calls to dsa (optional signing of DAP and
   DSP-calls, strong authentication in bind, security error, security
   parameters in common arguments), T61 alternative in CASE IGNORE and
   CASE EXACT STRING, Criteria-syntax, TeletexTerminalIdentifier syntax.
ToP   noToC   RFC1292 - Page 81
INTEROPERABILITY

   Interoperability with ISODE QUIPU 6.0 has been tested, no formal test
   suite was used.

PILOT CONNECTIVITY

   Not tested: It should work in principle, but has not been tested.

BUGS

   No known bugs at the moment.

CAVEATS AND GENERAL LIMITATIONS

   Object identifiers for object classes and attribute types can
   currently have only the form {2 5 6 x} or {2 5 4 x}, x<256. Changing
   the directory schema requires code writing.

INTERWORKING ENVIRONMENT

   RFC-1006 with TCP/IP, TP0 with X.25, TP4 with X.25 available by
   agreement.

HARDWARE PLATFORMS

   Sun-3, Sun 386, Apollo, a version of dua for IBM PC will be forthcom-
   ing 1991.

SOFTWARE PLATFORMS

   Unix System V. Our own database and database management system. Uses
   CVOPS protocol development tool.
ToP   noToC   RFC1292 - Page 82
AVAILABILITY

   Commercially available.  Contact

           Asko Vilavaara
           Telecommunications Laboratory
           Technical Research Centre of Finland
           Otakaati 7 B, 02150 Espoo, FINLAND
           Telephone:+358 0 456 5641
           FAX: +358 0 455 0115
           E-mail: Asko.Vilavaara@tel.vtt.fi

           Henryka Jormakka
           Telecommunications Laboratory
           Technical Research Centre of Finland
           Otakaati 7 B, 02150 Espoo, FINLAND
           Telephone:+ 358 0 456 5662
           FAX: +358 0 455 0115
           E-mail: Henryka.Jormakka@tel.vtt.fi
ToP   noToC   RFC1292 - Page 83
NAME

   WIN(tm)/DS
   The Wollongong Group, Inc.

LAST MODIFIED

   November, 1991

KEYWORDS

   API, CLNP, Commercially Available, DSA/DUA, Multiple Vendor Plat-
   forms, OSI Transport, RFC-1006, Source, UNIX, X Windows, X.25

ABSTRACT

   WIN/DS is an implementation of OSI Directory Services aligned with
   the ISO 1988 X.500 IS and NIST Stable Implementors Agreements. WIN/DS
   includes both a Directory User Agent (DUA) and a  Directory System
   Agent (DSA). The product supports all Directory Services operations,
   object classes and attributes.  It provides support for managing the
   Directory Information Tree (DIT) with facilities to control structure
   rules and their enforcement.  WIN/DS also provides solutions to areas
   not specified by the 1988 standards, such as replication and access
   control.

COMPLETENESS

   Wollongong closely follows the NIST OIW Stable Implementors' Agree-
   ments.  See also QUIPU.

INTEROPERABILITY

   WIN/DS has interoperated with other X.500 implementations at trade
   shows (CeBIT and Interop) and at strategic customer sites.

PILOT CONNECTIVITY

   [No information provided--Ed.]

BUGS

   Requests for product enhancement and modification should be sent to
   support@twg.com.
ToP   noToC   RFC1292 - Page 84
CAVEATS AND GENERAL LIMITATIONS

   [No information provided--Ed.]

INTERNETWORKING ENVIRONMENT

   TCP/IP (RFC 1006)
   TP0
   TP2
   TP4
   OSI TP[0/2,4] & TCP/IP dual stack gateway
   Ethernet
   X.25
   Ethernet/X.25 gateway
   ES-IS
   IS-IS
   Interface to OSI transport via the TLI
   Interface to the Data Link Layer via the DLPI
   STREAMS and DLPI compliant 3rd party network interfaces

HARDWARE PLATFORMS

   End-user binary product -

           386/i486 with UNIX System V (AT&T, Intel, INTERACTIVE, SCO)
           Apple Macintosh with A/UX

   Portable source code -

           UNIX SVR3, SVR4, BSD
           single- or mutli-processor 680x0, 880000, 386/i486

SOFTWARE PLATFORMS

   See above.

AVAILABILITY

   WIN/DS is commercially available from:

           The Wollongong Group, Inc.
           1129 San Antonio Road
           Palo Alto
           CA  94303
           Sales and Information: :415/962-7100   California
                                   703/847-4500   Wash D
                                   +32-2-718-0311 Belgium
ToP   noToC   RFC1292 - Page 85
NAME

   X.500 DUA process
   3Com Corporation

LAST MODIFIED

   July, 1991

KEYWORDS

   CLNP, Commercially Available, DUA Only, Multiple Vendor Platforms, X
   Window System, X.25, 3Com

ABSTRACT

   The DUA process runs on 3Com's dual-stack OSI/TCP terminal server,
   scheduled to be released in mid-June 1991.  It provides Presentation
   Address resolution for names, on behalf of the VTP application: when
   the user attempts an outgoing connection ("VTP <name>" or "connect
   <name>"), <name> gets mapped to its Presentation Address.

   The DUA process supports the AddEntry, RemoveEntry, and Search opera-
   tions.  Via a menu-driven command, the system administrator can con-
   figure any of these operations, then send the request to the DSA.  He
   would use the AddEntry operation to enter a resource name and its
   corresponding physical address in the DIB, the DeleteEntry operation
   to remove the name and its physical address, and the Search operation
   (with "filter" as an option) for a display of all registered names
   or, given a name, a display of the name's physical address.

   Regarding unbinding from a DSA, the system administrator could use an
   UnbindDSA command or set a timer which, once expired, would automati-
   cally perform the unbinding.  The binding to a DSA, on the other
   hand, is transparent, provided the system administrator has set a DSA
   address.  The binding is triggered by either an outgoing connection
   attempt or an operation request sent to the DSA.

   The schema supported by the DUA consists of the following sequence of
   object classes: Country, Organization, OrganizationalUnit (up to 3
   levels of OrganizationalUnits are allowed), ApplicationProcess, and
   ApplicationEntity.  Their respective attributes are CountryName,
   OrganizationName, OrganizationUnitName, CommonName, and Presenta-
   tionAddress.  The CommonName of the ApplicationEntity is always "vt"
   for VTP and is transparent to the system administrator.
ToP   noToC   RFC1292 - Page 86
COMPLETENESS

   Compliance with the ISO/IEC 9594 standards.
   Handling referrals not yet implemented.
   Schema supported: Country, Organization, OrganizationalUnit,
                     ApplicationProcess, and ApplicationEntity.
   Authentication not supported.

INTEROPERABILITY

   Interoperability with the ISODE QUIPU Directory Service and any DSA
   which strictly meets the ISO/IEC 9495 standards.

BUGS

   [No information provided--Ed.]

CAVEATS AND GENERAL LIMITATIONS

   Deleting an entry will fail if the DUA is interacting with a 6.0
   based version of QUIPU.  This is a bug in QUIPU, and version 7.0
   release will have it fixed.

   Adding a CountryName is disallowed if the DUA is bound to QUIPU.
   This decision was made because to add a country in QUIPU, one needs
   to bind as the manager of the DSA holding the root EDB file, and such
   information may not always be available to the system administrator.
   Also, our binding is done transparently.

INTERNETWORKING ENVIRONMENT

   OSI environments with the complete OSI stack, supporting CLNS and
   TP4.

HARDWARE PLATFORMS

   3Com's OSI/TCP CS/2000 and CS/2100.

SOFTWARE PLATFORMS

   The "SW/2000-OT Vers 1.0" software runs on 3Com's OSI/TCP CS/2000 and
   CS/2100, both stand-alone systems.

AVAILABILITY

   The dual-stack OSI/TCP terminal server and its "SW/2000-OT Vers 1.0"
   software is available from:
ToP   noToC   RFC1292 - Page 87
           3Com Corporation
           5400 Bayfront Plaza
           Santa Clara, CA 95054

           Information: Cyndi Jung
                        (408) 764-5173
                        cmj@3Com.COM
ToP   noToC   RFC1292 - Page 88
NAME

   Xdi
   Bellcore

LAST MODIFIED

   November, 1991

KEYWORDS

   DUA Only, DUA Connectivity, Available via FTP, Free, Source, Needs
   ISODE, X Window System, RFC-1006, CLNP, UNIX, X.25

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 dif-
   ferent 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.

COMPLETENESS

   The Xdi interface does not support accesses to Delete and Add DAP
   operations as in the 88 Directory Standard. Read, Search, and most
   Modify operations are fully supported. There are no facilities to
   modify the RDNs of entries. Strong authentication is not implemented.

INTEROPERABILITY

   Believed to be compliant. Only tested against ISODE/QUIPU DSAs.

PILOT CONNECTIVITY

   DUA Connectivity

BUGS

   Send bug reports to sywuu@thumper.bellcore.com
ToP   noToC   RFC1292 - Page 89
CAVEATS AND GENERAL LIMITATIONS

   None known.

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 6.8 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 environ-
   ments of ISODE.

AVAILABILITY

   The Xdi software is available via anonymous FTP from
   thumper.bellcore.com in file pub/xdi.tar.Z. Source code and execut-
   ables 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 contactSze-Ying Wuu at
   sywuu@thumper.bellcore.com.
ToP   noToC   RFC1292 - Page 90
NAME

   Xds
   CSIRO Division of Information Technology

LAST MODIFIED

   November, 1991

KEYWORDS

   Dua only, Free, Limited Functionality, Needs ISODE, RFC-1006, Source,
   Sun, X-Windows

ABSTRACT

   Xds is a DUA designed for users who have little or no knowledge of
   X.500. Its intended to be used, for example, by a receptionist who
   has to answer such queries as 'Could I have the telephone number of
   Andrew who works in Research?'. The display is customized for the
   particular organization and the results of the search are presented
   in the format of a business card. It is possible to customize the
   displayed information.

COMPLETENESS

   Xds does not provide user access to all the services provided by
   X.500.  Instead, Xds uses X.500 services to provide the specific
   functions for which it is designed to provide.

   Conforms to section 9 of X.519.

INTEROPERABILITY

   Only tested against the QUIPU (ISODE) DSA.

   No known bugs, but we would be interested in any found. Contact
   Andrew Waugh (ajw@mel.dit.csiro.au)

PILOT CONNECTIVITY

   Not tested.

BUGS

   No known bugs, but we would be interested in any found. Contact
   Andrew Waugh (ajw@mel.dit.csiro.au)
ToP   noToC   RFC1292 - Page 91
CAVEATS AND GENERAL LIMITATIONS

   The user can only bind as the anonymous user.

INTERNETWORKING ENVIRONMENT

   Uses the QUIPU (ISODE 7.0) libraries.

HARDWARE PLATFORMS

   Xds runs on Sun SPARCstations. We have not tested Xds on other
   hardware platforms, but it should run on other hardware which sup-
   ports ISODE-7.0 and X Windows.

SOFTWARE PLATFORMS

   Xds requires ISODE-7.0 and X 11 Version 4 with the Athena Widgets.

AVAILABILITY

   The Xds software will be distributed free to any non-commercial site
   provided

       i)    they do not pass the code on to any other site (rather they
             should ask the other site to contact us directly).

       ii)   they do not make money out of from the use or sale of the
             software.

       iii)  they inform us of any problems or possible improvements
             that they would like to see made.

   Commercial sites should contact us.

   For further information contact:

           Andrew Waugh
           CSIRO Division of Information Technology
           723 Swanston St
           Carlton VIC 3053
           AUSTRALIA

           Phone +61 3 282 2615
           Fax   +61 3 282 2600
           Email ajw@mel.dit.csiro.au
ToP   noToC   RFC1292 - Page 92
NAME

   xdua
   CSIRO Division of Information Technology

LAST MODIFIED

   November, 1991

KEYWORDS

   DUA Only, Free, Multiple Vendor Platforms, Needs ISODE, source, Sun,
   X Window System

ABSTRACT

   The xdua is a DUA designed to be used by DSA managers who have suffi-
   cient X.500 knowledge to manipulate the Directory Information Tree
   (DIT). It's typical use is to maintain the information stored on a
   DSA. The xdua has a Macintosh style interface.  This simplifies
   browsing the DIT hierarchy.  A user can traverse the DIT levels by
   using a standard mouse.  The xdua supports the X.500 operations of
   add, modify, delete, search and show.

COMPLETENESS

   Uses the QUIPU (ISODE) dsap interface to provide the X.500 opera-
   tions.

   Conforms to section 9 of X.519.

INTEROPERABILITY

   Only tested against the QUIPU (ISODE) DSA.

PILOT CONNECTIVITY

   [No information provided--Ed.]

BUGS

   No known bugs, but we would be interested in any found. Contact Brian
   May (Brian.May@mel.dit.csiro.au)

CAVEATS AND GENERAL LIMITATIONS

   The executable code is large as it uses the X11R4 and DiSh libraries.
   The xdua is in the testing phase.
ToP   noToC   RFC1292 - Page 93
INTERNETWORKING ENVIRONMENT

   As supported by ISODE.

HARDWARE PLATFORMS

   The xdua runs on Sun SPARCstations and probably on other hardware
   which supports ISODE-7.0 and X Windows.

SOFTWARE PLATFORMS

   The xdua requires ISODE-7.0 and X 11 Version 4 with the Athena Widg-
   ets and the Xt toolkit.

AVAILABILITY

   We will distribute it free to any non-commercial site provided

       i)    they do not pass the code on to any other site (rather they
             should ask the other site to contact us directly).

       ii)   they do not make money out of from the use or sale of the
             software.

       iii)  they inform us of any problems or possible improvements
             that they would like to see made.
   Commercial sites should contact us directly.  For further information
   contact:

           Brian May
           CSIRO Division of Information Technology
           723 Swanston St,
           Carlton,
           Victoria 3053,
           Australia

           Phone +61 3 282 2613
           Fax   +61 3 282 2600
           Email Brian.May@mel.dit.csiro.au
ToP   noToC   RFC1292 - Page 94
NAME

   XLU
   Brunel University

LAST MODIFIED

   November, 1991

KEYWORDS

   Available via FTAM, Available via FTP, DUA Only, Free, Multiple Ven-
   dor Platforms, Needs ISODE, RFC-1006, Source, UNIX

ABSTRACT

   XLU (X LookUp) is an X.500 DUA interface for the X Window System.
   Developed from POD, XLU can be configured for many different styles
   of interaction. Example configurations are provided for single window
   and multiple window (POD-like) use.

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

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

   At the time of writing (October 1991) XLU was in beta test.

COMPLETENESS

   88 standard:  strong authentication not implemented.

INTEROPERABILITY

   Believed to be compliant, though untested.

PILOT CONNECTIVITY

   DUA Connectivity: In use at Brunel and some other sites in the UK and
   PARADISE pilots.

BUGS

   Bugs to x500@brunel.ac.uk.
ToP   noToC   RFC1292 - Page 95
CAVEATS AND GENERAL LIMITATIONS

   [No information provided--Ed.]

INTERNETWORKING ENVIRONMENT

   TP0 over TCP/IP (and others as ISODE).

HARDWARE PLATFORMS

   Most UNIX machines.

SOFTWARE PLATFORMS

   UNIX
   MIT X libraries (release 11 version 4)
   ISODE/QUIPU libraries (version 7.0 upwards)

AVAILABILITY

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

           Andrew.Findlay@brunel.ac.uk        +44 1 895 274000 x 2512
           Damanjit.Mahl@brunel.ac.uk         +44 1 895 274000 x 2946
           x500@brunel.ac.uk

   Postal Address:

           Andrew Findlay
           Computer Centre
           Brunel University
           Cleveland Road,
           Uxbridge, Middlesex
           UB8 3PH
           United Kingdom

   Anonymous FTP:

           src.brunel.ac.uk
           x500/xlu.tar.Z
ToP   noToC   RFC1292 - Page 96
NAME

   XT-DUA
   X-Tel Services Limited

LAST MODIFIED

   November, 1991

KEYWORDS

   DUA Only, Multiple Vendor Platforms, Needs ISODE-7.0, RFC-1006 X Win-
   dow System, CLNP, X.25, OSI Transport, Sun, Unix, Commercially Avail-
   able.

ABSTRACT

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

   XT-DUA is available in two forms:

           as a browsing tool
           as a management tool

   Browsing features include:

      - 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 applicationEntities eg startup of ftam session.

      - User friendly name for attributes.

      - 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.
ToP   noToC   RFC1292 - Page 97
   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

COMPLETENESS

   XT-DUA provides access to all the X.500 DAP operations.  Protocol
   completeness is as for QUIPU-7.0.

INTEROPERABILITY

   As for the QUIPU-7.0.

PILOT CONNECTIVITY

   Full DUA Connectivity to the X.500 Pilot.

BUGS

   No known bugs.

CAVEATS AND GENERAL LIMITATIONS

   None.

INTERNETWORKING ENVIRONMENT

   As for the QUIPU-7.0.

HARDWARE PLATFORMS

   As for the QUIPU-7.0.

SOFTWARE PLATFORMS

   As for the QUIPU-7.0, with the addition of X Windows and either Motif
   or Open Look.
ToP   noToC   RFC1292 - Page 98
AVAILABILITY

   XT-DUA is commercial software. It is available via ftp.  For more
   details contact:

           Colin Robbins or Graeme Lunt
           X-Tel Services Limited
           University Park
           Nottingham
           NG7 2RD

           DN:             c=GB@o=X-Tel Services Ltd
           Telephone:      +44 602 412648
           Fax:            +44 602 790278
           E-Mail:         x500@xtel.co.uk
ToP   noToC   RFC1292 - Page 99
NAME

   xwp
   Performance Systems International Inc.

LAST MODIFIED

   July, 1991

KEYWORDS

   Commercially Available, DUA Only, Limited Functionality, Multiple
   Vendor Platforms, UNIX, X Window System

ABSTRACT

   xwp is a graphical user interface tailored specifically to provide
   easy access to the Directory for the purposes of performing White
   Pages searches. It is currently in use as one of user interfaces
   available on wp1.psi.net and wp2.psi.net, the two service machines
   for the White Pages Pilot Project.  Implements User-Friendly Naming
   scheme developed in IETF OSI-DS Working Group.

COMPLETENESS

   Compliant with X.500 standards to the extent that the QUIPU implemen-
   tation is.

INTEROPERABILITY

   Successfully interoperates with QUIPU DSAs.

PILOT CONNECTIVITY

   [No information provided--Ed.]

BUGS

   Bugs to ssd-help@psi.com

CAVEATS AND GENERAL LIMITATIONS

   xwp is not a general-purpose DUA. It was designed to be a special-
   purpose front-end for performing White Pages searches and thus, in
   the interests of simplification, does not provide the full range of
   functionality supported by the X.500 standard.
ToP   noToC   RFC1292 - Page 100
INTERNETWORKING ENVIRONMENT

   Runs in a BSD UNIX environment supporting the X Windows System.

HARDWARE PLATFORMS

   Should be capable of running in any BSD UNIX environment that sup-
   ports the X Windows system. No special hardware required beyond that
   required to support X Windows, BSD UNIX and the ISODE.

SOFTWARE PLATFORMS

   Tested under SUNOS 3.x and 4.x; should run under most variants of BSD
   UNIX. Requires X Windows Release 3 or later.

AVAILABILITY

   xwp is a commercial product that may be licensed from PSI Inc. as
   part of PSI's Software Source Distribution (SSD).  Email to

           ssd-info@psi.co

   will elicit an automatic response containing information on the SSD.
   Ordering information may be obtained by sending electronic mail to

           ssd-order@psi.com

   or contacting PSI at

           Performance Systems International Inc.
           11800 Sunrise Valley Drive
           Suite 1100
           Reston, Virginia 22091.

           1.703.620.6651
           1.800.82PSI82 (1.800.827.7482)
           1.703.620.4586 (fax)
ToP   noToC   RFC1292 - Page 101
NAME

   xwp
   University of Wisconsin

LAST MODIFIED

   July, 1991

KEYWORDS

   Free, IBM PC, Multiple Vendor Platforms, Needs ISODE, UNIX, X Window
   System

ABSTRACT

   The xwp program is a simple browser for the QUIPU/X.500 directory.
   It uses OSF/Motif and the X Window System to provide a convenient
   user interface.

   The user interface consists of five different top-level windows: the
   main window, the search window, and three option windows.  The main
   window appears when the program is executed and all others are
   reached through its menus.  The main window contains Current Loca-
   tion, Current Descendents, Descendent Filter, Current Information,
   and Directory Status subwindows.  The contents of these subwindows
   show information about the current location of the browser in the
   directory tree.  The search window contains Search Area, Search
   Filter, and Search Results subwindows.

   The mouse pointer may be used in the main window to change the
   current location of the browser in the directory tree.  We can des-
   cend deeper into the tree by clicking the mouse when it points to a
   member of the Current Descendents list.  Doing this "moves" the
   browser to this new (one level deeper) location in the directory
   tree.  This causes the main window to be updated as follows: (1) the
   selected descendent becomes the new Current Location, (2) its descen-
   dents are listed in Current Descendents, and (3) its contents are
   displayed in Current Information.  Any problems and messages from the
   directory are displayed in the Directory Status portion of the main
   window.  To move the browser up the directory tree (i.e. towards the
   root), click the mouse pointer on one of the components of the
   Current Location.  In this way it is possible to move the browser to
   any location above its current position (i.e. to any ancestor) in one
   mouse click.  Doing this causes the main window to be updated as dis-
   cussed above.  Due to directory-imposed limits, it may not always be
   possible to display all the descendents of the current position.  In
   such cases (and others) it may be useful to impose a filter on the
ToP   noToC   RFC1292 - Page 102
   descendents to be listed.  To do this, position the mouse pointer in
   the Descendent Filter box and use the keyboard to type in the desired
   filter expression.  Typing <RETURN> in this box causes the Current
   Descendents list to be updated using the new filter.

   xwp was developed at the University of Wisconsin - Madison Computer
   Sciences Department. It is used in conjunction with the ECI mail user
   agent project.  xwp was written by Robert Lazarus, III.

COMPLETENESS

   n/a

INTEROPERABILITY

   xwp currently operates with ISODE version 6.0

PILOT CONNECTIVITY

   [No information provided--Ed.]

BUGS

   xwp should be upgraded to the latest version of ISODE/QUIPU.

CAVEATS AND GENERAL LIMITATIONS

   n/a

INTERNETWORKING ENVIRONMENT

   xwp will operate in any environment where Motif, ISODE and QUIPU
   operate.

HARDWARE PLATFORMS

   xwp has been run on IBM PC/RT, soon to run on DecStation 3100.

SOFTWARE PLATFORMS

   Berkeley 4.3 and Ultrix 3.1

AVAILABILITY

   Openly available in May, 1991. Contact hagens@cs.wisc.edu for more
   information.
ToP   noToC   RFC1292 - Page 103
4. References


   [CCITT-88]  CCITT, "Data Communications Networks Directory," Recom-
               mendations 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 Interconnec-
               tion Protocols," Version 2 Edition 1, NIST Special Publi-
               cation 500-162, December 1988.

5. Security Considerations

   Security issues are not discussed in this memo.

6.  Authors' Addresses

   Ruth Lang
   SRI International
   333 Ravenswood Ave.
   Menlo Park, CA  94025
   (415) 859-5608
   rlang@nisc.sri.com

   Russ Wright
   Lawrence Berkeley Laboratory
   1 Cyclotron Road
   Berkeley, CA 94720
   (415) 486-6965
   wright@lbl.gov