- ipv6-wg - mailman.ripe.net

RIPE-501 replacement document - IPsec question to community - we need your input.
by Jan Zorz ＠ go6.si 27 Jan '12

27 Jan '12

Dear IPv6 community. (copy/paste from our internal discussion) The authors of RIPE-501 are finalizing the last comments from previous last call and would like community input for what to do with IPsec. All authors feel that IPsec should be a mandatory requirement for all devices although due to technical limitations, for mobile devices it will be optional. We are aware that RFC6434 made IPsec support a SHOULD rather than a MUST. From RFC 2119: SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. The change was largely due to limitations found in low power devices and therefore we still feel the community is best served by requiring mandatory IPsec support in all other devices (hosts, routers or layer-3 switches, network security devices, load balancers) If we get this input from you this year, there is a great chance that we could put out the new/final draft out for discussion and/or maybe last-last-call before new year. For RIPE-501 authors group, Jan P.S: wishing happy new year, merry xmass, happiness, IPv6 and all that stuff in at least next year :)

16 35

More IPv6 on mobile networks testing...
by Jan Zorz ＠ go6.si 18 Jan '12

18 Jan '12

Hi, I suspect some of you could find this interesting. Excuse to others for filling their mailboxes ;) http://go6.si/en/2012/01/nokia-usb-modem-21m02-ii/ Nokia USB "Internet stick" with PDPv4, PDPv6 and PDPv4v6 capability test. Cheers, Jan

3 2

IPv6 Launch Day
by Marco Hogewoning 17 Jan '12

17 Jan '12

The follow up on World IPv6 Day has just been announced. Marco http://www.worldipv6launch.org/press/20120117-2/ World IPv6 Launch Solidifies Global Support for New Internet Protocol Top websites, Internet service providers, and home networking equipment manufacturers commit to largest transition in the Internet’s history [Washington, D.C., USA and Geneva, Switzerland] – 17 January 2012 – Major Internet service providers (ISPs), home networking equipment manufacturers, and web companies around the world are coming together to permanently enable IPv6 for their products and services by 6 June 2012. Organized by the Internet Society, and building on the successful one-day World IPv6 Day event held on 8 June 2011, World IPv6 Launch represents a major milestone in the global deployment of IPv6. As the successor to the current Internet Protocol, IPv4, IPv6 is critical to the Internet’s continued growth as a platform for innovation and economic development. “The fact that leading companies across several industries are making significant commitments to participate in World IPv6 Launch is yet another indication that IPv6 is no longer a lab experiment; it’s here and is an important next step in the Internet’s evolution,” commented Leslie Daigle, the Internet Society’s Chief Internet Technology Officer. “And, as there are more IPv6 services, it becomes increasingly important for companies to accelerate their own deployment plans.” ISPs participating in World IPv6 Launch will enable IPv6 for enough users so that at least 1% of their wireline residential subscribers who visit participating websites will do so using IPv6 by 6 June 2012. These ISPs have committed that IPv6 will be available automatically as the normal course of business for a significant portion of their subscribers. Committed ISPs are: ● AT&T ● Comcast ● Free Telecom ● Internode ● KDDI ● Time Warner Cable ● XS4ALL Participating home networking equipment manufacturers will enable IPv6 by default through the range of their home router products by 6 June 2012. Committed equipment manufacturers are: ● Cisco ● D-Link Web companies participating in World IPv6 Launch will enable IPv6 on their main websites permanently beginning 6 June 2012. Inaugural participants are: ● Facebook (www.facebook.com) ● Google (www.google.com) ● Microsoft Bing (www.bing.com) ● Yahoo! (www.yahoo.com) Content delivery network providers Akamai and Limelight will be enabling their customers to join this list of participating websites by enabling IPv6 throughout their infrastructure. As IPv4 addresses become increasingly scarce, every segment of the industry must act quickly to accelerate full IPv6 adoption or risk increased costs and limited functionality online for Internet users everywhere. World IPv6 Launch participants are leading the way in this effort. For more information about World IPv6 Launch, products, and services covered, as well as links to useful information for users and information about how other companies may participate, visit: http://www.worldipv6launch.org About the need for IPv6 IPv4 has approximately four billion IP addresses (the sequence of numbers assigned to each Internet-connected device). The explosion in the number of people, devices, and web services on the Internet means that IPv4 is running out of space. IPv6, the next-generation Internet protocol which provides more than 340 trillion, trillion, trillion addresses, will connect the billions of people not connected today and will help ensure the Internet can continue its current growth rate indefinitely. About the Internet Society The Internet Society is the world’s trusted independent source of leadership for Internet policy, technology standards and future development. Based on its principled vision and substantial technological foundation, the Internet Society works with its members and Chapters around the world to promote the continued evolution and growth of the open Internet through dialog among companies, governments, and other organizations around the world. For more information, see: www.internetsociety.org Akamai Technologies, Inc. Jeff Young AT&T Jenny Bridges Cisco Marc Musgrove Comcast Jorge Alberni D-Link Denise Keddy Facebook Nisha Gulati Google Inc. Internet Society Wende Cover Internode John Harris Limelight Networks Microsoft Bing Bill Hankes Time Warner Cable Justin Venech Yahoo! Christina Scharrenberg

1 0

v6 World Connectivity To v4 World
by Matthew Walster 14 Jan '12

