Transcript

Wednesday 0900-1030

SRINIVAS CHENDI: We will start soon, just going through some last-minute checks. I do apologize for this technical delay. Good morning. Welcome to APNIC plenary, IPv6 in 3D. First of all I would like to thank the session sponsors, Hurricane Electric. They have been sponsoring it in Christchurch and it is the second time they are sponsoring the session. This session has web casting with video, audio and, as you can see on my left, text streaming. If you would like to make comments or ask a question, please approach the mic, speak clearly, state your name and association.

Just one reminder, the online voting for the EC elections closed 9 a.m. local time. If you received proxy nominations, please check with the Secretariat. It is just outside the door. You can approach them. The chair for this session is Matsuzaki Yoshinobu.

MATSUZAKI YOSHINOBU: Good morning, this is Matsuzaki Yoshinobu from IIJ, I am chairing this session. Get started. The first speaker is Paul Wilson of APNIC. He will talk about APNIC IPv6 survey.

PAUL WILSON: Good morning, everyone. I am Paul Wilson, the Director General of APNIC. It is nice to see a reasonable crowd at this early hour. Thank you for being here. I am here to present some information from the latest APNIC member survey, which is a two-yearly survey carried out by APNIC of all the stakeholders and members on, in this case, specific information about IPv6. APNIC, the acronym, means the Asia Pacific Network Information Centre.

As an RIR, the traditional mode of publishing information has been limited to the database, the fact we have concrete information about IP address deployment and registration and so forth. We have also often been asked to publish a broader spectrum of information. This survey does fall into that category. The trouble with the traditional Whois information and deployment is it shows what happened, where addresses are being used today. It doesn't tell us what might be planned for next year or down the track.

Although we have published a lot of statistics about the deployment of v6 in particular, showing in general a fairly slow rate of deployment, accelerating now, it has prompted the question what is going to be happening in a couple of years' time, particularly when IPv6 addresses are depleting. How many have plans are in place now, and who is ready to deploy.

The idea of the survey - which I should mention is not incredibly detailed survey, it was orientated towards getting a more broad snapshot of the state of readiness for IPv6 - but the survey looks at the current position of v6 readiness, what are the needs of the community and what is the role of APNIC, or the expectations of APNIC, in the process.

As I mentioned, it was part of the latest overall APNIC survey, which is our independent survey, which is conducted by KPMG every two years. In this survey we have a fantastic response, 601 responses from 44 different economies. It has given a wealth of information across APNIC's planning and resource allocation. We did have the IPv6 readiness survey, including, comprising a number of factual questions and propositions which respondents could agree with or not and also a section about where APNIC resources should be allocated.

We had, as I say, quite a wide response, 52% of that response was from people who identified themselves as network provider. So that is 314 responses. We had 55 Internet bodies, as self declared, 106 in the category or other business.

Now, the factual responses were eight questions. The simplest question that we asked was whether you have deployed or are ready for immediate IPv6 deployment. 37% of respondents said yes to that question. So I mention again, this is regardless of whether or not these have actually received addresses. It is to do with readiness to deploy IPv6. Although 37% are immediately ready, the next question is whether or not your organization has a formal plan for deployment and 40% said yes, they have a formal plan. 38% said they had budgeted for future resource allocations for deployment and 39% said their organization had allocated human or financial resources. It is a fairly consistent of high 30s, 40% of the entire community respondents who are ready in one way or other to make concrete plans for IPv6 deployment.

Whether you see it as an encouraging sign or not is up to your own interpretation but the point about making the survey is to gather concrete information because it is only with concrete information we can drive some meaningful debate and planning and discussion about v6.

There are three remaining factual questions I want to report here. 36% of the organizations responding had actually received IPv6 addresses from either RIRs, NIR or from their ISP. That matches fairly well with the previous responses. Interestingly, we had more than half - 54% of respondents said they do have the knowledge and expertise required to move to IPv6. I think it is very encouraging.

What it is telling us is although approximately a third, or below a third, have concrete plans, we still have more than half the community who regard themselves as having the knowledge and expertise to move when required. The message here for those people is, of course, that we have probably two years, under two years to be implementing the plans. Those who have the knowledge and expertise, I expect you want to make the plans concretely in the fairly near future. Those in the other category clearly have additional work to do.

Around 50% of the respondents said IPv6-related training and information services are easily available. It is fairly worrying if half the community feel they have access to the information training services. Because, as I say, things will become critical in the near future.

I would like to mention a couple of the propositions, these are questions that the respondents were asked to indicate a level of agreement with between 1 and 10. The first one, which is clear, is calling for APNIC to have a bigger role in promoting IPv6 deployment. The average response was 8.44 - a high level of agreement. The other was related to government, which asked whether the government should be requiring IPv6 compliance with entities under their control. There is a fairly high level of agreement there too. It was reflected in one of the factual questions which also asked whether governments should have a role in actively supporting IPv6 and that was strongly supported as well.

The final section of the survey was about the allocation of APNIC resources in the IPv6 area. We had four areas of resource allocation which were strongly supported. First being 28% of APNIC resources should be going into IPv6 promotion, education or training. This would be of resources allocated to IPv6 activities in general. 23% of those resources to IPv6 infrastructure services such as ISP support, routing registries etc.

