idnits 2.17.1 draft-omar-ipv10-03.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 an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 23 instances of too long lines in the document, the longest one being 8 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 5 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 (April 17, 2017) is 2566 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 66, but not defined ** Obsolete undefined reference: RFC 2460 (Obsoleted by RFC 8200) == Missing Reference: 'RFC-791' is mentioned on line 67, but not defined ** Obsolete normative reference: RFC 2460 (ref. 'RFC-2401') (Obsoleted by RFC 8200) Summary: 6 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-03 Khaled Omar 2 Internet-Draft The Road 3 Intended status: Standards Track 4 Expires: October 17, 2017 April 17, 2017 6 Internet Protocol version 10 (IPv10) 7 Specification 8 draft-omar-ipv10-03 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 October 17, 2017. 27 Copyright Notice 29 Copyright (c) 2016 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). 45 Table of Contents 47 1. Introduction..................................................1 48 2. Internet Protocol version 10 (IPv10)..........................3 49 3. The advantages of Using IPv10.................................3 50 3.1. IPv10: IPv6 Host to IPv4 Host...............................4 51 3.2. IPv10: IPv4 Host to IPv6 Host...............................5 52 3.3. IPv10: IPv6 Host to IPv6 Host...............................6 53 3.4. IPv10: IPv4 Host to IPv4 Host...............................7 54 4. IPv10 Packet Header Format....................................8 55 5. Security Considerations.......................................9 56 6. Acknowledgments...............................................9 57 7. Author Address................................................9 58 8. References....................................................9 59 9. Full Copyright Statement......................................9 61 RFC IPv10 Specification April 17, 2017 63 1. Introduction 65 IP version 10 (IPv10) is a new version of the Internet Protocol, 66 designed to allow IP version 6 [RFC-2460] to communicate to 67 IP version 4 (IPv4) [RFC-791] and vice versa. 69 - Internet is the global wide network used for communication between 70 hosts connected to it. 72 - These connected hosts (PCs, servers, routers, mobile devices, etc.) 73 must have a global unique addresses to be able to communicate 74 through the Internet and these unique addresses are defined in the 75 Internet Protocol (IP). 77 - The first version of the Internet Protocol is IPv4. 79 - When IPv4 was developed in 1975, it was not expected that the number 80 of connected hosts to the Internet reach a very huge number of hosts 81 more than the IPv4 address space, also it was aimed to be used for 82 experimental purposes in the beginning. 84 - IPv4 is (32-bits) address allowing approximately 4.3 billion unique 85 IP addresses. 87 - A few years ago, with the massive increase of connected hosts to the 88 Internet, IPv4 addresses started to run out. 90 - Three short-term solutions (CIDR, Private addressing, and NAT) were 91 introduced in the mid-1990s but even with using these solutions, 92 the IPv4 address space ran out in February, 2011 as announced by 93 IANA, The announcement of depletion of the IPv4 address space by 94 the RIRs is as follows: 96 * April, 2011: APNIC announcement. 97 * September, 2012: RIPE NCC announcement. 98 * June, 2014: LACNIC announcement. 99 * September, 2015: ARIN announcement. 101 - A long term solution (IPv6) was introduced to increase the address 102 space used by the Internet Protocol and this was defined in the 103 Internet Protocol version 6 (IPv6). 105 RFC IPv10 Specification April 17, 2017 107 - IPv6 was developed in 1998 by the Internet Engineering Task Force 108 (IETF). 110 - IPv6 is (128-bits) address and can support a huge number of unique 111 IP addresses that is approximately equals to 2^128 unique addresses. 113 - So, the need for IPv6 became a vital issue to be able to support 114 the massive increase of connected hosts to the Internet after the 115 IPv4 address space exhaustion. 117 - The migration from IPv4 to IPv6 became a necessary thing, but 118 unfortunately, it would take decades for this full migration to be 119 accomplished. 121 - 19 years have passed since IPv6 was developed, but no full migration 122 happened till now and this would cause the Internet to be divided 123 into two parts, as IPv4 still dominating on the Internet traffic 124 (85% as measured by Google in April, 2017) and new Internet hosts 125 will be assigned IPv6-only addresses and be able to communicate with 126 15% only of the Internet services and apps. 128 - So, the need for solutions for the IPv4 and IPv6 coexistence became 129 an important issue in the migration process as we cannot wake up in 130 the morning and find all IPv4 hosts are migrated to be IPv6 hosts, 131 especially, as most enterprises did not do this migration for 132 creating a full IPv6 implementation. 134 - Also, the request for using IPv6 addresses in addition to the 135 existing IPv4 addresses (IPv4/IPv6 Dual Stacks) in all enterprise 136 networks did not achieve a large implementation that can make IPv6 137 the most dominated IP in the Internet as many people believe that 138 they will not have benefits from just having a larger IP address 139 bits and IPv4 satisfies their needs, also, not all enterprises 140 devices support IPv6 and also many people are afraid of the service 141 outage that can be caused due to this migration. 143 - The recent solutions for IPv4 and IPv6 coexistence are: 145 * IPv4/IPv6 Dual Stacks. 146 * Tunneling. 147 * NAT-PT and NAT64. 149 - The first solution: (IPv4/IPv6 Dual Stacks), allows both IPv4 and 150 IPv6 to coexist by using both IPv4 and IPv6 addresses for 151 all hosts at the same time, but this solution does not allows 152 IPv4 hosts to communicate to IPv6 hosts and vice versa. Also, after 153 the depletion of the IPv4 address space, new Internet hosts will 154 not be able to use IPv4/IPv6 Dual Stacks. 156 - The second solution: (Tunneling), allows IPv6 hosts to communicate 157 to each other through an IPv4 network, but still does not allows 158 IPv4 hosts to communicate to IPv6 hosts and vice versa. 160 - The third solution: (NAT-PT), allows IPv6 hosts to communicate to 161 IPv4 hosts with only using hostnames and getting DNS involved in 162 the communication process but this solution was inefficient because 163 it does not allows communication using direct IP addresses, also 164 the need for so much protocol translations of the source and 165 destination IP addresses made the solution complex and not 166 applicable thats why it was moved to the Historic status in the 167 RFC 2766. 168 Also, NAT64 requires so much protocol translations and statically 169 configured bindings, and also getting a DNS64 involved in the 170 communication process. 172 RFC IPv10 Specification April 17, 2017 174 2. Internet Protocol version 10 (IPv10). 176 - IPv10 is the solution presented in this Internet draft. 178 - It solves the issue of allowing IPv6 only hosts to communicate to 179 IPv4 only hosts and vice versa in a simple and very efficient way, 180 especially when the communication is done using both direct IP 181 addresses and when using hostnames between IPv10 hosts, as there 182 is no need for protocol translations or getting the DNS involved 183 in the communication process more than its normal address 184 resolution function. 186 - IPv10 allows hosts from two IP versions (IPv4 and IPv6) to be able 187 to communicate, and this can be accomplished by having an IPv10 188 packet containing a mixture of IPv4 and IPv6 addresses in the same 189 IP packet header. 191 - From here the name of IPv10 arises, as the IP packet can contain 192 (IPv6 + IPv4 /IPv4 + IPv6) addresses in the same layer 3 packet 193 header. 195 3. Advantages of Using IPv10. 197 1) Introduces an efficient way of communication between IPv6 hosts 198 and IPv4 hosts. 200 2) Allows IPv4 only hosts to exist and communicate with IPv6 only 201 hosts even after the depletion of the IPv4 address space. 203 3) Adds flexibility when making a query sent to the DNS for 204 hostname resolution as IPv4 and IPv6 hosts can communicate with 205 IPv4 or IPv6 DNS servers and the DNS can reply with any record 206 it has (either an IPv6 record Host AAAA record or an IPv4 207 record Host A record). 209 4) There is no need to think about migration as both IPv4 and IPv6 210 hosts can coexist and communicate to each other which will 211 allow the usage of the address space of both IPv4 and IPv6 212 making the available number of connected hosts be bigger. 214 5) IPv10 support on "all" Internet connected hosts can be deployed 215 in a very short time by technology companies developing OSs 216 (for hosts and networking devices, and there will be no 217 dependence on enterprise users and it is just a software 218 development process in the NIC cards of all hosts to allow 219 encapsulating both IPv4 and IPv6 in the same IP packet header. 221 6) Offers the four types of communication between hosts: 223 - IPv6 hosts to IPv4 hosts (6 to 4). 225 - IPv4 hosts to IPv6 hosts (4 to 6). 227 - IPv6 hosts to IPv6 hosts (6 to 6). 229 - IPv4 hosts to IPv4 hosts (4 to 4). 231 RFC IPv10 Specification April 17, 2017 233 3.1) IPv10: IPv6 Host to IPv4 Host. 234 ------------------------------ 236 - IPv10 Packet: 238 | 128-bit | 32-bit | 239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 240 | Data| Source IPv6 Address | Destination IPv4 Address | 241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 243 - Sending IPv10 host TCP/IP Configuration: 245 IP Address: IPv6 Address 246 Prefix Length: /length 247 Default Gateway: IPv6 Address (Optional) 248 DNS Addresses: IPv6/IPv4 Address 250 - Example of IPv10 Operation: 251 --------------------------- 253 R1 & R2 have both IPv4/IPv6 routing enabled 254 IPv10 Host IPv10 Host 256 PC-1 R1 * R2 PC-2 257 +----+ * * +----+ 258 | | * * * * | | 259 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 260 +----+ 2001:1::1 * * * * 192.168.1.1 +----+ 261 / / * Network * / / 262 +----+ * * +----+ 263 * * 264 IPv6: 2001:1::10/64 * IPv4: 192.168.1.10/24 265 DG : 2001:1::1 DG : 192.168.1.1 267 | 128-bit | 32-bit | 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 269 |Data | 2001:1::10 | 192.168.1.10|---> 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 Src. Address Dest. Address 273 IPv10: IPv6 host to IPv4 host 275 RFC IPv10 Specification April 17, 2017 277 3.2) IPv10: IPv4 Host to IPv6 Host. 278 ------------------------------ 280 - IPv10 Packet: 282 | 32-bit | 128-bit | 283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 284 | Data| Source IPv4 Address | Destination IPv6 Address | 285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 287 - Sending IPv10 host TCP/IP Configuration: 289 IP Address: IPv4 Address 290 Subnet Mask: /mask 291 Default Gateway: IPv4 Address 292 DNS Addresses: IPv4/IPv6 Address 294 - Example of IPv10 Operation: 295 --------------------------- 297 R1 & R2 have both IPv4/IPv6 routing enabled 298 IPv10 Host IPv10 Host 300 PC-1 R1 * R2 PC-2 301 +----+ * * +----+ 302 | | * * * * | | 303 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 304 +----+ 2001:1::1 * * * * 192.168.1.1 +----+ 305 / / * Network * / / 306 +----+ * * +----+ 307 * * 308 IPv6: 2001:1::10/64 * IPv4: 192.168.1.10/24 309 DG : 2001:1::1 DG : 192.168.1.1 311 | 128-bit | 32-bit | 312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 313 <---| 2001:1::10| 192.168.1.10| Data| 314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 Dest. Address Src. Addres 317 IPv10: IPv4 host to IPv6 host 319 RFC IPv10 Specification April 17, 2017 321 3.3) IPv10: IPv6 Host to IPv6 Host. 322 ------------------------------ 324 - IPv10 Packet: 326 | 128-bit | 128-bit | 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 328 | Data| Source IPv6 Address | Destination IPv6 Address | 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 331 - Sending IPv10 host TCP/IP Configuration: 333 IP Address: IPv6 Address 334 Prefix Length: /Length 335 Default Gateway: IPv6 Address (Optional) 336 DNS Addresses: IPv6/IPv4 Address 338 - Example of IPv10 Operation: 339 --------------------------- 341 R1 & R2 have both IPv4/IPv6 routing enabled 342 IPv10 Host IPv10 Host 344 PC-1 R1 * R2 PC-2 345 +----+ * * +----+ 346 | | * * * * | | 347 | |o---------o* X *o---o* IPv4/IPv6 *o---o* X *o---------o| | 348 +----+ 2001:1::1 * * * * 3001:1::1 +----+ 349 / / * Network * / / 350 +----+ * * +----+ 351 * * 352 IPv6: 2001:1::10/64 * IPv6: 3001:1::10/64 353 DG : 2001:1::1 DG : 3001:1::1 355 | 128-bit | 128-bit | 356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 |Data |2001:1::10 |3001:1::10 |---> 358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 359 Src. Address Dest. Address 361 IPv10: IPv6 host to IPv6 host 363 RFC IPv10 Specification April 17, 2017 365 3.4) IPv10: IPv4 Host to IPv4 Host. 366 ------------------------------ 368 - IPv10 Packet: 370 | 32-bit | 32-bit | 371 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 372 | Data| Source IPv4 Address | Destination IPv4 Address | 373 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 375 - Sending IPv10 host TCP/IP Configuration: 377 IP Address: IPv4 Address 378 Subnet Mask: /Mask 379 Default Gateway: IPv4 Address 380 DNS Addresses: IPv6/IPv4 Address 382 - Example of IPv10 Operation: 383 --------------------------- 385 R1 & R2 have both IPv4/IPv6 routing enabled 386 IPv10 Host IPv10 Host 388 PC-1 R1 * R2 PC-2 389 +----+ * * +----+ 390 | | * * * * | | 391 | |o--------o* X *o---o* IPv4/IPv6 *o---o* X *o-----------o| | 392 +----+ 10.1.1.1 * * * * 192.168.1.1 +----+ 393 / / * Network * / / 394 +----+ * * +----+ 395 * * 396 IPv4: 10.1.1.10/24 * IPv6: 192.168.1.10/24 397 DG : 10.1.1.1 DG : 192.168.1.1 399 | 32-bit | 32-bit | 400 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 401 |Data | 10.1.1.10 | 192.168.1.10|---> 402 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 403 Src. Address Dest. Address 405 IPv10: IPv4 host to IPv4 host 407 Important Notes: - IPv4 and IPv6 routing must be enabled on all routers, so 408 when a router receives an IPv10 packet, it should use 409 the appropriate routing table based on the destination 410 address within the IPv10 packet. 412 - That means, if the received IPv10 packet contains an IPv4 413 address in the destination address field, the router 414 should use the IPv4 routing table to make a routing 415 decision, and if the received IPv10 packet contains an 416 IPv6 address in the destination address field, the router 417 should use the IPv6 routing table to make a routing 418 decision. 420 - All Internet connected hosts must be IPv10 hosts to be 421 able to communicate regardless the used IP version, 422 and the IPv10 deployment process can be accomplished 423 by ALL technology companies developing OSs for hosts 424 networking and security devices. 426 RFC IPv10 Specification April 17, 2017 428 4. IPv10 Packet Header Format. 430 - The following figure shows the IPv10 packet header which is almost 431 the same as the IPv6 packet header: 433 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 434 |Version| Traffic Class | Flow Label | 435 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 436 | Payload Length | Next Header | Hop Limit | 437 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 438 | | 439 + + 440 | | 441 + Source Address + 442 | | 443 + + 444 | | 445 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 446 | | 447 + + 448 | | 449 + Destination Address + 450 | | 451 + + 452 | | 453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 455 Version 4-bit Internet Protocol version number. 457 - 0100 : IPv4 Packet 458 (Src. and dest. are IPv4). 459 - 0110 : IPv6 Packet 460 (Src. and dest. are IPv6). 461 - 1010 : IPv10 Packet 462 (Src. and dest. are IPv4/IPv6). 464 Traffic Class 8-bit traffic class field. 466 Flow Label 20-bit flow label. 468 Payload Length 16-bit unsigned integer. Length of the payload, 469 i.e., the rest of the packet following 470 this IP header, in octets. (Note that any 471 extension headers [section 4] present are 472 considered part of the payload, i.e., included 473 in the length count.) 475 Next Header 8-bit selector. Identifies the type of header 476 immediately following the IP header. 478 Hop Limit 8-bit unsigned integer. Decremented by 1 by 479 each node that forwards the packet. The packet 480 is discarded if Hop Limit is decremented to 481 zero. 483 Source Address 128-bit address of the originator of the packet. 485 | 96-bit | 32-bit | 486 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 487 | IPv6 Address | OR | 00000......0 | IPv4 Address | 488 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 489 | 128-bit | | 128-bit | 491 Destination Address 128-bit address of the intended recipient of the 492 packet (possibly not the ultimate recipient, if 493 a Routing header is present). 495 | 96-bit | 32-bit | 496 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 497 | IPv6 Address | OR | 00000......0 | IPv4 Address | 498 +-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 499 | 128-bit | | 128-bit | 501 RFC IPv10 Specification April 17, 2017 502 Expires: 17-10-2017 504 Security Considerations 506 The security features of IPv10 are described in the Security 507 Architecture for the Internet Protocol [RFC-2401]. 509 Acknowledgments 511 The authors would like to thank S. Krishnan, W. Haddad, C. Huitema, 512 T. Manderson, JC. Zuniga, A. Sullivan, Lee H., K. Thomann, M. Abrahamsson, 513 S. Bortzmeyer, J. Linkova, and T. Herbert for the useful inputs and 514 discussions about IPv10. 516 Author Address 518 Khaled Omar Ibrahim Omar 519 The Road 520 6th of October City, 521 Giza, Egypt 522 Passport ID no.: A19954283 524 Phone: +2 01003620284 525 E-mail: eng.khaled.omar@hotmail.com 527 References 529 [RFC-2401] Stephen E. Deering and Robert M. Hinden, "IPv6 530 Specification", RFC 2460, December 1998. 532 Full Copyright Statement 534 Copyright (C) IETF (2016). All Rights Reserved. 536 This document and translations of it may be copied and furnished to 537 others, and derivative works that comment on or otherwise explain it 538 or assist in its implementation may be prepared, copied, published 539 and distributed, in whole or in part, without restriction of any 540 kind, provided that the above copyright notice and this paragraph are 541 included on all such copies and derivative works. However, this 542 document itself may not be modified in any way, such as by removing 543 the copyright notice or references, except as needed for the purpose of 544 developing Internet standards in which case the procedures for 545 copyrights defined in the Internet Standards process must be 546 followed, or as required to translate it into languages other than 547 English. 549 The limited permissions granted above are perpetual and will not be 550 revoked. 552 This document and the information contained herein is provided on 553 THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, 554 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 555 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 556 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 557 PURPOSE.