<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello Jim - <div> </div><div> You've got quite a bit of interesting information in your posts; I'd ask that </div><div> if possible you focus on the policy implications or suggestions for policy</div><div> changes (if any) that are necessary as as result of your information.</div><div><br></div><div>Thanks!</div><div>/John</div><div><br></div><div>John Curran</div><div>President and CEO</div><div>ARIN</div><div><br></div><div>p.s. For those interesting in training materials on IPv6, ARIN maintains a collection</div><div> of these educational materials at <<a href="https://www.arin.net/knowledge/general.html">https://www.arin.net/knowledge/general.html</a>></div><div> <br><div><div><div>On Aug 1, 2010, at 4:04 PM, Jim Fleming wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">IPv6 Education via ARIN Labor Union Hall ?<br><br>As a suggestion, ARIN may want to provide some IPv6 Education for your rank and file members<br>at your union hall. It appears people are not familiar with IPv6 and how it works.<br>
<br>Also, those Evil NAT Boxes may now morph into professional-grade IPv6 Network Elements in<br>a more comprehensive architecture. They were placed in the CPE for a reason. They have flash<br>memories to allow upgrades. They also allow storage for DHT - Distributed Hash Table parameters.<br>
If you are not educated about IPv6 DHTs may be very hard to grok. The address/key is 480 bits not 128<br>which is way too small.<br><br>In other IPv6 news/education you may want to note that proposals are being made to change the basic<br>
320-bit header. IPv4 has 160-bit basic headers and changes are harder with ASICs in hardware routers.<br><a href="http://www.ietf.org/mail-archive/web/ipv6/current/msg12067.html">http://www.ietf.org/mail-archive/web/ipv6/current/msg12067.html</a><br>
<br>Speaking of education, you might want to take advantage of various Do It Yourself Router Construction<br>classes.<br><a href="http://NetFPGA.org/">http://NetFPGA.org</a><br><br>At the risk of making the picture more complex, it may be important to track the IEEE 802.1Q work<br>
on single, double and triple VLAN Tagging. The 60 and 66 bit Address Plans bracket 64-bit plans.<br><a href="http://en.wikipedia.org/wiki/Talk:IEEE_802.1Q">http://en.wikipedia.org/wiki/Talk:IEEE_802.1Q</a><br><br>At the end of the day, the Address Plan survives the protocol(s). Renumbering is expensive.<br>
<br>Lastly, there are groups doing what they call "research".<br><a href="http://www.irtf.org/charter?gtype=rg&group=rrg">http://www.irtf.org/charter?gtype=rg&group=rrg</a><br>They seem mostly focused on a Location ID split, which people already use in IPv6.<br>
<br>If you view the evolution as a (Fringe(Edge(Core))) three ring target IPv6 is the Edge.<br>IPv4 currently dominates the Core, with MPLS which is outside the IP Header.<br>IPv4 can of course be extended with much larger address spaces for Core players.<br>
IPv6 helps to restore the illusion of an end-to-end best-effort .NET that just works.<br>...that is the illusion from "the Fringe"...<br><br>
_______________________________________________<br>PPML<br>You are receiving this message because you are subscribed to<br>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact info@arin.net if you experience any issues.<br></blockquote></div><br></div></div></body></html>