Brian Shacklett
My feedback
9 results found
-
149 votes
An error occurred while saving the comment Brian Shacklett supported this idea ·
-
10 votes
Brian Shacklett supported this idea ·
-
30 votes
Brian Shacklett supported this idea ·
-
26 votes
Brian Shacklett supported this idea ·
-
21 votes
An error occurred while saving the comment Brian Shacklett commented
How on earth is this not already implemented? Like Federico, I'm subscribed to one of the IETF mailing lists (v6ops) and all of the digests are sent in this format. I'd bet that the vast majority of digest emails from mailing lists are the same.
Brian Shacklett supported this idea ·
-
10 votes
Brian Shacklett supported this idea ·
-
27 votes
Brian Shacklett supported this idea ·
-
268 votes
Brian Shacklett supported this idea ·
-
124 votes
Brian Shacklett supported this idea ·
Guys, if you can't figure out how to do it, then hire someone who can. Heck, there are probably knowledgeable folks who would put the work in for free in order to drop another major site off of the list of those who are v4-only.
Right now it looks like you're doing nothing. Your response reads: "It's not a financial priority" or "it's too hard". Meanwhile, your entire brand is built around trust and doing the right thing for your customers.
Setting up v4 on a v6-only is, unfortunately, non-trivial. It should be easy, but it's not, and that means that there's a small, but growing, population out there who are blocked from using your service. Not to mention, folks don't have control over public WiFi. What happens when the operators of those hotspots decide they don't want to deal with dual-stack anymore? There goes one of the major drivers for your VPN product, unless it's v6-enabled.
Now, to give folks a little bit of hope: Proton already has a proper v6 allocation with real presence in the BGP table: https://stat.ripe.net/resource/2a05:2700::/29#tab=overview. So while the push for v6 isn't visible, there's at least _some_ effort being made.