- ipv6-wg - mailman.ripe.net

Re: [ipv6-wg] RIPE 80 IPv6 wg session Wilhelms DSL broke, some unanswered questions
by JORDI PALET MARTINEZ 14 May '20

14 May '20

My view on the 2nd one: I think SLAAC is sufficient! I guess unless Android change their mind and develops/enables DHCPv6, this will not be useful. Regards, Jordi @jordipalet El 14/5/20 13:59, "ipv6-wg en nombre de Jetten Raymond" <ipv6-wg-bounces(a)ripe.net en nombre de raymond.jetten(a)elisa.fi> escribió: Hello All, Thank you all for watching the IPv6 WG virtually, at the latest minutes of Wilhelms presentation Q&A his dsl connection unfortunately went down, there were still some questions in the buffer, could you Wilhelm comment yet on these ? Any tips to get app developers on board to develop IPv6 enabled apps? It’s not uncommon for companies to exclude IPv6 from minimum viable product as its “too hard” Could disabling SLAAC and better DHCPv6 support (eg in mobile devices) help the deployment? It would help with some migrations from IPv4 to IPv6 I think. (Mark Scholten / asking for myself) Rgds, Ray For Internal Use Only ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com 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

RIPE80 IPv6 WG Session
by Jen Linkova 08 May '20

08 May '20

Dear IPv6 Enthusiasts, The agenda for IPv6 WG at RIPE80 has been published: https://ripe80.ripe.net/programme/meeting-plan/ipv6-wg/ The instructions on how to attend the RIPE80 sessions could be found at https://ripe80.ripe.net/attend/how-to-participate/ See you there! -- SY, Jen Linkova aka Furry on behalf of IPv6 WG Chairs.

1 0

RIPE80 Call for Presentations
by Jen Linkova 01 May '20

01 May '20

Dear IPv6 Enthusiasts, As you might have noticed, RIPE80 is going to be a virtual meeting. So IPv6 WG is going to meet on Thu, May 14th, 13:00 - 13:45 CEST (Don't forget to convert to your local timezone). We are looking for talks. COVID-19 does not seem to be a reason good enough to slow down IPv6 deployments. I suspect it might be a reason for accelerate them, actually. So stories about 'IPv6 in the Time of Cholera' (or any other talks about IPv6) are appreciated. Please send your suggestions (the title, short summary, how much time you need) to ipv6-wg-chair(a)ripe.net. Thanks, -- SY, Jen Linkova aka Furry on behalf of IPv6 WG Chairs.

9 11

Fwd: [v6ops] WG Last Call on draft-ietf-v6ops-cpe-slaac-renum
by Fernando Gont 04 Apr '20

04 Apr '20

Hello, folks, v6ops is WGLC'ing one of the documents (https://tools.ietf.org/html/draft-ietf-v6ops-cpe-slaac-renum-01) we have authored to improve the reaction of SLAAC to renumbering events. This document contains recommendations for Customer Edge Routers. For background, you may want to consult: https://tools.ietf.org/html/draft-ietf-v6ops-slaac-renum-01 If you have any comments/feedback, please do let us know. If possible, on the v6ops list (https://www.ietf.org/mailman/listinfo/v6ops) Thanks! Cheers, Fernando -------- Forwarded Message -------- Subject: [v6ops] WG Last Call on draft-ietf-v6ops-cpe-slaac-renum Date: Mon, 30 Mar 2020 15:47:14 +0000 From: Ron Bonica <rbonica=40juniper.net(a)dmarc.ietf.org> To: v6ops(a)ietf.org <v6ops(a)ietf.org> Folks, This message initiates a WG Last Call on draft-ietf-v6ops-cpe-slaac-renum. Please submit comments by April 13, 2020. Fred and Ron Juniper Business Use Only -- Fernando Gont e-mail: fernando(a)gont.com.ar || fgont(a)si6networks.com PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1 -- Fernando Gont SI6 Networks e-mail: fgont(a)si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

3 3

New on RIPE Labs: What’s the Deal with IPv6 Link-Local Addresses?
by Philip Homburg 11 Mar '20

11 Mar '20

Dear colleagues, Stephen Strowes, Emile Aben and I published a new article on RIPE Labs on how link-local addresses in IPv6, and specifically the '%eth0'-part of link-local addresses, can have an impact on RIPE Atlas measurements. https://labs.ripe.net/Members/philip_homburg/whats-the-deal-with-ipv6-link-… We think this will be an interesting read for network operators and others who are using RIPE Atlas measurement data or are interested in IPv6. Kind regards, Philip Homburg RIPE NCC

2 1

Can ripemtg SSID promotes NAT64 (at least) during RIPE80 ? :)
by Willy Manga 28 Feb '20

