- ipv6-wg - mailman.ripe.net

Link to publicly available DNS64/NAT64 implementations
by Jan Zorz 15 May '15

15 May '15

Dear IPv6 WG, As promised during the IPv6 WG meeting at RIPE70, I'm sending the link with information how to test remotely different implementations of NAT64 that we are running in Go6lab: http://go6lab.si/current-ipv6-tests/nat64dns64-public-test/ Ecdysis is the weakest one and somehow a bit buggy, so please use the PAN and C1000 ones, that are dedicated boxes for this test and *will* handle the traffic and translation process ;) Cheers, Jan Zorz

4 3

Fwd: Re: IPv6-only network at RIPE70
by Wilfried Woeber 14 May '15

14 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Forgot to also include the wg mail list. sorry. Here you go, Wilfried. - -------- Forwarded Message -------- Subject: Re: [ipv6-wg] IPv6-only network at RIPE70 Date: Thu, 14 May 2015 11:50:07 +0200 From: Wilfried Woeber <woeber(a)cc.univie.ac.at> To: Jen Linkova <furry13(a)gmail.com> Hi Jen, v6-folks, > General feedback (do you guys see any value in such an experiment, > what was your experience etc) is appreciated. I was on this network while doing stuff after yesterday's key signing party, and it simply works, to fetch keys from servers and to upload. Just a minor thing and not too important for the "masses", but still thumbs-up :-) Wilfried -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVVQcKAAoJEPMGt0I/M2zSbX4P+waEJREbW9GoozrhpZov584V lKG5PKQGDRmLLvroF95Xr/KCKSMVwkOeE1Sizelh6uJXYkbnNpCCMifSg495SQY1 Oug/v0f6trhv03FpmQIKtpy2Jj9A3Vz6SislNbGFuvCB0T6LwV8vH1SKmGUdBeKX UoA8VfymQ6PGTOe2JsbIc6r3mdIhw9vjUeXYvoshEcItYmDYjrkXEELEO+YLpv88 8InaUVtlS1x5GR5M7DTaFhCjBaUPlEt9HXBk0BBg/6E+xXwaOU8JbtKq4yiifRH8 EjIEjsl77NGuhtlVPuUDmdq+pZ+Lgx9Sf1s0w7qOhQPxQI18EvnbqR0gVMZT0XGg PZjMt3W4AhktjXcwnS0bctCC+fdWYDK4YoxxhT9m9use94mj76Qk7BNMqyGKNJgF R9MFwps5pvVzykpoL0kHiIrfeN09EWMzjNTu+N5xUzu5KF4N3W431aYqsg4bFB64 mEbfzXbI7UBx7PYfCoGIvWwX+9Z4SM7MoO+FtZv/Bo/nXBP1X9nml2H3w0xYf7+R 2rOTciNesi9u1Mp0HCh6q0IUrijviw0QgdR7+fHYw7MDSbHmYaCO2ZGGDI8AVKjR aTf6Y6JZTr/WcH+nC18/Ix8gX88p8HfJT2bAsHVvmsAc5kzXxjlbklDFxMjYjV6i TaC7zIrY992Wt5ZXXFJc =FBOo -----END PGP SIGNATURE-----

1 0

IPv6-only network at RIPE70
by Jen Linkova 13 May '15

13 May '15

I'm glad to announce that there is a IPv6-only (with NAT64) network at RIPE70. Please note that this experimental network is not supported by the RIPE NCC or RIPE 67 Technical Team and is offered on a best-effort basis. How to connect: - Make sure IPv6 is enabled on your device - Connect to SSID: IPV6ONLYEXP - Enter the password: iknowbesteffort Please note that NAT64&DNS64 is used to provide connectivity to IPv4-only resources, so use DNS servers information provided by the network. If you see any connectivity issues: - connect to the 'normal' dual-stack one; - if connecting to dual-stack network solves the issue, please email me (furry13(a)gmail.com) with details, I'd love to know about any problems. General feedback (do you guys see any value in such an experiment, what was your experience etc) is appreciated. -- SY, Jen Linkova aka Furry

3 6

[training] RIPE NCC Training Courses July-September 2015
by Training Services 11 May '15