At the same level, what is described as consultancy or advisory services, which is different for a single organization to provide on a one-on-one basis but we do have a program of hosting the community of interest in IPv6 through the IPv6 Wiki, which is held on the website. Finally, also, with a reasonably high level of support is measurement, research and reporting on IPv6 deployment.

So in conclusion, from my point of view, as the head of APNIC, I am taking a very strong interest in the results of this survey. I think we will be carrying out further surveys in future. I would say, to ask, I would say, the same questions again to see how the responses change over time and more detailed questions as well. What we are seeing is there is still a great call and a great need for IPv6 training, education, information and that is something we will obviously continue to work on.

We have been called on as well as to liaise with government regulators to make sure they have understanding and support the transition. The support for government involvement in IPv6 needs to be dealt with fairly carefully because it can mean different things to different people. Taking the appropriate measures to promote IPv6 in government networks, government procurement, government organizations and so on.

Finally, APNIC providing support for the community to take the initial actions to bring IPv6 into the future business planning. So, as I mentioned, this is one part of the latest APNIC survey. This is a preview of some of the information that was gathered in the survey and the survey is a much broader instrument and much broader activity and there will be more reporting about that during this week and particularly on Friday during the member meeting. But I hope that information regarding IPv6 is a good start to the session today and the other presentations which are to follow. Thank you very much.

[APPLAUSE]

MATSUZAKI YOSHINOBU: Thank you, Paul. I would like to invite Martin Levy who, during ICANN 2008, took on the role of expanding the ICANN IPv6 commercial offering, including its expansion into Asia. So, Martin?

MARTIN LEVY: Good morning. Maybe that false start was the right thing for an IPv6 talk? But in reality, that is not really an option.

Out of the various layers that we are all going to talk about - I am pretty certain I have got the easier ask - going to talk about the IP layer, start at the bottom and work up during the talks. As we go through this, the reality is that this is a 10-year-old-defined RFC issue. Ten years should have been plenty. But we are here today and no, it isn't.

So as I go through this, what I want to talk about is the things that have been done. We have to address an interesting statistic that Paul showed, the fact that 37% to 40% - depending on which one of the graphs were in the deployment or planned-to-deploy area. It is a low percentage. But that truly does relate to this layer as it relates to the application layers and other layers that we are going to talk about.

So what we have is an educational level that is 50% in the stats but a deployment level that is lower. So I will talk about what it will take to finish off the IP layer, finish off the layer where in reality, the 100 bits of addressing lives, where the various core parts of the IPv6 protocols, the base parts exist.

As I said, I think the IP layer was the easiest one. It was defined. It was actually defined, if you think about it, 10 years ago. It really affects a very simple part of the whole protocol, everything we use, everything that runs on your laptops, it is just simply the base protocol layer. If I am very clever, I can completely ignore the issue of interoperability, move packets and not worry about whether the applications work. It is a very self-centred way of talking. But I have this layer and my colleagues here have the other layers. So let's just look at what happened and talk about this.

In reality, what it boils down to, at the IP layer, is IP allocation and availability and requirement to change that 37% - if you want to still be in business - to 100%. So I should be talking, in theory, to 63% of the audience here who are not ready.

So this is the timing. This is where we are today, in February, of 2009. Pretty soon, things start to change. If we, again, use the APNIC - using Geoff Huston's numbers here - within the next month, within the next month, we are T minus two years to the first major milestone where we have a problem. But the clock keeps on ticking. And you got to look at everything you need to do while that clock keeps on ticking.

As I said, I think the IP layer may have had the most time, and easiest to do. But as that clock keeps ticking you got to ask yourself, have I actually gone out and got my space? Not a hard task. Have I sat in the test lab and built a tester of some sort so I know my hardware is ready?

Well, the interesting thing about the hardware is the other thing this clock depicts is the fact the Telecom and IP backbone mode, in the application world, in the server world, application level, we look at hardware cycles, if we are lucky they last five years but technology being what it is, and the vendors being what they are, they want it quicker. They want to sell new hardware. If you have hardware and the network is two to three years old, the backbone side of things, not the application, not the soft touches of the end consumer, I am cheating somewhat because I come from a backbone side of the industry, the reality is that most are ready. The clock has been ticking for a while.

It continues to tick.

So now it question is: Are you ready to actually enable IPv6 on your network? For 37%, the answer is no. Then again, that part hasn't matched. Now it is one year until IANA and the press start talking about even more that there is going to be an issue in getting v4 space. The clock is now one year, less than the average cycle it could take for a large Telecom provider to go through project planning, financial, capital, and get everything ready to go.

Let's assume you are at that point. 37% are. Have you got your network connected? Have you got IPv6 routing that works properly? This IP layer definitely brought in a few problems. MTU issues, MTU discovery issues. Efficient routing. Is it going around the world twice to go somewhere? Was I even coming close to getting all the routes necessary? That is the part of the industry - the good news is - has had a lot of focus. Over the last year or so, has really cleaned up everything. So the routing side of things, a lot better now than it was. A lot better.

