The following topics may be obtained from the info-server using a request in the form: request: dirpilot topic: For example: From: Joe.Soap@somedomain To: info-server@uk.ac.ucl.cs Subject: Anything you like request: dirpilot topic: minutes1.txt This archive contains documents ... FILENAME.txt for plain text format FILENAME.ps for postscript FILENAME.ms for troff -ms Note that not all the files are available in all the formats. ... and also some shar files of scripts and small bits of source. Look in the directory for ISODE itself and any updates to the main source tree. FILENAME.shar for shar files The files are also available by NIFTP and FTAM. FTAM to 00000511160013, username = anon, no password NIFTP to uk.ac.ucl.cs, binary mode, username = guest, password = (Your mail address in the form user@site) filenames should be prepended with (Note that the angle brackets and capital letters are vital) ------------------------------------------------------------------------ DIRECTORY GROUP MINUTES minutes1 Minutes of 1st directory group meeting - 7/10/88 minutes2 Minutes of 2nd directory group meeting - 31/1/89 minutes3 Minutes of 3rd directory group meeting - 19/4/89 minutes4 Minutes of 4th directory group meeting - 12/7/89 minutes5 Minutes of 5th directory group meeting - 23/10/89 minutes6 Minutes of 6th directory group meeting - 24/1/90 minutes7 Minutes of 7th directory group meeting - 2/5/90 minutes8 Minutes of 8th directory group meeting - 5/9/90 minutes9 Minutes of 9th directory group meeting - 10/12/90 minutes10 Minutes of 10th directory group meeting - 21/3/91 minutes11 Minutes of 11th directory group meeting - 13/6/91 Meeting minutes are available in plain text only. -------------------------------------------------------------------------- BUG DATABASE AT XTEL bugdatabase A BUG database for both QUIPU and PP has been set up. This will enable you to find out if the problem you are experiencing with ISODE, QUIPU or PP is a known problem. If it is a known problem, advice on how to fix it is given where possible. If your problem is not listed in the database it should be reported to jnt-quipu@uk.co.xtel. Available in plain text only -------------------------------------------------------------------------- PREPARING A BID FOR HARDWARE TO JOIN THE PILOT bid This note gives advice to sites who wish to participate in the Directory Pilot about: o What to put in their bid? o What the onus is on a participating site? Available in plain text only ------------------------------------------------------------------------ PILOT HARDWARE O/R hwor This note details the operational requirement for the hardware purchased by the JNT (funded by the Computer Board) to run X.500 Directory software and an Electronic Mail protocol convertor at a number of U.K. academic sites. Available in postscript and plain text. ------------------------------------------------------------------------ PILOT HARDWARE hwlist Pilot hardware check list Available in plain text only. ------------------------------------------------------------------------ SUN MAINTENANCE sunmaint This very brief note advises on the maintenance arrangements you should take up with SUN. Available in plain text only. ------------------------------------------------------------------------ DIRECTORY SYSTEM CONFIGURATION pilconfig The "Directory System Configuration Guide" This document is a hardware and software configuration guide for UK academic sites participating in the Directory Pilot. This document was written wrt ISODE-6.0. It is still a useful set of guidelines but cannot be used reliably with later versions of the code. Available in plain text, postscript and troff -ms --------------------------------------------------------------------------- X.25 WIRING DIAGRAMS cable2 Cable spec for "SUN MCP TO X.21 TRUE DTE" cable3 Cable spec for "SUN MCP to true X.21 DCE" (e.g. TelePAC) Available in postscript only --------------------------------------------------------------------------- SUN MONITOR BODGE PLUG sunmonitor This note gives a wiring diagram for a special plug which can be used which allows disconnection of the SUN's console terminal. Available in plain text only -------------------------------------------------------------------------- SUN BINDER LABELS binder Postscript for Sun 4.0 binder labels Available in postscript only -------------------------------------------------------------------------- NOTES ON USE OF THE PATCH PROGRAM patch This note explains how to use the patch program, which is a program that makes installing source code patches straightforward. Notes are also included on how to obtain the source for patch. Available in plain text only ------------------------------------------------------------------------- CONFIGURING IXI ADDRESSES ixi This note (written by Colin Robbins of X-Tel) details how to configure your DSA to listen on an IXI address. A number of small modifications are required to ISODE and Quipu tailor files. Available in plain text only ------------------------------------------------------------------------- QUIPU LOG TAILORING logrecs "Tailoring Quipu's logging" This note makes recommendations on configuring the logging produced by Quipu DSAs in the UK academic pilot. A suggested location is given for the Quipu log files. In addition, advice is given on the suggested level of logging. This is critical, as it will allow UCL's log processing scripts to be run unaltered. The comments in this note specifically apply to sites running the UK pilot default set-up, but should be meaningful to other sites running Quipu. The log file locations and logging levels recommended herein are set up in the revised system configuration scripts, which will be available from May, 1990. Available in plain text, postscript and troff -ms ------------------------------------------------------------------------ PREPARING DATA FOR X.500 prepare "Preparing data for inclusion in an X.500 Directory" This note is intended to be a practical guide on preparing data for inclusion in the the U.K. Academic X.500 Directory Pilot. While the focus is on the U.K. Pilot, much of the document has general applicability to both academic and commercial sites, in particular those sites running the Quipu X.500 system. This note is intended to augment the information in the Quipu manual [1], and also to make some of the information therein more digestible. However this note falls far short of being a replacement for the manual, and Directory administrators will still need to refer to the Quipu manual for detail. Some of the discussion that follows refers to general X.500 issues, while other parts, for example those on access control and EDB files, necessarily refer specifically to the Quipu system. Aspects discussed include: the depth of the Directory Information Tree; choice of Relative Distinguished Names; selected object classes and attribute types; Quipu access control lists; format of EDB files. A number of example entries are specified to clarify the points discussed. Available in postscript and troff -ms (troff also requires files hyptree.pic and schema.pic) Available without diagrams in plain text as file "prepnopic.txt" --------------------------------------------------------------------------- QUIPU TIMEOUTS timeouts A brief explanation of the timeouts used by the Quipu system Available in plain text only --------------------------------------------------------------------------- IS OUR DSA VISIBLE? dsavisible A set of dish commands which allow a site to ascertain whether their DSA is visible to at least some of the rest of the world Available in plain text only --------------------------------------------------------------------------- TENDER FOR DIRECTORY SUPPORT tender Invitation to tender for Directory Pilot support contract Available in plain text only ------------------------------------------------------------------------- BRUNEL DUA PROJECT EXTENSION PROPOSAL brunprop The Computer Board issued a contract to Brunel in 1989 to develop some user interfaces for the X.500 directory. The designs which have evolved following experimentation and consultation are more ambitious than those originally envisaged. Thus, an extension to the original contract is proposed. Available in plain text only ------------------------------------------------------------------------- DATA PROTECTION ACT dpa Summary of the discussions related to the Data Protection Act. Extracts from meeting minutes Available in plain text, postscript and troff -ms -------------------------------------------------------------------------- BRUNEL X INTERFACE DESIGN xdir Design document for the Brunel X windows DUA Available in postscript only -------------------------------------------------------------------------- DESIGN FOR A SIMPLE-TO-USE INTERFACE de This paper describes a user interface to the OSI Directory. Although there are a considerable number of user interfaces already available, system administrators have complained that none of these interfaces is specifically intended for use as a "public access" interface. Such an interface must be very simple to use. This requirement leads to a set of key design goals: when there is a conflict of aims, simplicity must be favoured over functionality; ergonomic issues are of vital importance; the on-line help system must be simple but comprehensive. The search strategy employed by the interface is also discussed in some detail. The way that the strings provided by the user are mapped onto sets of X.500 operations and matched with Directory entries is described. The development of this interface has been funded by the PARADISE project, which in turn is funded by COSINE. PARADISE has a number of goals, including the coordination of directory service pilots. In addition, PARADISE is providing a number of central services, one of which is a public access interface to the Directory. Available in plain text and postscript --------------------------------------------------------------------------- USER-FRIENDLY NAMING ufn This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. This then leads to a specification of a standard format for representing names, and to procedures to resolve them. Available in plain text and postscript --------------------------------------------------------------------------- MANAGING MULTIPLY SOURCED DATA IN AN X.500 DIRECTORY manage X.500 Directories will not often be used as the master source of data until such directories are much longer established, and the technology trusted. Until then there will remain the substantial problem of keeping an X.500 Directory up-to-date from a number of sources. Usually the volume of data will require that maintenance procedures are as automated as possible. However, naive procedures will not suffice for a number of reasons: different sources will name the same object differently; different sources will name different objects the same; the data obtained from these sources may overlap to some extent, though one source may be regarded as more authoritative than another. This paper draws primarily upon experience gained from piloting ECMA TR32 and X.500 directory services as part of the THORN project's Large Scale Pilot Exercise. The tools developed for THORN, and the problems with them, are discussed. It is recognised that a complete solution to these data merging and updating problems will be quite complex, and such a solution is not essayed here. Instead, this paper proposes some pragmatic solutions to the majority of the problems. It is anticipated that further understanding of the problems will result from experimentation with implementations of the tools described herein. Available in postscript only --------------------------------------------------------------------------- MANAGEMENT IN QUIPU mgt This document (by Steve Kille) is a design plan for Management Extensions of the QUIPU Directory System [Kil88]. Management of the Directory is an increasing problem as pilot operation scales. This document describes a number of tools which will be developed. The aim here of this work is to manage the Directory and its configuration, but not the data in it. The latter is is an equally important, but rather separate issue. The problems of directory management are not well understood, and so this specification has many research aspects. The design is expected to evolve in the light of experience. Some parts of this design have been implemented. Available in postscript only --------------------------------------------------------------------------- ARTICLES ON X.500 WRITTEN FOR COLLEGE MAGAZINES uclnews An article submitted to UCL News (a glossy college magazine) hwadvert An article published in Heriot-Watt's Computing Services newsletter bathnews An article published in BUCS newsletter Available in plain text only -------------------------------------------------------------------------- MANUAL PAGE FOR THE PSI X WHITE PAGES INTERFACE xwp Manual page for Marshall Rose's new white pages interface to the Directory, which runs under X windows. Available in plain text only -------------------------------------------------------------------------- UP-TO-DATE REPORTS ON THE SIZE OF THE DIT dit No. of entries curently in the DIT. The report is organised on a per country, per organisation basis. This version does NOT include the animals! dit-dsa No. of entries curently in the DIT. The report is organised on a per country, per dsa basis. This version DOES include the animals! Available in postscript only -------------------------------------------------------------------------- X.500 USER INTERFACE DESIGN cardiff-89 This is a paper that was presented by Andrew Findlay at Cardiff UKUUG, 1989. It describes the early stages of user interface design. Available in postscript only -------------------------------------------------------------------------- SETTING UP AN X.500 DIRECTORY SERVICE nice-90 This is a paper that was presented by Andrew Findlay at Nice EUUG, 1990. It discusses a number of issues: in particular it discusses data gathering and data management. Available in postscript only -------------------------------------------------------------------------- DESIGNING AN X.500 USER INTERFACE: ONE YEAR IN camb-90 This is a paper by the team at Brunel which was presented at the 1990 UKUUG at Cambridge. It reports on developments over the past year. Several interfaces are described, including the current X Window and MS-Windows implementations. Available in postscript only -------------------------------------------------------------------------- OSIWOTSITS SIMPLE DUA osiwotsits.shar The osiwotsits are an attempt at a minimal DUA for everyday users who just want the odd piece of (mainly local) information. Phone numbers, e-mail addresses, photos and "everything" are chosen to satisfy most people now. This is easily changed should tastes become more exotic. This software is now in version 2.0 and works over ISODE-7.0 This is a shar file -------------------------------------------------------------------------- DSC - PUBLIC ACCESS DUA dsc.shar dsc is an interface to the X.500 Directory which was originally designed as an X.29 public access interface for use at UCL. It offers two modes of usage: easy and advanced. The "easy" interface is a specially written dish (DIrectory SHell) script. It only searches within the UK - this was done to keep the number of questions and the format of the input as simple as possible. Clearly the interface could be tweaked to allow a wider scope of querying. This script assumes that the dish binaries are already installed. The "advanced" interface is Brunel University's sd interface, which is freely available from them. Obviously another interface could be used if desired, although the help text would need to be rewritten. This script assumes that the sd interface has already been installed. This is a shar file ---------------------------------------------------------------------- DSASTATS - LOG PROCESSING SCRIPT dsastats.shar dsastats is a script which processes the log file produced by a quipu DSA of normal operation. This file is by default called quipu.log, which is by default written to the /usr/tmp directory. The script produces a summary of usage of a DSA. This is a shar file -------------------------------------------------------------------------- DM - DATA MANAGEMENT TOOLS dm.shar Some simple tools to handle some of the problems of managing Directory data. The tools detect differences between two sets of data and apply the changes to the directory (a dish script is created to effect this changes). The tools require that the data is in a format which is very similar, but not identical, to EDB format. This is a shar file -------------------------------------------------------------------------- PRINTED PHONE DIRECTORY pbook This note describes the data structures required, and the software used, to print a telephone directory from data held in an X.500 Directory. Available in postscript only -------------------------------------------------------------------------- THE UK COSINE X.500 DIRECTORY PILOT ukcosine This note describes the UK COSINE X.500 Directory Pilot, how organisations can become involved in the pilot, the services offered to sites wishing to participate in the pilot and the steps that need to taken to become connected into the pilot directory information tree. Available in plain text, postscript and troff -ms -------------------------------------------------------------------------- X.500 PRODUCT AND PUBLIC DOMAIN IMPLEMENTATION SURVEY survey Survey put together by DISI - a US Directory and Information Services group. Available in plain text only -------------------------------------------------------------------------- TUTORIAL ON ISODE DAEMONS daemons The slides used in a tutorial on ISODE's daemons. This talk was first presented by Colin Robbins to the U.K. Academic Directory Group at the October 1991 meeting. Available in postscript only