11 May '15

Dear colleagues, Our training team travels the RIPE NCC service region to deliver training courses to our members without any additional cost. Over the next few months, we'll be in Frankfurt, London, Skopje, Stockholm, Minsk, Sarajevo, Vladivostok, Tel Aviv, Tallinn, Zurich, Paris, Amsterdam. Visit the following page to register and to check which training courses we are giving in your area: https://lirportal.ripe.net/training/courses The RIPE NCC delivers the following training courses: - LIR Training Course - Database Training Course - Basic IPv6 Training Course - 2 day Advanced Training Course - Routing Security Training Course For more information visit: https://www.ripe.net/support/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 0

RIPE70 Draft Agenda
by Jen Linkova 14 Apr '15

14 Apr '15

Dear IPv6 WG members, RIPE70 is less than a month away and IPv6 WG is going to have two sessions, both on Thu, May 14th: - session #1: 09:00 - 10:30 (overlaps with DNS WG session); - session #2: 16:00 - 17:30 (overlaps with Database WG session). Please find the draft agenda below. NB: This time we are planning to have some informal discussion on IPv6 deployment bumps so please, please get ready to actively participate in the session! === Session 1, Thu, May 14th, 9:00 - 10:30 === A. Administrativia B. "HTTP state management (cookie) in an IPv6 world: apply caution!", Eric Vynke C. “Use Cases for IPv6 Extension Headers - Let's do some Marketing”, Wilhelm Boeddinghaus D. "OS Behavior in Contradicting Environments" , Enno Rey E. “IPv6 for ISP”, Aaron Hughes === Session2, Thu, May 14thm 16:00 - 17:30 === A. Administrativia B. WG Chair replacement procedure discussion C. "IPv6 - who is and who isn't" Geoff Huston D. Lighting talks: d1. "Lost stars”, Natalie Trenaman, d2. “Software & IPv6”, Natalie Trenaman d3. "554,631 - what's the next IPV6 speed-bump?" Jan Zorz E. IPv6 deployment bumps discussion/brainstorming session === If you have any questions/comments/concerns please do not hesitate to contact WG chairs (ipv6-wg-chairs(a)ripe.net) or reply to this email. -- SY, Jen Linkova aka Furry - on behalf of IPv6 WG chairs.

1 0

What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
by Philip Homburg 27 Mar '15

27 Mar '15

