"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
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@ripe.net [mailto:ipv6-wg-admin@ripe.net] On Behalf Of Mirjam Kuehne Sent: Wednesday, April 28, 2010 8:30 AM To: ipv6-wg@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
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
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@ripe.net [mailto:ipv6-wg-admin@ripe.net] On Behalf Of Gert Doering Sent: Monday, May 03, 2010 6:06 AM To: Tony Hain Cc: 'Mirjam Kuehne'; ipv6-wg@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)
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
On Mon, May 03, 2010 at 05:56:51AM -0700, Tony Hain wrote: 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
Hi Mirjam, On Wed, Apr 28, 2010 at 05:30:28PM +0200, Mirjam Kuehne wrote:
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:
You're asking for ideas for the "5th star". Some random thoughts... - have IPv6 transport (with addresses from their own prefix) to all/some of the DNS servers that the IPv6 reverse zone is delegated to - have www.<theirdomain> with working IPv6 connectivity (now, <theirdomain> might not be that easy to determine for some of the LIRs out there) - have IPv6 capable MXes for some/all of the listed contact e-mail addresses for the inet6num and/or the organization object Something revolving around "is actually moving bits over IPv6, instead of just sitting on the paperwork of having address + BGP + DNS in place" would be useful. Gert Doering -- NetMaster -- 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
Hi, On Mon, May 03, 2010 at 03:32:15PM +0200, Gert Doering wrote:
Something revolving around "is actually moving bits over IPv6, instead of just sitting on the paperwork of having address + BGP + DNS in place" would be useful.
The 6th star could be "has found a way to listen to the RIPE meeting stream over IPv6"... Indeed, what happened here? We had meeting streams over IPv6 5 years ago... Gert Doering -- NetMaster -- 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
Hay, Am 03.05.2010 15:39, schrieb Gert Doering:
Hi,
On Mon, May 03, 2010 at 03:32:15PM +0200, Gert Doering wrote:
Something revolving around "is actually moving bits over IPv6, instead of just sitting on the paperwork of having address + BGP + DNS in place" would be useful.
The 6th star could be "has found a way to listen to the RIPE meeting stream over IPv6"...
Indeed, what happened here? We had meeting streams over IPv6 5 years ago...
that just means that the NCC does get ZERO ipv6-ripeness stars for the RIPE60 meeting. The whole flash-java-ipv4only thing is a big step backwards anyways :-( -- ===================================================================== = Sascha Lenz SLZ-RIPE slz@baycix.de = = Network Design & Operations = = BayCIX GmbH, Landshut * PGP public Key on demand * = =====================================================================
Follow-up: Am 03.05.2010 16:43, schrieb Sascha Lenz: [...]
Indeed, what happened here? We had meeting streams over IPv6 5 years ago...
that just means that the NCC does get ZERO ipv6-ripeness stars for the RIPE60 meeting.
The whole flash-java-ipv4only thing is a big step backwards anyways :-(
...since it works now (thanks Brian & Team!), i only keep up complaining about thte flash-java things, but that's not relevant to the ipv6 wg so, i'm fine for now! You get all your ipv6-ripeness stars back :-) -- ===================================================================== = Sascha Lenz SLZ-RIPE slz@baycix.de = = Network Design & Operations = = BayCIX GmbH, Landshut * PGP public Key on demand * = =====================================================================
Hi, On Mon, May 03, 2010 at 04:56:47PM +0200, Sascha Lenz wrote:
You get all your ipv6-ripeness stars back :-)
Nah, the "Real Time Transcript" still uses v4-only. 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
Hay, Am 03.05.2010 17:14, schrieb Gert Doering:
Hi,
On Mon, May 03, 2010 at 04:56:47PM +0200, Sascha Lenz wrote:
You get all your ipv6-ripeness stars back :-)
Nah, the "Real Time Transcript" still uses v4-only.
right. The IRC Java thingy, too (at least here). But that is all included on my "flash-java, bad" ranting, that never can be good :-) No wonder it doesn't speak IPv6 properly. (Actually, i'm surprised it was that easy to enable IPv6 for the flash stream thing) -- ===================================================================== = Sascha Lenz SLZ-RIPE slz@baycix.de = = Network Design & Operations = = BayCIX GmbH, Landshut * PGP public Key on demand * = =====================================================================
Hi all, Thank you all for your feedback. The system used to stream video webcast of the RIPE Meeting for the past four years was not set up to stream over IPv6. The RIPE NCC Meeting Team has been working to remedy this over the past hour or so, and as of 16:30 (CEST) it is possible to access the RIPE Meeting video webstream over native IPv6: http://www.ripe.net/ripe/meetings/ripe-60/live/main-index.php Thank you to everyone who drew this matter to our attention. If you have any further questions or concerns, please send an email to <opsmtg@ripe.net
.
Regards, Brian Riddle IT Manager, RIPE NCC On 3 May 2010, at 15:39, Gert Doering wrote:
Hi,
On Mon, May 03, 2010 at 03:32:15PM +0200, Gert Doering wrote:
Something revolving around "is actually moving bits over IPv6, instead of just sitting on the paperwork of having address + BGP + DNS in place" would be useful.
The 6th star could be "has found a way to listen to the RIPE meeting stream over IPv6"...
Indeed, what happened here? We had meeting streams over IPv6 5 years ago...
Gert Doering -- NetMaster -- 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
Hi, On Mon, May 03, 2010 at 04:44:39PM +0200, Brian Riddle wrote:
Thank you all for your feedback. The system used to stream video webcast of the RIPE Meeting for the past four years was not set up to stream over IPv6. The RIPE NCC Meeting Team has been working to remedy this over the past hour or so, and as of 16:30 (CEST) it is possible to access the RIPE Meeting video webstream over native IPv6: http://www.ripe.net/ripe/meetings/ripe-60/live/main-index.php
Thanks! This is very good news, and I think we should see quite some v6 traffic peaks this week :-) Gert Doering -- NetMaster -- 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
For some reason I could not use the link provided. While it did replace the IPv4 literal with the fqdn, my system insisted on connecting IPv4 anyway. Someone did fix the app so that it is actually listening on IPv6 though because now I am getting the feed over an IPv6 literal based local hack on the html source. No it is not address selection preferring IPv4, because I have a local policy table that explicitly puts IPv4 after everything except 6over4 & SL. Precedence Label Prefix ---------- ----- -------------------------------- 90 0 ::1/128 80 8 2002::/16 65 1 fc00::/8 60 1 fd00::/8 50 2 2001::/16 50 2 2400::/8 50 2 2600::/8 50 2 2a00::/8 50 2 2c00::/8 30 3 2001::/32 20 4 ::/0 10 5 ::ffff:0:0/96 5 6 ::/96 4 6 fec0::/16 Earlier when I was playing around there was an error page returned from one of the RIPE url's complaining that it couldn't resolve the IPv6 ptr, so maybe that is part of the sequence and I can't tell from here. Tony
-----Original Message----- From: ipv6-wg-admin@ripe.net [mailto:ipv6-wg-admin@ripe.net] On Behalf Of Gert Doering Sent: Monday, May 03, 2010 7:54 AM To: Brian Riddle Cc: ipv6-wg@ripe.net; opsmtg@ripe.net Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Hi,
On Mon, May 03, 2010 at 04:44:39PM +0200, Brian Riddle wrote:
Thank you all for your feedback. The system used to stream video webcast of the RIPE Meeting for the past four years was not set up to stream over IPv6. The RIPE NCC Meeting Team has been working to remedy this over the past hour or so, and as of 16:30 (CEST) it is possible to access the RIPE Meeting video webstream over native IPv6: http://www.ripe.net/ripe/meetings/ripe-60/live/main-index.php
Thanks! This is very good news, and I think we should see quite some v6 traffic peaks this week :-)
Gert Doering -- NetMaster -- 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
For some reason the Flash thing is not working over IPv6 today. Also the RTSP streamer is not listening on IPv6. It appears that there is ~ 5 seconds delay for the Flash version wrt the RTSP stream. On the other hand the RTSP stream is very choppy and needs to rebuild the buffer every few minutes. Tony
-----Original Message----- From: Brian Riddle [mailto:briddle@ripe.net] Sent: Monday, May 03, 2010 7:45 AM To: ipv6-wg@ripe.net Cc: opsmtg@ripe.net; Tony Hain; Gert Doering; Mirjam Kuehne Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Hi all,
Thank you all for your feedback. The system used to stream video webcast of the RIPE Meeting for the past four years was not set up to stream over IPv6. The RIPE NCC Meeting Team has been working to remedy this over the past hour or so, and as of 16:30 (CEST) it is possible to access the RIPE Meeting video webstream over native IPv6: http://www.ripe.net/ripe/meetings/ripe-60/live/main-index.php
Thank you to everyone who drew this matter to our attention. If you have any further questions or concerns, please send an email to <opsmtg@ripe.net
.
Regards, Brian Riddle IT Manager, RIPE NCC
On 3 May 2010, at 15:39, Gert Doering wrote:
Hi,
On Mon, May 03, 2010 at 03:32:15PM +0200, Gert Doering wrote:
Something revolving around "is actually moving bits over IPv6, instead of just sitting on the paperwork of having address + BGP + DNS in place" would be useful.
The 6th star could be "has found a way to listen to the RIPE meeting stream over IPv6"...
Indeed, what happened here? We had meeting streams over IPv6 5 years ago...
Gert Doering -- NetMaster -- 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
For some reason the Flash thing is not working over IPv6 today. Also the RTSP streamer is not listening on IPv6. It appears that there is ~ 5 seconds delay for the Flash version wrt the RTSP stream. On the other hand the RTSP stream is very choppy and needs to rebuild the buffer every few minutes. Tony
-----Original Message----- From: Brian Riddle [mailto:briddle@ripe.net] Sent: Monday, May 03, 2010 7:45 AM To: ipv6-wg@ripe.net Cc: opsmtg@ripe.net; Tony Hain; Gert Doering; Mirjam Kuehne Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Hi all,
Thank you all for your feedback. The system used to stream video webcast of the RIPE Meeting for the past four years was not set up to stream over IPv6. The RIPE NCC Meeting Team has been working to remedy this over the past hour or so, and as of 16:30 (CEST) it is possible to access the RIPE Meeting video webstream over native IPv6: http://www.ripe.net/ripe/meetings/ripe-60/live/main-index.php
Thank you to everyone who drew this matter to our attention. If you have any further questions or concerns, please send an email to <opsmtg@ripe.net
.
Regards, Brian Riddle IT Manager, RIPE NCC
On 3 May 2010, at 15:39, Gert Doering wrote:
Hi,
On Mon, May 03, 2010 at 03:32:15PM +0200, Gert Doering wrote:
Something revolving around "is actually moving bits over IPv6, instead of just sitting on the paperwork of having address + BGP + DNS in place" would be useful.
The 6th star could be "has found a way to listen to the RIPE meeting stream over IPv6"...
Indeed, what happened here? We had meeting streams over IPv6 5 years ago...
Gert Doering -- NetMaster -- 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
Hi Tony, Thanks for letting us know. We've had a look and we are watching the stream over IPv6 without problems. The machine, qtstreamer.ripe.net is listening on port 1935 over IPv6 and we cant see any problems connecting. dhcp-26-179:~ bohara$ netstat -an |grep 1935 tcp6 0 0 2001:67c:64:42:2.65444 2001:610:240:5::.1935 ESTABLISHED As you can see above, im connected over v6 to the stream. Could you send us some further info, your IPv6 address, a traceroute to qtstreamer and try telneting to 1935 on the machine? As for the choppy nature of the video, we'll restart the tricaster which sends the stream to qtstreamer during the next break. We did see that the RTSP stream was unstable initially but was OK after it had got going. Any extra info you can provide will help us track down any problems. Cheers Ben On 6 May 2010, at 09:22, Tony Hain wrote:
For some reason the Flash thing is not working over IPv6 today. Also the RTSP streamer is not listening on IPv6. It appears that there is ~ 5 seconds delay for the Flash version wrt the RTSP stream. On the other hand the RTSP stream is very choppy and needs to rebuild the buffer every few minutes.
Tony
-----Original Message----- From: Brian Riddle [mailto:briddle@ripe.net] Sent: Monday, May 03, 2010 7:45 AM To: ipv6-wg@ripe.net Cc: opsmtg@ripe.net; Tony Hain; Gert Doering; Mirjam Kuehne Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Hi all,
Thank you all for your feedback. The system used to stream video webcast of the RIPE Meeting for the past four years was not set up to stream over IPv6. The RIPE NCC Meeting Team has been working to remedy this over the past hour or so, and as of 16:30 (CEST) it is possible to access the RIPE Meeting video webstream over native IPv6: http://www.ripe.net/ripe/meetings/ripe-60/live/main-index.php
Thank you to everyone who drew this matter to our attention. If you have any further questions or concerns, please send an email to <opsmtg@ripe.net
.
Regards, Brian Riddle IT Manager, RIPE NCC
On 3 May 2010, at 15:39, Gert Doering wrote:
Hi,
On Mon, May 03, 2010 at 03:32:15PM +0200, Gert Doering wrote:
Something revolving around "is actually moving bits over IPv6, instead of just sitting on the paperwork of having address + BGP + DNS in place" would be useful.
The 6th star could be "has found a way to listen to the RIPE meeting stream over IPv6"...
Indeed, what happened here? We had meeting streams over IPv6 5 years ago...
Gert Doering -- NetMaster -- 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
-- Ben O'Hara RIPE Network Coordination Center Systems Engineer Singel 258, Amsterdam, NL http://www.ripe.net +31 20 535 4444 PGP Fingerprint: 080A 52FF BF0A A7FB F176 E7DB 513D 9A3D E968 7DBC
Routing problem on my end causing the flash problem, but other sites are working??? Using a different interface for now so the IPv6 stream is back up. VLC is not able to connect to rtsp://[2001:610:240:5::162]:1935/live/ripe -- I know it doesn't like IPv6 literals so I created a host file entry for that address to make sure IPv6 was the only choice. In the past it has worked so I will keep poking at it. Given that the flash stream appears to be using ~ 30% less bandwidth, I am not overly motivated to get it working. Tony
-----Original Message----- From: ipv6-wg-admin@ripe.net [mailto:ipv6-wg-admin@ripe.net] On Behalf Of Ben O'Hara Sent: Thursday, May 06, 2010 12:32 AM To: alh-ietf@tndh.net Cc: 'Brian Riddle'; opsmtg@ripe.net; ipv6-wg@ripe.net Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Hi Tony,
Thanks for letting us know.
We've had a look and we are watching the stream over IPv6 without problems.
The machine, qtstreamer.ripe.net is listening on port 1935 over IPv6 and we cant see any problems connecting.
dhcp-26-179:~ bohara$ netstat -an |grep 1935 tcp6 0 0 2001:67c:64:42:2.65444 2001:610:240:5::.1935 ESTABLISHED
As you can see above, im connected over v6 to the stream.
Could you send us some further info, your IPv6 address, a traceroute to qtstreamer and try telneting to 1935 on the machine?
As for the choppy nature of the video, we'll restart the tricaster which sends the stream to qtstreamer during the next break. We did see that the RTSP stream was unstable initially but was OK after it had got going.
Any extra info you can provide will help us track down any problems.
Cheers Ben
On 6 May 2010, at 09:22, Tony Hain wrote:
For some reason the Flash thing is not working over IPv6 today. Also the RTSP streamer is not listening on IPv6. It appears that there is ~ 5 seconds delay for the Flash version wrt the RTSP stream. On the other hand the RTSP stream is very choppy and needs to rebuild the buffer every few minutes.
Tony
-----Original Message----- From: Brian Riddle [mailto:briddle@ripe.net] Sent: Monday, May 03, 2010 7:45 AM To: ipv6-wg@ripe.net Cc: opsmtg@ripe.net; Tony Hain; Gert Doering; Mirjam Kuehne Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Hi all,
Thank you all for your feedback. The system used to stream video webcast of the RIPE Meeting for the past four years was not set up to stream over IPv6. The RIPE NCC Meeting Team has been working to remedy this over the past hour or so, and as of 16:30 (CEST) it is possible to access the RIPE Meeting video webstream over native IPv6: http://www.ripe.net/ripe/meetings/ripe-60/live/main-index.php
Thank you to everyone who drew this matter to our attention. If you have any further questions or concerns, please send an email to <opsmtg@ripe.net
.
Regards, Brian Riddle IT Manager, RIPE NCC
On 3 May 2010, at 15:39, Gert Doering wrote:
Hi,
On Mon, May 03, 2010 at 03:32:15PM +0200, Gert Doering wrote:
Something revolving around "is actually moving bits over IPv6, instead of just sitting on the paperwork of having address + BGP + DNS in place" would be useful.
The 6th star could be "has found a way to listen to the RIPE meeting stream over IPv6"...
Indeed, what happened here? We had meeting streams over IPv6 5 years ago...
Gert Doering -- NetMaster -- 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
-- Ben O'Hara RIPE Network Coordination Center Systems Engineer Singel 258, Amsterdam, NL http://www.ripe.net +31 20 535 4444 PGP Fingerprint: 080A 52FF BF0A A7FB F176 E7DB 513D 9A3D E968 7DBC
Routing problem on my end causing the flash problem, but other sites are working??? Using a different interface for now so the IPv6 stream is back up. VLC is not able to connect to rtsp://[2001:610:240:5::162]:1935/live/ripe -- I know it doesn't like IPv6 literals so I created a host file entry for that address to make sure IPv6 was the only choice. In the past it has worked so I will keep poking at it. Given that the flash stream appears to be using ~ 30% less bandwidth, I am not overly motivated to get it working. Tony
-----Original Message----- From: ipv6-wg-admin@ripe.net [mailto:ipv6-wg-admin@ripe.net] On Behalf Of Ben O'Hara Sent: Thursday, May 06, 2010 12:32 AM To: alh-ietf@tndh.net Cc: 'Brian Riddle'; opsmtg@ripe.net; ipv6-wg@ripe.net Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Hi Tony,
Thanks for letting us know.
We've had a look and we are watching the stream over IPv6 without problems.
The machine, qtstreamer.ripe.net is listening on port 1935 over IPv6 and we cant see any problems connecting.
dhcp-26-179:~ bohara$ netstat -an |grep 1935 tcp6 0 0 2001:67c:64:42:2.65444 2001:610:240:5::.1935 ESTABLISHED
As you can see above, im connected over v6 to the stream.
Could you send us some further info, your IPv6 address, a traceroute to qtstreamer and try telneting to 1935 on the machine?
As for the choppy nature of the video, we'll restart the tricaster which sends the stream to qtstreamer during the next break. We did see that the RTSP stream was unstable initially but was OK after it had got going.
Any extra info you can provide will help us track down any problems.
Cheers Ben
On 6 May 2010, at 09:22, Tony Hain wrote:
For some reason the Flash thing is not working over IPv6 today. Also the RTSP streamer is not listening on IPv6. It appears that there is ~ 5 seconds delay for the Flash version wrt the RTSP stream. On the other hand the RTSP stream is very choppy and needs to rebuild the buffer every few minutes.
Tony
-----Original Message----- From: Brian Riddle [mailto:briddle@ripe.net] Sent: Monday, May 03, 2010 7:45 AM To: ipv6-wg@ripe.net Cc: opsmtg@ripe.net; Tony Hain; Gert Doering; Mirjam Kuehne Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Hi all,
Thank you all for your feedback. The system used to stream video webcast of the RIPE Meeting for the past four years was not set up to stream over IPv6. The RIPE NCC Meeting Team has been working to remedy this over the past hour or so, and as of 16:30 (CEST) it is possible to access the RIPE Meeting video webstream over native IPv6: http://www.ripe.net/ripe/meetings/ripe-60/live/main-index.php
Thank you to everyone who drew this matter to our attention. If you have any further questions or concerns, please send an email to <opsmtg@ripe.net
.
Regards, Brian Riddle IT Manager, RIPE NCC
On 3 May 2010, at 15:39, Gert Doering wrote:
Hi,
On Mon, May 03, 2010 at 03:32:15PM +0200, Gert Doering wrote:
Something revolving around "is actually moving bits over IPv6, instead of just sitting on the paperwork of having address + BGP + DNS in place" would be useful.
The 6th star could be "has found a way to listen to the RIPE meeting stream over IPv6"...
Indeed, what happened here? We had meeting streams over IPv6 5 years ago...
Gert Doering -- NetMaster -- 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
-- Ben O'Hara RIPE Network Coordination Center Systems Engineer Singel 258, Amsterdam, NL http://www.ripe.net +31 20 535 4444 PGP Fingerprint: 080A 52FF BF0A A7FB F176 E7DB 513D 9A3D E968 7DBC
Hi Tony, Thanks for letting us know. I get an error in VLNC when trying rtsp://[2001:610:240:5::162]:1935/live/ripe as it doesnt like the v6 address, however using qtstreamer.ripe.net which has AAAA and A records VLC connects over IPv6. Glad your now able to watch the stream anyway. Cheers Ben On 6 May 2010, at 10:02, Tony Hain wrote:
Routing problem on my end causing the flash problem, but other sites are working??? Using a different interface for now so the IPv6 stream is back up.
VLC is not able to connect to rtsp://[2001:610:240:5::162]:1935/live/ripe -- I know it doesn't like IPv6 literals so I created a host file entry for that address to make sure IPv6 was the only choice. In the past it has worked so I will keep poking at it. Given that the flash stream appears to be using ~ 30% less bandwidth, I am not overly motivated to get it working.
Tony
-----Original Message----- From: ipv6-wg-admin@ripe.net [mailto:ipv6-wg-admin@ripe.net] On Behalf Of Ben O'Hara Sent: Thursday, May 06, 2010 12:32 AM To: alh-ietf@tndh.net Cc: 'Brian Riddle'; opsmtg@ripe.net; ipv6-wg@ripe.net Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Hi Tony,
Thanks for letting us know.
We've had a look and we are watching the stream over IPv6 without problems.
The machine, qtstreamer.ripe.net is listening on port 1935 over IPv6 and we cant see any problems connecting.
dhcp-26-179:~ bohara$ netstat -an |grep 1935 tcp6 0 0 2001:67c:64:42:2.65444 2001:610:240:5::.1935 ESTABLISHED
As you can see above, im connected over v6 to the stream.
Could you send us some further info, your IPv6 address, a traceroute to qtstreamer and try telneting to 1935 on the machine?
As for the choppy nature of the video, we'll restart the tricaster which sends the stream to qtstreamer during the next break. We did see that the RTSP stream was unstable initially but was OK after it had got going.
Any extra info you can provide will help us track down any problems.
Cheers Ben
On 6 May 2010, at 09:22, Tony Hain wrote:
For some reason the Flash thing is not working over IPv6 today. Also the RTSP streamer is not listening on IPv6. It appears that there is ~ 5 seconds delay for the Flash version wrt the RTSP stream. On the other hand the RTSP stream is very choppy and needs to rebuild the buffer every few minutes.
Tony
-----Original Message----- From: Brian Riddle [mailto:briddle@ripe.net] Sent: Monday, May 03, 2010 7:45 AM To: ipv6-wg@ripe.net Cc: opsmtg@ripe.net; Tony Hain; Gert Doering; Mirjam Kuehne Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Hi all,
Thank you all for your feedback. The system used to stream video webcast of the RIPE Meeting for the past four years was not set up to stream over IPv6. The RIPE NCC Meeting Team has been working to remedy this over the past hour or so, and as of 16:30 (CEST) it is possible to access the RIPE Meeting video webstream over native IPv6: http://www.ripe.net/ripe/meetings/ripe-60/live/main-index.php
Thank you to everyone who drew this matter to our attention. If you have any further questions or concerns, please send an email to <opsmtg@ripe.net
.
Regards, Brian Riddle IT Manager, RIPE NCC
On 3 May 2010, at 15:39, Gert Doering wrote:
Hi,
On Mon, May 03, 2010 at 03:32:15PM +0200, Gert Doering wrote:
Something revolving around "is actually moving bits over IPv6, instead of just sitting on the paperwork of having address + BGP + DNS in place" would be useful.
The 6th star could be "has found a way to listen to the RIPE meeting stream over IPv6"...
Indeed, what happened here? We had meeting streams over IPv6 5 years ago...
Gert Doering -- NetMaster -- 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
-- Ben O'Hara RIPE Network Coordination Center Systems Engineer Singel 258, Amsterdam, NL http://www.ripe.net +31 20 535 4444 PGP Fingerprint: 080A 52FF BF0A A7FB F176 E7DB 513D 9A3D E968 7DBC
-- Ben O'Hara RIPE Network Coordination Center Systems Engineer Singel 258, Amsterdam, NL http://www.ripe.net +31 20 535 4444 PGP Fingerprint: 080A 52FF BF0A A7FB F176 E7DB 513D 9A3D E968 7DBC
The streaming has been very good - left my browser open through the event and it's kept running just fine, IPv6 all the time without problem. Compared to many other events the extra camera angles really help to make remote participation a better experience. Tim On Thu, May 06, 2010 at 10:16:49AM +0200, Ben O'Hara wrote:
Hi Tony,
Thanks for letting us know.
I get an error in VLNC when trying [1]rtsp://[2001:610:240:5::162]:1935/live/ripe as it doesnt like the v6 address, however using [2]qtstreamer.ripe.net which has AAAA and A records VLC connects over IPv6.
Glad your now able to watch the stream anyway.
Cheers
Ben On 6 May 2010, at 10:02, Tony Hain wrote:
Routing problem on my end causing the flash problem, but other sites are working??? Using a different interface for now so the IPv6 stream is back up. VLC is not able to connect to [3]rtsp://[2001:610:240:5::162]:1935/live/ripe -- I know it doesn't like IPv6 literals so I created a host file entry for that address to make sure IPv6 was the only choice. In the past it has worked so I will keep poking at it. Given that the flash stream appears to be using ~ 30% less bandwidth, I am not overly motivated to get it working. Tony
-----Original Message-----
From: [4]ipv6-wg-admin@ripe.net [mailto:ipv6-wg-admin@ripe.net] On Behalf
Of Ben O'Hara
Sent: Thursday, May 06, 2010 12:32 AM
To: [5]alh-ietf@tndh.net
Cc: 'Brian Riddle'; [6]opsmtg@ripe.net; [7]ipv6-wg@ripe.net
Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Hi Tony,
Thanks for letting us know.
We've had a look and we are watching the stream over IPv6 without
problems.
The machine, [8]qtstreamer.ripe.net is listening on port 1935 over IPv6
and we cant see any problems connecting.
dhcp-26-179:~ bohara$ netstat -an |grep 1935
tcp6 0 0 2001:67c:64:42:2.65444 2001:610:240:5::.1935
ESTABLISHED
As you can see above, im connected over v6 to the stream.
Could you send us some further info, your IPv6 address, a traceroute to
qtstreamer and try telneting to 1935 on the machine?
As for the choppy nature of the video, we'll restart the tricaster
which sends the stream to qtstreamer during the next break. We did see
that the RTSP stream was unstable initially but was OK after it had got
going.
Any extra info you can provide will help us track down any problems.
Cheers
Ben
On 6 May 2010, at 09:22, Tony Hain wrote:
For some reason the Flash thing is not working over IPv6 today. Also
the
RTSP streamer is not listening on IPv6. It appears that there is ~ 5
seconds
delay for the Flash version wrt the RTSP stream. On the other hand
the RTSP
stream is very choppy and needs to rebuild the buffer every few
minutes.
Tony
-----Original Message-----
From: Brian Riddle [mailto:briddle@ripe.net]
Sent: Monday, May 03, 2010 7:45 AM
To: [9]ipv6-wg@ripe.net
Cc: [10]opsmtg@ripe.net; Tony Hain; Gert Doering; Mirjam Kuehne
Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
Hi all,
Thank you all for your feedback. The system used to stream video
webcast of the RIPE Meeting for the past four years was not set up
to
stream over IPv6. The RIPE NCC Meeting Team has been working to
remedy
this over the past hour or so, and as of 16:30 (CEST) it is possible
to access the RIPE Meeting video webstream over native IPv6:
[11]http://www.ripe.net/ripe/meetings/ripe-60/live/main-index.php
Thank you to everyone who drew this matter to our attention. If you
have any further questions or concerns, please send an email to
<[12]opsmtg@ripe.net
.
Regards,
Brian Riddle
IT Manager, RIPE NCC
On 3 May 2010, at 15:39, Gert Doering wrote:
Hi,
On Mon, May 03, 2010 at 03:32:15PM +0200, Gert Doering wrote:
Something revolving around "is actually moving bits over IPv6,
instead
of just sitting on the paperwork of having address + BGP + DNS in
place"
would be useful.
The 6th star could be "has found a way to listen to the RIPE
meeting
stream
over IPv6"...
Indeed, what happened here? We had meeting streams over IPv6 5
years ago...
Gert Doering
-- NetMaster
--
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
--
Ben O'Hara RIPE Network Coordination Center
Systems Engineer Singel 258, Amsterdam, NL
[13]http://www.ripe.net +31 20 535 4444
PGP Fingerprint: 080A 52FF BF0A A7FB F176 E7DB 513D 9A3D E968 7DBC
-- Ben O'Hara RIPE Network Coordination Center Systems Engineer Singel 258, Amsterdam, NL [14]http://www.ripe.net +31 20 535 4444 PGP Fingerprint: 080A 52FF BF0A A7FB F176 E7DB 513D 9A3D E968 7DBC
References
1. rtsp://[2001:610:240:5::162]:1935/live/ripe 2. http://qtstreamer.ripe.net/ 3. rtsp://[2001:610:240:5::162]:1935/live/ripe 4. mailto:ipv6-wg-admin@ripe.net 5. mailto:alh-ietf@tndh.net 6. mailto:opsmtg@ripe.net 7. mailto:ipv6-wg@ripe.net 8. http://qtstreamer.ripe.net/ 9. mailto:ipv6-wg@ripe.net 10. mailto:opsmtg@ripe.net 11. http://www.ripe.net/ripe/meetings/ripe-60/live/main-index.php 12. mailto:opsmtg@ripe.net 13. http://www.ripe.net/ 14. http://www.ripe.net/
-- Tim
* Gert Doering wrote:
You're asking for ideas for the "5th star". Some random thoughts...
- have IPv6 transport (with addresses from their own prefix) to all/some of the DNS servers that the IPv6 reverse zone is delegated to
- have www.<theirdomain> with working IPv6 connectivity (now, <theirdomain> might not be that easy to determine for some of the LIRs out there)
- have IPv6 capable MXes for some/all of the listed contact e-mail addresses for the inet6num and/or the organization object
I second that. The draft-haberman-rpsl-reachable-test proposal is unusable: Update FAILED: [route6] 2001:4bd8::/32AS15725 ***Error: Syntax error in object route6: 2001:4bd8::/32 descr: DE-IKS-JENA origin: AS15725 mnt-by: IKS-MNT pingable: 2001:4bd8::4000:0:0:196 ***Error: "pingable" is not a known RPSL attribute ping-hdl: IKS-RIPE ***Error: "ping-hdl" is not a known RPSL attribute ... Update FAILED: [route] 217.17.192.0/20AS15725 ***Error: Syntax error in object route: 217.17.192.0/20 descr: DE-IKS-JENA origin: AS15725 mnt-by: IKS-MNT pingable: 217.17.192.196 ***Error: "pingable" is not a known RPSL attribute ping-hdl: IKS-RIPE ***Error: "ping-hdl" is not a known RPSL attribute ... Gert's tests are much more easy to fulfill: You might monitor (reverse) DNS queries on your system (to see who is resolving via IPv6 and who is queried for rDNSv6) ;; AUTHORITY SECTION: 8.d.b.4.1.0.0.2.ip6.arpa. NS avalon.iks-jena.de. 8.d.b.4.1.0.0.2.ip6.arpa. NS jengate.thur.de. ;; Query time: 114 msec ;; SERVER: 2001:610:240:0:53::3#53(2001:610:240:0:53::3) You might monitor your mailserver log to see which systems does send or receive emails via IPv6: May 3 15:51:03 annwfn sm-mta[17288]: o43DoqKp017288: to=<auto-dbm@ripe.net>, delay=00:00:09, xdelay=00:00:09, mailer=esmtp, pri=31240, relay=postgirl.ripe.net. [IPv6:2001:610:240:11::c100:1342], dsn=2.0.0, stat=Sent (OK id=1O8w30-0008Kf-CC) May 3 15:51:08 excalibur sm-mta[6518]: o43Dp6js006518: from=<unread@ripe.net>, size=2642, class=0, nrcpts=6, msgid=<20100503135105.6EBD89B1AC@cello.ripe.net>, proto=ESMTP, daemon=MTA, relay=beaver.ipv6.ripe.net [IPv6:2001:610:240:11::c100:131d] But your own mailinglist server should be upgraded first: May 3 15:07:11 excalibur sm-mta[19888]: o43D79XZ019888: from=<ipv6-wg-admin@ripe.net>, size=3142, class=0, nrcpts=1, msgid=<20100503130627.GB60850@Space.Net>, proto=ESMTP, daemon=MTA, relay=postboy.ripe.net [193.0.19.3] LIR's website is difficult to determine. You might add a field on the LIR portal at https://lirportal.ripe.net/lirportal/liruser/general.html OTOH what is IPv6 delivery of website? How many parts come via IPv6 how many via IPv4? Take our website www.iks-jena.de as an example. It delivers - dual stacked - all content via IPv6, but if IPv6 is enabled, the show remote client address is displayed as IPv6 AND IPv4 at the same time. Is this IPv6 enabled?
Thank you, Gert, and Lutz, for very concrete suggestions. On 5/3/10 3:32 PM, Gert Doering wrote:
You're asking for ideas for the "5th star". Some random thoughts...
We have received a lot of private answers (mostly in addition to requesting a T-shirt ;-) , and will summarize them *soon* and post them here and to the RIPE Labs forum. Greetings from a very busy RIPE 60, Vesna
On Mon, 3 May 2010, Gert Doering wrote:
You're asking for ideas for the "5th star". Some random thoughts...
- have IPv6 transport (with addresses from their own prefix) to all/some of the DNS servers that the IPv6 reverse zone is delegated to
For the purposes of automation, I'd say "at least one of the (reverse) DNS servers for the prefix answers to a DNS query over v6" should be sufficient, and better than the two first alternatives. While there may be some small relevance whether the DNS server is from another prefix, it would result in false negatives in the cases where a (somehow defined) organisation is using multiple prefixes (e.g. due to mergers etc.). That would be confusing. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
Dear colleagues, As a follow-up to the IPv6 ripeness article published on RIPE Labs last week, we created a little movie (Thanks, Emile!) that shows the IPv6 ripeness ratings of most countries in the RIPE region over time (for the period between January 2004 and May 2010). See the movie on RIPE Labs: http://labs.ripe.net. You can also download the file and watch it in a different media player. Kind Regards, Mirjam Kühne RIPE NCC Mirjam Kuehne wrote:
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
* Mirjam Kuehne wrote:
As a follow-up to the IPv6 ripeness article published on RIPE Labs last week, we created a little movie (Thanks, Emile!) that shows the IPv6 ripeness ratings of most countries in the RIPE region over time (for the period between January 2004 and May 2010).
Great video. Thank you all.
Hi Mirjam, One suggestion, which should increase awareness on the good Ripeness initiative and its importance, is to measure on a country basis the IPv4 rate of consumption, or v4's 'Witherness' , and this can use historical data that RIPE has already. For example, the number v4 addresses being reserved per year on a country basis can be presented over the past 5 year period, and LIRs can use this data to know when v6 readiness has to happen. Regards, -Ahmed -------------------------------------------------- From: "Mirjam Kuehne" <mir@ripe.net> Sent: Wednesday, April 28, 2010 6:30 PM To: <ipv6-wg@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
On Sat, May 29, 2010 at 12:41 PM, Ahmed Abu-Abed <ahmed@tamkien.com> wrote:
Hi Mirjam,
One suggestion, which should increase awareness on the good Ripeness initiative and its importance, is to measure on a country basis the IPv4 rate of consumption, or v4's 'Witherness' , and this can use historical data that RIPE has already. For example, the number v4 addresses being reserved per year on a country basis can be presented over the past 5 year period, and LIRs can use this data to know when v6 readiness has to happen.
IIRC, there is no "reservation per country" in IPv4 (or v6). It's one pool, not one pool of adddresses per country. -- Cheers, McTim "A name indicates what we seek. An address indicates where it is. A route indicates how we get there." Jon Postel
Data on IPv4 and v6 assignments per country is already published; see the link in my original post below. Similar information has also been presented in various forms during regional meetings by RIPE NCC. My question is where/how can we get *the rate* of v4 consumption on a country basis ? This is necessary to raise awareness at the local level. Regards, -Ahmed -------------------------------------------------- From: "McTim" <dogwallah@gmail.com> Sent: Saturday, May 29, 2010 12:50 PM To: "Ahmed Abu-Abed" <ahmed@tamkien.com> Cc: "Mirjam Kuehne" <mir@ripe.net>; <ipv6-wg@ripe.net> Subject: Re: [ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs
On Sat, May 29, 2010 at 12:41 PM, Ahmed Abu-Abed <ahmed@tamkien.com> wrote:
Hi Mirjam,
One suggestion, which should increase awareness on the good Ripeness initiative and its importance, is to measure on a country basis the IPv4 rate of consumption, or v4's 'Witherness' , and this can use historical data that RIPE has already. For example, the number v4 addresses being reserved per year on a country basis can be presented over the past 5 year period, and LIRs can use this data to know when v6 readiness has to happen.
IIRC, there is no "reservation per country" in IPv4 (or v6). It's one pool, not one pool of adddresses per country.
-- Cheers,
McTim "A name indicates what we seek. An address indicates where it is. A route indicates how we get there." Jon Postel
Hi On 29 May 2010, at 10:41, Ahmed Abu-Abed wrote:
and LIRs can use this data to know when v6 readiness has to happen.
Are you suggesting that v6 readiness doesn't have to happen now ?
For example, the number v4 addresses being reserved per year on a country basis can be presented over the past 5 year period
I am not sure why the per country is relevant - each country will have a mix of ISPs with varying sizes and growth patterns, it does not appear to be a good metric to group data points with. Although I do accept that it may be a good metric in the ITU world:-) Cheers f
participants (13)
-
Ahmed Abu-Abed -
Ben O'Hara -
Brian Riddle -
Fearghas McKay -
Gert Doering -
Lutz Donnerhacke -
McTim -
Mirjam Kuehne -
Pekka Savola -
Sascha Lenz -
Tim Chown -
Tony Hain -
Vesna Manojlovic