- ipv6-wg - mailman.ripe.net

RIPE75 IPv6 WG meeting minutes
by Jen Linkova 11 Apr '18

11 Apr '18

Hello, Just in time for RIPE76...;) Meeting minutes from RIPE75 IPv6 WG sessions are posted at RIPE website: https://www.ripe.net/participate/ripe/wg/ipv6/minutes/ipv6-working-group-mi… If you said anything at the mic during those sessions, please review and let us know if any correction is required! Thanks! -- SY, Jen Linkova aka Furry

1 0

New on RIP Labs: Persistent DHCPv6 Prefix Delegation at GavleNet
by Mirjam Kuehne 10 Apr '18

10 Apr '18

Dear colleagues, Read on RIPE Labs how Torbjorn Eklov helped municipalities in Sweden to deploy IPv6. In this second part he discusses how they used persistent DHCPv6 prefix delegation: https://labs.ripe.net/Members/teklov/static-dhcpv6-prefix-delegation Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: Connecting 5 Million Users to IPv6
by Mirjam Kuehne 04 Apr '18

04 Apr '18

Dear colleagues, Richard Patterson, Senior Network Design Engineer at Sky UK, describes on RIPE Labs how they connected 5 million users to IPv6: https://labs.ripe.net/Members/richard_patterson/connecting-5-million-users-… Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: The Avans Academy - Top of the Class in IPv6 Usage in the Netherlands
by Mirjam Kuehne 02 Feb '18

02 Feb '18

Dear colleagues, We met with the IPv6 team at the University of Applied Sciences in Breda, The Netherlands, and talked to them about the steps they took to deploy IPv6 in their network. Please find more details on RIPE Labs: https://labs.ripe.net/Members/nathalie_nathalie/the-avans-academy-top-of-th… Kind regards, Mirjam Kühne RIPE NCC

1 0

Call for presentations for the IPv6 Workgroup at RIPE76
by Jetten Raymond 02 Feb '18

02 Feb '18

Dear IPv6 WG list members, RIPE76 is coming up and its time again to grab your chances to present at the IPv6 working group, which will be on Wednesday 16 May 2018, in Palais du Pharo, Marseille, France. If you have a presentation or a topic that would be of great interest to the IPv6 WG, which unfortunately only has 1 timeslot this time, please inform the WG chairs on this. Send your presentation or explain the contents to ipv6-wg-chairs(a)ripe.net<mailto:ipv6-wg-chairs@ripe.net>. Rgds, Benedikt, Jen, Ray. For Internal Use Only

1 0

New on RIPE Labs: IPv6 Flow Label: Misuse in Hashing
by Mirjam Kuehne 12 Jan '18

12 Jan '18

Dear colleagues, Please read this new article by Joel Jaeggli on RIPE Labs: IPv6 Flow Label: Misuse in Hashing https://labs.ripe.net/Members/joel_jaeggli/ipv6-flow-label-misuse-in-hashing Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: How to Run and Protect an Email Server on IPv6
by Mirjam Kuehne 08 Jan '18

08 Jan '18

Dear colleagues, A new RIPE Best Current Operational Practices document is in the making. Please contribute your expertise! For more details, please read this short RIPE Labs article by Jan Zorz: https://labs.ripe.net/Members/JanZorz/how-to-run-and-protect-an-email-serve… Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: IPv6 in Enterprise Client Networks
by Mirjam Kuehne 04 Jan '18

04 Jan '18

Dear colleagues, A Happy New Year to you all! The first RIPE Labs article in 2018 explains how to deploy IPv6 in enterprise networks: IPv6 in Enterprise Client Networks by Wilhelm Boeddinghaus https://labs.ripe.net/Members/wilhelm_boeddinghaus/ipv6-in-enterprise-clien… Kind regards, Mirjam Kühne RIPE NCC

1 0

DMARC Solution Applied to this Mailing List
by Adam Castle 18 Dec '17

18 Dec '17

Dear Working Group, As more email providers enable Domain Message Authentication Reporting & Conformance (DMARC), some people find they can no longer receive emails from the mailing lists they are subscribed to. We have deployed a Mailman setting change to address this problem. After consultation with the RIPE Working Group Chairs, we have enabled the DMARC "Munge From" setting on all RIPE mailing lists. This means that if your email service provider has DMARC enabled, you will continue to receive all emails sent to this mailing list, but the "From" part of the header will change. If you don't have DMARC enabled, you won't see any change to the emails you receive from this mailing list. You can find more information about how we have been handling DMARC in the following RIPE Labs articles: https://labs.ripe.net/Members/adam_castle/dmarc-and-the-ripe-ncc https://labs.ripe.net/Members/adam_castle/ripe-mailing-lists-and-dmarc To ensure all working group participants are aware of the changes, I am sending this mail to all working groups. If you have any questions or encounter any issues on this mailing list, please let me know. Many thanks. Adam Castle Web Services Manager RIPE NCC

1 0

New on RIPE Labs: Let's talk about RFC 6980
by Mirjam Kuehne 13 Dec '17

13 Dec '17

