3 # These come from RFC1274 and are in ASN.1 syntax. They have been
4 # translated with some imagination. Only attributes and classes we
5 # already had are here. In general, the matching rules in the
6 # attribute types are incomplete or incorrect and have to be checked.
8 # Note: It seems that the pilot schema evolved beyond what was
9 # described in RFC1274. It also seems that Umich followed the changes
10 # but we don't know where are documented. More worrisome is that it
11 # seems that Netscape does not know either. Searches on Altavista
12 # have not shed any light, so we will have to ask for help.
14 # This file uses definitions from core.schema
16 # ccitt.data.pss.ucl.pilot ( 0.9.2342.19200300.100 )
17 # 1 pilotAttributeType
18 # 3 pilotAttributeSyntax
22 # Believe it or not, this is case-insensitive
24 attributetype ( 0.9.2342.19200300.100.1.2 NAME 'textEncodedORAddress'
25 EQUALITY caseIgnoreMatch
26 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
28 attributetype ( 0.9.2342.19200300.100.1.3 NAME ( 'mail' 'rfc822Mailbox' )
29 EQUALITY caseIgnoreIA5Match
30 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{256} )
32 attributetype ( 0.9.2342.19200300.100.1.4 NAME 'info' EQUALITY caseIgnoreMatch
33 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
35 attributetype ( 0.9.2342.19200300.100.1.5 NAME ( 'drink' 'favouriteDrink' )
36 EQUALITY caseIgnoreMatch
37 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
39 attributetype ( 0.9.2342.19200300.100.1.6 NAME 'roomNumber'
40 EQUALITY caseIgnoreMatch
41 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
43 attributetype ( 0.9.2342.19200300.100.1.7 NAME 'photo'
44 SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 )
46 attributetype ( 0.9.2342.19200300.100.1.8 NAME 'userClass'
47 EQUALITY caseIgnoreMatch
48 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
50 attributetype ( 0.9.2342.19200300.100.1.9 NAME 'host'
51 EQUALITY caseIgnoreMatch
52 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
54 attributetype ( 0.9.2342.19200300.100.1.10 NAME 'manager'
55 EQUALITY distinguishedNameMatch
56 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
58 attributetype ( 0.9.2342.19200300.100.1.11 NAME 'documentIdentifier'
59 EQUALITY caseIgnoreMatch
60 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
62 attributetype ( 0.9.2342.19200300.100.1.12 NAME 'documentTitle'
63 EQUALITY caseIgnoreMatch
64 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
66 attributetype ( 0.9.2342.19200300.100.1.13 NAME 'documentVersion'
67 EQUALITY caseIgnoreMatch
68 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
70 attributetype ( 0.9.2342.19200300.100.1.14 NAME 'documentAuthor'
71 EQUALITY distinguishedNameMatch
72 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
74 attributetype ( 0.9.2342.19200300.100.1.15 NAME 'documentLocation'
75 EQUALITY caseIgnoreMatch
76 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
78 attributetype ( 0.9.2342.19200300.100.1.20 NAME ( 'homeTelephoneNumber' 'homePhone' )
79 EQUALITY telephoneNumberMatch
80 SUBSTR telephoneNumberSubstringsMatch
81 SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 )
83 attributetype ( 0.9.2342.19200300.100.1.21 NAME 'secretary'
84 EQUALITY distinguishedNameMatch
85 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
87 # Netscape defines this with syntax 1.15 TBC
89 attributetype ( 0.9.2342.19200300.100.1.22 NAME 'otherMailbox'
90 SYNTAX 1.3.6.1.4.1.1466.115.121.1.39 )
92 # Netscape defines this with syntax 1.15 TBC
93 # Mathcing rules for this are unknown
95 attributetype ( 0.9.2342.19200300.100.1.23 NAME 'lastModifiedTime'
96 SYNTAX 1.3.6.1.4.1.1466.115.121.1.53 )
98 attributetype ( 0.9.2342.19200300.100.1.24 NAME 'lastModifiedBy'
99 EQUALITY distinguishedNameMatch
100 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
102 # This is the definition as defined in RFC2247
103 # Terrific, we don't know about caseIgnoreIA5SubstringsMatch
105 # See RFC2247 define in core.schema
106 #attributetype ( 0.9.2342.19200300.100.1.25 NAME 'dc'
107 # EQUALITY caseIgnoreIA5Match
108 # SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )
110 # This is aRecord in RFC1274. However, objectclass dNSDomain as we
111 # and Netscape use it is very different.
113 attributetype ( 0.9.2342.19200300.100.1.26 NAME 'dNSRecord'
114 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
116 # 0.9.2342.19200300.100.1.27 was probably intended to be mDRecord in
117 # RFC1274, but they got it wrong and did not define it, thought it
118 # is referenced by dNSDomain in it.
120 # 0.9.2342.19200300.100.1.28 was mXRecord in RFC1274
121 # 0.9.2342.19200300.100.1.29 was nSRecord in RFC1274
122 # 0.9.2342.19200300.100.1.30 was sOARecord in RFC1274
123 # 0.9.2342.19200300.100.1.31 was cNAMERecord in RFC1274
125 #attribute ( 0.9.2342.19200300.100.1.37 NAME 'associatedDomain'
126 # EQUALITY caseIgnoreIA5Match
127 # SUBSTR caseIgnoreIA5SubstringsMatch
128 # SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
130 attributetype ( 0.9.2342.19200300.100.1.38 NAME 'associatedName'
131 EQUALITY distinguishedNameMatch
132 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
134 # Netscape gives syntax 1.15 to this. TBC
135 # We take the matching rules from postalAddress in RFC2256
136 # Show stopper: we don't have the definition of caseIgnoreListSubstringsMatch
138 attributetype ( 0.9.2342.19200300.100.1.39 NAME 'homePostalAddress'
139 EQUALITY caseIgnoreListMatch
140 SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 )
142 attributetype ( 0.9.2342.19200300.100.1.40 NAME 'personalTitle'
143 EQUALITY caseIgnoreMatch
144 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
146 attributetype ( 0.9.2342.19200300.100.1.41 NAME ( 'mobileTelephoneNumber' 'mobile' )
147 EQUALITY telephoneNumberMatch
148 SUBSTR telephoneNumberSubstringsMatch
149 SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 )
151 attributetype ( 0.9.2342.19200300.100.1.42 NAME ( 'pagerTelephoneNumber' 'pager' )
152 EQUALITY telephoneNumberMatch
153 SUBSTR telephoneNumberSubstringsMatch
154 SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 )
156 attributetype ( 0.9.2342.19200300.100.1.43 NAME ( 'co' 'friendlyCountryName' )
157 EQUALITY caseIgnoreMatch
158 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
160 attributetype ( 0.9.2342.19200300.100.1.44 NAME 'uniqueIdentifier'
161 EQUALITY caseIgnoreMatch
162 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
164 attributetype ( 0.9.2342.19200300.100.1.45 NAME 'organizationalStatus'
165 EQUALITY caseIgnoreMatch
166 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
168 attributetype ( 0.9.2342.19200300.100.1.46 NAME 'janetMailbox'
169 EQUALITY caseIgnoreIA5Match
170 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
172 # Netscape gives syntax 1.27 (integer). However, 1.32 is only listed
173 # in RFC2252 without explanation. The SINGLE-VALUE thing comes from
174 # Netscape and is not backed by RFC1274.
176 attributetype ( 0.9.2342.19200300.100.1.47 NAME 'mailPreferenceOption'
177 SYNTAX 1.3.6.1.4.1.1466.115.121.1.32 SINGLE-VALUE )
179 attributetype ( 0.9.2342.19200300.100.1.48 NAME 'buildingName'
180 EQUALITY caseIgnoreMatch
181 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
183 # 0.9.2342.19200300.100.1.49 was dSAQuality in RFC1274
184 # 0.9.2342.19200300.100.1.50 was singleLevelQuality in RFC1274
185 # 0.9.2342.19200300.100.1.51 was subtreeMinimumQuality in RFC1274
186 # 0.9.2342.19200300.100.1.52 was subtreeMaximumQuality in RFC1274
188 # Netscape assigns binary syntax to this. RFC1274 is more detailed
189 # about this but RFC2252 does not seem to list a specific syntax.
190 # We had this as 'bin'
192 attributetype ( 0.9.2342.19200300.100.1.53 NAME 'personalSignature'
193 SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 )
195 attributetype ( 0.9.2342.19200300.100.1.54 NAME 'dITRedirect'
196 EQUALITY distinguishedNameMatch
197 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
199 # Netscape gives syntax 1.5 to this. We had it as 'bin'.
201 attributetype ( 0.9.2342.19200300.100.1.55 NAME 'audio'
202 SYNTAX 1.3.6.1.4.1.1466.115.121.1.4 )
204 attributetype ( 0.9.2342.19200300.100.1.56 NAME 'documentPublisher'
205 EQUALITY caseIgnoreMatch
206 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
208 # From RFC 2798 (inetOrgPerson)
209 attributetype ( 0.9.2342.19200300.100.1.60
212 SYNTAX 1.3.6.1.4.1.1466.115.121.1.28 )
214 # These attributes are pilot-related attributes that we had and Netscape
215 # has too, however, the OID is unknown for them and Netscape uses a
216 # string in place of the missing OID. We will do the same until we
217 # can make head or tails of this.
219 attributetype ( abstract-oid NAME 'abstract'
220 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
222 attributetype ( authorcn-oid NAME ( 'documentAuthorCommonName' 'authorCn' )
223 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
225 attributetype ( authorsn-oid NAME ( 'documentAuthorSurname' 'authorSn' )
226 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
228 attributetype ( documentStore-oid NAME 'documentStore'
229 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
231 attributetype ( keyWords-oid NAME 'keyWords'
232 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
234 attributetype ( obsoletedByDocument-oid NAME 'obsoletedByDocument'
235 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
237 attributetype ( obsoletesDocument-oid NAME 'obsoletesDocument'
238 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
240 attributetype ( subject-oid NAME 'subject'
241 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
243 attributetype ( updatedByDocument-oid NAME 'updatedByDocument'
244 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
246 attributetype ( updatesDocument-oid NAME 'updatesDocument'
247 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
249 # In classes, STRUCTURAL or AUXILIARY is chosen depending on the
250 # textual description that accompanies the class in RFC1274
252 # This is pilotObject from the RFC. However, we had both photo
253 # and jpegPhoto attributes. Nestcape does too.
255 objectclass ( 0.9.2342.19200300.100.4.3 NAME 'pilotObject' SUP top
256 AUXILIARY MAY ( info $ photo $ manager $ uniqueIdentifier $
257 lastModifiedTime $ lastModifiedBy $ dITRedirect $ audio $
260 # This is probably wrong. RFC1274 defines a pilotPerson. We did not
261 # have it and we did have a newPilotPerson instead. However, the
262 # definition is the same. Maybe it changed and was not reflected
265 objectclass ( 0.9.2342.19200300.100.4.4 NAME 'newPilotPerson' SUP person
266 STRUCTURAL MAY ( uid $ textEncodedORAddress $ mail $ drink $
267 roomNumber $ userClass $ homePhone $ homePostalAddress $
268 secretary $ personalTitle $ preferredDeliveryMethod $
269 businessCategory $ janetMailbox $ otherMailbox $ mobile $
270 pager $ organizationalStatus $ mailPreferenceOption $
271 personalSignature ) )
273 # The text is unclear about whether it is STRUCTURAL or AUXILIARY
274 # I think it was meant to be STRUCTURAL, it is the least restrictive
275 # of the options and RFC2377 explains uidObject as an auxiliary.
277 objectclass ( 0.9.2342.19200300.100.4.5 NAME 'account' SUP top
278 STRUCTURAL MUST uid MAY ( description $ seeAlso $ l $ o $ ou $
281 # Netscape says this is derived from pilotObject, but RFC1274 says top.
282 # Which is it? Our attribute list matches that of Netscape, so we will
283 # go with Netscape for the time being.
285 # Besides, this objectclass is a mess. I can only presume that
286 # originally documentAuthor, but later someone noticed that not all
287 # authors had DN's, so authorCN and authorSN were added. Other
288 # attributes were added as well. However, either no one remembered to
289 # assign OIDs to these attribute types or their assignments have been
290 # lost. See their definitions above for the Netscape kludge that we
291 # have adopted. FIX NEEDED.
293 objectclass ( 0.9.2342.19200300.100.4.6 NAME 'document' SUP pilotObject
294 MUST documentIdentifier MAY ( cn $ description $ seeAlso $ l $
295 o $ ou $ documentTitle $ documentVersion $ documentAuthor $
296 documentLocation $ documentPublisher $
297 abstract $ authorCN $ authorSN $ documentStore $ keywords $
298 obsoletedByDocument $ obsoletesDocument $ subject $
299 updatedByDocument $ updatesDocument ) )
301 objectclass ( 0.9.2342.19200300.100.4.7 NAME 'room' SUP top STRUCTURAL
302 MUST cn MAY ( roomNumber $ description $ seeAlso $ telephoneNumber ) )
304 objectclass ( 0.9.2342.19200300.100.4.9 NAME 'documentSeries' SUP top
305 STRUCTURAL MUST cn MAY ( description $ seeAlso $ telephonenumber $
308 # This definition is much longer than that in RFC1274 and is taken from RFC2247
309 objectclass ( 0.9.2342.19200300.100.4.13 NAME 'domain' SUP top STRUCTURAL
311 MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $
312 x121Address $ registeredAddress $ destinationIndicator $
313 preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $
314 telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $
315 street $ postOfficeBox $ postalCode $ postalAddress $
316 physicalDeliveryOfficeName $ st $ l $ description $ o $
319 # This class has in RFC1274 two attributes postalAttributeSet and
320 # telecomunicationAttributeSet that we did not have. We let them out
321 # for now. Netscape does not have them either.
323 objectclass ( 0.9.2342.19200300.100.4.14 NAME 'RFC822localPart' SUP domain
324 MAY ( cn $ sn $ description $ seeAlso $ telephonenumber ) )
326 # Another wonderful inconsistency. This objectclass has little
327 # relationship to the way it was defined in RFC1274, that was derived
328 # from domain, adding ARecord, MDRecord, MXRecord, NSRecord, SOARecord
329 # and CNAMERecord attribute types of syntax DNSRecordSyntax. On the
330 # other hand, we had dNSRecord and Netscape has it too. The OID for
331 # dNSRecord is the one used in RFC1274 for ARecord. Netscape also has
332 # a manager attribute type here that we did not. It seems a mistake
333 # and we do not include it.
335 objectclass ( 0.9.2342.19200300.100.4.15 NAME 'dNSDomain' SUP 'domain'
338 objectclass ( 0.9.2342.19200300.100.4.17 NAME 'domainRelatedObject'
339 SUP 'top' MUST associatedDomain )
341 # Well, first notice we (and Netscape) were using co as short for
342 # friendlyCountryName
344 objectclass ( 0.9.2342.19200300.100.4.18 NAME 'friendlyCountry' SUP country
347 objectclass ( 0.9.2342.19200300.100.4.19 NAME 'simpleSecurityObject'
348 SUP top MUST userPassword )
350 # Nice test case of class with two superiors. Netscape does not give
351 # OID for this objectclass and gives top as its superior. We use the
352 # OID given in RFC1274
354 objectclass ( 0.9.2342.19200300.100.4.20 NAME 'pilotOrganization'
355 SUP ( organization $ organizationalUnit ) MAY buildingName )