idnits 2.17.00 (12 Aug 2021) /tmp/idnits54573/draft-qin-softwire-multicast-prefix-option-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 31, 2011) is 3848 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) ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) == Outdated reference: draft-ietf-softwire-dslite-multicast has been published as RFC 8114 == Outdated reference: draft-ietf-softwire-mesh-multicast has been published as RFC 8638 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Softwire WG J. Qin 3 Internet-Draft ZTE 4 Intended status: Standards Track M. Boucadair 5 Expires: May 3, 2012 France Telecom 6 T. Tsou 7 Huawei Technologies (USA) 8 October 31, 2011 10 DHCPv6 Options for IPv6 DS-Lite Multicast Prefix 11 draft-qin-softwire-multicast-prefix-option-01 13 Abstract 15 This document defines Dynamic Host Configuration Protocol version 6 16 (DHCPv6) Options for multicast transition solutions, aiming to convey 17 the IPv6 prefixes to be used to build unicast and multicast IPv4- 18 embedded IPv6 addresses. 20 These options can be in particular used in the context of DS-Lite, 21 Stateless A+P and other IPv4-IPv6 interconnection techniques. 23 Status of this Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on May 3, 2012. 40 Copyright Notice 42 Copyright (c) 2011 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 3. PREFIX64 DHCPv6 Option . . . . . . . . . . . . . . . . . . . . 4 61 3.1. Option Format . . . . . . . . . . . . . . . . . . . . . . . 4 62 3.2. M_PREFIX64 Sub-option . . . . . . . . . . . . . . . . . . . 4 63 3.3. U_PREFIX64 Sub-option . . . . . . . . . . . . . . . . . . . 5 64 4. Client Behaviour . . . . . . . . . . . . . . . . . . . . . . . 6 65 5. Server Behaviour . . . . . . . . . . . . . . . . . . . . . . . 6 66 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 67 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 68 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 69 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 70 9.1. Normative References . . . . . . . . . . . . . . . . . . . 8 71 9.2. Informative References . . . . . . . . . . . . . . . . . . 8 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 74 1. Introduction 76 [I-D.ietf-softwire-dslite-multicast] and several other solutions 77 (e.g., [I-D.ietf-softwire-mesh-multicast], 78 [I-D.venaas-behave-mcast46], etc.) are proposed for the delivery of 79 multicast services in the context of transition to IPv6. Even these 80 solutions may have different applicable use cases, they all use 81 specific IPv6 addresses to embed IPv4 addresses, for both the 82 multicast group addresses 83 [I-D.boucadair-behave-64-multicast-address-format], and the multicast 84 source addresses [RFC6052]. 86 This document defines DHCPv6 options [RFC3315] to convey the IPv6 87 prefixes (a.k.a., PREFIX64) to be used for constructing these IPv4- 88 embedded IPv6 addresses. 90 These options can be in particular used in the context of DS-Lite 91 [RFC6333], Stateless A+P [RFC6346] and other IPv4-IPv6 92 interconnection techniques. 94 1.1. Requirements Language 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 98 document are to be interpreted as described in RFC 2119 [RFC2119]. 100 2. Terminology 102 This document makes use of the following terms: 104 o IPv4-embedded IPv6 address: is an IPv6 address which embeds a 32 105 bit-encoded IPv4 address [RFC6052]. An IPv4-embedded IPv6 address 106 can be unicast or multicast address. 108 o PREFIX64: is a dedicated IPv6 prefix for building IPv4-embedded 109 IPv6 addresses. A PREFIX64 can be of unicast or multicast. 111 o M_PREFIX64: denotes a multicast PREFIX64. It may belong to the 112 SSM range (i.e., ff3x::/32 [RFC4607]) or ASM range. 114 o U_PREFIX64: denotes a unicast PREFIX64 for building the IPv4- 115 embedded IPv6 addresses of multicast sources in SSM mode. 117 3. PREFIX64 DHCPv6 Option 119 OPTION_PREFIX64 is defined to convey the IPv6 prefix(es) to use to 120 synthesize IPv4-embbedded IPv6 addresses. This option MAY enclose 121 one or more sub-options. 123 3.1. Option Format 125 Figure 1 shows the format of the OPTION_PREFIX64 DHCPv6 option. 127 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 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 | OPTION_PREFIX64 | option-length | 130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 | sub-option | 132 . . 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | ... | 135 . . 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 137 | preferred-lifetime | 138 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 | valid-lifetime | 140 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 option-code: OPTION_PREFIX64 (TBD) 144 option-length: The length of enclosed sub-option(s) + 8 in octets 146 sub-option: One or several sub-obtions. Two sub-codes are defined 147 in this document: 148 (1) SUB_OPTION_M_PREFIX64 149 (2) SUB_OPTION_U_PREFIX64 151 preferred-lifetime: The preferred lifetime for the IPv6 prefix(es) 152 in the sub-option(s), expressed in units of seconds. 154 valid-lifetime: The valid lifetime for the IPv6 prefix(es) 155 in the sub-option(s), expressed in units of seconds. 157 Figure 1: DHCPv6 Option Format for PREFIX64 159 3.2. M_PREFIX64 Sub-option 161 This sub-option (Figure 2) is defined to convey the IPv6 multicast 162 prefix to use to synthesize the IPv4-embedded IPv6 addresses of the 163 multicast groups [I-D.boucadair-behave-64-multicast-address-format]. 164 The conveyed multicast IPv6 prefix MAY belong to the SSM range (i.e., 165 ff3x::/32 [RFC4607]) or ASM range. 167 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 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 169 | SUB_OPTION_M_PREFIX64 | sub-option-length | 170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 | prefix-length | reserved | 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 | | 174 | M_PREFIX64 (IPv6 multicast prefix) | 175 | | 176 | | 177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 sub-option-code: SUB_OPTION_M_PREFIX64 (TBD) 181 sub-option-len: 20 in octets 183 prefix-length: the length of M_PREFIX64 in bits 185 M_PREFIX64: the multicast prefix for constructing the IPv4-embedded 186 IPv6 addresses of multicast groups. It MAY belong to 187 SSM or ASM address range. 189 Figure 2: DHCPv6 Sub-option Format for M_PREFIX64 191 3.3. U_PREFIX64 Sub-option 193 This sub-option (Figure 3) is defined to convey the IPv6 unicast 194 prefix to be used in SSM mode for constructing the IPv4-embedded IPv6 195 addresses of the multicast sources. It is also used to extract the 196 IPv4 address from received multicast data flows (e.g., 197 [I-D.ietf-softwire-dslite-multicast]). The address synthesis MUST 198 follow the guidelines documented at [RFC6052]. 200 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 201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 202 | SUB_OPTION_U_PREFIX64 | sub-option-length | 203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 | prefix-length | reserved | 205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 206 | | 207 | U_PREFIX64 (IPv6 unicast prefix) | 208 | | 209 | | 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 sub-option-code: SUB_OPTION_U_PREFIX64 (TBD) 214 sub-option-len: 20 in octets 216 prefix-length: the length of U_PREFIX64 in bits 218 U_PREFIX64: the unicast prefix for constructing the IPv4-embedded 219 IPv6 addresses of the multicast sources in SSM mode 221 Figure 3: DHCPv6 Sub-option Format for U_PREFIX64 223 4. Client Behaviour 225 To retrieve the IPv6 prefixes to use to synthesize unicast and 226 multicast IPv4-embedded IPv6 addresses, the DHCPv6 client MUST 227 include OPTION_PREFIX64 in its OPTION_ORO. 229 If the DHCPv6 client receives more than one OPTION_PREFIX64 option 230 from the DHCPv6 server, only the first instance of that option MUST 231 be used. 233 When OPTION_PREFIX64 option is received from the DHCPv6 server, at 234 most three sub-options MAY be included. 236 The prefix conveyed in SUB_OPTION_U_PREFIX64 is used to synthesize 237 unicast IPv4-embedded IPv6 addresses as specified in [RFC6052]. 239 The prefix conveyed in SUB_OPTION_M_PREFIX64 is used to synthesize 240 multicast IPv4-embedded IPv6 addresses as specified in 241 [I-D.boucadair-behave-64-multicast-address-format]. 243 5. Server Behaviour 245 A DHCPv6 server MUST NOT reply with a value for the OPTION_PREFIX64 246 if the DHCPv6 client has not explicitly included OPTION_PREFIX64 in 247 its OPTION_ORO. 249 If OPTION_PREFIX64 option is requested by the DHCPv6 client, the 250 DHCPv6 server MUST NOT send more than one OPTION_PREFIX64 option in 251 the response. 253 One or two SUB_OPTION_M_PREFIX64 sub-options MAY be enclosed in 254 OPTION_PREFIX64 DHCPv6 option. In particular, if only SSM or ASM 255 mode is supported, only one SUB_OPTION_M_PREFIX64 sub-option MUST be 256 returned to the requesting client. If both SSM and ASM mode are 257 supported, two SUB_OPTION_M_PREFIX64 sub-options MUST be returned. 259 When two SUB_OPTION_M_PREFIX64 sub-options are present, one 260 SUB_OPTION_M_PREFIX64 sub-option MUST convey an IPv6 prefix in SSM 261 range and the other one MUST enclose an IPv6 prefix in the ASM range. 263 If the IPv6 multicast prefix conveyed in SUB_OPTION_M_PREFIX64 is an 264 SSM prefix, U_PREFIX64 sub-option MUST also be present. 266 6. Security Considerations 268 The security considerations in [RFC3315] are to be considered. 270 7. Acknowledgements 272 TBD 274 8. IANA Considerations 276 A new DHCPv6 option: 278 OPTION_PREFIX64 280 and two sub-options: 282 SUB_OPTION_M_PREFIX64, 284 SUB_OPTION_U_PREFIX64 286 need to be assigned by IANA. 288 9. References 289 9.1. Normative References 291 [I-D.boucadair-behave-64-multicast-address-format] 292 Boucadair, M., Qin, J., Lee, Y., Venaas, S., Li, X., and 293 M. Xu, "IPv4-Embedded IPv6 Multicast Address Format", 294 draft-boucadair-behave-64-multicast-address-format-03 295 (work in progress), October 2011. 297 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 298 Requirement Levels", BCP 14, RFC 2119, March 1997. 300 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 301 and M. Carney, "Dynamic Host Configuration Protocol for 302 IPv6 (DHCPv6)", RFC 3315, July 2003. 304 [RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for 305 IP", RFC 4607, August 2006. 307 [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. 308 Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, 309 October 2010. 311 9.2. Informative References 313 [I-D.ietf-softwire-dslite-multicast] 314 Wang, Q., Qin, J., Boucadair, M., Jacquenet, C., and Y. 315 Lee, "Multicast Extensions to DS-Lite Technique in 316 Broadband Deployments", 317 draft-ietf-softwire-dslite-multicast-00 (work in 318 progress), September 2011. 320 [I-D.ietf-softwire-mesh-multicast] 321 Xu, M., Cui, Y., Yang, S., Wu, J., Metz, C., and G. 322 Shepherd, "Softwire Mesh Multicast", 323 draft-ietf-softwire-mesh-multicast-01 (work in progress), 324 October 2011. 326 [I-D.venaas-behave-mcast46] 327 Venaas, S., Asaeda, H., SUZUKI, S., and T. Fujisaki, "An 328 IPv4 - IPv6 multicast translator", 329 draft-venaas-behave-mcast46-02 (work in progress), 330 December 2010. 332 [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 333 Stack Lite Broadband Deployments Following IPv4 334 Exhaustion", RFC 6333, August 2011. 336 [RFC6346] Bush, R., "The Address plus Port (A+P) Approach to the 337 IPv4 Address Shortage", RFC 6346, August 2011. 339 Authors' Addresses 341 Jacni Qin 342 ZTE 343 Shanghai, 344 China 346 Phone: +86 1391 8619 913 347 Email: jacni@jacni.com 349 Mohamed Boucadair 350 France Telecom 351 Rennes, 35000 352 France 354 Phone: 355 Email: mohamed.boucadair@orange.com 357 Tina Tsou 358 Huawei Technologies (USA) 359 2330 Central Expressway 360 Santa Clara, CA 95050 361 USA 363 Phone: +1 408 330 4424 364 Email: tina.tsou.zouting@huawei.com