- ipv6-wg - mailman.ripe.net

New on RIPE Labs: IPv6 Deployment in Estonia
by Mirjam Kuehne 04 Jun '15

04 Jun '15

Dear colleagues, In case you missed Tarko Tikan's description of the IPv6 deployment in Estonia on other lists, we put the story on RIPE Labs: https://labs.ripe.net/Members/tarko_tikan/ipv6-deployment-in-estonia Kind regards, Mirjam Kuehne RIPE NCC

1 0

IPv6 only as default for next meeting
by Jérôme Fleury 24 May '15

24 May '15

During WG this afternoon, the idea was submitted that the IPv6 only experimentation be made the default SSID for the next meeting. While this has been working tremendously well for routine internet usage, I've been unable to use this network mainly because of incompatibility with my VPN network. We have a dual-stack VPN. some of the resources are v4 only though. The DNS64 converts my v4 VPN resources into v6 resources that are then routed to the non-VPN interface. While there could be workarounds (DNS64 on the VPN side, full v6 routing on the VPN, or all VPN resources available on v6) I don't think the technology is mature enough to make it the default for advanced usage. My 0.02$

11 18

How to Unsubscribe!?
by Adem Karatepe 15 May '15

15 May '15

Hi folks, I used to work in IPV6 work group before in my company and my colleague add me to this list but I'm not working on this group anymore and my colleague resigned from company so we don't have login details and we can not unsubscribe from the mail list. Is there any other way to unsubscribe? Adem Karatepe BT Proje Asistanı Project Support Staff Yazılım Geliştirme Direktörlüğü Software Development www.turksat.com.tr<http://www.turksat.com.tr> akaratepe(a)turksat.com.tr<mailto:akaratepe@turksat.com.tr> Gazi Üniversitesi Gölbaşı Yerleşkesi Teknoparkplaza kat 2 06830 Gölbaşı/ANKARA T : +90 312 497 47 00 F : +90 "Bu mesaj ve ekleri mesajda gönderildiği belirtilen kişi ya da kişilere özel olup gizli bilgiler içeriyor olabilir. Mesajın muhatabı ilgilisi ya da gönderileni değilseniz lütfen mesajı herhangi bir şekilde kullanmayınız çoğaltmayınız ve başkalarına ifşa etmeyiniz. Eğer mesaj yanlışlıkla size ulaşmışsa anılan mesaj ve ekinde yer alan bilgileri gizli tutunuz ve mesajı gönderen kişiyi bilgilendirerek söz konusu mesaj ile eklerini derhal imha ediniz. Bu mesaj ve ekindeki belgelerin bilinen virüslere karşı kontrolü yapılmıştır. Ancak e-posta sistemlerinin taşıdığı risklerden dolayı şirketimiz bu mesajın ve içerdiği bilgilerin size değişikliğe uğrayarak veya geç ulaşmasından bütünlüğünün ve gizliliğinin korunamamasından virüs içermesinden ve herhangi bir sebeple bilgisayarınıza ve sisteminize verebileceği zararlardan sorumlu tutulamaz.”<<<<< “This message together with its attachments is intended solely for the address(es) and may contain confidential or privileged information. If you are not the intended recipient please do not use copy or disclose the message for any purpose. Should you receive this message by mistake please keep all information contained in the message or its attachments strictly confidential and advise the sender and delete it immediately without retaining a copy. This message and its attachments have been swept by anti-virus systems for the presence of known viruses. However due to the risks of e-mail systems our company cannot accept liability for any changes or delay in receiving loss of integrity and confidentiality containing viruses and any damages caused in any way to your computer and system recipient, you are notified that disclosing, distributing, or copying this e-mail is strictly prohibited. “

1 0

Chair replacement procedure for ipv6-wg
by Dave Wilson 15 May '15

15 May '15

