Interesting thokling Here's that quote you referred to earlier
(12-01-2011, 06:43 AM)thokling Wrote: http://mashable.com/2011/02/03/ipv4-ipv6-guide/ also notes under Q: Why are we running out of IPv4 addresses? that many blocks are owned by corporations, though the first link contains itself a link to the pertinent data.
and here is that pertinent data, once everyone else is forced off of the IPV4 protocol once it is widely adopted that frees up the old internet for use by or via the companies that control them, thus creating a free layer, or another
undernet layer for legacy communication.
Code:
IANA IPv4 Address Space Registry
Last Updated
2011-02-03
Description
The allocation of Internet Protocol version 4 (IPv4) address space to various registries is listed
here. Originally, all the IPv4 address spaces was managed directly by the IANA. Later parts of the
address space were allocated to various other registries to manage for particular purposes or
regional areas of the world. RFC 1466 [RFC1466] documents most of these allocations.
This registry is also available in plain text.
Prefix Designation Date Whois Status [1] Note
000/8 IANA - Local Identification 1981-09 RESERVED [2]
001/8 APNIC 2010-01 whois.apnic.net ALLOCATED
002/8 RIPE NCC 2009-09 whois.ripe.net ALLOCATED
003/8 General Electric Company 1994-05 LEGACY
004/8 Level 3 Communications, Inc. 1992-12 LEGACY
005/8 RIPE NCC 2010-11 whois.ripe.net ALLOCATED
006/8 Army Information Systems Center 1994-02 LEGACY
007/8 Administered by ARIN 1995-04 whois.arin.net LEGACY
008/8 Level 3 Communications, Inc. 1992-12 LEGACY
009/8 IBM 1992-08 LEGACY
010/8 IANA - Private Use 1995-06 RESERVED [3]
011/8 DoD Intel Information Systems 1993-05 LEGACY
012/8 AT&T Bell Laboratories 1995-06 LEGACY
013/8 Xerox Corporation 1991-09 LEGACY
014/8 APNIC 2010-04 whois.apnic.net ALLOCATED [4]
015/8 Hewlett-Packard Company 1994-07 LEGACY
016/8 Digital Equipment Corporation 1994-11 LEGACY
017/8 Apple Computer Inc. 1992-07 LEGACY
018/8 MIT 1994-01 LEGACY
019/8 Ford Motor Company 1995-05 LEGACY
020/8 Computer Sciences Corporation 1994-10 LEGACY
021/8 DDN-RVN 1991-07 LEGACY
022/8 Defense Information Systems Agency 1993-05 LEGACY
023/8 ARIN 2010-11 whois.arin.net ALLOCATED
024/8 ARIN 2001-05 whois.arin.net ALLOCATED
025/8 UK Ministry of Defence 1995-01 whois.ripe.net LEGACY
026/8 Defense Information Systems Agency 1995-05 LEGACY
027/8 APNIC 2010-01 whois.apnic.net ALLOCATED
028/8 DSI-North 1992-07 LEGACY
029/8 Defense Information Systems Agency 1991-07 LEGACY
030/8 Defense Information Systems Agency 1991-07 LEGACY
031/8 RIPE NCC 2010-05 whois.ripe.net ALLOCATED
032/8 AT&T Global Network Services 1994-06 LEGACY
033/8 DLA Systems Automation Center 1991-01 LEGACY
034/8 Halliburton Company 1993-03 LEGACY
035/8 MERIT Computer Network 1994-04 LEGACY
036/8 APNIC 2010-10 whois.apnic.net ALLOCATED
037/8 RIPE NCC 2010-11 whois.ripe.net ALLOCATED
038/8 PSINet, Inc. 1994-09 LEGACY
039/8 APNIC 2011-01 whois.apnic.net ALLOCATED
040/8 Eli Lily & Company 1994-06 LEGACY
041/8 AfriNIC 2005-04 whois.afrinic.net ALLOCATED
042/8 APNIC 2010-10 whois.apnic.net ALLOCATED
043/8 Administered by APNIC 1991-01 LEGACY
044/8 Amateur Radio Digital Communications 1992-07 LEGACY
045/8 Administered by ARIN 1995-01 whois.arin.net LEGACY
046/8 RIPE NCC 2009-09 whois.ripe.net ALLOCATED
047/8 Bell-Northern Research 1991-01 LEGACY
048/8 Prudential Securities Inc. 1995-05 LEGACY
049/8 APNIC 2010-08 whois.apnic.net ALLOCATED
050/8 ARIN 2010-02 whois.arin.net ALLOCATED
051/8 UK Government Department for Work and Pensions 1994-08 whois.ripe.net LEGACY
052/8 E.I. duPont de Nemours and Co., Inc. 1991-12 LEGACY
053/8 Cap Debis CCS 1993-10 LEGACY
054/8 Merck and Co., Inc. 1992-03 LEGACY
055/8 DoD Network Information Center 1995-04 LEGACY
056/8 US Postal Service 1994-06 LEGACY
057/8 SITA 1995-05 LEGACY
058/8 APNIC 2004-04 whois.apnic.net ALLOCATED
059/8 APNIC 2004-04 whois.apnic.net ALLOCATED
060/8 APNIC 2003-04 whois.apnic.net ALLOCATED
061/8 APNIC 1997-04 whois.apnic.net ALLOCATED
062/8 RIPE NCC 1997-04 whois.ripe.net ALLOCATED
063/8 ARIN 1997-04 whois.arin.net ALLOCATED
064/8 ARIN 1999-07 whois.arin.net ALLOCATED
065/8 ARIN 2000-07 whois.arin.net ALLOCATED
066/8 ARIN 2000-07 whois.arin.net ALLOCATED
067/8 ARIN 2001-05 whois.arin.net ALLOCATED
068/8 ARIN 2001-06 whois.arin.net ALLOCATED
069/8 ARIN 2002-08 whois.arin.net ALLOCATED
070/8 ARIN 2004-01 whois.arin.net ALLOCATED
071/8 ARIN 2004-08 whois.arin.net ALLOCATED
072/8 ARIN 2004-08 whois.arin.net ALLOCATED
073/8 ARIN 2005-03 whois.arin.net ALLOCATED
074/8 ARIN 2005-06 whois.arin.net ALLOCATED
075/8 ARIN 2005-06 whois.arin.net ALLOCATED
076/8 ARIN 2005-06 whois.arin.net ALLOCATED
077/8 RIPE NCC 2006-08 whois.ripe.net ALLOCATED
078/8 RIPE NCC 2006-08 whois.ripe.net ALLOCATED
079/8 RIPE NCC 2006-08 whois.ripe.net ALLOCATED
080/8 RIPE NCC 2001-04 whois.ripe.net ALLOCATED
081/8 RIPE NCC 2001-04 whois.ripe.net ALLOCATED
082/8 RIPE NCC 2002-11 whois.ripe.net ALLOCATED
083/8 RIPE NCC 2003-11 whois.ripe.net ALLOCATED
084/8 RIPE NCC 2003-11 whois.ripe.net ALLOCATED
085/8 RIPE NCC 2004-04 whois.ripe.net ALLOCATED
086/8 RIPE NCC 2004-04 whois.ripe.net ALLOCATED
087/8 RIPE NCC 2004-04 whois.ripe.net ALLOCATED
088/8 RIPE NCC 2004-04 whois.ripe.net ALLOCATED
089/8 RIPE NCC 2005-06 whois.ripe.net ALLOCATED
090/8 RIPE NCC 2005-06 whois.ripe.net ALLOCATED
091/8 RIPE NCC 2005-06 whois.ripe.net ALLOCATED
092/8 RIPE NCC 2007-03 whois.ripe.net ALLOCATED
093/8 RIPE NCC 2007-03 whois.ripe.net ALLOCATED
094/8 RIPE NCC 2007-07 whois.ripe.net ALLOCATED
095/8 RIPE NCC 2007-07 whois.ripe.net ALLOCATED
096/8 ARIN 2006-10 whois.arin.net ALLOCATED
097/8 ARIN 2006-10 whois.arin.net ALLOCATED
098/8 ARIN 2006-10 whois.arin.net ALLOCATED
099/8 ARIN 2006-10 whois.arin.net ALLOCATED
100/8 ARIN 2010-11 whois.arin.net ALLOCATED
101/8 APNIC 2010-08 whois.apnic.net ALLOCATED
102/8 AfriNIC 2011-02 whois.afrinic.net ALLOCATED
103/8 APNIC 2011-02 whois.apnic.net ALLOCATED
104/8 ARIN 2011-02 whois.arin.net ALLOCATED
105/8 AfriNIC 2010-11 whois.afrinic.net ALLOCATED
106/8 APNIC 2011-01 whois.apnic.net ALLOCATED
107/8 ARIN 2010-02 whois.arin.net ALLOCATED
108/8 ARIN 2008-12 whois.arin.net ALLOCATED
109/8 RIPE NCC 2009-01 whois.ripe.net ALLOCATED
110/8 APNIC 2008-11 whois.apnic.net ALLOCATED
111/8 APNIC 2008-11 whois.apnic.net ALLOCATED
112/8 APNIC 2008-05 whois.apnic.net ALLOCATED
113/8 APNIC 2008-05 whois.apnic.net ALLOCATED
114/8 APNIC 2007-10 whois.apnic.net ALLOCATED
115/8 APNIC 2007-10 whois.apnic.net ALLOCATED
116/8 APNIC 2007-01 whois.apnic.net ALLOCATED
117/8 APNIC 2007-01 whois.apnic.net ALLOCATED
118/8 APNIC 2007-01 whois.apnic.net ALLOCATED
119/8 APNIC 2007-01 whois.apnic.net ALLOCATED
120/8 APNIC 2007-01 whois.apnic.net ALLOCATED
121/8 APNIC 2006-01 whois.apnic.net ALLOCATED
122/8 APNIC 2006-01 whois.apnic.net ALLOCATED
123/8 APNIC 2006-01 whois.apnic.net ALLOCATED
124/8 APNIC 2005-01 whois.apnic.net ALLOCATED
125/8 APNIC 2005-01 whois.apnic.net ALLOCATED
126/8 APNIC 2005-01 whois.apnic.net ALLOCATED
127/8 IANA - Loopback 1981-09 RESERVED [5]
128/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
129/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
130/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
131/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
132/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
133/8 Administered by APNIC 1997-03 whois.apnic.net LEGACY
134/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
135/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
136/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
137/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
138/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
139/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
140/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
141/8 Administered by RIPE NCC 1993-05 whois.ripe.net LEGACY
142/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
143/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
144/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
145/8 Administered by RIPE NCC 1993-05 whois.ripe.net LEGACY
146/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
147/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
148/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
149/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
150/8 Administered by APNIC 1993-05 whois.apnic.net LEGACY
151/8 Administered by RIPE NCC 1993-05 whois.ripe.net LEGACY
152/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
153/8 Administered by APNIC 1993-05 whois.apnic.net LEGACY
154/8 Administered by AfriNIC 1993-05 whois.afrinic.net LEGACY
155/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
156/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
157/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
158/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
159/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
160/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
161/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
162/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
163/8 Administered by APNIC 1993-05 whois.apnic.net LEGACY
164/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
165/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
166/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
167/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
168/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
169/8 Administered by ARIN 1993-05 whois.arin.net LEGACY [6]
170/8 Administered by ARIN 1993-05 whois.arin.net LEGACY
171/8 Administered by APNIC 1993-05 whois.apnic.net LEGACY
172/8 Administered by ARIN 1993-05 whois.arin.net LEGACY [7]
173/8 ARIN 2008-02 whois.arin.net ALLOCATED
174/8 ARIN 2008-02 whois.arin.net ALLOCATED
175/8 APNIC 2009-08 whois.apnic.net ALLOCATED
176/8 RIPE NCC 2010-05 whois.ripe.net ALLOCATED
177/8 LACNIC 2010-06 whois.lacnic.net ALLOCATED
178/8 RIPE NCC 2009-01 whois.ripe.net ALLOCATED
179/8 LACNIC 2011-02 whois.lacnic.net ALLOCATED
180/8 APNIC 2009-04 whois.apnic.net ALLOCATED
181/8 LACNIC 2010-06 whois.lacnic.net ALLOCATED
182/8 APNIC 2009-08 whois.apnic.net ALLOCATED
183/8 APNIC 2009-04 whois.apnic.net ALLOCATED
184/8 ARIN 2008-12 whois.arin.net ALLOCATED
185/8 RIPE NCC 2011-02 whois.ripe.net ALLOCATED
186/8 LACNIC 2007-09 whois.lacnic.net ALLOCATED
187/8 LACNIC 2007-09 whois.lacnic.net ALLOCATED
188/8 Administered by RIPE NCC 1993-05 whois.ripe.net LEGACY
189/8 LACNIC 1995-06 whois.lacnic.net ALLOCATED
190/8 LACNIC 1995-06 whois.lacnic.net ALLOCATED
191/8 Administered by LACNIC 1993-05 whois.lacnic.net LEGACY
192/8 Administered by ARIN 1993-05 whois.arin.net LEGACY [8][9]
193/8 RIPE NCC 1993-05 whois.ripe.net ALLOCATED
194/8 RIPE NCC 1993-05 whois.ripe.net ALLOCATED
195/8 RIPE NCC 1993-05 whois.ripe.net ALLOCATED
196/8 Administered by AfriNIC 1993-05 whois.afrinic.net LEGACY
197/8 AfriNIC 2008-10 whois.afrinic.net ALLOCATED
198/8 Administered by ARIN 1993-05 whois.arin.net LEGACY [10]
199/8 ARIN 1993-05 whois.arin.net ALLOCATED
200/8 LACNIC 2002-11 whois.lacnic.net ALLOCATED
201/8 LACNIC 2003-04 whois.lacnic.net ALLOCATED
202/8 APNIC 1993-05 whois.apnic.net ALLOCATED
203/8 APNIC 1993-05 whois.apnic.net ALLOCATED [11]
204/8 ARIN 1994-03 whois.arin.net ALLOCATED
205/8 ARIN 1994-03 whois.arin.net ALLOCATED
206/8 ARIN 1995-04 whois.arin.net ALLOCATED
207/8 ARIN 1995-11 whois.arin.net ALLOCATED
208/8 ARIN 1996-04 whois.arin.net ALLOCATED
209/8 ARIN 1996-06 whois.arin.net ALLOCATED
210/8 APNIC 1996-06 whois.apnic.net ALLOCATED
211/8 APNIC 1996-06 whois.apnic.net ALLOCATED
212/8 RIPE NCC 1997-10 whois.ripe.net ALLOCATED
213/8 RIPE NCC 1993-10 whois.ripe.net ALLOCATED
214/8 US-DOD 1998-03 LEGACY
215/8 US-DOD 1998-03 LEGACY
216/8 ARIN 1998-04 whois.arin.net ALLOCATED
217/8 RIPE NCC 2000-06 whois.ripe.net ALLOCATED
218/8 APNIC 2000-12 whois.apnic.net ALLOCATED
219/8 APNIC 2001-09 whois.apnic.net ALLOCATED
220/8 APNIC 2001-12 whois.apnic.net ALLOCATED
221/8 APNIC 2002-07 whois.apnic.net ALLOCATED
222/8 APNIC 2003-02 whois.apnic.net ALLOCATED
223/8 APNIC 2010-04 whois.apnic.net ALLOCATED
224/8 Multicast 1981-09 RESERVED [12]
225/8 Multicast 1981-09 RESERVED [12]
226/8 Multicast 1981-09 RESERVED [12]
227/8 Multicast 1981-09 RESERVED [12]
228/8 Multicast 1981-09 RESERVED [12]
229/8 Multicast 1981-09 RESERVED [12]
230/8 Multicast 1981-09 RESERVED [12]
231/8 Multicast 1981-09 RESERVED [12]
232/8 Multicast 1981-09 RESERVED [12]
233/8 Multicast 1981-09 RESERVED [12]
234/8 Multicast 1981-09 RESERVED [12][13]
235/8 Multicast 1981-09 RESERVED [12]
236/8 Multicast 1981-09 RESERVED [12]
237/8 Multicast 1981-09 RESERVED [12]
238/8 Multicast 1981-09 RESERVED [12]
239/8 Multicast 1981-09 RESERVED [12][14]
240/8 Future use 1981-09 RESERVED [15]
241/8 Future use 1981-09 RESERVED [15]
242/8 Future use 1981-09 RESERVED [15]
243/8 Future use 1981-09 RESERVED [15]
244/8 Future use 1981-09 RESERVED [15]
245/8 Future use 1981-09 RESERVED [15]
246/8 Future use 1981-09 RESERVED [15]
247/8 Future use 1981-09 RESERVED [15]
248/8 Future use 1981-09 RESERVED [15]
249/8 Future use 1981-09 RESERVED [15]
250/8 Future use 1981-09 RESERVED [15]
251/8 Future use 1981-09 RESERVED [15]
252/8 Future use 1981-09 RESERVED [15]
253/8 Future use 1981-09 RESERVED [15]
254/8 Future use 1981-09 RESERVED [15]
255/8 Future use 1981-09 RESERVED [15][16]
Footnotes
[1] Indicates the status of address blocks as follows:
RESERVED: designated by the IETF for specific non-unicast purposes as noted.
LEGACY: allocated by the central Internet Registry (IR) prior to the Regional Internet Registries
(RIRs). This address space is now administered by individual RIRs as noted, including maintenance
of WHOIS Directory and reverse DNS records. Assignments from these blocks are distributed globally
on a regional basis.
ALLOCATED: delegated entirely to specific RIR as indicated.
UNALLOCATED: not yet allocated or reserved.
[2] 0.0.0.0/8 reserved for self-identification [RFC5735]
[3] Reserved for Private-Use Networks [RFC1918]
[4] This was reserved for Public Data Networks [RFC1356]
See: http://www.iana.org/assignments/public-data-network-numbers
It was recovered in February 2008 and was subsequently allocated to APNIC in April 2010
[5] 127.0.0.0/8 is reserved for Loopback [RFC5735]
[6] 169.254.0.0/16 reserved for Link Local [RFC5735]
[7] 172.16.0.0/12 reserved for Private-Use Networks [RFC1918]
[8] 192.0.2.0/24 reserved for TEST-NET-1 [RFC5737]
192.88.99.0/24 reserved for 6to4 Relay Anycast [RFC3068]
192.168.0.0/16 reserved for Private-Use Networks [RFC1918]
[9] 192.0.0.0/24 reserved for IANA IPv4 Special Purpose Address Registry [RFC5736]
[10] 198.18.0.0/15 reserved for Network Interconnect Device Benchmark Testing [RFC5735]
198.51.100.0/24 reserved for TEST-NET-2 [RFC5737]
[11] 203.0.113.0/24 reserved for TEST-NET-3 [RFC5737]
[12] Multicast (formerly "Class D") [RFC5771] registed in http://www.iana.org/assignments/multicast-addresses
[13] Unicast-Prefix-Based IPv4 Multicast Addresses [RFC6034]
[14] Administratively Scoped IP Multicast [RFC2365]
[15] Reserved for future use (formerly "Class E") [RFC1112]
[16] 255.255.255.255 is reserved for "limited broadcast" destination address [RFC0919] and [RFC0922]
http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt
.. or more simply put with a few examples:
Quote:How To Read Lists:
Each block of /8 Top Class A IPs = 16 Million IPv4 Addresses
Of the Top Level IPv4 Holders:
Department of Defense: 9 blocks of /8, thats 9 x 16 Million IPv4 Addresses.
Apple: 017/8 = 16 Million IPv4 Addresses
MIT: 018/8 = 16 Million IPv4 Addresses
Ford: 019/8 = 16 Million IPv4 Addresses
AT&T: 012/8 & 032/8 = thats 2 x 16 Million IPv4 Addresses
Halliburton: 034/8 = 16 Million IPv4 Addresses
US Postal Service: 056/8 = 16 Million IPv4 Addresses
http://forums.cnet.com/7723-10152_102-516104.html
The obvious answer as to why they need so many IP addresses is so that it a necessary step in assigning a static IP to everything, everyplace and everyone - and maybe something more abstract that I am missing.
This allows a unique identifier to be used in connected multirelational databases and establish a two way communication bridge to a centralized and/or networked collection system and send back communicate data or commands directly back to the source object, place or person AND/OR ANY OTHER SYSTEM CONNECTED TO THE NETWORK or indirectly by translating the communication protocol.
Not only that but efforts such as the
DNSSEC will act as a single catch-all relay and filtering system for the entire
Quote:Q: Why are we running out of IPv4 addresses?
A: IPv4 uses 32 bits for its Internet addresses. That means it can support 2^32 IP addresses in total — around 4.29 billion. That may seem like a lot, but all 4.29 billion IP addresses have now been assigned to various institutions, leading to the crisis we face today.
Let’s be clear, though: we haven’t run out of addresses quite yet. Many of them are unused and in the hands of institutions like MIT and companies like Ford and IBM. More IPv4 addresses are available to be assigned and more will be traded or sold (since IPv4 addresses are now a scarce resource), but they will become a scarcer commodity over the next two years until it creates problem for the web.
....
IPv6 utilizes 128-bit Internet addresses. Therefore, it can support 2^128 Internet addresses — 340,282,366,920,938,000,000,000,000,000,000,000,000 of them to be exact.
http://mashable.com/2011/02/03/ipv4-ipv6-guide/
I noticed that only global corporations based in the US were assigned massive blocs. Well that's will all, eventually, become a moot point as for new IP bloc ICANN has now shifted to become a global entity after being incubated by the US for the Web 1.0 protocol.
US Cedes Control ICANN, Internet.
http://concen.org/forum/showthread.php?tid=694
There is already a bit of forced compliance in the US and China to IPv6 and China is already a step ahead in creating IPV6 only infrastructure, thus showing the shape of things (planned) to come.
The reason I restored this thread was because it was an important pillar to lay the groundwork for the Internet of Things aka Real World Web aka SmartPlanet (IBM) aka CeNSE aka Smart Dust aka Web 2.0 that related to a post update last night. It took a good 4 hours to research, put it all together in a reasonably coherent way and find out what happened to this thread, which I eventually found was deleted from the forum . It follows up on the Smart Grid, Smart Dust, HP/Shell CeNSE and the DARPA Sensor Network research on I did previously and expands more into Smart Grid Deployment, Power Transmission Sensor Advances and the Real World Web that corporations and governments are elaborating on.
Check it out here: http://concen.org/forum/showthread.php?tid=33737&pid=234114#pid234114
So how long until this is installed globally? Well the US installed the Smart Grid nationwide pretty quickly over existing architecture.
Besides increasing the sheer number of IDs what else does the upgrade to IPV6 encompass that IPV4 did not?
Quote:IPv6 also implements additional features not present in IPv4. It simplifies aspects of address assignment (stateless address autoconfiguration), network renumbering and router announcements when changing Internet connectivity providers. The IPv6 subnet size has been standardized by fixing the size of the host identifier portion of an address to 64 bits to facilitate an automatic mechanism for forming the host identifier from link-layer media addressing information (MAC address). Network security is also integrated into the design of the IPv6 architecture, and the IPv6 specification mandates support for IPsec as a fundamental interoperability requirement.
The required IPsec authentication integrates the following Security Architecture:
* Authentication Headers (AH) provide connectionless integrity and data origin authentication for IP datagrams and provides protection against replay attacks.[5][6]
* Encapsulating Security Payloads (ESP) provide confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality.[1]
* Security Associations (SA) provide the bundle of algorithms and data that provide the parameters necessary to operate the AH and/or ESP operations. The Internet Security Association and Key Management Protocol (ISAKMP) provides a framework for authentication and key exchange,[7] with actual authenticated keying material provided either by manual configuration with pre-shared keys, Internet Key Exchange (IKE and IKEv2), Kerberized Internet Negotiation of Keys (KINK), or IPSECKEY DNS records.
http://en.wikipedia.org/wiki/IPv6
In short it means that it identifies and validates the connection utilizing multiple unique identifiers and forces a more rigid standard for communication in hardware, firmware and software.
The shift itself opens the door to install new standards, transfer/consolidate cyber-governance and IP bloc assignment and eliminate legacy devices' ability to interface across all layers encompassing the Link, Transport, Internet, and by extension from the transport layer the application layer. This enables the enforcement of a global closed app and closed device environment (see Apple's Business Model).
Taking it even further the control of the application layer allows control of the content, delivery, format, access and interface into it.
The European Space Agency also updated satellite equipment to IPV6 ... in 2004.
Quote:In order to illustrate native IPv6 deployment over satellite, two pilot demonstrations have been specified, implemented and performed. Both demonstrations used IPv6-capable DVB-S equipment developed in other ESA projects. The first demonstration was to show the usability of advanced services like IPsec, Mobile IPv6, and audio and video conferencing in a native IPv6 satellite network. For the second demonstration the SILK network, connecting academic and educational institutions residing in the Central Asian and Caucasian region to a hub station in Hamburg via DVB-S forward and SCPC return links, has been enhanced to support native IPv6 communication.
http://telecom.esa.int/telecom/www/object/index.cfm?fobjectid=11406
The internet was an expensive but calculated bribe to get this central nervous installed globally, along with sensors, wi-fi, bluetooth, RFID, cameras, cell phones...
Failing the all out refusal to adopt Real World Web we're set on a path to getting caught in it gradually ceding control of anything and everything connected to it, including ourselves. In the meantime we can utilize this resource of the internet during this window before it closes shut, wisely.