idnits 2.17.1 draft-ema-vpimdir-schema-00.txt: 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-16) 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 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 the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** The document is more than 15 pages and seems to lack a Table of Contents. == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 815 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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.) ** There are 2 instances of too long lines in the document, the longest one being 3 characters in excess of 72. ** There is 1 instance of lines with control characters in the document. ** The abstract seems to contain references ([VPIM2]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There is 16 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 1: '...T DRAFT EXPIRES MAY 1998 INTERNET DRA...' RFC 2119 keyword, line 353: '... MUST CONTAIN { e164Di...' RFC 2119 keyword, line 361: '... MUST e164Digit)...' RFC 2119 keyword, line 386: '... MAY CONTAIN { vPIMrf...' RFC 2119 keyword, line 399: '... MAY ( vPIMrfc822Mailbox $...' (4 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 712 has weird spacing: '...ngTypes id-...' == Line 718 has weird spacing: '...164Node id-vp...' == Line 720 has weird spacing: '...PIMUser id-vp...' == Line 739 has weird spacing: '...t Class by...' == Line 741 has weird spacing: '...ameForm id-v...' == (1 more instance...) -- 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 (November 18, 1997) is 9646 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- -- Missing reference section? 'VPIM2' on line 798 looks like a reference -- Missing reference section? 'ATTRIBS04' on line 792 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 8 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET DRAFT EXPIRES MAY 1998 INTERNET DRAFT 2 Network Working Group A. Brown 3 Internet Draft Nortel Technology 4 Expires: May 24, 1998 November 18, 1997 5 Category: Experimental 7 VPIM Directory 8 Schema Definition & Profile 9 11 Status of this Memo 13 This document is an Internet-Draft. Internet-Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its 15 areas, and its working groups. Note that other groups may also 16 distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six 19 months and may be updated, replaced, or obsoleted by other 20 documents at any time. It is inappropriate to use Internet- 21 Drafts as reference material or to cite them other than as 22 "work in progress." 24 To view the entire list of current Internet-Drafts, please check 25 the "1id-abstracts.txt" listing contained in the Internet-Drafts 26 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 27 (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East 28 Coast), or ftp.isi.edu (US West Coast). 30 Abstract 32 One use of a directory service is the retrieval of 33 information, such as email address and spoken name, to 34 support voice messsaging. This document defines the 35 directory schema required for an X.500/LDAP-based 36 directory service for use by applications supporting 37 Voice Profile for Internet Mail [VPIM2]. The directory 38 service is intended to assist the exchange of voice 39 messages between voice messaging systems. Interaction 40 with desktop applications is outside the scope of this 41 draft. 43 Some schema elements defined herin may be of more 44 general use than just for voice messaging. They are 45 included here because they are not defined elsewhere. 46 It is anticipated that the next version of this schema 47 will only reference such definitions if they get 48 defined in more appropriate areas. 50 This schema will be used to support a pilot VPIM 51 directory service based on X.500 93 and LDAPv2. This 52 next version of the schema will support X.500 97 and 53 LDAPv3. 55 1. Overview 57 This document defines a set of X.500/LDAP object 58 classes and attributes for use in a voice messsaging 59 directory service. Also defined are X.500 DIT content 60 rules, name forms and DIT structure rules. 62 The directory structure provides clients with the 63 ability to access directory information, given only a 64 telephone number. The voice messaging directory is 65 structured according to the E.164 numbering plan, with 66 each node in the tree representing a single digit of an 67 E.164 telephone number. Given a telephone number, an 68 LDAP client can pinpoint an entry in the voice 69 messaging tree. This structure allows voice messaging 70 systems to retrieve information without having to 71 perform a global search for a telephone number and 72 without having to understand different numbering plan 73 structures. 75 Other numbering plans besides E.164, and other 76 alphanumeric identity structures, such calling cards 77 and user IDs, can also be supported by similar tree 78 stuctures. 80 2. General Issues 82 Attribute type and object class definitions for use 83 with X.500 are written using Abstract Syntax Notation 84 One [ASN.1]. Equivalent attribute type and object 85 class definitions for use with LDAP are written using 86 the BNF form of AttributeTypeDescription and 87 ObjectClassDescription given in [ATTRIBS04]. Lines 88 have been folded for readability. 90 Schema definitions for use only with X.500 are defined 91 only in ASN.1. 93 3. Attributes 95 3.1 Sub-Tree Node Naming Attribute 97 The VPIM directory is structured in a hierarchy whereby 98 each node in the tree represents a single digit of an 99 E.164 telephone number. The higher in the tree a digit 100 is, the higher its significance in the telephone 101 number. The e164Digit attribute type is used for 102 naming nodes in the tree. Since the nodes in the tree 103 are named by a single digit, the e164Digit attribute 104 shall have a length of one digit. e164Digit will be 105 abbreviated to ed for this document. Some examples of 106 Distinguished Name composed from e164Digits are: 108 A telephone number of +1 613 765 1234 would have the 109 following corresponding Distinguished Name in the VPIM 110 directory: 112 ed=4, ed=3, ed=2, ed=1, ed=5, ed=6, ed=7, ed=3, ed=1, ed=6, ed=1, 113 o=some commonly agreed upon prefix 115 Telephone number +1 613 765 1234 with extension 555 116 would result in the following Distinguished Name: 118 ed=5, ed=5, ed=5, ed=4, ed=3, ed=2, ed=1, ed=5, ed=6, ed=7, ed=3, 119 ed=1, ed=6, ed=1, o=some commonly agreed upon prefix 121 The ASN.1 definition of e164Digit for X.500 122 implementations is: 124 e164Digit ATTRIBUTE ::= { 125 WITH SYNTAX NumericString (SIZE(ub-vpim-at-e164Digit)) 126 EQUALITY MATCHING RULE numericStringMatch 127 ID id-vpim-at-e164Digit} 129 ub-vpim-at-e164Digit INTEGER ::= 1 131 The BNF definition of e164Digit for use with LDAP is: 133 (2.16.840.1.113694.1.2.1.1.1 NAME 'e164Digit' 134 EQUALITY 2.5.13.8 135 SYNTAX '1.3.6.1.4.1.1466.115.121.1.36 {1}') 137 3.2 Voice Messaging Internet Mail Address 139 The attribute vPIMrfc822Mailbox stores the SMTP address 140 of a voice mailbox. It is defined as a distinct 141 attribute to distinguish it from the rfc822Mailbox 142 attribute that may be used for other purposes. Although 143 it would be preferable to define vPIMrfc822Mailbox as a 144 subtype of rfc822Mailbox, it is defined here as an 145 entirely new attribute because some directory 146 implementations do not support sub-typing. 148 The more desirable vCard emailoption (e.g. email:VPIM) 149 can be supported when X.500 97 and LDAPv3 products are 150 more readily available. With 1997 X.500 Directory 151 implementations, Directory Contexts will be used to 152 distinguish the VPIM value of email from other uses of 153 the email attribute type. Attribute Description will 154 be used to perform a similar function for LDAP. When 155 these implementations become more widespread, 156 subsequent versions of this document will be released 157 with the new schema. 159 The ASN.1 definition for X.500 implementations is: 161 vPIMrfc822Mailbox ATTRIBUTE ::= { 162 WITH SYNTAX caseIgnoreIA5StringSyntax 163 (SIZE (1 .. ub-rfc822-mailbox)) -- from RFC 1274 164 ID id-vpim-at-vPIMrfc822Mailbox } 166 --Note: The definition for vPIMrfc822Mailbox is 167 identical to that defined for rfc822Mailbox in 168 RFC 1274, except that vPIMrfc822Mailbox has a 169 different object identifier and is defined 170 using X.501 1993 as opposed to 1988 attribute 171 type definition notation. 173 The BNF definition for use with LDAP is: 175 (2.16.840.1.113694.1.2.1.1.2 NAME 'vPIMrfc822Mailbox' 176 EQUALITY 1.3.6.1.4.1.1466.109.114.2 177 SYNTAX '1.3.6.1.4.1.1466.115.121.1.26 {256}') 179 3.3 Text Name 181 The attribute commonName, abbreviated as cn, stores the 182 values of text name. The formatted name, FN, defined 183 for vCard, is based on the semantics of the X.520 184 Common Name attribute. 186 The ASN.1 definition for X.500 implementations can be 187 found in X.520. The BNF definition for use with LDAP 188 can be found in . 191 3.4 Spoken Name 193 The vPIMSpokenName attribute is an octet string and 194 should be encoded in 32 kbit/s ADPCM exactly as defined 195 by ITU-T Recommendation G.726. SpokenName shall contain 196 the spoken name of the user in the voice of the user. 197 The length of the spoken name segment must not exceed 198 12 seconds. Private or additional encoding types are 199 outside the scope of this version. When X.500 97 and 200 LDAPv3 implementations are widely used, additional 201 encoding types will be supported. The definition of 202 private types is a local matter and thus not subject to 203 standardization. 205 The ASN.1 definition for X.500 implementations is: 207 vPIMSpokenName ATTRIBUTE ::= { 208 WITH SYNTAX OCTET STRING 209 (SIZE (1..ub-vpim-at-vPIMSpokenName) 210 EQUALITY MATCHING RULE octetStringMatch 211 ID id-vpim-at-vPIMSpokenName } 213 ub-vpim-at-vPIMSpokenName INTEGER ::= 4000 215 The BNF definition for use with LDAP is: 217 (2.16.840.1.113694.1.2.1.1.3 NAME 'vPIMSpokenName' 218 EQUAILTY 2.5.13.17 219 SYNTAX '1.3.6.1.4.1.1466.115.121.1.40 {4000}') 221 For support of other encoding types for spoken, the 222 following four attribute types are also defined in 223 ASN.1 and BNF as follows: 225 vPIMSpokenName1 ATTRIBUTE ::= { 226 WITH SYNTAX OCTET STRING 227 (SIZE (1..ub-vpim-at-vPIMSpokenName) 228 EQUALITY MATCHING RULE octetStringMatch 229 ID id-vpim-at-vPIMSpokenName1 } 231 vPIMSpokenName2 ATTRIBUTE ::= { 232 WITH SYNTAX OCTET STRING 233 (SIZE (1..ub-vpim-at-vPIMSpokenName) 234 EQUALITY MATCHING RULE octetStringMatch 235 ID id-vpim-at-vPIMSpokenName2 } 237 vPIMSpokenName3 ATTRIBUTE ::= { 238 WITH SYNTAX OCTET STRING 239 (SIZE (1..ub-vpim-at-vPIMSpokenName) 240 EQUALITY MATCHING RULE octetStringMatch 241 ID id-vpim-at-vPIMSpokenName3 } 243 vPIMSpokenName4 ATTRIBUTE ::= { 244 WITH SYNTAX OCTET STRING 245 (SIZE (1..ub-vpim-at-vPIMSpokenName) 246 EQUALITY MATCHING RULE octetStringMatch 247 ID id-vpim-at-vPIMSpokenName4 } 249 (2.16.840.1.113694.1.2.1.1.3.1 NAME 'vPIMSpokenName1' 250 EQUAILTY 2.5.13.17 251 SYNTAX '1.3.6.1.4.1.1466.115.121.1.40 {4000}') 253 (2.16.840.1.113694.1.2.1.1.3.2 NAME 'vPIMSpokenName2' 254 EQUAILTY 2.5.13.17 255 SYNTAX '1.3.6.1.4.1.1466.115.121.1.40 {4000}') 257 (2.16.840.1.113694.1.2.1.1.3.3 NAME 'vPIMSpokenName3' 258 EQUAILTY 2.5.13.17 259 SYNTAX '1.3.6.1.4.1.1466.115.121.1.40 {4000}') 261 (2.16.840.1.113694.1.2.1.1.3.4 NAME 'vPIMSpokenName4' 262 EQUAILTY 2.5.13.17 263 SYNTAX '1.3.6.1.4.1.1466.115.121.1.40 {4000}') 265 Use of these additional spoken name definitions will be 266 defined as required in experimenatal trials. 267 Subsequent versions of this document will use one 268 attribute type to store all encoding types of spoken 269 name. 271 3.5 Supported Encoding Types 273 The vPIMSupportedEncodingTypes attribute indicates the 274 type(s) of encodings that can be received at the 275 address specified in vPIMrfc822Mailbox. 277 The ASN.1 definition for X.500 implementations is: 279 vPIMSupportedEncodingTypes ATTRIBUTE ::= { 280 WITH SYNTAX DirectoryString 281 EQUALITY MATCHING RULE caseIgnoreMatch 282 ID id-vpim-at-vPIMSupportedEncodingTypes } 284 The BNF definition of vPIMSupportedEncodingTypes for 285 use with LDAP is: 287 (2.16.840.1.113694.1.2.1.1.4 NAME 288 'vPIMSupportedEncodingTypes' 289 EQUALITY 2.5.13.2 290 SYNTAX '1.3.6.1.4.1.1466.115.121.1.15') 292 The allowable values of DirectoryString for this 293 version of the schema are: 295 audio/32KADPCM 296 image/tiff 298 Additional publicly-defined extensions, registered with 299 IANA as specified in RFC 2048, may also used. Non- 300 standard and private encoding types must be indicated 301 py prepending the new type name with either "X-" or "x-". 303 The existance of the value "image/tiff" indicates that 304 fax is enabled for the mailbox whose address is defined 305 by the vPIMrfc822mailbox attribute. 307 3.6 Maximum Message Size 309 Many email systems enforce size limitations on messages 310 that can be received. vPIMMaxMessageSize can be used 311 to record the maximum integer number of bytes that can 312 be received in a message, including the header, sent to 313 the address specified in vMrfc822Mailbox. This 314 attribute would be useful in other applications but has 315 not been defined elsewhere. This attribute is only to 316 be used until a more appropriate attribute is defined 317 elsewhere. 319 The ASN.1 definition for X.500 implementations is: 321 vPIMMaxMessageSize ATTRIBUTE ::= { 322 WITH SYNTAX NumericString 323 EQUALITY MATCHING RULE numericStringMatch 324 ID id-vpim-at-vPIMMaxMessageSize} 326 The BNF definition for use with LDAP is: 328 (2.16.840.1.113694.1.2.1.1.5 NAME 'vPIMMaxMessageSize' 329 EQUALITY 2.5.13.8 330 SYNTAX '1.3.6.1.4.1.1466.115.121.1.36') 332 3.7 Additional Multimedia Attributes 334 Types for other required multimedia attributes are for 335 further study. 337 4. Object Classes 339 4.1 e164Node Structural Object Class 341 Structural object classes are used in defining the 342 hierarchical structure of the directory tree. e164Node 343 is the structural object class that will be used in 344 defining the structure of VPIM directory tree. All 345 entries of this type must contain the e164Digit 346 attribute which is used to name entries in the VPIM 347 directory tree. 349 The ASN.1 definition for X.500 implementations is: 351 e164Node OBJECT-CLASS ::= { 352 SUBCLASS OF top 353 MUST CONTAIN { e164Digit } 354 ID { id-vpim-oc-e164node} } 356 The BNF definition for use with LDAP is: 358 (2.16.840.1.113694.1.2.1.2.1 NAME 'e164Node' 359 SUP top 360 STRUCTURAL 361 MUST e164Digit) 363 4.2 vPIMUser Auxiliary Object Class 365 An auxiliary object class is used to group related 366 attributes which can be applied to several types of 367 entries. The vPIMUser attribute type defines 368 attributes that may be useful in providing a VPIM 369 directory service. All entries having an object class 370 of vPIMUser may contain any of the attributes 371 vPIMrfc822Mailbox, commonName, vPIMSpokenName, 372 vPIMSpokenName1, vPIMSpokenName2, vPIMSpokenName3, 373 vPIMSpokenName4, vPIMSupportedEncodingTypes, and 374 vPIMMaxMessageSize. 376 This definition will be expanded in the future to other 377 multimedia attributes. If subtyping were used, 378 rfc822Mailbox would also be specified as an optional 379 attribute. 381 The ASN.1 definition for X.500 implementations is: 383 vPIMUser OBJECT-CLASS ::= { 384 KIND auxiliary 385 SUBCLASS OF top 386 MAY CONTAIN { vPIMrfc822Mailbox, 387 commonName, vPIMSpokenName, 388 vPIMSpokenName1, vPIMSpokenName2, 389 vPIMSpokenName3, vPIMSpokenName4, 390 vPIMSupportedEncodingTypes, 391 vPIMMaxMessageSize } 392 ID { id-vpim-oc-vPIMUser } } 394 The BNF definition for use with LDAP is: 396 (2.16.840.1.113694.1.2.1.2.2 NAME 'vPIMUser' 397 SUP top 398 AUXILIARY 399 MAY ( vPIMrfc822Mailbox $ 400 cn $ 401 vPIMSpokenName $ 402 vPIMSpokenName1 $ 403 vPIMSpokenName2 $ 404 vPIMSpokenName3 $ 405 vPIMSpokenName4 $ 406 vPIMSupportedEncodingTypes $ 407 vPIMMaxMessageSize )) 409 5. DIT Content Rules 411 Directory Information Tree (DIT) Content rules over- 412 ride all other rules for specifying which attributes 413 may appear in an entry. The e164NodeRule DIT content 414 rule specifies that the e164Node structural object 415 class and the vPIMUser auxiliary object class are to be 416 used to define entries to which this content rule 417 applies. 419 The ASN.1 definition for X.500 implementations is: 421 e164NodeRule CONTENT-RULE ::= { 422 STRUCTURAL OBJECT-CLASS e164Node 423 AUXILIARY OBJECT-CLASSES vPIMUser } 425 6. Name Forms 427 Name forms control how entries are named in the 428 directory tree. They are referenced in the DIT 429 structure rules which are used to define which classes 430 of object may be subordinate to other classes of object 431 in the directory. Object classes of the 432 e164DigitNameForm name form are named using the 433 e164Digit attribute type. 435 e164DigitNameForm NAME-FORM ::= { 436 NAMES e164Node 437 WITH ATTRIBUTES { e164Digit } 438 ID id-vpim-nf-e164Digitnameform } 440 7. DIT Structure Rules 442 The VPIM directory is structured according to Figure 1. 444 Structure rule 1 defines entries, that are named 445 according to countryNameForm (i.e., named with 446 attribute countryName), to be immediately subordinate 447 to the root of the DIT. Similarly, structure rule 2 448 defines organizations as also under root. 450 sr1 STRUCTURE-RULE ::= { 451 NAME FORM countryNameForm, - - X.521 452 ID 1 } 454 sr2 STRUCTURE-RULE ::= { 455 NAME FORM orgNameForm, - - X.521 456 ID 2 } 458 Structure rule 3 specifies that organization entries can be 459 located under country entries. 461 sr3 STRUCTURE-RULE ::= { 462 NAME FORM orgNameForm, 463 SUPERIOR RULES { sr1 }, 464 ID 3 } 465 root 466 /\ 467 2/ \1 468 / \ 469 / countryName 470 / / 471 / /3 472 / / 473 organziationName 474 \ 475 \4 476 \ 477 e164Digit 478 / | 479 5\ / 480 -- 482 Figure 1: DIT Structure Rules 484 Structure rule 4 specifies e164Digit entries placed 485 under organizational entries. 487 sr4 STRUCTURE-RULE ::= { 488 NAME FORM e164DigitNameform, 489 SUPERIOR RULES { sr2 | sr3 }, 490 ID 4 } 492 Structure rule 5 defines e164Digit entries subordinate 493 to e164Digit entries. 495 sr5 STRUCTURE-RULE ::= { 496 NAME FORM e164DigitNameform, 497 SUPERIOR RULES { sr4 }, 498 ID 5 } 500 8. Summary of ASN.1 and BNF Definitions 502 8.1 ASN.1 Definitions 504 -- attributes 506 e164Digit ATTRIBUTE ::= { 507 WITH SYNTAX NumericString (SIZE(ub-vpim-at-e164Digit)) 508 EQUALITY MATCHING RULE numericStringMatch 509 ID id-vpim-at-e164Digit} 511 vPIMrfc822Mailbox ATTRIBUTE ::= { 512 WITH SYNTAX caseIgnoreIA5StringSyntax 513 (SIZE (1 .. ub-rfc822-mailbox)) -- from RFC 1274 514 ID id-vpim-at-vPIMrfc822Mailbox } 516 vPIMSpokenName ATTRIBUTE ::= { 517 WITH SYNTAX OCTET STRING 518 (SIZE (1..ub-vpim-at-vPIMSpokenName) 519 EQUALITY MATCHING RULE octetStringMatch 520 ID id-vpim-at-vPIMSpokenName } 522 vPIMSpokenName1 ATTRIBUTE ::= { 523 WITH SYNTAX OCTET STRING 524 (SIZE (1..ub-vpim-at-vPIMSpokenName) 525 EQUALITY MATCHING RULE octetStringMatch 526 ID id-vpim-at-vPIMSpokenName1 } 528 vPIMSpokenName2 ATTRIBUTE ::= { 529 WITH SYNTAX OCTET STRING 530 (SIZE (1..ub-vpim-at-vPIMSpokenName) 531 EQUALITY MATCHING RULE octetStringMatch 532 ID id-vpim-at-vPIMSpokenName2 } 534 vPIMSpokenName3 ATTRIBUTE ::= { 535 WITH SYNTAX OCTET STRING 536 (SIZE (1..ub-vpim-at-vPIMSpokenName) 537 EQUALITY MATCHING RULE octetStringMatch 538 ID id-vpim-at-vPIMSpokenName3 } 540 vPIMSpokenName4 ATTRIBUTE ::= { 541 WITH SYNTAX OCTET STRING 542 (SIZE (1..ub-vpim-at-vPIMSpokenName) 543 EQUALITY MATCHING RULE octetStringMatch 544 ID id-vpim-at-vPIMSpokenName4 } 546 vPIMSupportedEncodingTypes ATTRIBUTE ::= { 547 WITH SYNTAX DirectoryString 548 EQUALITY MATCHING RULE caseIgnoreMatch 549 ID id-vpim-at-vPIMSupportedEncodingTypes } 551 vPIMMaxMessageSize ATTRIBUTE ::= { 552 WITH SYNTAX NumericString 553 EQUALITY MATCHING RULE numericStringMatch 554 ID id-vpim-at-vPIMMaxMessageSize } 556 -- object classes 558 e164Node OBJECT-CLASS ::= { 559 SUBCLASS OF top 560 MUST CONTAIN { e164Digit } 561 ID { id-vpim-oc-e164node} } 563 vPIMUser OBJECT-CLASS ::= { 564 KIND auxiliary 565 SUBCLASS OF top 566 MAY CONTAIN { vPIMrfc822Mailbox, 567 commonName, vPIMSpokenName, 568 vPIMSpokenName1, vPIMSpokenName2, 569 vPIMSpokenName3, vPIMSpokenName4, 570 vPIMSupportedEncodingTypes, 571 vPIMMaxMessageSize } 572 ID { id-vpim-oc-vPIMUser } } 574 -- DIT content rules 576 e164NodeRule CONTENT-RULE ::= { 577 STRUCTURAL OBJECT-CLASS e164Node 578 AUXILIARY OBJECT-CLASSES vPIMUser } 580 -- Name Forms 582 e164DigitNameForm NAME-FORM ::= { 583 NAMES e164Node 584 WITH ATTRIBUTES { e164Digit } 585 ID id-vpim-nf-e164Digitnameform } 587 -- structure rules 589 sr1 STRUCTURE-RULE ::= { 590 NAME FORM countryNameForm, - - X.521 591 ID 1 } 593 sr2 STRUCTURE-RULE ::= { 594 NAME FORM orgNameForm, - - X.521 595 ID 2 } 597 sr3 STRUCTURE-RULE ::= { 598 NAME FORM orgNameForm, 599 SUPERIOR RULES { sr1 }, 600 ID 3 } 602 sr4 STRUCTURE-RULE ::= { 603 NAME FORM e164DigitNameform, 604 SUPERIOR RULES { sr2 | sr3 }, 605 ID 4 } 607 sr5 STRUCTURE-RULE ::= { 608 NAME FORM e164DigitNameform, 609 SUPERIOR RULES { sr4 }, 610 ID 5 } 612 -- upper bounds 614 ub-vpim-at-e164Digit INTEGER ::= 1 615 ub-vpim-at-vPIMSpokenName INTEGER ::= 4,000 617 -- object identifiers 619 id-vpim OBJECT IDENTIFIER ::= {2.16.840.1.113694.1.2.1} 621 id-vpim-at OBJECT IDENTIFIER ::= {id-vpim 1} 622 id-vpim-at-e164Digit OBJECT IDENTIFIER ::= {id-vpim-at 1} 623 id-vpim-at-vPIMrfc822Mailbox OBJECT IDENTIFIER ::= {id-vpim-at 2} 624 id-vpim-at-vPIMSpokenName OBJECT IDENTIFIER ::= {id-vpim-at 3} 625 id-vpim-at-vPIMSpokenName1 OBJECT IDENTIFIER ::= {id-vpim-at 3.1} 626 id-vpim-at-vPIMSpokenName2 OBJECT IDENTIFIER ::= {id-vpim-at 3.2} 627 id-vpim-at-vPIMSpokenName3 OBJECT IDENTIFIER ::= {id-vpim-at 3.3} 628 id-vpim-at-vPIMSpokenName4 OBJECT IDENTIFIER ::= {id-vpim-at 3.4} 629 id-vpim-at-vPIMSupportedEncodingTypes 630 OBJECT IDENTIFIER ::= {id-vpim-at 4} 631 id-vpim-at-vPIMMaxMessageSize OBJECT IDENTIFIER ::= {id-vpim-at 5} 633 id-vpim-oc OBJECT IDENTIFIER ::= {id-vpim 2} 634 id-vpim-oc-vMNode OBJECT IDENTIFIER ::= {id-vpim-oc 1} 635 id-vpim-oc-vMUser OBJECT IDENTIFIER ::= {id-vpim-oc 2} 637 id-vpim-nf OBJECT IDENTIFIER ::= {id-vpim 3} 638 id-vpim-nf-e164Digitnameform OBJECT IDENTIFIER ::= { id-vpim-nf 1} 640 8.2 BNF Definitions 642 8.2.1.1.1.1.1.1.11 Attributes 644 (2.16.840.1.113694.1.2.1.1.1 NAME 'e164Digit' 645 EQUALITY 2.5.13.8 646 SYNTAX '1.3.6.1.4.1.1466.115.121.1.36 {1}') 648 (2.16.840.1.113694.1.2.1.1.2 NAME 'vPIMrfc822Mailbox' 649 EQUALITY 1.3.6.1.4.1.1466.109.114.2 650 SYNTAX '1.3.6.1.4.1.1466.115.121.1.26 {256}') 652 (2.16.840.1.113694.1.2.1.1.3 NAME 'vPIMSpokenName' 653 EQUAILTY 2.5.13.17 654 SYNTAX '1.3.6.1.4.1.1466.115.121.1.40 {4000}') 655 (2.16.840.1.113694.1.2.1.1.3.1 NAME 'vPIMSpokenName1' 656 EQUAILTY 2.5.13.17 657 SYNTAX '1.3.6.1.4.1.1466.115.121.1.40 {4000}') 659 (2.16.840.1.113694.1.2.1.1.3.2 NAME 'vPIMSpokenName2' 660 EQUAILTY 2.5.13.17 661 SYNTAX '1.3.6.1.4.1.1466.115.121.1.40 {4000}') 663 (2.16.840.1.113694.1.2.1.1.3.3 NAME 'vPIMSpokenName3' 664 EQUAILTY 2.5.13.17 665 SYNTAX '1.3.6.1.4.1.1466.115.121.1.40 {4000}') 667 (2.16.840.1.113694.1.2.1.1.3.4 NAME 'vPIMSpokenName4' 668 EQUAILTY 2.5.13.17 669 SYNTAX '1.3.6.1.4.1.1466.115.121.1.40 {4000}') 671 (2.16.840.1.113694.1.2.1.1.4 NAME 672 'vPIMSupportedEncodingTypes' 673 EQUALITY 2.5.13.2 674 SYNTAX '1.3.6.1.4.1.1466.115.121.1.15') 676 (2.16.840.1.113694.1.2.1.1.5 NAME 'vPIMMaxMessageSize' 677 EQUALITY 2.5.13.8 678 SYNTAX '1.3.6.1.4.1.1466.115.121.1.36') 680 8.2.1 Object Classes 682 (2.16.840.1.113694.1.2.1.2.1 NAME 'e164Node' 683 SUP top 684 STRUCTURAL 685 MUST e164Digit) 687 (2.16.840.1.113694.1.2.1.2.2 NAME 'vPIMUser' 688 SUP top 689 AUXILIARY 690 MAY ( vPIMrfc822Mailbox $ 691 cn $ 692 vPIMSpokenName $ 693 vPIMSpokenName1 $ 694 vPIMSpokenName2 $ 695 vPIMSpokenName3 $ 696 vPIMSpokenName4 $ 697 vPIMSupportedEncodingTypes $ 698 vPIMMaxMessageSize )) 700 8.3 Tabular Summary of Schema Elements 702 Attribute OID Abbrev Length 703 -------- --- ------ ------ 704 e164Digit id-vpim-at 1 1 705 vPIMrfc822Mailbox id-vpim-at 2 256 706 commonName (X.520) 5.4.3 cn 64 707 vPIMSpokenName id-vpim-at 3 4,000 708 vPIMSpokenName1 id-vpim-at 3.1 4,000 709 vPIMSpokenName2 id-vpim-at 3.2 4,000 710 vPIMSpokenName3 id-vpim-at 3.3 4,000 711 vPIMSpokenName4 id-vpim-at 3.4 4,000 712 vPIMSupportedEncodingTypes id-vpim-at 4 713 vPIMMaxMessageSize id-vpim-at 5 715 Object OID Kind Attributes 716 Class 717 ------ --- ---- ---------- 718 e164Node id-vpim-oc 1 structural Mandatory: 719 e164Digit 720 vPIMUser id-vpim-oc 2 auxiliary Optional: 721 vPIMrfc822Mailbox 722 commonName 723 vPIMSpokenName 724 vPIMSpokenName1 725 vPIMSpokenName2 726 vPIMSpokenName3 727 vPIMSpokenName4 728 vPIMSupported 729 EncodingTypes 730 vPIMMaxMessageSize 732 DIT Content Rule Contains Object Classes 733 ---------------- ------------------------ 734 Structural Mandatory 735 ---------- --------- 736 e164Node e164NOde vPIMUser 738 Name Form OID Applies to Named 739 Object Class by 740 --------- --- ------------ ------ 741 e164DigitNameForm id-vpim-nf 1 e164Node e164Digit 743 DIT 744 Structure 745 Rule Naming Attrib Superior rules Superior Attribs 746 --------- ---------------- -------------- ---------------- 747 sr1 countryName 748 sr2 organizationName 749 sr3 organizationName sr1 countryName 750 sr4 e164Digit sr2, sr3 organizationName 751 sr5 e164Digit sr4 e164Digit 753 9. Security considerations: 755 For the VPIM pilot directory service, access control 756 should be such that anonymous reads are allowed for all 757 VPIM attributes. 759 The VPIM directory was designed for single X.500 read 760 operations (base object searches in LDAP). Multiple 761 mulilevel searches may degrade performance and should 762 be discouraged. To prohibit access to entries without 763 explicitly providing the name of an entry, denyBrowse 764 should enforced for anonymous users. 766 10. Acknowledgements 768 Thanks to Mark Wahl for his valuable comments. 770 11. Additional information: 772 Person & email address to contact for further 773 information: 774 Anne R. Brown 775 arbrown@nortel.ca 776 Intended usage: COMMON 777 Author/Change controller: Anne R. Brown 779 11.1 Author's Address 781 Anne R. Brown 782 Nortel Technology 783 P.O. Box 3511, Station C 784 Ottawa, ON K1Y 4H7 785 Canada 786 Phone: +1-613-765-5274 787 Fax: +1-613-763-2697 788 arbrown@nortel.ca 790 6. References 792 [ATTRIBS04] M. Wahl, A. Coulbeck, T. Howes, S. Kille, W. Yeong, C. 793 Robbins, "Lightweight X.500 Directory Access 794 Protocol Attribute Syntax Definitions", INTERNET- 795 DRAFT , 796 March 1997. 798 [VPIM2] Greg Vaudreuil and Glenn Parsons, "Voice Profile for 799 Internet Mail - version 2", Work in Progress, May 800 1997. 802 Expires: May 24, 1997