- ipv6-wg - mailman.ripe.net

Call for agenda items and draft agenda for ipv6 wg RIPE56
by David Kessens 24 Apr '08

24 Apr '08

During next RIPE meeting, our working group is scheduled to meet on: Wed, May 7, 14:00 - 15:30, in Bordeaux Room, Hotel Palace, Berlin I have prepared a draft agenda (see below) with the all the usual agenda items. At this point, I would like to invite all of you to propose other agenda items that are relevant for the deployment of ipv6 in the RIPE service region. Note that we care more about the technical content of your topic than the presentation method: very brief topics without presentation slides that just need a brief discussion are just as welcome as longer presentations with slides. I would also like to draw your attention to the following: The RIPE NCC is planning to turn off IPv4 connectivity on the wireless network for the duration of around an hour on the wednesday morning. This will allow us to try out how one could survive on an IPv6 only network and to draw attention to all the issues that still need to be worked out in order to make this work 100% seemless for the rest of the Internet users. In order to help you prepare, in addition to the normal dual stack wireless network, there will be an IPv6 only wireless network available during the whole meeting and the RIPE NCC will provide instruction sheets on how to configure various popular operating systems. Obviously, the participants of the IPv6 working group don't need all this as we are already fully prepared for the coming of IPv6. However, you are very welcome to participate by helping other people to get their setup to work with IPv6 or by submitting reports and bugfixes/workarounds on problems that are discovered when trying this out. The actual operational details about this event will be posted by the RIPE NCC. In addition to our working group session and the ipv6 only event, I would like to encourage you to take a look at the plenary agendas. There are a large number of presentations scheduled that touch directly or indirectly on IPv6. I hope this helps and see you all in Berlin, David Kessens --- Draft agenda for the IPv6 Working Group Meeting RIPE56 When: Wed, May 7, 14:00 - 15:30 Where: Bordeaux Room, Hotel Palace, Berlin A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Quick update from the RIPE NCC regarding ipv6 services (RIPE NCC) C. Experience with ipv6 on the wireless network before, after and during the IPv4 turn-off (RIPE NCC, input from the audience) 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. Follow-up: Global IPv6 routing table status (discussion) (Gert Doering) F. 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 3

Conference, Internet and Technology 08, invitation
by Vilem Sladek 02 Apr '08

02 Apr '08

Dear Mr., dear Mrs., my name is Vilem Sladek and I work for CZ.NIC (www.nic.cz) in Prague. For May 2008 we prepare the conference Internet and Technology 08, where we would like to present Internet experiences from the World. We would like also introduce more about IPv6, so we would like to invite you to Prague, to present about IPv6 to the Czech community. The conference is planed on 20th of May, will start at 10 a.m. and finished at about 5 p.m. The conference will be divided it to four parts (Domains, Internet Resources, Technologies and Zeitgeist). Your presentation is planed to second block (Internet resources). We are really interested in this topic and would like to introduce it to the Internet community in the Czech Republic. Please, could you send me the information or call me, if you want to know more detail, if you would like to came, if we can do anything for you for welcome you at the conference Internet and Technology 08. Thank you for your interest and will looking forward the answer. Best regards form Prague Vilem Sladek -- Vilém Sládek Communication Specialist CZ.NIC, z.s.p.o. Americka 23, 120 00 Praha 2 Czech Republic T +420 222 745 117 F +420 222 745 112 M +420 739 452 919 www.nic.cz

1 0

What is difference among /32 , /48 and /64 as charge?
by Yavuz Maşlak 08 Feb '08

08 Feb '08

We are a LIR as small class. We want to apply for ipv6. Is there a difference as charge apply for between /32 and /64 ? I mean, a LIR who has large class, when that LIR applies for /32 and has it, What does that LIR cost for that ? Also, While We are a LIR as small; 1- Can we apply for ipv6 /32 ? 2- What is difference among /32 , /48 and /64 as charge? Thanks a lot.

3 2

[anandb@ripe.net: [dns-wg] IANA introduces AAAA record for K-root]
by David Kessens 05 Feb '08

05 Feb '08

----- Forwarded message from Anand Buddhdev <anandb(a)ripe.net> ----- From: Anand Buddhdev <anandb(a)ripe.net> To: dns-wg(a)ripe.net User-Agent: KMail/1.9.5 Subject: [dns-wg] IANA introduces AAAA record for K-root Date: Tue, 5 Feb 2008 15:10:43 +0100 Dear Colleagues, Yesterday, 4 February 2008, at around 17:00 (UTC), IANA introduced AAAA records for six of the root servers in the root server system. One of these servers is k.root-servers.net (2001:7fd::1), which is managed by the RIPE NCC. This change allows the root zone to be queried over IPv6. The K-root IPv6 prefix is currently anycast from the two global nodes, located in Amsterdam and Miami. The introduction of the AAAA records went smoothly, and we are monitoring the query rate and pattern. We are also collecting more detailed information for future analysis. A graph showing the IPv6 query rate for the last 24 hours can be viewed at: http://ripe.net/news/k-root-aaaa-announcement.html More information about AAAA records in the root zone is available at: http://www.iana.org/reports/root-aaaa-announcement.html Regards, -- Anand Buddhdev DNS Services Manager, RIPE NCC ----- End forwarded message -----

