idnits 2.17.1 draft-omar-ipv10-06.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 52 instances of too long lines in the document, the longest one being 20 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 2, 2017) is 2428 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 draft-omar-ipv10-06 Khaled Omar 2 Internet-Draft The Road 3 Intended status: Standards Track 4 Expires: March 2, 2018 September 2, 2017 6 Internet Protocol version 10 (IPv10) 7 Specification 8 draft-omar-ipv10-06 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 2, 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 September 2, 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 September 2, 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 Dual-stack Lite 150 NAT64 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 IPv10 Specification September 2, 2017 179 2. Internet Protocol version 10 (IPv10). 181 - IPv10 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 IPv10 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 - IPv10 allows hosts from two IP versions (IPv4 and IPv6) to be able 192 to communicate, and this can be accomplished by having an IPv10 193 packet containing a mixture of IPv4 and IPv6 addresses in the same 194 IP packet header. 196 - From here the name of IPv10 arises, as the IP packet can contain 197 (IPv6 + IPv4 /IPv4 + IPv6) addresses in the same layer 3 packet 198 header. 200 RFC IPv10 Specification September 2, 2017 202 3. The Four Types of Communication. 204 3.1) IPv10: IPv6 Host to IPv4 Host. 205 ------------------------------ 207 - IPv10 Packet: 209 | 128-bit | 128-bit | 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 211 | Data| Source IPv6 Address | 0000..0 ASN MAC Destination IPv4 Address | 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 - Sending IPv10 host TCP/IP Configuration: 216 IP Address: IPv6 Address 217 Prefix Length: /length 218 Default Gateway: IPv6 Address (Optional) 219 DNS Addresses: IPv6/IPv4 Address 221 - Example of IPv10 Operation: 222 --------------------------- 224 R1 & R2 have both IPv4/IPv6 routing enabled 225 IPv10 Host IPv10 Host 227 PC-1 R1 * R2 PC-2 228 +----+ * * +----+ 229 | | * * * * | | 230 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 231 +----+ 2001:1::1 * * * * 192.168.1.1 +----+ 232 / / * Network * / / 233 +----+ * * +----+ 234 * * 235 IPv6: 2001:1::10/64 * IPv4: 192.168.1.10/24 236 DG : 2001:1::1 DG : 192.168.1.1 238 | 128-bit | 128-bit | 239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 240 |Data | 2001:1::10 | 000..0 ASN MAC 192.168.1.10 |---> 241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 242 Src. IPv6 Address Dest. IPv4 Address 244 IPv10: IPv6 host to IPv4 host 246 RFC IPv10 Specification September 2, 2017 248 3.2) IPv10: IPv4 Host to IPv6 Host. 249 ------------------------------ 251 - IPv10 Packet: 253 | 128-bit | 128-bit | 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 | Data| 000..0 ASN MAC Source IPv4 Address | Destination IPv6 Address | 256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 258 - Sending IPv10 host TCP/IP Configuration: 260 IP Address: IPv4 Address 261 Subnet Mask: /mask 262 Default Gateway: IPv4 Address 263 DNS Addresses: IPv4/IPv6 Address 265 - Example of IPv10 Operation: 266 --------------------------- 268 R1 & R2 have both IPv4/IPv6 routing enabled 269 IPv10 Host IPv10 Host 271 PC-1 R1 * R2 PC-2 272 +----+ * * +----+ 273 | | * * * * | | 274 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 275 +----+ 2001:1::1 * * * * 192.168.1.1 +----+ 276 / / * Network * / / 277 +----+ * * +----+ 278 * * 279 IPv6: 2001:1::10/64 * IPv4: 192.168.1.10/24 280 DG : 2001:1::1 DG : 192.168.1.1 282 | 128-bit | 128-bit | 283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 284 <---| 2001:1::10 | 000..0 ASN MAC 192.168.1.10 | Data| 285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 286 Dest. IPv6 Address Src. IPv4 Address 288 IPv10: IPv4 host to IPv6 host 290 RFC IPv10 Specification September 2, 2017 292 3.3) IPv10: IPv6 Host to IPv6 Host. 293 ------------------------------ 295 - IPv10 Packet: 297 | 128-bit | 128-bit | 298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 299 | Data| Source IPv6 Address | Destination IPv6 Address | 300 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 302 - Sending IPv10 host TCP/IP Configuration: 304 IP Address: IPv6 Address 305 Prefix Length: /Length 306 Default Gateway: IPv6 Address (Optional) 307 DNS Addresses: IPv6/IPv4 Address 309 - Example of IPv10 Operation: 310 --------------------------- 312 R1 & R2 have both IPv4/IPv6 routing enabled 313 IPv10 Host IPv10 Host 315 PC-1 R1 * R2 PC-2 316 +----+ * * +----+ 317 | | * * * * | | 318 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o---------o| | 319 +----+ 2001:1::1 * * * * 3001:1::1 +----+ 320 / / * Network * / / 321 +----+ * * +----+ 322 * * 323 IPv6: 2001:1::10/64 * IPv6: 3001:1::10/64 324 DG : 2001:1::1 DG : 3001:1::1 326 | 128-bit | 128-bit | 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 328 |Data | 2001:1::10 | 3001:1::10 |---> 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 Src. IPv6 Address Dest. IPv6 Address 332 IPv10: IPv6 host to IPv6 host 334 RFC IPv10 Specification September 2, 2017 336 3.4) IPv10: IPv4 Host to IPv4 Host. 337 ------------------------------ 339 - IPv10 Packet: 341 | 128-bit | 128-bit | 342 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 343 | Data| 000..0 ASN MAC Source IPv4 Address | 000..0 ASN MAC Destination IPv4 Address | 344 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 346 - Sending IPv10 host TCP/IP Configuration: 348 IP Address: IPv4 Address 349 Subnet Mask: /Mask 350 Default Gateway: IPv4 Address 351 DNS Addresses: IPv6/IPv4 Address 353 - Example of IPv10 Operation: 354 --------------------------- 356 R1 & R2 have both IPv4/IPv6 routing enabled 357 IPv10 Host IPv10 Host 359 PC-1 R1 * R2 PC-2 360 +----+ * * +----+ 361 | | * * * * | | 362 | |o--------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 363 +----+ 10.1.1.1 * * * * 192.168.1.1 +----+ 364 / / * Network * / / 365 +----+ * * +----+ 366 * * 367 IPv4: 10.1.1.10/24 * IPv6: 192.168.1.10/24 368 DG : 10.1.1.1 DG : 192.168.1.1 370 | 128-bit | 128-bit | 371 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 372 |Data | 000..0 ASN MAC 10.1.1.10 | 000..0 ASN MAC 192.168.1.10 |---> 373 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 374 Src. IPv4 Address Dest. IPv4 Address 376 IPv10: IPv4 host to IPv4 host 378 Important Notes: - IPv4 and IPv6 routing must be enabled on all routers, so 379 when a router receives an IPv10 packet, it should use 380 the appropriate routing table based on the destination 381 address within the IPv10 packet. 383 - That means, if the received IPv10 packet contains an IPv4 384 address in the destination address field, the router 385 should use the IPv4 routing table to make a routing 386 decision, and if the received IPv10 packet contains an IPv6 387 address in the destination address field, the router should 388 use the IPv6 routing table to make a routing decision. 390 - All Internet connected hosts must be IPv10 hosts to be 391 able to communicate regardless the used IP version, 392 and the IPv10 deployment process can be accomplished 393 by ALL technology companies developing OSs for hosts 394 networking and security devices. 396 RFC IPv10 Specification September 2, 2017 398 4. IPv10 Packet Header Format. 400 - The following figure shows the IPv10 packet header which is almost 401 the same as the IPv6 packet header: 403 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 404 |Version| Traffic Class | Flow Label | 405 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 406 | Payload Length | Next Header | Hop Limit | 407 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 408 | | 409 + + 410 | | 411 + Source Address + 412 | | 413 + + 414 | | 415 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 416 | | 417 + + 418 | | 419 + Destination Address + 420 | | 421 + + 422 | | 423 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 Version 4-bit Internet Protocol version number. 427 - 0100 : IPv4 Packet 428 (Src. and dest. are IPv4). 429 - 0110 : IPv6 Packet 430 (Src. and dest. are IPv6). 431 - 1010 : IPv10 Packet 432 (Src. and dest. are IPv4/IPv6). 434 Traffic Class 8-bit traffic class field. 436 Flow Label 20-bit flow label. 438 Payload Length 16-bit unsigned integer. Length of the payload, 439 i.e., the rest of the packet following 440 this IP header, in octets. (Note that any 441 extension headers [section 4] present are 442 considered part of the payload, i.e., included 443 in the length count.) 445 Next Header 8-bit selector. Identifies the type of header 446 immediately following the IP header. 448 Hop Limit 8-bit unsigned integer. Decremented by 1 by 449 each node that forwards the packet. The packet 450 is discarded if Hop Limit is decremented to 451 zero. 453 Source Address 128-bit address of the originator of the packet. 455 | 32-bit | 16-bit | 48-bit | 32-bit | 456 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 457 | IPv6 Address | OR | 00000......0 | ASN | MAC | IPv4 Address | 458 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 459 | 128-bit | | 128-bit | 461 Destination Address 128-bit address of the intended recipient of the 462 packet (possibly not the ultimate recipient, if 463 a Routing header is present). 465 | 32-bit | 16-bit | 48-bit | 32-bit | 466 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 467 | IPv6 Address | OR | 00000......0 | ASN | MAC | IPv4 Address | 468 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 469 | 128-bit | | 128-bit | 471 5. Advantages of IPv10. 473 1) Introduces an efficient way of communication between IPv6 hosts 474 and IPv4 hosts. 476 2) Allows IPv4 only hosts to exist and communicate with IPv6 only 477 hosts even after the depletion of the IPv4 address space. 479 3) Adds flexibility when making a query sent to the DNS for 480 hostname resolution as IPv4 and IPv6 hosts can communicate with 481 IPv4 or IPv6 DNS servers and the DNS can reply with any record 482 it has (either an IPv6 record Host AAAA record or an IPv4 483 record Host A record). 485 4) There is no need to think about migration as both IPv4 and IPv6 486 hosts can coexist and communicate to each other which will 487 allow the usage of the address space of both IPv4 and IPv6 488 making the available number of connected hosts be bigger. 490 5) IPv10 support on "all" Internet connected hosts can be deployed 491 in a very short time by technology companies developing OSs 492 (for hosts and networking devices, and there will be no 493 dependence on enterprise users and it is just a software 494 development process in the NIC cards of all hosts to allow 495 encapsulating both IPv4 and IPv6 in the same IP packet header. 497 6) Offers the four types of communication between hosts: 499 - IPv6 hosts to IPv4 hosts (6 to 4). 501 - IPv4 hosts to IPv6 hosts (4 to 6). 503 - IPv6 hosts to IPv6 hosts (6 to 6). 505 - IPv4 hosts to IPv4 hosts (4 to 4). 507 RFC IPv10 Specification September 2, 2017 508 Expires: 2-3-2018 510 Security Considerations 512 The security features of IPv10 are described in the Security 513 Architecture for the Internet Protocol [RFC-2401]. 515 Acknowledgments 517 The author would like to thank S. Krishnan, W. Haddad, C. Huitema, 518 T. Manderson, JC. Zuniga, A. Sullivan, , K. Thomann, M. Abrahamsson, 519 S. Bortzmeyer, J. Linkova, T. Herbert and Lee H. for the useful inputs and 520 discussions about IPv10. 522 Author Address 524 Khaled Omar Ibrahim Omar 525 The Road 526 6th of October City, 527 Giza, Egypt 528 Passport ID no.: A19954283 530 Phone: +2 01003620284 531 E-mail: eng.khaled.omar@hotmail.com 533 References 535 [RFC-2401] Stephen E. Deering and Robert M. Hinden, "IPv6 536 Specification", RFC 2460, December 1998. 538 IANA Considerations 540 IANA must reserve version number 10 for the 4-bit Version Field 541 in the Layer 3 packet header for the IPv10 packet. 543 Full Copyright Statement 545 Copyright (C) IETF (2017). All Rights Reserved. 547 This document and translations of it may be copied and furnished to 548 others, and derivative works that comment on or otherwise explain it 549 or assist in its implementation may be prepared, copied, published 550 and distributed, in whole or in part, without restriction of any 551 kind, provided that the above copyright notice and this paragraph are 552 included on all such copies and derivative works. However, this 553 document itself may not be modified in any way, such as by removing 554 the copyright notice or references, except as needed for the purpose of 555 developing Internet standards in which case the procedures for 556 copyrights defined in the Internet Standards process must be 557 followed, or as required to translate it into languages other than 558 English. 560 The limited permissions granted above are perpetual and will not be 561 revoked. 563 This document and the information contained herein is provided on 564 THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, 565 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 566 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 567 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 568 PURPOSE.