idnits 2.17.1 draft-ietf-dhc-dhcpv6-opt-dstm-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: ---------------------------------------------------------------------------- == 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 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 the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (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 (Jan 2002) is 8136 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) == 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-05 -- Possible downref: Normative reference to a draft: ref. '3' ** Obsolete normative reference: RFC 2373 (ref. '4') (Obsoleted by RFC 3513) Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Bound 3 Internet-Draft Compaq Computer Corporation 4 Expires: July 2, 2002 M. Carney 5 Sun Microsystems, Inc. 6 C. Perkins 7 Nokia Research Center 8 T. Lemon 9 Nominum 10 B. Volz 11 Ericsson 12 R. Droms 13 Cisco Systems 14 Jan 2002 16 DSTM Options for DHCPv6 17 draft-ietf-dhc-dhcpv6-opt-dstm-00.txt 19 Status of this Memo 21 This document is an Internet-Draft and is in full conformance with 22 all provisions of Section 10 of RFC2026. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as Internet- 27 Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt. 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 This Internet-Draft will expire on July 2, 2002. 42 Copyright Notice 44 Copyright (C) The Internet Society (2002). All Rights Reserved. 46 Abstract 48 The DSTM Global IPv4 Address option and the DSTM Tunnel Endpoint 49 Option provide DSTM (Dual Stack Transition Mechanism) configuration 50 information to DHCPv6 hosts. 52 1. Introduction 54 This document describes two options for DHCPv6 [2] that provide 55 information for hosts using the "Dual Stack Transition Mechanism" 56 (DSTM) [3]. 58 2. Requirements 60 The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, 61 SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this 62 document, are to be interpreted as described in RFC 2119 [1] 64 3. Terminology 66 This document uses terminology specific to IPv6 and DHCPv6 as defined 67 in section "Terminology" of the DHCPv6 specification. 69 4. DSTM Global IPv4 Address option 71 The DSTM Global IPv4 Address option encapsulates other options that a 72 DHCP client is to use for DSTM. The DSTM Global IPv4 Address option 73 must include at least one Identity Association (IA) (see section 74 "Identity Association" of the DHCPv6 specification [2]) that carries 75 IPv4-mapped IPv6 addresses [4] as used in DSTM. 77 The format of the DSTM Global IPv4 Address option is: 79 0 1 2 3 80 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 81 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 82 | OPTION_DSTM | option-length | 83 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 84 . . 85 . options . 86 . . 87 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 89 option-code : OPTION_DSTM 91 option-length: Length of the 'options' field in octets 93 options : Options associated with DSTM 95 One Identity Association option (see section "Identity Association 96 option" of the DHCPv6 specification) MUST be encapsulated within the 97 options field in the DSTM Global IPv4 Address option. That IA option 98 MUST be used only for IPv4-mapped IPv6 addresses. 100 A DSTM Tunnel End Point option (Section 5) MAY be encapsulated in the 101 DSTM Global IPv4 Address option to specify one or more tunnel 102 endpoints. 104 5. DSTM Tunnel Endpoint Option 106 The DSTM Tunnel Endpoint option carries an IP address that is to be 107 used as a tunnel endpoint (TEP) to encapsulate IP datagrams within 108 IP. 110 The format of the DSTM Tunnel Endpoint option is: 112 0 1 2 3 113 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 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 | OPTION_DSTM_TEP | option-length | 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 . . 118 . tep . 119 . (16 octets) . 120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 122 option-code: OPTION_DSTM_TEP 124 option-length: 16 126 tep: Tunnel endpoint 128 A DSTM Tunnel EndPoint Option MUST NOT be used except when 129 encapsulated in a DSTM Global IPv4 Address option. 131 6. Appearance of these options 133 The DSTM Global IPv4 Address option MUST only appear in the options 134 section of the following DHCP messages: Solicit, Advertise, Request, 135 Confirm, Renew, Rebind, Decline, Release, Reply. 137 The DSTM Tunnel Endpoint option MUST only appear as an encapsulated 138 option in a DSTM Global IPv4 Address option. 140 7. Security Considerations 142 The DSTM Global IPv4 Address option may be used by an intruder DHCP 143 server to assign an invalid IPv4-mapped address to a DHCP client in a 144 denial of service attack. The DSTM Tunnel Endpoint option may be 145 used by an intruder DHCP server to configure a DHCP client with an 146 endpoint that would cause the client to route packets through an 147 intruder system. 149 To avoid these security hazards, a DHCP client MUST use authenticated 150 DHCP to confirm that it is exchanging the DSTM options with an 151 authorized DHCP server. 153 8. IANA Considerations 155 IANA is requested to assign an option code to this option from the 156 option-code space defined in section "DHCP Options" of the DHCPv6 157 specification [2]. 159 References 161 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 162 Levels", BCP 14, RFC 2119, March 1997. 164 [2] Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B. and R. 165 Droms (ed.), "Dynamic Host Configuration Protocol for IPv6 166 (DHCPv6)", draft-ietf-dhc-dhcpv6-23 (work in progress), February 167 2002. 169 [3] Bound, J., "Dual Stack Transition Mechanism (DSTM)", draft-ietf- 170 ngtrans-dstm-05 (work in progress), November 2001. 172 [4] Hinden, R. and S. Deering, "IP Version 6 Addressing 173 Architecture", RFC 2373, July 1998. 175 Authors' Addresses 177 Jim Bound 178 Compaq Computer Corporation 179 ZK3-3/W20 180 110 Spit Brook Road 181 Nashua, NH 03062-2698 182 USA 184 Phone: +1 603 884 0062 185 EMail: Jim.Bound@compaq.com 186 Mike Carney 187 Sun Microsystems, Inc. 188 Mail Stop: UMPK17-202 189 901 San Antonio Road 190 Palo Alto, CA 94303-4900 191 USA> 193 Phone: +1 650 786 4171 194 EMail: mwc@eng.sun.com 196 Charlie Perkins 197 Nokia Research Center 198 Communications Systems Lab 199 313 Fairchild Drive 200 Mountain View, CA 94043 201 USA 203 Phone: +1 650 625 2503 204 EMail: charliep@iprg.nokia.com 206 Nominum 208 EMail: mellon@nominum.com 210 Bernie Volz 211 Ericsson 212 959 Concord Street 213 Framingham, MA 01701 214 USA 216 Phone: +1 508 875 3162 217 EMail: bernie.volz@ericsson.com 219 Ralph Droms 220 Cisco Systems 221 250 Apollo Drive 222 Chelmsford, MA 01824 223 USA 225 Phone: +1 978 497 4733 226 EMail: rdroms@cisco.com 228 Full Copyright Statement 230 Copyright (C) The Internet Society (2002). All Rights Reserved. 232 This document and translations of it may be copied and furnished to 233 others, and derivative works that comment on or otherwise explain it 234 or assist in its implementation may be prepared, copied, published 235 and distributed, in whole or in part, without restriction of any 236 kind, provided that the above copyright notice and this paragraph are 237 included on all such copies and derivative works. However, this 238 document itself may not be modified in any way, such as by removing 239 the copyright notice or references to the Internet Society or other 240 Internet organizations, except as needed for the purpose of 241 developing Internet standards in which case the procedures for 242 copyrights defined in the Internet Standards process must be 243 followed, or as required to translate it into languages other than 244 English. 246 The limited permissions granted above are perpetual and will not be 247 revoked by the Internet Society or its successors or assigns. 249 This document and the information contained herein is provided on an 250 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 251 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 252 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 253 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 254 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 256 Acknowledgement 258 Funding for the RFC Editor function is currently provided by the 259 Internet Society.