1 0

how to generate ipv6 extension headers
by Prasanna kumar .E 23 Jan '08

23 Jan '08

I am into the ipv6 testing these days.I am stuck in between. I want to know how can I generate the ipv6 extension headers(like hopbyhop,encapsulation,etc.,) Thanks and regards, E Prasanna Kumar ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra. ============================================================================================================================

2 1

AAAA records to be added for root servers
by Barbara Roseman 07 Jan '08

07 Jan '08

apologies for cross-posting... On 4 February 2008, IANA will add AAAA records for the IPv6 addresses of the four root servers whose operators have requested it. A technical analysis of inserting IPv6 records into the root has been done by a joint working group of ICANN's Root Server System Advisory Committee and Security and Stability Advisory Committee, a report of which can be found at http://www.icann.org/committees/security/ sac018.pdf. Network operators should take whatever steps they feel appropriate to prepare for the inclusion of AAAA records in response to root queries. More information will be posted to the IANA web site during January. Regards, Barbara Roseman IANA General OperationsManager ICANN

3 2

2007 IPv4 Address Use Report
by Iljitsch van Beijnum 02 Jan '08

02 Jan '08

2007 IPv4 Address Use Report In 2007, the number of available IPv4 addresses went down from 1300.65 million to 1122.85 million, a difference of 177.8 million addresses. The number of usable addresses is 3706.65 million, so on January 1, 2007 we were at 64.9% utilization and a year later we're at 69.7%. These figures are derived from the records published on the FTP servers of the five Regional Internet Registries (RIRs): AfriNIC, which gives out address space in Africa, APNIC (Asia-Pacific region), ARIN (North America), LACNIC (Latin American and the Caribbean) and the RIPE NCC (Europe, the former Soviet Union and the Middle East). There are two other ways to interpret the same data. The first is simply add up all the address space with a date indicating that it was given out in 2007. That number is 186.93 million addresses. The third method is to compensate for ARIN's record keeping peculiarities (see this Internet Protocol Journal article). This brings the total for 2007 to no less than 196.77 million, the highest number ever. The second-highest was 1991 with 189 million addresses. The 196.77 million figure is approxmately 19% higher than the 2005 and 2006 numbers, which were largely the same. All numbers only include addresses that are still in use. For the first time in many years, in 2007 one of the old class A blocks was returned to IANA: block 46.0.0.0/8, 16.78 million addresses in size, is now part of the global pool of free address space. This accounts for most of the difference between the 177.8 and 196.77 numbers. The status of the 221 usable blocks of 16.78 million address is now as follows: Delegated to Blocks +/- 2007 Addresses (millions) AfriNIC 2 +1 33.55 APNIC 26 +7 436.21 ARIN 27 452.98 LACNIC 6 +2 100.66 RIPE NCC 26 +4 436.21 Various 49 -1 822.08 End-user 42 -1 704.64 Available 43 -12 721.42 In addition to the 43 unused blocks (721.42 million addresses) that IANA holds, there is additional free space in the form of addresses delegated from IANA to the regional internet registries, but not yet further delegated by the RIR in question to an ISP or end-user. 2006-01-01 2007-01-01 delegated delegated free delegated delegated free TO BY TO BY AfriNIC 16.78 6.39 10.39 33.55 11.97 21.58 APNIC 318.77 297.23 21.54 436.21 366.87 69.34 ARIN 452.98 350.48 102.50 452.98 394.08 58.90 LACNIC 67.11 42.71 24.40 100.66 57.52 43.14 RIPE NCC 369.10 317.62 51.48 436.21 378.35 57.86 Total RIRs 1224.74 1014.43 210.31 1459.61 1208.79 250.82 Various 838.86 671.26 167.60 822.08 671.48 150.60 End-user 721.42 704.64 16.78 704.64 671.09 33.55 Available 922.74 16.78 905.96 721.42 16.78 704.64 Total 3707.76 2407.11 1300.65 3707.75 2568.14 1139.61 This view uncovers two inconsistencies: block 7.0.0.0/8 that is part of the free space according to the IANA IPv4 address space overview shows up as delegated to the US Department of Defense in ARIN's records. Net 14.0.0.0/8 is for the "public data net" (see RFCs 3330 and 1700) so it's not part of the regular delegation system. 43.0.0.0/8 is delegated to "Japan Inet" by IANA. Those delegations used to be registered in ARIN's database but this block was transferred to APNIC in 2007, where it does show up in the whois service, but not as part of the delegated address space in the files on the FTP server. The total of 3707.76 (or 3707.75) million addresses is slightly different from the 3706.65 maximum mentioned earlier because the latter excludes all RFC 1918 private address space, the former still includes 192.168.0.0/16 and 172.16.0.0/12. The size of address blocks given out was increasing until 2005, but now shows a downturn. The table below shows the number of delegations 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 and 2007 values from 2007-01-01 data. No correction for the ARIN accounting method.) 2001 2002 2003 2004 2005 2006 2007 < 1000 474 547 745 1022 1309 1507 1830 1000 - 8000 1176 897 1009 1516 1891 2265 2839 8000 - 64k 868 822 1014 1100 1039 1192 1015 64k - 500k 262 163 215 404 309 419 395 500k - 2M 39 29 46 61 60 57 62 > 2M 5 5 6 7 18 17 24 The increase in large blocks has a very dramatic effect while the small blocks are insignificant, when looking at the millions of addresses involved: 2001 2002 2003 2004 2005 2006 2007 < 1000 0.16 0.18 0.25 0.35 0.44 0.51 0.63 1000 - 8000 4.47 3.23 3.45 4.49 5.07 5.83 6.93 8000 - 64k 12.81 11.35 14.00 15.99 15.46 18.01 15.67 64k - 500k 32.19 20.28 25.51 42.01 34.23 50.86 50.83 500k - 2M 24.64 21.30 31.98 44.63 41.63 46.69 45.50 > 2M 14.68 12.58 12.58 20.97 68.62 52.43 67.37 Despite the strong increase in the number of 2 million+ blocks and the amount of address space given out in these blocks, the average block size has been going down because of the very large growth in the numbers of smaller blocks: 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 5457 174.32 31945 2007 6165 186.92 30320 The 2568.14 million addresses currently in use aren't very evenly distributed over the countries in the world. The current top 15 is: 2007-01-01 2007-01-01 change Country 1 - US 1408.15 M 1366.53 M +3% United States 2 - JP 141.47 M 151.27 M -6% Japan 3 (4) CN 135.31 M 98.02 M +38% China 4 (3) EU 120.35 M 115.83 M +4% Multi-country in Europe 5 - GB 83.50 M 93.91 M -11% United Kingdom 6 - CA 73.20 M 71.32 M +3% Canada 7 - DE 72.46 M 61.59 M +18% Germany 8 - FR 67.79 M 58.23 M +16% France 9 - KR 58.86 M 51.13 M +15% Korea 10 - AU 33.43 M 30.64 M +9% Australia 11 (12) IT 24.04 M 19.14 M +26% Italy 12 (11) BR 23.46 M 19.27 M +22% Brazil 13 (16) MX 21.50 M 16.26 M +32% Mexico 14 (13) ES 20.42 M 18.69 M +9% Spain 15 - NL 19.89 M 18.08 M +10% Netherlands The -6% and -11% figures for the UK and Japan are once again anomalies: the former is the missing 43.0.0.0/8 net and in the latter case, ARIN and RIPE both had a record for 25.0.0.0/8 in the 2007-01-01 data, but this was cleared up in the 2008-01-01 data. Although the US still added more than 40 million new addresses to its immense existing stockpile, its growth was modest percentage-wise and it now holds 55% of the IPv4 address space in use, down from 57%. All of the other countries in the top 15 except for Canada and "EU" saw their address use grow faster than the 7% average. This brings the total for the top 15 excluding the US to 35%, up from 34%. The rest of the world gets the remaining 10%, up from 9%. See http://www.bgpexpert.com/addrspace2007.php for a copy of this report and links to the versions for 2006 and 2005.

