- ipv6-wg - mailman.ripe.net

IPv6 conference in September
by Gert Doering 11 May '07

11 May '07

Hi, (re-sending this because yesterday's mail was sent from a non-subscribed mail address and got stuck in the moderator's queue) Date: Thu, 10 May 2007 17:10:24 +0200 From: Gert Doering Subject: IPv6 conference in September Hi, as mentioned in the IPv6 WG: there is an IPv6 conference coming up in Cologne, Germany, this year (September 06+07): http://www.guug.de/veranstaltungen/ecai6-2007/ (I am not related to Guug, but there is a given chance that I'll show up and give a talk, so I'm not fully neutral :-)) gert -- Total number of prefixes smaller than registry allocations: 113403 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

1 0

IPv6 conference in September
by Gert Doering 10 May '07

10 May '07

Hi, as mentioned in the IPv6 WG: there is an IPv6 conference coming up in Cologne, Germany, this year (September 06+07): http://www.guug.de/veranstaltungen/ecai6-2007/ (I am not related to Guug, but there is a given chance that I'll show up and give a talk, so I'm not fully neutral :-)) gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert(a)greenie.muc.de fax: +49-89-35655025 gert(a)net.informatik.tu-muenchen.de

1 0

IPV6 problem
by praveen ch 07 May '07

07 May '07

Hi, I am facing a new problem while doing testing with IPV6. I am getting "Cannot assign requested address". Can you help me why i am getting that error. Waiting for your reply. -- Regards, praveen chebolu

2 1

Agenda for ipv6 wg RIPE54
by David Kessens 07 May '07

07 May '07

During next RIPE meeting, our working group is scheduled to meet: Thu May 10, 17:00 - 18:00 in Grande Room, Sokos Viru Hotel, Tallinn Please see below for our agenda. Many of our agenda items ask for participation of the working group. I would like to encourage everybody to take part in our discussions. Thanks and see you in Tallinn! David Kessens --- Agenda for the IPv6 Working Group Meeting RIPE54 When: Thu May 10, 17:00 - 18:00 in room Grande Room, Sokos Viru Hotel, Tallinn Where: Grande Room, Sokos Viru Hotel, Tallinn A. Administrative stuff - appointment of scribe - agenda bashing - approval of the minutes (David Kessens) B. Quick update from the RIPE NCC regarding ipv6 services (RIPE NCC) C. Problems with: Route Header Type 0 (Merike Kaeo) - did we already find other problems as well ? (discussion) D. Follow-up: IPv6 in large cable systems (discussion) - other operators with similar problems - IPv6 and network management E. Follow-up: Global IPv6 routing table status (discussion) (Gert Doering) F. Feedback and experience with Windows Vista (discussion) (input from the audience) G. Report(s) about *actual* v6 traffic volume as compared to v4? *what's real* out there, not what's on powerpoint? (input from the audience) H. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) ... Y. Input for the RIPE NCC Activity Plan (input from the audience) Z. AOB ---

1 0

Draft agenda (v1) for ipv6 wg RIPE54
by David Kessens 30 Apr '07

30 Apr '07

During next RIPE meeting, our working group is scheduled to meet: Thu, May 10, 17:00 - 18:00 in Grande Room, Sokos Viru Hotel, Tallinn I have prepared a draft agenda with all our standard items and a few more. We still have a little bit of time that we can use for additional agenda topics so feel free to send me any suggestions. In addition, I would very much appreciate your help if you are able to provide us with a few thought provoking slides/remarks regarding some of the discussion items on the agenda. Thanks! David Kessens --- Draft Agenda (v1) for the IPv6 Working Group Meeting RIPE53 When: Thu, May 10, 17:00 - 18:00 in room Grande Room, Sokos Viru Hotel, Tallinn Where: Grande Room, Sokos Viru Hotel, Tallinn A. Administrative stuff - appointment of scribe - agenda bashing - approval of the minutes (David Kessens) B. Quick update from the RIPE NCC regarding ipv6 services (RIPE NCC) C. Problems with: Route Header Type 0 - did we already find other problems as well ? (discussion, presentations welcome!) D. Follow-up: IPv6 in large cable systems (discussion) - other operators with similar problems - IPv6 and network management E. Follow-up: Global IPv6 routing table status (discussion) (Gert Doering) F. Feedback and experience with Windows Vista (discussion) (input from the audience) G. Report(s) about *actual* v6 traffic volume as compared to v4? *what's real* out there, not what's on powerpoint? (input from the audience) H. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) ... Y. Input for the RIPE NCC Activity Plan (input from the audience) Z. AOB ---

1 0

Call for agenda items
by David Kessens 24 Apr '07

24 Apr '07

