A lot of fuss, but if you look at the presentation slide in the middle of the page ( https://4.bp.blogspot.com/-PyyPpTv1p7g/WU7hMEBnm4I/AAAAAAAAE... for reference) it is clear that MIT is not stifling anything or shutting anyone's mouth. MIT is just moving to IPv6. Actually... MIT forcing an entire generation of future engineers to deal with IPv6... That will literally push innovation.
> MIT is just moving to IPv6. The "just" is incorrect. There are four bullets on the slide: DHCP, IPV6, private IPV4/NAT, and firewall. From the diagram it looks to me like even if you move to IPV6 (which, as others have noted, MIT has not yet rolled out, so at this point you can't), you will still be behind the firewall, so setting up a service visible to the Internet will still be more difficult than it used to be.
By installing NAT, MIT stifles innovation
41–50 of 188 posts
Re: By installing NAT, MIT stifles innovation
#42Earlier quoted context omitted.
If it went down like it did at CMU, IT polarized into a camp that wanted to maintain the traditional stack and a camp that wanted to tear it down and replace it with contemporary cloud services. When the latter won, they wasted no time in salting the earth of the former's territory. Disclaimer: I wasn't actually party to any of this, I heard it second hand, corrections welcome.
So why did the latter win?
Re: By installing NAT, MIT stifles innovation
#43Earlier quoted context omitted.
NAT will make future sales of IPv4 blocks easier? As you say, MIT doesn't need all those 8 million IP addresses, and eventually will adopt IPv6 anyway. Might as well sell surplus v4 space while it's still valuable.
But why is MIT making money on those addresses more valuable than giving its students an opportunity to experiment and innovate? Why would selling those "unused" spaces to Amazon further the cause of IPv6? Also MIT hasn't even rolled out IPv6 yet...
Re: By installing NAT, MIT stifles innovation
#44Projects have broken over this, with no real gain for implementing it. You would expect more rationality from MIT, of all places.
We are humans. We're not rational beings, we're rationalizing beings. We like to pretend we are better but there is a valid reason that they say science progresses one death at a time.
Re: By installing NAT, MIT stifles innovation
#45Normally, ISPs get a /32, from which, they hand out /48s to their customer. And, with pretty much zero paper work, and ISP can get a second /32 (usually adjacent with their first /32 so they can summarize as a /31).
So - an ISP might get 2001:1868::/32 and then hand off 2001:1868:0209::/48 to a customer.
Because a /48 allows 2^16 or 65k networks, each network containing (effectively) an infinite number of hosts, pretty much every single geographic region company can be effectively served with a single /48. The /32 allows the ISP to have 65K customer (each of which has 65K networks).
What on earth is MIT going to do with a 2603:4000::/24? I'd love to hear the story behind why they got such a large block.
edit: according to https://www.arin.net/fees/fee_schedule.html this is considered a "medium" (WTF?) allocation with a cost of $4k/year.
Re: By installing NAT, MIT stifles innovation
#46Perhaps doing it over .onion? Actually I have been experimenting this for my pet projects. Downside is that it's relatively slow but getting "global" address is click (well a few lines of config) away...
But that would just be ridiculous, considering that experimenting with Tor relays is like a favorite student passtime...
Re: By installing NAT, MIT stifles innovation
#47Re: By installing NAT, MIT stifles innovation
#48A lot of fuss, but if you look at the presentation slide in the middle of the page ( https://4.bp.blogspot.com/-PyyPpTv1p7g/WU7hMEBnm4I/AAAAAAAAE... for reference) it is clear that MIT is not stifling anything or shutting anyone's mouth. MIT is just moving to IPv6. Actually... MIT forcing an entire generation of future engineers to deal with IPv6... That will literally push innovation.
> MIT is just moving to IPv6. The "just" is incorrect. There are four bullets on the slide: DHCP, IPV6, private IPV4/NAT, and firewall. From the diagram it looks to me like even if you move to IPV6 (which, as others have noted, MIT has not yet rolled out, so at this point you can't), you will still be behind the firewall, so setting up a service visible to the Internet will still be more difficult than it used to be.
I totally understand the need for a campus-wide firewall. The MIT network is a juicy target for botnets, and individual students are not good enough at running security on their own computers. The old approach to IP assignment was that you needed to get your IP approved and made routable by IS&T anyway, and if they detected botnet activity on your computer, they'd manually intervene and make it unroutable again. That sounds like a lot of work.
If computers end up with firewalled but publicly routable IPv6 addresses, that sounds perfect.
Re: By installing NAT, MIT stifles innovation
#49[1]:http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP...
Re: By installing NAT, MIT stifles innovation
#50A lot of fuss, but if you look at the presentation slide in the middle of the page ( https://4.bp.blogspot.com/-PyyPpTv1p7g/WU7hMEBnm4I/AAAAAAAAE... for reference) it is clear that MIT is not stifling anything or shutting anyone's mouth. MIT is just moving to IPv6. Actually... MIT forcing an entire generation of future engineers to deal with IPv6... That will literally push innovation.
> Actually... MIT forcing an entire generation of future engineers to deal with IPv6 Then why are they doing NAT? Edit: Although moving to NAT might push innovation too, or at least some clever hacks. Speaking of that, if you want use a relay to do NAT traversal then is TCP over ARQ (on UDP) as bad as TCP over TCP?
Because they sold their IPv4 addresses.