- ipv6-wg - mailman.ripe.net

Re: RFC 1918 in "production networks"
by Geert Jan de Groot 06 Feb '10

06 Feb '10

> If we use 192.168.1.0/24 for the RIPE meeting, and your corporate network > at home uses 192.168.1.0/24 as well, most VPN clients will NOT be able > to build a working connection. Try it. > Given the number of attendees, the chances for address collisions with > at least one participant's home network can be assumed to be near 100%. One workaround would be to have two (vastly different) 1918 prefixes and giving people the possibility to switch (so, 2 SSID's, 2 prefixes, say 192.168.224.0/20 and 10.210.32.0/20). Chances that someone will conflict with both, are small. For better or worse, we will need to learn how to deal with this - denying these issues doesn't fix the fact that these situations will happen, without the escape of availability of public IPv4 addresses, in the near future. And, of course, if nobody puts pressure on the VPN-sellers, these issues will stick around for *years*. Geert Jan

7 8

IPv6 Act Now update
by Chris Buckridge 04 Feb '10

04 Feb '10

Hi all, A couple of items from the IPv6 Act Now newsfeed over the last week that may be of interest: YouTube Turns On IPv6 support, Net Traffic Spikes (2 Feb 2010) Martin Millnert has already posted some useful information to the list on this subject. Google has quietly turned on IPv6 support for its YouTube video streaming Web site, which sent a spike of IPv6 traffic across the Internet. <http://www.ipv6actnow.org/2010/02/youtube-turns-on-ipv6-support-net-traffic… > IPv6: the new platform (3 Feb 2010) Some perspectives on IPv6 deployment from India, the second largest telecom market in the world. The article includes discussion of the IPv6 survey done in the Asia Pacific recently by TNO/GNKS, who worked with the European Commission and the RIPE NCC on an IPv6 Deployment Monitoring Survey last year: <http://www.ipv6actnow.org/2010/02/ipv6-the-new-platform/> Separate to IPv6 Act Now, the IPv6 adoption issue continues to gain exposure in the mainstream press. Dutch news site nu.nl ran an article this week based on the recent announcement from the NRO and ICANN that the pool of available IPv4 address space has reached 10%: <http://www.nu.nl/internet/2175537/internetadressen-raken.html> [in Dutch] Regards, Chris Buckridge, RIPE NCC

1 0

How polluted is 1/8?
by Mirjam Kuehne 03 Feb '10

03 Feb '10

[Apologies for duplicates] Dear colleagues, After 1/8 was allocated to APNIC last week, the RIPE NCC did some measurements to find out how "polluted" this block really is. See some surprising results on RIPE Labs: http://labs.ripe.net/content/pollution-18 Please also note the call for feedback at the bottom of the article. Kind Regards, Mirjam Kuehne

1 0

Youtube over IPv6!
by Martin Millnert 03 Feb '10

03 Feb '10

Hello fellow IPv6 admirers, (I'm sending this here on behalf of Shane. :) ) As you might know already, Google has been so *tremendously* kind to, as of ~22 hours ago, initiate the enabling of their Youtube site over IPv6. It is currently available to participants in their Google over IPv6 program, http://www.google.com/intl/en/ipv6/ . The www.youtube.com user interface so far does *not* have any AAAA published, but the *much* more important (traffic wise) image and video servers do. Use tcpdump to verify. Eg., anticimex@hsa:~$ host s.ytimg.com s.ytimg.com is an alias for static.cache.l.google.com. static.cache.l.google.com has address 74.125.13.213 static.cache.l.google.com has IPv6 address 2001:4860:4001:402::15 anticimex@hsa:~$ host v1.lscache1.c.youtube.com v1.lscache1.c.youtube.com is an alias for v1.lscache1.l.google.com. v1.lscache1.l.google.com has address 74.125.97.80 v1.lscache1.l.google.com has IPv6 address 2001:4860:4001:402::10 The time when it began is clearly visible in our own IPv6 graphs, http://stats.csbnet.se/public/ipv6/csbnet-ipv6-traffictypes.html , and you can see similar correlated data at for example http://www.de-cix.net/content/network.html . To figure out all the mappings they give you, if you want to trace etc, something similar to: "for i in `seq 1 24 `; do for y in `seq 1 8 `; do host v$i.lscache$y.c.youtube.com ; done ; done | grep 'IPv6 address' | cut -d' ' -f 1,5 | sort -uk2" could be used - at least from where I sit. Adjust for correctness. I'm sure that as this matures and bugs are wiped out, there will no longer be any need for the Google over IPv6 program and everybody will be able to access this. Until then, join! :) I bow to the Google IPv6 team, their netops and everybody there that is working so hard to give the Internet true CONTENT on IPv6. Yippie! From 48514, much of love! Thank you guys (and gals)! Regards, -- Martin Millnert <millnert(a)csbnet.se>

