idnits 2.17.1 draft-omar-ipv10-10.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 (November 17, 2017) is 2345 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 69, but not defined ** Obsolete undefined reference: RFC 2460 (Obsoleted by RFC 8200) == Missing Reference: 'RFC-791' is mentioned on line 70, 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 raft-omar-ipv10-10 Khaled Omar 2 Internet-Draft The Road 3 Intended status: Standards Track 4 Expires: June 17, 2018 November 17, 2017 6 Internet Protocol version 10 (IPv10) 7 Specification 8 draft-omar-ipv10-10 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 June 17, 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 version 10 of the Internet Protocol (IPv10), sometimes 44 referred to as IP Mixture (IPmix). 46 Table of Contents 48 1. Introduction..................................................1 49 2. Internet Protocol version 10 (IPv10)..........................3 50 3. The Four Types of Communication...............................3. 51 3.1. IPv10: IPv6 Host to IPv4 Host...............................4 52 3.2. IPv10: IPv4 Host to IPv6 Host...............................5 53 3.3. IPv10: IPv6 Host to IPv6 Host...............................6 54 3.4. IPv10: IPv4 Host to IPv4 Host...............................7 55 4. IPv10 Packet Header Format....................................8 56 5. Advantages of IPv10...........................................8 57 6. Security Considerations.......................................9 58 7. Acknowledgments...............................................9 59 8. Author Address................................................9 60 9. References....................................................9 61 10. IANA Considerations..........................................9 62 11. Full Copyright Statement.....................................9 64 RFC IPv10 Specification November 17, 2017 66 1. Introduction 68 IP version 10 (IPv10) is a new version of the Internet Protocol, 69 designed to allow IP version 6 [RFC-2460] to communicate to 70 IP version 4 (IPv4) [RFC-791] and vice versa. 72 - Internet is the global wide network used for communication between 73 hosts connected to it. 75 - These connected hosts (PCs, servers, routers, mobile devices, etc.) 76 must have a global unique addresses to be able to communicate 77 through the Internet and these unique addresses are defined in the 78 Internet Protocol (IP). 80 - The first version of the Internet Protocol is IPv4. 82 - When IPv4 was developed in 1975, it was not expected that the number 83 of connected hosts to the Internet reach a very huge number of hosts 84 more than the IPv4 address space, also it was aimed to be used for 85 experimental purposes in the beginning. 87 - IPv4 is (32-bits) address allowing approximately 4.3 billion unique 88 IP addresses. 90 - A few years ago, with the massive increase of connected hosts to the 91 Internet, IPv4 addresses started to run out. 93 - Three short-term solutions (CIDR, Private addressing, and NAT) were 94 introduced in the mid-1990s but even with using these solutions, 95 the IPv4 address space ran out in February, 2011 as announced by 96 IANA, The announcement of depletion of the IPv4 address space by 97 the RIRs is as follows: 99 * April, 2011: APNIC announcement. 100 * September, 2012: RIPE NCC announcement. 101 * June, 2014: LACNIC announcement. 102 * September, 2015: ARIN announcement. 104 - A long term solution (IPv6) was introduced to increase the address 105 space used by the Internet Protocol and this was defined in the 106 Internet Protocol version 6 (IPv6). 108 RFC IPv10 Specification November 17, 2017 110 - IPv6 was developed in 1998 by the Internet Engineering Task Force 111 (IETF). 113 - IPv6 is (128-bits) address and can support a huge number of unique 114 IP addresses that is approximately equals to 2^128 unique addresses. 116 - So, the need for IPv6 became a vital issue to be able to support 117 the massive increase of connected hosts to the Internet after the 118 IPv4 address space exhaustion. 120 - The migration from IPv4 to IPv6 became a necessary thing, but 121 unfortunately, it would take decades for this full migration to be 122 accomplished. 124 - 19 years have passed since IPv6 was developed, but no full migration 125 happened till now and this would cause the Internet to be divided 126 into two parts, as IPv4 still dominating on the Internet traffic 127 (85% as measured by Google in April, 2017) and new Internet hosts 128 will be assigned IPv6-only addresses and be able to communicate with 129 15% only of the Internet services and apps. 131 - So, the need for solutions for the IPv4 and IPv6 coexistence became 132 an important issue in the migration process as we cannot wake up in 133 the morning and find all IPv4 hosts are migrated to be IPv6 hosts, 134 especially, as most enterprises have not do this migration for 135 creating a full IPv6 implementation. 137 - Also, the request for using IPv6 addresses in addition to the 138 existing IPv4 addresses (IPv4/IPv6 Dual Stacks) in all enterprise 139 networks have not achieve a large implementation that can make IPv6 140 the most dominated IP in the Internet as many people believe that 141 they will not have benefits from just having a larger IP address 142 bits and IPv4 satisfies their needs, also, not all enterprises 143 devices support IPv6 and also many people are afraid of the service 144 outage that can be caused due to this migration. 146 - The recent solutions for IPv4 and IPv6 coexistence are: 148 Native dual stack (IPv4 and IPv6) 149 Tunneling 150 NAT64 151 Dual-stack Lite 152 464xlat 153 MAP 154 (other technologies also exist, like lw6over4; they may have more 155 specific use cases) 157 - IPv4/IPv6 Dual Stack, allows both IPv4 and IPv6 to coexist by 158 using both IPv4 and IPv6 addresses for all hosts at the same time, 159 but this solution does not allows IPv4 hosts to communicate to 160 IPv6 hosts and vice versa. Also, after the depletion of the IPv4 161 address space, new Internet hosts will not be able to use IPv4/IPv6 162 Dual Stacks. 164 - Tunneling, allows IPv6 hosts to communicate to each other through 165 an IPv4 network, but still does not allows IPv4 hosts to communicate 166 to IPv6 hosts and vice versa. 168 - NAT-PT, allows IPv6 hosts to communicate to IPv4 hosts with only 169 using hostnames and getting DNS involved in the communication process 170 but this solution was inefficient because it does not allows 171 communication using direct IP addresses, also the need for so much 172 protocol translations of the source and destination IP addresses 173 made the solution complex and not applicable thats why it was moved 174 to the Historic status in the RFC 2766. Also, NAT64 requires so much 175 protocol translations and statically configured bindings, and also 176 getting a DNS64 involved in the communication process. 178 RFC IPv10 Specification November 17, 2017 180 2. Internet Protocol version 10 (IPv10). 182 - IPv10 is the solution presented in this Internet draft. 184 - It solves the issue of allowing IPv6 only hosts to communicate to 185 IPv4 only hosts and vice versa in a simple and very efficient way, 186 especially when the communication is done using both direct IP 187 addresses and when using hostnames between IPv10 hosts, as there 188 is no need for protocol translations or getting the DNS involved 189 in the communication process more than its normal address 190 resolution function. 192 - IPv10 allows hosts from two IP versions (IPv4 and IPv6) to be able 193 to communicate, and this can be accomplished by having an IPv10 194 packet containing a mixture of IPv4 and IPv6 addresses in the same 195 IP packet header. 197 - From here the name of IPv10 arises, as the IP packet can contain 198 (IPv6 + IPv4 /IPv4 + IPv6) addresses in the same layer 3 packet 199 header. 201 RFC IPv10 Specification November 17, 2017 203 3. The Four Types of Communication. 205 3.1) IPv10: IPv6 Host to IPv4 Host. 206 ------------------------------ 208 - IPv10 Packet: 210 |<-------- 128-bit ------>|<------------------ 128-bit ---------------->| 211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 | Data| Source IPv6 Address | Destination IPv4 Address MAC 0000..0 | 213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 |<--------- 32-bit -------->| 48-bit | 48-bit | 216 MAC ==> The sending host MAC address. 218 - The destination address is 128 bit, when the 1st 48-bits are zeros, the router 219 will know that the last 32-bit is an IPv4 address and it can start forwarding 220 the packet based on that address. 222 - The second 48-bit represents the sending host MAC address and this can be used for 223 host identification. 225 - The last 32-bit represents the destination IPv4 address. 227 - Sending IPv10 host TCP/IP Configuration: 229 IP Address: IPv6 Address 230 Prefix Length: /length 231 Default Gateway: IPv6 Address (Optional) 232 DNS Addresses: IPv6/IPv4 Address 234 - Example of IPv10 Operation: 235 --------------------------- 237 R1 & R2 have both IPv4/IPv6 routing enabled 238 IPv10 Host IPv10 Host 240 PC-1 R1 * R2 PC-2 241 +----+ * * +----+ 242 | | * * * * | | 243 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 244 +----+ 2001:1::1 * * * * 192.168.1.1 +----+ 245 / / * Network * / / 246 +----+ * * +----+ 247 * * 248 IPv6: 2001:1::10/64 * IPv4: 192.168.1.10/24 249 DG : 2001:1::1 DG : 192.168.1.1 251 | 128-bit | 128-bit | 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 |Data | 2001:1::10 | 192.168.1.10 MAC 000..0 |---> 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 Src. IPv6 Address Dest. IPv4 Address 257 IPv10: IPv6 host to IPv4 host 259 RFC IPv10 Specification November 17, 2017 261 3.2) IPv10: IPv4 Host to IPv6 Host. 262 ------------------------------ 264 - IPv10 Packet: 266 | 128-bit | 128-bit | 267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 268 | Data| Source IPv4 Address MAC 000..0 | Destination IPv6 Address | 269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 - Sending IPv10 host TCP/IP Configuration: 273 IP Address: IPv4 Address 274 Subnet Mask: /mask 275 Default Gateway: IPv4 Address 276 DNS Addresses: IPv4/IPv6 Address 278 - Example of IPv10 Operation: 279 --------------------------- 281 R1 & R2 have both IPv4/IPv6 routing enabled 282 IPv10 Host IPv10 Host 284 PC-1 R1 * R2 PC-2 285 +----+ * * +----+ 286 | | * * * * | | 287 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 288 +----+ 2001:1::1 * * * * 192.168.1.1 +----+ 289 / / * Network * / / 290 +----+ * * +----+ 291 * * 292 IPv6: 2001:1::10/64 * IPv4: 192.168.1.10/24 293 DG : 2001:1::1 DG : 192.168.1.1 295 | 128-bit | 128-bit | 296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 297 <---| 2001:1::10 | 000..0 MAC 192.168.1.10 | Data | 298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 299 Dest. IPv6 Address Src. IPv4 Address 301 IPv10: IPv4 host to IPv6 host 303 RFC IPv10 Specification November 17, 2017 305 3.3) IPv10: IPv6 Host to IPv6 Host. 306 ------------------------------ 308 - IPv10 Packet: 310 | 128-bit | 128-bit | 311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 312 | Data| Source IPv6 Address | Destination IPv6 Address | 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 - Sending IPv10 host TCP/IP Configuration: 317 IP Address: IPv6 Address 318 Prefix Length: /Length 319 Default Gateway: IPv6 Address (Optional) 320 DNS Addresses: IPv6/IPv4 Address 322 - Example of IPv10 Operation: 323 --------------------------- 325 R1 & R2 have both IPv4/IPv6 routing enabled 326 IPv10 Host IPv10 Host 328 PC-1 R1 * R2 PC-2 329 +----+ * * +----+ 330 | | * * * * | | 331 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o---------o| | 332 +----+ 2001:1::1 * * * * 3001:1::1 +----+ 333 / / * Network * / / 334 +----+ * * +----+ 335 * * 336 IPv6: 2001:1::10/64 * IPv6: 3001:1::10/64 337 DG : 2001:1::1 DG : 3001:1::1 339 | 128-bit | 128-bit | 340 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 341 |Data | 2001:1::10 | 3001:1::10 |---> 342 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 343 Src. IPv6 Address Dest. IPv6 Address 345 IPv10: IPv6 host to IPv6 host 347 RFC IPv10 Specification November 17, 2017 349 3.4) IPv10: IPv4 Host to IPv4 Host. 350 ------------------------------ 352 - IPv10 Packet: 354 | 128-bit | 128-bit | 355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 | Data| Source IPv4 Address MAC 000..0 | Destination IPv4 Address MAC 000..0 | 357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 359 - Sending IPv10 host TCP/IP Configuration: 361 IP Address: IPv4 Address 362 Subnet Mask: /Mask 363 Default Gateway: IPv4 Address 364 DNS Addresses: IPv6/IPv4 Address 366 - Example of IPv10 Operation: 367 --------------------------- 369 R1 & R2 have both IPv4/IPv6 routing enabled 370 IPv10 Host IPv10 Host 372 PC-1 R1 * R2 PC-2 373 +----+ * * +----+ 374 | | * * * * | | 375 | |o--------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 376 +----+ 10.1.1.1 * * * * 192.168.1.1 +----+ 377 / / * Network * / / 378 +----+ * * +----+ 379 * * 380 IPv4: 10.1.1.10/24 * IPv6: 192.168.1.10/24 381 DG : 10.1.1.1 DG : 192.168.1.1 383 | 128-bit | 128-bit | 384 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 385 |Data | 10.1.1.10 MAC 000..0 | 192.168.1.10 MAC 000..0 |---> 386 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 387 Src. IPv4 Address Dest. IPv4 Address 389 IPv10: IPv4 host to IPv4 host 391 Important Notes: - IPv4 and IPv6 routing must be enabled on all routers, so 392 when a router receives an IPv10 packet, it should use 393 the appropriate routing table based on the destination 394 address within the IPv10 packet. 396 - That means, if the received IPv10 packet contains an IPv4 397 address in the destination address field, the router 398 should use the IPv4 routing table to make a routing 399 decision, and if the received IPv10 packet contains an IPv6 400 address in the destination address field, the router should 401 use the IPv6 routing table to make a routing decision. 403 - All Internet connected hosts must be IPv10 hosts to be 404 able to communicate regardless the used IP version, 405 and the IPv10 deployment process can be accomplished 406 by ALL technology companies developing OSs for hosts 407 networking and security devices. 409 When the source or destination is an IPv4 address, the IPv4 address is located in 410 the last 32 bits. 412 When the source is IPv4 and the destination is IPv6, the sending host will consider 413 the destination IPv6 address as an IPv4 address not on the same subnet, meaning it 414 should send this frame to the default gateway (router). 416 Once the router receives the frame, it removes the frame header and trailer and look 417 for the destination IPv6 address, then the router start to take a routing decision by 418 checking its IPv6 routing table and start sending the packet to the next hop through 419 the IPv6 network. 421 Similarly, when the source is IPv6 and the destination is IPv4, the sending host will 422 consider the destination IPv4 address as an IPv6 address not on the same subnet, meaning 423 it should send this frame to the default gateway (router) 425 Once the router receives the frame, it removes the frame header and trailer and look for 426 the destination IPv4 address, then the router start to take a routing decision by checking 427 its IPv4 routing table and start sending the packet to the next hop through the IPv4 network. 429 S D 430 IPv4-IPv6 ---> IPv6 ---> IPv6 Network ---> IPv6 431 Sending Host Router Destination Host 433 S D 434 IPv4 <--- IPv4 Network <--- IPv4 <--- IPv6-IPv4 435 Destination Host Router Sending Host 437 RFC IPv10 Specification November 17, 2017 439 4. IPv10 Packet Header Format. 441 - The following figure shows the IPv10 packet header which is almost 442 the same as the IPv6 packet header: 444 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 445 |Version| Traffic Class | Flow Label | 446 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 447 | Payload Length | Next Header | Hop Limit | 448 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 449 | | 450 + + 451 | | 452 + Source Address + 453 | | 454 + + 455 | | 456 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 457 | | 458 + + 459 | | 460 + Destination Address + 461 | | 462 + + 463 | | 464 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 Version 4-bit Internet Protocol version number. 468 - 0100 : IPv4 Packet 469 (Src. and dest. are IPv4). 470 - 0110 : IPv6 Packet 471 (Src. and dest. are IPv6). 472 - 1010 : IPv10 Packet 473 (Src. and dest. are IPv4/IPv6). 475 Traffic Class 8-bit traffic class field. 477 Flow Label 20-bit flow label. 479 Payload Length 16-bit unsigned integer. Length of the payload, 480 i.e., the rest of the packet following 481 this IP header, in octets. (Note that any 482 extension headers [section 4] present are 483 considered part of the payload, i.e., included 484 in the length count.) 486 Next Header 8-bit selector. Identifies the type of header 487 immediately following the IP header. 489 Hop Limit 8-bit unsigned integer. Decremented by 1 by 490 each node that forwards the packet. The packet 491 is discarded if Hop Limit is decremented to 492 zero. 494 Source Address 128-bit address of the originator of the packet. 496 | 32-bit | 48-bit | 48-bit | 497 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 498 | IPv6 Address | OR | IPv4 Address | MAC | 00000......0 | 499 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 500 | 128-bit | | 128-bit | 502 Destination Address 128-bit address of the intended recipient of the 503 packet (possibly not the ultimate recipient, if 504 a Routing header is present). 506 | 32-bit | 48-bit | 48-bit | 507 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 508 | IPv6 Address | OR | IPv4 Address | MAC | 00000......0 | 509 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 510 | 128-bit | | 128-bit | 512 5. Advantages of IPv10. 514 1) Introduces an efficient way of communication between IPv6 hosts 515 and IPv4 hosts. 517 2) Allows IPv4 only hosts to exist and communicate with IPv6 only 518 hosts even after the depletion of the IPv4 address space. 520 3) Adds flexibility when making a query sent to the DNS for 521 hostname resolution as IPv4 and IPv6 hosts can communicate with 522 IPv4 or IPv6 DNS servers and the DNS can reply with any record 523 it has (either an IPv6 record Host AAAA record or an IPv4 524 record Host A record). 526 4) There is no need to think about migration as both IPv4 and IPv6 527 hosts can coexist and communicate to each other which will 528 allow the usage of the address space of both IPv4 and IPv6 529 making the available number of connected hosts be bigger. 531 5) IPv10 support on "all" Internet connected hosts can be deployed 532 in a very short time by technology companies developing OSs 533 (for hosts and networking devices, and there will be no 534 dependence on enterprise users and it is just a software 535 development process in the NIC cards of all hosts to allow 536 encapsulating both IPv4 and IPv6 in the same IP packet header. 538 6) Offers the four types of communication between hosts: 540 - IPv6 hosts to IPv4 hosts (6 to 4). 542 - IPv4 hosts to IPv6 hosts (4 to 6). 544 - IPv6 hosts to IPv6 hosts (6 to 6). 546 - IPv4 hosts to IPv4 hosts (4 to 4). 548 RFC IPv10 Specification November 17, 2017 549 Expires: 5-17-2018 551 Security Considerations 553 The security features of IPv10 are described in the Security 554 Architecture for the Internet Protocol [RFC-2401]. 556 Acknowledgments 558 The author would like to thank S. Krishnan, W. Haddad, L. Howard,C. Huitema, 559 T. Manderson, JC. Zuniga, A. Sullivan, , K. Thomann, S. Bortzmeyer, J. Linkova, 560 and T. Herbert for the useful inputs and discussions about IPv10. 562 Author Address 564 Khaled Omar Ibrahim Omar 565 The Road 566 6th of October City, 567 Giza, Egypt 568 Passport ID no.: A19954283 570 Phone: +2 01003620284 571 E-mail: eng.khaled.omar@hotmail.com 573 References 575 [RFC-2401] Stephen E. Deering and Robert M. Hinden, "IPv6 576 Specification", RFC 2460, December 1998. 578 IANA Considerations 580 IANA must reserve version number 10 for the 4-bit Version Field 581 in the Layer 3 packet header for the IPv10 packet. 583 Full Copyright Statement 585 Copyright (C) IETF (2017). All Rights Reserved. 587 This document and translations of it may be copied and furnished to 588 others, and derivative works that comment on or otherwise explain it 589 or assist in its implementation may be prepared, copied, published 590 and distributed, in whole or in part, without restriction of any 591 kind, provided that the above copyright notice and this paragraph are 592 included on all such copies and derivative works. However, this 593 document itself may not be modified in any way, such as by removing 594 the copyright notice or references, except as needed for the purpose of 595 developing Internet standards in which case the procedures for 596 copyrights defined in the Internet Standards process must be 597 followed, or as required to translate it into languages other than 598 English. 600 The limited permissions granted above are perpetual and will not be 601 revoked. 603 This document and the information contained herein is provided on 604 THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, 605 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 606 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 607 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 608 PURPOSE.