idnits 2.17.1 draft-ietf-dhc-dhcpv6-opt-dstm-ports-00.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 (February 2002) is 8077 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 131, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 134, but no explicit reference was found in the text == Outdated reference: A later version (-28) exists of draft-ietf-dhc-dhcpv6-23 == Outdated reference: A later version (-08) exists of draft-ietf-ngtrans-dstm-06 -- Possible downref: Normative reference to a draft: ref. '3' ** Obsolete normative reference: RFC 2373 (ref. '4') (Obsoleted by RFC 3513) == Outdated reference: A later version (-01) exists of draft-ietf-dhc-dhcpv6-opt-dstm-00 -- Possible downref: Normative reference to a draft: ref. '5' Summary: 4 errors (**), 0 flaws (~~), 8 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 Yong-Jin Kim 4 Expires: August 2002 ETRI 5 February 2002 7 DSTM Ports Option for DHCPv6 8 draft-ietf-dhc-dhcpv6-opt-dstm-ports-00.txt 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six 21 months and may be updated, replaced, or obsoleted by other docu- 22 ments at any time. It is inappropriate to use Internet-Drafts as 23 reference material or to cite them other than as "work in pro- 24 gress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on August 2002. 34 Copyright Notice 36 Copyright (C) The Internet Society (2002). All Rights Reserved. 38 Abstract 40 The DSTM Ports Option provide DSTM (Dual Stack Transition 41 Mechanism) configuration information to DHCPv6 hosts. 43 1. Introduction 45 This document describes the Ports Option for DHCPv6 [2] that 46 provide information for hosts using the "Dual Stack Transition 47 Mechanism" (DSTM) [3]. 49 2. Requirements 51 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 52 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 53 this document are to be interpreted as described in RFC 2119 [1]. 55 3. Terminology 57 This document uses terminology specific to IPv6 and DHCPv6 as 58 defined in section "Terminology" of the DHCPv6 specification. 60 4. DSTM Ports Option 62 The DSTM Ports option carries a port range that is to be used for 63 the associated IPv4-mapped IPv6 address in a DSTM Global IPv4 64 Address option. 66 The format of the DSTM Ports option is: 68 0 1 2 3 69 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 70 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 71 | OPTION_DSTM_PORTS | option-length | 72 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 73 | start port | end port | 74 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 76 option-code: OPTION_DSTM_PORTS 78 option-length: 4 80 start port: The start port number for the associated IPv4- 81 mapped IPv6 address. 83 end port: The end port number for the associated IPv4- 84 mapped IPv6 address. 86 A DSTM Ports option MAY be encapsulated in the DSTM Global IPv4 87 Address option to specify the port range associted with the IPv4- 88 mapped IPv6 address. 90 A DSTM Ports option MUST NOT be used except when encapsulated in a 91 DSTM Global IPv4 Address option. 93 5. Appearance of these options 95 The DSTM Ports option MUST only appear in the options section of 96 the following DHCP messages: Solicit, Advertise, Request, Confirm, 97 Renew, Rebind, Decline, Release, Reply. 99 The DSTM Ports option MUST only appear as an encapsulated option in 100 a DSTM Global IPv4 Address option. 102 6. Security Considerations 104 The DSTM Ports option may be used by an intruder DHCP server to 105 assign an invalid port range to a DHCP client in a denial of 106 service attack. 108 To avoid this security hazard, a DHCP client MUST use authenticated 109 DHCP to confirm that it is exchanging the DSTM options with an 110 authorized DHCP server. 112 7. IANA Considerations 114 IANA is requested to assign an option code to this option from the 115 option-code space defined in section "DHCP Option" of the DHCPv6 116 specification [2]. 118 References 120 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 121 Levels", BCP 14, RFC 2119, March 1997. 123 [2] Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B. and R. 124 Droms (ed.), "Dynamic Host Configuration Protocol for IPv6 125 (DHCPv6)", draft-ietf-dhc-dhcpv6-23 (work in progress), February 126 2002. 128 [3] Bound, J., "Dual Stack Transition Mechanism (DSTM)", draft-ietf- 129 ngtrans-dstm-06 (work in progress), Feburary 2002. 131 [4] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", 132 RFC 2373, July 1998. 134 [5] Bound, J. et al., "DSTM Options for DHCPv6", draft-ietf-dhc- 135 dhcpv6-opt-dstm-00.txt, (work in progress), February 2002. 137 Authors' Addresses 139 Myung-Ki Shin 140 ETRI PEC 141 161 Kajong-Dong, Yusong-Gu, Taejon 305-350, Korea 142 Tel : +82 42 860 4847 143 Fax : +82 42 861 5404 144 E-mail : mkshin@pec.etri.re.kr 145 Yong-Jin Kim 146 ETRI PEC 147 161 Kajong-Dong, Yusong-Gu, Taejon 305-350, Korea 148 Tel : +82 42 860 6564 149 Fax : +82 42 861 5404 150 E-mail : yjkim@pec.etri.re.kr 152 Full Copyright Statement 154 Copyright (C) The Internet Society (2002). All Rights Reserved. 156 This document and translations of it may be copied and furnished to 157 others, and derivative works that comment on or otherwise explain it 158 or assist in its implementation may be prepared, copied, published 159 and distributed, in whole or in part, without restriction of any 160 kind, provided that the above copyright notice and this paragraph are 161 included on all such copies and derivative works. However, this 162 document itself may not be modified in any way, such as by removing 163 the copyright notice or references to the Internet Society or other 164 Internet organizations, except as needed for the purpose of 165 developing Internet standards in which case the procedures for 166 copyrights defined in the Internet Standards process must be 167 followed, or as required to translate it into languages other than 168 English. 170 The limited permissions granted above are perpetual and will not be 171 revoked by the Internet Society or its successors or assigns. 173 This document and the information contained herein is provided on an 174 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 175 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 176 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 177 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 178 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 180 Acknowledgement 182 Funding for the RFC Editor function is currently provided by the 183 Internet Society.