But the IP layer also has other things it needs to do. The IP allocation means you have to worry about things like reverse DNS. It is the responsibility of the IP layer, those people administering the IP layer. The reason is that everything else is going to get built on that so it has to be part of the services. The good news is some people have got it done. Other people, not so much. There is a joke about reverse DNS and IPv6 not being used in the same sentence. But then you end up with no space at IANA. Surely, at this point people are listening?

The 37% has changed. Surely, when we meet in year's time? What will it be? 70%? 80%? I can hope. But that is the work that is done had for this layer. So what else has to be done?

A funny thing is, if you look at a 7-layer stack in the network layer, there is a lot of evangelisation that needs to happen. It needs to happen even quicker than you can imagine. Because as you start looking at the clock now, we are a year and a half away from now. I do apologize. Now we have got to the point where your local RIR has said, "Within a year we will have real issues within the IPv4 space." But we don't have to worry about translation, I haven't talked about tunnels brokers and tunnels and 6to4. These are things that may or may not live in this layer, but at the present moment in time I don't need to.

So now we get down to the point: can we tell our real customers? Can we get to the point where the IP layer can service the rest of the players on the panel there that represent these higher and higher layers that make up a complete solution?

The answer is - it should be by this point - yes. From a technical point of view, you're talking about now two years from now. You are looking at vendors that are at the, hopefully, CPU, all those things have promised to truly provide the solution.

You are looking at core network, maybe axis network that provides a layer of connectivity. Hopefully, in two years' time from now, that percentage has risen to be absolutely critical mass because people want to still be in business. They still want to deliver to their customers.

So what is left? What is left is the fact that in two and a half years time or less there is, according to projections, no more v4 space to hand out to ISPs and backbones, no more to hand out to large cable or DSL providers. The clock has ticked and turned red. This talk isn't necessary in two years time, the theory is if the IP layer is not ready, this won't be reedy and there are a certain number of people who will be out of business.

Everything that goes on from this point is going to be depending on this layer. The theory is there is plenty of time for the players that talked through APRICOT or in the past, who have gone through again and again and explained what is necessary, myself included. However you have time this, this slide, you always get it off by six seconds, so I will fast forward the clock. A quick recap, because as I said, this part is easy.

Have we applied for space? Yep, absolutely! Have we picked the hardware and firmware? My theory is yes. There are some people who are thinking of upgrade but most people at the backbone level don't. So the number of backbones should be much higher than the number of axis networks. But I think that part is well known. You can tell I am being very optimistic here.

Are we truly dualstack everywhere? No, there are a fair amount of networks that are not and have an overlaid tunnel network on the side or have two separate networks, physically separate networks. If the clock is anything, then that should change.

Is there the global connectivity? Well, we are sitting here in the Philippines and got IPv6 connectivity, provided by one of the local providers. It connects globally through a number of different providers. It is completely doable. We know it is doable. A high percentage of us - because we are a motivated set of users are, in fact, happily using this within their office or sometimes home environment. But not the masses, we know that.

So, the masses when we get to route this out to the end-user, not just the test lab or the backbone. That is the hard one. It might not be an optimistic tick, it should be half a tick, maybe. The reverse DNS, it is a subtlety, I plead with a lot of people to do it. It is worthwhile. Have we evangelised it? We have done it excessively.

We see real use from customers? The talk out of APRICOT talked about bandwidth levels. It doesn't come out of thin air. It comes out of two cooperating entities on the Internet. Bandwidth from customer A and customer B of some other network, therefore that real traffic says there is real use out there.

So what is the summary, so I can get off the stage and go to the next person? At the IP layer we are done. Obviously, we need to have this. The problem must be another layer. Because at the IP layer, we are ready to go. In the true sense of handing it off, on that note, guys? I am done. I am happy. My portion is absolutely done.

[APPLAUSE]

MATSUZAKI YOSHINOBU: We need to support IPv6 servers as well, so I would like to invite Koichi Taniguchi. His experienced about IPv6, with his contribution.

KOICHI TANIGUCHI: Good morning, everyone. My name is Koichi Taniguchi and I work for Livedoor. Livedoor's main business is website hosting and datacentres in Tokyo, Japan. I am responsible for developing our company's website.

Today I am going to talk about adding IPv6 to the application layer, especially from the viewpoint of web application developer. Consistently, the main target of this presentation is layer seven developers.

First, I would like to start by explaining the background. Livedoor's famous IT company in Japan. Because we have a huge portal site that provides blog hosting, social networking, RSS reader, photo sharing, news, forecasts, maps, and everything else. And also, we have our own data centre that provides full managed hosting, ISP, public, WiFi networking and many other things. These two services are our main business.

We started an experimental service which provides IPv6 testing environments for application developers. It has capitalised on our strength.

Then, Mr Koich Ise - who is the chief technology architect of Livedoor - offered me to add IPv6 to one of our web sites to prove the implementation of it is not so difficult. I got started.

There were a lot of problems at the beginning. I didn't know what I needed to do to completely. I didn't know how to develop web applications on IPv6. Although, I Googled, I couldn't find any useful tips and hints in regard to application development with IPv6.

So, I researched and developed an IPv6 supported-web application through my own trial and error. And I mentioned it on my blog a couple of months ago. It was titled "8 Tips How to Add IPv6 To Your Application, If You Don't Have Enough Knowledge About It".