Dear colleagues, This RIPE Labs article by Jacky Hammer covers the topic of whether different operating systems have correctly implemented RFC 6980 (Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery): https://labs.ripe.net/Members/jacky_hammer/lets-talk-about-rfc-6980 Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: IPv6 Addresses, Security and Privacy
by Mirjam Kuehne 08 Dec '17

08 Dec '17

Dear colleagues, The choice of the IPv6 address format impacts a host's security and privacy. This new RIPE Labs article by Johanna Ullrich discusses this impact, highlights how current address formats deal with matters of security and privacy, and pinpoints shortcomings in today's addressing mechanisms: https://labs.ripe.net/Members/johanna_ullrich/ipv6-addresses-security-and-p… Kind regards, Mirjam Kühne RIPE NCC

1 0

Join APNIC's IPv6 Hackathon at APRICOT 2018
by Vesna Manojlovic 07 Dec '17

07 Dec '17

Dear colleagues, I am very happy to invite you to the APNIC's first Hackathon, to be held from 23 to 25 February 2018 in Kathmandu, Nepal. What are Hackathons? -------------------- Hackathons (hacking marathons) are events where a group of people work together on a pre-defined set of problems, intensively, for a period of a few days. At the first APNIC Hackathon, participants will identify and help resolve IPv6-related challenges of their choice. Attendance is free but will be limited to 25 participants. Who should apply ---------------- - Informatics professionals (developers, testers, designers and so forth) - Telecommunications professionals (network/telecom engineers, network administrators/operators and so forth) - Researchers working on Internet measurements, networking, or similar projects - Advanced students of technology degrees For more information, application form, and key dates, visit the APRICOT 2018 website: https://2018.apricot.net/program/hackathon Participants will also receive an APNIC Hackathon t-shirt, a certificate of participation, and a chance to win assorted prizes. For any further queries, please email the Hackathon team at: conference(a)apnic.net Regards, Vesna Manojlovic Community Builder RIPE NCC

1 0

Results of the RIPE NCC Hackathon Version 6
by Vesna Manojlovic 28 Nov '17

28 Nov '17

Dear IPv6-wg, the topic of sixth RIPE NCC hackathon was, appropriately, IPv6 :) The highlights of the event: * 32 people from 18 countries participated * 6 projects were finalized * most future impact: ICMPv6 support for libpcap * most educational: Pocket Internet (lab of VM pods) * mostly covered topic: visualizing IPv6 deployment * most data used: RIPE Atlas traceroutes Please read the full report, with all the links, here: https://labs.ripe.net/Members/becha/results-hackathon-version-6 If you use one of the projects for your work, implement it or make further modifications, I would love to hear about it! Regards, Vesna

1 0

New on RIPE Labs: IPv6 Week Denmark
by Mirjam Kuehne 22 Nov '17

22 Nov '17

Dear colleagues, An IPv6 week is an opportunity to raise awareness and stimulate IPv6 deployment on a national level. It brings a wide variety of stakeholders, knowledge and experience to a country where deployment of IPv6 is low. One of the key factors affecting the success of a national IPv6 week is support from the local community. In Copenhagen, we were very happy to have assistance from DKNOG in preparing and delivering this event. You can now find a report on RIPE Labs: https://labs.ripe.net/Members/nathalie_nathalie/ipv6-week-denmark Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: IPv6-only? IPv4-as-a-service?
by Mirjam Kuehne 03 Nov '17

03 Nov '17

Dear colleagues, Please find this new article by Jordi Palet on RIPE Labs: IPv6-only? IPv4-as-a-service? We are starting to hear “IPv6-only” more often. However, it doesn't seem to be clear what exactly this means. Read Jordi's explanation: https://labs.ripe.net/Members/jordipaletm/ipv6-only-ipv4-as-a-service Kind regards, Mirjam Kuhne RIPE NCC

1 0

Looking for a secon opinion on using ULA along with GUA for residential access
by Radu-Adrian FEURDEAN 01 Nov '17

01 Nov '17

Hello, During the evaluation of a new model of CPE for our residential access we found one of the suppliers providing an option to announce a ULA prefix in addition to the GUA prefix obtained from DHCP-PD. I would like some second opinions regarding auch a practice. >From my point of view, if ULA is enabled: - it allows the client's LAN to stay IPv6-enabled even when the internet connection is down. It is a simpler version compared to the use of link-locals. - if the "auto" version of the setting is used, the ULA prefix will risk changing when changing the CPE, which is less than optimal. If ULA is disabled: - business as usual; when internet is down the client will only have RFC1918 (v4) + link-local (v6) So, is it worth enabling an additional ULA on the LAN ? -- Radu-Adrian FEURDEAN

3 2

New on RIPE Labs: IPv6 Address Planning in GavleNet
by Mirjam Kuehne 01 Nov '17

01 Nov '17

Dear colleagues, Here's a new article by Torbjorn Eklov on RIPE Labs in which he describes how he helped a municipality network to deploy native IPv6 for fibre-to-the-home customers: https://labs.ripe.net/Members/teklov/ipv6-address-planning-in-gavlenet If you have any thoughts or comments on Torbjorn's article, please sign in to RIPE NCC Access and post them below the article. Kind regards, Mirjam Kühne RIPE NCC

1 0

Happy Eyeballs reporting
by JORDI PALET MARTINEZ 27 Oct '17