1 0

RIPE NCC Makes Record Number of IPv6 Allocations
by Alex Le Heux 14 Dec '07

14 Dec '07

This announcement was posted on the RIPE NCC News & Announcements webpage yesterday: RIPE NCC Makes Record Number of IPv6 Allocations The months of October and November 2007 set new records for the number of IPv6 allocations made in a single month by the RIPE NCC. 24 allocations were made to RIPE NCC members in October, arecord immediately broken by the 31 allocations made in November. The previous peak was 19 allocations in a single month, which was achieved on three separate occasions in 2003, 2004 and 2007. This surge in demand for IPv6 address space follows recent changes in the IPv6 allocation policy, which made it easier to get IPv6 allocations. The increase also comes in the wake of the publication of the RIPE Community Resolution on IPv4 Depletion and Deployment of IPv6. This statement, released immediately after the RIPE 55 meeting in Amsterdam in October, urged all Internet industry stakeholders, including ISPs, governments and regulators, to take steps to foster the accelerating deployment of IPv6. The text of this resolution can be found at: http://www.ripe.net/news/community-statement.html The deployment of IPv6 across the Internet has been a subject of growing global interest, particularly as it relates to the diminishing pool of free IPv4 address space, and the impact that this will have on the ongoing growth and future stability of the Internet. For more information on this, please send an email to <ncc(a)ripe.net>. Best regards, Alex Le Heux Policy Implementation and Coordination, RIPE NCC

14 16

[Fwd: need help with global ipv6 topology measurement]
by Henk Uijterwaal 28 Nov '07

28 Nov '07

-------- Original Message -------- Subject: need help with global ipv6 topology measurement Date: Tue, 27 Nov 2007 15:55:42 -0800 From: k claffy <kc(a)caida.org> To: nanog(a)merit.edu if you have ipv6 connectivity and are willing to volunteer some (low bandwidth) v6 traceroute data to a good cause (== a topology map of observed ipv6 connectivity), please help us out for a few ( estimated < 15) min with: http://www.caida.org/data/how-to/scamper/ipv6-collection-2007/ please share w all your ipv6friends, k -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Is one of the choices leaving the office open? Alan Greenspan on the next elections

1 0

IPv6 policies & BGP announcements
by Clement Cavadore 28 Nov '07

28 Nov '07

