idnits 2.17.1 draft-omar-ipv10-05.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 8 longer pages, the longest (page 9) being 98 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 (June 28, 2017) is 2466 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-ipv10-05 Khaled Omar 2 Internet-Draft The Road 3 Intended status: Standards Track 4 Expires: December 28, 2017 June 28, 2017 6 Internet Protocol version 10 (IPv10) 7 Specification 8 draft-omar-ipv10-05 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 December 28, 2017. 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 advantages of Using IPv10.................................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. Security Considerations.......................................9 57 6. Acknowledgments...............................................9 58 7. Author Address................................................9 59 8. References....................................................9 60 9. IANA Considerations...........................................9 61 10. Full Copyright Statement.....................................9 63 RFC IPv10 Specification June 28, 2017 65 1. Introduction 67 IP version 10 (IPv10) 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 IPv10 Specification June 28, 2017 109 - IPv6 was developed in 1998 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 - 19 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 did 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 did 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 * IPv4/IPv6 Dual Stacks. 148 * Tunneling. 149 * NAT-PT and NAT64. 151 - The first solution: (IPv4/IPv6 Dual Stacks), allows both IPv4 and 152 IPv6 to coexist by using both IPv4 and IPv6 addresses for 153 all hosts at the same time, but this solution does not allows 154 IPv4 hosts to communicate to IPv6 hosts and vice versa. Also, after 155 the depletion of the IPv4 address space, new Internet hosts will 156 not be able to use IPv4/IPv6 Dual Stacks. 158 - The second solution: (Tunneling), allows IPv6 hosts to communicate 159 to each other through an IPv4 network, but still does not allows 160 IPv4 hosts to communicate to IPv6 hosts and vice versa. 162 - The third solution: (NAT-PT), allows IPv6 hosts to communicate to 163 IPv4 hosts with only using hostnames and getting DNS involved in 164 the communication process but this solution was inefficient because 165 it does not allows communication using direct IP addresses, also 166 the need for so much protocol translations of the source and 167 destination IP addresses made the solution complex and not 168 applicable thats why it was moved to the Historic status in the 169 RFC 2766. 170 Also, NAT64 requires so much protocol translations and statically 171 configured bindings, and also getting a DNS64 involved in the 172 communication process. 174 RFC IPv10 Specification June 28, 2017 176 2. Internet Protocol version 10 (IPv10). 178 - IPv10 is the solution presented in this Internet draft. 180 - It solves the issue of allowing IPv6 only hosts to communicate to 181 IPv4 only hosts and vice versa in a simple and very efficient way, 182 especially when the communication is done using both direct IP 183 addresses and when using hostnames between IPv10 hosts, as there 184 is no need for protocol translations or getting the DNS involved 185 in the communication process more than its normal address 186 resolution function. 188 - IPv10 allows hosts from two IP versions (IPv4 and IPv6) to be able 189 to communicate, and this can be accomplished by having an IPv10 190 packet containing a mixture of IPv4 and IPv6 addresses in the same 191 IP packet header. 193 - From here the name of IPv10 arises, as the IP packet can contain 194 (IPv6 + IPv4 /IPv4 + IPv6) addresses in the same layer 3 packet 195 header. 197 3. Advantages of Using IPv10. 199 1) Introduces an efficient way of communication between IPv6 hosts 200 and IPv4 hosts. 202 2) Allows IPv4 only hosts to exist and communicate with IPv6 only 203 hosts even after the depletion of the IPv4 address space. 205 3) Adds flexibility when making a query sent to the DNS for 206 hostname resolution as IPv4 and IPv6 hosts can communicate with 207 IPv4 or IPv6 DNS servers and the DNS can reply with any record 208 it has (either an IPv6 record Host AAAA record or an IPv4 209 record Host A record). 211 4) There is no need to think about migration as both IPv4 and IPv6 212 hosts can coexist and communicate to each other which will 213 allow the usage of the address space of both IPv4 and IPv6 214 making the available number of connected hosts be bigger. 216 5) IPv10 support on "all" Internet connected hosts can be deployed 217 in a very short time by technology companies developing OSs 218 (for hosts and networking devices, and there will be no 219 dependence on enterprise users and it is just a software 220 development process in the NIC cards of all hosts to allow 221 encapsulating both IPv4 and IPv6 in the same IP packet header. 223 6) Offers the four types of communication between hosts: 225 - IPv6 hosts to IPv4 hosts (6 to 4). 227 - IPv4 hosts to IPv6 hosts (4 to 6). 229 - IPv6 hosts to IPv6 hosts (6 to 6). 231 - IPv4 hosts to IPv4 hosts (4 to 4). 233 RFC IPv10 Specification June 28, 2017 235 3.1) IPv10: IPv6 Host to IPv4 Host. 236 ------------------------------ 238 - IPv10 Packet: 240 | 128-bit | 128-bit | 241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 242 | Data| Source IPv6 Address | 0000..0 ASN MAC Destination IPv4 Address | 243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 245 - Sending IPv10 host TCP/IP Configuration: 247 IP Address: IPv6 Address 248 Prefix Length: /length 249 Default Gateway: IPv6 Address (Optional) 250 DNS Addresses: IPv6/IPv4 Address 252 - Example of IPv10 Operation: 253 --------------------------- 255 R1 & R2 have both IPv4/IPv6 routing enabled 256 IPv10 Host IPv10 Host 258 PC-1 R1 * R2 PC-2 259 +----+ * * +----+ 260 | | * * * * | | 261 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 262 +----+ 2001:1::1 * * * * 192.168.1.1 +----+ 263 / / * Network * / / 264 +----+ * * +----+ 265 * * 266 IPv6: 2001:1::10/64 * IPv4: 192.168.1.10/24 267 DG : 2001:1::1 DG : 192.168.1.1 269 | 128-bit | 128-bit | 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 |Data | 2001:1::10 | 000..0 ASN MAC 192.168.1.10 |---> 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 Src. IPv6 Address Dest. IPv4 Address 275 IPv10: IPv6 host to IPv4 host 277 RFC IPv10 Specification June 28, 2017 279 3.2) IPv10: IPv4 Host to IPv6 Host. 280 ------------------------------ 282 - IPv10 Packet: 284 | 128-bit | 128-bit | 285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 286 | Data| 000..0 ASN MAC Source IPv4 Address | Destination IPv6 Address | 287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 - Sending IPv10 host TCP/IP Configuration: 291 IP Address: IPv4 Address 292 Subnet Mask: /mask 293 Default Gateway: IPv4 Address 294 DNS Addresses: IPv4/IPv6 Address 296 - Example of IPv10 Operation: 297 --------------------------- 299 R1 & R2 have both IPv4/IPv6 routing enabled 300 IPv10 Host IPv10 Host 302 PC-1 R1 * R2 PC-2 303 +----+ * * +----+ 304 | | * * * * | | 305 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 306 +----+ 2001:1::1 * * * * 192.168.1.1 +----+ 307 / / * Network * / / 308 +----+ * * +----+ 309 * * 310 IPv6: 2001:1::10/64 * IPv4: 192.168.1.10/24 311 DG : 2001:1::1 DG : 192.168.1.1 313 | 128-bit | 128-bit | 314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 <---| 2001:1::10 | 000..0 ASN MAC 192.168.1.10 | Data| 316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 317 Dest. IPv6 Address Src. IPv4 Address 319 IPv10: IPv4 host to IPv6 host 321 RFC IPv10 Specification June 28, 2017 323 3.3) IPv10: IPv6 Host to IPv6 Host. 324 ------------------------------ 326 - IPv10 Packet: 328 | 128-bit | 128-bit | 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 | Data| Source IPv6 Address | Destination IPv6 Address | 331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 333 - Sending IPv10 host TCP/IP Configuration: 335 IP Address: IPv6 Address 336 Prefix Length: /Length 337 Default Gateway: IPv6 Address (Optional) 338 DNS Addresses: IPv6/IPv4 Address 340 - Example of IPv10 Operation: 341 --------------------------- 343 R1 & R2 have both IPv4/IPv6 routing enabled 344 IPv10 Host IPv10 Host 346 PC-1 R1 * R2 PC-2 347 +----+ * * +----+ 348 | | * * * * | | 349 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o---------o| | 350 +----+ 2001:1::1 * * * * 3001:1::1 +----+ 351 / / * Network * / / 352 +----+ * * +----+ 353 * * 354 IPv6: 2001:1::10/64 * IPv6: 3001:1::10/64 355 DG : 2001:1::1 DG : 3001:1::1 357 | 128-bit | 128-bit | 358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 359 |Data | 2001:1::10 | 3001:1::10 |---> 360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 Src. IPv6 Address Dest. IPv6 Address 363 IPv10: IPv6 host to IPv6 host 365 RFC IPv10 Specification June 28, 2017 367 3.4) IPv10: IPv4 Host to IPv4 Host. 368 ------------------------------ 370 - IPv10 Packet: 372 | 128-bit | 128-bit | 373 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 374 | Data| 000..0 ASN MAC Source IPv4 Address | 000..0 ASN MAC Destination IPv4 Address | 375 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 377 - Sending IPv10 host TCP/IP Configuration: 379 IP Address: IPv4 Address 380 Subnet Mask: /Mask 381 Default Gateway: IPv4 Address 382 DNS Addresses: IPv6/IPv4 Address 384 - Example of IPv10 Operation: 385 --------------------------- 387 R1 & R2 have both IPv4/IPv6 routing enabled 388 IPv10 Host IPv10 Host 390 PC-1 R1 * R2 PC-2 391 +----+ * * +----+ 392 | | * * * * | | 393 | |o--------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 394 +----+ 10.1.1.1 * * * * 192.168.1.1 +----+ 395 / / * Network * / / 396 +----+ * * +----+ 397 * * 398 IPv4: 10.1.1.10/24 * IPv6: 192.168.1.10/24 399 DG : 10.1.1.1 DG : 192.168.1.1 401 | 128-bit | 128-bit | 402 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 403 |Data | 000..0 ASN MAC 10.1.1.10 | 000..0 ASN MAC 192.168.1.10 |---> 404 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 405 Src. IPv4 Address Dest. IPv4 Address 407 IPv10: IPv4 host to IPv4 host 409 Important Notes: - IPv4 and IPv6 routing must be enabled on all routers, so 410 when a router receives an IPv10 packet, it should use 411 the appropriate routing table based on the destination 412 address within the IPv10 packet. 414 - That means, if the received IPv10 packet contains an IPv4 415 address in the destination address field, the router 416 should use the IPv4 routing table to make a routing 417 decision, and if the received IPv10 packet contains an IPv6 418 address in the destination address field, the router should 419 use the IPv6 routing table to make a routing decision. 421 - All Internet connected hosts must be IPv10 hosts to be 422 able to communicate regardless the used IP version, 423 and the IPv10 deployment process can be accomplished 424 by ALL technology companies developing OSs for hosts 425 networking and security devices. 427 RFC IPv10 Specification June 28, 2017 429 4. IPv10 Packet Header Format. 431 - The following figure shows the IPv10 packet header which is almost 432 the same as the IPv6 packet header: 434 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 435 |Version| Traffic Class | Flow Label | 436 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 437 | Payload Length | Next Header | Hop Limit | 438 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 439 | | 440 + + 441 | | 442 + Source Address + 443 | | 444 + + 445 | | 446 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 447 | | 448 + + 449 | | 450 + Destination Address + 451 | | 452 + + 453 | | 454 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 456 Version 4-bit Internet Protocol version number. 458 - 0100 : IPv4 Packet 459 (Src. and dest. are IPv4). 460 - 0110 : IPv6 Packet 461 (Src. and dest. are IPv6). 462 - 1010 : IPv10 Packet 463 (Src. and dest. are IPv4/IPv6). 465 Traffic Class 8-bit traffic class field. 467 Flow Label 20-bit flow label. 469 Payload Length 16-bit unsigned integer. Length of the payload, 470 i.e., the rest of the packet following 471 this IP header, in octets. (Note that any 472 extension headers [section 4] present are 473 considered part of the payload, i.e., included 474 in the length count.) 476 Next Header 8-bit selector. Identifies the type of header 477 immediately following the IP header. 479 Hop Limit 8-bit unsigned integer. Decremented by 1 by 480 each node that forwards the packet. The packet 481 is discarded if Hop Limit is decremented to 482 zero. 484 Source Address 128-bit address of the originator of the packet. 486 | 32-bit | 16-bit | 48-bit | 32-bit | 487 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 488 | IPv6 Address | OR | 00000......0 | ASN | MAC | IPv4 Address | 489 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 490 | 128-bit | | 128-bit | 492 Destination Address 128-bit address of the intended recipient of the 493 packet (possibly not the ultimate recipient, if 494 a Routing header is present). 496 | 32-bit | 16-bit | 48-bit | 32-bit | 497 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 498 | IPv6 Address | OR | 00000......0 | ASN | MAC | IPv4 Address | 499 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 500 | 128-bit | | 128-bit | 502 RFC IPv10 Specification June 28, 2017 503 Expires: 28-12-2017 505 Security Considerations 507 The security features of IPv10 are described in the Security 508 Architecture for the Internet Protocol [RFC-2401]. 510 Acknowledgments 512 The author would like to thank S. Krishnan, W. Haddad, C. Huitema, 513 T. Manderson, JC. Zuniga, A. Sullivan, Lee H., K. Thomann, M. Abrahamsson, 514 S. Bortzmeyer, J. Linkova, and T. Herbert for the useful inputs and 515 discussions about IPv10. 517 Author Address 519 Khaled Omar Ibrahim Omar 520 The Road 521 6th of October City, 522 Giza, Egypt 523 Passport ID no.: A19954283 525 Phone: +2 01003620284 526 E-mail: eng.khaled.omar@hotmail.com 528 References 530 [RFC-2401] Stephen E. Deering and Robert M. Hinden, "IPv6 531 Specification", RFC 2460, December 1998. 533 IANA Considerations 535 IANA must reserve version number 10 for the 4-bit Version Field 536 in the Layer 3 packet header for the IPv10 packet. 538 Full Copyright Statement 540 Copyright (C) IETF (2017). All Rights Reserved. 542 This document and translations of it may be copied and furnished to 543 others, and derivative works that comment on or otherwise explain it 544 or assist in its implementation may be prepared, copied, published 545 and distributed, in whole or in part, without restriction of any 546 kind, provided that the above copyright notice and this paragraph are 547 included on all such copies and derivative works. However, this 548 document itself may not be modified in any way, such as by removing 549 the copyright notice or references, except as needed for the purpose of 550 developing Internet standards in which case the procedures for 551 copyrights defined in the Internet Standards process must be 552 followed, or as required to translate it into languages other than 553 English. 555 The limited permissions granted above are perpetual and will not be 556 revoked. 558 This document and the information contained herein is provided on 559 THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, 560 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 561 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 562 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 563 PURPOSE.