Join us for the RIPE NCC Educa::IPv6-only
Dear IPv6 working group, You are invited to join us for a deep-dive into an IPv6-only world! We’re hosting the fourth edition of a RIPE NCC::Educa - a one day online event, bringing together experts from around the world to take a deeper look at topics of interest. Registration is free. To mark the anniversary of World IPv6 Launch Day, we’re hosting the RIPE NCC::Educa IPv6-only on Monday, 8 June from 10:00 UTC+2 onwards. Expert presenters will talk about what it means to run IPv6-only data centres, ISPs and enterprises, among other topics. You can view the agenda at: https://www.ripe.net/support/training/ripe-ncc-educa/ripe-ncc-educa-ipv6-202... Register at: https://www.eventbrite.nl/e/ripe-ncceduca-ipv6-only-tickets-106761053184 We hope to see you online soon! Best regards, Ondřej Caletka RIPE NCC
Ondřej Caletka <Ondrej.Caletka@ripe.net> writes: Hi,
Register at: https://www.eventbrite.nl/e/ripe-ncceduca-ipv6-only-tickets-106761053184
$ dig AAAA www.eventbrite.nl +short $ "IPv6-only" Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
Hi, On Thu, May 28, 2020 at 02:24:47PM +0200, Jens Link wrote:
Register at: https://www.eventbrite.nl/e/ripe-ncceduca-ipv6-only-tickets-106761053184
$ dig AAAA www.eventbrite.nl +short $
"IPv6-only"
You spelled IPv4+ funny! Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
$ dig AAAA www.eventbrite.nl +short
You spelled IPv4+ funny!
I lost track of the discussion. Where does IPv4+ store the extra bit in DNS? Is there a new record type, or is it cleverly hidden in A records? In any case, for legacy IPv6 networks, just make sure that you have DNS64 and connecting to the internet will work just fine :-)
Hi, On Thu, May 28, 2020 at 03:17:26PM +0200, Philip Homburg wrote:
$ dig AAAA www.eventbrite.nl +short
You spelled IPv4+ funny!
I lost track of the discussion. Where does IPv4+ store the extra bit in DNS? Is there a new record type, or is it cleverly hidden in A records?
In any case, for legacy IPv6 networks, just make sure that you have DNS64 and connecting to the internet will work just fine :-)
The point was that the NCC is marketing an "IPv6 only" event, using a service provider who is not reachable from an IPv6 only client network. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
The point was that the NCC is marketing an "IPv6 only" event, using a service provider who is not reachable from an IPv6 only client network.
I agree. It is sad to see how little IPv6 support there is by content and services on the internet.
I personally think for each IPv4 only service we should create an IPv6 only service and use that for ripe/ieee/network related events. Everyone in our community should be able to get IPv6 anywhere, anytime. Cheers, Nico p.s.: Yes, I would always volunteer for providing that. Philip Homburg <pch-ripeml@u-1.phicoh.com> writes:
The point was that the NCC is marketing an "IPv6 only" event, using a service provider who is not reachable from an IPv6 only client network.
I agree. It is sad to see how little IPv6 support there is by content and services on the internet.
-- Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
Nico Schottelius <nico.schottelius@ungleich.ch> writes:
I personally think for each IPv4 only service we should create an IPv6 only service and use that for ripe/ieee/network related events.
I once removed the A record to a wiki I run for several nerds. I won't do that again. So much crying. And you can try for yourself: Put a link on twitter to an IPv6 only resource and see how many people are complaining.
Everyone in our community should be able to get IPv6 anywhere, anytime.
*should* Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
Jens Link <lists@quux.de> writes:
Nico Schottelius <nico.schottelius@ungleich.ch> writes:
I personally think for each IPv4 only service we should create an IPv6 only service and use that for ripe/ieee/network related events.
I once removed the A record to a wiki I run for several nerds. I won't do that again. So much crying. And you can try for yourself: Put a link on twitter to an IPv6 only resource and see how many people are complaining.
You are a person of your word and I take the liberty to share the experiment on here: https://twitter.com/QuuxBerlin/status/1266021157469290501 (so far did not see anyone complaining)
Everyone in our community should be able to get IPv6 anywhere, anytime.
*should*
I really don't think there is an excuse. HE.net work w/ static IPs, IPv6VPN.ch that we provide works with any kind of nat and I'd be open to make the latter a public service, if it was backed by more than just ungleich. In a nutshell, everyone can get IPv6 anywhere. So from my point of view it's only a matter of motivation and for us - in the network community - I'd assume that everybody is motivated to get connected via IPv6. Best regards, Nico -- Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
Nico Schottelius wrote on 28/05/2020 16:50:
In a nutshell, everyone can get IPv6 anywhere.
Some people would value reliable ipv4-only services as being more useful than ipv6 delivered over tunnelling hacks from third parties. But, most people don't care, in the same way that we don't care about e.g. the building materials used in our roads. Just that they work and that we can get on and do what we need to do. FWIW, I haven't had native ipv6 on my desktop for ~6 years because the service providers I use can't / won't provision it on the services I use. No, this doesn't bother me. Yes, I have v6 access via other means if I really need it. re: using Eventbrite, if it bothers people that the booking system isn't available over ipv6, then don't use it. Just bear in mind that the overall objective of wider ipv6 deployment may not be well served if you make that choice. Don't sacrifice the war to win a battle. Nick
Nick Hilliard <nick@foobar.org> writes:
re: using Eventbrite, if it bothers people that the booking system isn't available over ipv6, then don't use it.
Maybe it would be a better idea when choosing a tool / platform to check if IPv6 is supported and too prefer those tool / platform. And tell people why the other tool wasn't chosen. Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
Jens Link wrote on 28/05/2020 17:53:
Maybe it would be a better idea when choosing a tool / platform to check if IPv6 is supported and too prefer those tool / platform. And tell people why the other tool wasn't chosen.
Or not. You don't need to win all battles to win the war - just the important ones. This isn't one of them. Nick
Hi, On Thu, May 28, 2020 at 06:24:33PM +0100, Nick Hilliard wrote:
Jens Link wrote on 28/05/2020 17:53:
Maybe it would be a better idea when choosing a tool / platform to check if IPv6 is supported and too prefer those tool / platform. And tell people why the other tool wasn't chosen.
Or not. You don't need to win all battles to win the war - just the important ones. This isn't one of them.
So which battles do *you* find important to push IPv6 deployment on the content sidew? Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
Gert Doering wrote on 28/05/2020 18:35:
So which battles do *you* find important to push IPv6 deployment on the content sidew?
having the meetings, for starters. Then deploying ipv6 + making it available in a way that people don't even notice it's there. Nick
Nick Hilliard <nick@foobar.org> writes:
having the meetings, for starters.
Sure. Let's talk more about deploying IPv6. Did work very well for the last decade / years. Personally I think that one thing that might work better is to avoid IPv4 only services when there is an alliterative service with IPv6 enabled. One only has some little extra work, like installing a browser plugin and watching the output. So do not complain that $ISP has no IPv6 choose an alliterative if you can. If the git web service you are using does not complain and open tickets, choose an alternative. If your CDN does not fully support IPv6 do not complain and choose an alternative. .... Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
On 5/29/20 10:38 AM, Jens Link wrote:
Nick Hilliard <nick@foobar.org> writes:
having the meetings, for starters. Sure. Let's talk more about deploying IPv6. Did work very well for the last decade / years.
oh, but it has. Talking about issues, creating traction, usually helps. Just check the google stats for the percentage of users accessing google via IPv6: Sep 2008: 0.04%, May 2020: 30% . Then check the stats for Greece. Greece is at almost 50% and I can tell you why: We (main ISPs+Academia) created a task force and started presenting and educating (other SPs, Enterprises etc). I bet that countries with similar percentages followed a similar path. What you're proposing is the end user's perspective and its fine. We're not just end users, we can influence things on a larger scale (sometimes, at least) cheers, Yannis
Personally I think that one thing that might work better is to avoid IPv4 only services when there is an alliterative service with IPv6 enabled. One only has some little extra work, like installing a browser plugin and watching the output.
So do not complain that $ISP has no IPv6 choose an alliterative if you can. If the git web service you are using does not complain and open tickets, choose an alternative. If your CDN does not fully support IPv6 do not complain and choose an alternative. ....
Jens
Hi, On Fri, May 29, 2020 at 11:29:56AM +0300, Dez C wrote:
Just check the google stats for the percentage of users accessing google via IPv6: Sep 2008: 0.04%, May 2020: 30% . Then check the stats for Greece. Greece is at almost 50% and I can tell you why: We (main ISPs+Academia) created a task force and started presenting and educating (other SPs, Enterprises etc). I bet that countries with similar percentages followed a similar path.
The eyeball side (access ISPs) have done a good job, though it took 10 years longer than one would have hoped for, and many are still not there. The content and service and cloud and CDN and software development side still seems to be very much in the "denial" part of the curve, alas. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
On Fri, 29 May 2020, Gert Doering wrote:
Hi,
On Fri, May 29, 2020 at 11:29:56AM +0300, Dez C wrote:
Just check the google stats for the percentage of users accessing google via IPv6: Sep 2008: 0.04%, May 2020: 30% . Then check the stats for Greece. Greece is at almost 50% and I can tell you why: We (main ISPs+Academia) created a task force and started presenting and educating (other SPs, Enterprises etc). I bet that countries with similar percentages followed a similar path.
The eyeball side (access ISPs) have done a good job, though it took 10 years longer than one would have hoped for, and many are still not there.
The content and service and cloud and CDN and software development side still seems to be very much in the "denial" part of the curve, alas.
Hi, Name & shame seems not to be working, though........ Any brilliant ideas to turn the table? Carlos
Gert Doering -- NetMaster -- have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
Dez C <dez@otenet.gr> writes:
On 5/29/20 10:38 AM, Jens Link wrote:
Nick Hilliard <nick@foobar.org> writes:
having the meetings, for starters. Sure. Let's talk more about deploying IPv6. Did work very well for the last decade / years.
oh, but it has. Talking about issues, creating traction, usually helps. Just check the google stats for the percentage of users accessing google via IPv6:
It's always the two sides technology and sociological actions that need to work together. However at this point in time I think we, as a network community, have to admit that we carry the responsibility to drive the change and have to embrace it. That means that we need to be one step ahead, probably make one more sacrifice then the end user will ever do. And today, not tomorrow go with IPv6. That also means actively using, promoting and preferring IPv6 only services. Even if they lack behind in some regards. And not accepting hardware, software or platforms which lack features in IPv6 only environments. If we don't take that responsibility today, everyone of us is contributing to a very distorted Internet without the ability to have real end-to-end connectivity. If not the network community, who else will take action in going towards IPv6 only? Best regards, Nico "Change starts from within" -- Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
That also means actively using, promoting and preferring IPv6 only services.
(I'm assuming that IPv6 only meens a service that is reachable only over IPv6 and not IPv4) I don't see why promoting communication failures is a good thing. Except possibly as a fun thing to nudge people to take action. For example a quiz with prizes could be hosted on an IPv6-only platform.
And not accepting hardware, software or platforms which lack features in IPv6 only environments.
I don't know where to put it, but there may be a benefit for a list that lists known internet services that do not (or poorly) support IPv6 and with replacements that do support them. Such a list may have two advantages: 1) Somebody who likes to promote IPv6 would not have to spend time looking for good alternatives to known brands 2) Being on a list of backward companies is bad pr for any company, so it may stimulate companies to get off the wrong part of the list.
Hey Philip, Philip Homburg <pch-ripeml@u-1.phicoh.com> writes:
That also means actively using, promoting and preferring IPv6 only services.
(I'm assuming that IPv6 only meens a service that is reachable only over IPv6 and not IPv4)
That's correct.
I don't see why promoting communication failures is a good thing.
As previously stated, I think that everyone [in our community] is able to get IPv6. So this is not about promoting communication failures, but switching over to a protocol from which we all benefit.
Except possibly as a fun thing to nudge people to take action. For example a quiz with prizes could be hosted on an IPv6-only platform.
And not accepting hardware, software or platforms which lack features in IPv6 only environments.
I don't know where to put it, but there may be a benefit for a list that lists known internet services that do not (or poorly) support IPv6 and with replacements that do support them.
You have a point and it has actually been started about a year ago: https://redmine.ungleich.ch/projects/ipv6/wiki/IPv6_Hardware_Compatibility_L... Cheers, Nico -- Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
As previously stated, I think that everyone [in our community] is able to get IPv6. So this is not about promoting communication failures, but switching over to a protocol from which we all benefit.
In my experience, if you make people jump through hoops, you don't get any buy-in. Yes, they may be able to figure out how to set up a tunnel to access your service, but they will never do anything to support IPv6 in their own products or services.
I don't know where to put it, but there may be a benefit for a list that lists known internet services that do not (or poorly) support IPv6 and with replacements that do support them.
You have a point and it has actually been started about a year ago:
https://redmine.ungleich.ch/projects/ipv6/wiki/IPv6_Hardware_Compatibility_L... t
What I meant was services: - what to use instead of github (probably gitlab) - what to use instead of zoom (maybe jitsi, but does jitsi scale?) - and where this discussion started, what to use instead of eventbrite.nl
On Fri, May 29, 2020 at 02:51:47PM +0200, Philip Homburg wrote:
[..]
I don't know where to put it, but there may be a benefit for a list that lists known internet services that do not (or poorly) support IPv6 and with replacements that do support them.
You have a point and it has actually been started about a year ago:
https://redmine.ungleich.ch/projects/ipv6/wiki/IPv6_Hardware_Compatibility_L...
What I meant was services: - what to use instead of github (probably gitlab) - what to use instead of zoom (maybe jitsi, but does jitsi scale?) - and where this discussion started, what to use instead of eventbrite.nl
right, we need to get at this from an end user perspective. Due to the pandemic, many people are now using their home internet connection for work. As the network providers for these home networks frequently were among the first to encounter the shortage of IPv4 addresses, many of these networks provide IPv6 connectivity while at the same time using some kind of NAT to provide IPv4 connectivity. These NAT systems tend to be overloaded, now probably more than usual. So the message to users is "If you have trouble to access company A providing service X, it might be because A does not support IPv6 connections. Try company B as an alternative who does have IPv6". Regards, Wolfgang Zenker -- punkt.de GmbH Tel. +49 721 9109-500 Fax: -100 .infrastructure info@punkt.de https://infrastructure.punkt.de/ Kaiserallee 13a CEO: Jürgen Egeling, Daniel Lienert, Fabian Stein D-76133 Karlsruhe AG Mannheim HRB 108285
On Fri, 29 May 2020, Philip Homburg wrote:
That also means actively using, promoting and preferring IPv6 only services.
(I'm assuming that IPv6 only meens a service that is reachable only over IPv6 and not IPv4)
I don't see why promoting communication failures is a good thing. Except possibly as a fun thing to nudge people to take action. For example a quiz with prizes could be hosted on an IPv6-only platform.
And not accepting hardware, software or platforms which lack features in IPv6 only environments.
I don't know where to put it, but there may be a benefit for a list that lists known internet services that do not (or poorly) support IPv6 and with replacements that do support them.
Such a list may have two advantages: 1) Somebody who likes to promote IPv6 would not have to spend time looking for good alternatives to known brands 2) Being on a list of backward companies is bad pr for any company, so it may stimulate companies to get off the wrong part of the list.
ipv6shamelist.org seems to be available :-) Cheers, Carlos
Am Fri, 29 May 2020 schrieb Philip Homburg:
I don't see why promoting communication failures is a good thing.
Current IPv4-only services already cause communication failures, because they lack support for the latest standard version of the IP protocol and it is happening in networks where you wouldn't expect it: There is a well known very large telco provider in germany who offers broad ipv6 support, even on mobile. But their invoices will never reach the customer if it's mailserver is on an ipv6-only system, because they are not even offloading to a dualstack gateway for compatibility and enduser support is unable to route any complaint to someone clueful. You can do this correctly on your side of the wire by implementing some form of translation (and you should), but you need cooperation on the other side. There is lot of systems out there, having Ipv6 support, but checking connection credibility via IPv4 (mostly seen in broken email spamfilter setups, but not limited to that) and some of them do it on purpose. Some of them have been running ipv6 for a long time in their network, so they should know better. If you want to increase IPv6 adoption rates significantly from where we are now, just throwing ipv6 on the network it not enough. You need to address a grave acceptance problem: Server Admins don't want IPv6 or are afraid of it without valid reason anymore (mostly based on fud). People need to understand: Supporting other ipv6-only networks doesn't necessarily mean that you have to go ipv6-only yourself. Dualstack will be completely fine, but IPv6 is not optional anymore. As Gert wrote: The network is usually not the main problem IMHO RIPE NCC should provide a good example by offering at least dual stack based services for all their services without excuses. IPv6 support should be considered state of the art now. Bjørn -- Pengutronix e.K. | Bjørn Bürger | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-5002 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Hi, On Sat, May 30, 2020 at 01:53:58AM +0200, Bjoern Buerger wrote:
IMHO RIPE NCC should provide a good example by offering at least dual stack based services for all their services without excuses. IPv6 support should be considered state of the art now.
The NCC itself was asked like 15 years ago to provide dual-stack for everything, and as far as I can see, they've done a good job with that (thanks!). Using external services with no IPv6 is something not that easily addressed, but indeed, maybe some words might be spoken to these suppliers... Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
Philip Homburg <pch-ripeml@u-1.phicoh.com> writes:
I don't know where to put it, but there may be a benefit for a list that lists known internet services that do not (or poorly) support IPv6 and with replacements that do support them.
Some time ago I setup a wiki for stuff like that but got abused pretty fast. I'll move the content to markdown put it on gitlab (they have IPv6) an generate a website from there. More content would be welcome. Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
Dez C wrote on 29/05/2020 09:29:
What you're proposing is the end user's perspective and its fine. We're not just end users, we can influence things on a larger scale (sometimes, at least)
this kinda nails it. We're not appealing to end users because ipv6 is right at the bottom of the infrastructure stack and is completely boring for the same reason that e.g. cement or paint composition are boring. Sure, nerdy types like us might get excited about it, but we need to not kid ourselves that ipv6 has any mass appeal because it doesn't. People care about cat videos; people don't care how the cat videos arrive. If we want deployment, we need to create the ability to deploy ipv6 relatively easily, so that other pressures can be effective in pushing the actual deployment (e.g. pricing / NAT / policy / etc). There are lots of ways to approach this: one of them is having online meetings about deployment challenges. It isn't the only way; it's a long-term game and online deployment meetings won't cause the protocol to be deployed instantly. But it will help. Nick
On Fri, 29 May 2020, Jens Link wrote:
Nick Hilliard <nick@foobar.org> writes:
having the meetings, for starters.
Sure. Let's talk more about deploying IPv6. Did work very well for the last decade / years.
Personally I think that one thing that might work better is to avoid IPv4 only services when there is an alliterative service with IPv6 enabled. One only has some little extra work, like installing a browser plugin and watching the output.
So do not complain that $ISP has no IPv6 choose an alliterative if you can. If the git web service you are using does not complain and open tickets, choose an alternative. If your CDN does not fully support IPv6 do not complain and choose an alternative. ....
Hi, Fully agree. However it seems the ¤¤¤ argument often has more weight... :/ Regards, Carlos
Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
On 5/28/20 6:50 PM, Nico Schottelius wrote:
Jens Link <lists@quux.de> writes:
Nico Schottelius <nico.schottelius@ungleich.ch> writes:
I personally think for each IPv4 only service we should create an IPv6 only service and use that for ripe/ieee/network related events. I once removed the A record to a wiki I run for several nerds. I won't do that again. So much crying. And you can try for yourself: Put a link on twitter to an IPv6 only resource and see how many people are complaining. You are a person of your word and I take the liberty to share the experiment on here:
https://twitter.com/QuuxBerlin/status/1266021157469290501
(so far did not see anyone complaining)
no complaints from my IPv6-only (MAP-E) connection ;)
Everyone in our community should be able to get IPv6 anywhere, anytime. *should* I really don't think there is an excuse. HE.net work w/ static IPs, IPv6VPN.ch that we provide works with any kind of nat and I'd be open to make the latter a public service, if it was backed by more than just ungleich.
In a nutshell, everyone can get IPv6 anywhere.
So from my point of view it's only a matter of motivation and for us - in the network community - I'd assume that everybody is motivated to get connected via IPv6.
Best regards,
Nico
-- Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
On 28 May 2020, at 14:21, Gert Doering wrote:
The point was that the NCC is marketing an "IPv6 only" event, using a service provider who is not reachable from an IPv6 only client network.
https://www.ripe.net/ripe/mail/archives/ripe-list/2020-May/001867.html /N
please unsubscribe us On 28/05/2020 13:24, Jens Link wrote:
Ondřej Caletka <Ondrej.Caletka@ripe.net> writes:
Hi,
Register at: https://www.eventbrite.nl/e/ripe-ncceduca-ipv6-only-tickets-106761053184 $ dig AAAA www.eventbrite.nl +short $
"IPv6-only"
Jens
This is a great idea and I will definitely register. I cant help but wonder why there was no prior information about this, especially in RIPE's own IPv6 WG cheers, Yannis On 5/28/20 1:37 PM, Ondřej Caletka wrote:
Dear IPv6 working group,
You are invited to join us for a deep-dive into an IPv6-only world! We’re hosting the fourth edition of a RIPE NCC::Educa - a one day online event, bringing together experts from around the world to take a deeper look at topics of interest. Registration is free.
To mark the anniversary of World IPv6 Launch Day, we’re hosting the RIPE NCC::Educa IPv6-only on Monday, 8 June from 10:00 UTC+2 onwards.
Expert presenters will talk about what it means to run IPv6-only data centres, ISPs and enterprises, among other topics. You can view the agenda at: https://www.ripe.net/support/training/ripe-ncc-educa/ripe-ncc-educa-ipv6-202...
Register at: https://www.eventbrite.nl/e/ripe-ncceduca-ipv6-only-tickets-106761053184
We hope to see you online soon!
Best regards, Ondřej Caletka RIPE NCC
Hi *, How does it come that this event is "sold out"? By all means, its free and only virtual... How many slots are/were available? Will this be recorded and put online afterwards? Thanks. Best, Bernd
Hello Bernd,
How does it come that this event is "sold out"? By all means, its free and only virtual... How many slots are/were available?
The platform we are using has its limits for number of attendees. We've just raised the limit today so there are more tickets available now.
Will this be recorded and put online afterwards?
Yes, there will be recording, just like with previous Educas. -- Best regards, Ondřej Caletka, RIPE NCC
Ondřej Caletka <Ondrej.Caletka@ripe.net> writes:
Expert presenters will talk about what it means to run IPv6-only data centres, ISPs and enterprises, among other topics. You can view the agenda at: https://www.ripe.net/support/training/ripe-ncc-educa/ripe-ncc-educa-ipv6-202...
"Adobe Connect requires Flash Player 11.2 or above." Thanks for not letting me participate. We can discuss if using IPv4 only tools is a good idea or not but using something that requires Flash Player in 2020 is certainly not a good idea. As someone how is taking IT security serious and as a Linux User I fell discriminated. Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
On 08.06.20 10:08, Jens Link wrote:
Ondřej Caletka <Ondrej.Caletka@ripe.net> writes:
Expert presenters will talk about what it means to run IPv6-only data centres, ISPs and enterprises, among other topics. You can view the agenda at: https://www.ripe.net/support/training/ripe-ncc-educa/ripe-ncc-educa-ipv6-202...
"Adobe Connect requires Flash Player 11.2 or above."
Thanks for not letting me participate. We can discuss if using IPv4 only tools is a good idea or not but using something that requires Flash Player in 2020 is certainly not a good idea.
As someone how is taking IT security serious and as a Linux User I fell discriminated.
Jens
Try "Browser"....
Bernd Naumann <bena@spreadshirt.net> writes:
Try "Browser"....
I only get "Install flash". Using Firefox and Chromium. Jens -- ---------------------------------------------------------------------------- | Delbrueckstr. 41 | 12051 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
On 08.06.20 10:29, Jens Link wrote:
Bernd Naumann <bena@spreadshirt.net> writes:
Try "Browser"....
I only get "Install flash". Using Firefox and Chromium.
Jens
I may mistaken, but as far as I can tell (besides I still have flash installed :/) that is not used... Shouldn't there be an indicator icon that flash is used? I'm using firefox 76 on a Ubuntu 18 LTS. As Ondřej wrote, I think I'm also using html5. In the media section I see no flv or similar resource.
On 8.6. 2020 10:08, Jens Link wrote:
"Adobe Connect requires Flash Player 11.2 or above."
Thanks for not letting me participate. We can discuss if using IPv4 only tools is a good idea or not but using something that requires Flash Player in 2020 is certainly not a good idea.
As someone how is taking IT security serious and as a Linux User I fell discriminated.
Hello Jens, I'm very sorry about that. We have enabled HTML5 version of Adobe connect and were under impression that it would allow anybody to participate with just a browser. But today, I tested joining from my Linux and ChromeOS laptops and it turned out Adobe connect somehow evaluates User-agent string and offers HTML5 version only if your browser and operating system is approved. I only succeeded to connect to HTML5 version from Linux when I had my Firefox emulate Chrome on Windows. We will definitely reconsider using Adobe connect for next event. This event will be recorded and the recording will be published on an IPv6-ready platform that doesn't enforce Flash, so you will be able to at least follow the recordings. I know it's not as good as following the event live, but that's everything I can offer you right now :( -- Best regards, Ondřej Caletka RIPE NCC
On 8.6. 2020 10:33, Ondřej Caletka wrote:
I know it's not as good as following the event live, but that's everything I can offer you right now :(
Another tip for Linux users: there are Adobe connect apps for Android and iOS so you can try to follow the event on a mobile device. -- Ondřej Caletka RIPE NCC
* Jens Link
"Adobe Connect requires Flash Player 11.2 or above."
Thanks for not letting me participate. We can discuss if using IPv4 only tools is a good idea or not but using something that requires Flash Player in 2020 is certainly not a good idea.
As someone how is taking IT security serious and as a Linux User I fell discriminated.
For what it is worth, I had the same problem, but solved it by installing Windows 10 (which can be downloaded for free nowadays) in a throwaway virtual machine. Hardly ideal, but it works. If you're quick you'll have time to do install it in the lunch break and catch the afternoon session. Tore
participants (16)
-
Bernd Naumann -
Bjoern Buerger -
Carlos Friaças -
Dez C -
Gert Doering -
Jens Link -
Niall O'Reilly -
Nick Hilliard -
Nico Schottelius -
Ondřej Caletka -
Philip Homburg -
thomas＠cis.uni-muenchen.de -
Tore Anderson -
twall -
Wolfgang Zenker -
Yannis Nikolopoulos