The blog entry received popularity from many web developers in Japan. So you can check the entry out at this URI. But unfortunately, I blogged it only in Japanese, because I usually don't read, write or speak English like this. Anyway, I am here today to present the English version of the blog entry.

Well, so much for preliminaries. Let's go on to the main subject.

Number 1: You need IPv6 connectivity. You might have terminating gateways add side and server side. At least both of them should handle IPv6. Additionally, the operating systems of your client and your server should also handle IPv6 in your testing environment.

However, if you can't improve the client's side environment, you can substitute an HTTP proxy which handles IPv6 for your HTTP client. If you want to use IP v4 and IPv6 dual-stack environment, you have to give IPv6 priority over v4 when you test your application. Please note that some of enterprise load balancers often don't support IPv6. It's not unusual.

Number 2: SSL server ID is same as before.

If you want to provide your website using SSL, you can reuse same SSL server ID that was issued by trusted CA when you use only IPv4. Because SSL server key exchange happens after the connection is established. It doesn't matter which version of IP you are using.

Number 3: Easy Apache configuration.

I always use Apache as a web server. Apache version 2 or later is introduced APR library that supports IPv6 by default. That is, Apache also supports IPv6 on version 2 or later. There are a few differences on the configuration of Apache.

Configuration of IPv4, listen, NameVirtualHost and VirtualHost directives allow you to set a socket address as the parameter. Socket address is a pair of an IPv4 address and port number. It is separated by a colon like this. In fact, you can omit the port number. Configuration of IPv6, these directives allow you to set an IPv6 socket address by the same token but if you set a bear IPv6 address, we can't discriminate whether the end of the parameter is a piece of IPv6 or address a port number. It is so confusing.

Then the part of IPv6 address must be bracketed by a square brackets.

But "allow" and "deny" directives allow you to set an IP address and an IP address with a netmask or an IP address with CIDR specification. You don't need to bracket the IP address whatever it's an IPv4 or IPv6 address.

Number 4: Ping and traceroute are not able to be used on IPv6. For instance, we usually use ping and traceroute commands simply to check connectivity to servers. But most of connecting commands are suffixed with six. Of course, can't execute traceroute6 command on Windows. If you use Windows, substitute traceert6 for traceroute6.

Number 5: Use AAAA record in DNS. We usually use a record to resolve names to IP addresses. But the names won't be resolved to IPv6 addresses from A record. If you want to resolve them to IPv6 addresses, you should configure your DNS to add IPv6 entries to AAAA record.

Number 6: Which version of IP is the client using?

If your environment is dual-stack, and it is using the same hostname on both IPv4 and IPv6, you should want your application to vary, based on the version of IP that is used by the client.

Only referring the remote REMOTE_ADDR environment variable in your application will meet your specifications. I think you don't need to check the format of addresses strictly. It won't be a problem on your application.

If your application server is listen to proxied requests on a private network and the reverse proxy is listening to IPv6 requests, you can add some extra HTTP request headers on reverse proxy with using module. For instance, configure your reverse proxy like this. Your application will be able to get the IP version in each requests by referring the added extra HTTP header.

Number 7: Expand the column length.

Typically, some sort of user-generated content application saves users' remote addresses into the database. The column had to have at least 15-bytes to store remote addresses on IPv4. If you are using a fixed and minimum length column for it, you have to alter the column length to at least 45-bytes.

Number 8: Check that access log parser.

There are so many access log parsers in the world. Some of them might be failed to parse some lines that are started by an IPv6 remote address. If you are using any parser to analyse your website, you should check whether the parser can parse such lines before enabling to handle IPv6.

These are the main subject of the article. And as you saw, adding IPv6 to the application layer is not difficult thing. Currently, the critical issue is that there are a great difference between the opinions of application layer engineers and lower-layer engineers about IPv6.

Most of the web application developers are poorly informed about IPv6, as you already know. As I mentioned before, I didn't know what I need to do completely, I didn't know how to develop web applications on IPv6. Although I Googled, I couldn't find any useful tips and hint in regard to application development with IPv6. To make matters worse, most of web application developers have some misunderstandings of IPv6, as I also used to have them. Almost all of them know that IPv4 will be exhausted but they aren't sure when it will be exhausted. Some of them hope that some new technology will appear, without much ado, to avoid IPv4 exhaustion. Most of them aren't motivated to add IPv6 because they think that IPv6 doesn't have any advantages. And most of them don't think that IPv4 has some serious disadvantages.

I thought that switching to IPv6 is a desperate situation.

Now, let's imagine that all of the interesting web sites you think will be phased out in 2011 or 2012. Please call out and introduce the fact to some layer 7 developer you know. I wish this slides will be a Bible for web application developers. Bridging the layers is our task in the near future.

Thank you for your kind attention.

[APPLAUSE]

MATSUZAKI YOSHINOBU: Thank you, now, I introduce Bruce Sinclair.

SRINIVAS CHENDI: Two minutes, we will switch the steno feed.

BRUCE SINCLAIR: Good morning everybody. It's actually a pretty crowded house. Yes, so as Martin said - we started down and dirty and we got a little bit higher up at the survey level and what I'll be seeking about is getting IPv6 into the home.

