- ipv6-wg - mailman.ripe.net

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