- ipv6-wg - mailman.ripe.net

SD-WAN and Dual stack
by christian bretterhofer 31 Aug '18

31 Aug '18

Hello to all, We as enterprise (https://www.andritz.com) have deployed multiple DMZ ( DNS, some websites, soon VPN solutions ) in Dualstack, We converted most of our MPLS lines that they transport Dualstack Our first internal Datacenter is also Dualstack and IPV6 only capable. But now we need to extend some WLAN links and want to utilize SD-WAN offerings. But it seems that there are few solutions that support Dualstack. Cisco IWAN, Citrix Cloud bridge, Riverbed seems to support Dualstack partly What about others? CloudGenix Silverpeak ... Any hints? Some older blog posts i found: https://community.infoblox.com/t5/IPv6-CoE-Blog/Could-SD-WAN-Change-IPv6-Ad… https://community.infoblox.com/t5/IPv6-CoE-Blog/Making-a-New-Product-Make-i… -- --- best regards Christian Bretterhofer Andritz AG

2 1

Compilation of Comments on Y.IPv6RefModel Sent to ITU-T SG20
by Marco Hogewoning 04 Jul '18

04 Jul '18

Dear colleagues, In our role as secretariat to the RIPE community, we committed ourselves to compiling an overview of your evaluation of draft Recommendation Y.IPv6RefModel and sharing this with ITU Study Group 20. In consultation with the Chairs of this working group, we have now produced and submitted this document to the ITU, and this will serve as input to the next meeting of Study Group 20 from 3-13 December 2018 in Wuxi, China. We have also made the document available on our website: https://www-static.ripe.net/docs/2018/20180703-RIPE-Response-ITU-IPv6.pdf The document includes links to the working group discussions and excerpts taken from the email comments and meeting minutes. The RIPE NCC has also strongly encouraged Study Group 20 participants to review all of the feedback received via the working group. As a Sector Member of ITU-T, the RIPE NCC will attend the meeting in China to give further input, based on the community's feedback and comments received during this review process. We would like to thank the Chairs of this working group and all community members who took the time to submit comments. We will keep the RIPE community informed as this process continues within ITU Study Group 20. Regards, Marco Hogewoning Senior External Relations Officer RIPE NCC

1 0

New on RIPE Labs: A Large-scale lw4o6 Deployment for Broadband Users in Greece
by Mirjam Kuehne 04 Jul '18

04 Jul '18

Dear colleagues, Please read this interesting new article by Kostas Zorbadelos in which he describes a large-scale Lightweight 4over6 deployment for broadband users in Greece: https://labs.ripe.net/Members/kzorba/a-large-scale-lw4o6-deployment-for-bro… Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: Lightweight 4over6: One-step Further Than Dual-stack Networks
by Mirjam Kuehne 28 Jun '18

28 Jun '18

Dear colleagues, Please read this new RIPE Labs article by Diego Pino Garcia, one of the RACI fellows from RIPE 76. Diego describes lw4o6 (RFC 7596) and introduces Snabb, a toolkit that eases the development of high-performance network functions: https://labs.ripe.net/Members/diego_pino_garcia/lw4o6-one-step-further-than… Kind regards, Mirjm Kühne RIPE NCC

1 0

New on RIPE Labs: Spam Over IPv6 - Eight Years Later
by Mirjam Kuehne 18 Jun '18

18 Jun '18

Dear colleagues, A long time ago we published an article on the amount of spam we receive over IPv6. Now, eight years later, we were curious to see if the spam landscape has changed: https://labs.ripe.net/Members/ivodijkhuis/spam-over-ipv6-8-years-later Kind regards, Mirjam Kühne RIPE NCC

1 0

Invitation to supply feedback on ITU draft Recommendation on IPv6 address planning for IoT
by Jetten Raymond 15 Jun '18

15 Jun '18

Dear colleagues, RIPE 76 is coming closer and as you may have seen on the agenda, the date of the IPv6 WG has changed from Wednesday to Thursday. The reason for the date change you can read below and in the subject. If you want to present or have a topic that would be of great interest to the IPv6wg, send your presentation or explain the contents to ipv6-wg-chairs(a)ripe.net<mailto:ipv6-wg-chairs@ripe.net> and mention also how much time you would need. The session which will be on Thursday 17 may 2018, in Palais du Pharo, Marseille, France. Now back to the subject: During RIPE 74, Marco Hogewoning of the RIPE NCC, presented about ongoing work in ITU Study Group 20, which includes development of a Recommendation on an IPv6 address plan for IoT networks. In his presentation he also mentioned a Liaison Statement send by the ITU asking the RIPE NCC for feedback, to which they suggested that this work would be done in a more appropriate venue such as the RIPE community or at least that such a document would be developed in close coordination with the operational community. We, the chairs, have been following this discussion and after talking to RIPE NCC and some community members, we have understood that there has not been any operational feedback on this particular draft and ITU is still seeking input, for instance also by sending a Liaison Statement to IETF. In response to all this, we have decided to invite a representative of ITU, to join us in Marseille for RIPE 76 and present this work to us, for the purpose of collecting and incorporating feedback from IPv6 experts and network operators on their draft recommendation. We are happy to announce that ITU Study Group 20 has responded positively to our offer and have decided to share the current working draft with us, for the purpose of review and for RIPE community to provide feedback. As it is quite big, the text of this draft Recommendation Y.IPv6RefModel "Reference model of IPv6 subnet addressing plan for Internet of things deployment" has been made available on the IPv6 WG pages: https://www.ripe.net/participate/ripe/wg/ipv6/documents/itu-ipv6refmodel We kindly invite you to provide feedback and comments on the contents of this document via this mailing list or of course the RIPE Forum web interface. The RIPE NCC has agreed to ensure that the comments will be collected and made available to the ITU via response to the Liaison Statement below. We of course also hope to discuss the feedback with the editor of the document during our second session at RIPE 76. Regards, Benedikt, Jen, Raymond Liaison Statement we received from ITU Study Group 20 in response to our invite: > ITU-T Study Group 20 Q3/20 thanks the RIPE NCC for their contribution that contained the invitation from the RIPE IPv6 Working Group. We thank the RIPE IPv6 Working Group for the invitation to present Draft Recommendation ITU-T Y.IPv6RefModel at the May 2018 RIPE meeting for the purpose of obtaining operational feedback and input. We are delighted to recognize the invitation from RIPE and confirm it is the intention of the editor of the Draft Recommendation ITU-T Y.IPv6RefModel to participate in the RIPE meeting in May 2018. > > Attached is a copy of the draft Recommendation. We look forward to the feedback and comments from the RIPE community. For Internal Use Only

8 8

New on RIPE Labs: IPv6 Adoption Statistics: How do APNIC and Facebook Compare?
by Mirjam Kuehne 13 Jun '18

13 Jun '18

Dear colleagues, Both APNIC and Facebook publish statistics on IPv6 adoption per country. Next to the visualisations, these organisations also provide the numerical data. We take a look at these to see how the two methodologies compare. Please read on RIPE Labs: IPv6 Adoption Statistics: How do APNIC and Facebook Compare? https://labs.ripe.net/Members/wilhelm/ipv6-adoption-statistics-how-do-apnic… Kind regards, Mirjam Kühne RIPE NCC

1 0

Experiences with IPv6-only MX as primary?
by Shane Kerr 11 Jun '18

11 Jun '18

Hello, I set up a mail server zone to have an IPv6-only primary and a dual-protocol secondary, like this: ; SMTP chooses lower-priority first, so smtp-primary is preferred example.com. 300 MX 10 smtp-primary.example.com. example.com. 300 MX 100 smtp-secondary.example.com. ; smtp-primary is IPv6-only smtp-primary.example.com. 300 AAAA 2001:DB8::1 ; smtp-secondary has both IPv6 and IPv4 addresses smtp-secondary.example.com. 300 AAAA 2001:DB8::2 smtp-secondary.example.com. 300 A 192.0.2.11 Mail delivery via IPv6 works fine (as you would expect), and mail delivery from some IPv4-only servers also works fine (as I think the standards dictate). My concern is that some mail servers may choke on this setup. For example, http://mailtester.com complains "Network is unreachable". Of course, I also worry about all the spammers who may not be able to deliver because of incomplete mail implementations on the trojans and other viruses infecting their zombie hosts. 😉 Does anyone have any experience with a similar setup? Have there been problems? Cheers, -- Shane

2 1

Celebrating the Anniversary of World IPv6 Launch on RIPE Labs
by Mirjam Kuehne 07 Jun '18

07 Jun '18

Dear colleagues, We've been celebrating the sixth anniversary of the World IPv6 Launch with an RIPE NCC::Educa IPv6 Day event and a series of IPv6-related articles on RIPE Labs. Blockers to IPv6 and How to Overcome Them: https://labs.ripe.net/Members/david_holder/blockers-to-ipv6-adoption Celebrating IPv6 Launchiversary: A View from RIPE Atlas and K-root: https://labs.ripe.net/Members/stephen_strowes/ipv6-launchiversary-a-review-… So Long and Thanks for All the IPv6 (an article on the dissolution of the Dutch IPv6 Task Force): https://labs.ripe.net/Members/marco_hogewoning/so-long-and-thanks-for-all-t… RIPE NCC::Educa IPv6 Day (and the RIPE NCC's perspective on IPv6 deployment): https://labs.ripe.net/Members/ulka_athale_1/ripe-ncc-educa-ipv6-day Happy reading :-) Kind regards, Mirjam Kühne RIPE NCC

1 0

Y.IPv6RefModel is out of scope for the ITU
by Nick Hilliard 31 May '18

31 May '18

JORDI PALET MARTINEZ via ipv6-wg wrote on 26/05/2018 12:16: > I already said this before, but "... in running such networks vis > [via] the RIR policy making fora." is wrong. Stepping back a bit, what we're discussing here is not whether address assignment / allocation models should be dealt with by the RIRs or the IETF, but whether they are in scope for the ITU. The answer to this is that all aspects of IP number resource management are resoundingly out of scope for the ITU. This includes all IP number resource assignment and allocation issues, all addressing models, and by direct implication, the SG20 work on the Y.IPv6RefModel work item. There needs to be a crystal clear statement from the RIR community that this entire exercise is wildly out of scope for the ITU, that SG20 needs to cease and desist from reaching into areas outside their competence, and that the Y.IPv6RefModel work item needs to end, immediately and permanently. Nick

6 7