| 1 |
<pre>Network Working Group D. Chadwick |
| 2 |
Request for Comments: 2120 University of Salford |
| 3 |
Category: Experimental March 1997 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Managing the X.500 Root Naming Context</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo defines an Experimental Protocol for the Internet |
| 11 |
community. This memo does not specify an Internet standard of any |
| 12 |
kind. Discussion and suggestions for improvement are requested. |
| 13 |
Distribution of this memo is unlimited. |
| 14 |
|
| 15 |
Abstract |
| 16 |
|
| 17 |
The X.500 Standard [X.500 93] has the concept of first level DSAs, |
| 18 |
whose administrators must collectively manage the root naming context |
| 19 |
through bi-lateral agreements or other private means which are |
| 20 |
outside the scope of the X.500 Standard. |
| 21 |
|
| 22 |
The NameFLOW-Paradise X.500 service has an established procedure for |
| 23 |
managing the root naming context, which currently uses Quipu |
| 24 |
proprietary replication mechanisms and a root DSA. The benefits that |
| 25 |
derive from this are twofold: |
| 26 |
|
| 27 |
- firstly it is much easier to co-ordinate the management of the |
| 28 |
root context information, when there is a central point of |
| 29 |
administration, |
| 30 |
|
| 31 |
- secondly the performance of one-level Search operations is |
| 32 |
greatly improved because the Quipu distribution and replication |
| 33 |
mechanism does not have a restriction that exists in the 1988 and |
| 34 |
1993 X.500 Standard. |
| 35 |
|
| 36 |
The NameFLOW-Paradise project is moving towards 1993 ISO X.500 |
| 37 |
Standard replication protocols and wants to standardise the protocol |
| 38 |
and procedure for managing the root naming context which will be |
| 39 |
based on 1993 X.500 Standard protocols. Such a protocol and procedure |
| 40 |
will be useful to private X.500 domains as well as to the Internet |
| 41 |
X.500 public domain. It is imperative that overall system performance |
| 42 |
is not degraded by this transition. |
| 43 |
|
| 44 |
This document describes the use of 1993 ISO X.500 Standard protocols |
| 45 |
for managing the root context. Whilst the ASN.1 is compatible with |
| 46 |
that of the X.500 Standard, the actual settings of the parameters are |
| 47 |
supplementary to that of the X.500 Standard. |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Chadwick Experimental [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a> Introduction............................................. <a href="#page-2">2</a> |
| 60 |
<a href="#section-2">2</a> Migration Plan........................................... <a href="#page-3">3</a> |
| 61 |
<a href="#section-3">3</a> Technical Solutions...................................... <a href="#page-3">3</a> |
| 62 |
<a href="#section-4">4</a> The Fast Track Solution.................................. <a href="#page-4">4</a> |
| 63 |
<a href="#section-5">5</a> The Slower Track Solution................................ <a href="#page-6">6</a> |
| 64 |
<a href="#section-6">6</a> The Long Term Solution................................... <a href="#page-7">7</a> |
| 65 |
<a href="#section-7">7</a> Security Considerations.................................. <a href="#page-8">8</a> |
| 66 |
<a href="#section-8">8</a> Acknowledgments.......................................... <a href="#page-9">9</a> |
| 67 |
<a href="#section-9">9</a> References............................................... <a href="#page-9">9</a> |
| 68 |
<a href="#section-10">10</a> Author's Address........................................ <a href="#page-10">10</a> |
| 69 |
Annex 1 Solution Text of Defect Reports submitted to ISO/ITU- |
| 70 |
<a href="#appendix-T">T</a> by the UK........................................... <a href="#page-11">11</a> |
| 71 |
Annex 2 Defect Report on 1993 X.500 Standard for Adding |
| 72 |
full ACIs to DISP for Subordinate References, so that |
| 73 |
Secure List Operation can be performed in Shadow DSAs. 12 |
| 74 |
Annex 3 Defect Report on 1997 X.500 Standard Proposing |
| 75 |
an Enhancement to the Shadowing Agreement in order to |
| 76 |
support 1 Level Searches in Shadow DSAs............... <a href="#page-14">14</a> |
| 77 |
|
| 78 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a> Introduction</span> |
| 79 |
|
| 80 |
The NameFLOW-Paradise service has a proprietary way of managing the |
| 81 |
set of first level DSAs and the root naming context. There is a |
| 82 |
single root DSA (Giant Tortoise) which holds all of the country |
| 83 |
entries, and the country entries are then replicated to every country |
| 84 |
(first level) DSA and other DSAs by Quipu replication [<a href="./rfc1276">RFC 1276</a>] from |
| 85 |
the root DSA. In June 1996 there were 770 DSAs replicating this |
| 86 |
information over the Internet. The root DSA is not a feature of the |
| 87 |
X.500 Standard [X.500 93]. It was introduced because of the non- |
| 88 |
standard nature of the original Quipu knowledge model (also described |
| 89 |
in <a href="./rfc1276">RFC 1276</a>). However, it does have significant advantages both in |
| 90 |
managing the root naming context and in the performance of one-level |
| 91 |
Searches of the root. Performance is increased because each country |
| 92 |
DSA holds all the entry information of every country. |
| 93 |
|
| 94 |
By comparison, the 1988 X.500 Standard root context which is |
| 95 |
replicated to all the country DSAs, only holds knowledge information |
| 96 |
and a boolean (to say if the entry is an alias or not) for each |
| 97 |
country entry. This is sufficient to perform an insecure List |
| 98 |
operation, but not a one-level Search operation. When access controls |
| 99 |
were added to the 1993 X.500 Standard, the root context information |
| 100 |
was increased (erroneously as it happens - this is the subject of |
| 101 |
defect report 140 - see Annex 1) to hold the access controls for each |
| 102 |
country entry, but a note in the X.500 Standard restricted its use to |
| 103 |
the List operation, in order to remain compatible with the 1988 |
| 104 |
edition of the X.500 Standard. |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Chadwick Experimental [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a> Migration Plan</span> |
| 114 |
|
| 115 |
The NameFLOW-Paradise service is now migrating to X.500 Standard |
| 116 |
[X.500 93] conforming products, and it is essential to replace the |
| 117 |
Quipu replication protocol with the 1993 shadowing and operational |
| 118 |
binding protocols, but without losing the performance improvement |
| 119 |
that has been gained for one-level Searches. |
| 120 |
|
| 121 |
It is still the intention of the NameFLOW-Paradise service to have |
| 122 |
one master root DSA. This root DSA will not support user Directory |
| 123 |
operations via the LDAP, the DAP or the DSP, but each country (first |
| 124 |
level) DSA will be able to shadow the root context from this root |
| 125 |
DSA, using the DISP. Each first level DSA then only needs to have one |
| 126 |
bi-lateral agreement, between itself and the root DSA. This agreement |
| 127 |
will ensure that the first level DSA keeps the root DSA up to date |
| 128 |
with its country level information, and in turn, that the root DSA |
| 129 |
keeps the first level DSA up to date with the complete root naming |
| 130 |
context. When a new first level DSA comes on line, it only needs to |
| 131 |
establish a bi-lateral agreement with the root DSA, in order to |
| 132 |
obtain the complete root context. |
| 133 |
|
| 134 |
This is a much easier configuration to manage than simply a set of |
| 135 |
first level DSAs without a root DSA, as suggested in the ISO X.500 |
| 136 |
Standard. In the X.500 Standard case each first level DSA must have |
| 137 |
bi-lateral agreements with all of the other first level DSAs. When a |
| 138 |
new first level DSA comes on line, it must establish agreements with |
| 139 |
all the existing first level DSAs. As the number of first level DSAs |
| 140 |
grows, the process becomes unmanageable. |
| 141 |
|
| 142 |
However, it is also important to increase the amount of information |
| 143 |
that is held about every country entry, so that a one-level Search |
| 144 |
operation can be performed in each first level DSA, without it |
| 145 |
needing to chain or refer the operation to all the other first level |
| 146 |
DSAs (as is currently the case with a X.500 Standard conforming |
| 147 |
system.) |
| 148 |
|
| 149 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a> Technical Solutions</span> |
| 150 |
|
| 151 |
3.1 The solution at first appears to be relatively straight forward, |
| 152 |
and involves two steps. Firstly, create a root DSA, and establish |
| 153 |
hierarchical operational bindings using the DOP, between it and each |
| 154 |
master first level DSA. Secondly, each master first level DSA enters |
| 155 |
into a shadowing agreement with the root DSA, to shadow the enlarged |
| 156 |
root context information. In this way each first level DSA is then |
| 157 |
capable of independently performing List and one-level Search |
| 158 |
operations, and name resolving to all other first level DSAs. |
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Chadwick Experimental [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 167 |
|
| 168 |
|
| 169 |
3.2 Unfortunately there are a number of complications that inhibit a |
| 170 |
quick implementation of this solution. Firstly, few DSA suppliers |
| 171 |
have implemented the DOP. Secondly there are several defects in the |
| 172 |
X.500 Standard that currently stop the above solution from working. |
| 173 |
|
| 174 |
3.3 At a meeting chaired by DANTE in the UK on 18 June 1996[Mins], at |
| 175 |
which several DSA suppliers were present, the following pragmatic |
| 176 |
technical solution was proposed. This comprises a fast track partial |
| 177 |
solution and a slower track fuller solution. Both the fast and slower |
| 178 |
tracks use the shadowing protocol (DISP) for both steps of the |
| 179 |
solution, and do not rely on the DOP to establish HOBs. The fast |
| 180 |
track solution, described in <a href="#section-4">section 4</a>, will support knowledge |
| 181 |
distribution of the root context, and the (insecure) List operation |
| 182 |
of the root's subordinates. The List operation will be insecure |
| 183 |
because access control information will not be present in the shadow |
| 184 |
DSEs. (However, since it is generally thought that first level |
| 185 |
entries, in particular country entries, are publicly accessible, this |
| 186 |
is not considered to be a serious problem.) Suppliers expect to have |
| 187 |
the fast track solution available before the end of 1996. The slower |
| 188 |
track solution, described in <a href="#section-5">section 5</a>, will in addition support |
| 189 |
fully secure one level Search and List operations of the root |
| 190 |
(without the need to chain to the master DSAs). Suppliers at the |
| 191 |
DANTE meeting did not realistically expect this to be in their |
| 192 |
products much sooner than mid 1998. |
| 193 |
|
| 194 |
3.4 The long term solution, which relies on the DOP to establish |
| 195 |
HOBs, is described in <a href="#section-6">section 6</a> of this document. |
| 196 |
|
| 197 |
(Note. It is strongly recommended that non-specific subordinate |
| 198 |
references should not be allowed in the root context for efficiency |
| 199 |
reasons. This is directed by the European functional X.500 Standard |
| 200 |
[ENV 41215] and the NADF standing document [NADF 7]. It is also |
| 201 |
preferred by the International X.500 Standardized Profile [ISP |
| 202 |
10615-6].) |
| 203 |
|
| 204 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a> The Fast Track Solution</span> |
| 205 |
|
| 206 |
4.1 The fast track solution provides root knowledge collection and |
| 207 |
insecure List operations for first level DSAs, and will be of use to |
| 208 |
systems which do not yet support the DOP for managing hierarchical |
| 209 |
operational bindings. The fast track solution relies upon the DISP |
| 210 |
with very few changes to the 1993 edition of the X.500 Standard. |
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Chadwick Experimental [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 223 |
|
| 224 |
|
| 225 |
4.2 Each master first level DSA administrator will make available to |
| 226 |
the administrator of the root DSA, sufficient information to allow |
| 227 |
the root DSA to configure a subordinate reference to their DSA. In |
| 228 |
the simplest case, this can be via a telephone call, and the |
| 229 |
information comprises the access point of their DSA and the RDNs of |
| 230 |
the first level entries that they master. |
| 231 |
|
| 232 |
4.3 Each master first level DSA enters into a shadowing agreement |
| 233 |
with the root DSA, for the purpose of shadowing the root naming |
| 234 |
context. |
| 235 |
|
| 236 |
The 1993 edition of the X.500 Standard explicitly recognises that |
| 237 |
there can be master and shadow first level DSAs (X.501 <a href="#section-18.5">Section 18.5</a>). |
| 238 |
(The 1988 edition of the X.500 Standard does not explicitly recognise |
| 239 |
this, since it does not recognise shadowing.) A shadow first level |
| 240 |
DSA holds a copy of the root context, provided by a master first |
| 241 |
level DSA. In addition it holds shadow copies of the (one or more) |
| 242 |
country entries that the master first level DSA holds. There is |
| 243 |
currently an outstanding defect report [UK 142] on the 1993 X.500 |
| 244 |
Standard to clarify how a shadowing agreement is established between |
| 245 |
first level DSAs. Once this has been ratified, the only additional |
| 246 |
text needed in order to establish a shadowing agreement between the |
| 247 |
root DSA and a master first level DSA is as follows: |
| 248 |
|
| 249 |
"When clause 9.2 of ISO/IEC 9594-9:1993 is applied to the |
| 250 |
shadowing of the root context by a first level DSA from the root |
| 251 |
DSA of a domain, then UnitOfReplication shall be set as follows: |
| 252 |
|
| 253 |
contextPrefix of AreaSpecification shall be null, |
| 254 |
|
| 255 |
replicationArea of AreaSpecification shall be set to |
| 256 |
SEQUENCE { |
| 257 |
specificExclusions [1] SET OF { |
| 258 |
chopBefore [0] FirstLevelEntry}, |
| 259 |
maximum [3] 1 } |
| 260 |
|
| 261 |
where FirstLevelEntry is the RDN of a first level entry (e.g. |
| 262 |
country, locality or international organisation) held by the |
| 263 |
master first level DSA. specificExclusions shall contain one |
| 264 |
|
| 265 |
FirstLevelEntry for each first level entry mastered by this DSA, |
| 266 |
|
| 267 |
attributes of UnitofReplication shall be an empty SET OF SEQUENCE, |
| 268 |
|
| 269 |
knowledge of UnitofReplication shall be set to both (shadow and |
| 270 |
master). |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Chadwick Experimental [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 279 |
|
| 280 |
|
| 281 |
In other words, the information that will be replicated will be an |
| 282 |
empty root entry plus all the attributes of the complete set of |
| 283 |
subordinate DSEs of the root that are held in the root DSA excluding |
| 284 |
the DSEs that the first level DSA already masters, plus a complete |
| 285 |
set of subordinate reference." |
| 286 |
|
| 287 |
Note that the maximum component of replicationArea, although not |
| 288 |
strictly necessary, is there for pragmatic reasons, for example, |
| 289 |
where a community of users wish to use the root DSA to hold some |
| 290 |
country specific entries. |
| 291 |
|
| 292 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a> The Slower Track Solution</span> |
| 293 |
|
| 294 |
5.1 The slower track solution provides support for fully secure one |
| 295 |
level Search and List operations of the root in first level DSAs, and |
| 296 |
comprises of two steps for HOB establishment between the root DSA and |
| 297 |
master first level DSAs, using the DISP instead of the DOP. Step one, |
| 298 |
described in 5.3, allows the root DSA to shadow first level entries |
| 299 |
from a master first level DSA. Step two, described in 5.4, requires |
| 300 |
either the root DSA administrator or the root DSA implementation to |
| 301 |
massage the shadow first level entries so that they appear to have |
| 302 |
been created by a HOB. Managing the root context then continues as |
| 303 |
in 4.3 above. |
| 304 |
|
| 305 |
5.2 This solution requires two significant defects in the ISO X.500 |
| 306 |
Standard to be corrected. Firstly, access control information needs |
| 307 |
to be added to subordinate references in the DISP to allow the List |
| 308 |
operation to work securely in a shadowed DSA. (The ACI are held in |
| 309 |
both the subr DSE and in its subentry.) This requires a defect report |
| 310 |
on the 93 X.500 Standard to be submitted. The text of this defect |
| 311 |
report (that has been submitted to ISO) is given in Annex 2. |
| 312 |
|
| 313 |
Secondly, a new type of shadowing agreement will need to be |
| 314 |
established between the supplier and consumer DSAs, to copy |
| 315 |
subordinate entries rather than simply subordinate references, so |
| 316 |
that one level Search operations can work in the shadowing DSA. This |
| 317 |
procedure should have been part of the 1997 edition of the X.500 |
| 318 |
Standard, but due to an omission is not. Consequently a defect |
| 319 |
report on the 1997 X.500 Standard has been submitted. The text of |
| 320 |
this defect report is given in Annex 3. |
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Chadwick Experimental [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 335 |
|
| 336 |
|
| 337 |
5.3 The hierarchical operational binding between the root DSA and a |
| 338 |
master first level DSA can be replaced by a set of "spot" shadowing |
| 339 |
agreements, in which the first level DSA acts as the supplier, and |
| 340 |
the root DSA as the consumer. Each "spot" shadowing agreement |
| 341 |
replicates a first level entry which is mastered by the first level |
| 342 |
DSA. The UnitOfReplication shall be set as follows: |
| 343 |
|
| 344 |
contextPrefix of AreaSpecification shall be FirstLevelEntry, |
| 345 |
|
| 346 |
replicationArea of AreaSpecification shall be set to |
| 347 |
SEQUENCE { |
| 348 |
specificExclusions [1] SET OF { |
| 349 |
chopAfter [1] {null} } } |
| 350 |
|
| 351 |
where FirstLevelEntry is the Distinguished Name of a first level |
| 352 |
entry (e.g. country, locality or international organisation) held by |
| 353 |
the master first level DSA. |
| 354 |
|
| 355 |
attributes of UnitofReplication shall be an empty SET OF SEQUENCE, |
| 356 |
|
| 357 |
knowledge of UnitofReplication shall be absent. |
| 358 |
|
| 359 |
5.4 The root DSA administrator, or the root DSA implementation |
| 360 |
(suitably tailored) must then administratively update each shadowed |
| 361 |
first level entry, so that they appear to have been created by a HOB, |
| 362 |
i.e. it is necessary to add a subordinate reference to each one of |
| 363 |
them. The subordinate reference will point to the respective master |
| 364 |
first level DSA, and will comprise of a specific knowledge attribute, |
| 365 |
and the DSE bit of type subr being set. The contents of the specific |
| 366 |
knowledge attribute can be created from the contents of the supplier |
| 367 |
knowledge attribute already present in the first level entry and |
| 368 |
created by the "spot" shadowing agreement. |
| 369 |
|
| 370 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a> The Long Term Solution</span> |
| 371 |
|
| 372 |
6.1 Each master first level DSA will have a hierarchical operational |
| 373 |
binding with the root DSA of the domain. Each master first level DSA |
| 374 |
will master one or more first level entries. The hierarchical |
| 375 |
operational binding will keep the appropriate subordinate |
| 376 |
reference(s) (of category shadow and master) up to date, as well as |
| 377 |
the other entry information that is needed for one-level Search |
| 378 |
operations (such as access controls, and attributes used in |
| 379 |
filtering). |
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Chadwick Experimental [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 391 |
|
| 392 |
|
| 393 |
Whilst hierarchical agreements are standardised, this particular |
| 394 |
novel use of a HOB is not specifically recognised in the X.500 |
| 395 |
Standard. Although the ASN.1 will support it, there is no supporting |
| 396 |
text in the X.500 Standard. The following text supplements that in |
| 397 |
the X.500 Standard, and describes how a first level DSA may have a |
| 398 |
hierarchical operational binding with the root DSA of its domain. |
| 399 |
|
| 400 |
"Clause 24 of ISO/IEC 9594-4:1993 shall also apply when a first level |
| 401 |
DSA is a subordinate DSA, and the root DSA of the domain is the |
| 402 |
superior DSA. The naming context held by the superior (root) DSA is |
| 403 |
the root naming context (or root context - the terms are synonymous) |
| 404 |
of the domain. The root context consists of the root entry of the DIT |
| 405 |
(which is empty) plus a complete set of subordinate DSEs (i.e. first |
| 406 |
level DSEs), one for each first level naming context in the domain, |
| 407 |
and their corresponding subentries. The first level DSEs and their |
| 408 |
subentries will contain, in addition to specific knowledge attribute |
| 409 |
values of category master and shadow, sufficient attributes and |
| 410 |
collective attributes, including access control information, to allow |
| 411 |
List and one-level Search operations to be performed on them. |
| 412 |
|
| 413 |
In clause 24.1.2, the DistinguishedName of the immediateSuperior |
| 414 |
component of HierarchicalAgreement shall be null." |
| 415 |
|
| 416 |
6.2 The ASN.1 of hierarchical operational bindings already allows any |
| 417 |
attributes to be passed from the subordinate DSA to the superior DSA |
| 418 |
(SubordinateToSuperior parameter in clause 24.1.4.2 of X.518). |
| 419 |
However, a note in the 1993 edition of the X.500 Standard limits this |
| 420 |
to those which are required to perform a List operation. In the 1997 |
| 421 |
edition of the X.500 Standard [DAM User] this restriction has been |
| 422 |
removed, so that the attributes may also be used for a one-level |
| 423 |
Search operation. |
| 424 |
|
| 425 |
1993 implementations of X.500 conforming to this RFC, shall also |
| 426 |
remove this restriction. |
| 427 |
|
| 428 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a> Security Considerations</span> |
| 429 |
|
| 430 |
Security considerations are discussed in this memo in relation to |
| 431 |
List and one-level Search operations. Each DSE has access control |
| 432 |
information associated with it, and these must be adhered to when the |
| 433 |
operations are performed. |
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Chadwick Experimental [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a> Acknowledgments</span> |
| 450 |
|
| 451 |
The author would like to thank DANTE, without whose funding this work |
| 452 |
would not have been possible. |
| 453 |
|
| 454 |
The author would also like to thank Nexor, who reviewed the first |
| 455 |
version of this document in detail and provided valuable comments, |
| 456 |
and who first suggested the use of the DISP as a pragmatic solution |
| 457 |
for HOB establishment until the DOP becomes widely implemented. |
| 458 |
|
| 459 |
The author would also like to thank John Farrell from the ISODE |
| 460 |
Consortium, Andrew Palk from Digital and Keith Richardson from ICL |
| 461 |
who attended the DANTE meeting, and contributed to the technical |
| 462 |
contents of the defect reports in Annexes 2 and 3. |
| 463 |
|
| 464 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a> References</span> |
| 465 |
|
| 466 |
[DAM User] Draft Amendments on Minor Extensions to OSI Directory |
| 467 |
Service to support User Requirements, August 1995. |
| 468 |
|
| 469 |
[ENV 41215] "Behaviour of DSAs for Distributed Operations", |
| 470 |
European X.500 Pre-Standard, Dec 1992 |
| 471 |
|
| 472 |
[ISP 10615-6] "DSA Support of Distributed Operations", 5th draft |
| 473 |
pDISP, Oct 1994 |
| 474 |
|
| 475 |
[<a id="ref-Mins">Mins</a>] "Notes of DANTE meeting to discuss Managing the Root Naming |
| 476 |
Context. 18 June 1996." D W Chadwick, circulated to IDS mailing |
| 477 |
list |
| 478 |
|
| 479 |
[NADF 7] SD-7 "Mapping the North American DIT onto Directory |
| 480 |
Management Domains", North American Directory Forum, V 8.0, Jan |
| 481 |
1993 |
| 482 |
|
| 483 |
[<a id="ref-RFC 1276">RFC 1276</a>] Kille, S., "Replication and Distributed Operations |
| 484 |
extensions to provide an Internet Directory using X.500", UCL, |
| 485 |
November 1991. |
| 486 |
|
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Chadwick Experimental [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 503 |
|
| 504 |
|
| 505 |
[UK 142] Defect report number 142, submitted by the UK to ISO, |
| 506 |
March 1995. (Proposed solution text included in Annex 1) |
| 507 |
|
| 508 |
[X.500 93] X.500 | 9594.Part 1 Overview of Concepts, Models and |
| 509 |
Services |
| 510 |
X.501 | 9594.Part 2 Models |
| 511 |
X.511 | 9594.Part 3 Abstract Service Definition |
| 512 |
X.518 | 9594.Part 4 Procedures for Distributed Operations |
| 513 |
X.519 | 9594.Part 5 Protocol Specifications |
| 514 |
X.520 | 9594.Part 6 Selected Attribute Types |
| 515 |
X.521 | 9594.Part 7 Selected Object Classes |
| 516 |
X.509 | 9594.Part 8 Authentication Framework |
| 517 |
X.525 | 9594.Part 9 Replication |
| 518 |
|
| 519 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a> Author's Address</span> |
| 520 |
|
| 521 |
D W Chadwick |
| 522 |
IT Institute |
| 523 |
University of Salford |
| 524 |
Salford |
| 525 |
M5 4WT |
| 526 |
England |
| 527 |
Phone: +44 161 745 5351 |
| 528 |
Fax: +44 161 745 8169 |
| 529 |
E-mail: [email protected] |
| 530 |
|
| 531 |
|
| 532 |
|
| 533 |
|
| 534 |
|
| 535 |
|
| 536 |
|
| 537 |
|
| 538 |
|
| 539 |
|
| 540 |
|
| 541 |
|
| 542 |
|
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Chadwick Experimental [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 559 |
|
| 560 |
|
| 561 |
Annex 1 Solution Text of Defect Reports submitted to ISO/ITU-T by |
| 562 |
the UK |
| 563 |
|
| 564 |
Defect Report 140 |
| 565 |
|
| 566 |
Nature of Defect |
| 567 |
|
| 568 |
In <a href="#section-24.1.4.2">section 24.1.4.2</a> it is defined that the SubordinateToSuperior |
| 569 |
parameter of a HOB can pass an entryInfo parameter. This should |
| 570 |
contain entryACI which may be used in the resolution of the List |
| 571 |
operation. |
| 572 |
|
| 573 |
This is not correct as the prescriptive ACI from the relevant |
| 574 |
subentries is also required in the superior DSA. |
| 575 |
|
| 576 |
Solution Proposed by Source |
| 577 |
|
| 578 |
It is proposed that the following is added to the |
| 579 |
SubordinateToSuperior SEQUENCE of <a href="#section-24.1.4.2">section 24.1.4.2</a> of X.518: |
| 580 |
|
| 581 |
subentries [2] SET OF SubentryInfo OPTIONAL |
| 582 |
|
| 583 |
This is used to pass the relevant subentries from the subordinate to |
| 584 |
the superior. This is similar to the way subentry information is |
| 585 |
passed in the SuperiorToSubordinate parameter defined in 24.1.4.1. |
| 586 |
|
| 587 |
Defect Report 142 |
| 588 |
|
| 589 |
Nature of Defect |
| 590 |
|
| 591 |
The text which describes AreaSpecification in clause 9.2 of X.525 is |
| 592 |
completely general. However, for the special case of replicating |
| 593 |
first level knowledge references between first level DSAs, a |
| 594 |
clarifying sentence should be added. |
| 595 |
|
| 596 |
Solution Proposed by Source |
| 597 |
|
| 598 |
In <a href="#section-9.2">Section 9.2</a>, under the ASN.1, after the description of area, and |
| 599 |
before the description of SubtreeSpecification, add the sentence: |
| 600 |
|
| 601 |
"For the case where a DSA is shadowing first level knowledge from |
| 602 |
a first level DSA, the contextPrefix component is empty." |
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Chadwick Experimental [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 615 |
|
| 616 |
|
| 617 |
Annex 2 Defect Report on 1993 X.500 Standard for Adding full ACIs to |
| 618 |
DISP for Subordinate References, so that Secure List Operation can |
| 619 |
be performed in Shadow DSAs |
| 620 |
|
| 621 |
Nature of Defect: |
| 622 |
|
| 623 |
The List operation may be carried out in a superior DSA using |
| 624 |
subordinate reference information, providing that the fromEntry flag |
| 625 |
is set to false in the response. However, in order to do this |
| 626 |
securely, complete access control information is needed for the RDN |
| 627 |
of the subordinate entry. The existing text assumes that this is held |
| 628 |
in entry ACI (e.g. see 9.2.4.1 c) or in prescriptive ACI held in |
| 629 |
subentries above the DSE (e.g. see 9.2.4.1 b). In the case of a |
| 630 |
subordinate reference, the prescriptive ACI may be held below the |
| 631 |
DSE, if the subordinate reference points to a new administrative |
| 632 |
point. The shadowing document needs to make it clear that this can be |
| 633 |
the case, and needs to allow for this additional access control |
| 634 |
information to be shadowed. |
| 635 |
|
| 636 |
A related defect report (140) has already suggested that this same |
| 637 |
omission should be added to operational bindings. |
| 638 |
|
| 639 |
Solution Proposed by the Source: |
| 640 |
|
| 641 |
All the following changes are to X.525|ISO 9594-9. |
| 642 |
|
| 643 |
I) Insert the following text into 7.2.2.3, at the end of both the |
| 644 |
second paragraph and the first sentence of the third paragraph (after |
| 645 |
"appropriate knowledge"): "and access control information." |
| 646 |
|
| 647 |
II) Insert a new third paragraph into 7.2.2.3: "If subordinate |
| 648 |
knowledge is supplied, and the supplying DSE (of type subr) is also |
| 649 |
of type admPoint, then the SDSE shall additionally be of type |
| 650 |
admPoint and the administrativeRole attribute shall be supplied. If |
| 651 |
such a DSE has any immediately subordinate subentries containing |
| 652 |
PrescriptiveACI relating to the administrative point, then they shall |
| 653 |
also be supplied as SDSEs in the shadowed information. |
| 654 |
|
| 655 |
Note. A DSE can be of type subr and admPoint in a superior DSA, when |
| 656 |
the naming context in the subordinate DSA is the start of a new |
| 657 |
administrative area." |
| 658 |
|
| 659 |
III) Update figure 3 to show a subentry immediately below a |
| 660 |
subordinate reference. The subentry contains prescriptiveACI and is |
| 661 |
part of the shadowed information. |
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Chadwick Experimental [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 671 |
|
| 672 |
|
| 673 |
. |
| 674 |
Etc. / \ |
| 675 |
/ \ |
| 676 |
/ o \ |
| 677 |
/ / \ \ |
| 678 |
Replicated / / \ \ |
| 679 |
Area --------------/--/-> \ \ |
| 680 |
/ / \ \ |
| 681 |
/ / \ \ |
| 682 |
/ / \ \ |
| 683 |
Subordinate /__/_____________\__\ |
| 684 |
knowledge--------/-> o o o \ |
| 685 |
/ / \ \ |
| 686 |
Prescriptive---/-> o o \ |
| 687 |
ACI Subentries/ \ |
| 688 |
Unit of Replication |
| 689 |
|
| 690 |
|
| 691 |
Etc. |
| 692 |
o |
| 693 |
/ \ |
| 694 |
/ \ |
| 695 |
/ \ |
| 696 |
/ \ |
| 697 |
/ \ |
| 698 |
/ \ |
| 699 |
/_____________\ |
| 700 |
o o o |
| 701 |
/ \ |
| 702 |
o o |
| 703 |
Shadowed Information |
| 704 |
|
| 705 |
ADDITIONS TO FIGURE 3, <a href="#section-7.2">SECTION 7.2</a>, X.525 |
| 706 |
|
| 707 |
IV) Add supporting text to <a href="#section-7.2">section 7.2</a> in the paragraph after Figure |
| 708 |
3. Insert after the sentence "Subordinate knowledge may also be |
| 709 |
replicated" the following sentences "Implicit in the Add supporting |
| 710 |
text to <a href="#section-7.2">section 7.2</a> in the paragraph after Figure 3. Insert after |
| 711 |
the sentence subordinate knowledge is the access control information |
| 712 |
which governs access to the RDN of the subordinate knowledge. When |
| 713 |
the subordinate entry is an administrative point in another DSA, then |
| 714 |
part of this access control information may be held in |
| 715 |
prescriptiveACI subentries beneath the subordinate knowledge." |
| 716 |
|
| 717 |
v) Add a new point d) to 9.2.4.1: "if subordinate knowledge (not |
| 718 |
extended knowledge) is shadowed then any prescriptiveACI in |
| 719 |
subordinate subentries shall also be copied." |
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Chadwick Experimental [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc2120">RFC 2120</a> Managing the X.500 Root Naming Context March 1997</span> |
| 727 |
|
| 728 |
|
| 729 |
Annex 3 Defect Report on 1997 X.500 Standard Proposing an Enhancement to |
| 730 |
the Shadowing Agreement in order to support 1 Level Searches in Shadow |
| 731 |
DSAs. |
| 732 |
|
| 733 |
Nature of Defect: |
| 734 |
|
| 735 |
The 1997 edition of the X.500 Standard has allowed, for reasons of |
| 736 |
operational efficiency, one level Searches to be carried out in the |
| 737 |
superior DSA, when the actual entries are context prefixes in |
| 738 |
subordinate DSAs. The HOBs have been extended to allow this entry |
| 739 |
information to be carried up to the superior DSA. Unfortunately, we |
| 740 |
forgot to add the corresponding text to Part 9, so that shadow DSAs |
| 741 |
are able to copy this additional information from the supplier DSA. |
| 742 |
This defect report proposes the additional text for Part 9. |
| 743 |
|
| 744 |
Solution Proposed by the Source: |
| 745 |
|
| 746 |
All the following changes are to X.525|ISO 9594-9. |
| 747 |
|
| 748 |
I) <a href="#section-9.2">Section 9.2</a>, add a new subordinates parameter to |
| 749 |
UnitOfReplication, viz: |
| 750 |
|
| 751 |
UnitOfReplication ::= SEQUENCE{ |
| 752 |
area AreaSpecification, |
| 753 |
attributes AttributeSelection, |
| 754 |
knowledge Knowledge OPTIONAL, |
| 755 |
subordinates BOOLEAN DEFAULT FALSE } |
| 756 |
|
| 757 |
subordinates is used to indicate that subordinate entries, rather |
| 758 |
than simply subordinate references, are to be copied to the |
| 759 |
consumer DSA. subordinates may only be TRUE if knowledge is |
| 760 |
requested and extendedKnowledge is FALSE. |
| 761 |
|
| 762 |
II) Insert a new fourth paragraph (assuming previous defect for |
| 763 |
List was accepted) into 7.2.2.3: |
| 764 |
|
| 765 |
"If subordinates is specified, then the supplier shall send |
| 766 |
subordinate entries rather than subordinate references, and the |
| 767 |
SDSEs will be of type subr, entry and cp. The subordinate entries |
| 768 |
will contain attributes according to the attribute selection. |
| 769 |
|
| 770 |
In addition, if the supplying DSE is of type admPoint, then the |
| 771 |
SDSE shall additionally be of type admPoint and the |
| 772 |
administrativeRole attribute shall be supplied. All appropriate |
| 773 |
subentries below the admPoint DSE shall also be supplied as SDSEs |
| 774 |
in the shadowed information." |
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
Chadwick Experimental [Page 14] |
| 781 |
</pre> |