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

I did complain on the contact web page, but the only response has been the
robot letting me know that the message was received.  I also tried editing
the html source to put in the IPv6 literal and it sits in SYN_SENT mode.
This sounds like their choice of streamer app is the problem because it is
not binding to the IPv6 side. Given that assumption is correct, it would
make sense to put in an IPv4 literal because the fqdn would stall for all
IPv6 enabled clients. This raises the question about why they chose to use
that app for streaming.

Tony


> -----Original Message-----
> From: ipv6-wg-admin at ripe.net [mailto:ipv6-wg-admin at ripe.net] On Behalf
> Of Gert Doering
> Sent: Monday, May 03, 2010 6:06 AM
> To: Tony Hain
> Cc: 'Mirjam Kuehne'; ipv6-wg at ripe.net
> Subject: Re: [address-policy-wg] RE: [ipv6-wg] "IPv6 Ripeness"
> measurements on RIPE Labs
> 
> Hi,
> 
> (removing address-policy-wg from the CC: list)
> 
> On Mon, May 03, 2010 at 05:56:51AM -0700, Tony Hain wrote:
> > 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.
> 
> Seconded.  *complain*!
> 
> Gert Doering
> --
> Total number of prefixes smaller than registry allocations:  150584
> 
> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-
> Culemann
> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
> Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279