Hi, I have a few question regarding IPv6, and policies. I am not LIR, so I cannot get any /32 for my network usage. I got from my LIR a /48 for my internal network needs, and another /48 for another end-user, routed through my network. The two /48 are consecutive, and aggregable as a single /47. - Am I allowed to announce a prefix more specific than my LIR's /32 (originated from my ASN, not the LIR's one) ? - If I can announce a more specific prefix, do I have to announce a couple of /48s, or may I announce a single /47, originated from my AS ? If I can announce the /47, I assume the LIR has to create a route: object ? - Is there any recommendations I'd need to know for such a situation (except becoming LIR, which is not possible for us at the moment) ? Thank you for your help -- Clément Cavadore

5 7

Few questions about IPv6
by Marcin Gondek 15 Nov '07

15 Nov '07

Hello All , I have few question about IPv6 and maybe someone can explain this. Sorry if those information can be found on RIPE page or I'm sending it to wrong mailing list, I'm not able to find it. 1. Do I have to be a LIR to request /32 subnet from RIPE, can be it done by another LIR which will request subnet for me (as its customer)? 2. Do I have to be a LIR to request AS number from RIPE, can be it done by another LIR which will request AS number for me (as its customer)? Thanks in advance. -- Marcin Gondek / Drixter e-utp.net NIP: PL1181589645 REGON: 140584662 Tel. +48602159929 Fax. +48222012418 <mailto:office@e-utp.net> office(a)e-utp.net <http://www.e-utp.net> http://www.e-utp.net

6 9

Commercial IPv6 firewall support
by michael.dillon＠bt.com 08 Nov '07

08 Nov '07

Some people have claimed that they cannot yet sell IPv6 Internet access because there is no IPv6 firewall support. According to this ICANN study: http://www.icann.org/committees/security/sac021.pdf this is not quite true. At least 30% of the 42 vendors surveyed, had IPv6 support. According to this talk <http://www.guug.de/veranstaltungen/ecai6-2007/slides/2007-ECA-I6-Status -IPv6-Firewalling-PeterBieringer-Talk.pdf> many open-source and commercial firewalls supporting IPv6 are available. IPCop is based on Linux <http://www.ipcop.org/index.php?module=pnWikka&tag=IPCopScreenshots> m0n0wall is based on FreeBSD <http://m0n0.ch/wall/screenshots.php> pfSense is also based on FreeBSD <http://pfsense.com/index.php?id=26> FWBuilder is a management tool that builds filter setups for several different firewalls. <http://www.fwbuilder.org/archives/cat_screenshots.html> Checkpoint FW1 NGX R65 on SecurePlatform supports IPv6 FortiGate supports IPv6 in FortiOS 3.0 and up. Juniper SSG (formerly Netscreen) supports IPv6 in ScreenOS 6.0 and up. Cisco ASA (formerly PIX) supports IPv6 in version 7.0 and up. I suspect that the people complaining about IPv6 support are partially complaining because they have older hardware that the vendor does not plan to upgrade to IPv6 support until they have all features implemented in their newer products, and partially complaining because their vendor has not implemented some feature which they happen to use. Commercial firewall support may be lagging behind OS and router support, but not by much. And if commercial vendors are not responsive, maybe you should try pricing out an open source solution with a consultant. I believe there is a gap here that startup firewall companies could fill if they understand the enterprise market. --Michael Dillon

5 5

OT? Ripe NCC posting on youtube
by ed 07 Nov '07

07 Nov '07

Sorry if this is off topic or old news, but I saw this on the SCLUG mailing list. Truly excellent: http://uk.youtube.com/user/RIPENCC -- The 14.4 dialup to the PS2 is doing the twist because of a power outage. AOL is playing way too much Diablo II. :: http://www.s5h.net/ :: http://www.s5h.net/gpg

1 0

Re: [address-policy-wg] Commercial IPv6 firewall support
by jwkckid1＠ix.netcom.com 29 Oct '07

29 Oct '07

