<div dir="ltr"><div><div><div><div><div>Thank you, I forgot to think about NS and NA.<br><br></div>One more question, If I got the /64 mask from ISP and implement as below. Theoretically, is it work?<br><br></div><div>Normal Situation: work fine<br>
</div>IPv6 Internet ----- ISP (2001:db8:a:1::1/64) ----- (2001:db8:a:1::2/64) MyPC<br><br></div>My Implementation: is it possible?<br>IPv6 Internet ----- ISP (2001:db8:a:1::1/64) ----- (2001:db8:a:1:0::2/80) MyRouter (2001:db8:a:1:a::1/80) ----- (L2 SWITCH) ----- (2001:db8:a:1:a::2/80) MyPCs<br>
<br></div>So from my router will also be IPv6 network with Global Unicast address.<br><br></div>--Te<br><div><div><div><div><div><div><div><div><div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 18, 2014 at 1:14 PM, Eric Vyncke (evyncke) <span dir="ltr"><<a href="mailto:evyncke@cisco.com" target="_blank">evyncke@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>Not sure whether I fully understand the question in all details, but:</div>
<ol>
<li>on a LAN/WLAN (basically where NS/NA is required to work, = broadcast domain with MAC addresses), the use of a /64 prefix is recommended</li><li>Each host (being server or client) must have at least one global address within this prefix</li>
</ol>
<div>If you have one server per LAN, then it is perfectly OK to use one /64 per server. If you think about that, currently you use a /32 for IPv4 address :-) You are currently wasting more space (4 billion times more)</div>
<div><br>
</div>
<div>-éric</div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) -moz-use-text-color -moz-use-text-color;padding:3pt 0in 0in">
<span style="font-weight:bold">From: </span>Teerapatr Kittiratanachai <<a href="mailto:maillist.tk@gmail.com" target="_blank">maillist.tk@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>mercredi 18 juin 2014 05:28<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:ipv6-ops@lists.cluenet.de" target="_blank">ipv6-ops@lists.cluenet.de</a>" <<a href="mailto:ipv6-ops@lists.cluenet.de" target="_blank">ipv6-ops@lists.cluenet.de</a>><br>
<span style="font-weight:bold">Subject: </span>IPv6 Assignment for Server<br>
</div><div><div class="h5">
<div><br>
</div>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5">
<div>
<div>
<div dir="ltr">
<div>
<div>Dear IPv6-Ops,<br>
<br>
</div>
<div>I want the suggestion about the best practice for assign IPv6 Global Unicast address for server.<br>
According to the IPv6 Subnet ID also be built in with IPv6 address, so if I assign the /64 mask to the server is it will be some of wasteful usage?<br>
</div>
<div>AFAIK, the /64 mask address can be brought to use for many other subnets. Is it more suitable to assign the /128 to the server, or end server that doesn't act as any other gateway.<br>
<br>
</div>
<div>Thank you in advance.<br>
<br>
</div>
Regards,<br>
</div>
Teerapatr Kittiratanachai (Te)<br>
</div>
</div>
</div>
</blockquote>
</div></div></span>
</div>
</blockquote></div><br></div></div></div></div></div></div></div></div></div></div></div></div></div>