______________________________________________________________________ DRAFT TRANSCRIPT SIG: IPv6 technical Date: Wednesday 1 March 2006 Time: 11.00am Presentation: ip6.int deprecation project report Presenter: Sanjaya ______________________________________________________________________ KAZU YAMAMOTO: OK, second speaker is Sanjaya, APNIC. He will make a presentation now - ip6.int deprecation project report. SANJAYA: Right, this is a project update of a proposal that got approved in the last APNIC meeting. The proposal was presented in the DNS Operations SIG and got approved. So this is just an update on what's the progress of the implementation of that proposal. This is the overview. I'll start with the background and then just a reminder of what the proposal is and the project status and then the questions and answers. Right, the background of this proposal is because the use of the ip6.int domain has actually been deprecated with the RFC 3152 in 2001. So it's a long time ago. Then there's a new - relatively new - RFC, 4159 in August 2005, that says, because it has been deprecated, then the RIRs are no longer required to provide the ip6.int service. And the fact that APNIC also has stopped accepting new ip6.int domains as of June 2004 but, however, the query rate is still there, then we need to consider an orderly shutdown of the survey. So the proposal says, "It is proposed that APNIC cease devoting resources to support the operation of this deprecated domain and the cut-off date to be determined jointly with the other RIR." And also the proposal contains all the steps for an orderly cut-off. That consists of notifying parties, notifying - making public announcements of the projects and then notifying the root ip6.int to remove APNIC delegation on the cut-off date and then actually stopping the service. So this report is actually planned already in the last meeting, that we are going to make an update on APNIC 21. Right, here's our observations and statistics. We are seeing that most IP6 data flow on ip6.int and ip6.arpa is actually to our server - the majority of them are basically zone refresh and notification from masters on update. We have two measurement points - two days in November, so late 2005, and then another six days' measurement in February 2006. Here is the observations we made (refers to slide). This is the total number of queries we are seeing in our traffic analysis. This is the zone update and this is just a notification from master to the secondaries. So this, the one I mark here, is the actual query from end-users. So it is really, really small compared to the zone transfer and the notifications. Now, I'm going to zoom in to that and it turns out that actually, in November 2005, there's a bump in Linux version that does some PTR queries, but this is not normal. The blue colour is the ip6.arpa look-up which is there, but it's OK. But the NS query itself and the A query is just under half of query per minute so it's much less than the five queries per minute that we observed when we first came up with the proposal. So it's now down to half query per minute for the end-user queries. So how many queries worldwide? We are seeing - in November 2005, we see 36 queries. In the February 2006 measurement, which is six days - remember that, in November 2005 it's two days' measurement and in February 2006, it's six days' measurement, it's down to 29 queries only. Compare that with the ip6.arpa queries, which is much larger so it looks to us like it's a healthy decline of ip6.int queries. Right, on to the coordination work. We have been spending some time consulting with the other RIRs and NIR. Meeting with the other RIRs has resulted in an agreement to coordinate the cut-off date as a global activity. So we are going to - all the RIRs will stop operation at the same time. We will collaborate in the public communications so everyone will know and also technical activities. With the NIR, primarily with JPNIC, we consult their community if there is any issues or scheduling conflicts. It seems that, after a few consultations, we pretty much agreed that June 1, 2006, would be the cut-off date. And we are planning to then - now that that date has been set, we will start talking with the root ip6.int, which is held by Bill Manning. So this is the schedule (refers to slide). We are here now, cut-off date on the first of June. There'll be a lot of basically communications and notifications because there are not many technical things to do other than close to the cut-off date, we will notify Bill Manning about one week before and then stop the operation. Most of the work is basically communicating with the secondaries, the end-users, if we still see end-users sending queries to us, we will ask them, you know, "Why are you still using ip6.int?" That's it. Any questions? Any objections about the target date, cut-off date, 1st of June? TOMOHIRO FUJISAKI: Can I ask one question. You have put down to notify the third parties - how will you do that? SANJAYA: Look at the addresses that send the queries. Look up whois and see if you can e-mail the holder. I mean, it's hit and miss. We will just do our best. We may not actually reach the end-user that queries us but at least that's the plan. Does that answer your question? KAZU YAMAMOTO: Is the cut-off date June 1st decided or subject to change? SANJAYA: It's pretty much decided, yeah. I think we're fixed on 1st of June. KAZU YAMAMOTO: Any other questions? SANJAYA: Can you confirm that that is the understanding we have? 1st of June? Yes. KAZU YAMAMOTO: OK, thank you very much. SANJAYA: Thanks.