Yeah, dualstack, going dualstack at the backbone layer is not a problem. It's actually relatively simple and in fact, most of the equipment as you already know is already dualstack capable. In fact, even going and doing your access network. And doing what you think, yes, they may be applicable but may be small. So even the access layer in our experience is not so bad. You know what the real cost however is - and the real difficulty is actually getting it into the home. What that mines and remodelling the costs in terms of the sales people to go in and show our customers how to move forward with IPv6 and where their costs are going to be, but surprisingly, over 70% of the costs are actually at the CPE level in the home.

The problem is, even if you give the consumer, the home-owner a free device, a new free CPE, a new fancy wireless router, they don't install it. They don't want to play around with their networks. They're scared of it for most people. So what I'm going to be speaking about today is actually - I've been given the task of how to convince your boss it's time to go to IPv6 is to start deploying IPv6 but doing it with something that's interesting for the consumer to motivate them and what's even more important, interesting for the business people within the case that I'm talking about - the network operators, to move forward with an IPv6 deployment.

So just quickly about our company - our company's name is Hexago. We've been in the IPv6 business for almost 10 years, if you can believe that. You may be wondering how we're actually still in business. But we started out as consultants and in fact, we've been involved in the IETF and the working groups and where our main group is in the gateway and IPT and that type of equipment.

We're co-founders of the IPv6 forum and as mentioned yesterday, we've been involved in all of the IPv6 test networks.

In 2001, we launched a tunnel broker service called Freenet6. Some of you may be using it. Currently we have 180,000 user and we're deploying in parts of the world and very surprisingly or unsurprisingly, but encouraging, it has been doubling every six months for the last year. So the trend is hopefully going to go on. We released g4, that's what I'll talk about today, the back end that's powering the CPE in the home. I'll be doing a demonstration to show you the equipment and get a better sense of what we do.

We've been involved in quite a few deployments and trials since we were at APNIC. I bring up the customers from this region from China all the way down to Australia, in various forms. We have our system actually being deployed and used in different ways, but in fact, the companies that you see listed there are really the early adopters and the ones that went out there with the machete early in the jungle and going out there and putting IPv6 out there without a specific application that takes advantage of IPv6. If I have time in the presentation, I'll go into more details of what the operators have done to actually - I have some slides on the trials, but they're not what I'm going to be talking about today, except for... well, except for the first and third one.

But just to know that we've been actually out there, we've rolled up our sleeves and we've been deploying IPv6. So the typical situation that's even come up a few times already in this session is that - well, we know we're running out, but the problem is we don't know exactly when.

The people that are in charge of transitioning the network, the people who are in charge of making it secure, making it efficient, unfortunately, they're not the ones in charge of writing the cheques. So there's two constituents when I speak to an operator. The first one is the network engineering team. There's usually a task force that's brought together different folks in different organizations within the operator. And the second one is the business people who are actually making the decision to spend the capital expenditure on IPv6.

The engineering folks know that this is obviously overly simplified, but it's a lot of work to do, and from our projections, we think yeah, it's probably going to be two years, so we better get started. Unfortunately, business managers are not willing to spend the money until it is absolutely necessary. And this is obviously creating some problems for those of you or most of you who followed the IETF and the original work in the software group and the v6 OPS and how the world would transition to IPv6. The thinking was that it would be very orderly, the thinking was that the transition would move - first v4 and then v4 and v6 and then phase out v4 and everything would be fine. Well, that's not going to happen. It's not going to happen because the people writing the cheques to make this happen - unless the Government is forcing them to do so, will not write the cheque until the very last minute.

Now, what is the last minute? That's the problem. So the money is going to win, it's not going to be an orderly transition, everything is - in my view - the majority of the transition will happen right at the very last minute and we'll figure it out. But there's a better way. And what we as a company, being solely 100% dependant on IPv6, we can't wait. So we had to develop an application that would motivate our customers and right now, the leading customers are not so much the enterprise side, but the actual ISTs and the Telcos is to try to come up with an idea or an product set that motivates them to deploy IPv6 in advance of the actual depletion. And that's what I'll be demonstrating today.

So the ROI, that's the tough part. How do we generate an ROI? I was talking earlier about the home CPE and how expensive. This is what we called dongle 6. And this is another little CPE, but the way it works is that it plugs into the back of the - there is an inline version, maybe in the wireless router or the modem. The original intention of the device is that it is a client-server architecture for the gateway, for the tunnel broker so customers did not even like downloading the software. It is just a plug in play device and plug it in, it finds the tunnel and creates an IPv6 connection and the home is done. They don't know where it comes from, it just appears as if it is a dualstack connection.

But again, it's just the early adopters and I've seen a few of our customers in the audience and I've spoken to them. They're saying - OK, that's enough. But since we had this device, we thought, let's do something with it. Let's put a web server in it and let's take advantage of IPv6 and try to develop some services to galvanize our customers to move forward, and hopefully have something that's compelling for the consumer. So what we developed is something called mine portal. We thought,' not going to do IPv6 TV, it's been done. What we want to do is take advantage of the advantages of IPv6. Two big advantages. One is addressability. Being able to address various devices within the home is one, and the second is the peer-to-peer connectivity.

