<story><title>By installing NAT, MIT stifles innovation</title><url>http://blog.achernya.com/2017/06/by-installing-nat-mit-stifles-innovation.html?view=classic</url></story><parent_chain><item><author>znpy</author><text>A lot of fuss, but if you look at the presentation slide in the middle of the page (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;4.bp.blogspot.com&amp;#x2F;-PyyPpTv1p7g&amp;#x2F;WU7hMEBnm4I&amp;#x2F;AAAAAAAAEZ0&amp;#x2F;IZSBv4d5G1kV2rCkpA-DziMB_4o2ri0RQCLcBGAs&amp;#x2F;s640&amp;#x2F;MITNAT-Slide.png&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;4.bp.blogspot.com&amp;#x2F;-PyyPpTv1p7g&amp;#x2F;WU7hMEBnm4I&amp;#x2F;AAAAAAAAE...&lt;/a&gt; for reference) it is clear that MIT is not stifling anything or shutting anyone&amp;#x27;s mouth.&lt;p&gt;MIT is just moving to IPv6.&lt;p&gt;Actually... MIT forcing an entire generation of future engineers to deal with IPv6... That will literally push innovation.</text></item></parent_chain><comment><author>anderskaseorg</author><text>Yes, yes, it’s been three months since the provost triumphantly announced that IPv6 will finally be coming to the campus network, and communication about IPv6 on campus goes back much longer than that, but we have yet to see it in a single building (beyond the buildings where students have set up their own tunnels, and who knows if those will even work with the new network).  Meanwhile, the NAT was deployed in twelve buildings with same-day notice and no prior communication, leaving some student groups with unreachable servers.  If this had anything to do with pushing innovation, don’t you think the priorities and communication pattern would have been a bit different?</text></comment>
<story><title>By installing NAT, MIT stifles innovation</title><url>http://blog.achernya.com/2017/06/by-installing-nat-mit-stifles-innovation.html?view=classic</url></story><parent_chain><item><author>znpy</author><text>A lot of fuss, but if you look at the presentation slide in the middle of the page (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;4.bp.blogspot.com&amp;#x2F;-PyyPpTv1p7g&amp;#x2F;WU7hMEBnm4I&amp;#x2F;AAAAAAAAEZ0&amp;#x2F;IZSBv4d5G1kV2rCkpA-DziMB_4o2ri0RQCLcBGAs&amp;#x2F;s640&amp;#x2F;MITNAT-Slide.png&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;4.bp.blogspot.com&amp;#x2F;-PyyPpTv1p7g&amp;#x2F;WU7hMEBnm4I&amp;#x2F;AAAAAAAAE...&lt;/a&gt; for reference) it is clear that MIT is not stifling anything or shutting anyone&amp;#x27;s mouth.&lt;p&gt;MIT is just moving to IPv6.&lt;p&gt;Actually... MIT forcing an entire generation of future engineers to deal with IPv6... That will literally push innovation.</text></item></parent_chain><comment><author>dheera</author><text>No. IPv6 is great in concept but the world just isn&amp;#x27;t ready for it yet. Even our Google Wifi access points don&amp;#x27;t support IPv6 in their latest firmware, so I have no way of using IPv6 even though Comcast supports it. AWS IPv6 support has been sketchy until only this year. Many parts of the world are happily dancing with their IPv4 NAT and their sysadmins have no incentives to support IPv6 whatsoever.&lt;p&gt;Forcing people to use anything is &lt;i&gt;never&lt;/i&gt; a good way to promote innovation.&lt;p&gt;I went to MIT for my undergrad and doctoral studies. One of the &lt;i&gt;main&lt;/i&gt; reasons I chose MIT over other schools was the ease of availability of static IP addresses, unlimited symmetric gigabit bandwidth, no port restrictions, and other things. I even mentioned this in my undergrad application essay. I built a &lt;i&gt;lot&lt;/i&gt; of things with it and learned a lot in my time there. I probably learned more outside of classes than in classes, and I think that&amp;#x27;s one of the distinguishing aspects of MIT culture.</text></comment>