idnits 2.17.1 draft-ietf-dhc-multopt-03.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-19) 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. ** 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 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.) ** 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? RFC 2119 keyword, line 80: '...at MDHCP clients SHOULD use to contact...' Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. 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? '3' on line 101 looks like a reference -- Missing reference section? '1' on line 95 looks like a reference -- Missing reference section? '2' on line 98 looks like a reference Summary: 10 errors (**), 0 flaws (~~), 1 warning (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 DHC working group Baiju V. Patel, Intel Corp. 2 Internet Draft Munil Shah, Microsoft Corp. 3 August 1998 Stephen R. Hanna, Sun Microsystems, Inc. 4 Expires: February 1999 draft-ietf-dhc-multopt-03.txt 6 Multicast Address Allocation Configuration Options 8 Status of this memo 10 This document is an Internet Draft. Internet Drafts are working 11 documents of the Internet Engineering Task Force (IETF), its Areas, 12 and its Working Groups. Note that other groups may also distribute 13 working documents as Internet Drafts. 15 Internet Drafts are draft documents valid for a maximum of six 16 months. Internet Drafts may be updated, replaced, or obsoleted by 17 other documents at any time. It is not appropriate to use Internet 18 Drafts as reference material or to cite them other than as a "working 19 draft" or "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, nic.nordu.net, ftp.isi.edu, or 24 munnari.oz.au. 26 A revised version of this draft document will be submitted to the RFC 27 editor as a Proposed Standard for the Internet Community. Discussion 28 and suggestions for improvement are requested. This document will 29 expire before February 1999. Distribution of this draft is unlimited. 31 Abstract 33 This document describes DHCP options that may be used to provide 34 access to Multicast Address Allocation servers, such as MDHCP 35 servers. 37 1. Terminology 39 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 40 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and"OPTIONAL" in this 41 document are to be interpreted as described in RFC 2119. 43 This document uses the following terms: 45 o "DHCP client" 47 A DHCP client is an Internet host using DHCP to obtain 48 configuration parameters such as a network address. 50 o "DHCP server" 52 A DHCP server is an Internet host that returns configuration 53 parameters to DHCP clients. 55 o "MDHCP client" 57 An MDHCP client is an Internet host requesting multicast 58 address allocation services via MDHCP. 60 o "MDHCP server" 62 An MDHCP server is an Internet host providing multicast 63 address allocation services via MDHCP. 65 2. Multicast Address Allocation Configuration Options 67 The MDHCP protocol [3] allows hosts (known as MDHCP clients) to 68 request multicast address allocation services from multicast address 69 allocation servers (known as MDHCP servers). One way that MDHCP 70 clients communicate with MDHCP servers is by sending multicast 71 messages to an MDHCP Server Multicast Address. 73 This document defines a DHCP option (as described in [1] and [2]) 74 that may be used to configure MDHCP clients with an appropriate MDHCP 75 Server Multicast Address and TTL. 77 2.1. MDHCP Server Multicast Address option 79 The MDHCP Server Multicast Address option specifies a multicast 80 address and TTL that MDHCP clients SHOULD use to contact MDHCP 81 servers. 83 A DHCP client can obtain this parameter as part of the normal DHCP 84 protocol message exchange or separately via DHCPINFORM. 86 Code Len Multicast Address TTL 87 +-----+-----+-----+-----+-----+-----+-----+ 88 | TBD | 5 | i1 | i2 | i3 | i4 | ttl | 89 +-----+-----+-----+-----+-----+-----+-----+ 91 The code for this option is TBD and the length is 5. 93 3. References 95 [1] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, 96 March 1997. 98 [2] Alexander, S., and R. Droms, "DHCP Options and BOOTP Vendor 99 Extensions", RFC 2132, March 1997. 101 [3] Patel, B., M. Shah, and S. Hanna, "Multicast address 102 allocation based on the Dynamic Host Configuration Protocol", 103 draft-ietf-malloc-mdhcp-00.txt, August 1998. 105 4. Authors' Addresses 107 Baiju V. Patel 108 Intel Corp. 109 2111 NE 25th Ave. 110 Hillsboro, OR 97124 112 Phone: 503 264 2422 113 EMail: baiju.v.patel@intel.com 115 Munil Shah 116 Microsoft Corporation 117 One Microsoft Way 118 Redmond, WA 98052 120 Phone: 425 703 3924 121 Email: munils@microsoft.com 123 Stephen R. Hanna 124 Sun Microsystems, Inc. 125 2 Elizabeth Drive, M/S UCHL03-205 126 Chelmsford, MA 01824 128 Phone: +1.978.442.0166 129 Email: steve.hanna@sun.com