And the third one is the visibility to penetrate NATs in a simple but safe way. So the idea of the portal is - as the name implies - it's a web interface to your home.

I've spoken - I've already shown you the device, so very small plug that plugs into the back of the home. It also has USB connectors on it too, so you can - it's almost like a Internet interface for your so you can interface to anything that's on the Internet network, but also interface to anything that's on the USB device. You can put a USB on there and access USB as well.

OK, now I'm going to show you the product in action. The first service is call myCameras. It's really simple. It is plug a camera - in our case, the customer is using IP over power, so a camera, they plug the camera anywhere into their home, in the socket in their home. The camera is accessible immediately and plug and play and takes advantage of IPv6 and you can look at it on your phone on or your PC.

Remember, we have the USB device, so the second step is actually to store - kind of like a video surveillance, you can store images on the USB device locally if you ever want to use them for different purposes. So I'm going to sit down and show you the device now. I feel like Ray Charles here or something!

What we have here - I was frantically plugging all of this in here. We have the proxy for this device. This device is just a prototype that's been manufactured right now. It is not ready. What we've done is we've put the software on a number of different over-the-counter CPEs, but used Linksys, so this is taking the place here. I'm going to be accessing this device here, but I'm going to use IPv6. Now, I'm going to connect to the tunnel broker in Montreal, getting IPv6 and using it to connect to the device. But what with we do, what is very important is that we didn't want to enforce that the users of this device needed IPv6, so we in fact use proxying technology. The computer I use here - I guess - yeah, I guess the v4 also uses the phone. So it is in v4. The address when we address something in the home, we get the address of the gateway 6 device which proxies it into v6 and goes into the home and if necessary, the device is a v4 device, it does a reverse device. If it IPv6, it's no problem and stays that way. Obviously you can do it all in v6 but we've done this to make it a bit more widely appealing.

So I'll go through the interface of the device now. So again, where we are here, we're here and connecting and getting IPv6. This is automatically - and in fact, it also has the connectivity and it's gone out and made connection to Montreal and now we're getting connection through that IPv6 device.

OK, so this is the interface. It's very simple right now. There's an interface both for the PC and for the phone and I'll show you on my phone as well. You have a home page. This is expandable. You can use your imagination a little bit as to perhaps what you want to put on your home page. And then we have the three services that I'll talk about today. We have myCameras, myFiles and myDevices. So myCameras is really as sounds. Plug and play with this camera here. So here we are all.

So it's a little bit slow in the sense that we're travelling back and forth halfway across the world, but the concept is a very simple one. The concept is that you plug and play a camera. Use v6 for the capabilities and I'm here with the NAT and maybe there's multiple NATs. You can have multiple cameras obviously and you can set them up and I'm going to go through the set-up and the management and so forth, but you can provide different levels of accessibility to different users and make it a public camera or a private camera.

The second service is called myFiles. This is very simple for file sharing. The idea is that you can keep your files locally. A big trend right now, and I do it and I've seen the T-shirt around, the social networking T-shirt. I think statistically, eight out of ten of us have uploaded content to the cloud and then we provide access to the content via the social networking websites. The idea is that you can do that and the upload takes a little while. But as a first step, the idea is to put whatever files you want to share on a USB device. In this case it will be the little one or a thumb drive, any device that you want to make shareable, to yourself only or it could be to other people. You put files on here and all of a sudden, they're available through the interface. So peer-to-peer, NAT, it's all the same. We're just providing access to the different devices in the home. So I'm going to show you.

So I'm going to put a file on the thumb drive and then I'll plug it into the back of the dongle 6 and myPortal. This is the thumb drive right here and I have the Christmas card candidates from last year. Top candidates my wife did not like. This was the day before. This is the bottom one. She was in the wrong jacket! So the bottom candidates are there. As you can see, there's lots of snow. We'll look at it here. There's my family and there's the snow that I just left, that I'm happy to be here in the warmth right now because it's been about minus 20 in Montreal!

So very simply, so I bring up the USB and I'll just move this down to the bottom. It's OK, it's there. So now I have the file on the memory drive and then simply plug it. This is really simple. We want to make it as simple as possible and just plug it into the back of the dongle and there's USB connectors here. And I'm using this here and the idea is to plug it back and plug it in. And now we go back to the interface. We go to myFiles and there it is. So now we click on to here. So now we're using the file server software that's on the little device that we plugged into the back of the piece here.

You see this right here called "send to a friend". The idea of send to a friend is big mail. If you have an attachment of an e-mail on your USB drive or USB thumb drive, you can actually send an attachment to somebody of any size. Because when they get the e-mail - so you send to a friend and I'll show you here. You cut and paste the URL - this would be... I always get this wrong. Obfuscated..

The idea is that you can share an album, a DVD of any size, because when the person gets the e-mail, they click on the link and they start downloading there. So it's now just taking off here. So this is the home CPE, the home router and everything is plugged in the back switch here. Oh, the network is down right here.

So that's myFiles and the last service is myDevices. The concept here is just being able to access any IP device within the home. And in this case. I'm going to show you an example if I can get back the connection. I was actually connecting to this CPE and now I'm going through the APRICOT one. It might actually ask me for a password.

