idnits 2.17.1 draft-kumar-mboned-64mcast-wkp-address-00.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 (August 3, 2012) is 4284 days in the past. Is this intentional? Checking references for intended status: Full Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2119' is defined on line 252, but no explicit reference was found in the text == Unused Reference: 'RFC5234' is defined on line 256, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-softwire-dslite-multicast' is defined on line 267, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-softwire-mesh-multicast' is defined on line 274, but no explicit reference was found in the text == Unused Reference: 'RFC4607' is defined on line 283, but no explicit reference was found in the text == Outdated reference: A later version (-04) exists of draft-ietf-mboned-v4v6-mcast-ps-00 Summary: 0 errors (**), 0 flaws (~~), 7 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group N. Kumar 2 Internet Draft S. Venaas 3 Intended status: Standard Cisco Systems, Inc 4 Expires: February 2013 August 3, 2012 6 Well-Known Prefix for V4V6 Mcast Translation 7 draft-kumar-mboned-64mcast-wkp-address-00.txt 9 Status of this Memo 11 This Internet-Draft is submitted in full conformance with the 12 provisions of BCP 78 and BCP 79. 14 Internet-Drafts are working documents of the Internet 15 Engineering Task Force (IETF), its areas, and its working 16 groups. Note that other groups may also distribute working 17 documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of 20 six months and may be updated, replaced, or obsoleted by 21 other documents at any time. It is inappropriate to use 22 Internet-Drafts as reference material or to cite them other 23 than as "work in progress." 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 29 at http://www.ietf.org/shadow.html 31 This Internet-Draft will expire on February 3, 2009. 33 Copyright Notice 35 Copyright (c) 2012 IETF Trust and the persons identified as 36 the document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date 41 of publication of this document. Please review these 42 documents carefully, as they describe your rights and 43 restrictions with respect to this document. Code Components 44 extracted from this document must include Simplified BSD 45 License text as described in Section 4.e of the Trust Legal 46 Provisions and are provided without warranty as described in 47 the Simplified BSD License. 49 Abstract 51 This document reserves 2 Well known IPv6 Multicast prefixes 52 for the usage of IPv4-IPv6 Multicast transition. These 53 prefixes will be used to embed IPv4 group address as and when 54 required. 56 Table of Contents 58 1. Introduction...................................................2 59 2. Terminology....................................................3 60 3. Well-Known Prefix..............................................3 61 3.1. SSM64PREFIX Format........................................3 62 3.2. ASM64PREFIX Format........................................4 63 3.3. Text Representation.......................................5 64 4. Well-Known Prefix Usage........................................5 65 5. Use Cases......................................................5 66 5.1. IPv4 Receiver and Source connected over IPv6-Only 67 network........................................................6 68 6. Security Considerations........................................6 69 7. IANA Considerations............................................7 70 8. References.....................................................7 71 8.1. Normative References......................................7 72 8.2. Informative References....................................7 73 9. Acknowledgments................................................8 75 1. Introduction 77 As part of IPv4 to IPv6 migration, there are multiple 78 standards developed for smooth transition for Unicast. 79 Section 3 of [I-D.ietf-mboned-v4v6-mcast-ps] specifies 80 different possible scenarios for IPv4 to IPv6 multicast 81 transition as below, 83 1. IPv4 Receiver and Source connected over IPv6-Only 84 network 85 2. IPv6 Receiver Connected to IPv4 Source through IPv4 86 multicast access network and IPv6 Multicast network. 87 3. IPv6 Receiver and Source connected to IPv4-Only network. 88 4. IPv6 Receiver and IPv4 Source. 89 5. IPv4 Receiver and IPv6 Source. 91 Section 3.6 of [I-D.ietf-mboned-v4v6-mcast-ps] identifies the 92 use cases involving IPv4 source as highest priority. 94 There are also various solutions proposed (ex., [I-D.ietf- 95 softwire-mesh-multicast], [I-D.ietf-softwire-dslite- 96 multicast]) addressing the above use cases requirement which 97 requires to embed IPv4 multicast address into IPv6 address. 98 This IPv4-embedded IPv6 multicast address will be used as 99 group address within IPv6 cloud. 101 There were multiple options considered and discussed and this 102 draft is to document Well-known prefix option. 104 This document reserves 2 Well-Known prefixes from IPv6 105 Multicast address range which will be used for IPv4-IPv6 106 transition. 108 2. Terminology 110 (S4, G4)/(*, G4): (S, G) or (*, G) in IPv4 address format 112 (S6, G6)/(*, G6): (S, G) or (*, G) in IPv6 address format 114 SSM64PREFIX: Well-Known prefix reserved for SSM range IPv6 115 Multicast address as specified in Section 3.1. 117 ASM64PREFIX: Well-Known prefix reserved for ASM range IPv6 118 Multicast address as specified in Section 3.2. 120 3. Well-Known Prefix 122 This document reserves the below two address prefixes from 123 IPv6 Multicast address range for IPv4-IPv6 transition. 125 3.1. SSM64PREFIX Format 127 SSM64PREFIX is the prefix reserved from IPv6 SSM range 128 represented as below, 129 | 8 | 4 | 4 | 8 | 8 | 16 | 48 | 32 | 130 +--------+----+----+--------+--------+---------~----+----------+ 131 |11111111|0011|scop|00000000|00000000| WKP|0000~0000| V4-group | 132 +--------+----+----+--------+--------+----+----~----+----------+ 134 Scop : Scope as specified in [RFC4291] 136 WKP : Set to 04E6 in hexadecimal format. 138 V4-group : IPv4 multicast group address 140 The textual representation of SSM64PREFIX will be as below, 142 FF3x:0:0:04E6::/96 144 3.2. ASM64PREFIX Format 146 ASM64PREFIX is the prefix reserved from IPv6 ASM range 147 represented as below, 149 | 8 | 4 | 4 | 8 | 8 | 16 | 48 | 32 | 150 +--------+----+----+--------+--------+---------~----+----------+ 151 |11111111|0000|scop|00000000|00000000| WKP|0000~0000| V4-group | 152 +--------+----+----+--------+--------+----+----~----+----------+ 154 Scop : Scope as specified in [RFC4291] 156 WKP : Set to 04E6 in hexadecimal format. 158 V4-group : IPv4 multicast group address 160 The textual representation of ASM64PREFIX will be as below, 162 FF0x:0:0:04E6::/96 164 3.3. Text Representation 166 IPv4-embedded IPv6 Multicast address can be represented in 167 text with IPv4 group address in dotted decimal notation or 168 hexadecimal notation in conformity with Section 2.2 of 169 [RFC4291]. 171 Below are the example of text representation for ASM64PREFIX 172 and SSM64PREFIX, 174 +-------------------+--------------+------------------------------+ 175 | Well-Known Prefix | IPv4 address |V4-Embedded V6 group address | 176 +-------------------+--------------+------------------------------+ 177 | FF0x:0:0:4E6::/96 | 233.252.0.1 | FF0X:0:0:04E6::233.252.0.1 | 178 | | | (OR) | 179 | | | FF0X:0:0:04E6::E9FC:0001 | 180 +-------------------+--------------+------------------------------+ 181 | FF3x:0:0:4E6::/96 | 233.252.0.1 | FF3X:0:0:04E6::233.252.0.1 | 182 | | | (OR) | 183 | | | FF3X:0:0:04E6::E9FC:0001 | 184 +-------------------+--------------+------------------------------+ 186 4. Well-Known Prefix Usage 188 This document doesn't propose any procedure to define the 189 usage of the reserved well-known IPv6 Multicast prefix. Any 190 solution proposed to solve the transition problem mentioned 191 in [I-D.ietf-mboned-v4v6-mcast-ps] may use this reserved 192 prefixes. 194 5. Use Cases 196 In this document, we also describe the behavior of one high 197 priority scenario with above procedure. 199 5.1. IPv4 Receiver and Source connected over IPv6-Only network 201 This scenario simply known as 4-6-4 is shown below in Figure 202 1. 204 +--------+ +--------+ 205 | Host | | IPv4 | 206 | Rcvr | | DR | 207 | | | | 208 +--------+ +--------+ 209 | | 210 IGMP/IPv4 PIM IGMP/IPv4 PIM 211 | | 212 | | 213 +--------+ +--------+ +--------+ 214 | | MLD | IPv6 | IPv6 | | 215 | AFBR1 |----------| Only |----------| AFBR2 | 216 | | IPv6 PIM | Rtr | PIM | | 217 +--------+ +--------+ +--------+ 218 Figure 1: 4-6-4 Scenario 220 AFBR1 on receiving (S4, G4) or (*, G4) PIM Join or IGMP 221 Report will perform the below, 223 1. If Upstream is IPv6 PIM neighbor and if G4 is from ASM 224 range, should embed the IPv4 multicast group into last 225 32 bits of ASM64PREFIX and send PIMv6 JOIN towards 226 remote AFBR. 227 2. If Upstream is IPv6 PIM router, and if G4 is from SSM 228 range, should embed the IPv4 multicast group into last 229 32 bits of SSM64PREFIX and send PIMv6 JOIN upstream. 231 6. Security Considerations 233 This document reserves 2 IPv6 Multicast prefixes for Ipv4- 234 IPv6 transition purpose. The same security considerations 235 apply as those for [RFC6052]. This document doesn't introduce 236 any new security issues. 238 7. IANA Considerations 240 IANA is requested to reserve 2 variable scope IPv6 Multicast 241 prefixes for IPv4-IPv6 transition purpose. These should be the 242 /96 prefixes; 244 SSM Range - FF3x:0:0:04E6::/96 246 ASM Range - FF0x:0:0:04E6::/96 248 8. References 250 8.1. Normative References 252 [RFC2119] Bradner, S., "Key words for use in RFCs to 253 Indicate Requirement Levels", BCP 14, RFC 2119, 254 March 1997. 256 [RFC5234] Crocker, D. and Overell, P.(Editors), "Augmented 257 BNF for Syntax Specifications: ABNF", RFC 5234, 258 January 2008. 260 8.2. Informative References 262 [I-D.ietf-mboned-v4v6-mcast-ps] 263 Jacquenet, C., Boucadair, M., Lee, Y., Qin, J., 264 Tsou, T., and Q. Sun, "IPv4-IPv6 Multicast: Problem 265 Statement and Use Cases", draft-ietf-mboned-v4v6- 266 mcast-ps-00 (work in progress), May 2012. 267 [I-D.ietf-softwire-dslite-multicast] 268 Qin, J., Boucadair, M., Jacquenet, C., Lee, Y., 269 and Q. Wang, "Multicast Extension to DS-Lite 270 Technique in Broadband Deployments", 271 Draft-ietf-softwire-dslite-multicast-02 (work in 272 progress), May 2012. 274 [I-D.ietf-softwire-mesh-multicast] 275 Xu, M., Cui, Y., Yang, S., Wu, J., Metz, C., and 276 G. Shepherd, "Softwire Mesh Multicast", 277 Draft-ietf-softwire-mesh-multicast-02 (work in 278 progress), April 2012. 280 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 281 Architecture", RFC 4291, February 2006. 283 [RFC4607] Holbrook, H. and B. Cain "Source-Specific 284 Multicast for IP", RFC 4607, August 2006. 286 [RFC6052] Bao, C., Huitema, C., Bagnulo, M./ Boucadair, M., 287 and X. Li, "IPv6 Addressing of IPv4/IPv6 288 Translators", RFC 6052, October 2010. 290 9. Acknowledgments 292 This document was prepared using 2-Word-v2.0.template.dot. 294 Authors' Addresses 296 Stig Venaas 297 Cisco Systems, Inc. 298 Tasman Drive 299 San Jose, CA 95134 300 USA 301 Email: stig@cisco.com 303 Nagendra Kumar 304 Cisco Systems 305 Cessna Business Park, Sarjapura Marathalli Outer Ring Road 306 Bangalore, KARNATAKA 560 087 307 India 308 Email: naikumar@cisco.com