idnits 2.17.1 draft-ietf-dhc-range-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) 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. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 156 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** 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.) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 75 has weird spacing: '...rotocol conve...' -- 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 (August 1998) is 9385 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 129 looks like a reference -- Missing reference section? '2' on line 132 looks like a reference Summary: 10 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Walter D. Lazear 2 INTERNET DRAFT MITRE Corporation 3 February 1998 4 Expires August 1998 6 The Server Range Option for DHCP 7 9 Status of this memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its areas, 13 and its working groups. Note that other groups may also distribute 14 working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six months 17 and may be updated, replaced, or obsoleted by other documents at any 18 time. It is inappropriate to use Internet-Drafts as reference 19 material or to cite them other than as ``work in progress.'' 21 To learn the current status of any Internet-Draft, please check the 22 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 23 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 24 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 25 ftp.isi.edu (US West Coast). 27 1 Abstract 29 This document describes a configuration option that may be used 30 by hosts acting as IP forwarders. The option contains information 31 about the networks adjacent to the host and may be required by 32 routing protocols. 34 2 Requirements 36 Throughout this document, the words that are used to define the 37 significance of particular requirements are capitalized. These 38 words are: 40 o "MUST" 42 This word or the adjective "REQUIRED" means that the 43 item is an absolute requirement of this specification. 45 o "MUST NOT" 47 This phrase means that the item is an absolute prohibition 48 of this specification. 50 o "SHOULD" 52 This word or the adjective "RECOMMENDED" means that there 53 may exist valid reasons in particular circumstances to ignore 54 this item, but the full implications should be understood and 55 the case carefully weighed before choosing a different course. 57 3 Terminology 59 This document uses the following terms: 61 o "DHCP client" 63 A DHCP client is an Internet host using DHCP to obtain 64 configuration parameters such as a network address. 66 o "DHCP server" 68 A DHCP server is an Internet host that returns configuration 69 parameters to DHCP clients. 71 4 Server Range Option 73 Any client that is configured by DHCP[1] may act as an IP packet 74 forwarder. Depending on the network topology, the client may need to 75 participate in a routing protocol conversation with one or more 76 neighboring routers. Part of the input to this conversation is the 77 network that is served by the forwarding client. The attached 78 network can be a simple classless range derived from the IP address 79 and network mask supplied by the DHCP server to the client. Using 80 the mask to obtain just the network prefix, the client can advertise 81 this prefix in the routing protocol conversation. 83 The network served by a forwarding client, however, can be composed 84 of a series of subnets. Normally only one of these subnets is 85 reflected in the address assigned to a client's interface. The 86 purpose of the Server Range Option is to supply the set of IP 87 addresses that the DHCP server is serving to nearby hosts. From this 88 set of addresses, the forwarding client can derive the set of subnets 89 to advertise to its router neighbors. There are two possible 90 approaches to supplying the addresses. Experimentation will 91 determine which is most useful. 93 The code for this option is 111 and the length is a multiple of 8. 95 4.1. Address Range Approach 97 The option is built by the server as pairs of starting and ending IP 98 addresses, expressing ranges that can represent subnets. The client 99 may have to aggregate ranges to derive a subnet and its mask. 101 Code Len Start1-address End1-address 102 +-----+-----+-----+-----+-----+-----+-----+-----+-----+----- 103 | 111 | n | s1 | s2 | s3 | s4 | e1 | e2 | e3 | e4 104 +-----+-----+-----+-----+-----+-----+-----+-----+-----+----- 106 Start2-address ... 107 +-----+-----+ 108 | s1 | s2 | . . . 109 +-----+-----+ 111 4.2 Prefix and Mask Approach 113 The option is build by the DHCP server as pairs of subnet prefixes 114 (padded with zeroes to 32 bits) and subnet masks. These are usable 115 directly by the client. 117 Code Len Address-Prefix1 Mask1 118 +-----+-----+-----+-----+-----+-----+-----+-----+-----+----- 119 | 111 | n | a1 | a2 | a3 | a4 | m1 | m2 | m3 | m4 120 +-----+-----+-----+-----+-----+-----+-----+-----+-----+----- 122 AddressPrefix2 ... 123 +-----+-----+ 124 | a1 | a2 | . . . 125 +-----+-----+ 127 5 References 129 [1] Droms, R., "Dynamic Host Configuration Protocol", RFC 1541, 130 Bucknell University, October 1993. 132 [2] Alexander, S., and R. Droms, "DHCP Options and BOOTP Vendor 133 Extensions", RFC 1533, Lachman Technology, Inc., Bucknell 134 University, October 1993. 136 6 Author's Address 138 Walter D. Lazear 139 MITRE Corporation 140 1820 Dolley Madison Blvd. 141 McLean VA 22102 143 Phone: 703 883 6515 144 EMail: lazear@mitre.org 146 This document will expire on August, 1998