News for hackers. Stuff that matters.
Re:One way to make containers network: BGP by otterley on Monday July 18, 2016 @12:07AM (#12113181)
Both AWS and GCE can allocate private 10.0.0.0/8 subnets for internal networks (e.g. VPCs). There is no address scarcity in such subnets.
Re:One way to make containers network: BGP by e12e on Monday July 18, 2016 @02:57AM (#12113563)
There's a big difference between routable (on the Internet) addresses and non-routable addresses. For one, you can trivially merge two different sets of resources (say from two different organizations or projects) without address conflicts, if they both have globally unique, routable addresses.

LAN networking is great. Internet networking is so much better, it has effectively given birth to a new technological age.

Re:One way to make containers network: BGP by otterley on Monday July 18, 2016 @11:53AM (#12115804)
I don't disagree on these particular points. My contention is solely that lack of IPv6 is not a showstopper.
Re:One way to make containers network: BGP by tw04 on Monday July 18, 2016 @02:34PM (#12117139)
It absolutely is a showstopper if you don't have applications that are NAT friendly. And in 2016 if you are forcing people to use NAT and claiming that's a fix, you're doing the entire world a disservice.
Re:One way to make containers network: BGP by otterley on Tuesday July 19, 2016 @12:10AM (#12119575)
I've been hearing this argument for 15 years now and it hasn't changed. Sure, there's a public address shortage these days, but the incessant whining by end-to-end purists who think NAT is an unbearable sin falls on deaf ears just as much now as it ever did.

I'm not against V6 by any means, but internal IPv4 private subnets are simply not a problem for the 99+% of who still somehow manage to get things done in the real world.