27 Oct '17

Hi all, After my presentation this week on Dubai about this topic, I got several folks telling me that they believe this is very interesting. Here is again the link to the document: https://tools.ietf.org/html/draft-palet-ietf-v6ops-he-reporting-00 And to the slides from this week: https://ripe75.ripe.net/presentations/129-ipv6-hev2-v2.pdf The major concern is privacy issues. My response to that is that we have the same when we log other protocols, including CGN, etc., in addition to that, for signaling the ISP that there is a problem, we don’t really need to log the complete source IPv6 address that doesn’t work, just the prefix, and also, we have a simpler alternative. If the logging is only for the destination IPv6 address and not the source one, I think in a big % of the cases, is sufficient for the ISP to know that there is some problem from its network to the failed destination (so the ISP could replicate the failure from any other source address in its network to the same destination). This logic, I believe, will only fail if the problem is specific to the “interior” of the customer network, which will be out of the scope of the ISP (and even do, the ISP will be able to tell the user --- hey this destination works from my network, not from yours, so something got broken inside your network). I’m going to submit a new version of this document on Sunday, so if you have inputs, please, let me know ASAP. Thanks in advance for your inputs ! Regards, Jordi ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

1 0

Unique /64 per host
by JORDI PALET MARTINEZ 25 Oct '17

25 Oct '17

This is the draft we mention in the WG meeting: https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv6-prefix-per-ho… Regards, Jordi ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

2 1

RIPE75 - IPv6 fragmentation tool - Grafical solution - Opensource
by Stefan Jakob 25 Oct '17

25 Oct '17

Hi IPv6 Folks, Two colleagues of mine (Lorenz Schäfer under guidance of Jürgen Geinitz) created a grafical open source tool (python tk) to play around with your IPv6 space. The tool is inspired by Painting by Numbers presented at RIPE68 by Helge Holz. [1] --- README.md snip --- Description: This tool should make assigning of IPv6-address-blocks more manageable and easier to comprehend by showing the availible address space in an 8-bit matrix. In the left frame you can create radiobuttons, assigning them a name, colour and finally a certain address-space, which will be colored in the matrix and displayed in a label accordingly. --- README.md snap --- Since I am attending RIPE75 and some people didn't know about the tool, you chance to get a live demo today (maybe after the IPv6 WG) # long URL https://github.com/lorenz-schaefer/IPv6-address-space-fragmentation-tool # short URL https://goo.gl/KmyBLZ Rgds, SJ [1] https://ripe68.ripe.net/presentations/344-Painting_by_Numbers.pdf Beste Grüße, Stefan Jakob -- DENIC eG, Kaiserstraße 75 - 77, 60329 Frankfurt am Main, GERMANY E-Mail: jakob(a)denic.de, Fon: +49 69 27235-142, Fax: -235 https://www.denic.de Angaben nach § 25a Absatz 1 GenG: DENIC eG (Sitz: Frankfurt am Main) Vorstand: Helga Krüger, Martin Küchenthal, Andreas Musielak, Dr. Jörg Schweiger Vorsitzender des Aufsichtsrats: Thomas Keller Eingetragen unter Nr. 770 im Genossenschaftsregister, Amtsgericht Frankfurt am Main

1 0

Captive portal over IPv6
by Shahin Gharghi 24 Oct '17

24 Oct '17

Dear all, I have a public WiFi service which connects people to internet via hotspot (captive portal). I want to assign IPv6 addresses to users in dual-stack, but my captive portal doesn't support. Do you know any captive portal that supports IPv6? Both hardware and software models works for me. Thank you -- Shahin Gharghi

2 1

RIPE74 meeting minutes
by Jen Linkova 24 Oct '17

24 Oct '17

I've just realized (as I do every 6 months....) that I should have sent a link for the meeting minutes from the previous meeting... Here we are: https://www.ripe.net/participate/ripe/wg/ipv6/minutes/ipv6-working-group-mi… Please review and let us know if anything should be changed. Thanks! -- SY, Jen Linkova aka Furry on behalf of IPV6 WG chairs

1 0

IPv6 Radius Attributes
by Shahin Gharghi 21 Oct '17

21 Oct '17

Dear all, Do you have any idea how many IPv6 Radius Attributes are supported by Cisco? I need to send Framed-IPv6-Prefix (Attr 97) to radius server or find a way to send assigned IPv6 of PPPoE connection(both SLAAC and DHCPv6) to radius server. -- Shahin Gharghi

2 2

RIPE-690 document is now published...
by Jan Zorz - Go6 20 Oct '17

20 Oct '17

Dear RIPE IPv6 WG community, In past year you have heard a lot about this "Best Current Operational Practice for Operators: IPv6 prefix assignment for end-users - persistent vs non-persistent, and what size to choose" BCOP document draft that many of you also co-authored or contributed to - and I would like to thank chairs of IPv6 WG and also the whole community for all hard work and time, put in this BCOP. The document was recently published as RIPE-690!!! https://www.ripe.net/publications/docs/ripe-690/ Congratulations to everyone and thnx also to RIPE NCC staff for transforming the draft into a RIPE document!!! Cheers and see you all in Dubai next week, Jan Zorz

