1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
|
INTERNET-DRAFT Leif Johansson
Intented Category: Experimental Stockholm University
A directory (X.500 and LDAPv3) schema for Berkely automounter
1. Status of this Memo
This memo describes a directory (LDAP or X.500) schema for storing amd (Berkely-
style automounter) mount info maps. The schema is currently beeing supported by
the (beta version of the) am-utils version 6 package [AMUTILS].
2. Overview and Rationale
Directory services such as X.500 [X500] or LDAP [RFC2251] are a natural choice of
repository for amd mount map databases. All Object Identifiers in this document
are prefixed by amdSchema-id to be assigned later. The relation between this
schema and the automount schema elements in [HOWARD] are mostly superficial. The
model for the elements in [HOWARD] was the SUN automounter which has quite a
different syntax for mount maps. Furthermore the intended usage of this schema
differs from that of [HOWARD] in many respects.
3. DSA requirements
Directory servers implementing this schema SHOULD maintain the modifyTimestamp
operational attribute. If not the amdMapCacheTtl attribute SHOULD be set to 0
indicating to clients that caching of map entries SHOULD be turned off. Clients
wishing to use the amdMap schema MAY use the modifyTimestamp information to set
the ttl for internal caching schemes. A value of 0 for the amdMapCacheTtl must
result in clients turning off any local caching.
4. Syntax definitions
The following attribute syntax is defined in this document:
amdlocationlist
This syntax represents a amd map value. This is the syntax expressed in BNF using
definitions from [RFC2252]:
amdlocationlist = amdlocationselection |
amdlocationlist whsp "||" whsp amdlocationselection
amdlocationselection = amdlocation |
amdlocationselection whsp amdlocation
Johansson [Page 1]
Internet draft Berkeley AMD LDAP Schema 30 March 1998
amdlocation = amdlocationinfo |
"-" amdlocationinfo |
"-"
amdlocationinfo = seloropt |
amdlocationinfo ";" seloropt |
";"
seloropt = seletion |
optass
selection = keystring "==" printablestring
keystring "!=" printablestring
optass = keystring
X.500 servers or LDAPv3 servers (supporting the binary attribute option) may use
the following syntax definition:
AmdLocationList ::= SEQUENCE OF {
SEQUENCE OF {
location AmdLocation
}
}
AmdLocation ::= SET OF {
CHOICE {
location [0] AmdLocationInfo
notlocation [1] AmdLocationInfo
not [2] NULL
}
}
AmdLocationInfo ::= SET OF {
CHOICE {
selection [0] AmdSelection
option [1] AmdOption
}
}
AmdSelection ::= CHOICE {
eq [0] AttributeAndValue
ne [1] AttributeAndValue
}
AmdOption ::= AttributeAndValue
AttributeAndValue ::= SEQUENCE {
attribute IA5String
Johansson [Page 2]
Internet draft Berkeley AMD LDAP Schema 30 March 1998
value IA5String
}
5. Attribute types
The following attribute types are defined in this document:
amdMapName
amdMapCacheTtl
amdMapEntry
amdMapEntryKey
amdMapEntryValue
amdSchema-a OBJECT IDENTIFIER ::= { amdSchema-id 1 }
amdMapName ATTRIBUTE ::= {
WITH SYNTAX IA5String
EQUALITY MATCHING RULE caseIgoreExactMatch
--ID { amdSchema-a 1 }
DESCRIPTION
"This attribute is the symbolic and in the naming
context unique name of an amd map. This corresponds
in the case of a flat file database to the name of
the file or the mount-point of the map."
}
amdMapCacheTtl
ATTRIBUTE ::= {
WITH SYNTAX Integer
EQUALITY MATCHING RULE integerExactMatch
--ID { amdSchema-a 2 }
SINGLE VALUED
DESCRIPTION
"The maximum time-to-live for the entries in this
map. After this many milliseconds the map has to
be cleared from local caches and reloaded. A value
of 0 disables caching."
}
amdMapEntry
ATTRIBUTE ::= {
WITH SYNTAX DistinguishedName
EQUALITY MATHCING RULE dNCaseIgnoreExactMatch
--ID { amdSchema-a 3 }
DESCRIPTION
"A multivalued attribute listing the distinguished
names of the amdMapEntries making up this amdMap
Johansson [Page 3]
Internet draft Berkeley AMD LDAP Schema 30 March 1998
object."
}
amdMapEntryKey ::= {
ATTRIBUTE ::= {
WITH SYNTAX IA5String
EQUALITY MATCHING RULE stringExactMatch
--ID { amdSchema-a 4 }
SINGLE VALUED
DESCRIPTION
"The value of this attribute is usually the name of
a mountpoint for this amdMapEntry."
}
amdMapEntryValue ::= {
ATTRIBUTE ::= {
WITH SYNTAX AmdLocationList
--ID { amdSchema-a 5 }
DESCRIPTION
"This is the actual mount information for the amdMapEntry
using the syntax described above."
}
amdMapEntryKey ::= {
ATTRIBUTE ::= {
WITH SYNTAX IA5String
EQUALITY MATCHING RULE stringExactMatch
--ID { amdSchema-a 4 }
SINGLE VALUED
DESCRIPTION
"The value of this attribute is usually the name of
a mountpoint for this amdMapEntry."
}
amdMapEntryValue ::= {
ATTRIBUTE ::= {
WITH SYNTAX AmdLocationList
--ID { amdSchema-a 5 }
DESCRIPTION
"This is the actual mount information for the amdMapEntry
using the syntax described above."
}
6. Object classes
The following object classes are defined in this document:
amdMap
Johansson [Page 4]
Internet draft Berkeley AMD LDAP Schema 30 March 1998
amdMapEntry
defined as follows:
amdSchema-oc ::= { amdSchema-id 2 }
amdMap OBJECT-CLASS ::= {
SUBCLASS OF { top }
KIND auxiliary
--ID { amdSchema-oc 1 }
MAY CONTAIN { amdMapCacheTtl , cn }
MUST CONTAIN { amdMapName , amdMapEntry }
}
amdMapEntry OBJECT-CLASS ::= {
SUBCLASS OF { top }
KIND structural
--ID { amdSchema-oc 2 }
MUST CONTAIN {
amdMapName ,
amdEntryKey ,
amdEntryValue ,
} MAY CONTAIN
{ cn } DESCRIPTION "An entry of this
object class describes mount information relative to a
certain amdMap entry"
}
7. Examples
8. Security Considerations
Due to the security problems posed by NFS care should be taken not to advertise
exported filesystems. Therefore it is often desirable to limit access to entries
carrying amd mount map information to those systems to which the corresponding
filesystems have been exported.
9. References
[AMUTILS]
am-utils homepage: http://shekel.cs.columbia.edu/~erez/am-utils.html
[RFC2251]
M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access
Protocol (v3)", RFC 2251, December 1997.
Johansson [Page 5]
Internet draft Berkeley AMD LDAP Schema 30 March 1998
[RFC2252]
M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight Directory
Access Protocol (v3): Attribute Syntax Definitions", RFC 2252,
December 1997.
[RFC2253]
M. Wahl, S. Kille, T. Howes, "Lightweight Directory Access
Protocol (v3): UTF-8 String Representation of Distinguished
Names", RFC 2253, December 1997.
[HOWARD]
Luke Howard, "An Approach for Using LDAP as a Network
Information Service", draft-howard-nis-schema-??.txt, Internet
draft.
[X500]
ITU something or other.
Author's Address
Leif Johansson
Department of Mathematics
Stockholm University
S-106 91 Stockholm
SWEDEN
Email: leifj AT matematik.su.se
Johansson [Page 6]
|