Hi all, You might remember from the last RIPE meeting that each working group had to finalise chair selection procedures. Because we were changing chairs anyway, ipv6-wg got to wait for one more meeting. Since the other working groups have gone through that process, however, we can use that to our advantage. Instead of starting from scratch, we propose to use a procedure which has already been discussed by a working group. The one we've chosen, because it seems very close to what we discussed at RIPE 69, is the procedure used by anti-abuse-wg. I hope this draft is already "good enough" for us to adopt as a result; if so, it'll save us repeating work that's already been done several times over in other WGs. We have this on the agenda for RIPE 70, and I hope we'll be able to adopt it then. Best regards, Dave ===(cut here)=== Note on Language: Throughout this document the word Chair shall be used for both Chairs and Co-Chairs. ** Introduction: This document outlines procedures dealing with the tenure of RIPE Working Group Chairs. It applies to all RIPE Working Groups. ** WG Chair Term: The term of a WG Chair is three years. A current chair may stand for re-selection at the end of their term. A WG Chair may resign voluntarily at any time. ** Selection of a WG Chair: WG Chair vacancies, along with a call for candidates, must be announced on the WG mailing list at least one month in advance of the date upon which the selection will be held. The announcement should set a closing date for candidates. A WG may request that a WG Chair vacancy be opened so long as the addition of a new Chair would not cause the number of Chairs of that WG to exceed three. WG Chairs are elected at WG sessions at RIPE meetings. Anyone physically present at the WG session is eligible to participate in the selection process. The candidate does not need to be physically present at the WG session. If possible the Chair should be elected by acclamation by the WG or by consensus after discussion. If the result is unclear, then a secret ballot should be held. In the case of a ballot, votes will be counted by RIPE NCC Staff and/or Chairs of other WGs. The result will be determined by simple majority. ** Removal of a WG Chair: A WG Chair may be unable to fulfil their duties as described in this document or otherwise fail to serve the WG and the community. With the endorsement of a significant share of the WG, a vote of no confidence may be initiated. Before a vote of no confidence is taken, due effort should be made to address the issue(s) leading to the vote. The right of reply must be given to all parties involved in the procedure. If this effort fails to resolve the issue, the vote may proceed. The vote must be requested on the WG mailing list at least one week in advance of the WG Session at a RIPE meeting and should take place during the WG session. Anyone physically present at the WG session may take part in the vote. The vote should be conducted by secret ballot and votes counted by RIPE NCC Staff and/or WG Chairs of other WGs. The result will be determined by simple majority. If the vote of no confidence in a WG Chair is passed, the seat is vacated and the WG Chair is not eligible for stand for re-selection. ** No Chair: If a working group is left with no Chair, e.g. due to the resignation or removal of the sole WG Chair, then the WG may elect an interim WG Chair according to the selection procedures specified above, but with candidates nominated at the WG session. An interim WG Chair must resign at the next WG session, but may stand for re-selection. ** Staggered Introduction: For the purposes of staggering the introduction of this policy, in the case where all co-Chairs of a WG have served for more than the standard WG Chair term limit, an optional waiver is given to these WGs to allow them to schedule the automatic resignations of their Chairs over the two RIPE meetings immediately following the adoption of this policy. If the WG decides to avail of this waiver, it is the responsibility of the WG to decide in what order its co-Chairs should stand down. ===(cut here)=== -- Dave Wilson, Service Desk Manager web: www.heanet.ie HEAnet Ltd, 5 George's Dock, IFSC, Dublin 1 tel: +353-1-660-9040 Registered in Ireland, no 275301 fax: +353-1-660-3666

5 6

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

14 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

ipv6-wg Digest, Vol 41, Issue 2
by behroz abbaszadeh 08 Feb '15

08 Feb '15