4 3

Fwd: [Int-area] Liaison statement received from ITU-T regarding a "Reference Model of IPv6 Addressing Plan for Internet of Things Deployment"
by Rob Evans 05 Oct '17

05 Oct '17

Hi, This seems to cover areas where RIPE IPv6/IoT people might have some expertise. Cheers, Rob Forwarded message: > From: Suresh Krishnan <suresh.krishnan(a)gmail.com> > To: 6lo(a)ietf.org, 6man WG <ipv6(a)ietf.org>, 6tisch(a)ietf.org, int-area > <int-area(a)ietf.org>, int-dir(a)ietf.org, iot-dir(a)ietf.org, its(a)ietf.org, > lp-wan(a)ietf.org, lwip(a)ietf.org > Subject: [Int-area] Liaison statement received from ITU-T regarding a > "Reference Model of IPv6 Addressing Plan for Internet of Things > Deployment" > Date: Mon, 2 Oct 2017 22:53:45 -0400 > > Hi all, > The IETF has received a liaison statement from the ITU-T that their > Study Group SG20 is inviting inputs from the IETF regarding a work > item titled "Reference Model of IPv6 Addressing Plan for Internet of > Things > Deployment” and the deadline for providing inputs is 2018/01/28. The > statement can be found at > > https://datatracker.ietf.org/liaison/1546/ > > I have no further info and I am trying to get access to the referenced > documents. I just want to provide a heads up while that is in process. > > Thanks > Suresh > > > _______________________________________________ > Int-area mailing list > Int-area(a)ietf.org > https://www.ietf.org/mailman/listinfo/int-area

5 5

Reporting the current status of world wide IPv6 deployment and progress to itojun (Fwd)
by S.P.Zeidler 13 Sep '17

13 Sep '17

Dear all, if you have something you want to contribute to a sort-of memorial service for itojun, here's your chance: ----- Forwarded message from Jun Ebihara <jun(a)soum.co.jp> ----- From: Jun Ebihara <jun(a)soum.co.jp> Date: Wed, 13 Sep 2017 08:03:59 +0900 (JST) Subject: Reporting the current status of world wide IPv6 deployment and progress to itojun I make a short presentation about itojun on http://v6reporttoitojun.jp/index.html.en please give me comments about itojun. -- Jun Ebihara ----- End forwarded message ----- regards, spz -- spz(a)serpens.de (S.P.Zeidler)

1 0

IPv6 WG Agenda for RIPE75
by Jen Linkova 11 Sep '17

11 Sep '17

Hello, The agenda for the IPv6 WG session has been finalized and should be published soon. This time we have just one slot: A. Administrative matters [5 min] B. Geoff Huston, "Surviving IPv6 Fragmentation" [35 min] C. Wolfgang Zenker, "Webhosting on IPv6-only virtual machines - operational observations" [15 min] D. Benedikt Stockebrand, Wilhelm Boeddinghaus "IPv6 in Enterprise Network: Advanced Topics" [45 min] E. Lightning Talks [30 mins] F. IPv6 WG Chair Re-Election [10 mins] -- SY, Jen Linkova aka Furry on behalf of IPv6 WG chairs.

1 0

Re: [ipv6-wg] [ipv6-wg-chair] IPv6 prefix delegation BCOP
by Jetten Raymond 05 Sep '17

05 Sep '17

Dear IPv6 Working Group, I strongly believe we have consensus on version 7 of the "IPv6 prefix delegation BCOP" document. There is also consensus on this in the BCOP WG. We will now ask the NCC Comms team kindly to make this an official RIPE document. We apologize for delaying this. On behalf of Jen & Benedikt and ofcourse myself Ray, ************************************************************ Raymond Jetten Phone: +358 3 41024 139 Senior Network Specialist Fax: +358 3 41024 199 Elisa Oyj - IP/MPLS implementation O&M Mobile: +358 45 6700 139 Hermiankatu 3A raymond.jetten(a)elisa.fi FIN-33720, TAMPERE http://www.elisa.fi ************************************************************

2 1

New on RIPE Labs: Dealing with IPv6 Fragmentation in the DNS by Geoff Huston
by Mirjam Kuehne 30 Aug '17

30 Aug '17

Dear colleagues, Please find this new article by Geoff Huston on RIPE Labs: Dealing with IPv6 Fragmentation in the DNS https://labs.ripe.net/Members/gih/dealing-with-ipv6-fragmentation-in-the-dns Kind regards, Mirjam Kuhne RIPE NCC

1 1

Join RIPE NCC Hackathon Version 6, 4-5. November, Copenhagen, Denmark
by Vesna Manojlovic 28 Aug '17

28 Aug '17

Dear colleagues, The sixth RIPE NCC hackathon will take place on Saturday and Sunday, 4-5 November 2017 in Copenhagen, Denmark. The topic is: IPv6! We're looking for creative thinkers: front-end developers, UI designers, network operators, researchers, hackers and other enthusiastic coders, to help us develop new tools that would enable deployment of IPv6 and visualizations based on IPv6 measurements data. All source code developed during the hackathon will be publicly licensed and available on GitHub, and will be free for the entire community to use. -------------------- How to Apply -------------------- Interested? Learn more and apply online today! https://atlas.ripe.net/hackathon/version6/#!application-form *The application deadline is 9.9.* (9th September) We look forward to seeing you there! Find out more in this RIPE Labs article: https://labs.ripe.net/Members/becha/join-the-ripe-ncc-hackathon-version-6 Regards, Vesna Manojlovic Community Builder RIPE NCC