OK, we're back and I'm now using a different one. So lastly very quickly is myDevices. And I'll show you just an example of the automation. There's an interesting company that makes an IP power bar, so it allows you in a very simple way to turn on and off devices. You know remotely, so this is actually - because I didn't want to bring up that set-up, this is in Montreal. So it shows you, you can turn on your air conditioner on and off but I'll show you very quickly. But I'll show you quickly. The devices there, so as simple as that. Very simple. But you think that it is a simple concept and I done know if we have the killer application yet out of this one that I've shown you, but we think that at least it is a platform for maybe the application development.

I know we're in a rush but I had to do this one here. And that is the return investment. That was the whole point of this presentation, so that was the product. So the return investment is - now you need to convince the business manager to actually deploy the service. So why do that - just to give you some high level numbers and if anyone is interested in this is a model that our sales guys use and work with the customers, but just the highlights. The initial cost is $100,000. This gives you the equipment for what you need here and gives you also 900 dongles. The assumption of the model is around $7 per month and that's net to the operator from the consumer, providing the camera and in some places in the world, it's nanny cam and in other places in the world, it's home security. We're looking at a quarter time dedicated support person and around 300 new subscribers a month, so it is not too high. And the break-even is one year, so the break-even analysis is one year and after two years, you're making $1.69 for every $1 that you put into the program, so around a 69% return on investment.

So, in convincing this to make incremental revenue, it shows a return on investment which is good for the business people. And also what's very important is that now, whether the consumer knows it or not and really they don't care, it gives the network operator the chance to use IPv6 in the network which is really important, because there's lots of leaks and cracks and security issues that you need to work through. So this gives you the valuable experience for the future, and from a customer point of view, there's very little change.

And I think that's it. I think I've run out of time. But if anyone is interested, I've got some examples of different deployments that have been done over the last couple of years. So thank you very much.

APPLAUSE

YOSHINOBU MATSUZAKI: Thank you, Bruce. Now we open the mic for any comments or questions. Discussion?

SRINIVAS CHENDI: We have a number of participants on the remote participation as well through the jabber chat. If they have any questions, they can ask through jabber and one of our staff will relay it to the speakers here. Thank you.

ROQUE GAGLIANO: With the managers, talking with the people who have the money, that it is a bit more difficult, so I wonder what impact you think the current global situation is going to have on trying to convince the board manager in deploying this with the solutions?

BRUCE SINCLAIR: Yes, note that it is tough. The current economic situation has made it even more difficult. But I think that it has to do with the management in the organization. Going to IPv6 is inevitable. It's recession-proof, assuming the addresses are being consumed at the same rate they're being consumed now. They are going to run out and this just gives you an extra feather in your quilt to be able to try to make a convincing argument to move before that last minute. But obviously the economic environment doesn't make it any easier, that's for sure.

MARTIN LEVY: Yeah, I want to add just one thing to that. It isn't going to help in looking for people with capital expenditure. In fact, we know that some at the telecom companies have no capital expenditure. There are some companies who don't have it. But the reality is that the clock is ticking. So if you look at not how you are going to operate your business within this month, next month and the following month, you may also want to look at how you're going to operate your business in three years time. And if in three years time, you still want to be in business because you've managed to survive a serious downturn, then you need to know what to do now. And sometimes that may mean short circuiting grand plans, but doing nothing or continuously delaying quarter after quarter is a very foolish decision. The return on investment is always a key aspect. But the reality is that long-term survival is just as important and getting something done and getting an understanding of what needs to be done today, whether it is at the application layer, at the end consumer layer or at the backbone layer, put this aside and it won't matter whether we get a recovery or not. You could be out of business be. You just may not be in the prime area you're meant to be in with connectivity.

RANDY BUSH: Randy Bush IIJ. Two comments. One, I remember with amusement those large computer companies who were slow to get on the Internet. Secondly, I hope all my competitors are slow to get on IPv6.

YOSHINOBU MATSUZAKI: Any other comments? What do you feel about the IPv6 situation in this?

PAUL WILSON: The Internet development in the region as demonstrated by the address allocations is faster in the Asia-Pacific than anywhere else. And although in fact the amount of IPv4 allocated last year around the world was actually less in 2008, was below 2000. And in the Asia-Pacific region, it increased dramatically, and we were well ahead of the other regions in the total amount of address space allocated.

There is clearly a huge amount of growth potential in the region. I don't think we've yet seen a slowdown as a result of the economic climate, but we can look back at the history of IP address allocations over the last 10-15 years, and we do see two points at which allocation slowed down. Firstly during the Asia economic crisis in 1997 and 1998, and that again in 2000 during the dot-com crash. But in neither case did the IP allocations stop. We kept allocating addresses. Networks kept being deployed around the region and I suppose we are yet to see if the same trend happens now.

With respect to IPv6, we're certainly seeing ongoing interest in IPv6 allocations and last year, the number of allocations was dramatically higher than previously, and I think this year is starting off the same way. The number of addresses being deployed is actually substantially less, but that's only due to policy changes which have happened over the last year or so. I gather that Geoff may be standing up to give us some comments.