Dear community members, The RIPE Atlas team has a question what to do with probes that have only a Unique Local IPv6 Unicast Address (ULA) [RFC4193] as their IPv6 address. The question is whether to treat those probes as IPv6 capable or not. It is known that about 10% of the RIPE Atlas probes that have IPv6 addresses do not actually have IPv6 connectivity. This was documented by Stéphane Bortzmeyer in his RIPE Labs article "How Many RIPE Atlas Probes Believe They Have IPv6 (But Are Wrong)?" (https://labs.ripe.net/Members/stephane_bortzmeyer/how-many-atlas-probes-bel…) As a way of dealing with this problem, the RIPE Atlas system now tags probes that have broken IPv6. Any probe that has an IPv6 address (other than link local) but cannot reach the global internet is tagged as "IPv6 Doesn't Work" (see https://atlas.ripe.net/docs/probe-tags/) At the moment, around 2800 probes are connected and have an IPv6 address. Of those probes, around 350 (12.5%) are tagged that IPv6 doesn't work. Of those 350 probes, 114 have the surprising condition that the connect system call fails immediately with the error 'Network is unreachable.' Those 114 probes have two things in common, they have only a ULA address and the do not have a default route. It is the lack of default route that causes the connect system call to fail immediately. This feature (ULA and no default route) is specified in RFC-7084 (IPv6 CE Router Requirements) requirement ULA-5 ("An IPv6 CE router MUST NOT advertise itself as a default router with a Router Lifetime greater than zero whenever all of its configured and delegated prefixes are ULA prefixes.") The surprising thing is that for some probes this condition persists for many months. For the Atlas project, the question is how we should treat these probes. Currently they are regarded as having broken IPv6 connectivity. However, an alternative is to consider those probes as having no IPv6 at all. Broader questions are: are CPEs doing the right thing here. Should a CPE announce a ULA on the local LAN even if there hasn't been any IPv6 internet connectivity for a very long time? It is already complex enough for normal users to understand that there is always a link local IPv6 address even if there is no IPv6 connectivity. Now we have to add ULA to that group as well. So the question to the community, should RIPE Atlas treat ULAs in the same way as RFC-1918, addresses that should be ignored unless a valid global address can be found elsewhere. Or should we keep the current approach where ULAs are treated just like other global IPv6 addresses and consider the probe host's network setup to be broken? Philip

15 26

[training] RIPE NCC Webinars - new dates
by Olivia Mijnals-Ruimwijk 27 Mar '15

27 Mar '15

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://lirportal.ripe.net/training/courses Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

Re: [ipv6-wg] What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
by Geert Jan de Groot 26 Mar '15

26 Mar '15

As to the ATLAS-ULA discussion, here is a datapoint that may be interesting to some. After some network changes / upgrades, my probe was not happy with IPv6. For the built-in measurements, IPv4 was fine but all the IPv6 measurements were showing on-off behaviour with a cycle time of 2 hours. Initially I had no clue what was happening. Set up various IPv6 ping tests to the probe, and they were clean, and the measurements still showed the same outages. Also, measurements to other SLAAC clients were also spotless. While I was investigating something else however, I noticed these packets on the VDSL PPPoE-link to the ISP: 15:25:39.366673 IP6 fd0c:8f98:a1d2:80:6666:b3ff:fec5:dee.54536 > 2001:500:2d::d .53: 61413 TXT CHAOS? hostname.bind. (31) 15:25:41.911297 IP6 fd0c:8f98:a1d2:80:6666:b3ff:fec5:dee.46086 > 2001:500:2::c. 53: 64278 TXT CHAOS? hostname.bind. (31) Note the source address of these packets. Indeed, looking at the ATLAS portal, both the public IPv6 IP and ULA IP was listed on the info page of my probe, and the ULA IP didn't have connectivity. I diked out the ULA config on the OpenWRT router (not sure how it got there, probably PEBCAK but I didn't explicitely configure it), and things are a lot better now. Thanks to Philip for spotting the problem, Geert Jan

1 0

New Document Published - RIPE-631, IPv6 Troubleshooting for Residential ISP Helpdesks
by Nathalie Trenaman 26 Feb '15

26 Feb '15

Dear colleagues, I’m happy to announce we just published a new RIPE Document called "IPv6 Troubleshooting for Residential ISP Helpdesks”. This document serves as a best current operational practice for helpdesks at residential Internet service providers that offer IPv6 to their customers. The full text is available at: https://www.ripe.net/ripe/docs/ripe-631 The PDF version of this document was designed to have an easy-to-read layout so it can be kept close at hand and used as a reference document. Many thanks to the authors: Lee Howard, John Jason Brzozowski, David Freedman, Jason Fesler, Tim Chown, Sander Steffann, Chris Grundemann, Jen Linkova, Chris Tuska, Daniel Breuer, Jan Žorž, and everybody else in the community who contributed to this text. We would also like to thank the RIPE NCC staff who helped edit and publish the document. Best regards, Nathalie Künneke-Trenaman IPv6 Program Manager RIPE NCC

1 0

[training] RIPE NCC Training Courses April-June 2015
by Training Services 17 Feb '15

17 Feb '15

Dear colleagues, Our training team travels the RIPE NCC service region to deliver training courses to our members without any additional cost. Over the next few months, we'll be in Tashkent, Lisbon, Poznan, Belgrade, Manchester, Kuwait, Helsinki, Dublin, Nicosia, Kazan, Amsterdam, Vienna, Hamburg. Visit the following page to register and to check which training courses we are giving in your area: https://lirportal.ripe.net/training/courses The RIPE NCC delivers the following training courses: - Local Internet Registry (LIR) Training Course - RIPE Database Training Course - Basic IPv6 Training Course - Advanced IPv6 Training Course - Routing Security Training Course - DNSSEC Training Course For more information visit: http://www.ripe.net/lir-services/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 0