idnits 2.17.1 draft-omar-ipmix-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: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 7 longer pages, the longest (page 9) being 136 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 9 pages 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. ** There are 68 instances of too long lines in the document, the longest one being 24 characters in excess of 72. ** There are 8 instances of lines with control characters in the document. == There are 12 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. == There are 6 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The "Author's Address" (or "Authors' Addresses") section title is misspelled. -- The document date (September 28, 2017) is 2402 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) == Missing Reference: 'RFC-2460' is mentioned on line 68, but not defined ** Obsolete undefined reference: RFC 2460 (Obsoleted by RFC 8200) == Missing Reference: 'RFC-791' is mentioned on line 69, but not defined ** Obsolete normative reference: RFC 2460 (ref. 'RFC-2401') (Obsoleted by RFC 8200) Summary: 5 errors (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 draft-omar-ipmix-00 Khaled Omar 2 Internet-Draft The Road 3 Intended status: Standards Track 4 Expires: March 28, 2018 September 28, 2017 6 Internet Protocol Mixture (IPmix) 7 Specification 8 draft-omar-ipmix-00 10 Status of this Memo 12 This Internet-Draft is submitted in full conformance with the provisions 13 of BCP 78 and BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering Task 16 Force (IETF). Note that other groups may also distribute working documents 17 as Internet-Drafts. The list of current Internet-Drafts is at 18 http://datatracker.ietf.org/drafts/current/. 20 Internet-Drafts are draft documents valid for a maximum of six months and 21 may be updated, replaced, or obsoleted by other documents at any time. 22 It is inappropriate to use Internet-Drafts as reference material or to cite 23 them other than as "work in progress." 25 This Internet-Draft will expire on March 28, 2018. 27 Copyright Notice 29 Copyright (c) 2017 IETF Trust and the persons identified as the document 30 authors. All rights reserved. 32 This document is subject to BCP 78 and the IETF Trust's Legal Provisions 33 Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect 34 on the date of publication of this document. Please review these documents 35 carefully, as they describe your rights and restrictions with respect to this 36 document. Code Components extracted from this document must include 37 Simplified BSD License text as described in Section 4.e of the Trust Legal 38 Provisions and are provided without warranty as described in the Simplified 39 BSD License. 41 Abstract 43 This document specifies the Internet Protocol Mixture (IPmix). 45 Table of Contents 47 1. Introduction..................................................1 48 2. Internet Protocol Mixture (IPmix).............................3 49 3. The Four Types of Communication...............................3. 50 3.1. IPmix: IPv6 Host to IPv4 Host...............................4 51 3.2. IPmix: IPv4 Host to IPv6 Host...............................5 52 3.3. IPmix: IPv6 Host to IPv6 Host...............................6 53 3.4. IPmix: IPv4 Host to IPv4 Host...............................7 54 4. IPmix Packet Header Format....................................8 55 5. Advantages of IPmix...........................................8 56 6. Security Considerations.......................................9 57 7. Acknowledgments...............................................9 58 8. Author Address................................................9 59 9. References....................................................9 60 10. IANA Considerations..........................................9 61 11. Full Copyright Statement.....................................9 63 RFC IPmix Specification September 28, 2017 65 1. Introduction 67 IPmix is a new version of the Internet Protocol, 68 designed to allow IP version 6 [RFC-2460] to communicate to 69 IP version 4 (IPv4) [RFC-791] and vice versa. 71 - Internet is the global wide network used for communication between 72 hosts connected to it. 74 - These connected hosts (PCs, servers, routers, mobile devices, etc.) 75 must have a global unique addresses to be able to communicate 76 through the Internet and these unique addresses are defined in the 77 Internet Protocol (IP). 79 - The first version of the Internet Protocol is IPv4. 81 - When IPv4 was developed in 1975, it was not expected that the number 82 of connected hosts to the Internet reach a very huge number of hosts 83 more than the IPv4 address space, also it was aimed to be used for 84 experimental purposes in the beginning. 86 - IPv4 is (32-bits) address allowing approximately 4.3 billion unique 87 IP addresses. 89 - A few years ago, with the massive increase of connected hosts to the 90 Internet, IPv4 addresses started to run out. 92 - Three short-term solutions (CIDR, Private addressing, and NAT) were 93 introduced in the mid-1990s but even with using these solutions, 94 the IPv4 address space ran out in February, 2011 as announced by 95 IANA, The announcement of depletion of the IPv4 address space by 96 the RIRs is as follows: 98 * April, 2011: APNIC announcement. 99 * September, 2012: RIPE NCC announcement. 100 * June, 2014: LACNIC announcement. 101 * September, 2015: ARIN announcement. 103 - A long term solution (IPv6) was introduced to increase the address 104 space used by the Internet Protocol and this was defined in the 105 Internet Protocol version 6 (IPv6). 107 RFC IPmix Specification September 28, 2017 109 - IPv6 was developed in 1995 by the Internet Engineering Task Force 110 (IETF). 112 - IPv6 is (128-bits) address and can support a huge number of unique 113 IP addresses that is approximately equals to 2^128 unique addresses. 115 - So, the need for IPv6 became a vital issue to be able to support 116 the massive increase of connected hosts to the Internet after the 117 IPv4 address space exhaustion. 119 - The migration from IPv4 to IPv6 became a necessary thing, but 120 unfortunately, it would take decades for this full migration to be 121 accomplished. 123 - 22 years have passed since IPv6 was developed, but no full migration 124 happened till now and this would cause the Internet to be divided 125 into two parts, as IPv4 still dominating on the Internet traffic 126 (85% as measured by Google in April, 2017) and new Internet hosts 127 will be assigned IPv6-only addresses and be able to communicate with 128 15% only of the Internet services and apps. 130 - So, the need for solutions for the IPv4 and IPv6 coexistence became 131 an important issue in the migration process as we cannot wake up in 132 the morning and find all IPv4 hosts are migrated to be IPv6 hosts, 133 especially, as most enterprises have not do this migration for 134 creating a full IPv6 implementation. 136 - Also, the request for using IPv6 addresses in addition to the 137 existing IPv4 addresses (IPv4/IPv6 Dual Stacks) in all enterprise 138 networks have not achieve a large implementation that can make IPv6 139 the most dominated IP in the Internet as many people believe that 140 they will not have benefits from just having a larger IP address 141 bits and IPv4 satisfies their needs, also, not all enterprises 142 devices support IPv6 and also many people are afraid of the service 143 outage that can be caused due to this migration. 145 - The recent solutions for IPv4 and IPv6 coexistence are: 147 Native dual stack (IPv4 and IPv6) 148 Tunneling 149 NAT64 150 Dual-stack Lite 151 464xlat 152 MAP 153 (other technologies also exist, like lw6over4; they may have more 154 specific use cases) 156 - IPv4/IPv6 Dual Stack, allows both IPv4 and IPv6 to coexist by 157 using both IPv4 and IPv6 addresses for all hosts at the same time, 158 but this solution does not allows IPv4 hosts to communicate to 159 IPv6 hosts and vice versa. Also, after the depletion of the IPv4 160 address space, new Internet hosts will not be able to use IPv4/IPv6 161 Dual Stacks. 163 - Tunneling, allows IPv6 hosts to communicate to each other through 164 an IPv4 network, but still does not allows IPv4 hosts to communicate 165 to IPv6 hosts and vice versa. 167 - NAT-PT, allows IPv6 hosts to communicate to IPv4 hosts with only 168 using hostnames and getting DNS involved in the communication process 169 but this solution was inefficient because it does not allows 170 communication using direct IP addresses, also the need for so much 171 protocol translations of the source and destination IP addresses 172 made the solution complex and not applicable thats why it was moved 173 to the Historic status in the RFC 2766. Also, NAT64 requires so much 174 protocol translations and statically configured bindings, and also 175 getting a DNS64 involved in the communication process. 177 RFC IPmix Specification September 28, 2017 179 2. Internet Protocol Mixture (IPmix). 181 - IPmix is the solution presented in this Internet draft. 183 - It solves the issue of allowing IPv6 only hosts to communicate to 184 IPv4 only hosts and vice versa in a simple and very efficient way, 185 especially when the communication is done using both direct IP 186 addresses and when using hostnames between IPmix hosts, as there 187 is no need for protocol translations or getting the DNS involved 188 in the communication process more than its normal address 189 resolution function. 191 - IPmix allows hosts from two IP versions (IPv4 and IPv6) to be able 192 to communicate, and this can be accomplished by having an IPmix 193 packet containing a mixture of IPv4 and IPv6 addresses in the same 194 IP packet header. 196 - From here the name of IPmix arises, as the IP packet can contain 197 (IPv6 + IPv4 /IPv4 + IPv6) addresses in the same layer 3 packet 198 header. 200 RFC IPmix Specification September 28, 2017 202 3. The Four Types of Communication. 204 3.1) IPmix: IPv6 Host to IPv4 Host. 205 ------------------------------ 207 - IPmix Packet: 209 |<-------- 128-bit ------>|<------------------ 128-bit ---------------->| 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 211 | Data| Source IPv6 Address | Destination IPv4 Address MAC 0000..0 | 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 |<--------- 32-bit -------->| 48-bit | 48-bit | 215 MAC ==> The sending host MAC address. 217 - The destination address is 128 bit, when the 1st 48-bits are zeros, the router 218 will know that the last 32-bit is an IPv4 address and it can start forwarding 219 the packet based on that address. 221 - The second 48-bit represents the sending host MAC address and this can be used for 222 host identification. 224 - The last 32-bit represents the destination IPv4 address. 226 - Sending IPmix host TCP/IP Configuration: 228 IP Address: IPv6 Address 229 Prefix Length: /length 230 Default Gateway: IPv6 Address (Optional) 231 DNS Addresses: IPv6/IPv4 Address 233 - Example of IPmix Operation: 234 --------------------------- 236 R1 & R2 have both IPv4/IPv6 routing enabled 237 IPmix Host IPmix Host 239 PC-1 R1 * R2 PC-2 240 +----+ * * +----+ 241 | | * * * * | | 242 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 243 +----+ 2001:1::1 * * * * 192.168.1.1 +----+ 244 / / * Network * / / 245 +----+ * * +----+ 246 * * 247 IPv6: 2001:1::10/64 * IPv4: 192.168.1.10/24 248 DG : 2001:1::1 DG : 192.168.1.1 250 | 128-bit | 128-bit | 251 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 252 |Data | 2001:1::10 | 192.168.1.10 MAC 000..0 |---> 253 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 254 Src. IPv6 Address Dest. IPv4 Address 256 IPmix: IPv6 host to IPv4 host 258 RFC IPmix Specification September 28, 2017 260 3.2) IPmix: IPv4 Host to IPv6 Host. 261 ------------------------------ 263 - IPmix Packet: 265 | 128-bit | 128-bit | 266 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 267 | Data| Source IPv4 Address MAC 000..0 | Destination IPv6 Address | 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 270 - Sending IPmix host TCP/IP Configuration: 272 IP Address: IPv4 Address 273 Subnet Mask: /mask 274 Default Gateway: IPv4 Address 275 DNS Addresses: IPv4/IPv6 Address 277 - Example of IPmix Operation: 278 --------------------------- 280 R1 & R2 have both IPv4/IPv6 routing enabled 281 IPmix Host IPmix Host 283 PC-1 R1 * R2 PC-2 284 +----+ * * +----+ 285 | | * * * * | | 286 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 287 +----+ 2001:1::1 * * * * 192.168.1.1 +----+ 288 / / * Network * / / 289 +----+ * * +----+ 290 * * 291 IPv6: 2001:1::10/64 * IPv4: 192.168.1.10/24 292 DG : 2001:1::1 DG : 192.168.1.1 294 | 128-bit | 128-bit | 295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 296 <---| 2001:1::10 | 000..0 MAC 192.168.1.10 | Data | 297 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 298 Dest. IPv6 Address Src. IPv4 Address 300 IPmix: IPv4 host to IPv6 host 302 RFC IPmix Specification September 28, 2017 304 3.3) IPmix: IPv6 Host to IPv6 Host. 305 ------------------------------ 307 - IPmix Packet: 309 | 128-bit | 128-bit | 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 311 | Data| Source IPv6 Address | Destination IPv6 Address | 312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 314 - Sending IPmix host TCP/IP Configuration: 316 IP Address: IPv6 Address 317 Prefix Length: /Length 318 Default Gateway: IPv6 Address (Optional) 319 DNS Addresses: IPv6/IPv4 Address 321 - Example of IPmix Operation: 322 --------------------------- 324 R1 & R2 have both IPv4/IPv6 routing enabled 325 IPmix Host IPmix Host 327 PC-1 R1 * R2 PC-2 328 +----+ * * +----+ 329 | | * * * * | | 330 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o---------o| | 331 +----+ 2001:1::1 * * * * 3001:1::1 +----+ 332 / / * Network * / / 333 +----+ * * +----+ 334 * * 335 IPv6: 2001:1::10/64 * IPv6: 3001:1::10/64 336 DG : 2001:1::1 DG : 3001:1::1 338 | 128-bit | 128-bit | 339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 340 |Data | 2001:1::10 | 3001:1::10 |---> 341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 Src. IPv6 Address Dest. IPv6 Address 344 IPmix: IPv6 host to IPv6 host 346 RFC IPmix Specification September 28, 2017 348 3.4) IPmix: IPv4 Host to IPv4 Host. 349 ------------------------------ 351 - IPmix Packet: 353 | 128-bit | 128-bit | 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 | Data| Source IPv4 Address MAC 000..0 | Destination IPv4 Address MAC 000..0 | 356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 358 - Sending IPmix host TCP/IP Configuration: 360 IP Address: IPv4 Address 361 Subnet Mask: /Mask 362 Default Gateway: IPv4 Address 363 DNS Addresses: IPv6/IPv4 Address 365 - Example of IPmix Operation: 366 --------------------------- 368 R1 & R2 have both IPv4/IPv6 routing enabled 369 IPmix Host IPmix Host 371 PC-1 R1 * R2 PC-2 372 +----+ * * +----+ 373 | | * * * * | | 374 | |o--------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 375 +----+ 10.1.1.1 * * * * 192.168.1.1 +----+ 376 / / * Network * / / 377 +----+ * * +----+ 378 * * 379 IPv4: 10.1.1.10/24 * IPv6: 192.168.1.10/24 380 DG : 10.1.1.1 DG : 192.168.1.1 382 | 128-bit | 128-bit | 383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 384 |Data | 10.1.1.10 MAC 000..0 | 192.168.1.10 MAC 000..0 |---> 385 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 386 Src. IPv4 Address Dest. IPv4 Address 388 IPmix: IPv4 host to IPv4 host 390 Important Notes: - IPv4 and IPv6 routing must be enabled on all routers, so 391 when a router receives an IPmix packet, it should use 392 the appropriate routing table based on the destination 393 address within the IPmix packet. 395 - That means, if the received IPmix packet contains an IPv4 396 address in the destination address field, the router 397 should use the IPv4 routing table to make a routing 398 decision, and if the received IPmix packet contains an IPv6 399 address in the destination address field, the router should 400 use the IPv6 routing table to make a routing decision. 402 - All Internet connected hosts must be IPmix hosts to be 403 able to communicate regardless the used IP version, 404 and the IPmix deployment process can be accomplished 405 by ALL technology companies developing OSs for hosts 406 networking and security devices. 408 When the source or destination is an IPv4 address, the IPv4 address is located in 409 the last 32 bits. 411 When the source is IPv4 and the destination is IPv6, the sending host will consider 412 the destination IPv6 address as an IPv4 address not on the same subnet, meaning it 413 should send this frame to the default gateway (router). 415 Once the router receives the frame, it removes the frame header and trailer and look 416 for the destination IPv6 address, then the router start to take a routing decision by 417 checking its IPv6 routing table and start sending the packet to the next hop through 418 the IPv6 network. 420 Similarly, when the source is IPv6 and the destination is IPv4, the sending host will 421 consider the destination IPv4 address as an IPv6 address not on the same subnet, meaning 422 it should send this frame to the default gateway (router) 424 Once the router receives the frame, it removes the frame header and trailer and look for 425 the destination IPv4 address, then the router start to take a routing decision by checking 426 its IPv4 routing table and start sending the packet to the next hop through the IPv4 network. 428 S D 429 IPv4-IPv6 ---> IPv6 ---> IPv6 Network ---> IPv6 430 Sending Host Router Destination Host 432 S D 433 IPv4 <--- IPv4 Network <--- IPv4 <--- IPv6-IPv4 434 Destination Host Router Sending Host 436 RFC IPmix Specification September 28, 2017 438 4. IPmix Packet Header Format. 440 - The following figure shows the IPmix packet header which is almost 441 the same as the IPv6 packet header: 443 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 444 |Version| Traffic Class | Flow Label | 445 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 446 | Payload Length | Next Header | Hop Limit | 447 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 448 | | 449 + + 450 | | 451 + Source Address + 452 | | 453 + + 454 | | 455 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 456 | | 457 + + 458 | | 459 + Destination Address + 460 | | 461 + + 462 | | 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 465 Version 4-bit Internet Protocol version number. 467 - 0100 : IPv4 Packet 468 (Src. and dest. are IPv4). 469 - 0110 : IPv6 Packet 470 (Src. and dest. are IPv6). 471 - 1010 : IPmix Packet 472 (Src. and dest. are IPv4/IPv6). 474 Traffic Class 8-bit traffic class field. 476 Flow Label 20-bit flow label. 478 Payload Length 16-bit unsigned integer. Length of the payload, 479 i.e., the rest of the packet following 480 this IP header, in octets. (Note that any 481 extension headers [section 4] present are 482 considered part of the payload, i.e., included 483 in the length count.) 485 Next Header 8-bit selector. Identifies the type of header 486 immediately following the IP header. 488 Hop Limit 8-bit unsigned integer. Decremented by 1 by 489 each node that forwards the packet. The packet 490 is discarded if Hop Limit is decremented to 491 zero. 493 Source Address 128-bit address of the originator of the packet. 495 | 32-bit | 48-bit | 48-bit | 496 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 497 | IPv6 Address | OR | IPv4 Address | MAC | 00000......0 | 498 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 499 | 128-bit | | 128-bit | 501 Destination Address 128-bit address of the intended recipient of the 502 packet (possibly not the ultimate recipient, if 503 a Routing header is present). 505 | 32-bit | 48-bit | 48-bit | 506 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 507 | IPv6 Address | OR | IPv4 Address | MAC | 00000......0 | 508 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 509 | 128-bit | | 128-bit | 511 5. Advantages of IPmix. 513 1) Introduces an efficient way of communication between IPv6 hosts 514 and IPv4 hosts. 516 2) Allows IPv4 only hosts to exist and communicate with IPv6 only 517 hosts even after the depletion of the IPv4 address space. 519 3) Adds flexibility when making a query sent to the DNS for 520 hostname resolution as IPv4 and IPv6 hosts can communicate with 521 IPv4 or IPv6 DNS servers and the DNS can reply with any record 522 it has (either an IPv6 record Host AAAA record or an IPv4 523 record Host A record). 525 4) There is no need to think about migration as both IPv4 and IPv6 526 hosts can coexist and communicate to each other which will 527 allow the usage of the address space of both IPv4 and IPv6 528 making the available number of connected hosts be bigger. 530 5) IPmix support on "all" Internet connected hosts can be deployed 531 in a very short time by technology companies developing OSs 532 (for hosts and networking devices), and there will be no 533 dependence on enterprise users and it is just a software 534 development process in the NIC cards of all hosts to allow 535 encapsulating both IPv4 and IPv6 in the same IP packet header. 537 6) Offers the four types of communication between hosts: 539 - IPv6 hosts to IPv4 hosts (6 to 4). 541 - IPv4 hosts to IPv6 hosts (4 to 6). 543 - IPv6 hosts to IPv6 hosts (6 to 6). 545 - IPv4 hosts to IPv4 hosts (4 to 4). 547 RFC IPmix Specification September 28, 2017 548 Expires: 9-28-2018 550 Security Considerations 552 The security features of IPmix are described in the Security 553 Architecture for the Internet Protocol [RFC-2401]. 555 Acknowledgments 557 The author would like to thank S. Krishnan, W. Haddad, L. Howard,C. Huitema, 558 T. Manderson, JC. Zuniga, J. Touch, A. Sullivan, , K. Thomann, S. Bortzmeyer, 559 J. Linkova, R. Bonica and T. Herbert for the useful inputs and discussions about IPmix. 561 Author Address 563 Khaled Omar Ibrahim Omar 564 The Road 565 6th of October City, 566 Giza, Egypt 567 Passport ID no.: A19954283 569 Phone: +2 01003620284 570 E-mail: eng.khaled.omar@hotmail.com 572 References 574 [RFC-2401] Stephen E. Deering and Robert M. Hinden, "IPv6 575 Specification", RFC 2460, December 1998. 577 IANA Considerations 579 IANA must reserve version number 10 for the 4-bit Version Field 580 in the Layer 3 packet header for the IPmix packet. 582 Full Copyright Statement 584 Copyright (C) IETF (2017). All Rights Reserved. 586 This document and translations of it may be copied and furnished to 587 others, and derivative works that comment on or otherwise explain it 588 or assist in its implementation may be prepared, copied, published 589 and distributed, in whole or in part, without restriction of any 590 kind, provided that the above copyright notice and this paragraph are 591 included on all such copies and derivative works. However, this 592 document itself may not be modified in any way, such as by removing 593 the copyright notice or references, except as needed for the purpose of 594 developing Internet standards in which case the procedures for 595 copyrights defined in the Internet Standards process must be 596 followed, or as required to translate it into languages other than 597 English. 599 The limited permissions granted above are perpetual and will not be 600 revoked. 602 This document and the information contained herein is provided on 603 THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, 604 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 605 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 606 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 607 PURPOSE.