| 1 |
<pre>Network Working Group V. Ryan |
| 2 |
Request for Comments: 2714 R. Lee |
| 3 |
Category: Informational S. Seligman |
| 4 |
Sun Microsystems, Inc. |
| 5 |
October 1999 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">Schema for Representing CORBA Object References in an LDAP Directory</span> |
| 9 |
|
| 10 |
Status of this Memo |
| 11 |
|
| 12 |
This memo provides information for the Internet community. It does |
| 13 |
not specify an Internet standard of any kind. Distribution of this |
| 14 |
memo is unlimited. |
| 15 |
|
| 16 |
Copyright Notice |
| 17 |
|
| 18 |
Copyright (C) The Internet Society (1999). All Rights Reserved. |
| 19 |
|
| 20 |
Abstract |
| 21 |
|
| 22 |
CORBA [<a href="#ref-CORBA" title=""Common Object Request Broker Architecture Specification 2.2"">CORBA</a>] is the Common Object Request Broker Architecture |
| 23 |
defined by the Object Management Group. This document defines the |
| 24 |
schema for representing CORBA object references in an LDAP directory |
| 25 |
[<a href="#ref-LDAPv3" title=""Lightweight Directory Access Protocol (v3)"">LDAPv3</a>]. |
| 26 |
|
| 27 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 28 |
|
| 29 |
This document assumes that the reader has a general understanding of |
| 30 |
CORBA. |
| 31 |
|
| 32 |
Traditionally, LDAP directories have been used to store data. Users |
| 33 |
and programmers think of the directory as a hierarchy of directory |
| 34 |
entries, each containing a set of attributes. You look up an entry |
| 35 |
from the directory and extract the attribute(s) of interest. For |
| 36 |
example, you can look up a person's telephone number from the |
| 37 |
directory. Alternatively, you can search the directory for entries |
| 38 |
with a particular set of attributes. For example, you can search for |
| 39 |
all persons in the directory with the surname "Smith". |
| 40 |
|
| 41 |
CORBA applications require access to CORBA objects. Traditionally, |
| 42 |
CORBA applications have used the COS Naming service for storage and |
| 43 |
retrieval of CORBA object references. When deployed in environments |
| 44 |
with a directory, CORBA applications should be able to use the |
| 45 |
directory as a repository for CORBA object references. The directory |
| 46 |
provides a centrally administered, and possibly replicated, service |
| 47 |
for use by CORBA applications distributed across the network. |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Ryan, et al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2714">RFC 2714</a> Schema for CORBA Object References October 1999</span> |
| 55 |
|
| 56 |
|
| 57 |
For example, an application server may use the directory for |
| 58 |
"registering" CORBA objects representing the services that it |
| 59 |
manages, so that a client can later search the directory to locate |
| 60 |
those services as it needs. |
| 61 |
|
| 62 |
The motivation for this document is to define a common way for |
| 63 |
applications to store and retrieve CORBA object references from the |
| 64 |
directory. Using this common schema, any CORBA application that |
| 65 |
needs to read or store CORBA object references in the directory can |
| 66 |
do so in an interoperable way. |
| 67 |
|
| 68 |
Note that this schema is defined for storing CORBA "object |
| 69 |
references," not CORBA objects in general. There might be other ways |
| 70 |
to store CORBA objects in an LDAP directory but they are not covered |
| 71 |
by this schema. |
| 72 |
|
| 73 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Representation of CORBA Object References</span> |
| 74 |
|
| 75 |
This document defines schema elements to represent a CORBA object |
| 76 |
reference in LDAP directory. Applications in possession of a |
| 77 |
reference to an object can invoke calls on that object. Such a |
| 78 |
reference is termed an "interoperable object reference," or IOR. |
| 79 |
Access to CORBA objects by using IORs is achieved transparently to |
| 80 |
the application, by means of the General Inter-ORB Protocol. |
| 81 |
|
| 82 |
A CORBA object reference is represented in the directory by the |
| 83 |
object class corbaObjectReference. corbaObjectReference is a subclass |
| 84 |
of the abstract corbaObject object class. corbaObjectReference is an |
| 85 |
auxiliary object class, which means that it needs to be mixed in with |
| 86 |
a structural object class. |
| 87 |
|
| 88 |
The object class corbaContainer is used in a directory entry which |
| 89 |
represents a CORBA object or object reference. It is a structural |
| 90 |
object class, and when representing an object reference, the |
| 91 |
corbaObjectReference object class would also need to be present in |
| 92 |
the entry. corbaContainer is not required when a subclass of |
| 93 |
corbaObject (such as corbaObjectReference) is mixed in with another |
| 94 |
structural object class. |
| 95 |
|
| 96 |
The definitions for the object classes corbaObject, |
| 97 |
corbaObjectReference, and corbaContainer are presented in <a href="#section-4">Section 4</a>. |
| 98 |
|
| 99 |
The corbaObject class has two optional attributes: corbaRepositoryId |
| 100 |
and description. corbaRepositoryId is a multivalued attribute that |
| 101 |
is used to store the repository ids of the interfaces implemented by |
| 102 |
a CORBA object. description is used to store a textual description |
| 103 |
of a CORBA object. |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Ryan, et al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2714">RFC 2714</a> Schema for CORBA Object References October 1999</span> |
| 111 |
|
| 112 |
|
| 113 |
The corbaObjectReference class has one mandatory attribute: corbaIor. |
| 114 |
corbaIor is used to store the object's stringified IOR. |
| 115 |
|
| 116 |
corbaIor and corbaRepositoryId are defined in <a href="#section-3">Section 3</a>; description |
| 117 |
is defined in [<a href="#ref-v3Schema" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">v3Schema</a>]. |
| 118 |
|
| 119 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Attribute Type Definitions</span> |
| 120 |
|
| 121 |
The following attribute types are defined in this document: |
| 122 |
|
| 123 |
corbaIor |
| 124 |
corbaRepositoryId |
| 125 |
|
| 126 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> corbaIor</span> |
| 127 |
|
| 128 |
This attribute stores the string representation of the interoperable |
| 129 |
object reference (IOR) for a CORBA object. An IOR is an opaque handle |
| 130 |
for the object which contains the information necessary to locate the |
| 131 |
object, even if the object is in another ORB. |
| 132 |
|
| 133 |
This attribute's syntax is 'IA5 String' and its case is |
| 134 |
insignificant. |
| 135 |
|
| 136 |
( 1.3.6.1.4.1.42.2.27.4.1.14 |
| 137 |
NAME 'corbaIor' |
| 138 |
DESC 'Stringified interoperable object reference of a CORBA object' |
| 139 |
EQUALITY caseIgnoreIA5Match |
| 140 |
SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 |
| 141 |
SINGLE-VALUE |
| 142 |
) |
| 143 |
|
| 144 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> corbaRepositoryId</span> |
| 145 |
|
| 146 |
Each CORBA interface has a unique "repository id" (also called "type |
| 147 |
id") that identifies the interface. A CORBA object has one or more |
| 148 |
repository ids, one for each interface that it implements. |
| 149 |
|
| 150 |
The format of a repository id can be any string, but the OMG |
| 151 |
specifies four standard formats: |
| 152 |
|
| 153 |
a. IDL-style |
| 154 |
|
| 155 |
IDL:Prefix/ModuleName/InterfaceName:VersionNumber |
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Ryan, et al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2714">RFC 2714</a> Schema for CORBA Object References October 1999</span> |
| 167 |
|
| 168 |
|
| 169 |
For example, the repository id for the "NamingContext" in OMG's COS |
| 170 |
Naming module is: "IDL:omg.org/CosNaming/NamingContext:1.0". |
| 171 |
|
| 172 |
b. RMI-style |
| 173 |
|
| 174 |
RMI:ClassName:HashCode[:SUID] |
| 175 |
|
| 176 |
This format is used by RMI-IIOP remote objects [<a href="#ref-RMI-IIOP" title=""RMI over IIOP"">RMI-IIOP</a>]. |
| 177 |
"ClassName" is the fully qualified name of the class (for example, |
| 178 |
"java.lang.String"). "HashCode" is the object's hash code (that is, |
| 179 |
that obtained by invoking the "hashCode()" method). "SUID" is the |
| 180 |
"stream unique identifier", which is a 64-bit number that uniquely |
| 181 |
identifies the serialization version of the class; SUID is optional |
| 182 |
in the repository id. |
| 183 |
|
| 184 |
c. DCE-style |
| 185 |
|
| 186 |
DCE:UUID |
| 187 |
|
| 188 |
This format is used for DCE/CORBA interoperability [<a href="#ref-CORBA-DCE" title=""DCE/CORBA Interworking Specification"">CORBA-DCE</a>]. |
| 189 |
"UUID" represents a DCE UUID. |
| 190 |
|
| 191 |
d. "local" |
| 192 |
|
| 193 |
This format is defined by the local Object Request Broker (ORB). |
| 194 |
|
| 195 |
The corbaRepositoryId attribute is a multivalued attribute; each |
| 196 |
value records a single repository id of an interface implemented by |
| 197 |
the CORBA object. This attribute need not contain a complete list of |
| 198 |
the interfaces implemented by the CORBA object. |
| 199 |
|
| 200 |
This attribute's syntax is 'Directory String' and its case is |
| 201 |
significant. The values of this attribute are encoded using UTF-8. |
| 202 |
Some values may require translation from their native representation |
| 203 |
in order to be correctly encoded using UTF-8. |
| 204 |
|
| 205 |
( 1.3.6.1.4.1.42.2.27.4.1.15 |
| 206 |
NAME 'corbaRepositoryId' |
| 207 |
DESC 'Repository ids of interfaces implemented by a CORBA object' |
| 208 |
EQUALITY caseExactMatch |
| 209 |
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 |
| 210 |
) |
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Ryan, et al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2714">RFC 2714</a> Schema for CORBA Object References October 1999</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Object Class Definitions</span> |
| 226 |
|
| 227 |
The following object classes are defined in this document: |
| 228 |
|
| 229 |
corbaContainer |
| 230 |
corbaObject |
| 231 |
corbaObjectReference |
| 232 |
|
| 233 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> corbaContainer</span> |
| 234 |
|
| 235 |
This structural object class represents a container for a CORBA |
| 236 |
object. |
| 237 |
|
| 238 |
( 1.3.6.1.4.1.42.2.27.4.2.10 |
| 239 |
NAME 'corbaContainer' |
| 240 |
DESC 'Container for a CORBA object' |
| 241 |
SUP top |
| 242 |
STRUCTURAL |
| 243 |
MUST ( cn ) |
| 244 |
) |
| 245 |
|
| 246 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> corbaObject</span> |
| 247 |
|
| 248 |
This abstract object class is the root class for representing a CORBA |
| 249 |
object. |
| 250 |
|
| 251 |
( 1.3.6.1.4.1.42.2.27.4.2.9 |
| 252 |
NAME 'corbaObject' |
| 253 |
DESC 'CORBA object representation' |
| 254 |
SUP top |
| 255 |
ABSTRACT |
| 256 |
MAY ( corbaRepositoryId $ description ) |
| 257 |
) |
| 258 |
|
| 259 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> corbaObjectReference</span> |
| 260 |
|
| 261 |
This auxiliary object class represents a CORBA object reference. It |
| 262 |
must be mixed in with a structural object class. |
| 263 |
|
| 264 |
( 1.3.6.1.4.1.42.2.27.4.2.11 |
| 265 |
NAME 'corbaObjectReference' |
| 266 |
DESC 'CORBA interoperable object reference' |
| 267 |
SUP corbaObject |
| 268 |
AUXILIARY |
| 269 |
MUST ( corbaIor ) |
| 270 |
) |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Ryan, et al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2714">RFC 2714</a> Schema for CORBA Object References October 1999</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span> |
| 282 |
|
| 283 |
Obtaining a reference to an object and storing it in the directory |
| 284 |
may make a handle to the object available to a wider audience. This |
| 285 |
may have security implications. |
| 286 |
|
| 287 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span> |
| 288 |
|
| 289 |
We would like to thank Sanjeev Krishnan of Sun Microsystems, Simon |
| 290 |
Nash of IBM, and Jeffrey Spirn of Oracle for their comments and |
| 291 |
suggestions. |
| 292 |
|
| 293 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span> |
| 294 |
|
| 295 |
[<a id="ref-CORBA">CORBA</a>] The Object Management Group, "Common Object Request |
| 296 |
Broker Architecture Specification 2.2", |
| 297 |
<a href="http://www.omg.org">http://www.omg.org</a> |
| 298 |
|
| 299 |
[<a id="ref-CORBA-DCE">CORBA-DCE</a>] Distributed Systems Technology Center and Digital |
| 300 |
Equipment Corporation, "DCE/CORBA Interworking |
| 301 |
Specification", May 1998. |
| 302 |
<a href="http://www.omg.org/library/schedule/DCE_CORBA_Interworking_RFP.html">http://www.omg.org/library/schedule/</a> |
| 303 |
<a href="http://www.omg.org/library/schedule/DCE_CORBA_Interworking_RFP.html">DCE_CORBA_Interworking_RFP.html</a> |
| 304 |
|
| 305 |
[<a id="ref-LDAPv3">LDAPv3</a>] Wahl, M., Howes, T. and S. Kille, "Lightweight Directory |
| 306 |
Access Protocol (v3)", <a href="./rfc2251">RFC 2251</a>, December 1997. |
| 307 |
|
| 308 |
[<a id="ref-RMI-IIOP">RMI-IIOP</a>] IBM and Java Software, Sun Microsystems, Inc., "RMI over |
| 309 |
IIOP", June 1999. <a href="http://java.sun.com/products/rmi-iiop/index.html">http://java.sun.com/products/rmi-</a> |
| 310 |
<a href="http://java.sun.com/products/rmi-iiop/index.html">iiop/index.html</a> |
| 311 |
|
| 312 |
[<a id="ref-v3Schema">v3Schema</a>] Wahl, M., "A Summary of the X.500(96) User Schema for use |
| 313 |
with LDAPv3", <a href="./rfc2256">RFC 2256</a>, December 1997. |
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Ryan, et al. Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc2714">RFC 2714</a> Schema for CORBA Object References October 1999</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Authors' Addresses</span> |
| 338 |
|
| 339 |
Vincent Ryan |
| 340 |
Sun Microsystems, Inc. |
| 341 |
Mail Stop EDUB03 |
| 342 |
901 San Antonio Road |
| 343 |
Palo Alto, CA 94303 |
| 344 |
USA |
| 345 |
|
| 346 |
Phone: +353 1 819 9151 |
| 347 |
EMail: [email protected] |
| 348 |
|
| 349 |
|
| 350 |
Rosanna Lee |
| 351 |
Sun Microsystems, Inc. |
| 352 |
Mail Stop UCUP02-206 |
| 353 |
901 San Antonio Road |
| 354 |
Palo Alto, CA 94303 |
| 355 |
USA |
| 356 |
|
| 357 |
Phone: +1 408 863 3221 |
| 358 |
EMail: [email protected] |
| 359 |
|
| 360 |
|
| 361 |
Scott Seligman |
| 362 |
Sun Microsystems, Inc. |
| 363 |
Mail Stop UCUP02-209 |
| 364 |
901 San Antonio Road |
| 365 |
Palo Alto, CA 94303 |
| 366 |
USA |
| 367 |
|
| 368 |
Phone: +1 408 863 3222 |
| 369 |
EMail: [email protected] |
| 370 |
|
| 371 |
|
| 372 |
|
| 373 |
|
| 374 |
|
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Ryan, et al. Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc2714">RFC 2714</a> Schema for CORBA Object References October 1999</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Appendix </span>- LDAP Schema |
| 394 |
|
| 395 |
-- Attribute types -- |
| 396 |
|
| 397 |
( 1.3.6.1.4.1.42.2.27.4.1.14 |
| 398 |
NAME 'corbaIor' |
| 399 |
DESC 'Stringified interoperable object reference of a CORBA object' |
| 400 |
EQUALITY caseIgnoreIA5Match |
| 401 |
SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 |
| 402 |
SINGLE-VALUE |
| 403 |
) |
| 404 |
|
| 405 |
( 1.3.6.1.4.1.42.2.27.4.1.15 |
| 406 |
NAME 'corbaRepositoryId' |
| 407 |
DESC 'Repository ids of interfaces implemented by a CORBA object' |
| 408 |
EQUALITY caseExactMatch |
| 409 |
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 |
| 410 |
) |
| 411 |
|
| 412 |
-- from <a href="./rfc2256">RFC-2256</a> -- |
| 413 |
|
| 414 |
( 2.5.4.13 |
| 415 |
NAME 'description' |
| 416 |
EQUALITY caseIgnoreMatch |
| 417 |
SUBSTR caseIgnoreSubstringsMatch |
| 418 |
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024} |
| 419 |
) |
| 420 |
|
| 421 |
-- Object classes -- |
| 422 |
|
| 423 |
( 1.3.6.1.4.1.42.2.27.4.2.9 |
| 424 |
NAME 'corbaObject' |
| 425 |
DESC 'CORBA object representation' |
| 426 |
SUP top |
| 427 |
ABSTRACT |
| 428 |
MAY ( corbaRepositoryId $ description ) |
| 429 |
) |
| 430 |
|
| 431 |
( 1.3.6.1.4.1.42.2.27.4.2.10 |
| 432 |
NAME 'corbaContainer' |
| 433 |
DESC 'Container for a CORBA object' |
| 434 |
SUP top |
| 435 |
STRUCTURAL |
| 436 |
MUST ( cn ) |
| 437 |
) |
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Ryan, et al. Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc2714">RFC 2714</a> Schema for CORBA Object References October 1999</span> |
| 447 |
|
| 448 |
|
| 449 |
( 1.3.6.1.4.1.42.2.27.4.2.11 |
| 450 |
NAME 'corbaObjectReference' |
| 451 |
DESC 'CORBA interoperable object reference' |
| 452 |
SUP corbaObject |
| 453 |
AUXILIARY |
| 454 |
MUST ( corbaIor ) |
| 455 |
) |
| 456 |
|
| 457 |
-- Matching rule from ISO X.520 -- |
| 458 |
|
| 459 |
( 2.5.13.5 |
| 460 |
NAME 'caseExactMatch' |
| 461 |
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 |
| 462 |
) |
| 463 |
|
| 464 |
|
| 465 |
|
| 466 |
|
| 467 |
|
| 468 |
|
| 469 |
|
| 470 |
|
| 471 |
|
| 472 |
|
| 473 |
|
| 474 |
|
| 475 |
|
| 476 |
|
| 477 |
|
| 478 |
|
| 479 |
|
| 480 |
|
| 481 |
|
| 482 |
|
| 483 |
|
| 484 |
|
| 485 |
|
| 486 |
|
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Ryan, et al. Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc2714">RFC 2714</a> Schema for CORBA Object References October 1999</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Full Copyright Statement</span> |
| 506 |
|
| 507 |
Copyright (C) The Internet Society (1999). All Rights Reserved. |
| 508 |
|
| 509 |
This document and translations of it may be copied and furnished to |
| 510 |
others, and derivative works that comment on or otherwise explain it |
| 511 |
or assist in its implementation may be prepared, copied, published |
| 512 |
and distributed, in whole or in part, without restriction of any |
| 513 |
kind, provided that the above copyright notice and this paragraph are |
| 514 |
included on all such copies and derivative works. However, this |
| 515 |
document itself may not be modified in any way, such as by removing |
| 516 |
the copyright notice or references to the Internet Society or other |
| 517 |
Internet organizations, except as needed for the purpose of |
| 518 |
developing Internet standards in which case the procedures for |
| 519 |
copyrights defined in the Internet Standards process must be |
| 520 |
followed, or as required to translate it into languages other than |
| 521 |
English. |
| 522 |
|
| 523 |
The limited permissions granted above are perpetual and will not be |
| 524 |
revoked by the Internet Society or its successors or assigns. |
| 525 |
|
| 526 |
This document and the information contained herein is provided on an |
| 527 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 528 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 529 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 530 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 531 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 532 |
|
| 533 |
Acknowledgement |
| 534 |
|
| 535 |
Funding for the RFC Editor function is currently provided by the |
| 536 |
Internet Society. |
| 537 |
|
| 538 |
|
| 539 |
|
| 540 |
|
| 541 |
|
| 542 |
|
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
Ryan, et al. Informational [Page 10] |
| 557 |
</pre> |