IPv6
Parts of this article (those related to RFC 8200 and RFC 8201) need to be updated.(July 2017) |
Communication protocol | |
Abbreviation | IPv6 |
---|---|
Purpose | Internetworking protocol |
Developer(s) | Internet Engineering Task Force |
Introduction | December 1995 |
Based on | IPv4 |
OSI layer | Network layer |
RFC(s) | 2460, 8200 |
Internet protocol suite |
---|
Application layer |
Transport layer |
Internet layer |
Link layer |
Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the long-anticipated problem of IPv4 address exhaustion, and was intended to replace IPv4.[1] In December 1998, IPv6 became a Draft Standard for the IETF,[2] which subsequently ratified it as an Internet Standard on 14 July 2017.[3][4]
Devices on the Internet are assigned a unique
IPv6 provides other technical benefits in addition to a larger addressing space. In particular, it permits hierarchical address allocation methods that facilitate
IPv6 addresses are represented as eight groups of four hexadecimal digits each, separated by colons. The full representation may be shortened; for example, 2001:0db8:0000:0000:0000:8a2e:0370:7334 becomes 2001:db8::8a2e:370:7334.
Main features
IPv6 is an
In addition to offering more addresses, IPv6 also implements features not present in IPv4. It simplifies aspects of address configuration, network renumbering, and router announcements when changing network connectivity providers. It simplifies packet processing in routers by placing the responsibility for packet fragmentation in the end points. The IPv6
The addressing architecture of IPv6 is defined in
: 210Motivation and origin
IPv4 address exhaustion
Internet Protocol Version 4 (IPv4) was the first publicly used version of the Internet Protocol. IPv4 was developed as a research project by the Defense Advanced Research Projects Agency (DARPA), a United States Department of Defense agency, before becoming the foundation for the Internet and the World Wide Web. IPv4 includes an addressing system that uses numerical identifiers consisting of 32 bits. These addresses are typically displayed in dot-decimal notation as decimal values of four octets, each in the range 0 to 255, or 8 bits per number. Thus, IPv4 provides an addressing capability of 232 or approximately 4.3 billion addresses. Address exhaustion was not initially a concern in IPv4 as this version was originally presumed to be a test of DARPA's networking concepts.[6] During the first decade of operation of the Internet, it became apparent that methods had to be developed to conserve address space. In the early 1990s, even after the redesign of the addressing system using a classless network model, it became clear that this would not suffice to prevent IPv4 address exhaustion, and that further changes to the Internet infrastructure were needed.[7]
The last unassigned top-level address blocks of 16 million IPv4 addresses were allocated in February 2011 by the
RIPE NCC announced that it had fully run out of IPv4 addresses on 25 November 2019,[13] and called for greater progress on the adoption of IPv6.
Comparison with IPv4
On the Internet, data is transmitted in the form of network packets. IPv6 specifies a new packet format, designed to minimize packet header processing by routers.[2][14] Because the headers of IPv4 packets and IPv6 packets are significantly different, the two protocols are not interoperable. However, most transport and application-layer protocols need little or no change to operate over IPv6; exceptions are application protocols that embed Internet-layer addresses, such as File Transfer Protocol (FTP) and Network Time Protocol (NTP), where the new address format may cause conflicts with existing protocol syntax.
Larger address space
The main advantage of IPv6 over IPv4 is its larger address space. The size of an IPv6 address is 128 bits, compared to 32 bits in IPv4.
While this address space is very large, it was not the intent of the designers of IPv6 to assure geographical saturation with usable addresses. Rather, the longer addresses simplify allocation of addresses, enable efficient
Multicasting
In IPv4 it is very difficult for an organization to get even one globally routable multicast group assignment, and the implementation of inter-domain solutions is arcane.
Stateless address autoconfiguration (SLAAC)
IPv6 hosts configure themselves automatically. Every interface has a self-generated link-local address and, when connected to a network, conflict resolution is performed and routers provide network prefixes via router advertisements.[19] Stateless configuration of routers can be achieved with a special router renumbering protocol.[20] When necessary, hosts may configure additional stateful addresses via Dynamic Host Configuration Protocol version 6 (DHCPv6) or static addresses manually.
Like IPv4, IPv6 supports globally unique IP addresses. The design of IPv6 intended to re-emphasize the end-to-end principle of network design that was originally conceived during the establishment of the early Internet by rendering network address translation obsolete. Therefore, every device on the network is globally addressable directly from any other device.
A stable, unique, globally addressable IP address would facilitate tracking a device across networks. Therefore, such addresses are a particular privacy concern for mobile devices, such as laptops and cell phones.[21] To address these privacy concerns, the SLAAC protocol includes what are typically called "privacy addresses" or, more correctly, "temporary addresses", codified in RFC 4941, "Privacy Extensions for Stateless Address Autoconfiguration in IPv6".[22] Temporary addresses are random and unstable. A typical consumer device generates a new temporary address daily and will ignore traffic addressed to an old address after one week. Temporary addresses are used by default by Windows since XP SP1,[23] macOS since (Mac OS X) 10.7, Android since 4.0, and iOS since version 4.3. Use of temporary addresses by Linux distributions varies.[24]
Renumbering an existing network for a new connectivity provider with different routing prefixes is a major effort with IPv4.[25][26] With IPv6, however, changing the prefix announced by a few routers can in principle renumber an entire network, since the host identifiers (the least-significant 64 bits of an address) can be independently self-configured by a host.[19]
The SLAAC address generation method is implementation-dependent. IETF recommends that addresses be deterministic but semantically opaque.[27]
IPsec
Simplified processing by routers
The packet header in IPv6 is simpler than the IPv4 header. Many rarely used fields have been moved to optional header extensions. The IPv6 packet header has simplified the process of packet forwarding by routers. Although IPv6 packet headers are at least twice the size of IPv4 packet headers, processing of packets that only contain the base IPv6 header by routers may, in some cases, be more efficient, because less processing is required in routers due to the headers being aligned to match common word sizes.[2][14] However, many devices implement IPv6 support in software (as opposed to hardware), thus resulting in very bad packet processing performance.[29] Additionally, for many implementations, the use of Extension Headers causes packets to be processed by a router's CPU, leading to poor performance or even security issues.[30]
Moreover, an IPv6 header does not include a checksum. The
IPv6 routers do not perform IP fragmentation. IPv6 hosts are required to do one of the following: perform Path MTU Discovery, perform end-to-end fragmentation, or send packets no larger than the default maximum transmission unit (MTU), which is 1280 octets.
Mobility
Unlike mobile IPv4,
Extension headers
The IPv6 packet header has a minimum size of 40 octets (320 bits). Options are implemented as extensions. This provides the opportunity to extend the protocol in the future without affecting the core packet structure.[2] However, RFC 7872 notes that some network operators drop IPv6 packets with extension headers when they traverse transit autonomous systems.
Jumbograms
IPv4 limits packets to 65,535 (216−1) octets of payload. An IPv6 node can optionally handle packets over this limit, referred to as jumbograms, which can be as large as 4,294,967,295 (232−1) octets. The use of jumbograms may improve performance over high-MTU links. The use of jumbograms is indicated by the Jumbo Payload Option extension header.[32]
IPv6 packets
An IPv6 packet has two parts: a header and payload.
The header consists of a fixed portion with minimal functionality required for all packets and may be followed by optional extensions to implement special features.
The fixed header occupies the first 40 octets (320 bits) of the IPv6 packet. It contains the source and destination addresses, traffic class, hop count, and the type of the optional extension or payload which follows the header. This Next Header field tells the receiver how to interpret the data which follows the header. If the packet contains options, this field contains the option type of the next option. The "Next Header" field of the last option points to the upper-layer protocol that is carried in the packet's payload.
The current use of the IPv6 Traffic Class field divides this between a 6 bit Differentiated Services Code Point[33] and a 2-bit Explicit Congestion Notification field.[34]
Extension headers carry options that are used for special treatment of a packet in the network, e.g., for routing, fragmentation, and for security using the IPsec framework.
Without special options, a payload must be less than 64kB. With a Jumbo Payload option (in a Hop-By-Hop Options extension header), the payload must be less than 4 GB.
Unlike with IPv4, routers never fragment a packet. Hosts are expected to use Path MTU Discovery to make their packets small enough to reach the destination without needing to be fragmented. See IPv6 packet fragmentation.
Addressing
IPv6 addresses have 128 bits. The design of the IPv6 address space implements a different design philosophy than in IPv4, in which subnetting was used to improve the efficiency of utilization of the small address space. In IPv6, the address space is deemed large enough for the foreseeable future, and a local area subnet always uses 64 bits for the host portion of the address, designated as the interface identifier, while the most-significant 64 bits are used as the routing prefix.[35] While the myth has existed regarding IPv6 subnets being impossible to scan, RFC 7707 notes that patterns resulting from some IPv6 address configuration techniques and algorithms allow address scanning in many real-world scenarios.
Address representation
The 128 bits of an IPv6 address are represented in 8 groups of 16 bits each. Each group is written as four hexadecimal digits (sometimes called ) and the groups are separated by colons (:). An example of this representation is 2001:0db8:0000:0000:0000:ff00:0042:8329.
For convenience and clarity, the representation of an IPv6 address may be shortened with the following rules:
- One or more leading zeros from any group of hexadecimal digits are removed, which is usually done to all of the leading zeros. For example, the group 0042 is converted to 42. The group 0000 is converted to 0.
- Consecutive sections of zeros are replaced with two colons (::). This may only be used once in an address, as multiple use would render the address indeterminate.
An example of application of these rules:
- Initial address: 2001:0db8:0000:0000:0000:ff00:0042:8329.
- After removing all leading zeros in each group: 2001:db8:0:0:0:ff00:42:8329.
- After omitting consecutive sections of zeros: 2001:db8::ff00:42:8329.
The loopback address 0000:0000:0000:0000:0000:0000:0000:0001 is defined in
As an IPv6 address may have more than one representation, the IETF has issued a proposed standard for representing them in text.[40]
Because IPv6 addresses contain colons, and URLs use colons to separate the host from the port number, RFC2732[41] specifies that an IPv6 address used as the host-part of a URL should be enclosed in square brackets, e.g. http://[2001:db8:4006:812::200e] or http://[2001:db8:4006:812::200e]:8080/path/page.html.
Link-local address
All interfaces of IPv6 hosts require a link-local address, which have the prefix fe80::/10. This prefix is followed by 54 bits that can be used for subnetting, although they are typically set to zeros, and a 64-bit interface identifier. The host can compute and assign the Interface identifier by itself without the presence or cooperation of an external network component like a DHCP server, in a process called link-local address autoconfiguration.[citation needed]
The lower 64 bits of the link-local address (the suffix) were originally derived from the MAC address of the underlying network interface card. As this method of assigning addresses would cause undesirable address changes when faulty network cards were replaced, and as it also suffered from a number of security and privacy issues,
Address uniqueness and router solicitation
IPv6 uses a new mechanism for mapping IP addresses to link-layer addresses (e.g. MAC addresses), because it does not support the broadcast addressing method, on which the functionality of the Address Resolution Protocol (ARP) in IPv4 is based. IPv6 implements the Neighbor Discovery Protocol (NDP, ND) in the link layer, which relies on ICMPv6 and multicast transmission.[5]: 210 IPv6 hosts verify the uniqueness of their IPv6 addresses in a local area network (LAN) by sending a neighbor solicitation message asking for the link-layer address of the IP address. If any other host in the LAN is using that address, it responds.[42]
A host bringing up a new IPv6 interface first generates a unique link-local address using one of several mechanisms designed to generate a unique address. Should a non-unique address be detected, the host can try again with a newly generated address. Once a unique link-local address is established, the IPv6 host determines whether the LAN is connected on this link to any router interface that supports IPv6. It does so by sending out an ICMPv6 router solicitation message to the all-routers[43] multicast group with its link-local address as source. If there is no answer after a predetermined number of attempts, the host concludes that no routers are connected. If it does get a response, known as a router advertisement, from a router, the response includes the network configuration information to allow establishment of a globally unique address with an appropriate unicast network prefix.[44] There are also two flag bits that tell the host whether it should use DHCP to get further information and addresses:
- The Manage bit, which indicates whether or not the host should use DHCP to obtain additional addresses rather than rely on an auto-configured address from the router advertisement.
- The Other bit, which indicates whether or not the host should obtain other information through DHCP. The other information consists of one or more prefix information options for the subnets that the host is attached to, a lifetime for the prefix, and two flags:[42]
- On-link: If this flag is set, the host will treat all addresses on the specific subnet as being on-link and send packets directly to them instead of sending them to a router for the duration of the given lifetime.
- Address: This flag tells the host to actually create a global address.
Global addressing
The assignment procedure for global addresses is similar to local-address construction. The prefix is supplied from router advertisements on the network. Multiple prefix announcements cause multiple addresses to be configured.[42]
Stateless address autoconfiguration (SLAAC) requires a 64 address block, as defined in
IPv6 in the Domain Name System
In the
When a dual-stack host queries a DNS server to resolve a
An alternate record type was used in early DNS implementations for IPv6, designed to facilitate network renumbering, the A6 records for the forward lookup and a number of other innovations such as bit-string labels and
Transition mechanisms
IPv6 is not foreseen to supplant IPv4 instantaneously. Both protocols will continue to operate simultaneously for some time. Therefore, IPv6 transition mechanisms are needed to enable IPv6 hosts to reach IPv4 services and to allow isolated IPv6 hosts and networks to reach each other over IPv4 infrastructure.[48]
According to
Dual-stack IP implementation
Dual-stack IP implementations provide complete IPv4 and IPv6 protocol stacks in the operating system of a
A device with dual-stack implementation in the operating system has an IPv4 and IPv6 address, and can communicate with other nodes in the LAN or the Internet using either IPv4 or IPv6. The DNS protocol is used by both IP protocols to resolve fully qualified domain names and IP addresses, but dual stack requires that the resolving DNS server can resolve both types of addresses. Such a dual-stack DNS server holds IPv4 addresses in the A records and IPv6 addresses in the AAAA records. Depending on the destination that is to be resolved, a DNS name server may return an IPv4 or IPv6 IP address, or both. A default address selection mechanism, or preferred protocol, needs to be configured either on hosts or the DNS server. The
While dual-stack is supported by major operating system and network device vendors, legacy networking hardware and servers do not support IPv6.
ISP customers with public-facing IPv6
A significant percentage of ISPs in all
While some ISPs still allocate customers only IPv4 addresses, many ISPs allocate their customers only an IPv6 or dual-stack IPv4 and IPv6. ISPs report the share of IPv6 traffic from customers over their network to be anything between 20% and 40%, but by mid-2017 IPv6 traffic still only accounted for a fraction of total traffic at several large
Tunneling
The technical basis for tunneling, or encapsulating IPv6 packets in IPv4 packets, is outlined in RFC 4213. When the Internet backbone was IPv4-only, one of the frequently used tunneling protocols was
IPv4-mapped IPv6 addresses
Hybrid dual-stack IPv6/IPv4 implementations recognize a special class of addresses, the IPv4-mapped IPv6 addresses.[59][60] These addresses are typically written with a 96-bit prefix in the standard IPv6 format, and the remaining 32 bits are written in the customary dot-decimal notation of IPv4.
Addresses in this group consist of an 80-bit prefix of zeros, the next 16 bits are ones, and the remaining, least-significant 32 bits contain the IPv4 address. For example, ::ffff:192.0.2.128 represents the IPv4 address 192.0.2.128. A previous format, called "IPv4-compatible IPv6 address", was ::192.0.2.128; however, this method is deprecated.[60]
Because of the significant internal differences between IPv4 and IPv6 protocol stacks, some of the lower-level functionality available to programmers in the IPv6 stack does not work the same when used with IPv4-mapped addresses. Some common IPv6 stacks do not implement the IPv4-mapped address feature, either because the IPv6 and IPv4 stacks are separate implementations (e.g., Microsoft Windows 2000, XP, and Server 2003), or because of security concerns (OpenBSD).[61] On these operating systems, a program must open a separate socket for each IP protocol it uses. On some systems, e.g., the Linux kernel, NetBSD, and FreeBSD, this feature is controlled by the socket option IPV6_V6ONLY.[62]: 22
The address prefix 64:ff9b::/96 is a class of IPv4-embedded IPv6 addresses for use in NAT64 transition methods.[63] For example, 64:ff9b::192.0.2.128 represents the IPv4 address 192.0.2.128.
Security
A number of security implications may arise from the use of IPv6. Some of them may be related with the IPv6 protocols themselves, while others may be related with implementation flaws.[64][65]
Shadow networks
The addition of nodes having IPv6 enabled by default by the software manufacturer may result in the inadvertent creation of shadow networks, causing IPv6 traffic flowing into networks having only IPv4 security management in place. This may also occur with operating system upgrades, when the newer operating system enables IPv6 by default, while the older one did not. Failing to update the security infrastructure to accommodate IPv6 can lead to IPv6 traffic bypassing it.[66] Shadow networks have occurred on business networks in which enterprises are replacing Windows XP systems that do not have an IPv6 stack enabled by default, with Windows 7 systems, that do.[67] Some IPv6 stack implementors have therefore recommended disabling IPv4 mapped addresses and instead using a dual-stack network where supporting both IPv4 and IPv6 is necessary.[68]
IPv6 packet fragmentation
Research has shown that the use of fragmentation can be leveraged to evade network security controls, similar to IPv4. As a result,
Standardization through RFCs
Working-group proposals
Due to the anticipated global growth of the
The Internet Engineering Task Force adopted the IPng model on 25 July 1994, with the formation of several IPng working groups.
RFC standardization
The first RFC to standardize IPv6 was the
Deployment
The 1993 introduction of Classless Inter-Domain Routing (CIDR) in the routing and IP address allocation for the Internet, and the extensive use of network address translation (NAT), delayed IPv4 address exhaustion to allow for IPv6 deployment, which began in the mid-2000s.
Universities were among the early adopters of IPv6.
The Domain Name System (DNS) has supported IPv6 since 2008. In the same year, IPv6 was first used in a major world event during the Beijing 2008 Summer Olympics.[74][75]
By 2011, all major operating systems in use on personal computers and server systems had production-quality IPv6 implementations. Cellular telephone systems presented a large deployment field for Internet Protocol devices as mobile telephone service made the transition from
The deployment of IPv6 in the Internet backbone continued. In 2018 only 25.3% of the about 54,000 autonomous systems advertised both IPv4 and IPv6 prefixes in the global Border Gateway Protocol (BGP) routing database. A further 243 networks advertised only an IPv6 prefix. Internet backbone transit networks offering IPv6 support existed in every country globally, except in parts of Africa, the Middle East and China.[77]: 6 By mid-2018 some major European broadband ISPs had deployed IPv6 for the majority of their customers. Sky UK provided over 86% of its customers with IPv6, Deutsche Telekom had 56% deployment of IPv6, XS4ALL in the Netherlands had 73% deployment and in Belgium the broadband ISPs VOO and Telenet had 73% and 63% IPv6 deployment respectively.[77]: 7 In the United States the broadband ISP Xfinity had an IPv6 deployment of about 66%. In 2018 Xfinity reported an estimated 36.1 million IPv6 users, while AT&T reported 22.3 million IPv6 users.[77]: 7–8
See also
- China Next Generation Internet
- Comparison of IPv6 support in operating systems
- Comparison of IPv6 support in common applications
- DoD IPv6 product certification
- OCCAID
- University of New Hampshire InterOperability Laboratory
References
- ^ "FAQs". New Zealand IPv6 Task Force. Archived from the original on 29 January 2019. Retrieved 26 October 2015.
- ^ RFC 2460Obsoletes RFC 1883.
- ^ RFC 8200Obsoletes RFC 2460.
- ^ Siddiqui, Aftab (17 July 2017). "RFC 8200 – IPv6 Has Been Standardized". Internet Society. Archived from the original on 23 October 2023. Retrieved 25 February 2018.
- ^ OCLC 869747983.
- ^ Google IPv6 Conference 2008: What will the IPv6 Internet look like?. Event occurs at 13:35. Archived from the original on 11 December 2021.
- ^ .
- ^ "Free Pool of IPv4 Address Space Depleted". NRO.net. Montevideo: The Number Resource Organization. 3 February 2011. Archived from the original on 18 January 2024. Retrieved 19 January 2022.
- ^ Rashid, Fahmida (1 February 2011). "IPv4 Address Exhaustion Not Instant Cause for Concern with IPv6 in Wings". eWeek. Archived from the original on 20 January 2024. Retrieved 23 June 2012.
- ^ Ward, Mark (14 September 2012). "Europe hits old internet address limits". BBC News. Archived from the original on 5 November 2023. Retrieved 15 September 2012.
- ^ Huston, Geoff. "IPV4 Address Report". Archived from the original on 10 January 2024.
- ^ "FAQ". my.afrinic.net. AFRINIC. Archived from the original on 23 October 2023. Retrieved 28 November 2018.
- ^ "The RIPE NCC has run out of IPv4 Addresses" (Press release). RIPE NCC. 25 November 2019. Archived from the original on 19 January 2024. Retrieved 26 November 2019.
- ^ RFC 1726.
- RFC 1112, Host extensions for IP multicasting, S. Deering (August 1989)
- RFC 3956, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address, P. Savola, B. Haberman (November 2004)
- RFC 2908, The Internet Multicast Address Allocation Architecture, D. Thaler, M. Handley, D. Estrin (September 2000)
- RFC 3306, Unicast-Prefix-based IPv6 Multicast Addresses, B. Haberman, D. Thaler (August 2002)
- ^ from the original on 11 January 2024.
- RFC 2894, Router Renumbering for IPv6, M. Crawford, August 2000.
- ^ T. Narten; R. Draves; S. Krishnan (September 2007). "Privacy Extensions for Stateless Address Autoconfiguration in IPv6". www.ietf.org. Retrieved 13 March 2017.
- .
- ^ "Overview of the Advanced Networking Pack for Windows XP". Microsoft. Archived from the original on 7 September 2017. Retrieved 15 April 2019.
- ^ "Privacy Extensions for IPv6 SLAAC". Internet Society. 8 August 2014. Archived from the original on 23 October 2023. Retrieved 17 January 2020.
- from the original on 7 January 2024.
- from the original on 8 June 2023.
- .
- OCLC 881832733.
- ^ Zack, E. (July 2013). "IPv6 Security Assessment and Benchmarking".
- IETF. Archivedfrom the original on 27 October 2023.
- RFC 3963, Network Mobility (NEMO) Basic Protocol Support, V. Devarapalli, R. Wakikawa, A. Petrescu, P. Thubert (January 2005)
- RFC 2675, IPv6 Jumbograms, D. Borman, S. Deering, R. Hinden (August 1999)
- RFC 2474
- RFC 3168
- RFC 4291, p. 9.
- ISBN 978-0-13-303347-2.
- ISBN 978-1-4919-0326-1.
- ^ ISBN 978-1-4302-6371-5.
- from the original on 12 January 2024.
- from the original on 12 January 2024.
- from the original on 5 January 2024.
- ^ .
- from the original on 17 January 2024.
- from the original on 11 January 2024.
- ^ "IPv6 Address Allocation and Assignment Policy". RIPE NCC. 8 February 2011. Archived from the original on 3 June 2023. Retrieved 27 March 2011.
- ^ Brzozowski, John (31 January 2011). "Comcast Activates First Users With IPv6 Native Dual Stack Over DOCSIS" (Press release). Comcast. Archived from the original on 23 October 2023. Retrieved 15 April 2019.
- ISBN 9781449335267.
- ^ "IPv6 Transition Mechanism/Tunneling Comparison". Sixxs.net. Archived from the original on 23 October 2023. Retrieved 20 January 2012.
- ISBN 9781449335267.
- from the original on 28 January 2023. Retrieved 20 August 2012.
- ^ "IPv6: Dual stack where you can; tunnel where you must". networkworld.com. 5 September 2007. Archived from the original on 20 January 2024. Retrieved 27 November 2012.
- from the original on 11 January 2024. Retrieved 20 August 2012.
- ISBN 9781449335267.
- ^ "Understanding Dual Stacking of IPv4 and IPv6 Unicast Addresses". Juniper.net. Juniper Networks. 31 August 2017. Retrieved 19 January 2022.
- ^ "IPv6". NRO.net. Archived from the original on 12 January 2017. Retrieved 13 March 2017.
- ^ Pujol, Enric (12 June 2017). "What Stops IPv6 Traffic in a Dual-Stack ISP?". APNIC.net. APNIC. Archived from the original on 27 March 2023. Retrieved 13 June 2017.
- ^ Vaughan-Nichols, Steven J. (14 October 2010). "Five ways for IPv6 and IPv4 to peacefully co-exist". ZDNET. Archived from the original on 5 December 2023. Retrieved 13 March 2017.
- ISBN 9781449335267.
- . Table 20.
- ^ .
- ^ OpenBSD Kernel Interfaces Manual –
- .
- .
- ^ Gont, Fernando (10 March 2019), IPv6 Security for IPv4 Engineers (PDF), retrieved 30 August 2019
- ^ Gont, Fernando (10 January 2019), IPv6 Security Frequently Asked Questions (FAQ) (PDF), retrieved 30 August 2019
- ^ Mullins, Robert (5 April 2012), Shadow Networks: an Unintended IPv6 Side Effect, archived from the original on 11 April 2013, retrieved 2 March 2013
- ^ Cicileo, Guillermo; Gagliano, Roque; O’Flaherty, Christian; et al. (October 2009). IPv6 For All: A Guide for IPv6 Usage and Application in Different Environments (PDF). p. 5. Retrieved 2 March 2013.
- ^ Jun-ichiro itojun Hagino (October 2003). "IPv4-Mapped Addresses on the Wire Considered Harmful".
- RFC 1550.
- ^ "History of the IPng Effort". The Sun. Archived from the original on 23 May 2014.
- RFC 1752.
- .
- ^ State of IPv6 Deployment 2018, Internet Society, 2018, p. 3
- ^ "Beijing2008.cn leaps to next-generation Net" (Press release). The Beijing Organizing Committee for the Games of the XXIX Olympiad. 30 May 2008. Archived from the original on 4 February 2009.
- ^ Das, Kaushik (2008). "IPv6 and the 2008 Beijing Olympics". IPv6.com. Archived from the original on 1 August 2008. Retrieved 15 August 2008.
- ^ a b Morr, Derek (9 June 2009). "Verizon Mandates IPv6 Support for Next-Gen Cell Phones". CircleID.
- ^ a b c "State of IPv6 Deployment 2018" (PDF). InternetSociety.org. Internet Society. Retrieved 19 January 2022.
External links
- IPv6 in the Linux Kernel by Rami Rosen
- An Introduction and Statistics about IPv6 by Google
- The standard document ratifying IPv6 – RFC 8200 document ratifying IPv6 as an Internet Standard