1 1

IPv6 Act Now news update
by Chris Buckridge 28 Jan '10

28 Jan '10

Hi all, In what I hope will be a regular addition to the IPv6 WG mailing list, I wanted to provide a quick round-up of some of the items we've featured in the IPv6 Act Now newsfeed over the past week. These are provided for your information, but also, we hope, to provoke some discussion. You're obviously welcome to discuss on this list, or you can leave comments on the new pages themselves at www.ipv6actnow.org. I'd also be keen to hear feedback on whether the WG feels that this is a useful activity! Regards, Chris Buckridge, RIPE NCC IPv6 interview: Maria Häll, Swedish Government (28 Jan 2010) Maria Häll, Deputy Director for the Ministry of Enterprise, Energy and Communications in Sweden, and Co-chair of the RIPE Cooperation Working Group, talks about the role governments can play in encouraging IPv6 deployment in the latest IPv6 Act Now video interview. <http://www.ipv6actnow.org/2010/01/maria-hall-interview/> Comcast to start a series of public IPv6 trials using 3 transition mechanisms (28 Jan 2010) Comcast announced plans to conduct production-network trials of IPv6 technology in the coming year. The trials are aimed at helping identify and solve any areas of difficulty involved in the transition to IPv6, and determining what approach will be the easiest and most seamless for Comcast's customers. <http://www.ipv6actnow.org/2010/01/comcast-to-start-a-series-of-public-ipv6-… > Blue Coat introduces industry’s first IPv6 secure Web gateway solution (25 Jan 2010) Blue Coat Systems announced that it has introduced the industry’s first IPv6 secure web gateway solution to enable the secure and seamless migration of applications, services and content between IPv4 and IPv6 environments. <http://www.ipv6actnow.org/2010/01/blue-coat-introduces-industrys-first-ipv6… > 2009, the year before IPv6 took off? (22 Jan 2010) Emile Aben, of the RIPE NCC Science Department, talks about some of the signs of IPv6 adoption seen from the RIPE NCC, in terms of traffic to RIPE NCC websites and services. [links to the RIPE Labs website] <http://www.ipv6actnow.org/2010/01/2009-year-ipv6-took/> BT Diamond IP awarded U.S. patent for integrated management of IPv4 and IPv6 (21 Jan 2010) Shane Kerr mentioned this briefly on the list earlier in the week: BT Diamond IP announced the awarding of U.S. Patent 7,623,547 for "Internet Protocol Address Management System and Method", an IP Address Management (IPAM) system which supports both IPv4 and IPv6 address space using a unique hierarchical container structure and block allocation techniques. <http://www.ipv6actnow.org/2010/01/bt-diamond-ip-awarded-u-s-patent-for-inte… >

1 0

Comcast IPv6 trials
by Sander Steffann 28 Jan '10

28 Jan '10

FYI: Jaap Akkerhuis just brought this to the attention of the Dutch IPv6 task force list: <john_brzozowski(a)cable.comcast.com> wrote: > Folks, > > I am emailing you today to share some news that we hope you will find > interesting. > > Today we are announcing our 2010 IPv6 trial plans. =A0For more informatio= n > please visit the following web site: > > http://www.comcast6.net > > We have also made available a partial, dual-stack version of our portal > which can be found at: > > http://ipv6.comcast.net

1 0

[Fwd: IPv6 deployment scenarios]
by Brian E Carpenter 26 Jan '10

26 Jan '10

Please excuse the interruption if you've already seen this. -------- Original Message -------- Subject: IPv6 deployment scenarios Date: Fri, 22 Jan 2010 10:37:08 +1300 From: Brian E Carpenter <brian.e.carpenter(a)gmail.com> Organization: University of Auckland To: nanog(a)nanog.org Hi, Sheng Jiang (Huawei) and Brian Carpenter (University of Auckland, research consultant to Huawei) are currently running a questionnaire on IPv6 deployment, addressed to every ISP. The purpose is to provide facts for a document about deployment scenarios that we are drafting for discussion in the IETF. We will keep your reply strictly confidential and we will publish only combined results. We will not identify information about individual ISPs in any published results. If you request it, we will not mention you or the ISP in the acknowledgments. Please find the questionnaire at http://www.cs.auckland.ac.nz/~brian/ISP-v6-QQ.html Answers are requested ASAP. (Hmm. As I write, the IPv6 access to that server is broken. Hopefully it will be back soon.) btw, we know that the questionnaire is imperfect; all questionnaires are imperfect. Also, this is not a marketing survey; we are after technical information. Regards Brian Carpenter