1 1

New on RIPE Labs: Echoes
by Mirjam Kuehne 25 Aug '17

25 Aug '17

Dear colleagues, Read on RIPE Labs how the NAT64 checker helped us to discover a fun network bug on our web front-end: https://labs.ripe.net/Members/stephen_strowes/echoes Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: Introducing NAT64 Checker
by Mirjam Kuehne 22 Aug '17

22 Aug '17

Dear colleagues, Please check out the NAT64 checker developed by Jan Zorz and Sander Steffann. It is now described on RIPE Labs: https://labs.ripe.net/Members/JanZorz/introducing-nat64-checker Kind regards, Mirjam Kuhne RIPE NCC

1 0

Version 6 of IPv6 prefix delegations BCOP is out
by Jan Zorz - Go6 15 Aug '17

15 Aug '17

Dear RIPE IPv6 WG, We received offline some good and valuable comments from MarcoH, addressed them and issued the version 6 of the document draft. https://sinog.si/docs/draft-IPv6pd-BCOP-v6.pdf Please, read and comment, if you think that we need to carry on with editing this document. If not, I would like to see if we can reach a consensus to move forward and ask RIPE staff to do the language check and publish this document as RIPE BCP. Any comments? Suggestions? For v6_pd_BCOP co-authors team, Jan Žorž

4 6

RIPE75 DCTM requirements ( small changes )
by Jetten Raymond 15 Aug '17

15 Aug '17

Hello IPv6 Working group! > ** NOTE FOR SPEAKERS[1] ** > > After Dubai had already been chosen as the location for the upcoming RIPE meeting, the authorities there (DTCM) have started to enforce some rules for conferences and speakers. All speakers (including remote speakers) will need to email the following information to meeting(a)ripe.net<mailto:meeting@ripe.net> before 15 September 2017): > > - Full name, title > - A colour copy of their passport > - A copy of their Emirates ID (if a UAE resident) > - Profile/bio for the speaker (at least 200 characters) > - Mobile number > - Email address > > This information will then be forwarded to the DTCM by the RIPE NCC. > > We realise that these requirements go beyond what was expected at previous meetings and that they may be a cause for concern for some people - especially the sharing of colour copies of passports. Unfortunately there is nothing we can do about this - we have to comply with local laws. If you do not wish to comply with these requirements then you will not be allowed to present on stage. You will still be able to join the discussions from the floor. > > [1] "Speakers" includes anyone who is presenting on stage - presenters, WG Chairs, and community members who are chairing or moderating sessions. This also includes policy proposers who are planning to present their policy. Attendees speaking at the microphones during the Q&A are explicitly not considered as speakers. The RIPE NCC has negotiated with the authorities in Dubai, and has some good news for us. It is now confirmed that a photocopy of speakers' passports is *not* required. Residents of the UAE are still required to upload a copy of their Emirates ID (in jpeg format). The information on https://ripe75.ripe.net/attend/dtcm-requirements/ has been updated. All attendees, and especially speakers, should take a look at that page to avoid surprises. Speakers will be asked to upload the above data via a secure webform provided by the RIPE NCC, who will then pass it on to the DTCM. The data will be permanently deleted from the RIPE NCC infrastructure one week after the RIPE 75 Meeting. Rgds, Ray, IPv6 working group Co-Chair

1 0

Same procedure as every year: Chair (Re-)election
by Benedikt Stockebrand 15 Aug '17

15 Aug '17

Hi IPv6 working group, looks like it's time we did a bit of paperwork... According to the "IPv6 WG Chair Selection Process"[1] it is time for one of us chairs to step down and possibly stand again for re-election. Jen and I fought it out (and what you'd expect, I lost:-) and it was decided that I'll step down---to stand for re-election---effective the next WG meeting in Dubai. With the way things have worked out, I'd be more than happy to serve another term as a WG chair. Cheers, Benedikt [1] https://www.ripe.net/participate/ripe/wg/ipv6/ipv6-wg-chair-selection-proce… -- 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/

3 2

IPv6 Prefix delegation BCOP version 3 is out...
by Jan Zorz - Go6 28 Jul '17

28 Jul '17

Dear RIPE IPv6 WG, After presentation at RIPE74 BCOP TF and IPv6 WG sessions we got some feedback from community over mailing list and while on stage and we addressed those comments as far as we could, resulting in version 3 of the IPv6 prefix delegations draft. To avoid sending around emails with attachment I'm providing the link where you can access the PDF file: https://www.sinog.si/docs/draft-IPv6pd-BCOP-v3.pdf I have a feeling that after all this cycles and comments from the community - we are reaching the point when we'll have to consider calling a consensus if possible, make it a stable RIPE BCOP document and give it a number. Please, read the latest version and see if you can agree with the current text and express your support (if agree) on this mailing list, so chairs can judge if there is enough consensus on the text to maybe go into a WG last call (or maybe even skip that if clear consensus, this is not PDP process ;) ) Cheers and thnx, Jan (on behalf of the co-authors of the document)