Hi, The next RIPE meeting is getting close. That means that we will have to get our agenda together as soon as possible. Our session is scheduled for: Thursday, May 10 17:00 - 18:00 in room Grande Room I plan on sending out the first draft agenda by the end of the week. To do this, I will need your help to volunteer a talk or discussion topic that is relevant for the deployment of ipv6 in the RIPE region. Any topic, no matter how short and/or if you are new to our working group is welcome as long as the topic is relevant for our working group. Thanks, David Kessens ---

1 0

Accommodating IPv6 Address RRs for the Root of the Domain Name System
by JORDI PALET MARTINEZ 28 Mar '07

28 Mar '07

http://www.ipv6tf.org/news/counter.php?id=2743 ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.org This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

1 0

IPv6 Deployment Panel at ICANN, Lisbon
by Leo Vegoda 27 Mar '07

27 Mar '07

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

10 17

IPv6 Deployment Panel at ICANN Meeting, Lisbon
by Axel Pawlik 26 Mar '07

26 Mar '07

[Apologies for duplicate e-mails.] Dear Colleagues, An IPv6 deployment panel discussion was held at the ICANN meeting in Lisbon on Sunday 25 March between 13:00 and 15:00 (UTC+1). The session focused on IPv6 deployment in the root DNS and ISP environments as well as the policy support needed for this. The panel consisted of Gert Doering from SpaceNet AG, who discussed the ISPs' view of IPv6 deployment, Joao Damas from Internet Systems Consortium (ISC) who discussed IPv6 deployment in the DNS and Alex Le Heux from the RIPE NCC who gave the Regional Internet Registry (RIR) perspective. The agenda, webcast and presentations can be found on the meeting website at: http://www.icann.org/meetings/lisbon/ Remote participation was possible through the ICANN public participation site, which allowed registered users to ask questions and comment in chatrooms and forums. The site can be found at: http://public.icann.org/ The site can be reached through IPv6 as well as IPv4. Regards, Axel Pawlik Managing Director RIPE NCC

1 0

RE: [ipv6-wg] 2006 IPv4 Address Use Report
by Tanya Hinman 02 Jan '07

02 Jan '07

Hey there Ray! Are these actually statistics or parameters, and are either available at this time for IPv6 and IPv4? I would be interested in seeing them, especially would like to update my view of how IPv6 is being utilized at this time. Thanks, Tanya > From: plzak(a)arin.net> To: iljitsch(a)muada.com; emmiesan(a)msn.com> CC: ipv6-wg(a)ripe.net> Subject: RE: [ipv6-wg] 2006 IPv4 Address Use Report> Date: Tue, 2 Jan 2007 08:08:33 -0500> > I would think that an interesting statistic to look at would be the> consumption rates by region and by the top 10 economy/country consumers in> both IPv4 and IPv6. I would also look at the percentage of the allocated> IPv6 resources by region and by the top 10 economy/country consumers.> > Ray > > > -----Original Message-----> > From: ipv6-wg-admin(a)ripe.net [mailto:ipv6-wg-admin@ripe.net] On Behalf Of> > Iljitsch van Beijnum> > Sent: Tuesday, January 02, 2007 5:33 AM> > To: Tanya Hinman> > Cc: ipv6-wg(a)ripe.net> > Subject: Re: [ipv6-wg] 2006 IPv4 Address Use Report> > > > On 1-jan-2007, at 23:53, Tanya Hinman wrote:> > > > > Is the decrease in the percentage of used IPv4 space in the United> > > States of America due to other countries increasing their usage and/> > > or the return of unused IPv4 space in the United States of America?> > > Just looking at upcoming usage statistics globally.> > > > A year ago, the US held 1324.93 million addresses out of a total of> > 2238.04 million = 59.2% (apparently I rounded off incorrectly with my> > 60% figure).> > > > Yesterday's total is 2407.11 so for the US to maintain its 59.2% it> > would have to hold 1425 million addresses, which is an increase of> > exactly 100 million addresses. But the US didn't get 100 million> > addresses last year, but "only" 41.66 million for a total of 1366.53> > (56.8%).> > > > So the US keeps growing, and still uses up a quarter of the new> > addresses given out in 2006, but the rest of the world grows faster> > so the US lead is diminishing.> _________________________________________________________________ Get into the holiday spirit, chat with Santa on Messenger. http://imagine-windowslive.com/minisites/santabot/default.aspx?locale=en-us

2 1

RE: [ipv6-wg] 2006 IPv4 Address Use Report
by Tanya Hinman 02 Jan '07

02 Jan '07

