<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>There would be no need for upper levels to help out. Only during
the transition would there be IPv4 only clients. They would still talk to the
globally unique IPv4 addresses. However, once upgraded to IPv-X they would have
the ability to use the other level prefixes to communicate. Biggest IPv6
problem is the lack of compatibility with IPv4.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Anyway, since we have IPv6 my main point is that keeping your private
network separate from the public is more a matter of minimizing changes to your
internal LAN during whatever need comes up.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> TJ
[mailto:trejrco@gmail.com] <br>
<b>Sent:</b> Thursday, April 15, 2010 11:10 AM<br>
<b>To:</b> Gams, Matthew D<br>
<b>Cc:</b> Gary T. Giesen; arin-ppml@arin.net<br>
<b>Subject:</b> Re: [arin-ppml] The role of NAT in IPv6<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<p class=MsoNormal>> -----Original Message-----<br>
> From: Gary T. Giesen [mailto:<a href="mailto:ggiesen@akn.ca">ggiesen@akn.ca</a>]<br>
> Sent: Thursday, April 15, 2010 10:40 AM<br>
> To: Gams, Matthew D<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal>> Cc: '<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>'<br>
> Subject: RE: [arin-ppml] The role of NAT in IPv6<br>
><br>
> On Thu, 2010-04-15 at 11:21 -0400, Gams, Matthew D wrote:<o:p></o:p></p>
</div>
</div>
</blockquote>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p class=MsoNormal>Close is the key word. It is a flat address which is then
being logically broken down. A true hierarchical model (closer to the OSI
addressing) would have those layers built-in and be able to take them out when
not needed. Also, the IPv6 model breaks down as you allow exceptions with
bigger organizations getting direct allocations.<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><br>
I like the level concept in IS-IS and wish IPv6 would have taken the concept
and created something a bit different. Level-0, 1, 2, 3, and 4. We could have
still ended up with 128-bit addressing if needed (or more) and been much more
efficient. Organizations would still use their comfortable 32-bit IPv4
addresses and only the network "gods" would know anything about the
larger space available. During transition RFC1918 would be kept intact but
eventually DNS would respond with the updated prefixes to allow global routing
of the new blocks and in theory the whole 32-bit address space could be used
internally.<br>
<br>
Routers would only know about the level are configured for with only Level-4
being the biggest back-bone routers that know the whole structure.<br>
<br>
Oh well, maybe in another reality... :)<o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>That model works for edge nodes accessing centrally
located/managed services, client-server style.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Scaling it to end-to-end / peer-to-peer operations is either
really kludgey at Layer3 or relies increasingly on Layer7'ish
helpers.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>(In some cases that model breaks even sooner - there are
networks where a total of 4.3Billion addresses may not be enough by the time
you divie it up in a hierarchical fashion ... requiring yet more layers of duct
tape and/or bailing wire.)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>IMHO, if it is a network problem it should almost always be
solved at the network layer. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Let's get that part fixed first, and let's see where we can
make it with that infrastructure ... <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>/TJ<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>