Thank You very Much I will Appreciate if you can Share the PDF version of Materials. Thank you Behrouz -------------------------------------------- On Thu, 2/5/15, ipv6-wg-request(a)ripe.net <ipv6-wg-request(a)ripe.net> wrote: Subject: ipv6-wg Digest, Vol 41, Issue 2 To: ipv6-wg(a)ripe.net Date: Thursday, February 5, 2015, 2:30 PM Send ipv6-wg mailing list submissions to ipv6-wg(a)ripe.net To subscribe or unsubscribe via the World Wide Web, visit https://www.ripe.net/mailman/listinfo/ipv6-wg or, via email, send a message with subject or body 'help' to ipv6-wg-request(a)ripe.net You can reach the person managing the list at ipv6-wg-owner(a)ripe.net When replying, please edit your Subject line so it is more specific than "Re: Contents of ipv6-wg digest..." Today's Topics: 1. IPv6-only network & Android 5 (Colin Petrie) 2. ipv6-wg Digest, Vol 41, Issue 1 (behroz abbaszadeh) 3. Re: ipv6-wg Digest, Vol 41, Issue 1 (Nathalie Trenaman) ---------------------------------------------------------------------- Message: 1 Date: Wed, 04 Feb 2015 13:55:35 +0100 From: Colin Petrie <cpetrie(a)ripe.net> To: ipv6-wg(a)ripe.net Subject: [ipv6-wg] IPv6-only network & Android 5 Message-ID: <54D216C7.9060709(a)ripe.net> Content-Type: text/plain; charset=ISO-8859-1 Hello, We thought you might be happy to know that the RIPE Meeting IPv6-only/nat64/dns64 network works with Android 5 (Lollipop) I tried this a few days ago on the meeting network kit in the lab here, using a stock 2012 Nexus 7 (which received a OTA update to Android 5 a couple of weeks ago). It uses RAs/SLAAC, plus RFC6106 for DNS options. Here is a link to the test-ipv6 results, from using Chrome while connected: http://isp.test-ipv6.com/?ip4=193.0.31.242&ip6=2001:67c:64:49:2cdb:4986:ce8… Glad to see one more major OS supporting V6-only networks! Regards, Colin -- Colin Petrie RIPE NCC ------------------------------ Message: 2 Date: Wed, 4 Feb 2015 22:44:46 -0800 From: behroz abbaszadeh <abbaszadehb(a)yahoo.com> To: ipv6-wg(a)ripe.net Subject: [ipv6-wg] ipv6-wg Digest, Vol 41, Issue 1 Message-ID: <1423118686.53039.YahooMailBasic(a)web125704.mail.ne1.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 I recommendation RIPE NCC to expand the training materials. For example Security in IPv6, APIs and .. Thank you ------------------------------------------ On Mon, 2/2/15, ipv6-wg-request(a)ripe.net <ipv6-wg-request(a)ripe.net> wrote: Subject: ipv6-wg Digest, Vol 41, Issue 1 To: ipv6-wg(a)ripe.net Date: Monday, February 2, 2015, 2:30 PM Send ipv6-wg mailing list submissions to ??? ipv6-wg(a)ripe.net To subscribe or unsubscribe via the World Wide Web, visit ??? https://www.ripe.net/mailman/listinfo/ipv6-wg or, via email, send a message with subject or body 'help' to ??? ipv6-wg-request(a)ripe.net You can reach the person managing the list at ??? ipv6-wg-owner(a)ripe.net When replying, please edit your Subject line so it is more specific than "Re: Contents of ipv6-wg digest..." Today's Topics: ???1. [training] RIPE NCC Webinars - new dates (Training Services) ---------------------------------------------------------------------- Message: 1 Date: Mon, 02 Feb 2015 10:49:15 +0100 From: Training Services <training(a)ripe.net> To: ipv6-wg(a)ripe.net Subject: [ipv6-wg] [training] RIPE NCC Webinars - new dates Message-ID: <54CF481B.3000109(a)ripe.net> Content-Type: text/plain; charset=utf-8; format=flowed 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://www.ripe.net/lir-services/training/e-learning/webinars 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 End of ipv6-wg Digest, Vol 41, Issue 1 ************************************** ------------------------------ Message: 3 Date: Thu, 5 Feb 2015 09:36:01 +0100 From: Nathalie Trenaman <nathalie(a)ripe.net> To: behroz abbaszadeh <abbaszadehb(a)yahoo.com> Cc: ipv6-wg(a)ripe.net Subject: Re: [ipv6-wg] ipv6-wg Digest, Vol 41, Issue 1 Message-ID: <0A1753E8-84C0-4AA0-A2CE-4907A5D20071(a)ripe.net> Content-Type: text/plain; charset="iso-8859-1" Dear Behroz, Thank you for your feedback. We are constantly expanding our IPv6 training course portfolio. At this moment, we offer 2 different IPv6 webinars plus the Basic and Advanced IPv6 course and we are developing an IPv6 training course for the RIPE NCC Academy as we speak. The topic of IPv6 security is covered in our Advanced IPv6 training course. You can find all our training material here: http://www.ripe.net/lir-services/training/material With kind regards, Nathalie K?nneke-Trenaman IPv6 Program Manager RIPE NCC On 05 Feb 2015, at 07:44, behroz abbaszadeh <abbaszadehb(a)yahoo.com> wrote: > I recommendation RIPE NCC to expand the training materials. For example Security in IPv6, APIs and .. > Thank you > > ------------------------------------------ > On Mon, 2/2/15, ipv6-wg-request(a)ripe.net <ipv6-wg-request(a)ripe.net> wrote: > > Subject: ipv6-wg Digest, Vol 41, Issue 1 > To: ipv6-wg(a)ripe.net > Date: Monday, February 2, 2015, 2:30 PM > > Send ipv6-wg mailing list submissions > to > ipv6-wg(a)ripe.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ripe.net/mailman/listinfo/ipv6-wg > or, via email, send a message with subject or body 'help' > to > ipv6-wg-request(a)ripe.net > > You can reach the person managing the list at > ipv6-wg-owner(a)ripe.net > > When replying, please edit your Subject line so it is more > specific > than "Re: Contents of ipv6-wg digest..." > > > Today's Topics: > > 1. [training] RIPE NCC Webinars - new > dates (Training Services) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 02 Feb 2015 10:49:15 +0100 > From: Training Services <training(a)ripe.net> > To: ipv6-wg(a)ripe.net > Subject: [ipv6-wg] [training] RIPE NCC Webinars - new dates > Message-ID: <54CF481B.3000109(a)ripe.net> > Content-Type: text/plain; charset=utf-8; format=flowed > > 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://www.ripe.net/lir-services/training/e-learning/webinars > > 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 > > > > End of ipv6-wg Digest, Vol 41, Issue 1 > ************************************** > >