1 0

Call for nominations for co-chair position ipv6 working group 20100202
by David Kessens 25 Jan '10

25 Jan '10

I would like to invite everybody who is interested him/herself, or would like to propose somebody else for the position of co-chair of the ipv6 working group. Nominations should be received by me or on the list by close of business in a time zone of your choice by Feb 2, 2010. I already received two nominations for Shane Kerr <shane(a)time-travellers.org> and Marco Hogewoning <marcoh(a)marcoh.net>. The procedure that we plan to use to select our co-chairs is outlined in: http://www.ripe.net/ripe/maillists/archives/ipv6-wg/2010/msg00028.html As mentioned in the above mail, the exact selection procedure is still a proposal and subject to change. David Kessens ---

5 5

Two new IPv6 related articles on RIPE Labs
by Mirjam Kuehne 25 Jan '10

25 Jan '10

Dear colleagues, Please see two IPv6 related articles published on RIPE Labs recently: 1. REX - the Resource Explainer - is now also supporting IPv6 addresses. See a description and some examples here: http://labs.ripe.net/content/rex-supports-ipv6 Please check out the tool and let us know if you have any comments or suggestions. 2. We have been measuring IPv6 usage on RIPE Labs and other servers and found some encouraging results. You can find more details here: http://labs.ripe.net/content/2009-year-ipv6-took Kind Regards, Mirjam Kuehne RIPE NCC

1 0

Proposed procedure for ipv6 working group cochair selection process
by David Kessens 22 Jan '10

22 Jan '10

All, As mentioned earlier, I would like to write down our approach for co-chair selection. This would help us to have an open and transparent process to get a cochair appointed, but also help in the future for other working groups as either an example or at the minimum that they can use the same set of principles. I believe that this request already has resulted in a quite bit useful discussion on a few things that we should, or shouldn't do and many of you mentioned that it would be useful if we don't wait too long as our new charter would also be a good starting point for the appointment of (an) additional cochair(s). Below, I will summarize some of the key principles that I came away with and my initial idea on how to start the process. Since these are initial ideas, I very much welcome your input or if you would be interested in volunteering to work out the text further. At the same time, there doesn't seem to be much disagreement about the first step of the process so I would like to start with that step right away: an open call for candidates. I realize that there is a bit of risk involved on starting this before we have agreed on the full process: however, there has been already quite a bit discussion on the list on the general direction and I have confidence in our community that we will be able to find a workable solution along the way. I will send a seperate mail with an official call for nominations. David Kessens --- Date: Thu Jan 21 21:36:39 PST 2010 Draft Proposal on handling of chair position selection within the RIPE community RIPE (Réseaux IP Européens) is a collaborative forum open to a parties interested in wide area IP networks in Europe and beyond. Work is carried out within a variety of working groups. Each of these working groups has more than one co-chair. The selection process for a chair position is deliberately left to the working group, so that at any given time, the community is free to select the organisational structure that best reflects the work they want to do at that time. Working group chairs are responsible for organizing the working groups activities as defined in their charters. In addition, they are required to participate in the policy making process to judge and ensure that the RIPE policy making process has been properly followed after new policy proposals have been accepted by a working group (http://www.ripe.net/ripe/docs/pdp.html). While the actual implementation of the chair position selection process is on purpose not codified in any process document, it is expected that such a process follows the same principles as outlined in the RIPE policy development process: 1. It is open to all and follows an established, bottom-up process of collaboration. Everyone interested in the well-being of the Internet may propose a policy and take part in the discussions that follow on from the proposal. 2. It is transparent. All discussions and resulting actions are documented and freely available to all. 3. Conclusions are reached by consensus. 4. All policies are documented within RIPE Documents and placed in the RIPE Document Store The same dispute resolution process as used for the policy development applies to cochair selection process or results of the process. The Process As there is no standardized process for working group selection, this section serves as an example only and describes on how the IPv6 working group is currently selecting its co-chairs. The following is a proposal only and it has not been decided on how to continue after the nomination step. - Call for nominations of more than 7 days (self nominations being ok) - During the same time period: 1) The nominees are given a chance to determine whether they want to be considered or withdraw as they decided that there are other good candidates already available 2) The community may express opinions that could help the candidates to come to a decision on whether they want to be continued to be considered as a candidate - the community may consider appointing more than one co-chair in case of several good candidates - If the discussion period seems to result in a consensus decision, a last call of more than 7 days is issued or - Each nominee writes a short statement to the WG Mailinglist - Election using single transferable vote (we need to figure out whether we can do this online or wheter this is better done at the meeting) ----

5 6