GEOFF HUSTON: Geoff Huston APNIC. I've done some analysis of the rate of allocations which have been happening since 2002 here, and it's certainly the case that seven years ago, globally the RIR system was allocating between the equivalent of four and six /8s a year. And in the period basically from 2004 to 2006, that increased very quickly. And by late 2005 and early 2006, we were looking at an average of around ten /8s a year.

Since then, it's been oscillating and there are still strong cyclical increases, and what happens is that between February and March, these operators get approval from the managers to go forth and get addresses and through the rest of the calendar year, you seem to then use them and ask for less. So around the start of the next year, you do it again. Now, this is March, it's the start of the year and yes, again, this is peaking again. And we're looking right now at a seasonally adjusted rate of 13 /8s a year. There are 32 left in the pool and five of those reserved for the last /8s. Go figure how much time IANA has left.

YOSHINOBU MATSUZAKI: OK, thank you, Geoff. And so, Bruce, could you share a comment from your customers?

BRUCE SINCLAIR: It's really dependent, the feedback, I'll just speak on the feedback on the early services that we showed here or that I showed here today. We've only done it in two operators, so it's very early. One has been more focused on security and that's been the camera, the camera side. And what we found and we're talking about less than 1,000 subscribers, so we're not talking in big numbers at all. But from a security point of view, it is the target market is the unmarried, 28-34-year-old woman that has... that's the data coming out right now. But that has the highest desire to simply look in their apartment before they enter. With their phone, so on the way home from work, on the train, that's been one piece of data that's been interesting, is that they simply want to look inside their house and make sure that the lights are turned on or whatever the case may be. And so, that's quite interesting.

YOSHINOBU MATSUZAKI: Any other comments? OK, then I would like to invite Miwa Fujii from APNIC to talk about the IPv6 program manager.

MIWA FUJII: Thank you very much. Good morning everybody. My name is Miwa and I work at APNIC. In the next five minutes, I would like to introduce IPv6 program wiki as a new APNIC initiative. IPv6 program wiki is an information sharing site about IPv6.

We want to make one-stop-shop for IPv6 information, so if you come to this site, you'll find the most useful information. We prepare customer's information for different layers. As our start-up process and this site is a dynamic site. The information will be constantly updated with community's effort. So if you find missing information or want to contribute content, please contact us. You can send your e-mail to IPv6@APNIC.net or add comment or create a thread through the IPv6 forum page.

So IPv6 forum page is completely open to the community. Please feel free to share your experience with IPv6 deployment, your knowledge about IPv6. If you're a network engineer or application developers, content distributors or content provider ors Government regulators, if you have any questions, please feel free to raise your questions and hopefully, the community will already have questions and will come back and share the information through this forum.

So many people have computers in front of you, so hopefully you can go to www.APNIC.net. Please quick on the bottom and you will go into the icons home page.

There are icons, IPv6 wiki link or on the left-hand side, on the menu bar there is an IPv6 menu link. Once you click there, you will be in the IPv6 wiki page. As you can see in this page, the various information is categorised. Information for ISPs, application developers, content providers, enterprises and regulators. And also information for business people, a different category. And more information is categorised in the detail so please take a look. Check what kind of information is so far applauded, and if you find any missing information or if you want to contribute, please feel free to join this site. This is your site, the community site.

Now, IPv6 forum, if you click IPv6 forum on the right-hand side menu, you go into the IPv6 forum page, and also to use this IPv6 forum page, you need to register. So please register and become a user.

This is the IPv6 forum page. Please feel free to share experience, knowledge.

Finally, I would like to seek from the community, your input and feed back or the site. Please participate in this survey. If you go into this icon wiki top page, there is the link. The feedback is very important. Click on the IPv6 wiki survey link. It will take only one or two minutes and very short and simple questions. We would like to hear how you feel about it about this site so far, and if you have any comment, please let us know.

And tomorrow, also if you participate in this survey, you will be enrolled into the lucky draw. The lucky draw will be at 5:00 on Thursday, February 26 and the lucky draw will be conducted on the last day of APNIC 27 on February 27, Friday. Two fantastic prizes are prepared, so please participate in the survey.

So thank you, and see you on IPv6 Program Wiki. It is really nice to see all of you in this room for this program. Thank you very much for your participation.

APPLAUSE

YOSHINOBU MATSUZAKI: Thank you very much. Are we finished? Just 3D. Here is Sunny.

SRINIVAS CHENDI: Thank you. Thank you to everyone for participating in the session. A few reminders, The NIR SIG starts at 11:00 in Sulu. We have a social dinner tonight sponsored by Hurricane Electric and Google. The buses will leave at 6:00 and the last one will leave at 6:15. The buses will leave from the exit where we had the breakfast.

There is a door prize and it is away from the hotel, a very nice venue and I'm sure that you will enjoy tonight's dinner. Please join me to appreciate our sponsor for this session, Hurricane Electric. Thank you very much.

APPLAUSE

Just a reminder of an informal dinner on Friday night. If you wish to come, please see the Helpdesk staff for purchasing the tickets. The seats are limited, so by Friday morning tea, we'll be selling the tickets for the dinner. Thank you very much.

APPLAUSE.

(End of session)