28 Feb '20

Hello, I was looking the trends of the last FOSDEM [1] and I recalled discussions before and during RIPE79. I humbly think you could give a try ... 1. https://blogs.cisco.com/getyourbuildon/fosdem-2020-trends-and-analysis -- Willy Manga @ongolaboy https://ongola.blogspot.com/

5 4

IPv6 WG Minutes - RIPE 79
by Jetten Raymond 16 Dec '19

16 Dec '19

Hello all, Please find attached the draft minutes from the IPv6 WG session at RIPE 79. Do let us know if you want any changes made to the minutes. If we haven't heard from you by 20 December, we'll assume all is in order and publish the minutes to the website as they are. Rgds, Ray, Jen, Benedikt For Internal Use Only

1 0

New on RIPE Labs: How to Build and Market IPv6-only Services
by Mirjam Kuehne 04 Dec '19

04 Dec '19

Dear colleagues, For those of you who missed Nico Schotteluis' presentation at RIPE 79, here is his story on how they built and marketed IPv6-only services (including cute penguin drawings :-)): https://labs.ripe.net/Members/nico_schottelius/how-to-build-and-market-ipv6… Kind regards, Mirjam Kühne RIPE NCC

1 0

Its that time of the year...
by Yannis Nikolopoulos 02 Dec '19

02 Dec '19

...when we're starting to deploy yet another IPv6-only technology :) Hello all, as a fairly large ISP (for Greek standards at least), we've been affected by IPv4 exhaustion for quite some time now. A few years back we gave LW4o6 a go, as documented here https://ripe76.ripe.net/presentations/11-lw4o6-deployment-as6799.pdf . In the end, it did not work out very well. Quoting myself (from v6ops mailing list), the reasons behind that were: "In no particular order: 1. CPE (almost OK after ~2 years and god knows how many iterations) 2. lwaftr performance (worth noting the the lwaftr is implemented as a VNF 3. vendor's reluctance to continue (much needed) dev/ment because of *lack of interest from other ISPs* " Please take extra note of (3). In any case, being the optimists we are, and having supportive mgmt, we decided (once more) against burying ourselves deeper into CGN. This time we're going with MAP-E (which incidentally was our first choice), mainly because we understand it and our MAP BR vendor does too :) . So, as I already mentioned, we're just about to deploy it commercially. We've tested with 2 CPE vendors sucessfully and we're just ironing out some provisioning details before launching. Deployment will be gradual of course and very very cautious. Unofficially, we are aware of a couple of similar trials from other ISPs and we'd love to hear about people who have already deployed such technologies (IPv6-only with IPv4aas) or are thinking about doing so. After all, that is exactly what this WG is about :) thanks for reading, Yannis

3 3

Re: [ipv6-wg] Its that time of the year...
by Jan Zorz - Go6 02 Dec '19

02 Dec '19

On 01/12/2019 20:57, Ole Troan wrote: >> No matter how hard you try, at the end of the day LW4o6 is still >> stateful mechanism. > > Just make sure there are no misunderstandings. MAP-E and LW46 both > have the same NAT placement (at the CPE). A MAP-E implementation can > implement LW46 by supporting a MAP rule per subscriber. So it’s more > correct to say that LW46 has per-user configured state, and that > MAP-E can aggregate this configured state into a few rules covering > the whole domain. Both are stateless, in contrast to a NAT that has > state per session. Ya, you are right. Got confused for a millisecond with dslight ;) Too many things going on right now. My bad. As far as I remember - LW4o6 is useful in cases where you don't have one huge IPv4 block of addresses to assign to the transition mechanism and/or where you want to dynamically assign additional ports to the CPE if it runs out of it. If none of this is a requirement, then MAP-E/T should be the way to go. Do we have any experiments/deployments of 464XLAT in fixed networks? CLAT in CPE and NAT64 in the core? Cheers, Jan

1 0