idnits 2.17.1 draft-ietf-dhc-migagntlist-00.txt: -(36): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(80): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** 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 Shadow Directories. == There are 2 instances of lines with non-ascii characters in the document. == 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 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. ** The abstract seems to contain references ([3], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack 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? (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 (June 2000) is 8717 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) == Unused Reference: '2' is defined on line 114, but no explicit reference was found in the text Summary: 6 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Nirupma Kulshreshtha 2 INTERNET DRAFT Novell Inc. 3 December 1999 4 Expires June 2000 6 The Migration Agent List Option for DHCP 7 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. Internet-Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its areas, 14 and its working groups. Note that other groups may also distribute 15 working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference 20 material or to cite them other than as "work in progress". 22 The list of current Internet-Drafts can be accessed at 23 http://www.ietf.org/ietf/1id-abstracts.txt. 25 The list of Internet-Drafts Shadow Directories can be accessed at 26 http://www.ietf.org/ietf/shadow.html. 28 This document is a submission to the Dynamic Host Configuration 29 Working Group of the Internet Engineering Task Force (IETF). Comments 30 should be submitted to the dhcp-v4@bucknell.edu mailing list. 32 Abstract 34 This document defines a new DHCP option for delivering configuration 35 information to hosts utilizing the Compatibility Mode Driver (CMD) 36 provided with Novell�s NetWare 5. This option is passed from the DHCP 37 server to the DHCP Client to provide the addresses of one or more 38 Migration Agents along with their CMD network number. 40 Introduction 42 The Dynamic Host Configuration Protocol (DHCP)[1] provides a 43 framework for passing configuration information to hosts on a TCP/IP 44 network. The Compatibility Mode Driver (CMD) provided with NetWare 5 45 facilitates smooth migration of networks from IPX and NetWare/IP, to 46 Pure IP. This component provides the necessary connectivity for IPX 47 Client/Server applications to communicate with nodes that connect to 48 the IP internet. It also allows IPX Client/Server applications to run 49 on IP Nodes. 51 Connectivity between IPX Nodes and IP Nodes is achieved through the 52 use of gateways called Migration Agents. 54 This document describes a DHCP option that carries addresses of one 55 or more Migration Agents along with their CMD Network number. The 56 addresses of Migration Agents are required by other Migration Agents 57 to discover new IPX Nodes. 59 Definitions 61 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 62 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this 63 document are to be interpreted as described in RFC 2119 [3]. 65 This document also uses the following terms: 67 "DHCP client" 69 DHCP client or "client" is an Internet host using DHCP to 70 obtain configuration parameters such as a network address. 72 "DHCP server" 74 A DHCP server or "server" is an Internet host that returns 75 configuration parameters to DHCP clients. 77 Migration Agent List Option Format 79 The code for this option is TBD. The minimum length specified in the 80 �Len� field is 8 bytes, and this length MUST be a multiple of 8. This 81 option can contain addresses of multiple migration agents along with 82 their CMD Network number. The first four bytes specifies the IP 83 address (in hexadecimal format) of the Migration Agent, and the next 84 four bytes specifies the CMD Network number (in hexadecimal format) 85 of the Migration Agent. 87 Code Len IP Address CMD Network Number 88 +-----+----+----+----+----+----+----+----+----+----+- 89 | TBD | 08 | a1 | a2 | a3 | a4 | n1 | n2 | n3 | n4 | 90 +-----+----+----+----+----+----+----+----+----+----+- 92 In the above example, (0xa1a2a3a4) specifies the IP address of the 93 Migration Agent and (0xn1n2n3n4) specifies the CMD Network number of 94 the Migration Agent. 96 DHCP Client Behavior 98 The DHCP client will use this option to get the IP addresses of all 99 the Migration Agents in the CMD network in which the client is 100 present. 102 Security Considerations 104 DHCP currently provides no authentication or security mechanisms. 105 Potential exposures to attack are discussed in section 7 of the DHCP 106 protocol specification [1]. In particular, these DHCP options allow 107 an unauthorized DHCP server to misdirect any client to a non existent 108 Migration Agent. 110 References 112 [1] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 113 1997. 114 [2] Alexander, S. and Droms, R., "DHCP Options and BOOTP Vendor 115 Extensions", RFC 2132, March 1997. 116 [3] Bradner, S., "Key words for use in RFCs to indicate requirement 117 levels", RFC 2119, March 1997. 119 Author Information 121 Nirupma Kulshreshtha 122 Novell Software Development (I) Ltd. 123 49/1 & 49/3, Garvebhavipalya 124 7th Mile, Hosur Road, 125 Bangalore - 560 068. INDIA 126 Phone: +91(80)572-1856 127 email: knirupama@novell.com 129 Expiration 131 This document will expire on June 6, 2000. 133 Full Copyright Statement 135 Copyright (C) The Internet Society (1998). All Rights Reserved. 137 This document and translations of it may be copied and furnished to 138 others, and derivative works that comment on or otherwise explain it 139 or assist in its implementation may be prepared, copied, published 140 and distributed, in whole or in part, without restriction of any 141 kind provided that the above copyright notice and this paragraph are 142 included on all such copies and derivative works. However, this 143 document itself may not be modified in any way, such as by removing 144 the copyright notice or references to the Internet Society or other 145 Internet organizations, except as needed for the purpose of 146 developing Internet standards in which case the procedures for 147 copyrights defined in the Internet Standards process must be 148 followed, or as required to translate it into languages other than 149 English. 151 The limited permissions granted above are perpetual and will not be 152 revoked by the Internet Society or its successors or assigns. 154 This document and the information contained herein is provided on an 155 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 156 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 157 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 158 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 159 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.