11 24

IMPORTANT: RIPE75 is SPECIAL (call for presentations)
by Jen Linkova 24 Jul '17

24 Jul '17

Dear IPv6 Enthusiasts, We are building the agenda for the next meeting, so if you'd like to present at IPv6 WG sessions at RIPE75 or have some ideas/suggestions for the agenda - please contact ipv6-wg-chairs(a)ripe.net. IMPORTANT: There is smth unusual about RIPE75 you should be aware of, especially if you are planning to present. Dubai's Department of Tourism and Commerce Marketing (DCTM) have special requirements for events. The more detailed information could be found below in the text format (and the .docx is attached for your reference), but the short summary is: 1) a final list of all speakers at RIPE 75 must be provided to the DCTM one month before the start of the meeting; 2) all speakers (including remote presenters) need to provide a colour copy of their passport and a short bio (min 2000 chars). What does it means for us? Obviously we need to finalize the agenda much earlier than usual. Also those requirements make it very hard (almost impossible) to add new talks at the very last moment or deal with speakers change. Therefore if you are considering to present but still hesitating it's better to let us (chairs) know and submit a talk tentatively. Sorry about hassle and we hope to see as many amazing talks submitted as usual, despite all those irritating inconvenience! ;) Additional info: ---- Department of Commerce and Tourism Marketing (DTCM) Permit General information The application of a UAE law applies to all events held in Dubai including the RIPE 75 meeting. Following this local law, all speakers and attendees must provide additional personal information to the DTCM in advance of the meeting. While the impact will be minimal for attendees, the requirement to have speakers’ passports and other information weeks ahead of the meeting will require the RIPE Meeting agenda to be finalised much earlier than usual, and with less room for last-minute agenda changes. What are the requirements of the law? 1. All RIPE 75 attendees (including RIPE NCC staff) will need to provide the following information: Full name Country of residence Date of birth Nationality Telephone number (mobile or landline) Email address This information will be collected through our usual registration form and will be passed to the event agency that acts on behalf of the government. The event agency will use attendees’ information to produce barcodes for each attendee. The meeting badge will include the barcode and barcode number. 2. All speakers (including remote speakers) will need to email the following information to meeting(a)ripe.net one month before the start of the meeting. We will forward this information to the DTCM: Full name, title A colour copy of their passport A copy of their Emirates ID (if a UAE resident) Profile/bio for the speaker (at least 200 characters) Mobile number Email According to the law, a speaker will be rejected if any false information is submitted and a new application must be submitted. What does this mean for the WG Chairs and PC? The agendas for all WG sessions should be finalised one month before RIPE 75 begins, so that all presenters have time to submit their information/passports. The WG Chairs will need to make people aware of this deadline in their calls for presentations and when soliciting presentations for the meeting. We suggest that panels be avoided as much as possible, as it might be challenging logistically to ensure that speakers send in their information in time. Another option (“loophole”) would be to have the panel participants contribute as “audience members” from the floor. Who counts as a speaker? Essentially, this includes anyone who is presenting on stage - plenary and WG presenters, panel participants, WG Chairs and PC members and community members who are chairing or moderating sessions. Not included in this definition is attendees who are speaking at the microphones during Q&A sessions. Why does the government require this information? How will the data be handled? The stated reason is to facilitate greater efficiency for event organisers and government entities that are responsible for granting permits. The data is used to conduct analysis, market research and examine industry trends. The data is not shared with other event organisers or ticket resellers/registration companies. We have also been told that the real reason is for security (to avoid anti-government or anti-religious speakers). The information on attendees is also used to get an accurate sense of how many attendees were at the meeting. We do not know how long they will keep the information supplied or how it will be handled. Telephone numbers/email addresses will not be checked. What are the penalties for non-compliance? A fee is paid to the government for each individual case of incorrect data submitted. The attendee is liable for this, not the RIPE NCC. However, the DTCM has said if we show good faith, they will be understanding. Regarding the speakers, the fine is 5-15,000 AUD in the case of non-compliance. The RIPE NCC would be liable for this. Are any people exempted from these requirements? There are some options for a limited number of people to be exempted, but this is intended for high-level government attendees only. -- SY, Jen Linkova aka Furry on behalf of RIPE IPv6 WG Chairs.

11 12

New on RIPE Labs: Local Packet Filtering with IPv6
by Mirjam Kuehne 13 Jul '17

13 Jul '17

Dear colleagues, Please read this new article by Enno Rey on RIPE Labs where he discusses local packet filtering of IPv6, which might depend on the address configuration strategy chosen for your respective systems: https://labs.ripe.net/Members/enno_rey/local-packet-filtering-with-ipv6 Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: Simplifying IPv6 Addressing for Customers - Part 1
by Mirjam Kuehne 11 Jul '17

11 Jul '17

Dear colleagues, One of the main issues when an ISP is planning to deliver IPv6 services is to decide how to address the customers. In this first of two articles Jordi Palet Martinez looks into one of the issues related to IPv6 addressing for customers: the value of “persistence”. https://labs.ripe.net/Members/jordipaletm/simplifying-ipv6-addressing-of-cu… Kind regards, Mirjam Kühne RIPE NCC

