These are unedited transcripts and may contain errors.
THE PLENARY SESSION COMMENCED ON THE 6TH OF OCTOBER, 2009, AT 9 A.M.:
RIR /NRO REPORTS:
CHAIR: Good morning everyone. My name is Paul Rendek, I am from the RIPE NCC and I am chairing this session this morning. If I can just ask ?? this is actually the session for RIR updates, IANA, ICANN updates, the ASO update as well. So if I can ask Leo to start for us first, we'll have IANA to give us their update.
Good to see you, Leo.
LEO VEGODA: Good morning everyone. Good to be back in Lisbon. Let's get cracking. This is what I'll be talking about this morning: The status of the IANA free pools, special addresses, throwing some back, the new mechanism we have for selecting which /8 to allocate to an RIR when they request more address space from us, the introduction of the new reverse DNS self?management system, IDN ccTLDs and the business excellence programme we are working on.
The IANA free pool status: There are 26 Unicast IPv4 /8s. That's roughly 400 million IPv4 addresses, give or take. So that's what we have got left. And as Geoff mentioned yesterday in his presentation in the Monday afternoon Plenary, there are 816?bit AS number blocks left. We seem to have a bit of a rush on AS number blocks last year. I think we went through a few more than usual. RIPE NCC received three, I think.
Special addresses:
We have been working in the IETF on doing a lot of documentation. One of the things we have been documenting is documentation prefixes, making it easier for people to write documentation and not to use address space allocated to someone else or themselves and risk that address space causing problems. APNIC were very kind and they donated 2 /24s from different /8s, just to make it a little more eye?catching and easier to do this documentation.
Now, the draft that that's documented in is, I believe, on the agenda for the next IESG meeting in October. So we should have an answer soon as to whether that will be heading its way towards the RFC editor.
Now, as people in this room will definitely know, we reclaimed fourteen /8 a couple of years ago, mainly through the help of people in this room, because most of the addresses in that particular /8 we used in this part of the world, so it was people in this part of the world that helped in cleaning that up. We haven't had another /8 that we could reclaim, but we have been working on returning some slightly smaller block of address space to the free pool. We have been working with ARIN and the IESG. Basically, these addresses were registered to us in the ARIN WHOIS database and so we have been making sure that there is no reason that they cannot go back into the free pool and I believe that the RIRs will be distributing these addresses, admittedly not very many addresses, between the RIRs, so that they can be allocated as necessary. There is one other block, 128.66 /16: That is mentioned in the draft IANA IPv4 examples there. It was unofficially used as a documentation prefix, so it wasn't included in the last RFC 3330, the IPv4 special addresses RFC. So it hasn't actually been a documentation prefix for years and years, but it wasn't noted, so now we have noted. I think that will be going back as well.
So, this is the mechanism for selecting which /8s to allocate to RIRs. Now, as was presented here and in a few other groups a couple of years ago, we noticed that there were people using /8s that had not been allocated and we realised that that could be a little bit problematic, so we commissioned Duane Wessels from the measurement factory and Oark to do some research into this, and he did some research and he came up with a series of this is how these /8s seem to be used. It was a research based on DNS queries received in the in.addr.arpa servers, which are the root DNS servers. And we basically, based on this research, took the unallocated /8s and cut them into the two pools: those that seemed to be more used and those that seemed to be less used. And now, when an RIR comes for additional address space and they justify it and we are going to allocate them address space, we use a random allocation mechanism based on the mechanism in RFC 2777, which is a verifiable random selection mechanism. It means that you can replay this yourself to make sure that you can see what's going on, and we have described it in an announcement on the IANA website and on the ICANN block. Basically, we use stock market closing prices ?? no, stock market prices at midday to work out which /8 is allocated to the RIR from each of these pools.
Now, AfriNIC and LACNIC both have smaller pools of /8s, and so what we did there was we pooled two of the less used /8s and set them aside for LACNIC and AfriNIC, so that when they come for additional allocations, they will get /8s from these /8s that are set aside for them. Just because they have smaller pools of address space to start off with.
So, if you want to go and look at the details, if you look at the report section on the IANA website, and we have got an explanation of how that works in detail.
Another thing we have been doing is working with the engineering departments of the five RIRs on a self?service management system for reverse DNS. Basically, this will allow the RIRs to very, very quickly change the DNS servers and DNSSEC records for their reverse domains, both in IPv6 to arpa and in.addr.arpa. It's based on standard security technologies and we are at the point now where the work is finished and we are just scheduling the deployment. Along with this there will also be a new mechanism in the whois.iana.org that supports DNS look up which currently, if you look at for the domain or IP6 to arpa or iana.org, you don't get an answer. You will be getting an answer when this is launched.
Another thing that I think I should mention, just because it's probably important to people in this room, even though it's not directly a numbers issue: We are expecting about 20 percent more TLDs over the next six months or nine months. This is a result of introducing the Fastrack for IDF ccTLDs. We have been expecting 50 to 60 requests, 15 to 20 languages. We are not entirely sure what will be requested and by who, but we are getting ready for it. 16th November is when, I believe, the application process begins and we are expecting that there will be what, it's not we are expecting, there will be a string validation process and then it goes through the regular IANA process for delegating a domain.
So, as you can expect, with that increase both in the number of TLDs and also just generally the workload that we are going to be having at IANA, is increasing a bit. One thing we want to do is we want to make sure that we are doing the right job. We want to do an excellent job. It's something that's part of the strategic plan that we are working on and so we are introducing a business excellence programme. Basically, this is to make sure that we have a sustainable programme and framework for introducing improvements in our services.
Now, the first thing we are doing is we are going to be creating a baseline measurement for what we do. So that we have got a method for tracking how we are improving our services. By mid?December, we will have a document that will have that baseline measurement in it. We'll do a self?assessment on that document in mid?January. And what we'll be doing is we'll be looking for the areas that we need to make improvements, what those improvements are, and so on. And in the January to March period, we will be identifying the strategic initiatives that will we'll be taking and then we'll be beginning projects for what those improvements are going to be. Now, the reason that we are going ?? we are doing it in this time line is we do our budget setting from the 1st January, so rather than go and sort of identify things in the middle of the year and then have to wait several months to go and put them into a budget so that we can make sure that we will make the relevant improvements, we are doing the work to identify where we need to make improvements directly before the budget setting process to make sure that we are all in sync and we can go ahead and make these improvements straight away, as the budget goes through.
So, one of the important things, of course, is that we have got to keep you all updated. So, we are trying to make sure that we keep people updated on this. So ICAN meetings, RIR meetings, IETF meetings, meetings relevant to top level domain operators and so on. Sometimes through presentations, also through written announcements on our blog, and, of course, just sitting down with people and having a chat, because you can't beat sitting down with people and having a chat; that's very good.
So, we are going to be continuing our communication work on this as it proceeds. This is something which is cyclical; it's not just a one?off thing. The idea is it's a multi?year piece of work, and we go and do our baseline measurement this year and then we continue to do self?assessments to make sure that we are identifying what areas we have for improvement and then we go and work through on those areas, introduce those improvements. Then do additional analysis to make sure that the improvements we have made are actually working, and so on and so forth. So we'll be making an effort to keep people in this community and other communities, stakeholders, aware of what we are doing.
Another mechanism that we'll be using for communicating is Twitter. We have got a Twitter account. We are obviously not going to be posting anything very long on Twitter. Normally something like "We are here today, and you can come and have a chat." Because having a chat is nice. So if you want to follow us on Twitter, we are quite low volume. Feel free.
And that's it. Thank you. Paul?
CHAIR: Any questions for Leo? Geoff.
GEOFF HUSTON: Geoff Huston, APNIC. Going back to the first part of your presentation when you talked about various bits of old IPv4 address blocks and their current status, my question is: Is one able to interpret the latest 3330 bis draft as the definitive list of all IANA reserved addresses so that if it's not in that draft, it's not reserved by IANA? You made a comment about that on the IETF, on the list and I agree with your comment. I think that that should be the document that says it and if there is something else that should go in there, then we should update that document. I think it's very confusing to people to have multiple documents. I think there should be one source.
GEOFF HUSTON: My question is, do you believe that 3330 business document that's currently in draft form is the definitive record?
LEO VEGODA: I believe it is. I have no reason to believe that it isn't.
GEOFF HUSTON: The rest of us can walk off with that knowledge and assume that's the case, yeah?
LEO VEGODA: Yes. Because, of course, it's an IETF document which means that everyone has had an opportunity to tell us we are wrong. It's gone through, I think, eleven versions now. If, after eleven versions, it's not authoritative, then we have done a very poor job of reviewing it in the IETF.
GEOFF HUSTON: Thank you.
CHAIR: Any other questions for Leo? Okay. Thanks very much, Leo.
(Applause)
CHAIR: Okay. Next up on the schedule should be a presentation from AfriNIC. Although no one is here from AfriNIC today, I am told that we will have some slides that we can put up on website. The reason for AfriNIC's absence is that some of you may be aware that there is an ITU world event, a Telecom event, happening in Geneva, and the NRO does have a presence there, and as the coin drops, a lot of the resources from AfriNIC were taken and sent to Geneva, so they have got most of their people that they have extra resources anyway, on that side. So they are quite busy, close to us, but quite busy as well. So if I can then just ask Geoff Huston to come up from APNIC to give his presentation.
And before I do, I think you can see that you have seen some of us running around with these red T?shirts on. There are a few of us here that are doing the meet and greet. For those of you that weren't here yesterday, it was announced. We are here, for those of you that are new, to answer any questions you may have or to introduce you to anyone you want to know, so I am one of those people as well; I am in the red T?shirt. So for those of you that are new here that weren't here yesterday, then I'd like to meet you. So please don't be shy.
GEOFF HUSTON: Thanks, Paul. My name would have been Paul Wilson, but he sends his apologies, so instead you get me.
I am here to give you the APNIC update. Very quick overview. I'll go through the update on services, give you a quick rundown on the outcomes of the most recent meeting, APNIC 28, which was held in Beijing in the last week of August, and then have a look at some activities in our priorities and services arising from our survey of members as to what they want done and their priorities and where the next APNIC meetings are.
We are a registry. We give out addresses. These are some pretty pictures that show what we have done. I would say, however, there are some slightly interesting things here if you dig pretty hard. If you look at 2008 in IPv4, APNIC allocated a little in excess of five /8s across that twelve?month period. The average run rate at the moment we are going through in IPv4 addresses is approximately 12 /8s a year. So as you can see, APNIC is certainly allocating a relatively large proportion of address spaces in IPv4 at this point in time. Obviously, some of the economies in Asia, and in particular China, have weathered this financial whatever it was very well, and growth in that area is still remarkably strong. However, the year is now three quarters full and if you extrapolate 2009 to the end, the growth that we have seen in 2006, 2007 and 2008 will probably not be an outcome in 2009, and that probably is an outcome of the broader business dimension. So overall, in our region, the Internet is not growing at the pace that it was before someone decided to make a bonfire of all that money.
It's also pretty obvious in the one at the bottom there with AS numbers, that last year we did around 700 AS numbers. That's actually a really good indicator of activity, oddly enough, and this year we won't do that many. We are on track for doing around 550. So again, what it points to is the broader world and its financial sort of state does have an impact in the registry activity.
The one that's moving along is IPv6, and this is not the amount of space that's been delegated; it's actually the number. And again here, three quarters of the way through the year, 140. Last year it was 160 for the entire year. So, oddly enough, v6 is back in that larger trend and there are still, you know, a hefty number of allocations. But, don't forget, 160 isn't many, not in the grand scheme of things. These are still, by comparison, pretty small numbers. Don't forget, we did 700 AS numbers last year. It's not that every person that comes to APNIC is getting IPv6 at this point. It's still a much smaller proportion. So, two years to go, there are a hell of a lot of people all over the world that need to get moving, and APNIC is not immune.
Anyway, beyond the numbers. Back to words now. We have got lots of members and we feel very good about that and we love them dearly. We now have 2,000 and that's terriffic. Indeed, July 2009 was the largest month on record for new membership. So, even though the industry itself is aggregating pretty heavily in terms of mass market deployment where large provider are now doing massive deployments, we are still seeing a huge number of folk in the corporate and small business environment who are actually using these services directly to get their own space and their own resources. So, there is a hefty amount of activity.
Help?desk inquiries are now 1,400?plus a month and the growth rate is still remarkable, so we are moving along.
Of course, with policy, we continue to have fun. We had fun with proposition 50, which was IPv4 address transfers for over three years. And after a rather fascinating year, eventually in Beijing, we managed to reach consensus in the meeting that that we wanted a transfer policy proposal and you can have a look at the details online. But basically, it's much the same as we had been thinking about for some years, there is a few tweaks about before v4 runs out there are a few criteria you have to meet. Once the pool is completely deleted the framework for transfers changes slightly and is a little more open.
We also proposition 73, did an interesting one that realistically tries to make v6 far more accessible to existing holders of v4 space. So the proposal was to direct the secretariat to try and automate a huge amount of the v6 assessment process and allocation process for existing holders of address space and try and get it done in the current parlance of one click shopping; in other words, to really make that particular allocation remarkably smooth and efficient for users. So we would get on and do that.
There is a global policy proposal. I am not sure about the status in RIPE, but the address policy meeting later this week will tell you about the IANA assignment of AS blocks.
We also had a policy proposal around the reclamation of AS numbers.
Three things didn't reach consensus and you can see about them on the web page. A rather technical proposal about historical address resources. Another thing about that whole last /8 in v4 and requiring aggregation on subsequent allocations in v6 didn't get consensus at the meeting. Again, details on website.
APNIC's manner in which it determines its priorities and services and activities is certainly subtly different to what you are used to here in RIPE, and rather than having a standing Working Group to look at that, we actually conduct, every two year, a survey of members and stakeholders across the region with the assistance of John Earls, and, from that, derive a priority list of what kinds of activities and services are valued by the members. And that list there is basically the current set we are working to, and I am very pleased to see that the work in the research and development sector from the chief scientist division is up there at the top. Well done, members. Thank you for your support.
Seriously, yes, we are moving on and doing a fair deal of work. APNIC's resource certification service went online as part of the MyAPNIC portal. Now a year ago and we have now had that service up and running as a normal part of our service now for over twelve months. Work still continues in that and we are doing some developmental work over the next few months in enhancing that service and broadening its area of application in a number of spaces. We are also suspending a fair deal of time working inside the IATF to get a lot of that technology standardiseed to allow others to create tools and services.
We are also in the research and development area, actually looking at BGP. There have been a lot of folks saying if everyone on the plan get got their own /32 and decided to route it, BGP would die a horrible death. Is it true? What are the true dynamics of BGP. What's its scaling capability? How big can it get and why? We have certainly being doing work in APNIC on the research and development area just to understand precisely those kinds of constraints where the routing system may or may not impose some form of constraint on the address allocation structure. What sort of spaces can we route with our existing technology and what sort of future scaling is possible, even within the current constraints of BGP? There has been similar stuff we have been doing in measuring DNS. And there is a report later this week on one of the more fascinating areas of looking at DNS queries and measuring them. I think I reported in Berlin last year sometime in RIPE something, some work we had done in trying to measure IPv6 using different metrics than just simply looking at pact etc. On the wire and trying to understand if there are visible long term trends. So we continue to do that work.
Education and training: There is a big focus at this point in network engineering education now to actually try and assist folk in some of the areas with IPv6 in particular. As any of you have tried when you start bringing things up in IPv6, more than just adding it as another protocol into the routing mix but looking at things like authentication, DHCP, address allocation structures and so on, there is a lot of detail there and we have expanded our test lab there to actually include an IPv6 test bed to give some practical experience. And we have been working with a team similar are you to do expert security training in that region. We have also had the e?Learning and self paste work.
IPv6 promotion: Certainly like all the RIRs is definitely up there as a very high priority. We too have got an icons IPv6 Wiki working and a huge amount of messages and material. Our latest effort was in the Asia Pacific economic community. We have a a meeting I think it's once a year in the Telco sector and the latest meeting was a couple of weeks ago in Mexico where the Pacific RIM nations met for a workshop and we were there with an IPv6 set of presentation material.
It's been a longstanding issue I think with the RIRs almost since their inception that our processes are arcane, weird, convoluted and bizarre and certainly this is something that we have been trying for years to make a rather difficult process of creating materials that justify an allocation into something that's simple and easy to use. We are certainly still working on trying to make sure that we can make that process as simple as possible. So we have been working with or portal MyAPNIC to have features and try and make that whole process of requesting resources to be massively easier and simpler for all concerned. In particular the initial resource allocation and the subsequent resources, we are doing a huge amount of process engineering. So work continues.
We are very grateful for the work done in RIPE at the test traffic measurement work. So grateful indeed that we have been taken on a partnership with them and helping to deploy TTM boxes across the Asia Pacific region. We are doing that now. We are sponsoring 12 nodes straight up and we are trying to deploy them where we currently have root server location. You can read the list there. George Michaelson will be reporting later this week on a day in the life project around that area of monitoring the DNS.
As Leo mentioned as well, there is also been a fair deal of work in trying to make this whole delegated zone service better. Trying to automate those tools and giving a secure channel with positive acknowledgements up and down that a delegation request was made, received and acted on. So, we are also doing that facing downward in the reverse pointer zones that we serve and we are doing that with DNSSEC signing as well so that we have full DNSSEC support.
Root server deployment continues. One deployed in Taiwan and planning for Mongolia, hopefully by the end of the year.
You Northern hemisphere folk, winters are bad, particularly they are really icy and awful and I have been told that the winters in Amsterdam are particular crappy around late February, early March, so now is the time to head to sunnier equatorial climes and make your way to Kuala Lumper, where I can guarantee it will be a huge amount warmer than you will have at home. I can guarantee heat there in APRICOT 2010, in February. So certainly, we'd love to see you there.
And if that's not quite in your timetable. Then we'd like to see you in Bangkok in Thailand in August 2010. Thank you very much.
Any questions?
(Applause)
CHAIR: Thank you for the weather report and for the reminder of winters here. Any questions for Geoff there? Okay. Thank you very much, Geoff.
Just a quick announcement before I ask the next speaker to come up. There is a RIPE NCC services centre located across the hall from here, so any of you that are members, please feel tree to stop by there if you have any questions for any of our staff about the services or the service we give to you, we are happy to speak with you.
Next up is ARIN. So if I can ask John Curran, their CEO and President, to come up.
JOHN CURRAN: Good morning. I am giving the ARIN update to this RIPE meeting. You will see a similarity between some of the RIR presentations. We are all facing some challenges and doing similar activities.
ARIN spent a lot of time recently working on its online portal and its business processes. It's definitely true that the processes that have evolved over the last decade and the RIRs are colourful, and we actually have a pretty significant team back at home doing business process reengineering, trying to stream line and make sense of these processes, so that we can then be put online. We actually released ARIN online 2.1 about two months ago, which allows a much better update process for all of points of contact update.
We also have a time line for all of the enhancements that will will be putting in ARIN online. For these people who deal with contacts both in this region and in ARIN and deal with RIR information, you might want to look at the time line for the road map because we are trying to aggressively automate everything you need to interact with ARIN.
Community consultation is underway. ARIN has a process by which we are about to make a decision for resources. It's not presently in the plan and we are looking for guidance. We go to the community to a consultation process. And with the release of ARIN online 2.1, we went out to community consultation on phasing out the use of those e?mail based whip at the moment plates for certain updates. This was a colourful consultation and I knew it would be. You can follow it ?? if you happen to be in the ARIN region, you can follow it on the ARIN consult mailing lists. We have an upcoming ARIN election. Board of trustees, our Advisory Council which acts as our policy consultation group, and the NRO number Council. These will all be elected right after our October meeting.
Research:
We don't have a huge research team in ARIN. Occasionally, we go out to the community to do research. We contracted recently for study regarding potential market pricing for IPv4 address space in the period near and through exhaustion. We have actually been asked by this for the community. Some of our ISPs have said "I am not sure what to expect once IPv4 runs out. You won't have any in the free pool. What will happen? What do you think I'll be doing two or three years hence to obtain address space to continue our business?" And that's an interesting question. So we are out having, study has been announced, we have a researcher working on it now interviewing folks in the region to try to predict what might happen post v4 depletion. We have developed an ARIN pandemic response plan. We have seen the various flu viruses going around. A lot of the concerns are work?place?based spread of those. So we have a tiered response plan that allows ARIN to work with less people in the office, a lot less people in the office, no one in the office with various levels of services as a result.
We are also supporting the NRO efforts, obviously. There is a lot of about reach going on doing education about IPv4 depletion and IPv6 adoption. We also have personnel at ITU Telecom World this week. IGF in November.
In terms of activities that we are doing in resource management, we have a fairly big portion on revoked resources, making sure that resources that aren't being used are not sitting idle in the community. We have recently, as a result of going through and making sure everything is current, we have pulled over the history of the last three years, more than 3,800 ASNs, those are predominantly 2?byte ASNs which have helped us enormously. Also quite a number of IPv4 blocks, with a distribution you can see on the graph, which provides space for all of us to use and prevents draw?down of the of free pool unnecessarily.
Legacy: Really, somewhat unique situation. All the RIRs have legacy resources in their regions. But ARIN has a very large base of what we call legacy resources which are address blocks assigned prior to the RIRs conception. In our region, part of the process of making sure that we do the right thing is formalising our relationship with legacy block holders. We asked legacy address holders to sign a legacy RSA, or registration services agreement, and this legacy RSA, as part of the signing it they agree to pay us 100 dollars per year so we keep track of their records in the database and provide WHOIS service and we also validate that the parties that claim that they are responsible for that address space actually are responsible for that address space, which can be an adventure as we all know. A lot of folks like to jump up and claim they are responsible for companies that are not around any more. Claim responsibility for address space that they were only peripherally involved with another company. So we go through and we are working with the legacy holders to validate that they are the holder of record, and to bring them under a contractual agreement with ARIN. The legacy RSA has some properties that people may not realise. It is basically a stand still almost agreement. It states that we won't change the fees, nor will policies adopted after you have signed it affect you unless you, as a legacy RSA holder, up great to the latest version of the agreement. To this end, it's a very important thing for people who have legacy RSA, legacy resources in the ARIN region to pursue, yet we have a very small adoption. The number of organisations coming in looking for legacy RSAs is probably about 5 percent in our estimate of the potential legacy pool. This will probably change since we won't be processing requests for things like transfers unless we have validated the resources under a legacy RSA. So as we get in the next few years, we expect to see a few more people to show up to make share the resource that is they are holding are actually theirs. At present we have 756 requests in nor legacy agreements. 334 have within signed. 340 are pending. These pending ones are ones where we are out there saying we need some more information about to make sure you are the actual authorised contact. In the case of these legacy blocks, they are all early nineties or even late 1980 assignments, so validating them as they come in is very important.
Engineering activities: As I said we are doing quite a bit on business process reengineering and upgrading or services. Trying to improve you are Internet routing registry is. Our WHOIS system in terms of performance. Our RPKI pilot. We are working with an RPKI pilot allowing us to issue certs for blocks that have been issued to members. And DNSSEC: We have a two?phase DNS security process. Phase one is signing the zone, that we are responsible for and phase 2 will be including of the DS provision that go members want us to be able to pass that down hierarchically.
Policy discussions: We have quite a few policy discussions on the docket. You can go to the website to look at it. Equitable IPv4 run out is, right now as ?? it proposes that as we get closer and closer to a depleted IPv4 free pool, the number of months worth of address space that we issue with a new request gets shortened to six months, three months. So it ensures that there isn't a party coming in swooping up twelve months worth of addresses and grabbing the last where everyone else gets none. It makes sure that the rate at which we draw the quanta drops as we get closer and closer to depletion.
Open access to IPv6 removes the ?? currently there is some constraints on IPv6 assignments. You really have to be an existing operator or have a plan to provide service as an ISP to a certain number of entities. This makes it much easier to get v6 address. It's not very difficult now but it this remove nearly any impediment for any organisation to get IPv6 address space.
IPv6 multiple discrete he networks allows entities to operate separately that don't have connectivity between them. We have the same global IANA to RIR policies that are in the discussion in the other regions, and IPv4 assignment one and an ASN assignment one and we have actually got recommended for adoption coming up. Community yet works IPv6 policy. That will be discussed.
In terms of the outreach that we are doing: We are very active, going out to many, many fora discussing about IPv4 depletion, IPv6 adoption, the RIR system, and the policy development process. Some of the venues we have been about at or will be at: CES, [APECTEL], hosting con, Internet2. A number of forums out there. A lot of people think that this is a well?known issue, the IPv4 /IPv6 issue. It is not. Outside of a small number of folks in this community in the business community, this is a completely unknown issue that's two years away. And so every time we go out and present the message, we get interesting responses. People coming to us saying "You are kidding, right? What do you mean we are running out of IPv4 addresses?" So, we are trying to get the message out there and we are trying to be right with it. It's not that we are running out; it's just that we are running out of the ones that are free and easy to get at. There will ?? the same number of addresses exists three years from now as before. It's just most of them already have been assigned to someone at least once. It still is an exciting message for people hearing it the first time.
ARIN goes social: We have outreach on Twitter, Facebook and YouTube. You can go find us out there if you are interested. Some people like interacting with us this way. They find it easier.
Finally, we also have an upcoming meeting in an exciting dynamic place. Ours happens to be in coordination with NANOG, will be in Dearborn, Michigan, in October later on this month, and we more than welcome folks to come on out. After that we are going to be in Toronto in April, and I can't tell you the other meetings after that, but we hope to get to some warmer climates, like our other RIRs. That's about all I have. And any questions?
Thank you very much.
(Applause)
CHAIR: Thanks very much, John. I just flew in from Toronto and I can tell you that it's not warm there. Next up if I can ask my colleague LACNIC to give us an update.
ROQUE GAGLIANO: Hello everybody. I am from LACNIC. I know Raul is in your programme, he is about to arrive, he is landing in couple of hours but he will be here in the afternoon to answer all the questions.
This is the LACNIC engineering department and this is the LACNIC report. This is my one slide presentation. We are still growing a number of resources. We are growing in the membership base. We got now more than 1,000 members and we are also growing in the staff number. Similarities with the other RIRs, as Geoff mentioned, we are growing particularly in the end user space. That means companies, and also we are growing particularly in the small business side. So ?? small ISPs. So, we made the landmark of the thousand members, which very good.
If you look at the registration numbers. The IPv4 space, we can see that the amount of space we are allocating per year is pretty much the same in the last three years, and we believe this year we are going to be around the same amount of allocation than the previous year. It's different in the IPv6 area where this year is going to be our, this is going to be the year with the highest number of allocations. We are already surpassing 2008. So we are very happy about that.
Policy development process: We have a new policy development process since last year, and we have been implementing it through the whole year, and as a consequence of this, we have now co?chairs, so we have two chairs and in the last LACNIC meeting, we selected Nicholas [] Anteniena to be our second co?chair and he will be serving for two years.
Policies under discussion:
As our policy development process goes, the status of most of the policy we are now discussing in the meetings is right now they are in the board director queue and the one that reached consensus that are waiting in that queue are particularly the global policy for the IPv4 blocks, that you guys are also discussing in this forum. We have an IPv6 policy for ISPs that already have IPv4 space. We had something similar for end users in our region and now we have kind of like a fastrack for IPv6 for every single ISP that already have IPv4, making it easier for them to justify the IPv6 space and giving them a /32.
ASPLAIN notation for 32?bit ASNs, this is similar to what's been approved in other RIRs. We have a regional policy about the 16?bit allocation ASN. Basically the policy says that starting in the 1st January 2010, if there is still 16?bit ASNs in the LACNIC pool and you can justify them, you need the 16?bit ASN somehow, LACNIC will allocate those 16?bit still 32 and you will still have them.
We have a new resource recovery process for all of our resources. We have just modified ?? we are modifying or minimum allocation for IPv4 space to /22. Previously it was a/21 in the LACNIC region.
We are in the last call for the IANA assigned number, the policy for the ASN numbers from IANA and this policy is particular, because it's the first policy that has come in through what we call the expedited process. This is ?? LACNIC has only one [ENRON] meeting and that means that policy has to wait for the whole year cycle to get discussed in our forum and through this expedited process, we'll be able to discuss policies only electronically by e?mail in our mailing list.
So, I talk about the LACNIC 12 meeting happened in Panama last May. It was a very successful meeting. We had more than 300 participants from 40 countries. There we introduced two new projects. The first one is the project about providing training and promoting the creation of security response team all along the region. And the second project is the assignment project, which is going tore our measurement project for the LACNIC region, and we are excited about both of them.
We also have our regional Caribbean meeting. This is a meeting that is focused on the Caribbean region. It happened last July in Trinidad. We got 70 attendees from 17 countries in the region. We normally try to co?organise that together with some other Caribbean event and this year it happens at the same time as the can't owe meeting. So, again, very successful because it allows us to discuss policy with the Caribbean people.
IPv6 tour: We continue our IPv6 activities. We are doing activities all over the continent and what you can see is the countries we have been in the last 24 months. This year we had activities in eight countries and we are going next to nick ago a next month. There is a lot of activities in Brazil as well. But basically we are trying to finally covering the whole service area.
FRIDA programme: This is our fund for helping the development of research in the region. We are just finishing a new call for proposers yesterday and the results are going to be out 11th of December. You can find all the information online. I think it's the 19th December, which project were funded by these initiatives.
Other activities: We are got something new this year which is our outstanding achievement award. Basically, this is an award to honour an individual who made a great contribution to the development of the internet society in the Latin American region. So this time was the first year that we organised it. And this first edition was presented to this lady, who is the head of the central computer department in the university of the Republic in Uruaguy. Basically, there was a committee that selected the person, who received the nomination and selected the person. This is a very good new opportunity to award very important people in our region.
In the public affairs area we set up a Government Working Group, something similar you guys have done already. This is the idea of this was to facilitate the communication with governments, related to Internet resource activities. The first meeting was held during Panama, so we took time to get some Government representatives to our meeting and the second meeting was held in Rio de Janeiro in Brazil, which was also coordinated to be at the same time of another meeting we held there. Next, which is actually our preparation meeting. We did this in Rio, together with some other organisations, particularly from the non?profit area.
Last week we just came from Argentina, which was also pretty cold, I can tell you that. We organised a workshop about exchange points etc., with the CITEL organisation, which is the organisation that takes care of regulation in the whole of the Americans. This kind of workshop, we are going to be organised in the AGF next month. So ??
Our project has to do with developing installation of root servers all along the region. We install this year, we had 6 servers from the F?root through an agreement we have with ISC. This was a landmark for us, because it was the first root server that we installed in the Caribbean part of the LACNIC region. We were in ASN Martin, where we installed the OCS exchange point. You can see the crew there doing the installation and we took advantage of this activity to do some v6 training too.
The engineering side: RPKI, we are working on our own projects and we plan to have a better system by March 2010. We are also working on DNS upgrades and preparing our selves for DNSSEC deployment and also an increase in our DNS activity due to some internal reorganisation that we are working on.
So that's all. Got any questions? Okay. Thank you.
(Applause)
CHAIR: Okay. That completes the updates on the RIRs. Thank you everyone. We are going to move over to the ASO, if I can ask Dave Wilson to come up and give us an update on what's happening in the Address Council.
DAVE WILSON: Thank you very much. I am Dave Wilson. The hat I am wearing this morning is that of member of the ICANN address supporting organisation Address Council. The position is an elected one. I was elected by, more or less, the people in this room three years ago, which means that the seat is due for renewal at this meeting. What I am just doing now is giving a summary of what we have done over the past few months since the last RIPE meeting.
While that's sorting out, I'll just begin. The Address Council, if you haven't witnessed it before, is made up of 15 members. There are three nominated from each of the five regions. The three members in the RIPE region are Hans [Peter Holen], Wilfried [Weber] and myself. The main functions we do. There is a few things things.
The group works as a liaison between the RIR system and ICANN itself. The three main function that is I have put up here, we appoint two ICANN Board directors, two out of every three years. We also nominate someone to the ICANN nominations committee. Our main function is to shepherd global policy to ensure that the process is followed in each region and give assurances to the ICANN Board when they go to finally adopt a global policy on the basis of that assurance.
One of those functions, nominating someone to the nominations committee. The way this works is someone can serve on the ICANN NomCom for a maximum of two conservative years, I think there is a two?year period before they can be nominated again. Hartmut Glaser this did job very well for the past two years and has stepped down as required and Wilfried is our nominee for next year. So thank you very much both.
The only other thing I want to mention are the two global policy proposals that are in our remit right now, each of the members keep an eye on how the policy is proceeding in each given region, or in their own region. And the first of these is a global policy for autonomous system numbers. You might remember this from the last RIPE region. This is about removing the deferentialation between 16?bit and 21 AS bit numbers. There is currently a policy in place such that at the end of this year, ICANN will merge in essence the 16 and 21 AS number space and there will be no distinction. The policy proposal here is to avoid that merging for now. This is in final call now in three regions. It's still in discussion in two. I know in the ARIN region, I think it's reached the Advisory Council adoption, but there is discussion going on. And then in the AfriNIC region, their next policy meeting is in November. So I imagine we'll see some progress then.
The other policy proposal that's on our plate and I think we'll hear more about this I imagine in the Address Policy Working Group later, is what we know at 2009?01, which is a policy proposal for the allegation of IPv4 blocks to RIRs. This has already been adopted in one region. Although I see the text is change in other regions. So there is still discussion to go on there. There'll be more discussion about that later.
If you'd like to know any more, there is ?? first of all, to say thank you very much to the NRO itself for providing the funding and the ongoing support in what we do and especially the secretariat function who provide wonderful support for the work that we do as volunteers.
The additional information I mentioned. There is the ASO's own website. There is the number resource organisation website and if you have any questions feel free to e?mail any of us and that's my e?mail address on the slide.
Thank you very much.
(Applause)
CHAIR: Any questions for Dave? Thanks, Dave.
Moving onto the NRO updates. We have a stats update from my colleague at the RIPE NCC, Andrea Cima, who will give us the NRO statistics.
ANDREA CIMA: Good morning everybody. I am from the RIPE NCC, and I'll be presenting the joint. This report is put together by all five RIRs and it shows the number of IPv4/IPv6 allocations and AS number assignments that have been made. As you can see the date, it's dated the 30th June, 2009, because this statistics are collected on a quarterly basis and this is being collected right now as we speak.
Starting with IPv4: How much IPv4 allocations have been handed out and how much is still available? Starting from the ring there, we can see that 35 /8s are not available. They have been reserved by the IETF for different purposes. Moving to the left you can see central registry with 91 /8. These are the /8s which have been allocated in the early days of the Internet and before the RIR system was set in place.
Now, going down, we can see that 100 /8s have been allocated to the RIRs. But as I said just at the beginning, these numbers are from June 2009 and this number in the meantime has changed and the total amount of /8s allocated to the RIRs is now 104, because both APNIC and the RIPE NCC in the meantime have received another two /8s each, bringing the amount of /8s allocated to APNIC to 34, RIPE NCC to 30, LACNIC still 6, AfriNIC 3 and ARIN 31. So this also means that the number of /8s reserved by IANA for future allocation is not 30 but is 26, as Leo has told us earlier this morning.
Now, how much address space has been allocated by each RIR in the last few years? We can see that there has been a steady growth over the years but if we look at the last three, four years we can see that the amount of IPv4 space allocated in the AfriNIC, LACNIC and ARIN region has been quite stable. There has been growth in the RIPE region, even though in 2008 this growth has stopped. And like Geoff showed us before, the amount of, there is still growth in the APNIC region where in 2008 a bit more than /8s have been allocated.
Now, if we look at the total amount of IPv4 address space allocated in the last ten years, we can see that the RIPE NCC has allocated 22.76 /8s, ARIN 21.23, LACNIC 3.55, LACNIC.88 and AfriNIC that.
Moving on to AS numbers. We can see that the first five years of this decade ARIN has been the RIR assigning the highest number of AS numbers. We can see that this role has somehow been taken over by the RIPE NCC since 2005. However, if we look at the numbers of the first six months of 2009, we can see that the number of AS numbers assigned in all the others has somehow been lowered and this is most probably due to the effect of the economical crisis in which we are at the moment.
Looking at the AS number assignments made by the RIRs in the last ten years. We can see that the RIPE NCC has assigned almost 18,000 of them, ARIN almost 19,000 and each of those two RIRs has actually made more AS number assignments than the other three RIRs together.
Moving on to IPv6 and to what I think is the busiest slide of this presentation. On the top left we can see all the IPv6 address space. A /3 of this block has been reserved by the IETF for global Unicast. Out of these, 512 /8s, a 506 are being reserved by the IANA for future allocations. Each of the RIRs has received a /12 in October 2006. However, before this date, RIRs would get /23 allocation blocks from the IANA, and that is what it's about the lowest by with all the other numbers because the RIPE NCC had received 15 /23s, APNIC 7, ARIN 5, LACNIC and AfriNIC 1. And 3 /23s has been allocated for special purposes.
If you look at the IPv6 allocations, the number of applications over the years. We can see that there has been some increase and a growth trend in the number of IPv6 allocations given out. This is probably due to the awareness in the Internet community about the depletion of IPv4 address space. However we can see a big jump in 2008 in the RIPE region, and this is mainly due to the fact that the RIPE community, in 2007, decided to remove one of the requirements of the IPv6 allocation policy, and mainly the one that was stating that an LIR had to plan for at least 200 end users within two years, removing this requirement has made it easier for LIRs to get their IPv6 allocation.
If we look at the chart on your left side, we can see the number of IPv6 allocations made by each RIR. The RIPE NCC has allocated about 15 hundred IPv6 allocations. ARIN about 620, LACNIC about 190, AfriNIC 70, and APNIC about 520.
Now, if you move to the other pie, the one on the right?hand side, we can actually see the amount of address space that has been allocated, calculated in /32s, because that is the minimum allocation size, we can see that the RIPE NCC has allocated more than 33,500, that is /32s, ARIN number 15,000, LACNIC about 200, AfriNIC 69 and APNIC about 24,000. Now, this actually means that many RIRs have actually been making ?? allocations, IPv6 allocations which are much larger than the minimum allocation itself.
If you want to see the statistics again or the latest ones, please see the NRO website and the raw data can be found on the IANA pages. So that's it from me. Do you have any questions?
CHAIR: Questions on the numbers? Geoff?
GEOFF HUSTON: If you go back to the IPv6 chart you had. I was just questioning this because I think, actually, this is quite misleading. Of the APNIC and RIPE numbers on the right, the 24,000 and the 33,000, which is basically a /20 in APNIC and a /19 in RIPE, how many individual allocations do they refer to? It's a rhetorical question because I know the answer. The answer is 3. And the reason is is that between January 1999 and somewhere around 2005 we were using an HT ratio of 0.8 and a /48 end site. So a /20 spanned around 6 million customers, an average large scale deployment. In the current framework, how much would you get for 5 million customers using an HD ratio of 0.93? You know and the answer is probably around a /25, /26, /27. So, I am pointing out that that slide is really quite misleading as to what it represents because it's actually the amalgam of two different policy regimes and there were really only 3 allocations that accounted for the bulk of that space and that was in the old policy framework.
ANDREA CIMA: I will bring it up with the other LIRs. You have got a point. Any other questions? Thank you.
(Applause)
CHAIR: Thank you very much. The last talk of this session will be just a general update from the NRO, which will be given by Axel.
AXEL PAWLIK: I am not adequately as you can see, as Paul has said we sent him off to represent all of us to Geneva. I think it's cold and range. I got lucky to sit in sunny Lisbon.
A quick update about the NRO, what it is and what we have been doing and what we are planning for the next couple of months. Basically the NRO is just all of the RIRs working together and you probably all know that already to represent all of ourselves with one voice. Formally protecting the unallocated numbers resource pool, although ICANN is doing that quite nicely currently. Protecting our policy development process. This is what we are doing here this week. We need to inform people about it, outside our traditional communities, politicians, governments and obviously generate business as well who are not familiar with it. And we are acting as the focal point for a one entry into the RIR system all over the world. We have been re?established basically the ASO with ICANN in a framework by MoU signed in 2004. Basically saying that the NRO is performing the role of the address supporting organisation within ICANN and that's what the numbers Council, or the Address Council is doing currently.
We have three of us all of us within the NRO. And the secretary, I am the secretary for the rest of the year and Rajoul from LACNIC is Treasurer. We also have coordination groups to help us organising or engineering and communications work among the RIRs. There is the engineering coordination group ECG with and re from the RIPE NCC as chair, and there is the CCG, the communication coordination group with Paul as chair, and recently we thought communications is great but we need also a group that focuses more on higher level political outreach governments and the like, public affairs and so I think this is the public affairs communications group, and Paul is chair of that as well.
We also, for as long as we contributed to the ICANN budget, have an idea of how we divide those expenses among ourselves and we do the same for overall NRO expenses. And you see the slides there. We have also recommitted ourselves to continue to contribute to the ICANN budget on the same level as year as before, so no big change there. Exchange of letters, basically.
And we do go, of course, to all the ICANN meetings in one shape or the other. This year we have been in Mexico and in Sydney. And we will go on to [] /STKPWHRAOUL in a couple of years weeks' time and we do all sorts of things there. One of the most visible and possibly most continuous feature there is that we relatively regular, you not at every meeting but certainly every second or so get invited and speak to the present to the governmental advisory committee, or to theirs as part of our outreach and we are usually very well received there and people are quite happy with what we are doing and even say that.
Internet governance forum: Obviously there is one of these events every year, and we very activity participate in those, we coordinate workshops among ourselves and with other parties as well, basically to represent, present what we are doing in the RIR world. There is the Multi?Stakeholder Advisory Group ?? the MAG ?? that is basically a group of quite a number of people from all over the place, from all walks of life, preparing the format of the fora, and [] Rajoul is in that for us. The next meeting in Sharm el?Sheikh, nice and sunny and warm probably, is taking place. There have been a number of preparatory meetings in Geneva already, we will have a booth there and we will send staff to do that. Basically, again, quite a number of staff from the RIRs and also board members from the RIRs going to be there to talk about the good things that we are doing. We also have a couple of years ago, started to produce a brochure from the NRO on continuing cooperation basically, again explaining in simple words and lovely pictures and some statistics what we have been doing. What we are doing and what we would like to continue to do and we have just redone this publication and will start distributing that then.
International cooperation: Well, the ITU is an interesting partner always and they have sometimes interesting ideas. So we need to talk to them quite closely, we do go to some of their meetings. Obviously right now and a number of other RIR stuff is in Geneva to represent ourselves at the Telecom World exhibition there to represent us for the next couple of days. Also at the staff level we go to the ITU and talk to the people over there, try to get some idea of what they are saying about studying of the allocation of Internet address space and how they see their role in that, and that's always interesting.
Also, you might remember last year in summer we went to the OECD managerial meeting. The one big thing for us was the establishment of the advisory committee, what's that, the IT advisory committee? The Internet technical advisory committee. Anyway, that has been decided to be brought into existence, and the RIRs are part of this, as is quite a number of other, from our friends in the technical, what we call the technical community, and of course, they have occasional meetings and request our presence and our advice there, so that's a very good, relatively new partnership.
Into 2009: We have done quite a bit in engineering, sort of parallel efforts to improve what we are doing and doing it together. Obviously v4/v6 is a really big issue there and we are continuing to have joint discussions among the RIR staff, the RIR boards and the like, and we manage to finally go out together to one retreat, all together it's the CEOs of the RIRs and some of their senior staff go to a retreat in Mauritius and to sit in side in an hotel room to think about quite a lot of things. We decided on the new coordination group there. We also looked at a way to improve the ways we work together and to improve communications within the NRO. Basically thought it doesn't make much sense ?? as you know the offices of chairman and secretary and treasurer go around the world among the RIRs on a yearly basis and we used to also rotate some of the technical infrastructure, which in the end doesn't make that much sense so we decided not to do that for some of them. We also said starting from next year the coordination group chairs should actually be very close to the Chairman of the NRO, so we'll start that next year, and we also said among ourselves, well seeing that short ASNs are getting relatively scarce, we want to restrict ourselves to getting two blocks on each occasion from the IANA.
And basically, that's it. If you have any questions, you are more than welcome... otherwise, there is a coffee break looming outside. Thank you.
(Applause)
CHAIR: Okay. We are just a little bit early. We'll let you go to your coffee break. The next session starts here at eleven o'clock, so we'll see you then. Thank you very much.
(Coffee break)
Next session at 11 a.m..