Hello all, I have been out of the IP field for a few years so forgive me if my question is about old news, but here it is: Is the decrease in the percentage of used IPv4 space in the United States of America due to other countries increasing their usage and/or the return of unused IPv4 space in the United States of America? Just looking at upcoming usage statistics globally. Thanks, Tanya Hinman, RN +1 919 272 1835 > To: ipv6-wg(a)ripe.net; address-policy-wg(a)ripe.net> From: iljitsch(a)muada.com> Subject: [ipv6-wg] 2006 IPv4 Address Use Report> Date: Mon, 1 Jan 2007 17:27:08 +0100> > 2006 was another busy year for the five Regional Internet Registries: > together, they gave out 161.48 million IPv4 addresses, just shy of > the 165.45 million given out in 2005 as measured on january first 2006.> > The current (jan 1st, 2007) figure for 2005 is 175.52 million > addresses. Together with adjustments for earlier years, this brings > the total addresses available to almost exactly 1.3 billion, down > from 1468.61 million a year ago. This is out of 3706.65 million > usable IPv4 addresses, so 2407.11 million addresses are currently > given out to either end-users or Internet Service Providers.> > Breakdown by Regional Internet Registry over the past few years as > seen on 2007-01-01:> > 2000 2001 2002 2003 2004 2005 2006> > AfriNIC 0.56 0.39 0.26 0.22 0.51 1.03 2.72> APNIC 20.94 28.83 27.03 33.05 42.89 53.86 51.78> ARIN 30.83 28.55 21.08 22.32 34.26 47.57 38.94> LACNIC 0.88 1.61 0.65 2.62 3.77 10.97 11.50> RIPE NCC 24.79 25.36 19.84 29.61 47.49 62.09 56.53> > Total 78.00 84.73 68.87 87.82 128.92 175.52 161.48> > Compare this to the totals as seen on 2006-01-01:> > Total 78.35 88.95 68.93 87.77 128.45 165.45> > (See last year's report for more details at http://www.bgpexpert.com/ > addrspace2005.php )> > The main reason for the discrepancy is that the RIRs publish on their > respective FTP servers lists of which address block was given out > when. When a block of address space is given back by the holder, it's > removed from the list. This is the reason why the numbers for earlier > years keep going down. The 10 million extra addresses in 2005 and 4 > million in 2001 are the responsibility of ARIN, which went from 36.30 > million addresses for 2005 in their 2006-01-01 records to 47.56 in > their 2007-01-01 records. The reason for the retroactive growth is > unknown.> > AfriNIC gives out address space in Africa, APNIC in the Asia-Pacific > region, ARIN in North America, LACNIC in Latin American and the > Caribbean and the RIPE NCC in Europe, the former Soviet Union and the > Middle East.> > The Internet Assigned Numbers Authority (IANA, part of ICANN) keeps > an overview of the IPv4 address space at http://www.iana.org/ > assignments/ipv4-address-space. The list consists of 256 blocks of > 16.78 million addresses. Breakdown:> > Delegated to Blocks +/- 2006 Addresses (millions)> > AfriNIC 1 16.78> APNIC 19 +3 318.77> ARIN 27 +4 452.98> LACNIC 4 67.11> RIPE NCC 22 +3 369.10> Various 50 838.86> End-user 43 721.42> Available 55 -10 922.74> > Of the 2063.60 million addresses delegated to the five Regional > Internet Registries, 1685.69 million have been delegated to end-users > or ISPs by the RIRs, and 377.91 million are still available, which is > almost identical to last year's 378.09 number. Along with the 922.74 > million addresses still available in the IANA global pool this makes > the total number of available addresses 1300.65 million, down 167.96 > million from a year earlier.> > The size of address blocks given has been increasing steadily. The > table below shows the number of requests for a certain range of block > sizes (equal or higher than the first, lower than the second value).> > (2005 and earlier values from 2006-01-01 data, 2006 values from > 2007-01-01 data.)> > 2000 2001 2002 2003 2004 2005 2006> > < 1000 326 474 547 745 1022 1309 1526> 1000 - 8000 652 1176 897 1009 1516 1891 2338> 8000 - 64k 1440 868 822 1014 1100 1039 1133> 64k - 500k 354 262 163 215 404 309 409> 500k - 2M 19 39 29 46 61 60 56> > 2M 3 5 5 6 7 18 13> > The number of blocks in the two smallest categories have increased > rapidly, but not as fast as the number of blocks in the largest > category, in relative numbers at least. However, the increase in > large blocks has a very dramatic effect while the small blocks are > insignificant, when looking at the millions of addresses involved:> > 2000 2001 2002 2003 2004 2005 2006> > < 1000 0.10 0.16 0.18 0.25 0.35 0.44 0.52> 1000 - 8000 2.42 4.47 3.23 3.45 4.49 5.07 6.10> 8000 - 64k 18.79 12.81 11.35 14.00 15.99 15.46 17.17> 64k - 500k 35.98 32.19 20.28 25.51 42.01 34.23 49.64> 500k - 2M 12.68 24.64 21.30 31.98 44.63 41.63 46.64> > 2M 8.39 14.68 12.58 12.58 20.97 68.62 41.42> > The increase in the 2M+ blocks was solely responsible for the high > number of addresses given out in 2005. In 2006, there was growth in > all categories except the 2M+ one (even the 500k - 2M category > increased in number of addresses if not in number of blocks). When > the 2M+ blocks are taken out of the equation, 2005 had a total of > 96.83 million addresses (2006-01-01) and 2006 119.06 million given out.> > Another way to look at the same data:> > Year Blocks Addresses (M) Average block size> > 2000 2794 78.35 28043> 2001 2824 88.95 31497> 2002 2463 68.93 27985> 2003 3035 87.77 28921> 2004 4110 128.45 31252> 2005 4626 165.45 35765> 2006 5475 161.48 29494> > The 2407.11 million addresses currently in use aren't very evenly > distributed over the countries in the world. The current top 15 is:> > Country Addresses 2007-01-01 Addr 2006-01-01> > US 1366.53 M 1324.93 M United States> JP 151.27 M 143.00 M Japan> EU 115.83 M 113.87 M Multi-country in > Europe> CN 98.02 M 74.39 M China> GB 93.91 M 73.81 M United Kingdom> CA 71.32 M 67.43 M Canada> DE 61.59 M 51.13 M Germany> FR 58.23 M 45.16 M France> KR 51.13 M 41.91 M Korea> AU 30.64 M 26.87 M Australia> BR 19.27 M 17.17 M Brazil> IT 19.14 M 18.39 M Italy> ES 18.69 M 16.29 M Spain> TW 18.16 M 16.28 M Taiwan> NL 18.08 M 16.40 M Netherlands> > The US holds 57% (down from 60% a year ago) of the IPv4 address space > in use. The other countries in the list together hold another 34% (up > from 32%). The rest of the world has 9% (up from 8%).> > A copy of this information and a tool to perform queries on up to > date data is available at http://www.bgpexpert.com/addrspace2006.php> _________________________________________________________________ Fixing up the home? Live Search can help. http://imagine-windowslive.com/search/kits/default.aspx?kit=improve&locale=…

4 4

2006 IPv4 Address Use Report
by Iljitsch van Beijnum 01 Jan '07

01 Jan '07

2006 was another busy year for the five Regional Internet Registries: together, they gave out 161.48 million IPv4 addresses, just shy of the 165.45 million given out in 2005 as measured on january first 2006. The current (jan 1st, 2007) figure for 2005 is 175.52 million addresses. Together with adjustments for earlier years, this brings the total addresses available to almost exactly 1.3 billion, down from 1468.61 million a year ago. This is out of 3706.65 million usable IPv4 addresses, so 2407.11 million addresses are currently given out to either end-users or Internet Service Providers. Breakdown by Regional Internet Registry over the past few years as seen on 2007-01-01: 2000 2001 2002 2003 2004 2005 2006 AfriNIC 0.56 0.39 0.26 0.22 0.51 1.03 2.72 APNIC 20.94 28.83 27.03 33.05 42.89 53.86 51.78 ARIN 30.83 28.55 21.08 22.32 34.26 47.57 38.94 LACNIC 0.88 1.61 0.65 2.62 3.77 10.97 11.50 RIPE NCC 24.79 25.36 19.84 29.61 47.49 62.09 56.53 Total 78.00 84.73 68.87 87.82 128.92 175.52 161.48 Compare this to the totals as seen on 2006-01-01: Total 78.35 88.95 68.93 87.77 128.45 165.45 (See last year's report for more details at http://www.bgpexpert.com/ addrspace2005.php ) The main reason for the discrepancy is that the RIRs publish on their respective FTP servers lists of which address block was given out when. When a block of address space is given back by the holder, it's removed from the list. This is the reason why the numbers for earlier years keep going down. The 10 million extra addresses in 2005 and 4 million in 2001 are the responsibility of ARIN, which went from 36.30 million addresses for 2005 in their 2006-01-01 records to 47.56 in their 2007-01-01 records. The reason for the retroactive growth is unknown. AfriNIC gives out address space in Africa, APNIC in the Asia-Pacific region, ARIN in North America, LACNIC in Latin American and the Caribbean and the RIPE NCC in Europe, the former Soviet Union and the Middle East. The Internet Assigned Numbers Authority (IANA, part of ICANN) keeps an overview of the IPv4 address space at http://www.iana.org/ assignments/ipv4-address-space. The list consists of 256 blocks of 16.78 million addresses. Breakdown: Delegated to Blocks +/- 2006 Addresses (millions) AfriNIC 1 16.78 APNIC 19 +3 318.77 ARIN 27 +4 452.98 LACNIC 4 67.11 RIPE NCC 22 +3 369.10 Various 50 838.86 End-user 43 721.42 Available 55 -10 922.74 Of the 2063.60 million addresses delegated to the five Regional Internet Registries, 1685.69 million have been delegated to end-users or ISPs by the RIRs, and 377.91 million are still available, which is almost identical to last year's 378.09 number. Along with the 922.74 million addresses still available in the IANA global pool this makes the total number of available addresses 1300.65 million, down 167.96 million from a year earlier. The size of address blocks given has been increasing steadily. The table below shows the number of requests for a certain range of block sizes (equal or higher than the first, lower than the second value). (2005 and earlier values from 2006-01-01 data, 2006 values from 2007-01-01 data.) 2000 2001 2002 2003 2004 2005 2006 < 1000 326 474 547 745 1022 1309 1526 1000 - 8000 652 1176 897 1009 1516 1891 2338 8000 - 64k 1440 868 822 1014 1100 1039 1133 64k - 500k 354 262 163 215 404 309 409 500k - 2M 19 39 29 46 61 60 56 > 2M 3 5 5 6 7 18 13 The number of blocks in the two smallest categories have increased rapidly, but not as fast as the number of blocks in the largest category, in relative numbers at least. However, the increase in large blocks has a very dramatic effect while the small blocks are insignificant, when looking at the millions of addresses involved: 2000 2001 2002 2003 2004 2005 2006 < 1000 0.10 0.16 0.18 0.25 0.35 0.44 0.52 1000 - 8000 2.42 4.47 3.23 3.45 4.49 5.07 6.10 8000 - 64k 18.79 12.81 11.35 14.00 15.99 15.46 17.17 64k - 500k 35.98 32.19 20.28 25.51 42.01 34.23 49.64 500k - 2M 12.68 24.64 21.30 31.98 44.63 41.63 46.64 > 2M 8.39 14.68 12.58 12.58 20.97 68.62 41.42 The increase in the 2M+ blocks was solely responsible for the high number of addresses given out in 2005. In 2006, there was growth in all categories except the 2M+ one (even the 500k - 2M category increased in number of addresses if not in number of blocks). When the 2M+ blocks are taken out of the equation, 2005 had a total of 96.83 million addresses (2006-01-01) and 2006 119.06 million given out. Another way to look at the same data: Year Blocks Addresses (M) Average block size 2000 2794 78.35 28043 2001 2824 88.95 31497 2002 2463 68.93 27985 2003 3035 87.77 28921 2004 4110 128.45 31252 2005 4626 165.45 35765 2006 5475 161.48 29494 The 2407.11 million addresses currently in use aren't very evenly distributed over the countries in the world. The current top 15 is: Country Addresses 2007-01-01 Addr 2006-01-01 US 1366.53 M 1324.93 M United States JP 151.27 M 143.00 M Japan EU 115.83 M 113.87 M Multi-country in Europe CN 98.02 M 74.39 M China GB 93.91 M 73.81 M United Kingdom CA 71.32 M 67.43 M Canada DE 61.59 M 51.13 M Germany FR 58.23 M 45.16 M France KR 51.13 M 41.91 M Korea AU 30.64 M 26.87 M Australia BR 19.27 M 17.17 M Brazil IT 19.14 M 18.39 M Italy ES 18.69 M 16.29 M Spain TW 18.16 M 16.28 M Taiwan NL 18.08 M 16.40 M Netherlands The US holds 57% (down from 60% a year ago) of the IPv4 address space in use. The other countries in the list together hold another 34% (up from 32%). The rest of the world has 9% (up from 8%). A copy of this information and a tool to perform queries on up to date data is available at http://www.bgpexpert.com/addrspace2006.php

1 0

New IPv6 block allocated to RIPE NCC
by leo vegoda 18 Oct '06

18 Oct '06

[Apologies for duplicate mails] Dear Colleagues, The RIPE NCC received the IPv6 address range 2a00::/12 from the IANA in October 2006. This allocation expands two previous allocations. We will begin allocating from this new space in the near future. The minimum allocation size for this /12 has been set at /32. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html Regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

2001:502:d399::1
by Max Tulyev 10 Oct '06

10 Oct '06

Hi! Can anybody reach 2001:502:d399::1? It is the DNS server listed in the .org and some other TLDs. Now I'm getting ICMP6 host unreachable and DNS slows down slightly, -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

4 3

Comercial IPv6 availability in the Nordics
by Hans Petter Holen 04 Oct '06

04 Oct '06

This spring I renegotiated our corporate VPN and Internet agreements. In the request for interest/proposals I among other things asked for IPv6 availability. Since I the company I work for, Visma, has offices in Norway, Sweden, Denmark and Finland there was not that many ISPs to ask. >From the 4 that was able to offer service in all the Nordic countries only one of them answered Yes - but added "not for production - we do not offer any SLA on this service yet." -hph (and yes - I did choose the provider that said they could offer IPv6 - but for other reasons like price and SLA conditions)

2 1

Agenda for ipv6 wg RIPE53
by David Kessens 29 Sep '06

29 Sep '06

During the next RIPE meeting, our working group is scheduled to meet: Wed Oct 4, 17:00-18:00, Grand Ballroom, Krasnapolsky Hotel, Amsterdam Please see below for the agenda. I believe that we might still have a little bit of time left so we can still consider some last minute contributions. I would also like to point you to various topics during the EOF sessions that are about ipv6 (IPv6 Routing Table, IPv6 in Real Life - Deployment of Popular Servers in IPv6, IPv6 Routing Tutorial, DHCPv6), or that will cover ipv6 in addition to ipv4 (What is Wrong With the DNS?, UMTS/GPRS Systems). Thanks and see you in Amsterdam! David Kessens --- Agenda for the IPv6 Working Group Meeting RIPE53 When: Wed Oct 4, 17:00-18:00 Where: Grand Ballroom, Krasnapolsky Hotel, Amsterdam A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Quick update from the RIPE NCC regarding ipv6 services (RIPE NCC) C. Global IPv6 routing table status (discussion) (Gert Doering) D. Impact of 6bone address space depreciation (discussion - presentations welcome) E. IPv6 Multihoming Solutions (Marla Azinger) F. Proposal for IPv6 Multihoming Using PA Space (Iljitsch van Beijnum) Background reading material: http://www.muada.com/drafts/draft-van-beijnum-v6ops-pa-mhome-community-01.t… G. Impact of ip6.int deprecation (discussion - presentations welcome) H. Report(s) about *actual* v6 traffic volume as compared to v4? *what's real* out there, not what's on powerpoint? (input from the audience) I. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) Y. Input for the RIPE NCC Activity Plan (input from the audience) Z. AOB ---

2 1

Multihoming in IPv6 using PA space
by Iljitsch van Beijnum 28 Sep '06

28 Sep '06

[Going out to routing-wg and ipv6-wg, trim as needed in follow-ups] Before the last IETF meeting there was some discussion about the difficulties in multihoming using a prefix out of PA space from an ISP in IPv6. Because many ISPs filter at /32 or /35 in IPv6, the /48s (or /56s) used for multihoming are often filtered out. After some discussion with people from the IETF v6ops wg, I've written the draft mentioned below, outlining the problem and proposing a BGP community to tag the prefixes used for this so they can be un-filtered as needed. Feedback from people involved with and/or an interest in IPv6 routing is highly appreciated. I'd be happy to discuss the draft in either the routing or IPv6 wgs, or talk about it briefly at the end of my IPv6 routing tutorial on wednesday morning. And of course one-on-one in the hallway. The -01 with only minor changes should be up soon, or you can find it at http://www.muada.com/drafts/draft-van-beijnum-v6ops-pa-mhome- community-01.txt Begin forwarded message: > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > Title : BGP Community for PA Multihoming > Author(s) : I. van Beijnum > Filename : draft-van-beijnum-v6ops-pa-mhome-community-00.txt > Pages : 8 > Date : 2006-9-11 > When an organization wants to connect to the internet using two or > more > Internet Service Providers (multihoming), this is usually done by > setting up BGP routing between the organization in question and > each of > its ISPs. For this, the multihomed organization needs a block of > address space. This can either be a provider independent (PI) > address block that belongs to the organization, or a block out of > the provider aggregatable (PA) address space of one its ISPs. > With IPv4, an address block of at least /24 will generally be suitable > for multihoming, whether its origin is PI or PA. However, until now, > ISPs were encouraged to only accept /32 prefixes from IPv6 PA space, > while end-users generally receive a /48. This makes multihoming > with PA > address space in IPv6 very difficult. This memo describes a new > well-known BGP community attribute for tagging prefixes used for > multihoming with PA space in order to facilitate filtering, rather > than > filter based on prefix length alone. > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-van-beijnum-v6ops-pa- > mhome-community-00.txt

1 0

Call for agenda topics & draft agenda (v1) for ipv6 wg RIPE53
by David Kessens 13 Sep '06

13 Sep '06

During next RIPE meeting, our working group is scheduled to meet: Wed Oct 4, 17:00-18:00, Grand Ballroom, Krasnapolsky Hotel, Amsterdam I have prepared a draft agenda with all our standard items. However, the meeting will only be a success if we get a lot of active participation from all participants. In fact there is little reason to have a working group meeting scheduled if we don't get other topics than the standard topics. Is there anything that you have been thinking about regarding the deployment of ipv6 in the european region ? It doesn't matter whether it is a brief topic, whether you have slides or simply would like to ask me to find a speaker. Just send me a quick mail! One thing that I personally was thinking about is the expiration of the 6bone address space. Is there anybody who is willing to give us an overview on what happened, and whether there were any positive or negative effects ? Or anybody knows what the vatican is planning to do with their address space ? Thanks! David Kessens --- Draft Agenda (v1) for the IPv6 Working Group Meeting RIPE53 When: Wed Oct 4, 17:00-18:00 Where: Grand Ballroom, Krasnapolsky Hotel, Amsterdam A. Administrative stuff - appointment of scribe - agenda bashing - approval of the minutes (David Kessens) B. Quick update from the RIPE NCC regarding ipv6 services (RIPE NCC) C. Global IPv6 routing table status (discussion) (Gert Doering) D. Report(s) about *actual* v6 traffic volume as compared to v4? *what's real* out there, not what's on powerpoint? (input from the audience) E. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) Y. Input for the RIPE NCC Activity Plan (input from the audience) Z. AOB ---

1 0

IPv6 Benchmarking - Sept'2006
by Carlos Friacas 05 Sep '06

05 Sep '06

Hello, You can fill in (yet another) survey about IPv6 at: http://surveys.ipv6.eu This survey is part of the European IPv6 Task-Force Steering Commitee's Benchmarking Activity, in the scope of project IST-2-004572-CA, partly funded by the EC. Your cooperation is needed and very welcome! Please also help this message reach the mailboxes of people on your communities, even to those folks which are still far from using IPv6, but who can spare 10 mins to fill this form. This survey is focused on metrics we cannot have input without direct intervention from humans. The outcome of it, plus the data we periodically collect automatically (from several sources) will be worked/aggregated and published on http://www.ipv6.eu Stay tuned! ps: sorry for any duplicate messages. Best Regards, ./Carlos -------------- Wide Area Network (WAN) Workgroup, CMF8-RIPE, CF596-ARIN FCCN - Fundacao para a Computacao Cientifica Nacional http://www.fccn.pt "Internet is just routes (191157/571), naming (millions) and... people!"

3 2

[info@arin.net: [arin-announce] NRPM version 2006.2 - New Policy Implementations]
by David Kessens 31 Aug '06

31 Aug '06

For your information. Please post followups regarding these policy changes to the address policy working group only. David Kessens --- ----- Forwarded message from Member Services <info(a)arin.net> ----- Delivered-To: arin-announce(a)lists.arin.net From: Member Services <info(a)arin.net> To: ARIN Announce <arin-announce(a)arin.net>, "'Public Policy Mailing List'" <ppml(a)arin.net> Date: Wed, 30 Aug 2006 19:22:07 -0400 Subject: [arin-announce] NRPM version 2006.2 - New Policy Implementations Reply-To: info(a)arin.net On 9 May 2006, the ARIN Board of Trustees, based on the recommendation of the Advisory Council and noting that the Internet Resource Policy Evaluation Process had been followed, adopted the following policy proposals: 2005-1: Provider-independent IPv6 Assignments for End Sites 2005-8: Proposal to amend ARIN IPv6 assignment and utilisation requirement 2005-9: 4-Byte AS Number These policy proposals have been incorporated into version 2006.2 of the ARIN Number Resource Policy Manual (NRPM) which is effective 30 August 2006. NRPM version 2006.2 supersedes previous versions. See Appendix A of the NRPM for information regarding changes to the manual. The NRPM can be found at: http://www.arin.net/policy/nrpm.html Appendix A can be found at: http://www.arin.net/policy/nrpm_changelog.html On 11 July 2006, the ARIN Board of Trustees added IPv6 Assignments to the ARIN fee schedule. The Board waived all but $500 of the IPv6 Initial Assignment fee through 31 December 2007. The fee schedule can be found at: http://www.arin.net/billing/fee_schedule.html For information about requesting an IPv6 assignment, please see the guidelines at: http://www.arin.net/registration/guidelines/ipv6_assignment.html Regards, Member Services American Registry for Internet Numbers (ARIN) _______________________________________________ ARIN-announce mailing list ARIN-announce(a)arin.net http://lists.arin.net/mailman/listinfo/arin-announce "To Unsubscribe,<mailto:arin-announce-request@arin.net?subject=unsubscribe>." ----- End forwarded message -----

4 4

2001:7f9::/32 still being announced even though the 'experiment' has finished 2 days ago?
by Jeroen Massar 25 Aug '06

25 Aug '06

Hi, inet6num: 2001:07F9::/32 org: ORG-CA59-RIPE netname: CONSULINTEL-20040713 descr: Experimental Prefix ======================== Duration of assignment: ======================== Start date: 2004-07-19 End date: 2006-07-19 ======================== Details of Experiment: http://www.consulintel.euro6ix.org ======================== But according to: http://noc.sixxs.net/tools/grh/lg/?find=2001:7f9::/32 it is still being announced. Also the mentioned URL doesn't contain any 'details of experiment' at all. What is up with this? Has this become free IPv6 space? GRH automarked it as reclaimed due to the expiry date btw. Greets, Jeroen

4 4

IPv6 access to ftp.ripe.net
by James Aldridge 28 Jun '06

28 Jun '06

[Apologies for duplicate e-mails] Dear Colleagues, IPv6 access to ftp.ripe.net is currently not possible. IPv4 access is unaffected. The current ScreenOS firewall software is unable to support extended passive-mode FTP. We have therefore temporarily removed the AAAA record for ftp.ripe.net from the DNS. We hope to restore IPv6 access as quickly as possible and will inform you when this occurs. We apologise for any inconvenience. Regards, James Aldridge Systems & Network Engineer RIPE NCC Operations Group

1 0

6to4 address utilisation
by Thu Thuy 09 Jun '06

09 Jun '06

Hi, I have a question about 6to4 address utilisation. May i post it here ? Thanks everyone for your guidance. 6to4 is a tunnel method. From an IPv4 address, we have /48 6to4 IPv6 space. So i'm wonder if this /48 range can be commonly used for our IPv6 network (workstations, servers) like native IPv6, or it just be used only for tunnel, to connect native IPv6 lands. Thank you once more, Thu Thuy Development & Research Department. Vietnam Internet Network Information Center - VNNIC.

1 0

V6 connectivity
by Max Tulyev 09 Jun '06

09 Jun '06

Hi! I see v6 connectivity is much worse than v4: traceroute to kite-www.ripe.net (2001:610:240:0:a843::8) from 2a01:d8:0:99:211:11ff:fe1f:bfc9, 30 hops max, 16 byte packets 1 2a01:d8:0:99::1 (2a01:d8:0:99::1) 0.782 ms 0.719 ms 2.227 ms 2 2a01:d8:0:1::1 (2a01:d8:0:1::1) 40.904 ms 2.346 ms 2.754 ms 3 2001:b08:0:2::1 (2001:b08:0:2::1) 35.849 ms 7.533 ms 2.576 ms 4 2001:b08:b08:3::2 (2001:b08:b08:3::2) 35.205 ms 25.399 ms 25.649 ms 5 se-kth.nordu.net (2001:948:0:f02c::1) 29.649 ms 25.579 ms 25.545 ms 6 se-ov.nordu.net (2001:948:0:f027::2) 33.705 ms 25.539 ms 25.927 ms 7 dk-gw2.nordu.net (2001:948:0:f03f::2) 39.785 ms 33.901 ms 33.688 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 nikipv6.ripe.net (2001:7f8:1::a500:3333:1) 214.93 ms 226.989 ms 215.676 ms 13 kite-www.ripe.net (2001:610:240:0:a843::8) 214.484 ms 215.588 ms 221.891 ms 1: greentheatre (195.209.50.18) 0.273ms pmtu 1500 1: gw.gpt.ru (195.209.50.1) 1.366ms 2: LEO-MG-2.Garnet.ru (195.209.63.20) 57.568ms 3: d2-msk-m9-ge0-0-0-v102.ruscomnet.ru (80.249.128.117) asymm 4 3.034ms 4: c1-msk-m9-ge0-1-0.ruscomnet.ru (80.249.132.9) asymm 5 4.265ms 5: d1-fft-as0.ruscomnet.ru (80.249.132.26) asymm 6 51.486ms 6: gigabitethernet3-0.104.gw9.fft4.de.ALTER.NET (139.4.144.5) 51.952ms 7: so-7-1-0.XR1.FFT4.ALTER.NET (149.227.48.25) asymm 8 52.247ms 8: so-0-1-0.TR2.FFT1.ALTER.NET (146.188.8.138) asymm 9 52.400ms 9: so-5-1-0.TR2.AMS2.ALTER.NET (146.188.2.169) asymm 10 58.617ms 10: POS2-0.BR1.AMS3.ALTER.NET (146.188.3.218) 58.315ms 11: Amsterdam1.ripe.net (195.69.144.68) 53.182ms 12: kite.ripe.net (193.0.0.214) asymm 11 53.245ms reached Resume: pmtu 1500 hops 12 back 11 And some parts of v6 Internet is completly unreachable. Is it my bug or real situation? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO) "Garant-Park-Telecom", +7 095 783-3-783

6 5

New ROUTE-SET and RIPE document: Address Space Managed by the RIPE NCC
by leo vegoda 31 May '06

31 May '06

[Apologies for duplicates] Dear Colleagues, We have updated the RIPE document "Address Space Managed by the RIPE NCC" to include references to a ROUTE-SET object describing the address space allocated to the RIPE NCC by the IANA. The new version is ripe-380 and can be found on our web site at: https://www.ripe.net/docs/ripe-ncc-managed-address-space.html We hope the ROUTE-SET object is useful. Kind regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0