Nick and all, Chiming in here as a kinda unusual occurance. I agree with Nicks assessment here unfortunately. Seems across a broad business spectrum a disinterest in IPv6 remains or presists. Given, what I believe to be an accurate essesment by Nick below, it would seem that a more concerted effort to make IPv6 more palatable in very short order is advisable. As to how to accomplish that, I do not know. -----Original Message----- >From: Nick Hilliard <nick(a)inex.ie> >Sent: Oct 27, 2007 9:25 AM >To: michael.dillon(a)bt.com >Cc: address-policy-wg(a)ripe.net, ipv6-wg(a)ripe.net >Subject: Re: [address-policy-wg] Commercial IPv6 firewall support > >> Some people have claimed that they cannot yet sell >> IPv6 Internet access because there is no IPv6 firewall >> support. According to this ICANN study: >> http://www.icann.org/committees/security/sac021.pdf >> this is not quite true. At least 30% of the 42 vendors >> surveyed, had IPv6 support. > >There is, of course, "support" and support when talking about any feature, >whether ipv6 related or not. > >As a useful example of what "support" implies, the "support" from one of my >firewall vendors includes basic support for ipv6 packet forwarding and >filtering, but no support for configuring this from the GUI. And no support >for failover / failback on ipv6. And no support for ospfv3. Or DHCPv6. Or >v6 support for VPNs. And so on - you get the idea. There are piles more >features which just aren't there if you use v6. In fact, I would suggest >that there is such a large functionality gap between their ipv4 and ipv6 >support right now, that even if they invested heavily between now and the >current expected dates for ipv4 exhaustion, I seriously doubt that they >would achieve feature parity, not to mind stability parity for these >features. > >I have talked to them about this, and their opinion is that there is no >commercial demand for ipv6, and therefore ipv6 feature parity is on the >feature roadmap. And indeed, it is difficult for the organisation I work >for to demand ipv6 support, when other companies can talk to their vendors >with a EUR100m firewall / networking contract going a-begging. I have >little doubt that this is the reason that MOP got re-enabled by default on a >certain router vendor's products. > > >Them: "We have EUR200m to spend and we want MOP enabled by default". >Vendor: "Three bags full, sir". > >Me: "I want to you spend $50m in development costs to support ipv6, and > then i'll buy some low end kit from you" >Vendor: <laughs hysterically> > >Open source solutions tend to fare better in this regard. Lots of people >may end up using them in a future ipv6 world, but you're not going to end up >seeing F500 companies stampeding to replace their current high-end solutions >with m0n0wall installations, just because they have more-or-less parity >support for ipv4 and ipv6. > >There's a more interesting discussion of this of this linked from: > >http://www.arin.net/meetings/minutes/ARIN_XX/ppm.html > >See the talk entitled "IPv6 Support Among Commercial Firewalls", by Dave >Piscitello. > >Nick > >-- >Network Ability Ltd. | Technical Operations | Tel: +353 1 6169698 >3 Westland Square | INEX - Internet Neutral | Fax: +353 1 6041981 >Dublin 2, Ireland | Exchange Association | Email: nick(a)inex.ie > 'Regards, Jeffrey A. Williams Spokesman for INEGroup LLA. - (Over 277k members/stakeholders strong!) "Obedience of the law is the greatest freedom" - Abraham Lincoln "Credit should go with the performance of duty and not with what is very often the accident of glory" - Theodore Roosevelt "If the probability be called P; the injury, L; and the burden, B; liability depends upon whether B is less than L multiplied by P: i.e., whether B is less than PL." United States v. Carroll Towing (159 F.2d 169 [2d Cir. 1947] =============================================================== Updated 1/26/04 CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS. div. of Information Network Eng. INEG. INC. ABA member in good standing member ID 01257402 E-Mail jwkckid1(a)ix.netcom.com

1 0

Re: [ipv6-wg] RIPE Community Resolution on IPv4 Depletion and Deployment of IPv6
by Andy Davidson 27 Oct '07

27 Oct '07

On 25 Oct 2007, at 10:55, JORDI PALET MARTINEZ wrote: > 1) Network operators and Internet Service Providers (ISPs) are > called to the urgent deployment of IPv6 across their networks as > soon as possible. This deployment must include providing IPv6 > access to End Users and ensuring services are accessible by IPv6. I thought that yesterday's session was useful (I watched via the webcast), and that the publication of this resolution will send the right signals to decision makers - well done everyone. We have to remember that a lot of networks use only v4 PI, as this is the model typically deployed by end sites who rely on multihoming for performance or reliability reasons. Unless and until 2006-01 becomes approved, there is no migration path to v6 for these networks. We must ratify 2006-01 in order to strengthen the impact of the publication of this resolution. Best wishes, Andy Davidson -- :: http://www.localphone.com/ - Call Global, Pay Local :: /* opinions and thoughts expressed here are my own */

2 1

RIPE Community Resolution on IPv4 Depletion and Deployment of IPv6
by JORDI PALET MARTINEZ 25 Oct '07

25 Oct '07

I don't think my comment was well understood today in the session, so I drafted how I think the community resolution should look. See below. English nits should be reviewed, but the main idea is that we start with a short kind of intro of the situation (those points from the original 5 that are generic), staying focus, keeping it short, but at the same time help each "kind of reader" to identify what is the paragraph that is *more* relevant to him. I also added a specific action for policy makers/regulators and one for users. I hope that, as very few people (in the list and session) has provided input on this, we are allowed to participate in the final drafting of the document. Not being a big group is possible to do it, as otherwise, will not really be a community resolution. Regards, Jordi At current allocation rates, the remaining pool of unallocated IPv4 address space is likely to be allocated within the next two to four years. Although the Internet will continue to function as normal after this point, this event will have a significant influence on future network operations as well as IP address management and allocation policies. Therefore we recognise that the widespread deployment of IPv6 will be essential to sustain future growth of the Internet. We recognise that the responsibility for creating policies related to the management of critical Internet resources in the RIPE NCC service region rests with the RIPE community and the proven success of the RIPE Policy Development Process (PDP). In recognition of this responsibility, we commit to continue development of effective policies for the responsible management of IPv4 and IPv6 address space. We agree that this situation requires a committed effort from network operators, ISPs and the RIPE community. We urge that the widespread deployment of IPv6 be made a high priority. In addition to that, other sectors must take their own measures in order to success on this mission: 1) Network operators and Internet Service Providers (ISPs) are called to the urgent deployment of IPv6 across their networks as soon as possible. This deployment must include providing IPv6 access to End Users and ensuring services are accessible by IPv6. 2) Vendors (hardware and software) are called to the urgent support of IPv6 support in their products, to make it possible for network operators and Internet Service Providers to provide these services. 3) Regulators and policy makers are called to make sure the relevance of the IPv6 support is considered in all their decisions, including as an immediate condition for public procurements. 4) Users must ensure, when acquiring new services, hardware or software, that it supports IPv6 (natively or by means of transition mechanisms). ********************************************** 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.