2 2

IPv6 operations discussions
by Lee Howard 16 Jun '17

16 Jun '17

The IETF v6ops working group is chartered to improve the operation of IPv6. We have several active documents right now that would benefit from broader operator feedback. For instance, there is current active discussion on: Requirements for IPv6 Routers <https://tools.ietf.org/html/draft-ietf-v6ops-ipv6rtr-reqs> This document provides a list of requirements for operators’ routers. Is it clear and exhaustive? Basic Requirements for IPv6 Customer Edge Routers <https://tools.ietf.org/html/draft-ietf-v6ops-rfc7084-bis> What transition technologies should all CPE vendors put in their devices? The current version proposes all of: 464xlat, DS-Lite, lw4o6, MAP-E, MAP-T, 6in4, and 6rd, as well as IPv4 multicast over IPv6. There are related documents that split out some requirements for further discussion. Happy Eyeballs Version 2: Better Connectivity Using Concurrency <https://tools.ietf.org/html/draft-ietf-v6ops-rfc6555bis> Is this a useful update to the existing Happy Eyeballs specification (rfc6555)? Should we update Happy Eyeballs? Considerations For Using Unique Local Addresses <https://tools.ietf.org/html/draft-ietf-v6ops-ula-usage-considerations> Are ULAs useful, or are they a natural and risky predecessor to IPv6 NAT? It would help future IPv6 operations if current operators would read these documents and comment on them on the mailing list: https://www.ietf.org/mailman/listinfo/v6ops Note Well that comments become part of the IETF record, and thank you for them. Lee v6ops co-chair

1 0

New on RIPE Labs: Finding Open DNS Resolvers on IPv6
by Mirjam Kuehne 16 Jun '17

16 Jun '17

Dear colleagues, Please read this new article by Luuk Hendriks on how to find open DNS resolvers on IPv6: https://labs.ripe.net/Members/luuk_hendriks/finding-open-dns-resolvers-on-i… Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: What Stops IPv6 Traffic in a Dual-stack ISP?
by Mirjam Kuehne 14 Jun '17

14 Jun '17

Dear colleagues, Enric Pujol, network data analyst, is looking at barriers for dual-stack ISPs to carry IPv6 traffic: https://labs.ripe.net/Members/mirjam/what-stops-ipv6-traffic-in-a-dual-stac… Kind regards, Mirjam Kühne RIPE NCC

1 0

plea for increase participation in v6ops/IETF
by JORDI PALET MARTINEZ 13 Jun '17

13 Jun '17

