idnits 2.17.1 draft-miller-dhcp-ldap-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-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 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. == There are 231 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 12 longer pages, the longest (page 2) being 62 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. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** 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 135: '... MUST (cn...' RFC 2119 keyword, line 137: '... MAY (DNIPSubnetAttr $ DNIPDNSServer...' RFC 2119 keyword, line 258: '... MUST (cn $ DNIPSubnetAddress $ DNIP...' RFC 2119 keyword, line 260: '... MAY ( DNIPLeaseTime $ DNIPConfigOpt...' RFC 2119 keyword, line 366: '... MUST (cn $ DNIPStartAddressNumber $...' (7 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 20 has weird spacing: '...soleted by ot...' -- 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 (June 1, 1998) is 9461 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'DNSSCHEMA' -- Duplicate reference: RFC2131, mentioned in 'RFC2132', was also mentioned in 'RFC2131'. ** Obsolete normative reference: RFC 2252 (Obsoleted by RFC 4510, RFC 4512, RFC 4517, RFC 4523) Summary: 12 errors (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT T. Miller 2 Informational Draft A.Patel 3 Expires 1 December 1998 P. Rao 4 Novell, Inc. 5 June 1, 1998 7 Lightweight Directory Access Protocol (v3): 8 Schema for Dynamic Host Configuration Protocol (DHCP) 9 11 Status of this Memo 13 This document is an Internet-Draft. Internet-Drafts are 14 working documents of the Internet Engineering Task Force 15 (IETF), its areas, and its working groups. Note that other 16 groups may also distribute working documents as Internet- 17 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six 20 months and may be updated, replaced, or obsoleted by other 21 documents at any time. It is inappropriate to use Internet- 22 Drafts as reference material or to cite them other than as 23 "work in progress". 25 To view the entire list of current Internet-Drafts, please check 26 the "1id-abstracts.txt" listing contained in the Internet-Drafts 27 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 28 (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au 29 (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu 30 (US West Coast). 32 This distribution of this memo is unlimited. It is filed as 33 , and expires on 34 December 1, 1998. 36 Abstract 38 This document defines a schema for Dynamic Host Configuration 39 Protocol (DHCP). This schema makes it possible to integrate 40 DHCP servers with an LDAP-based directory service, allowing an 41 organization to maintain a single store of IP addresses and 42 other configuration data provided to clients using the DHCP 43 protocol. Integration of DHCP into LDAP directories is 44 desirable since it reduces administrative overhead and 45 eliminates the need to maintain multiple server centric 46 configuration databases. 48 It is anticipated that this schema will be useful for 49 providing a standardized format for the representation of 50 attributes needed by DHCP implementations within LDAP-based 51 directory services. 53 1. Introduction 55 DHCP [RFC2131] is a protocol which allows IP addresses to be 56 assigned to devices from a server, usually at boot time. 57 DHCP servers typically allow an administrator to assign an 58 address to a device dynamically from a pool of addresses or, 59 if necessary, a specific address can be assigned to a device 60 based upon an identifier such as a MAC address. 62 In addition to assigning IP addresses to clients, DHCP can be 63 used to provide other configuration information to devices, 64 such as the IP address of DNS servers, the address of a 65 default router, and many other configuration parameters. 66 [RFC2132], [RFC2241], and [RFC2242] describe DHCP options and 67 vendor extensions that represent this configuration 68 information. 70 Organizations need to manage addresses and device 71 configuration for widely dispersed (often, global) networks. 72 While many DHCP servers may be needed within an organization�s 73 network, it is highly desirable to be able to manage addresses 74 and configuration from a single point. Integrating DHCP into 75 an LDAP directory allows for a single point of administration 76 for a distributed set of DHCP servers. 78 In order to support DHCP, new object classes are defined for 79 Locator, Subnet, Subnet Address Range, IP Address, Subnet 80 Pool, and DHCP Server. These object classes are described in 81 the next section, �Object Descriptions� with the detailed 82 class attribute definitions following each description. 83 [RFC2252] describes the syntaxes used in these definitions. 85 2. DHCP Object Descriptions 87 OIDs have been assigned for these schema extensions (as well 88 as DNS extensions described in [DNSSCHEMA]) as follows: 90 joint-iso-ccitt(2).country(16).us(840) 91 .organization(1).novell(113719).applications(1).DNIP(25) 92 .DNIPAttributeType(4) 94 joint-iso-ccitt(2).country(16).us(840) 95 .organization(1).novell(113719).applications(1).DNIP(25) 96 .DNIPAttributeSyntax(5) 98 joint-iso-ccitt(2).country(16).us(840) 99 .organization(1).novell(113719).applications(1).DNIP(25) 100 .DNIPObjectClass(6) 101 2.1 DNS/DHCP Locator 103 The DNS/DHCP Locator object is an object used to store global 104 information relevant for both DNS and DHCP. [DNSSCHEMA] 105 describes a LDAP schema for DNS. These two services interact 106 in some cases, such as for Dynamic DNS updates. Also, the 107 administration of the two services is often linked. 109 The Locator object has two purposes. First, it contains DNs 110 (Distinguished Names) of other objects of interest for DNS and 111 DHCP. For DHCP these include subnets, subnet pools, and DHCP 112 servers. By having DNs of all these objects, an application 113 such as a GUI, is able to present a list of all these objects 114 without needing to search the entire tree for the objects. 115 Instead, the application just needs to find the locator, and 116 then read the DNs of the other objects. This can offer a 117 significant performance advantage. 119 The second DHCP usage of the locator object is to store 120 configuration information that is to apply to the entire tree. 121 This global configuration, such as DHCP option values, is to 122 apply to the entire tree unless it is overridden at a lower 123 level of the tree. In the case of DHCP options, the global 124 values in the locator object could be overridden at the Subnet 125 object or IP address object levels. 127 Object Class Definition: 129 (2.16.840.1.113719.1.25.6.1.1 130 NAME �DNS/DHCP Locator� 131 SUP top 132 PARENT (country $ organization $ organizationalUnit $ 133 locality) 134 STRUCTURAL 135 MUST (cn 136 ) 137 MAY (DNIPSubnetAttr $ DNIPDNSServers $ DNIPDHCPServers $ 138 DNIPDNSZones $ DNIPSubnetPoolList $ DNIPConfigOptions $ 139 DNIPCfgPreferences $ DNIPExcludedMac $ DNIPGroupReference 140 ) 141 ) 143 Attribute Definitions: 145 (2.16.840.1.113719.1.25.4.1.1 146 NAME �DNIPSubnetAttr� 147 DESC(�The distinguished names of Subnets. 148 �) 149 SYNTAX �DN� 150 MULTI-VALUED 151 ) 153 (2.16.840.1.113719.1.25.4.1.2 154 NAME �DNIPDNSServers� 155 DESC(�The distinguished names of DNS servers. 156 �) 157 SYNTAX �DN� 158 MULTI-VALUED 159 ) 161 (2.16.840.1.113719.1.25.4.1.3 162 NAME �DNIPDHCPServers� 163 DESC(�The distinguished names of DHCP servers. 164 �) 165 SYNTAX �DN� 166 MULTI-VALUED 167 ) 169 (2.16.840.1.113719.1.25.4.1.4 170 NAME �DNIPDNSZones� 171 DESC(�The distinguished names of DNS Zones. 172 �) 173 SYNTAX �DN� 174 MULTI-VALUED 175 ) 177 (2.16.840.1.113719.1.25.4.1.5 178 NAME �DNIPSubnetPoolList� 179 DESC(�The distinguished names of Subnet Pools. 180 �) 181 SYNTAX �DN� 182 MULTI-VALUED 183 ) 185 (2.16.840.1.113719.1.25.4.1.6 186 NAME �DNIPConfigOptions� 187 DESC(�DHCP options are included in this string. The 188 first four octets are reserved. The rest of the string 189 contains encoded DHCP options. 190 �) 191 SYNTAX �OCTETSTRING� 192 SINGLE-VALUE 193 ) 195 (2.16.840.1.113719.1.25.4.1.8 196 NAME �DNIPCfgPReferences� 197 DESC(�Configuration preferences for the administrative 198 utility. 199 �) 200 SYNTAX �OCTETSTRING� 201 MULTI-VALUED 202 ) 204 (2.16.840.1.113719.1.25.4.1.9 205 NAME �DNIPExcludedMac� 206 DESC(�A list of MAC addresses which the administrator 207 wishes to exclude from receiving addresses by DHCP. Each 208 address is described as in [RFC2131] with the first octet as 209 hlen, second octet a htype, and the remaining octets are the 210 actual hardware address. A wildcard format is also supported. 211 If the length is greater than 17 octets this indicates a 212 wildcard. A wildcard MAC address has an �*� to indicate the 213 portion of the address that is a wildcard. For example, 214 �00:02:*� would indicate that all addresses starting with 215 00:02 should be excluded. 216 �) 217 SYNTAX �OCTETSTRING� 218 MULTI-VALUED 219 ) 221 (2.16.840.1.113719.1.25.4.1.11 222 NAME �DNIPGroupReference� 223 DESC(�The distinguished name of the group object through 224 which servers gain their rights to the tree. 225 �) 226 SYNTAX �DN� 227 SINGLE-VALUED 228 ) 230 2.2 Subnet 232 The Subnet object represents an IP subnet. As would be 233 expected, it has an address and mask to define the subnet. 234 The Subnet object is designed to be placed in the part of the 235 tree representing the location it is serving; it is contained 236 by an O, OU, C, or L(Organization, Organizational Unit, 237 Locality, or Country). 239 The Subnet object also has attributes for configuration that 240 apply to the entire Subnet. For example, there is an 241 attribute to specify the lease time for addresses assigned 242 dynamically from the Subnet. A very important attribute in 243 the Subnet is DHCPConfigOptions. These are the values that 244 are to be passed to the client when it requests DHCP options. 245 DHCP options that are not specified at the Subnet level can be 246 inherited from the DNS/DHCP Locator object. This allows an 247 administrator to configure options for an entire enterprise 248 once, and then specify exceptions at the Subnet level. 250 Object Class Definition: 252 (2.16.840.1.113719.1.25.6.1.2 253 NAME �DHCP Subnet� 254 SUP top 255 PARENT (country $ organization $ organizationalUnit $ 256 locality) 257 STRUCTURAL 258 MUST (cn $ DNIPSubnetAddress $ DNIPSubnetMask 259 ) 260 MAY ( DNIPLeaseTime $ DNIPConfigOptions $ 261 DNIPZoneReference $ DNIPDomainName $ 262 DNIPBootParameter $ DNIPSubnetPoolReference $ 263 DNIPSubnetType $ DNIPComment 264 ) 265 ) 267 Attribute Definitions: 269 (2.16.840.1.113719.1.25.4.1.32 270 NAME �DNIPSubnetAddress� 271 DESC(�The starting address of a subnet which, along with 272 the subnet�s mask, defines the subnet�) 273 SYNTAX �INTEGER� 274 SINGLE-VALUE 275 ) 277 (2.16.840.1.113719.1.25.4.1.33 278 NAME �DNIPSubnetMask� 279 DESC(�The mask for the subnet which, along with the 280 subnet address, defines the subnet�) 281 SYNTAX �INTEGER� 282 SINGLE-VALUE 283 ) 285 (2.16.840.1.113719.1.25.4.1.6 286 NAME �DNIPConfigOptions� 287 DESC(�DHCP Options are included in this string. The 288 first four octets are reserved. The rest of the string 289 contains encoded DHCP options�) 290 SYNTAX �OCTETSTRING� 291 SINGLE-VALUE 292 ) 294 (2.16.840.1.113719.1.25.4.1.34 295 NAME �DNIPZoneReference� 296 DESC(�A Distinguished Name of a zone that should be 297 updated when Dynamic DNS (DDNS) updates are made�) 298 SYNTAX �DN� 299 SINGLE-VALUE 300 ) 302 (2.16.840.1.113719.1.25.4.1.36 303 NAME �DNIPDomainName� 304 DESC(�The domain name that should be provided to the DHCP 305 client.�) 306 SYNTAX �IA5STRING� 307 SINGLE-VALUE 308 ) 310 (2.16.840.1.113719.1.25.4.1.7 311 NAME �DNIPBOOTParameter� 312 DESC(�This parameter contains the siaddr, sname, and file 313 parameters of a DHCP message as described in [RFC2131]. The 314 maximum length of the parameter is 198 octets. The syntax is 315 a 4 octet siaddr in network order, a null terminated sname 316 character string, followed by another null terminated file 317 character sting.�) 318 SYNTAX �OCTET_STRING� 319 SINGLE-VALUE 320 ) 322 (2.16.840.1.113719.1.25.4.1.35 323 NAME �DNIPSubnetPoolReference� 324 DESC(�This Distinguished Name identifies the subnet pool 325 by name that the Subnet is a part of.�) 326 SYNTAX �DN� 327 SINGLE-VALUE 328 ) 330 (2.16.840.1.113719.1.25.4.1.31 331 NAME �DNIPSubnetType� 332 DESC(�This identifies the type of subnet. The defined 333 values are 1 = Subnet for LAN clients. 2 = Subnet for Remote 334 Access Clients.�) 335 SYNTAX �INTEGER� 336 SINGLE-VALUE 337 ) 339 (2.16.840.1.113719.1.25.4.1.79 340 NAME �DNIPComment� 341 DESC(�This is for the administrator to provide a comment 342 about the object.�) 343 SYNTAX �IA5STRING� 344 SINGLE-VALUE 345 ) 347 2.3 Subnet Address Range 349 The Subnet Address Range object identifies a range of 350 addresses within a Subnet. It is a leaf object that is 351 contained under the Subnet. The Subnet Address Range has 352 a type attribute to identify it as one of several type of 353 ranges available for dynamic address assignment (types 354 are available to support both Dynamic DHCP and Dynamic 355 BOOTP, as well as automatic host name generation) or as a 356 set of addresses that an administrator wishes to exclude 357 from address assignment. 359 Class Definition: 361 (2.16.840.1.113719.1.25.6.1.5 362 NAME �DHCP Subnet Address Range� 363 SUP top 364 PARENT (Subnet) 365 STRUCTURAL 366 MUST (cn $ DNIPStartAddressNumber $ DNIPEndAddressNumber 367 ) 368 MAY ( DNIPDHCPServerReference $ DNIPDNSUpdateOption $ 369 DNIPRangeType $ DNIPAutoHostNameStart $ DNIPComment 370 ) 371 ) 373 Attribute Definitions: 375 (2.16.840.1.113719.1.25.4.1.38 376 NAME �DNIPStartAddressNumber� 377 DESC(�This is the starting address in an IP Address 378 Range.�) 379 SYNTAX �INTEGER� 380 SINGLE-VALUE 381 ) 383 (2.16.840.1.113719.1.25.4.1.39 384 NAME �DNIPEndAddressNumber� 385 DESC(�This is the ending address in an IP Address 386 Range.�) 387 SYNTAX �INTEGER� 388 SINGLE-VALUE 389 ) 391 (2.16.840.1.113719.1.25.4.1.12 392 NAME �DNIPServerReference� 393 DESC(�This is the DN of the server object representing 394 the server that has been assigned the Subnet Address Range.�) 395 SYNTAX �INTEGER� 396 SINGLE-VALUE 397 ) 399 (2.16.840.1.113719.1.25.4.1.40 400 NAME �DNIPDNSUpdateOption� 401 DESC(�Specifies whether DNS should be updated as 402 addresses are assigned: 403 1 = Don�t Update 404 2 = Always Update 405 �) 406 SYNTAX �INTEGER� 407 SINGLE-VALUE 408 ) 410 (2.16.840.1.113719.1.25.4.1.41 411 NAME �DNIPRangeType� 412 DESC(�The type of Subnet Address Range 413 1 = Dynamic BOOTP 414 2 = Dynamic DHCP 415 3 = Dynamic BOOTP and DHCP 416 4 = Remote Access 417 5 = Dynamic DHCP with Automatic Name Generation 418 255 = Exclusion 419 �) 420 SYNTAX �INTEGER� 421 SINGLE-VALUE 422 ) 424 (2.16.840.1.113719.1.25.4.1.37 425 NAME �DNIPAutoHostNameStart� 426 DESC(�This string is used to automatically generate host 427 names. It is used when the DNIPRangeType attribute is set to 428 5 for Dynamic DHCP with Automatic Name Generation. The use of 429 this attribute implies the use of the DNIPDomainName attribute 430 in the corresponding subnet object.�) 431 SYNTAX �IA5STRING� 432 SINGLE-VALUE 433 ) 435 (2.16.840.1.113719.1.25.4.1.79 436 NAME �DNIPComment� 437 DESC(�This is for the administrator to provide a comment 438 about the object.�) 439 SYNTAX �IA5STRING� 440 SINGLE-VALUE 441 ) 443 2.4 IP Address 445 The IP Address object represents a single IP address. It is a 446 leaf object that is contained under a subnet. The IP Address 447 object is created by an administrator when a specific address 448 needs to be assigned to a device. The IP Address object has 449 as attributes a MAC address and Client ID. When a request is 450 received from a client for an address the MAC address or 451 Client ID is compared to these attributes to determine what 452 address to provide the client. 454 The IP Address object has attributes similar to the Subnet 455 object, that apply to the specific address instead of the 456 entire subnet. One part of this are DHCP options. When a 457 client requests DHCP options they first come from the IP 458 address object if an individual option is specified. For 459 those options that aren�t specified at the IP address object 460 level, the DHCP server will first check the Subnet object and 461 then the DNS/DHCP locator object. 463 In addition to being created by administrators, IP Address 464 objects can be created by a DHCP server to represent IP 465 address assignments in the directory. The IP Address object 466 has attributes to identify when the lease will expire and when 467 it was last renewed. 469 The IP Address object has a type attribute to indicate whether 470 it was created to represent a static address assignment or 471 created to represent a dynamic address assignment. This 472 attribute can also indicate that the IP Address object 473 represents an address that is currently not assigned. This 474 allows a DHCP server to mark an attribute, rather than delete 475 an object, when an address lease expires. 477 Object Class Definition: 479 (2.16.840.1.113719.1.25.6.1.6 480 NAME �DHCP IP Address Configuration� 481 SUP top 482 PARENT (Subnet) 483 STRUCTURAL 484 MUST (cn $ DNIPAddressNumber $ DNIPAssignmentType 485 ) 486 MAY ( DNIPLeaseTime $ DNIPConfigOptions $ DNIPHostName $ 487 DNIPLastUsed $ DNIPLeaseExpiration $ DNIPObjectReference 488 $ DNIPMACAddress $ DNIPClientIdentifier $ 489 DNIPBootParameters $ DNIPFQDomainName $DNIPComment 490 ) 491 ) 493 Attribute Definitions: 495 (2.16.840.1.113719.1.25.4.1.44 496 NAME �DNIPAddressNumber� 497 DESC(�An IP Address 498 �) 499 SYNTAX �INTEGER� 500 SINGLE-VALUE 501 ) 503 (2.16.840.1.113719.1.25.4.1.42 504 NAME �DNIPAssignmentType� 505 DESC(�Indicates what this address represents 506 1 = BOOTP Assignment 507 2 = Dynamic DHCP Assignment 508 4 = IPCP (Remote Access) Assignment 509 8 = Manual Address Assignment 510 16 = MAC address exclusion 511 32 = Unauthorized IP Address Usage 512 64 = Dynamic DHCP Assignment with Host Name 513 Generation 514 128 = IP Address Exclusion 515 �) 516 SYNTAX �INTEGER� 517 SINGLE-VALUE 518 ) 520 (2.16.840.1.113719.1.25.4.1.19 521 NAME �DNIPLeaseTime� 522 DESC(�The configured time for the address lease, in 523 seconds. �1 implies a permanent lease. 524 �) 525 SYNTAX �INTEGER� 526 SINGLE-VALUE 527 ) 529 (2.16.840.1.113719.1.25.4.1.6 530 NAME �DNIPConfigOptions� 531 DESC(�DHCP Options are included in this string. The 532 first four octets are reserved. The rest of the string 533 contains encoded DHCP options�) 534 SYNTAX �OCTETSTRING� 535 SINGLE-VALUE 536 ) 538 (2.16.840.1.113719.1.25.4.1.47 539 NAME �DNIPHostName� 540 DESC(�The name of the host. 541 �) 542 SYNTAX �IA5STRING� 543 SINGLE-VALUE 544 ) 546 (2.16.840.1.113719.1.25.4.1.48 547 NAME �DNIPLastUsed� 548 DESC(�The time that the address lease was last extended, 549 or initially given if it has never been extended. 550 �) 551 SYNTAX �TIME� 552 SINGLE-VALUE 553 ) 555 (2.16.840.1.113719.1.25.4.1.49 556 NAME �DNIPLeaseExpiration� 557 DESC(�The time when the lease will expire. 558 �) 559 SYNTAX �TIME� 560 SINGLE-VALUE 561 ) 563 (2.16.840.1.113719.1.25.4.1.46 564 NAME �DNIPObjectReference� 565 DESC(�The DN of another object in the tree that may 566 represent the usage of the address object with this attribute. 567 For example, this could be a DN of a computer or user object. 568 This is for informational purposes and may be provided 569 dynamically by system software or manually by an 570 administrator. 571 �) 572 SYNTAX �DN� 573 SINGLE-VALUE 574 ) 575 (2.16.840.1.113719.1.25.4.1.51 576 NAME �DNIPMACAddress� 577 DESC(�MAC address, with a format of the first octet being 578 hlen, second octet htype, and the remaining data is the actual 579 hardware address. 580 �) 581 SYNTAX �OCTETSTRING� 582 SINGLE-VALUE 583 ) 585 (2.16.840.1.113719.1.25.4.1.43 586 NAME �DNIPClientIdentifier� 587 DESC(�The DHCP client identifier. 588 �) 589 SYNTAX �OCTETSTRING� 590 SINGLE-VALUE 591 ) 593 (2.16.840.1.113719.1.25.4.1.50 594 NAME �DNIPFQDomainName� 595 DESC(�The fully qualified domain name of the client 596 �) 597 SYNTAX �IA5STRING� 598 SINGLE-VALUE 599 ) 601 (2.16.840.1.113719.1.25.4.1.79 602 NAME �DNIPComment� 603 DESC(�This is for the administrator to provide a comment 604 about the object.�) 605 SYNTAX �IA5STRING� 606 SINGLE-VALUE 607 ) 609 2.5 Subnet Pool 611 The Subnet Pool object is used to group together a set of 612 Subnets. It is a leaf object that is contained in any O, OU, 613 L, or C. The subnet pool has a multi valued attribute with 614 distinguished names of Subnet objects. 616 The primary purpose of the Subnet pool object is to group 617 together subnets when multiple subnets are being forwarded to 618 a DHCP server by a DHCP relay agent. Since only the address 619 of the DHCP relay agent is received by the DHCP server, it is 620 impossible for it to assign addresses from multiple subnets, 621 without having a way to group them together. 623 Object Class Definition: 625 (2.16.840.1.113719.1.25.6.1.3 626 NAME �DHCP Subnet Pool� 627 SUP top 628 PARENT (country $ organization $ organizationalUnit $ 629 locality) 630 STRUCTURAL 631 MUST (cn $ DNIPSubnetType 632 ) 633 MAY ( DNIPSubnetAttr $DNIPComment 634 ) 635 ) 636 Attribute Definitions: 638 (2.16.840.1.113719.1.25.4.1.31 639 NAME �DNIPSubnetType� 640 DESC(�This identifies the type of subnet. The defined 641 values are 1 = Subnet for LAN clients. 2 = Subnet for Remote 642 Access Clients. All subnets in the subnet pool must be the 643 same type as this attribute in the subnet pool.�) 644 SYNTAX �INTEGER� 645 SINGLE-VALUE 646 ) 648 (2.16.840.1.113719.1.25.4.1.1 649 NAME �DNIPSubnetAttr� 650 DESC(�A list of Subnet references. 651 �) 652 SYNTAX �DN� 653 MULTI-VALUED 654 ) 655 (2.16.840.1.113719.1.25.4.1.79 656 NAME �DNIPComment� 657 DESC(�This is for the administrator to provide a comment 658 about the object.�) 659 SYNTAX �IA5STRING� 660 SINGLE-VALUE 661 ) 663 2.6 DHCP Server 665 The DHCP Server object has attributes for server oriented 666 configuration. This includes distinguished names of Subnet 667 Address ranges assigned to the server for dynamic address 668 assignment. 670 Attributes have also been defined to provide for a fail-over 671 capability. The DHCP server object has attributes with syntax 672 of distinguished name to identify a primary and a secondary 673 DHCP server that will provide the DHCP service represented by 674 this object. 676 Object Class Definition: 678 (2.16.840.1.113719.1.25.6.1.4 679 NAME �DHCP Server� 680 SUP top 681 PARENT (country $ organization $ organizationalUnit $ 682 locality) 683 STRUCTURAL 684 MUST (cn 685 ) 686 MAY ( DNIPIPAssignmentPolicy $ DNIPSubnetAddressRangeAttr 687 $ DNIPPrimaryServerRefererence $ 688 DNIPSecondaryServerReference $ DNIPServerIPAddress $ 689 DNIPSecondaryServerIPAddress $ DNIPAuditLevel $ 690 DNIPFaultToleranceUpdateInterval 691 $DNIPFaultToleranceAutomatic $ 692 DNIPFaultToleranceSyncronizationDelay $DNIPPingEnabled $ 693 DNIPComment 694 ) 695 ) 697 Attribute Definitions: 699 (2.16.840.1.113719.1.25.4.1.45 700 NAME �DNIPAssignmentPolicy� 701 DESC(�Policy information for mobile clients. Indicates 702 whether the server should provide an IP address for a client 703 it is already aware of: 704 1 = Allow Duplicate�instructs the server to allow 705 the same client to get multiple IP addresses in more than one 706 subnet. 707 2 = Delete Duplicate�instructs the server to only 708 allow the client to get a single IP address. If the client had 709 an existing address assignment on one subnet and moved to 710 another subnet, the first address would be deleted as the new 711 one was assigned. 712 3 = No Duplicate�instructs the server to only 713 provide a client with a single IP address. If the client 714 already has an address assigned and requests another one, the 715 request for a new address assignment is ignored. 716 �) 717 SYNTAX �INTEGER� 718 SINGLE-VALUED 719 ) 721 (2.16.840.1.113719.1.25.4.1.23 722 NAME �DNIPSubnetAddressRangeAttr� 723 DESC(�The Subnet Address Ranges assigned to a server 724 �) 725 SYNTAX �DN� 726 MULTI-VALUED 727 ) 728 (2.16.840.1.113719.1.25.4.1.21 729 NAME �DNIPPrimaryServerReference� 730 DESC(�Reference to actual server that will be the primary 731 DHCP server 732 �) 733 SYNTAX �DN� 734 SINGLE-VALUED 735 ) 737 (2.16.840.1.113719.1.25.4.1.22 738 NAME �DNIPSecondaryServerReference� 739 DESC(�Reference to the server that will act as the fail- 740 over server in case the primary fails. 741 �) 742 SYNTAX �DN� 743 SINGLE-VALUED 744 ) 746 (2.16.840.1.113719.1.25.4.1.29 747 NAME �DNIPServerIPAddress� 748 DESC(�IP address of the primary DHCP server 749 �) 750 SYNTAX �OCTET_STRING� 751 SINGLE-VALUED 752 ) 754 (2.16.840.1.113719.1.25.4.1.16 755 NAME �DNIPSecondaryServerIPAddress� 756 DESC(�IP address of the Secondary DHCP server 757 �) 758 SYNTAX �OCTET_STRING� 759 SINGLE-VALUED 760 ) 762 (2.16.840.1.113719.1.25.4.1.27 763 NAME �DNIPAuditLevel� 764 DESC(�Level of auditing that the DHCP server is to 765 perform: 766 1 = No auditing 767 2 = Log major events 768 3 = Log leases and major events 769 4 = Log all events 770 �) 771 SYNTAX �INTEGER� 772 SINGLE-VALUED 773 ) 775 (2.16.840.1.113719.1.25.4.1.17 776 NAME �DNIP FT UpdateInterval� 777 DESC(�Denotes how often a primary will keep a 778 secondary informed about its health. The value is in 779 seconds. �1 implies that as soon as an update is made to 780 the directory, the secondary should be informed. 781 �) 782 SYNTAX �INTEGER� 783 SINGLE-VALUED 784 ) 786 (2.16.840.1.113719.1.25.4.1.24 787 NAME �DNIP FT Automatic� 788 DESC(�If set to true, in the event of a failure by 789 the primary server, automatic switch over will be 790 executed without operator intervention. 791 �) 792 SYNTAX �BOOLEAN� 793 SINGLE-VALUED 794 ) 796 (2.16.840.1.113719.1.25.4.1.18 797 NAME �DNIPFaultSynronizationDelay� 798 DESC(�A positive value in seconds. If undefined, a 799 value of zero is assumed. This attribute defines the 800 amount of time a secondary is willing to wait for 801 synchronization with DS during a take over from the 802 primary during fail-over. 803 �) 804 SYNTAX �INTEGER� 805 SINGLE-VALUED 806 ) 808 (2.16.840.1.113719.1.25.4.1.15 809 NAME �DNIPPingEnable� 810 DESC(�Indicates the DHCP server�s policy regarding 811 whether to ping addresses before making assignments: 812 1 = No Ping 813 2 = Ping Addresses 814 �) 815 SYNTAX �INTEGER� 816 SINGLE-VALUED 817 ) 819 (2.16.840.1.113719.1.25.4.1.79 820 NAME �DNIPComment� 821 DESC(�This is for the administrator to provide a comment 822 about the object.�) 823 SYNTAX �IA5STRING� 824 SINGLE-VALUE 825 ) 826 3. Acknowledgements 828 Thanks to Kester Fong for his work at Novell in defining the 829 DHCP schema and implementing a DHCP service tied into it. 831 Thanks to Winston Bumpus, Steve Bostock, Marc Lavine, Ed Reed, 832 and others at Novell who provided review input. 834 4. References 836 [DNSSCHEMA] 837 T. Miller, �Lightweight Directory Access Protocol (v3): 838 Schema for Domain Name System�, INTERNET-DRAFT , (work in progress) 841 [RFC2131] 842 R. Droms, �Dynamic Host Configuration Protocol�, RFC 843 2131, March 1997. 845 [RFC2132] 846 S. Alexander, R. Droms, "DHCP Options and BOOTP Vendor 847 Extensions�, RFC 2131, March 1997. 849 [RFC2241] 850 D. Provan, �DHCP Options for Novell Directory Services�, 851 RFC 2241, November 1997. 853 [RFC2242] 854 R. Droms, K. Fong, "NetWare/IP Domain Name and 855 Information, RFC 2242, November 1997. 857 [RFC2252] 858 M. Wahl, A. Coulbeck, T. Howles, S. Kille, "Lightweight 859 Directory Access Protocol (v3): Attribute Syntax 860 Definitions, RFC 2252, December 1997. 862 5. Authors� Addresses 864 Tom Miller 865 Novell, Inc. 866 2180 Fortune Dr. 867 San Jose, CA 95131 869 Phone: 408-577-8781 870 Fax: 408-577-5560 871 e-mail: tom_miller@novell.com 873 Alpesh Patel 874 Novell, Inc. 875 2180 Fortune Dr. 876 San Jose, CA 95131 878 Phone 408-577-8538 879 Fax: 408-577-5560 880 Email: apatel@novell.com 882 Patnala Rao 883 Novell, Inc. 884 2180 Fortune Dr. 885 San Jose, CA 95131 887 Phone 408-577-7752 888 Fax: 408-577-5560 889 Email: pdrao@novell.com