1 0

ipv6-wg Digest, Vol 41, Issue 1
by behroz abbaszadeh 05 Feb '15

05 Feb '15

I recommendation RIPE NCC to expand the training materials. For example Security in IPv6, APIs and .. Thank you ------------------------------------------ On Mon, 2/2/15, ipv6-wg-request(a)ripe.net <ipv6-wg-request(a)ripe.net> wrote: Subject: ipv6-wg Digest, Vol 41, Issue 1 To: ipv6-wg(a)ripe.net Date: Monday, February 2, 2015, 2:30 PM Send ipv6-wg mailing list submissions to ipv6-wg(a)ripe.net To subscribe or unsubscribe via the World Wide Web, visit https://www.ripe.net/mailman/listinfo/ipv6-wg or, via email, send a message with subject or body 'help' to ipv6-wg-request(a)ripe.net You can reach the person managing the list at ipv6-wg-owner(a)ripe.net When replying, please edit your Subject line so it is more specific than "Re: Contents of ipv6-wg digest..." Today's Topics: 1. [training] RIPE NCC Webinars - new dates (Training Services) ---------------------------------------------------------------------- Message: 1 Date: Mon, 02 Feb 2015 10:49:15 +0100 From: Training Services <training(a)ripe.net> To: ipv6-wg(a)ripe.net Subject: [ipv6-wg] [training] RIPE NCC Webinars - new dates Message-ID: <54CF481B.3000109(a)ripe.net> Content-Type: text/plain; charset=utf-8; format=flowed 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://www.ripe.net/lir-services/training/e-learning/webinars 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 End of ipv6-wg Digest, Vol 41, Issue 1 **************************************

2 1

IPv6-only network & Android 5
by Colin Petrie 04 Feb '15

04 Feb '15

Hello, We thought you might be happy to know that the RIPE Meeting IPv6-only/nat64/dns64 network works with Android 5 (Lollipop) I tried this a few days ago on the meeting network kit in the lab here, using a stock 2012 Nexus 7 (which received a OTA update to Android 5 a couple of weeks ago). It uses RAs/SLAAC, plus RFC6106 for DNS options. Here is a link to the test-ipv6 results, from using Chrome while connected: http://isp.test-ipv6.com/?ip4=193.0.31.242&ip6=2001:67c:64:49:2cdb:4986:ce8… Glad to see one more major OS supporting V6-only networks! Regards, Colin -- Colin Petrie RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 02 Feb '15

02 Feb '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://www.ripe.net/lir-services/training/e-learning/webinars 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

[training] RIPE NCC Webinars
by Training Services 26 Jan '15

26 Jan '15

Dear colleagues, The RIPE NCC Training Services Department invites you to register 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://www.ripe.net/lir-services/training/e-learning/webinars 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

Last Call: "IPv6 Troubleshooting for Residential ISP Helpdesks"
by Jen Linkova 21 Jan '15

21 Jan '15

Hello, At IPv6 WG session in London, we discussed the most recent version of the "IPv6 Troubleshooting for Residential ISP Helpdesks" document. The proposed plan of action was to reach the consensus on the technical details of the document and then publish it (as combined IPv6 WG and BCOP TF effort). This email announces the working group last call for the "IPv6 Troubleshooting for Residential ISP Helpdesks" document. Please read the most recent version of it: https://www.ripe.net/ripe/groups/tf/bcop/ipv6-troubleshooting-for-residenti… and provide your comments to the list *until 23:59 Fri Dec 19th 2014*. Thanks! -- SY, Jen Linkova aka Furry

