TIM: Mon, 01 Oct 2012 21:30:13 +0000 -> Wed, 06 Feb 2013 08:40:04 +0000
SRC: VIA-Watcher/3.0
--- /daten/vwhois/iana-utils/ipv6-watcher/stable.xml	2012-10-01 23:30:13.000000000 +0200
+++ /daten/vwhois/iana-utils/ipv6-watcher/ipv6-unicast-address-assignments.xml	2013-02-06 09:40:04.000000000 +0100
@@ -6 +6 @@
-  <updated>2012-10-01</updated>
+  <updated>2013-02-06</updated>
@@ -10,5 +10,3 @@
-  <note>The assignable Global Unicast Address space is defined
-in <xref type="rfc" data="rfc4291"/> as being the address block defined by the
-prefix 2000::/3. All address space in this block not
-listed in the table below is reserved by IANA for
-future allocation.</note>
+  <note>The assignable Global Unicast Address space is defined in <xref type="rfc" data="rfc4291"/> as being the address 
+block defined by the prefix 2000::/3. All address space in this block not listed in the 
+table below is reserved by IANA for future allocation.</note>
@@ -121,0 +120 @@
+    <whois/>
@@ -193,0 +193 @@
+    <whois/>
@@ -251 +251,2 @@
-    <description>IANA</description>
+    <description>IANA</description>    
+    <whois/>
@@ -256 +257,2 @@
-    <description>IANA</description>
+    <description>IANA</description>    
+    <whois/>
@@ -261 +263,2 @@
-    <description>IANA</description>
+    <description>IANA</description>    
+    <whois/>
@@ -265 +268 @@
-    <prefix>3ffe::/16</prefix>
+    <prefix>3FFE::/16</prefix>
@@ -266,0 +270 @@
+    <whois/>
@@ -268 +272 @@
-    <xref type="note" data="9"/>
+    <xref type="note" data="9"/><xref type="note" data="10"/>
@@ -271,2 +275,3 @@
-    <prefix>5f00::/8</prefix>
-    <description>IANA</description>
+    <prefix>5F00::/8</prefix>
+    <description>IANA</description>    
+    <whois/>
@@ -277,5 +282,3 @@
-    See: <xref type="registry" data="iana-ipv6-special-registry"/></footnote>
-  <footnote anchor="2">2001:0DB8::/32 has been assigned as a NON-ROUTABLE 
-    range to be used for documentation purpose <xref type="rfc" data="rfc3849"/>.</footnote>
-  <footnote anchor="3">2001:3C00::/22 is reserved for possible future allocation 
-    to the RIPE NCC.</footnote>
+See: <xref type="registry" data="iana-ipv6-special-registry"/></footnote>
+  <footnote anchor="2">2001:0DB8::/32 has been assigned as a NON-ROUTABLE range to be used for documentation purposes <xref type="rfc" data="rfc3849"/>.</footnote>
+  <footnote anchor="3">2001:3C00::/22 is reserved for possible future allocation to the RIPE NCC.</footnote>
@@ -283,18 +286,13 @@
-  <footnote anchor="5">2A00:0000::/21 was originally allocated on 2005-04-19. 
-    2A01:0000::/23 was allocated on 2005-07-14. 2A01:0000::/16 (incorporating 
-    the 2A01:0000::/23) was allocated 2005-12-15. The more recent allocation
-    (2006-10-03) incorporates these previous allocations.</footnote>
-  <footnote anchor="6">2800:0000::/23 was allocated on 17 Nov 05.  The more recent 
-    allocation (2006-10-03) incorporates the previous allocation.</footnote>
-  <footnote anchor="7">2400:0000::/19 was allocated on 2005-05-20. 2400:2000::/19 
-    was allocated on 2005-07-08.  2400:4000::/21 was allocated on 2005-08-08.  
-    2404:0000::/23 was allocated on 2006-01-19.  The more recent allocation 
-    (2006-10-03) incorporates all these previous allocations.</footnote>
-  <footnote anchor="8">2600:0000::/22, 2604:0000::/22, 2608:0000::/22 and 
-    260C:0000::/22 were allocated on 2005-04-19. The more recent allocation 
-    (2006-10-03) incorporates all these previous allocations.</footnote>
-  <footnote anchor="9">3FFE:831F::/32 was used for Teredo in some old but widely 
-    distributed networking stacks. This usage is deprecated in favour of 2001::/32, 
-    which was allocated for the purpose in <xref type="rfc" data="rfc4380"/></footnote>
-  <footnote anchor="9">3ffe::/16 was used for the 6bone but was returned. <xref type="rfc" data="rfc5156"/></footnote>
-  <footnote anchor="10">5f00::/8 was used for the 6bone but was returned. <xref type="rfc" data="rfc5156"/></footnote>
+  <footnote anchor="5">2A00:0000::/21 was originally allocated on 2005-04-19. 2A01:0000::/23 was allocated on 2005-07-14. 
+2A01:0000::/16 (incorporating the 2A01:0000::/23) was allocated on 2005-12-15. The more recent allocation 
+(2006-10-03) incorporates these previous allocations.</footnote>
+  <footnote anchor="6">2800:0000::/23 was allocated on 2005-11-17. The more recent allocation (2006-10-03) incorporates the 
+previous allocation.</footnote>
+  <footnote anchor="7">2400:0000::/19 was allocated on 2005-05-20. 2400:2000::/19 was allocated on 2005-07-08. 2400:4000::/21 was 
+allocated on 2005-08-08.  2404:0000::/23 was allocated on 2006-01-19. The more recent allocation (2006-10-03) 
+incorporates all these previous allocations.</footnote>
+  <footnote anchor="8">2600:0000::/22, 2604:0000::/22, 2608:0000::/22 and 260C:0000::/22 were allocated on 2005-04-19. The more 
+recent allocation (2006-10-03) incorporates all these previous allocations.</footnote>
+  <footnote anchor="9">3FFE:831F::/32 was used for Teredo in some old but widely distributed networking stacks. This usage is 
+deprecated in favour of 2001::/32, which was allocated for the purpose in <xref type="rfc" data="rfc4380"/>.</footnote>
+  <footnote anchor="10">3FFE::/16 and 5F00::/8 were used for the 6bone but were returned. <xref type="rfc" data="rfc5156"/></footnote>