Amazon EC2-Classic Is Retiring • Hacker News Board

Re: Amazon EC2-Classic Is Retiring

#151

Post by fulafel » Sun, Aug 01, 2021, 6:02 AM UTC

KirillPanov wrote: post #127

lillecarl wrote: post #118

Earlier quoted context omitted.

It would be nice if NAT64 was embraced everywhere, I love typing IP addresses because I'm lazy, but we need IPv6 right now. There are still too many rough edges going V6 only though, like if I set my own DNS servers, will they resolve A records to NAT64 AAAA records? And how will the regular Windows sysadmin deal with registering DNS records?

We continue to suffer for the boneheaded failure to make NAT64 a mandatory, required element of every IPv6 router. DJB saw all this with crystal clarity almost twenty years ago : http://cr.yp.to/djbdns/ipv6mess.html Note that when he wrote this, NAT64 didn't even exist. NAT64 is basically standardization of "make IPv6 work the way DJB said it should".

Everyone who wants to is already doing v4 NAT along with IPv6 in a dual-stack setup. In this NAT64 alternate reality the discussed AWS configuration would be "v6-only vpc with NAT64 disabled".

(And mandating NAT in routers would be a pretty radical departure from the current internet architecture).

Re: Amazon EC2-Classic Is Retiring

#152

Post by murgindrag » Sun, Aug 01, 2021, 10:53 AM UTC

psanford wrote: post #149

murgindrag wrote: post #147

Earlier quoted context omitted.

Not according to Google: https://cloud.google.com/products/ https://cloud.google.com/blog/products/workspace But it's a moot point in either case, if you want long-term support. * Internal corporate lines shift with re-orgs * Culture is shared and common * I've had issues across Google. I listed the ones I can talk about. My lesson, each time, has been: Never Use Google For Business. Ever.

Considering how many companies use gsuite and are happy with it, I'd say thats a pretty silly lesson.

Five out of six people report being happy playing Russian Roulette.

Re: Amazon EC2-Classic Is Retiring

#153

Post by p1mrx » Sun, Aug 01, 2021, 2:53 PM UTC

KirillPanov wrote: post #127

lillecarl wrote: post #118

Earlier quoted context omitted.

It would be nice if NAT64 was embraced everywhere, I love typing IP addresses because I'm lazy, but we need IPv6 right now. There are still too many rough edges going V6 only though, like if I set my own DNS servers, will they resolve A records to NAT64 AAAA records? And how will the regular Windows sysadmin deal with registering DNS records?

We continue to suffer for the boneheaded failure to make NAT64 a mandatory, required element of every IPv6 router. DJB saw all this with crystal clarity almost twenty years ago : http://cr.yp.to/djbdns/ipv6mess.html Note that when he wrote this, NAT64 didn't even exist. NAT64 is basically standardization of "make IPv6 work the way DJB said it should".

DJB's (sketch of a) solution seems more like 6to4, where every IPv4 address automatically gets a /48 IPv6 prefix. It was deprecated due to unpredictable reliability.

It doesn't make sense to have NAT64 on every router, because NAT64 is stateful and needs to be properly engineered into a network. There are also alternatives like DS-Lite and MAP, with different design tradeoffs.

Re: Amazon EC2-Classic Is Retiring

#154

Post by KirillPanov » Mon, Aug 02, 2021, 8:41 AM UTC

fulafel wrote: post #151

KirillPanov wrote: post #127

Earlier quoted context omitted.

We continue to suffer for the boneheaded failure to make NAT64 a mandatory, required element of every IPv6 router. DJB saw all this with crystal clarity almost twenty years ago : http://cr.yp.to/djbdns/ipv6mess.html Note that when he wrote this, NAT64 didn't even exist. NAT64 is basically standardization of "make IPv6 work the way DJB said it should".

Everyone who wants to is already doing v4 NAT along with IPv6 in a dual-stack setup. In this NAT64 alternate reality the discussed AWS configuration would be "v6-only vpc with NAT64 disabled". (And mandating NAT in routers would be a pretty radical departure from the current internet architecture).

Far less radical than having two different versions of IP on the Internet at the same time.

When there was only IPv4 there was no reason for backwards compatibility. Caring about backwards compatability doesn't become radical simply because it becomes necessary.

Re: Amazon EC2-Classic Is Retiring

#155

Post by simfree » Sat, Aug 07, 2021, 6:43 PM UTC

seized wrote: post #98

simfree wrote: post #58

Earlier quoted context omitted.

Google Fi already sells cell service, it's essentially T-Mobile service but without most domestic roaming and with higher prices than Mint, T-Mobile Connect and their other MVNOs. From what I hear MMS stopped working a few months ago for iPhones on Google Fi.

It's a higher price with the benefit of world wide roaming without a special plan. There are also some unlimited and multi line plans now. I've been on Fi for years and its great.

Google Fi has the same included international roaming country list as T-Mobile.