3 3

New on RIPE Labs: IPv4 and IPv6 Tweets on a Map
by Mirjam Kuehne 21 Jan '15

21 Jan '15

Dear colleagues, We looked at tweets mentioning IPv4 and IPv6 and how they appear on a map over time. It's great to see that IPv6-related tweets are more popular. Find more information on RIPE Labs: https://labs.ripe.net/Members/emileaben/visualising-ipv4-ipv6-tweets If you have any questions or suggestions, please let us know. Kind regards, Mirjam Kuehne RIPE NCC

3 2

Call for Presentations
by Benedikt Stockebrand 18 Jan '15

18 Jan '15

Hi folks, since the call for presentations for the plenary sessions of RIPE 70 on May 18--22 in Amsterdam (https://ripe69.ripe.net) is already out (see https://ripe70.ripe.net/submit-topic/submission-form/) we'd like to ask anyone interested in doing "anything" (presentation or whatever else, I'll just write "presentation" from here on) during the working group session to send us your proposal. A couple of notes about the procedure: - There is no formal submission mechanism as with the plenary/program committee. Just drop a mail to ipv6-wg-chairs(a)ripe.net and if we have any questions we'll contact you. - We're interested in pretty much anything related to IPv6, including deployment, operation, further development and whatever you think might be of interest to the working group. - If you're unsure about proposing your presentation to the plenary or the IPv6 working group, I suggest you submit it to the plenary through the link mentioned above and send us an e-mail in parallel; that way we have a better chance to make sure that topics too esoteric for the plenary may actually find their niche in the working group, rather than being lost forever. - What we do need are: - Your name and (at least) e-mail address - The (preliminary) title of your presentation - A (preliminary) abstract (a paragraph or two) - A short bio of yours - The time you roughly expect to need <=== IMPORTANT:-) - Whatever questions you have - We need to have an idea how much time we need for the working group session, so we can request an additional time slot from the NCC if needed. So please, send us at least a preliminary draft as soon as possible; you can always polish your proposal up afterwards. - And, as Filiz pointed out in the call for presentations for the plenary: "Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings." Cheers, Benedikt (with blessings from Jen and Dave) -- Benedikt Stockebrand, Stepladder IT Training+Consulting Dipl.-Inform. http://www.stepladder-it.com/ Business Grade IPv6 --- Consulting, Training, Projects BIVBlog---Benedikt's IT Video Blog: http://www.stepladder-it.com/bivblog/

1 0

IPv6 survey (JANOG 35 IPv6 session)
by MAWATARI Masataka 09 Jan '15

09 Jan '15

Hi all, JANOG will have a session "Why don't we want to deploy IPv6?" in JANOG 35 meeting next month. It will focus on IPv6 deployment of the contents providers in Japan. To help us make this session better, we carry out a questionnaire survey to the service providers. It would be great if you could fill out the following form: https://www.janog.gr.jp/meeting/janog35/program/ipv6/ipv6_form_en/ Your co-operation will be appreciated. We will make a good use out of the survey information in order to improve this session. We'll update you with more details about JANOG 35 meeting through the following page. http://www.janog.gr.jp/en/index.php?JANOG35_Meeting Happy Holidays! -- Japan Internet Exchange MAWATARI Masataka <mawatari(a)jpix.ad.jp>

1 2

We suggest that RIPE-554bis CPE equipment requires RFC 7084 and CE-Router Logo. Thank you!
by 邱萬德 09 Jan '15

09 Jan '15

Hello Sir: We suggest that RIPE-554bis CPE equipment requires RFC 7084 and CE-Router Logo. (https://www.ipv6ready.org/?page=documents&tag=phase-2-cpe ) CE-Router Logo are developed by US UNH-IOL, CableLab and Taiwan CHT-TL. CE-Router Logo Conformance Test Software is developed by CHT-TL IPv6 Testing Lab. The URL is as follows: http://interop.ipv6.org.tw/CERouter/ Thank you very much! Best Regards, Wan-Der Chiou@CHT-TL IPv6 Testing Lab. http://interop.ipv6.org.tw/English/index.php Requirements for CPE equipment Mandatory support: · RFC6204 (Basic Requirements for IPv6 Customer Edge Routers) * => RFC7084 and requires CE-Router Logo [../images/IPv6_CE_Router1.png] Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information.

7 10

[training] RIPE NCC Webinars - new dates
by Training Services 01 Dec '14

01 Dec '14

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://www.ripe.net/lir-services/training/e-learning/webinars 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