3 3

DRAFT: RIPE Community Resolution on IPv4 Depletion and Deployment of IPv6
by Gert Doering 24 Oct '07

24 Oct '07

Hello Address Policy Working Group, IPv6 Working Group, as announced yesterday on the APWG list, here's the first draft of the "we are going to tell the world what the RIPE community recommends regarding the end of IPv4 / advent of IPv6". The text has been drafted by the RIPE NCC, but the actual recommendation needs to come from "the community", so change whatever you think needs changing. Face-to-face discussion will take place in the APWG and IPv6 WG meeting on Thursday, October 25th. (Short discussion in APWG early morning, time to think about it during the day, final decision in the IPv6 WG meeting on Thursday afternoon). ----------------------- snip ----------------------- DRAFT - RIPE Community Resolution on IPv4 Depletion and Deployment of IPv6 RIPE 55: 22 - 26 October 2007 The RIPE community resolves as follows: 1) At current allocation rates, the remaining pool of unallocated IPv4 address space is likely to be allocated within the next two to four years. Although the Internet will continue to function as normal after this point this event will have a significant influence on future network operations as well as IP address management and allocation policies. Therefore we recognise that the widespread deployment of IPv6 will be essential to sustain future growth of the Internet. 2) We urge network operators and Internet Service Providers (ISPs) to deploy IPv6 across their networks as soon as possible. This deployment must include providing IPv6 access to End Users and ensuring services are accessible by IPv6. 3) We recognise that the responsibility for creating policies related to the management of critical Internet resources in the RIPE NCC service region rests with the RIPE community and the proven success of the RIPE Policy Development Process (PDP). In recognition of this responsibility, we commit to continue development of effective policies for the responsible management of IPv4 and IPv6 address space. 4) We agree that this situation requires a committed effort from network operators, ISPs and the RIPE community. We urge that the widespread deployment of IPv6 be made a high priority. ----- End forwarded message ----- Gert Doering -- APWG chair -- Total number of prefixes smaller than registry allocations: 122119 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

14 37

Agenda for ipv6 wg RIPE55
by David Kessens 19 Oct '07

19 Oct '07

During next RIPE meeting, our working group is scheduled to meet: Thu, Oct 25, 16:00 - 17:30 in Grand Ballroom, Hotel Krasnapolsky, Amsterdam The agenda became quite packed due to the last minute agenda item of a proposed community statement regarding the depletion of ipv4 and the deployment of ipv6. Note that this proposal will be discussed first in the APWG session in the early thursday morning session. I have included a link to the actual proposal in the agenda and you might want to take a look at it and the discussion that followed on the list after the first posting of the draft. Rather than cutting the discussion short, we might let the meeting run past the normal closing time of 17:30 but to no later than 18:00 (I usually ask for the afternoon slot so that we have a bit more flexibility with our time). See you all in Amsterdam, David Kessens --- Agenda for the IPv6 Working Group Meeting RIPE55 When: Thu, Oct 25, 16:00 - 17:30 Where: Grand Ballroom, Hotel Krasnapolsky, Amsterdam A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Experience with ipv6 in the RIPE NCC network (Mark Guz, RIPE NCC) C. Two jokes, one and half proposal (IPv4->IPv6 transition in DSL environment) (Geza Turchanyi) D. Report(s) about *actual* v6 traffic volume as compared to v4? *what's real* out there, not what's on powerpoint? AMS-IX (Henk Steenman) & (input from the audience) E. Follow-up: Global IPv6 routing table status (discussion) (Gert Doering) F. RIPE Community Resolution on IPv4 Depletion and Deployment of IPv6 http://www.ripe.net/ripe/maillists/archives/ipv6-wg/2007/msg00047.html and follow-up mails on ipv6 and apwg mailing list (Gert Doering, David Kessens) G. 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 & Draft Agenda (v1) for the IPv6 Working Group Meeting RIPE55
by David Kessens 14 Sep '07

14 Sep '07

During next RIPE meeting, our working group is scheduled to meet: Thu, Oct 25, 16:00 - 17:30 in Grand Ballroom, Hotel Krasnapolsky, Amsterdam To start with, I have prepared a draft agenda with all our standard items. However, to make this a successful meeting we will actually have to get more items on the agenda than just the standard topics. Please let me know if you have any suggestions for issues that need to be discussed. Note that we don't have a requirement for powerpoint or duration of your presentation: the important thing is that the issue to be discussed is relevant for the deployment of ipv6 in the RIPE service region. Thanks! David Kessens --- Draft Agenda (v1) for the IPv6 Working Group Meeting RIPE55 When: Thu, Oct 25, 16:00 - 17:30 Where: Grand Ballroom, Hotel Krasnapolsky, 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. Follow-up: 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

Re: [ipv6-wg] IPv6 news - weekly summary
by David Kessens 28 Aug '07

28 Aug '07

