![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to q-introduction.tex CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / manual|
Return to q-introduction.tex CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / manual |
1.1 root 1: % run this through LaTeX with the appropriate wrapper
2:
3: \chapter {Overview of QUIPU}
4:
5: \section {Summary}
6:
7: QUIPU is a Public Domain implementation of the OSI Directory as
8: specified in CCITT X.500 Recommendations /
9: ISO 9594 for Directory Services \cite{ISO.Directory}
10: \cite{CCITT.Directory}.
11: It is intended to provide an environment for experimentation and for early
12: pilots using Standardised Directory Services. QUIPU is currently aligned to
13: the CCITT X.500 Recommendations (unofficial version). This is expected to
14: be technically identical to the ISO IS. The latest available ISO version is
15: the DIS.
16:
17: Quipu is intended to provide an environment
18: for early experimentation with standardized Directory services.
19: It is used by the ISODE for identification of the location of OSI
20: applications (including QUIPU) and for provision of white and yellow
21: page services.
22: The Directory Abstract Service and DSA Abstract Service
23: defined in \cite{CCITT.Directory,ISO.Directory} and their associated
24: protocols are supported.
25:
26:
27: Major aspects of the QUIPU implementation are:
28: \begin{itemize}
29: \item
30: Use of memory structures to provide fast access
31: \item
32: Activity scheduling within the DSA to allow for multiple accesses
33: \item
34: General and flexible searching capabilities
35: \item
36: Extensions to provide access control
37: \item
38: External schema management
39: \item
40: Use of the Directory to control Distributed Operations
41: \end{itemize}
42:
43: The current implementation provides a DSA, and a procedural interface to the
44: Directory Abstract Service, which will enable other applications to use the
45: Directory.
46: There is also a DIrectory SHell interface --- DISH. This provides full
47: access to the Directory Abstract Service, using the procedural interface.
48: Standard Distributed Operations are used with both referrals and chaining
49: (using the Directory System Protocol) provided.
50:
51: \ifnum\volnum=5
52: A full discussion of the design issues relating to QUIPU can be
53: found in \cite{QUIPU.Design}.
54: \fi
55:
56: \section {Pronouncing QUIPU}
57:
58: The name of the INCA Directory is QUIPU.
59: The official pronunciation of QUIPU takes two syllables:
60: {\em kwip-ooo}.
61:
62: \section {Why QUIPU}
63:
64: QUIPU was originally developed as a part of the INCA project.
65: The Inca of Peru did not have writing. Instead, they stored information on
66: strings, carefully knotted in a specific manner and with coloured thread, and
67: attached to a larger rope.
68: These devices were known as {\em Quipus}.
69: The encoding was obscure, and could only be read by selected trained people:
70: the {\em Quipucamayocs}.
71: The Quipu was a key component of Inca society, as it contained information
72: about property and locations throughout the extensive Inca empire.
73:
74:
75: \section {Objectives}
76:
77: \subsection {General Aims}
78:
79: QUIPU has a number of general aims:
80:
81: \begin{itemize}
82: \item To produce an implementation which follows the
83: emerging OSI Directory standards.
84:
85: \item Flexibility to enable the system to be used
86: for experimentation and research into problems relating to Directory Service.
87:
88: \item Investigation of distribution and replication
89:
90: \item Pilot experimental usage.
91: \end{itemize}
92:
93: \subsection {Technical Goals}
94:
95: The major goals of the QUIPU Directory Service are:
96:
97: \begin{itemize}
98: \item
99: Full support of the Directory Access Protocol,
100: Directory System Protocol and Distributed Operations, as
101: defined in \cite{CCITT.Directory}.
102: \item
103: Support of the majority of the service elements specified in
104: \cite{CCITT.Directory}.
105: \item
106: Ability for interworking with other Directory implementations, including
107: use of
108: referrals and chaining.
109: \item
110: Very full searching and matching capabilities, beyond the minimum
111: required by \cite{CCITT.Directory}.
112: \end{itemize}
113:
114: The following are not goals:
115:
116: \begin{itemize}
117: \item
118: In practice, the memory based approach has led to a quite fast lookup and
119: searching.
120: \item
121: The ability to handle very large volumes of data (e.g., greater than 100~MB
122: or 1 Million entries per DSA) is not a requirement.
123: \item
124: Substantial data robustness is not required: there is no need to employ
125: complex data backup techniques.
126: \item
127: Use (as opposed to provision) of Authentication services.
128:
129: \end{itemize}
130:
131: \section {Roadmap}
132:
133: This manual is split into 6 parts.
134: You are reading Part I, which is a general introduction.
135: Part II describes a set of user interfaces (DUAs) developed as part of
136: Quipu.
137: Part III, an administrators guide, describes how to set up both the
138: DUAs introduced in Part II, and how the install and manage a Quipu Directory
139: System Agent (DSA).
140: Part IV is a programmers guide which discusses a procedural interface to the
141: directory for those of you who want to write your own DUAs.
142: Part V is a discussion of some of the design issues not already
143: covered elsewhere; this is essentially included for those of you who are
144: interested in the DSA implementation.
145: Finally, Part VI contains Appendices.
146:
147: \section {QUIPU Support Address}\label{quipu:support}
148:
149: If you have any problem installing QUIPU,
150: following the documentation
151: or any other QUIPU related problems, then there are two
152: discussion lists.
153:
154: Comments concerning the operation of
155: QUIPU should be addressed to the QUIPU support address:
156: \[\begin{tabular}{ll}
157: Internet Mailbox:& \tt [email protected] \\
158: Janet Mailbox:& \tt [email protected] \\
159: X.400 Mailbox:& \tt surname = quipu-support \\
160: & \tt ou = cs \\
161: & \tt Org = UCL \\
162: & \tt PRMD = UK.AC \\
163: & \tt ADMD = Gold 400 \\
164: & \tt C = GB
165: \end{tabular}\]
166: Or, you could look up the mailbox attribute of
167: \[\begin{tabular}{l}
168: \tt c=GB \\
169: \tt o=University College London \\
170: \tt ou=Computer Science \\
171: \tt cn=Quipu-Support
172: \end{tabular}\]
173: in the Directory!!!
174:
175: There is also a discussion list for a general discussion of topics
176: related to QUIPU; the address is as above, but with ``quipu-support''
177: replaced by just ``quipu''.
178: We suggest that everybody who is intending to run QUIPU should be on this
179: list, as this will be used to keep you informed of what is happening.
180: Details of updates will also be sent to this list.
181:
182: To be added to the \verb"quipu" discussion list, send a message to
183: ``quipu-request''.
184:
185: \section {Acknowledgements}
186:
187: QUIPU was developed at the Department of Computer Science at University
188: College London, under the {\ae}gis of the INCA\index{INCA} (Integrated Network
189: Communication Architecture) project, which is project~395
190: of ESPRIT\index{ESPRIT} (European Strategic Programme for Research into
191: Information Technology). The partners of INCA (GEC plc\index{GEC plc},
192: Olivetti\index{Olivetti}, Nixdorf AG\index{Nixdorf AG},
193: and Modcomp GmbH\index{Modcomp GmbH}) are acknowledged for releasing this
194: software into the public domain.
195:
196: Continued funding of QUIPU as Openly Available Software is provided by the
197: Joint Network Team (JNT)\index{JNT}.
198:
199: QUIPU 6.0 was implemented
200: primarily by Colin Robbins\index{Robbins, Colin J.}
201: and Alan Turland\index{Turland, Alan}.
202: with considerable help from Marshall Rose\index{Rose, Marshall T.} of
203: NYSERNet Inc.
204: Mike Roe, \index{Roe, Mike} implemented the authentication code.
205:
206: Chris Moore\index{Moore, Christopher W.} of
207: The Wollongong Group helped considerably in the early development
208: of QUIPU, and integration with ISODE.
209: Simon Walton\index{Walton, Simon} of University College London,
210: also provided much help in integrating the software with ISODE.
211:
212: Steve Titcombe\index{Titcombe, Steve}, of
213: University College London, did much
214: of the early work on DISH.
215: Andrew Eliasz\index{Eliasz, Andrew} of University College London developed the SUNINT interface.
216: Paul Sharpe\index{Sharpe, Paul}, of GEC Hirst Research Laboratories
217: put considerable effort into the development of WIDGET.
218:
219: Stella Page \index{Page, Stella} and Alastair
220: Hickling \index{Hickling, Alastair} of University College London
221: helped considerably with testing the software and proof reading this manual.
222: George Michaelson\index{Michaelson, George}
223: of the Department of Computer Science at the University of Melbourne in
224: Australia and Julian P.~Onions\index{Onions, Julian},
225: at the Department of Computer Science at Nottingham University, both ran
226: early versions of the system, and provided much useful feedback.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.