idnits 2.17.1 draft-ietf-roamops-ldap-phonebook-01.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 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. ** 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 25 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 26 pages -- Found 26 instances of the string 'FORMFEED[Page...' -- is this a case of missing nroff postprocessing? 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 132 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? == There are 2 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 11 has weird spacing: '...This document...' == Line 12 has weird spacing: '...as, and its...' == Line 17 has weird spacing: '...and may be ...' == Line 18 has weird spacing: '...ference mater...' == Line 21 has weird spacing: '...To learn the...' == (127 more instances...) == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- 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 1998) is 9539 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) ** Obsolete normative reference: RFC 1700 (ref. '2') (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 1274 (ref. '3') (Obsoleted by RFC 4524) -- Possible downref: Non-RFC (?) normative reference: ref. '4' Summary: 13 errors (**), 0 flaws (~~), 10 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Zorn 3 Internet-Draft Microsoft Corporation 4 Category: Standards Track March 1998 5 7 An LDAP Schema for Phone Books 9 1. Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working docu- 12 ments of the Internet Engineering Task Force (IETF), its areas, and its 13 working groups. Note that other groups may also distribute working doc- 14 uments 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 material 19 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 ds.internic.net (US East Coast), nic.nordu.net (Europe), 24 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 26 The distribution of this memo is unlimited. It is filed as , and expires September 15, 1998. Please 28 send comments to the Roaming Operations Working Group mailing list 29 (roamops@tdmx.rutgers.edu) or to the author (glennz@microsoft.com). 31 2. Abstract 33 This document describes an LDAP schema for the attributes to be included 34 in the standard phone book. Goals of this document include: 36 - Creating a flexible, extensible and robust framework 37 upon which to build a standard phone book 38 - Promoting a standard phone book format, to enhance 39 interoperability between ISPs and roaming consortia 41 Non-goals of this document include: 43 - Attempting to create a ''Swiss army knife'', with phone 44 book attributes to please everyone on Earth 45 - Definition of either server-server or client-server 46 phone book update or transfer protocols 48 3. Rationale for LDAP Usage 50 The attributes are defined in terms that are directly usable by the 51 Lightweight Directory Access Protocol (LDAP) for several reasons: 53 - Extensibility 54 - Flexibility 55 - Integration with LDAP-based Directory 57 Extensibility is important because phone books are living documents; as 58 such, it is unlikely that all the semantic requirements of arbitrary 59 Internet service providers (ISPs) would be met by a fixed scheme, no 60 matter how well thought out. Phone book designers must be free to cre- 61 ate new attributes in an well-understood fashion to meet changing busi- 62 ness needs. 64 Flexibility is required of the attribute definition syntax for many of 65 the same reasons that semantic extensibility is necessary. If we assume 66 that phone book designers may need to define attributes of arbitrary 67 type, the syntax chosen must be able to represent these objects cleanly. 68 The meta-language used to describe LDAP attributes fits this bill 69 nicely, since it can be used to unambiguously describe virtually any 70 data type. 72 Integration with LDAP-based directories: although it is unlikely that 73 phone books will be stored in the directory due to performance consider- 74 ations, the creation of an LDAP schema describing phone book attributes 75 leaves that option open, with relatively little incremental effort 76 required to implement it. 78 4. Specification of Requirements 80 In this document, the key words "MAY", "MUST, "MUST NOT", "optional", 81 "recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as 82 described in [1]. 84 5. Object definitions 86 This document includes definitions of the following objects: 88 - Phone Book class 89 - Provider class 90 - POP class 91 - Support class 92 - Setup class 94 5.1. Phone Book Class 96 5.1.1. Description 97 The Phone Book class is the basic container for phone book entries. 98 It always contains a phone book version number (applying to the phone 99 book as a whole), a phone book name and one or more pointers (in the 100 form of Distinguished Names) to POP objects. A Phone Book object may 101 also contain multiple pointers to Provider and Setup objects 102 (described below). These pointers also take the form of Distin- 103 guished Names. 105 5.1.2. Syntax 106 ( phoneBookClass 1 107 NAME 'phoneBookClass' 108 SUP top 109 STRUCTURAL 110 MUST ( 111 phoneBookVersion $ phoneBookName $ popPointer 112 ) 113 MAY ( 114 setupPointer $ providerPointer $ supportPointer 115 ) 116 ) 118 5.2. Provider Class 120 5.2.1. Description 121 The Provider class contains attributes pertaining to the general 122 business operations of a given network service provider. The 123 attributes include such things as telephone number, mailing address, 124 etc., as well as URLs for e-mail and a World Wide Web site. A 125 Provider object may also contain a pointer (in the form of a Distin- 126 guished Name) to support information. 128 5.2.2. Syntax 129 ( providerClass 1 130 NAME 'providerClass' 131 SUP top 132 STRUCTURAL 133 MAY ( 134 providerName $ providerIcon $ wwwURL 135 $ generalMailtoURL $ billingMailtoURL 136 $ businessCategory $ x121Address $ registeredAddress 137 $ destinationIndicator $ preferredDeliveryMethod 138 $ telexNumber $ teletexTerminalIdentifier 139 $ telephoneNumber $ internationalISDNNumber 140 $ facsimileTelephoneNumber $ street $ postOfficeBox 141 $ postalCode $ postalAddress $ physicalDeliveryOfficeName 142 $ description $ supportPointer 143 ) 144 ) 146 5.3. POP Class 148 5.3.1. Description 149 The POP class contains attributes relevant to individual network 150 points of presence (POPs). The required attributes are addrFamily, 151 address, media and entryVersion. The media attribute represents the 152 media types supported by the POP, while the entryVersion attribute is 153 a monotonically-increasing integer which should be incremented when- 154 ever the object is modified. 156 5.3.2. Syntax 157 ( popClass 1 158 NAME 'popClass' 159 SUP top 160 PARENT ( 161 country $ organization $ organizationalunit 162 $ locality $ container 163 ) 164 STRUCTURAL 165 MUST ( 166 addrFamily $ address $ media $ entryVersion 167 ) 168 MAY ( 169 encodingType $ modemProtocols 170 $ isdnProtocols $ city $ region $ country 171 $countryCode $ minBitsPerSecond 172 $ maxBitsPerSecond $ areaCode 173 $ unicastRoutingProtocols 174 $ multicastRoutingProtocols $ dialScriptType 175 $ dialScript $ pricing $ vpnProtocols $ popProperties 176 $ popSetupPointer $ popSupportPointer $ popProviderPointer 177 ) 178 ) 180 5.4. Support Class 182 5.4.1. Description 183 The Support class includes those attributes that are pertinent to the 184 provision of customer support for a POP or provider. 186 5.4.2. Syntax 187 ( supportClass 1 188 NAME 'supportClass' 189 SUP top 190 PARENT ( 191 country $ organization $ organizationalunit 192 $ locality $ container 193 ) 194 STRUCTURAL 195 MAY ( 196 supportTelephoneNumber $ supportLanguages 197 $ supportMailtoURL 198 ) 199 ) 201 5.5. Setup Class 203 5.5.1. Description 204 The Setup class includes attributes which describe services which may 205 change from provider to provider or even from POP to POP. Many of 206 the values contained in these attributes may be available by other 207 means (e.g., DHCP), but others may not. 209 5.5.2. Syntax 210 ( setupClass 1 211 NAME 'setupClass' 212 SUP top 213 PARENT ( 214 country $ organization $ organizationalunit 215 $ locality $ container 216 ) 217 STRUCTURAL 218 MAY ( 219 dnsServerAddress $ nntpServerName $ smtpServerName 220 $ popServerName $ imapServerName $ wwwProxyServerName 221 $ ftpProxyServerName $ winsockProxyServerName 222 $ defaultGatewayAddress $ userNamePrefix $ userNameSuffix 223 ) 224 ) 226 6. Attribute Definitions 228 6.1. New attributes defined for the Phone Book Class 230 6.1.1. Phone Book Version 232 6.1.1.1. Description 233 The phoneBookVersion attribute is an integer representing the version 234 of the phone book; it is a monotonically increasing counter which 235 should be incremented each time the phone book is modified. This 236 attribute can be used by a server to help decide what (if any) 237 actions are required to bring a client's phone book up to date. For 238 example, the client can, at connect time, send an update request to 239 the server including in the request the version number of its current 240 phone book. If the client's phone book version is not the same as 241 the server's current phone book version, the server can easily take 242 appropriate action, e.g., reply with a URL pointing to a file con- 243 taining the differences between the client and server phone books. 245 6.1.1.2. Syntax 246 ( phoneBook phoneBookClass 1 247 NAME 'phoneBookVersion' 248 DESC 'Version number of the phone book' 249 EQUALITY IntegerMatch 250 SYNTAX 'INTEGER' 251 SINGLE-VALUE 252 ) 254 6.1.2. Phone Book Name 256 6.1.2.1. Description 257 The phoneBookName attribute is an arbitrary string assigned as an 258 identifier for a phone book. 260 6.1.2.2. Syntax 261 ( phoneBook phoneBookClass 2 262 NAME 'phoneBookName' 263 DESC 'The name of the phone book' 264 EQUALITY caseIgnoreIA5Match 265 SYNTAX PrintableString 266 SINGLE-VALUE 267 ) 269 6.1.3. POP Pointer 271 6.1.3.1. Description 272 The popPointer attribute is a Distinguished Name which points to a 273 POP object for this phone book. 275 6.1.3.2. Syntax 276 ( phoneBook phoneBookClass 3 277 NAME 'popPointer' 278 DESC 'A pointer to one or more POP objects' 279 EQUALITY distinguishedNameMatch 280 SYNTAX 'DN' 281 ) 283 6.1.4. Setup Pointer 285 6.1.4.1. Description 286 The setupPointer attribute is a Distinguished Name which points to a 287 Setup object for this phone book. 289 6.1.4.2. Syntax 290 ( phoneBook phoneBookClass 4 291 NAME 'setupPointer' 292 DESC 'A pointer to a Setup object for this phone book' 293 EQUALITY distinguishedNameMatch 294 SYNTAX 'DN' 295 SINGLE-VALUE 296 ) 298 6.1.5. Provider Pointer 300 6.1.5.1. Description 301 The providerPointer attribute is a Distinguished Name which points to 302 a Provider object for this phone book. 304 6.1.5.2. Syntax 305 ( phoneBook phoneBookClass 5 306 NAME 'providerPointer' 307 DESC 'A pointer to a Provider object for this phonebook' 308 EQUALITY distinguishedNameMatch 309 SYNTAX 'DN' 310 SINGLE-VALUE 311 ) 313 6.1.6. Support Pointer 315 6.1.6.1. Description 316 The supportPointer attribute is a Distinguished Name which points to 317 a Support object for this phone book. 319 6.1.6.2. Syntax 320 ( phoneBook phoneBookClass 6 321 NAME 'supportPointer' 322 DESC 'A pointer to a Support object for this phone book' 323 EQUALITY distinguishedNameMatch 324 SYNTAX 'DN' 325 SINGLE-VALUE 326 ) 328 6.2. New attributes defined for the Provider Class [3] 330 6.2.1. Provider Name 332 6.2.1.1. Description 333 The providerName attribute is a string containing the name of the 334 provider (e.g., "BIGNET Corporation"). 336 6.2.1.2. Syntax 337 ( phoneBook providerClass 1 338 NAME 'providerName' 339 DESC 'The name of the provider' 340 EQUALITY caseIgnoreIA5Match 341 SYNTAX 'PrintableString' 342 SINGLE-VALUE 343 ) 345 6.2.2. Provider Icon 347 6.2.2.1. Description 348 The providerIcon attribute contains a JPEG graphic which may be used 349 for 'branding' phone book entries or displayed when dialing. 351 6.2.2.2. Syntax 352 ( phoneBook providerClass 2 353 NAME 'providerIcon' 354 DESC 'An icon in JPEG format' 355 EQUALITY octetStringMatch 356 SYNTAX 'JPEG' 357 SINGLE-VALUE 358 ) 360 6.2.3. Provider's World Wide Web URL 362 6.2.3.1. Description 363 The wwwURL attribute contains a Uniform Resource Locator (URL) for 364 the provider's Web site, for example, http://www.uu.net. 366 6.2.3.2. Syntax 367 ( phoneBook providerClass 3 368 NAME 'wwwURL' 369 DESC 'A Uniform Resource Locator for the provider's home page' 370 EQUALITY caseExactIA5Match 371 SYNTAX 'IA5String' 372 SINGLE-VALUE 373 ) 375 6.2.4. Provider's Main Email Address 377 6.2.4.1. Description 378 The generalMailtoURL attribute contains a URL for the provider's main 379 email address, for example, mailto://contact@uu.net. This URL could 380 be used for general correspondence, complaints, etc. 382 6.2.4.2. Syntax 383 ( phoneBook providerClass 4 384 NAME 'generalMailtoURL' 385 DESC 'A Uniform Resource Locator for the provider's 386 email address' 387 EQUALITY caseExactIA5Match 388 SYNTAX 'IA5String' 389 SINGLE-VALUE 390 ) 392 6.2.5. Billing Inquiry Email Address 394 6.2.5.1. Description 395 The billingMailtoURL attribute contains a URL for the provider's 396 billing support email address, for example, mailto://billing@uu.net. 397 This URL could be used to for correspondence regarding billing and 398 payment issues. 400 6.2.5.2. Syntax 401 ( phoneBook providerClass 6 402 NAME 'billingMailtoURL' 403 DESC 'A Uniform Resource Locator for the email 404 address to be used for billing inquiries' 405 EQUALITY caseExactIA5Match 406 SYNTAX 'IA5String' 407 SINGLE-VALUE 408 ) 410 6.3. New attributes defined for the POP Class 412 6.3.1. Address Family 414 6.3.1.1. Description 415 The addrFamily attribute is an integer which represents the address 416 family to which the value in the address attribute (below) belongs. 417 For POPs offering dial-up network access, the addrFamily attribute 418 will generally contain a value for a telephone network based address 419 family. The current list of IANA-assigned address family numbers is 420 reproduced below for convenience; for an up-to-date list, see [2]. 422 Number Description 423 ------ -------------------------------------- 424 0 Reserved 425 1 IP (IP version 4) 426 2 IP6 (IP version 6) 427 3 NSAP 428 4 HDLC (8-bit multidrop) 429 5 BBN 1822 430 6 802 (includes all 802 media 431 plus Ethernet "canonical format") 432 7 E.163 433 8 E.164 (SMDS, Frame Relay, ATM) 434 9 F.69 (Telex) 435 10 X.121 (X.25, Frame Relay) 436 11 IPX 437 12 Appletalk 438 13 Decnet IV 439 14 Banyan Vines 440 65535 Reserved 442 6.3.1.2. Syntax 443 ( phoneBook popClass 1 444 NAME 'addrFamily' 445 SUP top 446 DESC 'The address family to which the address attribute 447 below belongs' 448 EQUALITY integerMatch 449 SYNTAX INTEGER 450 SINGLE-VALUE 451 ) 453 6.3.2. Address 455 6.3.2.1. Description 456 The address attribute in a binary quantity representing the address 457 of the POP. For POPs offering dial-up network access, the address 458 attribute will generally contain an IA5 string representing a tele- 459 phone number, formatted in standard fashion [4] (e.g. "+ 1 234 460 5678"). 462 6.3.2.2. Syntax 463 ( phoneBook popClass 2 464 NAME 'address' 465 SUP top 466 DESC 'A network address for this POP' 467 EQUALITY bitStringMatch 468 SYNTAX 'BitString' 469 SINGLE-VALUE 470 ) 472 6.3.3. Media 474 6.3.3.1. Description 475 The media attribute describes the types of media supported by this 476 POP. The following values are defined: 478 Type Value 479 ----------- ----- 480 Modem 1 481 ISDN 2 482 ATM 3 483 Frame Relay 4 484 X.25 5 485 SMDS 6 487 6.3.3.2. Syntax 488 ( phoneBook popClass 3 489 NAME 'media' 490 SUP top 491 DESC 'The types of media supported by this POP' 492 EQUALITY integerMatch 493 SYNTAX INTEGER 494 ) 496 6.3.4. Entry Version 498 6.3.4.1. Description 499 The entryVersion attribute is an integer representing the version of 500 the POP object; it is a monotonically increasing counter which should 501 be incremented each time the object is modified. This attribute may 502 be useful in merging and updating phone books. 504 6.3.4.2. Syntax 505 ( phoneBook popClass 4 506 NAME 'entryVersion' 507 DESC 'version number of POP object' 508 EQUALITY IntegerMatch 509 SYNTAX 'INTEGER' 510 SINGLE-VALUE 511 ) 513 6.3.5. Encoding Type 515 6.3.5.1. Description 516 The encodingType attribute is an integer representing the type of 517 encoding used within a specific address family The value '0' is 518 reserved and represents the native encoding. 520 6.3.5.2. Syntax 521 ( phoneBook popClass 5 522 NAME 'entryVersion' 523 DESC 'the type of encoding used within this address family' 524 EQUALITY IntegerMatch 525 SYNTAX 'INTEGER' 526 SINGLE-VALUE 527 ) 529 6.3.6. Modem Protocols 531 6.3.6.1. Description 532 The modemProtocols attribute is a bit string representing the modem 533 protocols supported by the access devices that can be reached at 534 address. The initially defined modem protocol flags are listed in 535 the table below. All 'Position' values are in hexadecimal, all 536 'Speed' values are in bits per second. If the bit in 'Position' is 537 1, 'Protocol' is supported; otherwise, 'Protocol' is unsupported. 538 For example, the string 00110001 (0x31) means that V.21, V.32bis and 539 V.34 are supported while V.22, V.29 and V.32 are not. 541 Name Position Duplex Speed Protocol 542 ---- -------- ------ ----- ------------- 543 V21 0x0001 Full 300 ITU-T V.21 544 V22 0x0002 Full 1200 ITU-T V.22 545 V29 0x0004 Half 9600 ITU-T V.29 546 V32 0x0008 Full 9600 ITU-T V.32 547 V32b 0x0010 Full 14.4k ITU-T V.32bis 548 V34 0x0020 Full 28.8k ITU-T V.34 549 VF 0x0040 Full V.FAST 551 Question: Are these flags useful? If so, are there more that need to 552 be added? 554 6.3.6.2. Syntax 555 ( phoneBook popClass 6 556 NAME 'modemProtocols' 557 DESC 'A bit string representing the modem 558 protocols supported by the access devices at 559 this POP' 560 EQUALITY bitStringMatch 561 SYNTAX 'BitString' 562 SINGLE-VALUE 563 ) 565 6.3.7. ISDN Protocols 567 6.3.7.1. Description 568 The isdnProtocols attribute is a bit string representing the ISDN 569 protocols supported by the access devices that can be reached at 570 address. The initially defined ISDN protocols are listed in the 571 table below. All 'Value. values are in hexadecimal, all 'Speed' val- 572 ues are in bits per second. If the bit in 'Position' is 1, 'Proto- 573 col' is supported; otherwise, 'Protocol' is unsupported. For exam- 574 ple, the string 00001101 (0x0d) means that V.120 is supported at both 575 56K and 64K bps while V.110 is supported only at 19.2K bps. 577 Name Value Speed Meaning 578 ----- ------ ----- ----------- 579 V110L 0x0001 19.2k ITU-T V.110 580 V110H 0x0002 38.4k ITU-T V.110 581 V120L 0x0004 56k ITU-T V.120 582 V120H 0x0008 64k ITU-T V.120 584 Question: Are the ISDN flags useful? If so, should there be more? 586 6.3.7.2. Syntax 587 ( phoneBook popClass 7 588 NAME 'isdnProtocols' 589 DESC 'A bit string representing the ISDN flavors 590 supported by the access devices at this POP' 591 EQUALITY bitStringMatch 592 SYNTAX 'BitString' 593 SINGLE-VALUE 594 ) 596 6.3.8. City 598 6.3.8.1. Description 599 The city attribute contains the name of the city in which the POP is 600 located (not the city(s) from which it is accessible by a local 601 call). 603 6.3.8.2. Syntax 604 ( phoneBook popClass 8 605 NAME 'city' 606 DESC 'The name of the city in which this POP is located' 607 EQUALITY caseExactIA5Match 608 SYNTAX 'IA5String {64}' 609 SINGLE-VALUE 610 ) 612 6.3.9. Region 614 6.3.9.1. Description 615 The region attribute contains the name of the region in which the POP 616 is located. In the United States, this would be the name of a state 617 or (for Washington, D.C.) administrative district. In other coun- 618 tries, it might be the name of a province, parish or county. 620 6.3.9.2. Syntax 621 ( phoneBook popClass 9 622 NAME 'region' 623 DESC 'The name of the region in which this POP is located' 624 EQUALITY caseExactIA5Match 625 SYNTAX 'IA5String {64}' 626 SINGLE-VALUE 627 ) 629 6.3.10. Country 631 6.3.10.1. Description 632 The country attribute contains the name of the country in which the 633 POP is located. The country name may be abbreviated (e.g., "USA" for 634 the United States of America or "UK" for the United Kingdom) but if 635 abbreviations are used the usage must be consistent within a given 636 phone book. 638 6.3.10.2. Syntax 639 ( phoneBook popClass 10 640 NAME 'country' 641 DESC 'The name of the country in which this POP is located' 642 EQUALITY caseExactIA5Match 643 SYNTAX 'IA5String {64}' 644 SINGLE-VALUE 645 ) 647 6.3.11. Country Code 649 6.3.11.1. Description 650 The countryCode attribute indicates the international dialing prefix 651 for the country in which the POP is located. 653 6.3.11.2. Syntax 654 ( phoneBook popClass 11 655 NAME 'countryCode' 656 DESC 'ITU dialing code for the country in which 657 this POP is located' 658 EQUALITY integerMatch 659 SYNTAX 'INTEGER' 660 SINGLE-VALUE 661 ) 663 6.3.12. Minimum Data Rate 665 6.3.12.1. Description 666 The minBitsPerSecond attribute indicates the minimum data rate (in 667 bits/second) supported by the access devices at the POP. 669 6.3.12.2. Syntax 670 ( phoneBook popClass 12 671 NAME 'minBitsPerSecond' 672 DESC 'Minimum data rate supported by this POP' 673 in bits/second' 674 EQUALITY integerMatch 675 SYNTAX 'INTEGER' 676 SINGLE-VALUE 677 ) 679 6.3.13. Maximum Data Rate 681 6.3.13.1. Description 682 The maxBitsPerSecond attribute indicates the maximum data rate (in 683 bits/second) supported by the access devices at the POP. 685 6.3.13.2. Syntax 686 ( phoneBook popClass 13 687 NAME 'maxBitsPerSecond' 688 DESC 'Maximum data rate supported by this POP, 689 in bits/second' 690 EQUALITY integerMatch 691 SYNTAX 'INTEGER' 692 SINGLE-VALUE 693 ) 695 6.3.14. Area Code 697 6.3.14.1. Description 698 The areaCode attribute contains the area or city code component of 699 the telephone number in the 'address' attribute (if any) associated 700 with this POP. 702 6.3.14.2. Syntax 703 ( phoneBook popClass 14 704 NAME 'areaCode' 705 DESC 'Area or city code component of the telephone 706 number in the accessTelephoneNumber attribute 707 associated with this POP' 709 EQUALITY integerMatch 710 SYNTAX INTEGER 711 SINGLE-VALUE 712 ) 714 6.3.15. Unicast Routing Protocols 716 6.3.15.1. Description 717 The unicastRoutingProtocols attribute is a bitstring representing the 718 unicast routing protocols supported by this POP. The initially 719 defined values are listed in the table below. If the bit in 'Posi- 720 tion' is 1, 'Protocol' is supported; otherwise, 'Protocol' is unsup- 721 ported. 723 Position Protocol 724 -------- -------- 725 0x0001 Static 726 0x0002 RIP v1 727 0x0004 RIP v2 728 0x0008 OSPF 729 0x0010 IS-IS 730 0x0020 IGRP 731 0x0040 EIGRP 732 0x0080 BGP 734 6.3.15.2. Syntax 735 ( phoneBook popClass 15 736 NAME 'unicastRoutingProtocols' 737 DESC 'A bit string representing the unicast routing 738 protocols supported by the access devices at this POP' 739 EQUALITY bitStringMatch 740 SYNTAX 'BitString' 741 SINGLE-VALUE 742 ) 744 6.3.16. Multicast Routing Protocols 746 6.3.16.1. Description 747 The multicastRoutingProtocols attribute is a bitstring representing 748 the multicast routing protocols supported by this POP. The initially 749 defined values are listed in the table below. If the bit in 'Posi- 750 tion' is 1, 'Protocol' is supported; otherwise, 'Protocol' is unsup- 751 ported. 753 Position Protocol 754 -------- ---------- 755 0x0001 Static 756 0x0002 DVMRP 757 0x0004 SM-PIM 758 0x0008 DM-PIM 759 0x0010 CBT v1 760 0x0020 CBT v2 761 0x0040 BGMP 762 0x0080 Proxy IGMP 764 6.3.16.2. Syntax 765 ( phoneBook popClass 15 766 NAME 'multicastRoutingProtocols' 767 DESC 'A bit string representing the multicast routing 768 protocols supported by the access devices at this POP' 769 EQUALITY bitStringMatch 770 SYNTAX 'BitString' 771 SINGLE-VALUE 772 ) 774 6.3.17. Dial Script Type 776 6.3.17.1. Description 777 The dialScript attribute indicates the type of dialing script that 778 should be used when connecting to this POP. 780 Question: What kinds of scripts are there? 782 6.3.17.2. Syntax 783 ( phoneBook popClass 16 784 NAME 'dialScriptType' 785 DESC 'Type of the dial script to be used' 786 EQUALITY caseExactIA5Match 787 SYNTAX 'IA5String {64}' 788 SINGLE-VALUE 789 ) 791 6.3.18. Dialing Script 793 6.3.18.1. Description 794 The dialScript attribute contains the dialing script to be used when 795 connecting to this POP. 797 6.3.18.2. Syntax 798 ( phoneBook popClass 17 799 NAME 'dialScript' 800 DESC 'The dial script to be used' 801 EQUALITY caseIgnoreIA5Match 802 SYNTAX 'IA5String' 803 SINGLE-VALUE 804 ) 806 6.3.19. Pricing Information 808 6.3.19.1. Description 809 The pricing attribute is a free-form string representing pricing 810 information for this POP. It may be anything from a simple string 811 indicating relative expense (e.g., "$$$$" for a very expensive POP) 812 to a paragraph describing time-of-day and other differential pricing 813 variables. 815 6.3.19.2. Syntax 816 ( phoneBook popClass 18 817 NAME 'pricing' 818 DESC 'Pricing information for this POP' 819 EQUALITY caseIgnoreIA5Match 820 SYNTAX 'IA5String' 821 ) 823 6.3.20. Tunneling Protocols 825 6.3.20.1. Description 826 The tunnelingProtocols attribute is a bitstring representing the tun- 827 neling protocols supported by this POP. The initially defined values 828 are listed in the table below. If the bit in 'Position' is 1, 'Pro- 829 tocol' is supported; otherwise, 'Protocol' is unsupported. 831 Position Protocol 832 -------- ------------------ 833 0x0001 PPTP 834 0x0002 L2F 835 0x0004 L2TP 836 0x0008 ATMP 837 0x0010 VTP 838 0x0020 IP AH Tunnel Mode 839 0x0040 IP-IP 840 0x0080 Minimal IP-IP 841 0x0100 IP ESP Tunnel Mode 842 0x0200 GRE 843 0x0400 Bay DVS 845 6.3.20.2. Syntax 846 ( phoneBook popClass 21 847 NAME 'tunnelingProtocols' 848 DESC 'A bit string representing the tunneling protocols 849 supported by the access devices at this POP' 850 EQUALITY bitStringMatch 851 SYNTAX 'BitString' 852 SINGLE-VALUE 853 ) 855 6.3.21. POP Properties 857 6.3.21.1. Description 858 The popProperties attribute is a bitstring representing a variety of 859 Boolean properties characterizing this POP. The initially defined 860 properties are listed in the table below. If the bit in 'Position' 861 is 1, 'Property' is supported; otherwise, 'Property' is unsupported. 863 Position Property 864 -------- ---------------------- 865 0x0001 Multilink 866 0x0002 Mobile IP 867 0x0004 Multicast Reception 868 0x0008 Multicast Transmission 870 6.3.21.2. Syntax 871 ( phoneBook popClass 22 872 NAME 'popProperties' 873 DESC 'A bit string representing a variety of Boolean 874 properties characterizing this POP' 875 EQUALITY bitStringMatch 876 SYNTAX 'BitString' 877 SINGLE-VALUE 878 ) 880 6.3.22. POP Setup Pointer 882 6.3.22.1. Description 883 The popSetupPointer attribute is a Distinguished Name which points to 884 a Setup object for this POP. 886 6.3.22.2. Syntax 887 ( phoneBook popClass 23 888 NAME 'popSetupPointer' 889 DESC 'A pointer to a Setup object for this POP' 890 EQUALITY distinguishedNameMatch 891 SYNTAX 'DN' 892 SINGLE-VALUE 893 ) 895 6.3.23. POP Support Pointer 897 6.3.23.1. Description 898 The popSupportPointer attribute is a Distinguished Name which points 899 to a Support object for this POP. 901 6.3.23.2. Syntax 902 ( phoneBook popClass 25 903 NAME 'popSupportPointer' 904 DESC 'A pointer to a Support object for this POP' 905 EQUALITY distinguishedNameMatch 906 SYNTAX 'DN' 907 SINGLE-VALUE 908 ) 910 6.3.24. POP Provider Pointer 912 6.3.24.1. Description 913 The popProviderPointer attribute is a Distinguished Name which points 914 to a Provider object for this POP. 916 6.3.24.2. Syntax 917 ( phoneBook popClass 24 918 NAME 'popProviderPointer' 919 DESC 'A pointer to a Provider object for this POP' 920 EQUALITY distinguishedNameMatch 921 SYNTAX 'DN' 922 SINGLE-VALUE 923 ) 925 6.4. New attributes defined for the Support Class 927 6.4.1. Support Telephone Number 929 6.4.1.1. Description 930 The supportTelephoneNumber attribute contains a number that may be 931 called to reach the support center for a particular provider or POP. 932 This attribute is basically a string and should contain the entire 933 telephone number in international form, e.g., "+1 425 838 8080". 935 6.4.1.2. Syntax 936 ( phoneBook supportClass 1 937 NAME 'supportTelephoneNumber' 938 SUP TelephoneNumber 939 DESC 'The number to be dialed to contact customer 940 support for this POP or provider' 941 SINGLE-VALUE 942 ) 944 6.4.2. Support Languages 945 6.4.2.1. Description 946 The supportLanguages attribute contains a comma-separated list of 947 languages spoken by the staff at the support center at supportTele- 948 phoneNumber. 950 Question: Is there a standard way to represent languages (like coun- 951 try codes for phone numbers)? 953 6.4.2.2. Syntax 954 ( phoneBook supportClass 2 955 NAME 'supportLanguages' 956 DESC 'A comma-separated list of languages spoken by 957 support personnel for this POP or provider' 958 EQUALITY caseExactIA5Match 959 SYNTAX 'IA5String' 960 ) 962 6.4.3. Support Email Address 964 6.4.3.1. Description 965 The supportMailtoURL attribute contains a URL for the provider's cus- 966 tomer support email address, for example, mailto://support@uu.net. 967 This URL could be used to contact customer support personnel regard- 968 ing non-urgent issues. 970 6.4.3.2. Syntax 971 ( phoneBook supportClass 3 972 NAME 'supportMailtoURL' 973 DESC 'A Uniform Resource Locator for the 974 provider's customer support email address' 975 EQUALITY caseExactIA5Match 976 SYNTAX 'IA5String' 977 SINGLE-VALUE 978 ) 980 6.5. New attributes defined for the Setup class 982 6.5.1. DNS Server Address 984 6.5.1.1. Description 985 The dnsServerAddress attribute represents the IP address of the 986 Domain Name Service (DNS) server which should be used when connected 987 to this POP. The address is represented in the form of a string in 988 dotted-decimal notation (e.g., 192.168.101.1). 990 6.5.1.2. Syntax 991 ( phoneBook setupClass 1 992 NAME 'dnsServerAddress' 993 DESC 'Domain Name Server IP address (in dotted decimal 994 notation)' 995 EQUALITY caseIgnoreIA5Match 996 SYNTAX 'IA5String {128}' 997 SINGLE-VALUE 998 ) 1000 6.5.2. NNTP Server Name 1002 6.5.2.1. Description 1003 The nntpServerName attribute contains the fully qualified domain name 1004 (FQDN) of the Network News Transfer Protocol (NNTP) server which 1005 should be used when connected to this POP. 1007 6.5.2.2. Syntax 1008 ( phoneBook setupClass 2 1009 NAME 'nntpServerName' 1010 DESC 'Name of an NNTP server' 1011 EQUALITY caseIgnoreIA5Match 1012 SUBSTRINGS caseIgnoreIA5SubstringsMatch 1013 SYNTAX 'IA5String' 1014 SINGLE-VALUE 1015 ) 1017 6.5.3. SMTP Server Name 1019 6.5.3.1. Description 1020 The smtpServerName attribute contains the FQDN of the Simple Mail 1021 Transfer Protocol (SMTP) server which should be used when connected 1022 to this POP. 1024 6.5.3.2. Syntax 1025 ( phoneBook setupClass 3 1026 NAME 'smtpServerName' 1027 DESC 'Name of an SMTP mail server' 1028 EQUALITY caseIgnoreIA5Match 1029 SUBSTRINGS caseIgnoreIA5SubstringsMatch 1030 SYNTAX 'IA5String' 1031 SINGLE-VALUE 1032 ) 1034 6.5.4. POP3 Server Name 1035 6.5.4.1. Description 1036 The popServerName attribute contains the FQDN of the Post Office Pro- 1037 tocol (POP) server which should be used when connected to this POP. 1039 6.5.4.2. Syntax 1040 ( phoneBook setupClass 4 1041 NAME 'popServerName' 1042 DESC 'Name of an POP3 mail server' 1043 EQUALITY caseIgnoreIA5Match 1044 SUBSTRINGS caseIgnoreIA5SubstringsMatch 1045 SYNTAX 'IA5String' 1046 SINGLE-VALUE 1047 ) 1049 6.5.5. IMAP Server Name 1051 6.5.5.1. Description 1052 The imapServerName attribute contains the FQDN of the Internet Mail 1053 Access Protocol (IMAP) server which should be used when connected to 1054 this POP. 1056 6.5.5.2. Syntax 1057 ( phoneBook setupClass 5 1058 NAME 'imapServerName' 1059 DESC 'Name of an IMAP4 server' 1060 EQUALITY caseIgnoreIA5Match 1061 SUBSTRINGS caseIgnoreIA5SubstringsMatch 1062 SYNTAX 'IA5String' 1063 SINGLE-VALUE 1064 ) 1066 6.5.6. WWW Proxy 1068 6.5.6.1. Description 1069 The wwwProxyServerName attribute contains the FQDN of the World Wide 1070 Web (WWW) proxy server which should be used when connected to this 1071 POP. 1073 6.5.6.2. Syntax 1074 ( phoneBook setupClass 6 1075 NAME 'wwwProxyServerName' 1076 DESC 'Name of an WWW Proxy' 1077 EQUALITY caseIgnoreIA5Match 1078 SUBSTRINGS caseIgnoreIA5SubstringsMatch 1079 SYNTAX 'IA5String' 1080 SINGLE-VALUE 1081 ) 1083 6.5.7. FTP Proxy 1085 6.5.7.1. Description 1086 The ftpProxyServerName attribute contains the FQDN of the File Trans- 1087 fer Protocol (FTP) proxy server which should be used when connected 1088 to this POP. 1090 6.5.7.2. Syntax 1091 ( phoneBook setupClass 7 1092 NAME 'ftpProxyServerName' 1093 DESC 'Name of an FTP Proxy' 1094 EQUALITY caseIgnoreIA5Match 1095 SUBSTRINGS caseIgnoreIA5SubstringsMatch 1096 SYNTAX 'IA5String' 1097 SINGLE-VALUE 1098 ) 1100 6.5.8. Winsock Proxy 1102 6.5.8.1. Description 1103 ThewinsockProxyServerName attribute contains the FQDN of the Windows 1104 Socket (Winsock) proxy server which should be used when connected to 1105 this POP. 1107 6.5.8.2. Syntax 1108 ( phoneBook setupClass 8 1109 NAME 'winsockProxyServerName' 1110 DESC 'Name of an Winsock Proxy' 1111 EQUALITY caseIgnoreIA5Match 1112 SUBSTRINGS caseIgnoreIA5SubstringsMatch 1113 SYNTAX 'IA5String' 1114 SINGLE-VALUE 1115 ) 1117 6.5.9. Default Gateway Address 1119 6.5.9.1. Description 1120 The defaulttGatewayAddress attribute represents the address of the 1121 default gateway which should be used when connected to this POP. The 1122 address is represented in the form of a string in dotted-decimal 1123 notation (e.g., 192.168.101.1). 1125 6.5.9.2. Syntax 1126 ( phoneBook setupClass 8 1127 NAME 'defaultGatewayAddress' 1128 DESC 'Default Gateway IP address (in dotted decimal notation)' 1129 EQUALITY caseIgnoreIA5Match 1130 SYNTAX 'IA5String {128}' 1131 SINGLE-VALUE 1132 ) 1134 6.5.10. User Name Suffix 1136 6.5.10.1. Description 1137 The userNameSuffix attribute represents a string which should be con- 1138 catenated to the base username. For example, if the base username is 1139 "userA" and the value of this attribute is "@bigco.com", the result- 1140 ing augmented username would be "userA@bigco.com". An intelligent 1141 dialer may concatenate the string automatically. Note that both the 1142 userNameSuffix and the userNamePrefix (below) may be applied to the 1143 same base username. 1145 6.5.10.2. Syntax 1146 ( phoneBook setupClass 9 1147 NAME 'userNameSuffix' 1148 DESC 'User Name suffix' 1149 EQUALITY caseIgnoreIA5Match 1150 SYNTAX 'IA5String {128}' 1151 SINGLE-VALUE 1152 ) 1154 6.5.11. User Name Prefix 1156 6.5.11.1. Description 1157 The userNamePrefix attribute represents a string to which the base 1158 username should be concatenated. For example, if the base username 1159 is "userB" and the value of this attribute is "BIGCO/" the resulting 1160 augmented username would be "BIGCO/userB". An intelligent dialer may 1161 perform the concatenation automatically. Note that both the user- 1162 NameSuffix (above) and the userNamePrefix may be applied to the same 1163 base username. 1165 6.5.11.2. Syntax 1166 ( phoneBook setupClass 10 1167 NAME 'userNamePrefix' 1168 DESC 'User Name prefix' 1169 EQUALITY caseIgnoreIA5Match 1170 SYNTAX 'IA5String {128}' 1171 SINGLE-VALUE 1172 ) 1174 7. Security Considerations 1176 None (submissions welcome). 1178 8. References 1180 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 1181 Levels", BCP 14, RFC 2119, March 1997 1183 [2] Reynolds, J. and Postel, J., "ASSIGNED NUMBERS", STD 2, RFC 1700, 1184 October 1994 1186 [3] The rest of the attributes in this class are described in RFC 1274 1188 [4] ITU Rec. E.123, "Notation for national and international telephone 1189 numbers", 1988 1191 9. Acknowledgements 1193 Thanks to Bernard Aboba (aboba@internaut.com), Jay Farhat 1194 (jfarhat@ipass.com), Butch Anton (butch@ipass.com), Quentin Miller 1195 (quentinm@microsoft.com), and Ken Crocker (kcrocker@microsoft.com) for 1196 salient input and review. 1198 10. Author's Address 1200 Questions about this memo can be directed to: 1202 Glen Zorn 1203 Microsoft Corporation 1204 One Microsoft Way 1205 Redmond, Washington 98052 1207 Phone: +1 425 703 1559 1208 E-Mail: glennz@microsoft.com 1210 11. Expiration Date 1212 This memo is filed as draft-ietf-roamops-ldap-phonebook-01.txt and 1213 expires on September 15, 1998.