IPv6 Deployment Panel at ICANN, Lisbon
Hi, There will be an IPv6 Deployment Panel discussion at the ICANN meeting in Lisbon on Sunday 25 March between 1pm and 3pm (UTC+1). The session will focus on IPv6 deployment in the root DNS and ISP environments as well as looking at the policy support needed for this. The agenda and webcast links can be found on the meeting web site at: http://www.icann.org/meetings/lisbon/ the presentations will be made available before the session begins. As well as webcasting the session, remote participation will be possible through the ICANN public participation site, which allows registered users to ask questions and comment in chatrooms and forums. Please feel free to submit questions to the panel in advance or during the session, or use the blog facility to write about it afterwards. The site can be found at: http://public.icann.org/ And it can be reached through IPv6 as well as IPv4 :-) Thanks, -- Leo Vegoda IANA Numbers Liaison
Hi Leo, It is not reachable from me (2a01:d0::11:1) :( maxtul@office ~ $ ping public.icann.org PING public.icann.org (192.0.38.31) 56(84) bytes of data. 64 bytes from 192.0.38.31: icmp_seq=1 ttl=51 time=235 ms 64 bytes from 192.0.38.31: icmp_seq=2 ttl=51 time=251 ms --- public.icann.org ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 235.965/243.683/251.402/7.734 ms maxtul@office ~ $ ping6 public.icann.org PING public.icann.org(2001:1878:900:1::4) 56 data bytes --- public.icann.org ping statistics --- 8 packets transmitted, 0 received, 100% packet loss, time 6998ms maxtul@office ~ $ /usr/sbin/traceroute6 public.icann.org traceroute to public.icann.org (2001:1878:900:1::4) from 2a01:d0::11:1, 30 hops max, 24 byte packets 1 2a01:d0::11:2 (2a01:d0::11:2) 40.79 ms 34.218 ms 29.33 ms 2 2a01:d0::6:3 (2a01:d0::6:3) 105.722 ms 116.838 ms 109.799 ms 3 ser1-0-0-espanix-po6mbtx1.lab.bt.es (2001:ac0:100:1::1) 105.503 ms 97.197 ms 101.554 ms 4 2001:7f8:f::16 (2001:7f8:f::16) 260.479 ms 275.203 ms 273.469 ms 5 ge-0-1-0.r01.mdrdsp01.es.bb.gin.ntt.net (2001:728:0:2000::49) 264.848 ms 265.033 ms 262.95 ms 6 p16-0-0-3.r22.amstnl02.nl.bb.gin.ntt.net (2001:728:0:2000::9a) 261.868 ms 270.44 ms 257.946 ms 7 xe-0-2-0.r23.amstnl02.nl.bb.gin.ntt.net (2001:728:0:2000::1e) 267.963 ms 265.611 ms 264.576 ms 8 p64-1-1-0.r20.asbnva01.us.bb.gin.ntt.net (2001:418:0:2000::105) 265.36 ms 266.028 ms 268.349 ms 9 ae-0.r21.asbnva01.us.bb.gin.ntt.net (2001:418:0:2000::8e) 270.305 ms 267.817 ms 263.784 ms 10 p64-1-1-0.r20.dllstx09.us.bb.gin.ntt.net (2001:418:0:2000::20d) 266.906 ms 262.132 ms 270.733 ms 11 p64-1-0-0.r20.hstntx01.us.bb.gin.ntt.net (2001:418:0:2000::96) 267.124 ms 267.501 ms 270.304 ms 12 p64-2-1-0.r21.lsanca03.us.bb.gin.ntt.net (2001:418:0:2000::265) 265.067 ms 282.571 ms 266.888 ms 13 xe-7-3.r00.lsanca03.us.bb.gin.ntt.net (2001:418:0:2000::1a2) 274.879 ms 267.035 ms 281.627 ms 14 * * * 15 * How it can be fixed? Leo Vegoda wrote:
Hi,
There will be an IPv6 Deployment Panel discussion at the ICANN meeting in Lisbon on Sunday 25 March between 1pm and 3pm (UTC+1). The session will focus on IPv6 deployment in the root DNS and ISP environments as well as looking at the policy support needed for this.
The agenda and webcast links can be found on the meeting web site at:
http://www.icann.org/meetings/lisbon/
the presentations will be made available before the session begins.
As well as webcasting the session, remote participation will be possible through the ICANN public participation site, which allows registered users to ask questions and comment in chatrooms and forums. Please feel free to submit questions to the panel in advance or during the session, or use the blog facility to write about it afterwards. The site can be found at:
And it can be reached through IPv6 as well as IPv4 :-)
Thanks,
--Leo Vegoda IANA Numbers Liaison
-- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)
Hi Max, On Mar 22, 2007, at 1:53 PM, Max Tulyev wrote:
Hi Leo,
It is not reachable from me (2a01:d0::11:1) :(
It looks like your prefix is being filtered by an upstream ISP. We've contacted them and asked them to correct this. Regards, -- Leo Vegoda IANA Numbers Liaison
On Sat, 24 Mar 2007, Leo Vegoda wrote:
Hi Max,
Hi All,
On Mar 22, 2007, at 1:53 PM, Max Tulyev wrote:
Hi Leo,
It is not reachable from me (2a01:d0::11:1) :(
It looks like your prefix is being filtered by an upstream ISP. We've contacted them and asked them to correct this.
Go figure... some choose not to filter out 3ffe::'s while others are filtering IPv6 Unicast production address space. ;-)
Regards,
-- Leo Vegoda IANA Numbers Liaison
Best Regards, ------------------------------------------------------------------------- Carlos Friac,as See: Wide Area Network Working Group (WAN) www.gigapix.pt FCCN - Fundacao para a Computacao Cientifica Nacional www.ipv6.eu Av. do Brasil, n.101 www.6diss.org 1700-066 Lisboa www.geant2.net Tel: +351 218440100 Fax: +351 218472167 www.fccn.pt ------------------------------------------------------------------------- The end is near........ see http://www.potaroo.net/tools/ipv4/index.html "Internet is just routes (214049/730), naming (billions) and... people!" Aviso de Confidencialidade Esta mensagem e' exclusivamente destinada ao seu destinatario, podendo conter informacao CONFIDENCIAL, cuja divulgacao esta' expressamente vedada nos termos da lei. Caso tenha recepcionado indevidamente esta mensagem, solicitamos-lhe que nos comunique esse mesmo facto por esta via ou para o telefone +351 218440100 devendo apagar o seu conteudo de imediato. Warning This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail or by telephone +351 218440100 and delete it immediately.
On Sat, Mar 24, 2007 at 12:57:27PM +0000, Carlos Friacas wrote:
On Sat, 24 Mar 2007, Leo Vegoda wrote:
Hi Max,
Hi All,
On Mar 22, 2007, at 1:53 PM, Max Tulyev wrote:
Hi Leo,
It is not reachable from me (2a01:d0::11:1) :(
It looks like your prefix is being filtered by an upstream ISP. We've contacted them and asked them to correct this.
Go figure... some choose not to filter out 3ffe::'s while others are filtering IPv6 Unicast production address space. ;-)
I think there are some people that haven't woken up to the fact address space is being allocated out of more than just 2001:: now, for example I currently have some space from 2402:: (2402:8000::/32 specifically) and it seems a few people are possibly filtering this, among other things I can't get to isc.org. Cheers, Trent
Regards,
-- Leo Vegoda IANA Numbers Liaison
Best Regards,
------------------------------------------------------------------------- Carlos Friac,as See: Wide Area Network Working Group (WAN) www.gigapix.pt FCCN - Fundacao para a Computacao Cientifica Nacional www.ipv6.eu Av. do Brasil, n.101 www.6diss.org 1700-066 Lisboa www.geant2.net Tel: +351 218440100 Fax: +351 218472167 www.fccn.pt ------------------------------------------------------------------------- The end is near........ see http://www.potaroo.net/tools/ipv4/index.html "Internet is just routes (214049/730), naming (billions) and... people!"
Aviso de Confidencialidade Esta mensagem e' exclusivamente destinada ao seu destinatario, podendo conter informacao CONFIDENCIAL, cuja divulgacao esta' expressamente vedada nos termos da lei. Caso tenha recepcionado indevidamente esta mensagem, solicitamos-lhe que nos comunique esse mesmo facto por esta via ou para o telefone +351 218440100 devendo apagar o seu conteudo de imediato.
Warning This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail or by telephone +351 218440100 and delete it immediately.
On Sat, 24 Mar 2007, Trent Lloyd wrote:
It is not reachable from me (2a01:d0::11:1) :(
It looks like your prefix is being filtered by an upstream ISP. We've contacted them and asked them to correct this.
Go figure... some choose not to filter out 3ffe::'s while others are filtering IPv6 Unicast production address space. ;-)
I think there are some people that haven't woken up to the fact address space is being allocated out of more than just 2001:: now, for example I currently have some space from 2402:: (2402:8000::/32 specifically) and it seems a few people are possibly filtering this, among other things I can't get to isc.org.
Cheers, Trent
Good that you are complaining. It's the 1st step to see it solved! :-) Cheers, Carlos
On Sat, Mar 24, 2007 at 03:08:10PM +0000, Carlos Friacas wrote:
On Sat, 24 Mar 2007, Trent Lloyd wrote:
It is not reachable from me (2a01:d0::11:1) :(
It looks like your prefix is being filtered by an upstream ISP. We've contacted them and asked them to correct this.
Go figure... some choose not to filter out 3ffe::'s while others are filtering IPv6 Unicast production address space. ;-)
I think there are some people that haven't woken up to the fact address space is being allocated out of more than just 2001:: now, for example I currently have some space from 2402:: (2402:8000::/32 specifically) and it seems a few people are possibly filtering this, among other things I can't get to isc.org.
Cheers, Trent
Good that you are complaining. It's the 1st step to see it solved! :-)
Hehe, yes I've actually only just wised up to this being the reason for my poor visibility to some people. The SixXS GRH project has some highly usefull information, especially if you are actually peering with them. http://www.sixxs.net/tools/grh/ Jeroen pointed out the following URL which might be a more usefull guide to those configuring their filters http://www.space.net/~gert/RIPE/ipv6-filters.html Cheers, Trent
Cheers, Carlos
Carlos Friacas wrote: Hi Carlos et al, I am trying to figure out the reason for that. Well It is not my surprise that ISPs have not yet adopted the RPSLng for documenting their new IPv6 routing policies. So we are stuck by hardwired policies which are not be propagated in routing filters. Regards Dimitrios
On Sat, 24 Mar 2007, Trent Lloyd wrote:
It is not reachable from me (2a01:d0::11:1) :(
It looks like your prefix is being filtered by an upstream ISP. We've contacted them and asked them to correct this.
Go figure... some choose not to filter out 3ffe::'s while others are filtering IPv6 Unicast production address space. ;-)
I think there are some people that haven't woken up to the fact address space is being allocated out of more than just 2001:: now, for example I currently have some space from 2402:: (2402:8000::/32 specifically) and it seems a few people are possibly filtering this, among other things I can't get to isc.org.
Cheers, Trent
Good that you are complaining. It's the 1st step to see it solved! :-)
Cheers, Carlos
-- -- Dimitrios K. Kalogeras Electrical Engineer, Ph.D. Network Engineer NTUA/GR-Net Network Management Center _____________________________________ icq: 11887484 voice: +30-210-772 1863 fax: +30-210-772 1866 e-mail: D.Kalogeras@noc.ntua.gr pub 1024D/0E421B50 2007-01-17 [expires: 2008-01-17] Dimitrios Kalogeras (dkalo) <D.Kalogeras@noc.ntua.gr> Key fingerprint = F8C8 7B67 74A4 1F82 CDDF 8554 E1EF 7FAE 0E42 1B50 PGP-KEY: http://ajax.noc.ntua.gr/~dkalo/dkalo_pgp.txt
On Mon, 26 Mar 2007, Dimitrios Kalogeras wrote:
Carlos Friacas wrote:
Hi Carlos et al,
I am trying to figure out the reason for that. Well It is not my surprise that ISPs have not yet adopted the RPSLng for documenting their new IPv6 routing policies. So we are stuck by hardwired policies which are not be propagated in routing filters.
Regards Dimitrios
Yes. No surprise here too :-) (easy) work to be done...
On Sat, 24 Mar 2007, Trent Lloyd wrote:
It is not reachable from me (2a01:d0::11:1) :(
It looks like your prefix is being filtered by an upstream ISP. We've contacted them and asked them to correct this.
Go figure... some choose not to filter out 3ffe::'s while others are filtering IPv6 Unicast production address space. ;-)
I think there are some people that haven't woken up to the fact address space is being allocated out of more than just 2001:: now, for example I currently have some space from 2402:: (2402:8000::/32 specifically) and it seems a few people are possibly filtering this, among other things I can't get to isc.org.
Cheers, Trent
Good that you are complaining. It's the 1st step to see it solved! :-)
Cheers, Carlos
-- -- Dimitrios K. Kalogeras
Electrical Engineer, Ph.D. Network Engineer NTUA/GR-Net Network Management Center _____________________________________ icq: 11887484 voice: +30-210-772 1863 fax: +30-210-772 1866 e-mail: D.Kalogeras@noc.ntua.gr pub 1024D/0E421B50 2007-01-17 [expires: 2008-01-17] Dimitrios Kalogeras (dkalo) <D.Kalogeras@noc.ntua.gr> Key fingerprint = F8C8 7B67 74A4 1F82 CDDF 8554 E1EF 7FAE 0E42 1B50 PGP-KEY: http://ajax.noc.ntua.gr/~dkalo/dkalo_pgp.txt
------------------------------------------------------------------------- Carlos Friac,as See: Wide Area Network Working Group (WAN) www.gigapix.pt FCCN - Fundacao para a Computacao Cientifica Nacional www.ipv6.eu Av. do Brasil, n.101 www.6diss.org 1700-066 Lisboa www.geant2.net Tel: +351 218440100 Fax: +351 218472167 www.fccn.pt ------------------------------------------------------------------------- The end is near........ see http://www.potaroo.net/tools/ipv4/index.html "Internet is just routes (214049/730), naming (billions) and... people!" Aviso de Confidencialidade Esta mensagem e' exclusivamente destinada ao seu destinatario, podendo conter informacao CONFIDENCIAL, cuja divulgacao esta' expressamente vedada nos termos da lei. Caso tenha recepcionado indevidamente esta mensagem, solicitamos-lhe que nos comunique esse mesmo facto por esta via ou para o telefone +351 218440100 devendo apagar o seu conteudo de imediato. Warning This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail or by telephone +351 218440100 and delete it immediately.
Hi, On Mon, 26 Mar 2007, Dimitrios Kalogeras wrote:
I am trying to figure out the reason for that. Well It is not my surprise that ISPs have not yet adopted the RPSLng for documenting their new IPv6 routing policies. So we are stuck by hardwired policies which are not be propagated in routing filters.
Just as a data-point: many networks received their allocation before the RIPE DB supported route6 objects (thus couldn't add them, and have forgotten to do so after the support was added) or simply haven't known route6 objects should be added too. I believe in many cases the operators would be willing to add the objects if approached with a gentle reminder. Maybe someone should send such reminders? It'd maybe be best if RIPE NCC could do this, but I'm not sure if such operational checks are within their current toolbox.. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
Pekka Savola wrote:
Hi,
Hi Pekka, You are right RIPE-DB had some incapabilities at that time. However rtconfig had serious lack of concrete support for RPSLng in tools. I don't know whether we are facing a chicken-egg problem, where operators are reluctant to through away hardwired policies because there are not proven quality tools. and tools do not evolve beacuse we do not use them !. regards,
On Mon, 26 Mar 2007, Dimitrios Kalogeras wrote:
I am trying to figure out the reason for that. Well It is not my surprise that ISPs have not yet adopted the RPSLng for documenting their new IPv6 routing policies. So we are stuck by hardwired policies which are not be propagated in routing filters.
Just as a data-point: many networks received their allocation before the RIPE DB supported route6 objects (thus couldn't add them, and have forgotten to do so after the support was added) or simply haven't known route6 objects should be added too. I believe in many cases the operators would be willing to add the objects if approached with a gentle reminder.
Maybe someone should send such reminders? It'd maybe be best if RIPE NCC could do this, but I'm not sure if such operational checks are within their current toolbox..
I am not sure whether the route monitor project could aid in this direction. Regards, -- -- Dimitrios K. Kalogeras Electrical Engineer, Ph.D. Network Engineer NTUA/GR-Net Network Management Center _____________________________________ icq: 11887484 voice: +30-210-772 1863 fax: +30-210-772 1866 e-mail: D.Kalogeras@noc.ntua.gr pub 1024D/0E421B50 2007-01-17 [expires: 2008-01-17] Dimitrios Kalogeras (dkalo) <D.Kalogeras@noc.ntua.gr> Key fingerprint = F8C8 7B67 74A4 1F82 CDDF 8554 E1EF 7FAE 0E42 1B50 PGP-KEY: http://ajax.noc.ntua.gr/~dkalo/dkalo_pgp.txt
Hi, Thus wrote Dimitrios Kalogeras (D.Kalogeras@noc.ntua.gr):
You are right RIPE-DB had some incapabilities at that time. However rtconfig had serious lack of concrete support for RPSLng in tools.
But peval, also from the IRRToolSet suite, works fine. regards, Petra Zeidler
Hi, On Mon, Mar 26, 2007 at 03:40:47PM +0300, Pekka Savola wrote:
Maybe someone should send such reminders? It'd maybe be best if RIPE NCC could do this, but I'm not sure if such operational checks are within their current toolbox..
I've talked to all my downstreams, and they have all be very willing to add route6: objects and mp-import/mp-export clauses to their AS objects. As an extention, it would be good to talk if "you all" could talk to "all of your peers" (but yes, I know that this takes *lots* of time)... :) Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 98999 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
On 24-Mar-2007, at 09:58, Trent Lloyd wrote:
I think there are some people that haven't woken up to the fact address space is being allocated out of more than just 2001:: now, for example I currently have some space from 2402:: (2402:8000::/32 specifically) and it seems a few people are possibly filtering this, among other things I can't get to isc.org.
Send mail to noc@isc.org, and if there is a problem it will be fixed promptly. (I'd look right now, but I'm about to get on a plane.) Joe
The noc already has a ticket about this Sorry for the mess up Joao On 24 Mar 2007, at 20:20, Joe Abley wrote:
On 24-Mar-2007, at 09:58, Trent Lloyd wrote:
I think there are some people that haven't woken up to the fact address space is being allocated out of more than just 2001:: now, for example I currently have some space from 2402:: (2402:8000::/32 specifically) and it seems a few people are possibly filtering this, among other things I can't get to isc.org.
Send mail to noc@isc.org, and if there is a problem it will be fixed promptly. (I'd look right now, but I'm about to get on a plane.)
Joe
Hi, Going back to the subject on this message: I think the session was generally positive. Next time perhaps the term "Tutorial" should be dropped... this and the fact it was held from 13:00 to 15:00 on a sunday might have driven people away from it...... I specially did get a bad feeling about the question being raised by the jordan government person: didn't feel he got a proper and clear answer... imho he should have heard IPv6 should be something to have in mind because v4 address exaustion can in fact endanger internet companies' business in jordan (in the same way it will in every other country!) in the medium/long run. In fact, it's the second time i get the same feeling... once in an ITU IPv6 session someone did a simmilar question and nobody supplied a proper answer too... :-( I'm blaming myself for not having stepped up to the mike on that moment (despite a small crisis on the event's network i was trying to debug...), but i really hope next time someone speaks out loud why *everybody* should take v6 seriously. :-) Best Regards, ------------------------------------------------------------------------- Carlos Friac,as See: Wide Area Network Working Group (WAN) www.gigapix.pt FCCN - Fundacao para a Computacao Cientifica Nacional www.ipv6.eu Av. do Brasil, n.101 www.6diss.org 1700-066 Lisboa www.geant2.net Tel: +351 218440100 Fax: +351 218472167 www.fccn.pt ------------------------------------------------------------------------- The end is near........ see http://www.potaroo.net/tools/ipv4/index.html "Internet is just routes (214049/730), naming (billions) and... people!" Aviso de Confidencialidade Esta mensagem e' exclusivamente destinada ao seu destinatario, podendo conter informacao CONFIDENCIAL, cuja divulgacao esta' expressamente vedada nos termos da lei. Caso tenha recepcionado indevidamente esta mensagem, solicitamos-lhe que nos comunique esse mesmo facto por esta via ou para o telefone +351 218440100 devendo apagar o seu conteudo de imediato. Warning This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail or by telephone +351 218440100 and delete it immediately.
Hi Carlos, On Mar 26, 2007, at 12:17 PM, Carlos Friacas wrote:
Going back to the subject on this message: I think the session was generally positive. Next time perhaps the term "Tutorial" should be dropped... this and the fact it was held from 13:00 to 15:00 on a sunday might have driven people away from it......
I specially did get a bad feeling about the question being raised by the jordan government person: didn't feel he got a proper and clear answer... imho he should have heard IPv6 should be something to have in mind because v4 address exaustion can in fact endanger internet companies' business in jordan (in the same way it will in every other country!) in the medium/long run.
In fact, it's the second time i get the same feeling... once in an ITU IPv6 session someone did a simmilar question and nobody supplied a proper answer too... :-(
I'm blaming myself for not having stepped up to the mike on that moment (despite a small crisis on the event's network i was trying to debug...), but i really hope next time someone speaks out loud why *everybody* should take v6 seriously. :-)
Thanks for your feedback on the session. I know the timing and billing were not perfect. I'm sorry about that. If you add your comments and answer on the session web page (http:// public.icann.org/25mar/tutorial-ipv6), or write a blog on the public participation site it's likely that Mr Fraihat will see your answer there. Thanks, -- Leo Vegoda IANA Numbers Liaison
Hi, On Mon, Mar 26, 2007 at 12:17:30PM +0100, Carlos Friacas wrote:
Going back to the subject on this message: I think the session was generally positive. Next time perhaps the term "Tutorial" should be dropped... this and the fact it was held from 13:00 to 15:00 on a sunday might have driven people away from it......
Thanks for the positive feedback. (Actually, it was quite a novel experience to see your own words being typed in real-time on the transcript monitors... and yes, it did quite confuse me :) ).
I specially did get a bad feeling about the question being raised by the jordan government person: didn't feel he got a proper and clear answer... imho he should have heard IPv6 should be something to have in mind because v4 address exaustion can in fact endanger internet companies' business in jordan (in the same way it will in every other country!) in the medium/long run.
I thought I said something along the line of "it's a preparedness thing, for the time IPv4 runs out" - but maybe that wasn't clear enough. *Today*, there indeed is no cost saving in changing to IPv6 - but making sure all your gear is ready for IPv6 will save you money when you can't avoid IPv6 any longer.. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 98999 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
participants (10)
-
Carlos Friacas -
Dimitrios Kalogeras -
Gert Doering -
Joao Damas -
Joe Abley -
Leo Vegoda -
Max Tulyev -
Pekka Savola -
Petra Zeidler -
Trent Lloyd