idnits 2.17.1 draft-ietf-dhc-dhcpv6-opt-dstm-ports-01.txt: 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 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 4 longer pages, the longest (page 1) being 62 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. 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 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 2002) is 7979 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: '4' is defined on line 122, but no explicit reference was found in the text == Outdated reference: A later version (-28) exists of draft-ietf-dhc-dhcpv6-26 == Outdated reference: A later version (-08) exists of draft-ietf-ngtrans-dstm-07 -- Possible downref: Normative reference to a draft: ref. '3' ** Obsolete normative reference: RFC 2373 (ref. '4') (Obsoleted by RFC 3513) -- Possible downref: Normative reference to a draft: ref. '5' Summary: 4 errors (**), 0 flaws (~~), 6 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Myung-Ki Shin 3 Internet-Draft ETRI 4 Expires: December 2002 June 2002 6 DSTM Ports Option for DHCPv6 7 draft-ietf-dhc-dhcpv6-opt-dstm-ports-01.txt 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. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other 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 docu- 21 ments at any time. It is inappropriate to use Internet-Drafts as 22 reference material or to cite them other than as "work in pro- 23 gress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on August 2002. 33 Copyright Notice 35 Copyright (C) The Internet Society (2002). All Rights Reserved. 37 Abstract 39 The DSTM Ports Option provides DSTM (Dual Stack Transition 40 Mechanism) configuration information to DHCPv6 hosts. 42 1. Introduction 44 This document describes the Ports Option for DHCPv6 [2] that 45 provide information for hosts using the "Dual Stack Transition 46 Mechanism" (DSTM) [3]. 48 2. Requirements 49 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 50 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 51 this document are to be interpreted as described in RFC 2119 [1]. 53 3. Terminology 55 This document uses terminology specific to IPv6 and DHCPv6 as 56 defined in section "Terminology" of the DHCPv6 specification. 58 4. DSTM Ports Option 60 The DSTM Ports option carries a port range that is to be used for 61 the associated IPv4-mapped IPv6 address in an IA_DSTM option [5]. 63 The format of the DSTM Ports option is: 65 0 1 2 3 66 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 67 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 68 | OPTION_DSTM_PORTS | option-length | 69 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 70 | start port | end port | 71 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 73 option-code: OPTION_DSTM_PORTS (TBD) 75 option-length: 4 77 start port: The start port number for the associated IPv4- 78 mapped IPv6 address. 80 end port: The end port number for the associated IPv4- 81 mapped IPv6 address. 83 A DSTM Ports option MAY be encapsulated in an IA_DSTM option [5] to 84 specify the port range associted with the IPv4-mapped IPv6 address. 86 A DSTM Ports option MUST NOT be used except when encapsulated in an 87 IA_DSTM option [5]. 89 5. Appearance of these options 91 The DSTM Ports option MUST only appear as an encapsulated option in 92 an IA_DSTM option [5]. 94 6. Security Considerations 96 The DSTM Ports option may be used by an intruder DHCP server to 97 assign an invalid port range to a DHCP client in a denial of 98 service attack. 100 To avoid this security hazard, a DHCP client MUST use authenticated 101 DHCP to confirm that it is exchanging the DSTM options with an 102 authorized DHCP server. 104 7. IANA Considerations 106 IANA is requested to assign an option code to this option from the 107 option-code space defined in section "DHCP Option" of the DHCPv6 108 specification [2]. 110 References 112 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 113 Levels", BCP 14, RFC 2119, March 1997. 115 [2] Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B. and R. 116 Droms (ed.), "Dynamic Host Configuration Protocol for IPv6 117 (DHCPv6)", draft-ietf-dhc-dhcpv6-26 (work in progress), June 2002. 119 [3] Bound, J., "Dual Stack Transition Mechanism (DSTM)", draft-ietf- 120 ngtrans-dstm-07 (work in progress), Feburary 2002. 122 [4] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", 123 RFC 2373, July 1998. 125 [5] Volz, B. et al., "DSTM Options for DHCPv6", draft-ietf-dhc-dhcpv6- 126 opt-dstm-01.txt, (work in progress), April 2002. 128 Authors' Addresses 130 Myung-Ki Shin 131 ETRI PEC 132 161 Kajong-Dong, Yusong-Gu, Taejon 305-350, Korea 133 Tel : +82 42 860 4847 134 Fax : +82 42 861 5404 135 E-mail : mkshin@pec.etri.re.kr 137 Full Copyright Statement 139 Copyright (C) The Internet Society (2002). All Rights Reserved. 141 This document and translations of it may be copied and furnished to 142 others, and derivative works that comment on or otherwise explain it 143 or assist in its implementation may be prepared, copied, published 144 and distributed, in whole or in part, without restriction of any 145 kind, provided that the above copyright notice and this paragraph are 146 included on all such copies and derivative works. However, this 147 document itself may not be modified in any way, such as by removing 148 the copyright notice or references to the Internet Society or other 149 Internet organizations, except as needed for the purpose of 150 developing Internet standards in which case the procedures for 151 copyrights defined in the Internet Standards process must be 152 followed, or as required to translate it into languages other than 153 English. 155 The limited permissions granted above are perpetual and will not be 156 revoked by the Internet Society or its successors or assigns. 158 This document and the information contained herein is provided on an 159 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 160 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 161 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 162 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 163 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 165 Acknowledgement 167 Funding for the RFC Editor function is currently provided by the 168 Internet Society.