<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi Gert, <div class="moz-cite-prefix">Am 10.12.2014 um 20:02 schrieb Gert Doering: </div> <blockquote cite="mid:20141210190210.GF28745@Space.Net" type="cite"> <pre wrap="">So did you actually *deploy* IPv6, as in "every new service you run and install has IPv6 on it, every new product you build supports IPv6", or did you just *get* an IPv6 block, put it on a shelf, and leave it there? I'm impressed if our existing policy actually had such a big impact, and it wasn't just "the last nudge to get going" - which we could easily achieve by having the NCC IPRAs ensure that LIRs asking for a /22 are aware of IPv6 ("have you considered deploying IPv6?"). </pre> </blockquote> We really deployed IPv6 ;-) All servers used for customer software solutions and except for one service all our other services are IPv6 enabled. For sure, we still have some servers in our internal network that are not IPv6 capable (e.g. some print servers); for IPv6 we currently focus on everything that is publicly accessible (and on core components, for sure). Servers that are only used internally get IPv6 enabled on the next OS update or at the time the server will be replaced. I get your point that there is no use in allocation IPv6 space to an LIR if that space is not used; do you know whether statistical data is available how much IPv6 address space that has been allocated to those LIRs which requested their final /22 is actually visible in the BGP routing tables? Regards, Stefan </body> </html>