Hello all, At the last LACNIC event, I mentioned on a couple of occasions the need for ISPs in the region, especially small and medium-sized ones, to participate in the decisions taken in the IETF IPv6 Operations Working Group (v6ops). I’m sending this here as well, as I believe the situation also apply to this region. When I asked among the attendees how many participate in v6ops, only one person raised his hand. What does it mean to participate in the mailing list? Follow some emails (sometimes only 1-2 a week, sometimes they can be several in a day), and therefore learn about what is being discussed and give your opinion and, given that decisions are made by Consensus, influence them. What consequences has NOT participating? That decisions against your interests/opinions could be taken, and obviously do not consider your perspective in the standards. Generally large operators are involved, which implies that your interests are not sufficiently represented, and in general are contrary to yours. Your "vote/opinion" is not worth more than yours, but the big one is present and the small/medium NO! I give you a very concrete example. The serious problem that small and medium ISPs have, is to continue offering IPv6 and IPv4 services to their customers, when they already do not have IPv4 addresses. Only the biggest ISPs have a great purchasing power and can influence the manufacturers to do for them what they need. One possibility to solve it, extending the life of IPv4, but not necessarily deploying IPv6, is using CGN, which is also very expensive, and breaks many things. The solution is simple. Deploying IPv6-only services in the last mile, which involves using transition mechanisms, such as 464XLAT that has been deployed on millions of smartphones worldwide, so that applications continue to operate transparently as they "believe" they have IPv4. What is the problem, then? That manufacturers of CPEs are based on an old specification (RFC7084) that does not contemplate these transition mechanisms, so when a small/medium ISP asks a manufacturer for a firmware upgrade or a new CPE, they do not include that solution and perhaps they offer it with an extra cost. In my view, this should change, and that is why I am working on a number of documents, including RFC7084-bis (https://datatracker.ietf.org/doc/draft-ietf-v6ops-rfc7084-bis/), To update this situation, but there is opposition from large ISPs and virtually no small/medium "talks" about it, and in fact these large ISPs deny the situation. In addition, the document also specifies the "automated" support of those cases in which the user installs other routers (which is very common as we all know, and will be more and more in IPv6, IoT, etc.), behind the router installed by the ISP, through homenet (HNCP). I am not asking for your support for my documents, but for understanding the problem and the solution that is being proposed and/or possible new ones, and for the opinion of not only those very few “big ones”, but also of many small and medium, who are most affected. If you want to subscribe to this list, search for "subscribing" at: https://www.ietf.org/mailman/listinfo/v6ops You can see the files of the discussion in: https://mailarchive.ietf.org/arch/search/?email_list=v6ops I remind you that participating in the IETF does not require a presence in the meetings, as consensus is agreed in the list. Regards, Jordi ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

1 0

New on RIPE Labs: 12 Steps to Enable IPv6 in an ISP Network
by Mirjam Kuehne 08 Jun '17

08 Jun '17

Dear colleagues, Please find this new article by Jordi Palet Martinez on RIPE Labs: "12 Steps to Enable IPv6 in an ISP Network" https://labs.ripe.net/Members/jordipaletm/12-steps-to-enable-ipv6-in-an-isp… Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: 6th Anniversary of IPv6 Day and the next RIPE NCC Hackathon
by Mirjam Kuehne 06 Jun '17

06 Jun '17

Dear colleagues, We're celebrating the 6th anniversary of IPv6 Day with two IPv6 related articles on RIPE Labs: 6th Anniversary of the World IPv6 Day: https://labs.ripe.net/Members/nathalie_nathalie/6th-anniversary-of-the-worl… and Save the Date for the RIPE NCC IPv6 Hackathon in October: https://labs.ripe.net/Members/becha/save-the-date-ripe-ncc-hackathon-versio… Kind regards, Mirjam Kuhne RIPE NCC

1 0

New IPv6 Support for Governments Programme
by Mirjam Kuehne 17 May '17

17 May '17

Dear colleagues, Governments planning IPv6 deployments can now access assistance through our new IPv6 Support for Governments Programme. This is part of our ongoing efforts to work more closely with governments and encourage IPv6 adoption throughout our service region. We have explained our approach in more detail in a RIPE Labs article here: https://labs.ripe.net/Members/arne_kiessling/ipv6-support-for-governments-p… We have also documented this on our website here: https://www.ripe.net/manage-ips-and-asns/ipv6/ipv6-for-governments If you represent a government that is planning to make an IPv6 allocation request, please get in touch with us by emailing <IPv6forGov(a)ripe.net>. Kind regards, Mirjam Kuhne RIPE NCC

1 0

IPv6 prefix delegation BCOP document - draft v.2 for review.
by Jan Zorz - Go6 16 May '17

16 May '17

Dear RIPE IPv6 WG, As promised at BCOP TF meeting on Monday, the co-authors present at the RIPE74 meeting gathered on Tuesday afternoon and did some editorial work, addressing majority of the comments and suggestions we got from the community based on first version of the draft. Draft version 2 is now available for reading at https://sinog.si/docs/draft-IPv6pd-BCOP-v2.pdf We'll have a short "lightning talk" in Thursday IPv6 WG session, please go and read the document (those that have enough time and energy), so we get more feedback and input for further improvements (if needed). See you all in couple of hours! For co-authors team, Jan Žorž

7 15

RIPE73 meeting minutes
by Jen Linkova 08 May '17

08 May '17

Hello, I know I should have sent this email long time ago but better late than never... Anyway, the meeting minutes for RIPE73 IPv6 WG sessions could be found at https://www.ripe.net/participate/ripe/wg/ipv6/minutes/minutes-from-the-ipv6… Please review them (especially if you said anything at the mic), and let us know if there are any errors/omissions. Again, sorry for being late with sending this email. I'd also like to thank RIPE NCC for providing the meeting minutes! -- SY, Jen Linkova aka Furry on behalf of IPv6 WG chairs.

1 0

New on RIPE Labs: IPv6 RIPEness Through the Years
by Mirjam Kuehne 13 Apr '17

13 Apr '17

Dear colleagues, In 2010, we introduced IPv6 RIPEness to recognise Local Internet Registries in the RIPE NCC service region that had begun deploying IPv6. Seven years later, we looked at how the IPv6 RIPEness level of the RIPE NCC membership evolved over time. Please find some interesting results on RIPE Labs: https://labs.ripe.net/Members/wilhelm/ipv6-ripeness-through-the-years Kind regards, Mirjam Kuhne RIPE NCC

1 0

IPv6 prefix delegation BCOP document available for comments and suggestions
by Jan Zorz - Go6 13 Apr '17

13 Apr '17

Dear RIPE IPv6 WG, As promised at last RIPE meeting in Madrid, we produced a first draft of "Best Current Operational Practice for operators: IPv6 prefix assignment for end-users - static (stable) or dynamic (non-stable) and what size to choose." The aim of this document is to document the best current operational practice on what size of IPv6 prefix ISPs should assign/delegate to their customers and should they delegate it in a stable, static way or should it change over time. Please find the PDF attached and also accessible at: https://www.sinog.si/docs/draft-IPv6pd-BCOP-v1.pdf We are submitting this document to RIPE IPv6 WG (here) to check the technical validity of the document and also get consensus on it. We are also submitting it to RIPE BCOP TF to check if this is a real best operational practice and get consensus on it there. Please, read the document and send back comments to this mailing list. All feedback is more than welcome. On behalf of co-authors, Jan Žorž P.S: This document is not intended to document what practices may be in future and what they might look like, but to reflect the best methods of implementing IPv6 at the time of publication. Updates to this document will be published to reflect changes in best current practices where there are developments in standards and implementations.

13 30