News for hackers. Stuff that matters.

A comment on IPv6 Support for AWS Extended to 15 Regions. Parent comment

Re:IPv6 Support for AWS Extended to 15 Regions by bluejekyll on Wednesday January 25, 2017 @11:02PM (#13488598)
Out of curiousity, why? IPv6 is much more important on the edge, than inside your VPC.

Is it just for the simplicity of your networking? One strategy is to define your IPv4 space inside one of your IPv6 networks such that you have dual addressing with directly mappable addresses.

Do you have some other use case than just simplicity of design?

[ Parent | on HN ]
Re:IPv6 Support for AWS Extended to 15 Regions by dboreham on Wednesday January 25, 2017 @11:27PM (#13488702)
I'm not the OP but globally unique and optionally reachable from anywhere addresses are super-attractive from a not-going-insane perspective if you manage a non-triviality sized network.
[ Parent | on HN ]
Re:IPv6 Support for AWS Extended to 15 Regions by bluejekyll on Thursday January 26, 2017 @12:40AM (#13489030)
Absolutely, but the OP was talking about a 4-6 NAT, which seems less useful.
[ Parent | on HN ]
Re:IPv6 Support for AWS Extended to 15 Regions by subway on Thursday January 26, 2017 @03:06AM (#13489599)
GP hit it on the head. Every node is globally addressable. Regarding the 464xlat, that's strictly to enable hosts in the internal network to communicate with external IPv4 only hosts. IPv6 is still used as the only internal transport, and primary external transport.
[ Parent | on HN ]
Re:IPv6 Support for AWS Extended to 15 Regions by bluejekyll on Thursday January 26, 2017 @03:35AM (#13489731)
Cool. That makes a lot more sense.
[ Parent | on HN ]
Re:IPv6 Support for AWS Extended to 15 Regions by cortesoft on Thursday January 26, 2017 @11:30AM (#13492716)
The key was the 'outbound' word.
[ Parent | on HN ]