Jordi, I have received the following comments on my request to provide input whether people believe that your "IPv6 news - weekly summary" is something that the working group participants would like to receive on the mailing list: Prefer not to receive your summary: Daniel Roesen Geoff Huston Marc Blanchet Roger Jorgensen Bernhard Schmidt Dominik Bay Gert Doering Edward Lewis (after deadline) Would like to receive your summary: Aleksi Suhonen Neutral: Mohsen Souissi Other comments: Philip Smith would consider your message acceptable if the MessageID was the same for all lists that you post the summary to I believe the results are quite clear and I would like to ask you to stop posting your weekly messages to the mailing list. As a courtesy to you and the people who did have an interest in your mails, feel free to post one more message where people can find the weekly summary on their own and/or contains the information so that people can subscribe on their own to a mailing list that you manage to receive your summary. Thanks, David Kessens Chair IPv6 working group --- ----- Forwarded message from David Kessens <david.kessens(a)nsn.com> ----- From: David Kessens <david.kessens(a)nsn.com> To: Bernhard Schmidt <berni(a)birkenwald.de> Cc: ipv6-wg(a)ripe.net Subject: Re: [ipv6-wg] IPv6 news - weekly summary Date: Tue, 21 Aug 2007 11:34:53 -0700 Hi, Based on Bernhard's input, I would like to poll the working group whether they like to receive these weekly summaries from Jordi on the working group list. I for one was close to asking Jordi to immediately cease posting as they are readily available from other mailing list or at his website (I personally receive now 4 unwanted copies of his mail). However, I can see that other people might have a different opinion. Please send your comments directly to me by Sunday 8/26, without CC'ing the list as their is no need to make this a lengthy discussion. I will post a summary to the list (but I will as a matter of principle mention your name in the summary). Thanks, David Kessens IPv6 working group chair --- On Mon, Aug 20, 2007 at 10:24:23PM +0200, Bernhard Schmidt wrote: > Hi Jordi, > > will it become standard to post this weekly summary of IPv6 news, where > some of your featured stories mention IPv6 just in one small sentence? > Example > > >IT security: Too big for government > >http://www.ipv6tf.org/index.php?page=news/newsroom&id=3154 > ><http://www.ipv6tf.org/index.php?page=news/newsroom&id=3154> > > | However, there are bright spots. Companies are beginning to reduce the > | scope of vulnerabilities in their software and IPv6 is slowly moving > | forward, especially in Asia. > > This is the only occurence of IPv6 in this text. > > Occasional posting of really interesting news to this ml is fine in my > point of views, but gating every unrelated story that happens to have > "IPv6" somewhere in the text through your "portal" page isn't. > > Just my 2 cents, > Bernhard ----- End forwarded message -----

2 1

IPv6 news - weekly summary
by JORDI PALET MARTINEZ 27 Aug '07

27 Aug '07

Main News: Other News: Govt expects users to migrate to IPv6 in 3 years http://www.ipv6tf.org/index.php?page=news/newsroom&id=3171 The Tech Lab: Vint Cerf http://www.ipv6tf.org/index.php?page=news/newsroom&id=3170 Is the Internet Over? http://www.ipv6tf.org/index.php?page=news/newsroom&id=3168 IPv6 readiness is key as IPv4 peters out http://www.ipv6tf.org/index.php?page=news/newsroom&id=3167 Posts Face IPv6 Challenges http://www.ipv6tf.org/index.php?page=news/newsroom&id=3166 Don¹t miss the forest for the trees http://www.ipv6tf.org/index.php?page=news/newsroom&id=3165 Security: Corporate and Products: Centennial Discovery 2007 Eases Management of IT Hardware and Software Assets http://www.ipv6tf.org/index.php?page=news/newsroom&id=3169 ********************************************** 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 news - weekly summary
by JORDI PALET MARTINEZ 22 Aug '07

22 Aug '07

Main News: New Portal of the Transition to IPv6 of Latin America and Caribbean http://www.ipv6tf.org/index.php?page=news/newsroom&id=3164&lan=en Nuevo Portal de Transición a IPv6 de América Latina y el Caribe http://www.ipv6tf.org/index.php?page=news/newsroom&id=3164&lan=sp Other News: Pacific urged to keep up with new internet http://www.ipv6tf.org/index.php?page=news/newsroom&id=3162 China's IT Olympic Lineup http://www.ipv6tf.org/index.php?page=news/newsroom&id=3161 Army taps AT&T for Fort Bliss data network update http://www.ipv6tf.org/index.php?page=news/newsroom&id=3159 IT execs ask: What can IPv6 do for me? http://www.ipv6tf.org/index.php?page=news/newsroom&id=3157 IT security: Too big for government http://www.ipv6tf.org/index.php?page=news/newsroom&id=3154 Delegates In Honiara For Leading Pacific ICT Meet http://www.ipv6tf.org/index.php?page=news/newsroom&id=3151 Security: Corporate and Products: F5 Selects Mu Security for Automated Security Analysis of Application Delivery Product Family http://www.ipv6tf.org/index.php?page=news/newsroom&id=3163 Extreme Networks Offers A Smooth Transition To IPv6 http://www.ipv6tf.org/index.php?page=news/newsroom&id=3160 xStack Switches http://www.ipv6tf.org/index.php?page=news/newsroom&id=3158 Microsoft Moves Toward Exchange Server 2007 SP1 http://www.ipv6tf.org/index.php?page=news/newsroom&id=3156 Incognito Software Announces Support and Participation from ARRIS in the Incognito DOCSIS 3.0-IPv6 Interoperability Program http://www.ipv6tf.org/index.php?page=news/newsroom&id=3155 GameRail Gives Online Gamers the Competitive Edge by Deploying Foundry Backbone Routers http://www.ipv6tf.org/index.php?page=news/newsroom&id=3153 Cisco and Texas Instruments Complete First Interoperability Testing of DOCSIS 3.0 Network Upstream Channel Bonding http://www.ipv6tf.org/index.php?page=news/newsroom&id=3152 ********************************************** 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.

