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@ripe.net. Thanks, -- SY, Jen Linkova aka Furry on behalf of IPv6 WG Chairs.
Jen Linkova <furry13@gmail.com> writes: Hi,
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@ripe.net.
Not a suggestion but something I like to see especially as right now several people pointing out that github has no IPv6. I would like to see a presentation explaining what is so hard about deploying IPv6 and what the technical difficulties are. If I remember correctly in her talk at RIPE79 Veronika asked the audience who has deployed IPv6 an only 1/4 (or 1/3) raised their hands. Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
On 24. Apr 2020, at 13:38, Jens Link <lists@quux.de> wrote:
I would like to see a presentation explaining what is so hard about deploying IPv6 and what the technical difficulties are. If I remember correctly in her talk at RIPE79 Veronika asked the audience who has deployed IPv6 an only 1/4 (or 1/3) raised their hands.
I think in the off-record discussion after her talk Veronika was also asked about the sad status of Github with regard to IPv6 and she promised to address this to the appropriate folks within Microsoft. Perhaps we should follow up on this with her … and as an additional incentive: competitor GitLAB finally seems to have added IPv6 support recently :-) -Andi
Andreas Härpfer <ah@v6x.org> writes: Hi,
I think in the off-record discussion after her talk Veronika was also asked about the sad status of Github with regard to IPv6 and she promised to address this to the appropriate folks within Microsoft.
it's a long an sad story. Many people have asked. Every time I asked the answer was something like "it's on our road map but can't tell you a date'. At the last RIPE meeting in Amsterdam I was told that they are done and just needed to add AAAA record to DNS. That was in October in 2018. Looking at it today: It might have been to ger rid of me and to stop asking.
Perhaps we should follow up on this with her … and as an additional incentive: competitor GitLAB finally seems to have added IPv6 support recently :-)
I think they will only notice when enough *large* projects moved from github to gitlab. Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
Hi, "in the off-record discussion after" What happened to the "off" bit...? :-) Carlos On Fri, 24 Apr 2020, Andreas Härpfer wrote:
On 24. Apr 2020, at 13:38, Jens Link <lists@quux.de> wrote:
I would like to see a presentation explaining what is so hard about deploying IPv6 and what the technical difficulties are. If I remember correctly in her talk at RIPE79 Veronika asked the audience who has deployed IPv6 an only 1/4 (or 1/3) raised their hands.
I think in the off-record discussion after her talk Veronika was also asked about the sad status of Github with regard to IPv6 and she promised to address this to the appropriate folks within Microsoft.
Perhaps we should follow up on this with her ? and as an additional incentive: competitor GitLAB finally seems to have added IPv6 support recently :-)
-Andi
On 24 Apr 2020, at 13:23, Andreas Härpfer <ah@v6x.org> wrote:
On 24. Apr 2020, at 13:38, Jens Link <lists@quux.de> wrote:
I would like to see a presentation explaining what is so hard about deploying IPv6 and what the technical difficulties are. If I remember correctly in her talk at RIPE79 Veronika asked the audience who has deployed IPv6 an only 1/4 (or 1/3) raised their hands.
I think in the off-record discussion after her talk Veronika was also asked about the sad status of Github with regard to IPv6 and she promised to address this to the appropriate folks within Microsoft.
Perhaps we should follow up on this with her … and as an additional incentive: competitor GitLAB finally seems to have added IPv6 support recently :-)
Veronika is no longer with MS, but still strong advocate of IPv6 :) Tim
On Fri, Apr 24, 2020 at 9:37 PM Jens Link <lists@quux.de> wrote:
I would like to see a presentation explaining what is so hard about deploying IPv6 and what the technical difficulties are.
Any volunteers? :)
If I remember correctly in her talk at RIPE79 Veronika asked the audience who has deployed IPv6 an only 1/4 (or 1/3) raised their hands.
I'd not assume that IPv6 is not getting deployed (only) because it's hard or because of the technical difficulties. Maybe you are more lucky but I personally have a lot of things on my 'would be nice to get done' list - and none of them are hard to do. It's just they keep getting postponed because if other things which are either more urgent or more important. I'd not be surprised if IPv6 deployments suffer from the same issue quite often. -- SY, Jen Linkova aka Furry
On 1 May 2020, at 04:44, Jen Linkova <furry13@gmail.com> wrote:
I'd not assume that IPv6 is not getting deployed (only) because it's hard or because of the technical difficulties. Maybe you are more lucky but I personally have a lot of things on my 'would be nice to get done' list - and none of them are hard to do. It's just they keep getting postponed because if other things which are either more urgent or more important. I'd not be surprised if IPv6 deployments suffer from the same issue quite often.
I think this is spot on; IPv6 never makes it to the top of the list for most organisations. The difference is when something critical comes along that changes that. Tim
It's just they keep getting postponed because if other things which are either more urgent or more important. I'd not be surprised if IPv6 deployments suffer from the same issue quite often.
I think this is spot on; IPv6 never makes it to the top of the list for most organisations.
The difference is when something critical comes along that changes that.
I agree, I see this often. But to keep spirits high, I must say that I also see customers that work on it consistently and with a realistic long term perspective with no emergency pressure and even keep going in these crazy Corona times. I guess our impression of what is going on and what not is also very often limited, because unless we're involved, we don't know much about such initiatives. There is hope. Silvia -----Ursprüngliche Nachricht----- Von: ipv6-wg <ipv6-wg-bounces@ripe.net> Im Auftrag von Tim Chown Gesendet: Freitag, 1. Mai 2020 11:04 An: Jen Linkova <furry13@gmail.com> Cc: Jens Link <lists@quux.de>; ipv6-wg@ripe.net IPv6 <ipv6-wg@ripe.net> Betreff: Re: [ipv6-wg] RIPE80 Call for Presentations
On 1 May 2020, at 04:44, Jen Linkova <furry13@gmail.com> wrote:
I'd not assume that IPv6 is not getting deployed (only) because it's hard or because of the technical difficulties. Maybe you are more lucky but I personally have a lot of things on my 'would be nice to get done' list - and none of them are hard to do. It's just they keep getting postponed because if other things which are either more urgent or more important. I'd not be surprised if IPv6 deployments suffer from the same issue quite often.
I think this is spot on; IPv6 never makes it to the top of the list for most organisations. The difference is when something critical comes along that changes that. Tim
On Fri, May 1, 2020 at 7:06 PM Tim Chown <Tim.Chown@jisc.ac.uk> wrote:
On 1 May 2020, at 04:44, Jen Linkova <furry13@gmail.com> wrote:
I'd not assume that IPv6 is not getting deployed (only) because it's hard or because of the technical difficulties. Maybe you are more lucky but I personally have a lot of things on my 'would be nice to get done' list - and none of them are hard to do. It's just they keep getting postponed because if other things which are either more urgent or more important. I'd not be surprised if IPv6 deployments suffer from the same issue quite often.
I think this is spot on; IPv6 never makes it to the top of the list for most organisations.
From my previous life, almost 6/7years ago the decision to either go with IPv6 (network was ready and we did the POC as well) or buy more IPv4 blocks was made on the basis of a 2/3sec pause from the engineering head in response to a BU head questioning "are you confident that IPv6 is not going to create any problems?" 2 days later I was talking to brokers. Fast forward, I would be interested if someone who can do myth busting for c-suite would be great. A Panel may be?
Best Wishes, Aftab Siddiqui
On Fri, May 01, 2020 at 09:03:59AM +0000, Tim Chown wrote:
On 1 May 2020, at 04:44, Jen Linkova <furry13@gmail.com> wrote: I'd not assume that IPv6 is not getting deployed (only) because it's hard or because of the technical difficulties. Maybe you are more lucky but I personally have a lot of things on my 'would be nice to get done' list - and none of them are hard to do. It's just they keep getting postponed because if other things which are either more urgent or more important. I'd not be surprised if IPv6 deployments suffer from the same issue quite often.
I think this is spot on; IPv6 never makes it to the top of the list for most organisations.
The difference is when something critical comes along that changes that.
I think that "something critical" has just come along with drastically changed usage patterns for private internet access as many people now are working from home. Interactive work probably puts a lot more stress on CGN gateways than streaming videos, even if the amount of traffic is much lower. If someone who runs CGN gateways could do a presentation on that then I would like to see it. Maybe we could also discuss recommendations for a way forward. Some things that come to mind: - access providers that already operate dual stack networks but by default only provide IPv4 to customers could move their default to dual stack - access providers that already operate dual stack networks but only for private users (usually with DSLite or similar) and hand IPv4 only to their business customers could offer dual stack for the latter - website operators who are on dual stack systems should make sure that they publish AAAA records in DNS. I see this on our network: while almost all newer websites are on IPv6-only VMs (we charge extra for IPv4), many of the customers on the older dual stack systems don't bother to publish AAAA records. - networks that still offer legacy-IP only should consider to join the Internet :-) Greetings, Wolfgang
Tim Chown wrote on 01/05/2020 10:03:
I think this is spot on; IPv6 never makes it to the top of the list for most organisations.
The difference is when something critical comes along that changes that.
this is another way of saying: humans are often a crisis-driven species. Nick
participants (9)
-
Aftab Siddiqui -
Andreas Härpfer -
Carlos Friaças -
Jen Linkova -
Jens Link -
Nick Hilliard -
Silvia Hagen -
Tim Chown -
Wolfgang Zenker