[address-policy-wg] RE: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs

How about getting RIPE-NCC to read it.... ;)
The remote feed page for the RIPE60 plenary has an embedded IPv4 address
rather than the fqdn.

            // netConnectionUrl defines where the streams are found 
            netConnectionUrl: 'rtmp://193.0.0.162/live'

Putting the IPv6 literal into VLC shows that the streamer is not even
listening on the IPv6 address of that machine because it just fails the
connect, where VLC crashes when trying to take the stream from the IPv4
literal. 


> -----Original Message-----
> From: ipv6-wg-admin at ripe.net [mailto:ipv6-wg-admin at ripe.net] On Behalf
> Of Mirjam Kuehne
> Sent: Wednesday, April 28, 2010 8:30 AM
> To: ipv6-wg at ripe.net
> Subject: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
> 
> Dear colleagues,
> 
> We looked at the "IPv6 ripeness" of all LIRs in the RIPE NCC service
> region. This was initially created to adjust our IPv6 training course
> depending on the country we are in. However, we felt this might also be
> valuable in a bigger context.
> 
> Please find the results and methodology on RIPE Labs:
> 
> http://labs.ripe.net/content/ipv6-ripeness
> 
> We would be interested to hear what you think about this idea in
> general
> and if you have any suggestions on how to modify or improve this.
> 
> Kind Regards,
> Mirjam Kühne
> RIPE NCC