3 4

2006-02 Implementation: IPv6 Address Allocation and Assignment Policy
by Alex Le Heux 30 Jul '07

30 Jul '07

[Apologies for duplicate emails] Dear Colleagues, We are pleased to announce that the policy proposed in 2006-02 "IPv6 Address Allocation and Assignment Policy" has been implemented. The RIPE NCC is now ready to accept requests for IPv6 address space under the new policy. The archived proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2006-02.html The updated "IPv6 Address Allocation and Assignment Policy" is available at: http://www.ripe.net/ripe/docs/ripe-412.html The following RIPE documents have also been updated to reflect this policy implementation: Supporting Notes for the IPv6 First Allocation Request Form http://ripe.net/ripe/docs/ripe-413.html IPv6 First Allocation Request Form http://ripe.net/ripe/docs/ripe-414.html Best regards, Alex Le Heux RIPE NCC Policy Implementation Co-ordinator

1 0

IPv6 news - weekly summary
by JORDI PALET MARTINEZ 23 Jul '07

23 Jul '07

Main News: Commission consults public on tougher ICT-trade strategy http://www.ipv6tf.org/index.php?page=news/newsroom&id=3081 Other News: Saving the Earth one phone at a time http://www.ipv6tf.org/index.php?page=news/newsroom&id=3092 Voice over IP problems persist http://www.ipv6tf.org/index.php?page=news/newsroom&id=3090 All Systems Go for IPv6 in SA http://www.ipv6tf.org/index.php?page=news/newsroom&id=3080 We should lead way on IPv6 http://www.ipv6tf.org/index.php?page=news/newsroom&id=3079 Security: Ubuntu Security Notice - linux-source-2.6.15 vulnerability (USN-489-1) http://www.ipv6tf.org/index.php?page=news/newsroom&id=3089 Ubuntu Security Notice - linux-source-2.6.17 vulnerabilities (USN-486-1) http://www.ipv6tf.org/index.php?page=news/newsroom&id=3087 Corporate and Products: Xlight FTP Server: an enhanced and cost-effective file management solution for enterprise http://www.ipv6tf.org/index.php?page=news/newsroom&id=3091 Network Equipment Technologies Announces Second Phase of Technology Partnership With Bay Microsystems to Deliver Next Generation High Performance Multi-Service Platforms http://www.ipv6tf.org/index.php?page=news/newsroom&id=3088 Axis launches professional wireless network camera fulfilling highest market demands http://www.ipv6tf.org/index.php?page=news/newsroom&id=3086 Allied Telesis Unveils Enhanced Fast Ethernet Layer 3 Switch with Advanced QoS http://www.ipv6tf.org/index.php?page=news/newsroom&id=3085 Check Point secures lead http://www.ipv6tf.org/index.php?page=news/newsroom&id=3084 NetIntercept 4.0 Beta Now Available from Sandstorm Enterprises http://www.ipv6tf.org/index.php?page=news/newsroom&id=3083 A10 Networks Announces AX Series 2000 and AX Series 2100 Application Acceleration Switches for Next-generation Server Load Balancing http://www.ipv6tf.org/index.php?page=news/newsroom&id=3082 Intellitactics Ahead of the Game in IPv6; Intellitactics Security Manager Deployed in Landmark Pilot for Major Civilian Agency and Showcased in IPv6 Center of Excellence http://www.ipv6tf.org/index.php?page=news/newsroom&id=3078 Windows optional on Server 2008 http://www.ipv6tf.org/index.php?page=news/newsroom&id=3077 In Systems launches pioneering security analyser in Australia http://www.ipv6tf.org/index.php?page=news/newsroom&id=3076

1 0

6to4 and Teredo relay deployment
by JORDI PALET MARTINEZ 29 Jun '07

29 Jun '07

Some weeks ago I started to work in documenting how to setup 6to4 and Teredo relays/servers in several platforms for the afripv6-discuss mailing list. There are many 6to4 relays already, but it becomes even more important to have them where the bandwidth is more expensive, because it avoids traffic going thru upstream links. The first message on this is here: https://lists.afrinic.net/pipermail/afripv6-discuss/2007/000061.html More information about 6to4 also available at: http://www.ipv6tf.org/index.php?page=using/connectivity/6to4 Similarly for Teredo: https://lists.afrinic.net/pipermail/afripv6-discuss/2007/000080.html And more info about Teredo at: http://www.ipv6tf.org/index.php?page=using/connectivity/teredo Regards, Jordi ********************************************** 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 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