idnits 2.17.1 draft-ietf-schema-rwhois-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 13 longer pages, the longest (page 1) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 5 instances of too long lines in the document, the longest one being 2 characters in excess of 72. ** The abstract seems to contain references ([2], [3], [4], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 13, 1998) is 9541 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 632 looks like a reference -- Missing reference section? '2' on line 636 looks like a reference -- Missing reference section? '3' on line 639 looks like a reference -- Missing reference section? '4' on line 642 looks like a reference -- Missing reference section? '5' on line 645 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Michael Mealling 3 Request for Comments: DRAFT Network Solutions, Inc. 4 March 13, 1998 6 A MIME Directory Profile for RWhois 1.5 Schema 7 9 1. Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its areas, 13 and its working groups. Note that other groups may also distribute 14 working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six months 17 and may be updated, replaced, or obsoleted by other documents at any 18 time. It is inappropriate to use Internet-Drafts as reference 19 material or to cite them other than as ``work in progress.'' 21 To learn the current status of any Internet-Draft, please check the 22 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 23 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 24 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 25 ftp.isi.edu (US West Coast). 27 2. Abstract 29 This document defines two MIME directory profiles [1] for holding a 30 RWhois 1.5 [2] schema. It is intended for communication with the 31 Internet schema listing service [3]. One profile defines an attribute 32 and the other defines a class. 34 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 35 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 36 this document are to be interpreted as described in RFC 2119 [4]. 38 3. Overview 40 RWhois 1.5 has the concepts of attributes and classes. A schema in 41 the sense used by Internet schema listing service is analogous to 42 an RWhois class. A class definition in RWhois is simply the listing 43 of attributes that are well understood for that class. There is a 44 desire in many directory services to encourage attribute definition 45 re-use. Therefore, this schema description service will separate 46 the attribute descriptions from the class descriptions. 48 The MIME-DIR specification describes how relationships between 49 objects included in a multipart/related MIME type can be specified. 50 This is used by the class profile to include by reference all of 51 the attribute definitions included within one multipart/related 52 MIME object. 54 Due to the requirements of the schema listing service, there must be 55 one 'top' profile, which is called 'schema-rwhois-0'. Since the 'top' 56 of the RWhois schema definition is the class, the class definition's 57 profile name will be 'schema-rwhois-0'. The attribute definition will 58 use the profile name 'rwhois-attribute-0'. 60 4. Multipart/related header values 62 The schema listing service's infrastructure depends on an easily 63 parsed and easily navigated structure of filenames in a directory. In 64 some cases the definition of a schema is contained in one MIME-DIR 65 profile. This makes for a simple correlation to one file and also 66 makes it easy to find that file's profile and schema name. 68 In the case of RWhois' class and attribute objects this is not so 69 simple as the actual schema name would be in the 70 multipart/related's start object. Luckily the multipart/related 71 standard gives us the "Start-Info" parameter. For the purposes of 72 the schema-listing application's use of RWhois schema this parameter 73 is used to denote the profile of the start object. 75 All other attributes have standard values. This leaves us with 76 the following specification: 78 'boundary' has its standard RFC2046 specified value 79 'start' is the CID of the 'schema-rwhois-0' or class object 80 'type' MUST be 'text/directory' 81 'start-info' MUST be 'schema-rwhois-0' 82 An example: 84 To: ietf-schema-review@TBD 85 Subject: schema unit listing request 86 MIME-Version: 1.0 87 Message-Id: 88 Content-Type: multipart/related; boundary="boundary"; 89 start=3@foo.com; type="text/directory"; 90 start-info="schema-rwhois-0" 91 Content-ID: top@foo.com 93 --boundary 94 Content-Type: text/directory; profile="schema-rwhois-0" 95 Content-Transfer-Encoding: Quoted-Printable 96 Content-ID: 3@foo.com 98 (class description elements and values as specified in Section 5, 99 which includes a reference to an attribute whose CID is 4@foo.com) 101 --boundary 102 Content-Type: text/directory; profile="rwhois-attribute-0>" 103 Content-Transfer-Encoding: Quoted-Printable 104 Content-ID: 4@foo.com 106 (an RWhois attribute definition) 108 --boundary 110 5. schema-rwhois-0 definition 112 The schema-rwhois-0 definition is extremely straightforward. It 113 is a combination of the '-schema' and '-class' directives defined 114 in RFC2167. The class directive defines the description and version 115 of the class. The schema directive defines the attributes that are 116 valid for that class but also lists the description of the values 117 themselves. For ease of parsing, this class definition will include 118 the attribute name. Therefore, the attribute definition object will not 119 have to be parsed in order to allow for the most basic function of 120 showing the user the attribute and plain text value. 122 Therefore, the well understood attributes for the schema-rwhois-0 123 profile are as follows: 125 'name' contains the class' name 126 'description' contains a plain text description of the class 127 'version' contains the version as specified by RFC2167 128 'attribute' contains the attribute name and the CID of its definition 129 The syntax of the 'attribute' value is as follows: 131 attribute-value = name " " CID 132 name=1*id-char 133 CID = Content-ID as defined as used in RFC1873 [5] 134 id-char = alpha / digit / "_" / "-" 135 alpha = "a".."z" / "A".."Z" 136 digit = "0".."9" 138 Example: 140 Content-Type: text/directory; profile="schema-rwhois-0" 141 Content-Transfer-Encoding: Quoted-Printable 142 Content-ID: 3@foo.com 144 Name: Referral 145 Description: Required class for specifying a referral 146 Version: 19961101 147 Attribute: Referred-Auth-Area 4@foo.com 148 Attribute: Referral 5@foo.com 150 This example in its entirety would be included as the start object of 151 a multipart/related object that included the 4@foo.com and 5@foo.com 152 objects. 154 The MIME-DIR profile registration template is included in Section 8. 156 6. rwhois-attribute-0 definition 158 The rwhois attribute definition profile is also fairly 159 straightforward since it follows the '-schema' directive very closely. 160 The RFC2167 defined attribute properties are: 162 Attribute This is the name of the attribute. 164 Description This is a natural language description of the 165 attribute. 167 Type This is a parameter that broadly indicates the use 168 of the attribute to the protocol. There are three 169 standard types: TEXT, ID, and SEE-ALSO. 171 Format This is an interpretable string that describes the 172 acceptance format of the value. 174 Indexed This is a true or false flag indicating that this 175 attribute should be indexed (and therefore able to be 176 searched). 178 Required This is a true or false flag indicating that this 179 attribute must have a value in an instance of the 180 class. 182 Multi-Line This is a true or false flag indicating that this 183 attribute may have multiple instances in a class, but 184 all of the instances are to be considered as multiple 185 lines of the same attribute instance. This allows 186 normal line terminators to terminate values. 188 Repeatable This is a true or false flag indicating that there may 189 be multiple instances of this attribute in a class and 190 each instance is to be interpreted as a separate 191 instance (in contrast to Multi-Line). 193 Primary This is a true or false flag that indicates that this 194 attribute is a primary key. 196 Hierarchical This is a true or false flag that indicates that this 197 attribute is lexically hierarchical. 199 Private This is a true or false flag that indicates whether or 200 not this attribute is private (that is, publicly not 201 viewable). 203 Each of these properties corresponds exactly to an attribute in the 204 'rwhois-attribute-0' profile except that 'rwhoisAttrDef' is 205 prepended to the attribute name. The values follow the ABNF specified 206 in RFC2167. 208 Example: 210 Content-Type: text/directory; profile="rwhois-attribute-0>" 211 Content-Transfer-Encoding: Quoted-Printable 212 Content-ID: 4@foo.com 214 rwhoisAttrDefAttribute: Referral 215 rwhoisAttrDefFormat: none 216 rwhoisAttrDefDescription: Referral to an RWhois server 217 rwhoisAttrDefIndexed: OFF 218 rwhoisAttrDefRequired: ON 219 rwhoisAttrDefMulti-line: OFF 220 rwhoisAttrDefRepeatable: ON 221 rwhoisAttrDefHierarchical: OFF 222 rwhoisAttrDefPrivate: OFF 223 rwhoisAttrDefType: Text 224 rwhoisAttrDefPrimary: OFF 226 7. Full example 228 This is a full example of a schema object that is intended to be 229 registered with the schema listing service. It represents the Base 230 class which every RWhois class must include. 232 To: ietf-schema-review@TBD 233 Subject: schema unit listing request 234 MIME-Version: 1.0 235 Message-Id: 236 Content-Type: multipart/related; boundary="boundary"; 237 start=3@foo.com; type="text/directory"; 238 start-info="schema-rwhois-0" 239 Content-ID: top@foo.com 241 --boundary 242 Content-Type: text/directory; profile="schema-rwhois-0" 243 Content-Transfer-Encoding: Quoted-Printable 244 Content-ID: 3@foo.com 246 Name: Base 247 Description: The RWhois 1.5 Base class from which all classes inherit 248 Version: 19961101 249 Attribute: Class-Name 4@foo.com 250 Attribute: Auth-Area 5@foo.com 251 Attribute: ID 6@foo.com 252 Attribute: Updated 7@foo.com 253 Attribute: Guardian 8@foo.com 254 Attribute: Private 9@foo.com 255 Attribute: TTL 10@foo.com 257 --boundary 258 Content-Type: text/directory; profile="rwhois-attribute-0>" 259 Content-Transfer-Encoding: Quoted-Printable 260 Content-ID: 4@foo.com 262 rwhoisAttrDefAttribute: Class-Name 263 rwhoisAttrDefFormat: none 264 rwhoisAttrDefDescription: Type of the object. 265 rwhoisAttrDefIndexed: OFF 266 rwhoisAttrDefRequired: ON 267 rwhoisAttrDefMulti-line: OFF 268 rwhoisAttrDefRepeatable: OFF 269 rwhoisAttrDefHierarchical: OFF 270 rwhoisAttrDefPrivate: OFF 271 rwhoisAttrDefType: Text 272 rwhoisAttrDefPrimary: OFF 274 --boundary 275 Content-Type: text/directory; profile="rwhois-attribute-0>" 276 Content-Transfer-Encoding: Quoted-Printable 277 Content-ID: 5@foo.com 279 rwhoisAttrDefAttribute: Auth-Area 280 rwhoisAttrDefFormat: none 281 rwhoisAttrDefDescription: Authority area to which the object belongs 282 rwhoisAttrDefIndexed: OFF 283 rwhoisAttrDefRequired: ON 284 rwhoisAttrDefMulti-line: OFF 285 rwhoisAttrDefRepeatable: OFF 286 rwhoisAttrDefHierarchical: ON 287 rwhoisAttrDefPrivate: OFF 288 rwhoisAttrDefType: Text 289 rwhoisAttrDefPrimary: OFF 291 --boundary 292 Content-Type: text/directory; profile="rwhois-attribute-0>" 293 Content-Transfer-Encoding: Quoted-Printable 294 Content-ID: 6@foo.com 296 rwhoisAttrDefAttribute: ID 297 rwhoisAttrDefFormat: none 298 rwhoisAttrDefDescription: Globally unique object identifier 299 rwhoisAttrDefIndexed: ON 300 rwhoisAttrDefRequired: OFF 301 rwhoisAttrDefMulti-line: OFF 302 rwhoisAttrDefRepeatable: OFF 303 rwhoisAttrDefHierarchical: ON 304 rwhoisAttrDefPrivate: OFF 305 rwhoisAttrDefType: Text 306 rwhoisAttrDefPrimary: OFF 308 --boundary 309 Content-Type: text/directory; profile="rwhois-attribute-0>" 310 Content-Transfer-Encoding: Quoted-Printable 311 Content-ID: 7@foo.com 313 rwhoisAttrDefAttribute: Updated 314 rwhoisAttrDefFormat: none 315 rwhoisAttrDefDescription: Last modification time/serial number 316 rwhoisAttrDefIndexed: OFF 317 rwhoisAttrDefRequired: OFF 318 rwhoisAttrDefMulti-line: OFF 319 rwhoisAttrDefRepeatable: OFF 320 rwhoisAttrDefHierarchical: OFF 321 rwhoisAttrDefPrivate: OFF 322 rwhoisAttrDefType: Text 323 rwhoisAttrDefPrimary: OFF 325 --boundary 326 Content-Type: text/directory; profile="rwhois-attribute-0>" 327 Content-Transfer-Encoding: Quoted-Printable 328 Content-ID: 8@foo.com 330 rwhoisAttrDefAttribute: Guardian 331 rwhoisAttrDefFormat: none 332 rwhoisAttrDefDescription: Guardian object 333 rwhoisAttrDefIndexed: OFF 334 rwhoisAttrDefRequired: OFF 335 rwhoisAttrDefMulti-line: OFF 336 rwhoisAttrDefRepeatable: ON 337 rwhoisAttrDefHierarchical: OFF 338 rwhoisAttrDefPrivate: OFF 339 rwhoisAttrDefType: ID 340 rwhoisAttrDefPrimary: OFF 342 --boundary 343 Content-Type: text/directory; profile="rwhois-attribute-0>" 344 Content-Transfer-Encoding: Quoted-Printable 345 Content-ID: 9@foo.com 347 rwhoisAttrDefAttribute:Private 348 rwhoisAttrDefFormat:none 349 rwhoisAttrDefDescription:object is private 350 rwhoisAttrDefIndexed:OFF 351 rwhoisAttrDefRequired:OFF 352 rwhoisAttrDefMulti-line:OFF 353 rwhoisAttrDefRepeatable:OFF 354 rwhoisAttrDefHierarchical:OFF 355 rwhoisAttrDefPrivate:ON 356 rwhoisAttrDefType:Text 357 rwhoisAttrDefPrimary:OFF 359 --boundary 360 Content-Type: text/directory; profile="rwhois-attribute-0>" 361 Content-Transfer-Encoding: Quoted-Printable 362 Content-ID: 10@foo.com 364 rwhoisAttrDefAttribute:TTL 365 rwhoisAttrDefFormat:none 366 rwhoisAttrDefDescription:Time to live 367 rwhoisAttrDefIndexed:OFF 368 rwhoisAttrDefRequired:OFF 369 rwhoisAttrDefMulti-line:OFF 370 rwhoisAttrDefRepeatable:OFF 371 rwhoisAttrDefHierarchical:OFF 372 rwhoisAttrDefPrivate:OFF 373 rwhoisAttrDefType:Text 374 rwhoisAttrDefPrimary:OFF 376 --boundary 378 8. Registration Templates 380 8.1 'schema-rwhois-0' profile registration template 382 To: ietf-mime-direct@imc.org 383 Subject: Registration of text/directory profile "schema-rwhois-0" 385 Profile name: schema-rwhois-0 387 Profile purpose: To represent the RWhois 1.5 class definition as 388 defined in RFC2167. 390 Profile types: name, description, version, attribute 392 Profile special notes: 394 Neither the "BEGIN" and "END" types nor type grouping are used 395 in contents of this profile. 397 The only type which is allowed to be multi-valued is 'attribute'. 399 The SOURCE type is optional, and if values are present it is 400 suggested that they be a rwhois URI as RWhois schema definitions 401 from other sources have not been investigated. 403 Intended usage: COMMON 405 8.2 'schema-rwhois-0' 'rwhoisAttrDefAttribute' type template 407 To: ietf-mime-direct@imc.org 408 Subject: Registration of text/directory type rwhoisAttrDefAttribute 410 Type name: rwhoisAttrDefAttribute 412 Type purpose: This is the name of the attribute. 414 Type encoding: 8bit 416 Type valuetype: text 418 Type special notes: This value must follow the rules as specified 419 in RFC2167. 421 Intended usage: COMMON 423 8.3 'schema-rwhois-0' 'rwhoisAttrDefDescription' type template 425 To: ietf-mime-direct@imc.org 426 Subject: Registration of text/directory type rwhoisAttrDefDescription 428 Type name: rwhoisAttrDefDescription 430 Type purpose: This is a natural language description of the 431 attribute. 433 Type encoding: 8bit 435 Type valuetype: text 437 Type special notes: This value must follow the rules as specified 438 in RFC2167. 440 Intended usage: COMMON 442 8.4 'schema-rwhois-0' 'rwhoisAttrDefType' type template 444 To: ietf-mime-direct@imc.org 445 Subject: Registration of text/directory type rwhoisAttrDefType 447 Type name: rwhoisAttrDefType 449 Type purpose: This is a parameter that broadly indicates the use 450 of the attribute to the protocol. There are three 451 standard types: TEXT, ID, and SEE-ALSO. 453 Type encoding: 8bit 455 Type valuetype: text 457 Type special notes: This value must follow the rules as specified 458 in RFC2167. 460 Intended usage: COMMON 462 8.5 'schema-rwhois-0' 'rwhoisAttrDefFormat' type registration template 464 To: ietf-mime-direct@imc.org 465 Subject: Registration of text/directory MIME type rwhoisAttrDefFormat 467 Type name: rwhoisAttrDefFormat 469 Type purpose: This is an interpretable string that describes the 470 acceptance format of the value. 472 Type encoding: 8bit 474 Type valuetype: text 476 Type special notes: This value must follow the rules as specified 477 in RFC2167. 479 Intended usage: COMMON 481 8.6 'schema-rwhois-0' 'rwhoisAttrDefIndexed' type template 483 To: ietf-mime-direct@imc.org 484 Subject: Registration of text/directory type rwhoisAttrDefIndexed 486 Type name: rwhoisAttrDefIndexed 487 Type purpose: This is a true or false flag indicating that this 488 attribute should be indexed (and therefore able to be 489 searched). 491 Type encoding: 8bit 493 Type valuetype: text 495 Type special notes: This value must follow the rules as specified 496 in RFC2167. 498 Intended usage: COMMON 500 8.7 'schema-rwhois-0' 'rwhoisAttrDefRequired' type template 502 To: ietf-mime-direct@imc.org 503 Subject: Registration of text/directory type rwhoisAttrDefRequired 505 Type name: rwhoisAttrDefRequired 507 Type purpose: This is a true or false flag indicating that this 508 attribute must have a value in an instance of 509 the class. 511 Type encoding: 8bit 513 Type valuetype: text 515 Type special notes: This value must follow the rules as specified 516 in RFC2167. 518 Intended usage: COMMON 520 8.8 'schema-rwhois-0' 'rwhoisAttrDefMulti-Line' type template 522 To: ietf-mime-direct@imc.org 523 Subject: Registration of text/directory type rwhoisAttrDefMulti-Line 525 Type name: rwhoisAttrDefMulti-Line 527 Type purpose: This is a true or false flag indicating that this 528 attribute may have multiple instances in a class, but 529 all of the instances are to be considered as multiple 530 lines of the same attribute instance. This allows 531 normal line terminators to terminate values. 533 Type encoding: 8bit 535 Type valuetype: text 537 Type special notes: This value must follow the rules as specified 538 in RFC2167. 540 Intended usage: COMMON 542 8.9 'schema-rwhois-0' 'rwhoisAttrDefRepeatable' type template 544 To: ietf-mime-direct@imc.org 545 Subject: Registration of text/directory type rwhoisAttrDefRepeatable 547 Type name: rwhoisAttrDefRepeatable 549 Type purpose: This is a true or false flag indicating that there may 550 be multiple instances of this attribute in a class and 551 each instance is to be interpreted as a separate 552 instance (in contrast to Multi-Line). 554 Type encoding: 8bit 556 Type valuetype: text 558 Type special notes: This value must follow the rules as specified 559 in RFC2167. 561 Intended usage: COMMON 563 8.10 'schema-rwhois-0' 'rwhoisAttrDefPrimary' type template 565 To: ietf-mime-direct@imc.org 566 Subject: Registration of text/directory MIME type rwhoisAttrDefPrimary 568 Type name: rwhoisAttrDefPrimary 570 Type purpose: This is a true or false flag that indicates that this 571 attribute is a primary key. 572 Type encoding: 8bit 574 Type valuetype: text 576 Type special notes: This value must follow the rules as specified 577 in RFC2167. 579 Intended usage: COMMON 581 8.11 'schema-rwhois-0' 'rwhoisAttrDefHierarchical' type template 583 To: ietf-mime-direct@imc.org 584 Subject: Registration of text/directory type rwhoisAttrDefHierarchical 586 Type name: rwhoisAttrDefHierarchical 588 Type purpose: This is a true or false flag that indicates that this 589 attribute is lexically hierarchical. 591 Type encoding: 8bit 593 Type valuetype: text 594 Type special notes: This value must follow the rules as specified 595 in RFC2167. 597 Intended usage: COMMON 599 8.12 'schema-rwhois-0' 'rwhoisAttrDefPrivate' type template 601 To: ietf-mime-direct@imc.org 602 Subject: Registration of text/directory MIME type rwhoisAttrDefPrivate 604 Type name: rwhoisAttrDefPrivate 606 Type purpose: This is a true or false flag that indicates whether or 607 not this attribute is private (that is, publicly not 608 viewable). 610 Type encoding: 8bit 612 Type valuetype: text 614 Type special notes: This value must follow the rules as specified 615 in RFC2167. 617 Intended usage: COMMON 619 9. Author's Contact 621 Michael Mealling 622 Network Solutions 623 505 Huntmar Park Drive 624 Herndon, VA 22070 625 voice: (703) 742-0400 626 fax: (703) 742-9552 627 email: michaelm@netsol.com 628 URL: http://www.netsol.com/ 630 10. References: 632 [1] Howes, Tim, Mark Smith, Frank Dawson. "A MIME Content-Type for 633 Directory Information", 07/24/1997, INTERNET DRAFT 634 . 636 [2] Williamson, S., M. Kosters, et al. "Referral Whois (RWhois) 637 Protocol V1.5", 06/01/1997, RFC2167. 639 [3] Apple, C. "Directory Schema Listing Requirements", 08/28/1997, 640 INTERNET DRAFT . 642 [4] Bradner, S. "Key words for use in RFCs to Indicate Requirement 643 Levels", 3/01/1997, RFC2119. 645 [5] Levinson, E., J. Clark, "Message/External-Body Content-ID Access 646 Type", RFC1872, 12/01/95.