14 Jan '12

Apologies if this would be more suitable for IETF v6ops rather than IPv6-WG, I'm not overly familiar with the v6 development community. As is painfully apparent, most of the world if v4 only at the moment - and the various DNS ALGs etc for getting v4 connectivity onto v6 only connections seem "hackish" at best, and have real problems when it comes to things such as 1500-byte v4 packets needing fragmenting to travel over v6 nets. While playing with my local ssh daemon, I was reminded that inside my ssh client is a SOCKS5 server - I can connect to it by just setting my global SOCKS setting to use the localhost and all the traffic is forwarded down the tunnel to the remote host for processing. I was wondering whether anyone had any experience in setting a SOCKS proxy on a v6-only host, where the DNS/SOCKS proxies have both v4 and v6 addressing, and whether they can then access v4 services like web sites, mail servers, gaming applications etc. The basic idea is that you would use the v6 internet where possible, and go through your ISPs v4 SOCKS gateway for anything that didn't return a AAAA record. Is that idea right, and if so, is it sustainable? Assuming for the moment that I've made a correct assumption, is there a way we can make the process easier? Back in v4 world, there's DHCP option 252 which allows you to configure a WPAD file that would be downloaded and parsed by your web browser, setting HTTP proxies etc for certain classes of service - non-local traffic etc. Is it feasible to add an option to DHCPv6 so that a "v4 compatibility" string could be set, whereby a fall-back SOCKS server is used for non-v6 connections? Thinking off the top of my head, it would work as follows for the "no-clue" home user: User's router talks to ISP via DHCPv6: gets response detailing address to use also gets prefix delegation for local LAN usage also gets v4 compatibility string, which it stores for relaying to clients User's router listens for DHCPv6 requests, issues clients on local LAN public v6 addresses: sets option for v4-compatibility for clients User's computer turns on, asks for addressing information: gets v6 address via DHCPv6 gets v4-compatibility string and sets global SOCKS proxy variable, if not manually configured gets other string - DNS servers, routes etc. I stress that this idea is for v6/v4 co-existence, and isn't designed for "islands of v4" or "islands of v6", it would of course assume that v4 availability is restricted and a real effort to move to v6 was made. It's a transition mechanism that should be easy to turn off once most of the services have been migrated (hopefully transparently to the end customer). If there is a major flaw in my idea, I'd greatly appreciate constructive criticism and feedback! Matthew Walster

1 0

Latest 6::gle phone Nexus supports IPv6 on 3G
by Jan Zorz ＠ go6.si 02 Jan '12

02 Jan '12

All good in new year, the year of IPv6 :) In Go6Lab we tested new 6::gle phone with Android 4 and good news is, that it supports IPv6 PDP context over 3G. With Cameron from T-Mobile USA we are compiling list of apps, that are not working in IPv6-only environment, but for now we can live with it in everyday life :) The list will be published and compiled later. Short first report with snapshots: http://go6.si/en/2011/12/samsung-galaxy-nexus-nov-google-phone-podpira-tudi… Good news for start of new year. Cheers, Jan Zorz Go6 Institute Slovenia, CEO

1 0

Usenix: Google deploys IPv6 for internal network
by Carsten Schiefner 19 Dec '11

19 Dec '11

Dear all - maybe this: https://www.networkworld.com/news/2011/120911-usenix-google-deploys-ipv6-fo… is an interesting read-up for at least some of you... Best, -C.

2 2

Update in the RIPE document for IPv6 Allocation and Assignment policies
by Emilio Madaio 07 Dec '11

07 Dec '11

Dear colleagues, An editorial correction has been made to ripe-523 "IPv6 Address Allocation and Assignment Policy". The updated document has been renumbered to ripe-538. It is available at: http://www.ripe.net/ripe/docs/ripe-538 There was a mismatch between the policy text and the index title for section 5.4.2. This mismatch occurred between the updates from ripe-421 to ripe-450. Apologies for any inconvenience caused. Kind regards, Emilio Madaio Policy Development Officer RIPE NCC

1 0

on RIPE-523 IPv6 Address Allocation and Assignment Policy
by Jac Kloots 05 Dec '11

05 Dec '11

While I was reading RIPE-523 I noticed a mismatch between titles in the indexand the paragraph itself. The index for 5.4.2 says: Assignments shorter than a /48 to a single End Site While the paragraph title is: Assignment of multiple /48s to a single End Site Any change on getting this in line? Regards, Jac -- Jac Kloots Network Services SURFnet bv

1 0

New on RIPE Labs: Hampered Eyeballs
by Mirjam Kuehne 30 Nov '11

30 Nov '11

Dear colleagues, Please see a new article by Emile Aben on RIPE Labs: "Hampered Eyeballs - Observations on Two "Happy Eyeballs" Implementations" https://labs.ripe.net/Members/emileaben/hampered-eyeballs Kind Regards, Mirjam Kuehne RIPE NCC

1 1

New IPv6 related article on RIPE Labs
by Mirjam Kuehne 22 Nov '11

22 Nov '11

Dear colleagues, Please see a new article on RIPE Labs submitted by Emile Aben. It contains interesting treegraphs showing IPv6 deployment in correlation with the an LIR's size: https://labs.ripe.net/Members/emileaben/interesting-graph-ipv6-per-lir Kind regards, Mirjam Kuehne RIPE NCC

1 0