<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Howto Subnet IPv6</title>
	<atom:link href="http://www.clarksys.com/blog/2009/03/12/howto-subnet-ipv6/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.clarksys.com/blog/2009/03/12/howto-subnet-ipv6/</link>
	<description>Rants and Raves!</description>
	<lastBuildDate>Fri, 12 Feb 2010 03:10:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Max</title>
		<link>http://www.clarksys.com/blog/2009/03/12/howto-subnet-ipv6/comment-page-1/#comment-100</link>
		<dc:creator>Max</dc:creator>
		<pubDate>Thu, 21 May 2009 17:02:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarksys.com/?p=399#comment-100</guid>
		<description>Chris,

Maybe this will help you (&lt;a href=&quot;https://www.arin.net/policy/nrpm.html#six54&quot; rel=&quot;nofollow&quot;&gt;https://www.arin.net/policy/nrpm.html#six54&lt;/a&gt;):

&lt;blockquote&gt;
&gt; /64 when it is known that one and only one subnet is needed
&gt; /56 for small sites, those expected to need only a few subnets over the next 5 years.
&gt; /48 for larger sites
&lt;/blockquote&gt;

We will allocate a /48 to any downstream customer that requests one otherwise it is a /56. Anything connected to one of our routers is a /64 nothing larger. We use /126 on all of our connected interfaces with the customer. A /120 in your case for HSRP would fit the bill, we use a second interface via a different device and OSPF costing to facilitate link redundancy.

-Max</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>Maybe this will help you (<a href="https://www.arin.net/policy/nrpm.html#six54" rel="nofollow">https://www.arin.net/policy/nrpm.html#six54</a>):</p>
<blockquote><p>
&gt; /64 when it is known that one and only one subnet is needed<br />
&gt; /56 for small sites, those expected to need only a few subnets over the next 5 years.<br />
&gt; /48 for larger sites
</p></blockquote>
<p>We will allocate a /48 to any downstream customer that requests one otherwise it is a /56. Anything connected to one of our routers is a /64 nothing larger. We use /126 on all of our connected interfaces with the customer. A /120 in your case for HSRP would fit the bill, we use a second interface via a different device and OSPF costing to facilitate link redundancy.</p>
<p>-Max</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.clarksys.com/blog/2009/03/12/howto-subnet-ipv6/comment-page-1/#comment-99</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 21 May 2009 15:49:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarksys.com/?p=399#comment-99</guid>
		<description>Max,

Thanks for the information. I feel that not all customers deserve a /48. I work for a Co-location facility and we also have several DSL and ATM customers. So I am looking into the implementation for our customers; If we follow the RFCs and guidelines, then I honestly feel that giving a Co-location customer /48 is a waste of address space if the customer only requires a handful of subnets, it would make more sense to give the customer a /56. We also implement HSRP for customers that have IPv4 connectivity, so when the time comes to implement IPv6 and HSRP (There is anycast), but for now, we are looking at all options and the best scalable method; So in the case with HSRP and IPv6, it does not make sense configuring a vlan interface with a /64. I see that maybe configuring the SVI with a /120 and then routing a /56 or a /48 to the customers router from the /120. I have reviewed many RFCs and the discussion for subnets that are longer than a /64 and what is breaks and so fourth, so I am just trying to get an idea what others have implemented.

Thanks for your time.
Chris</description>
		<content:encoded><![CDATA[<p>Max,</p>
<p>Thanks for the information. I feel that not all customers deserve a /48. I work for a Co-location facility and we also have several DSL and ATM customers. So I am looking into the implementation for our customers; If we follow the RFCs and guidelines, then I honestly feel that giving a Co-location customer /48 is a waste of address space if the customer only requires a handful of subnets, it would make more sense to give the customer a /56. We also implement HSRP for customers that have IPv4 connectivity, so when the time comes to implement IPv6 and HSRP (There is anycast), but for now, we are looking at all options and the best scalable method; So in the case with HSRP and IPv6, it does not make sense configuring a vlan interface with a /64. I see that maybe configuring the SVI with a /120 and then routing a /56 or a /48 to the customers router from the /120. I have reviewed many RFCs and the discussion for subnets that are longer than a /64 and what is breaks and so fourth, so I am just trying to get an idea what others have implemented.</p>
<p>Thanks for your time.<br />
Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max</title>
		<link>http://www.clarksys.com/blog/2009/03/12/howto-subnet-ipv6/comment-page-1/#comment-95</link>
		<dc:creator>Max</dc:creator>
		<pubDate>Wed, 20 May 2009 19:53:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarksys.com/?p=399#comment-95</guid>
		<description>Chris,

I have looked into different IPv6 subnet lengths but because ARIN wants to assign /32s to ISPs and wants the ISP to allocate out a /48 per customer it hasn&#039;t been a pressing issue as of yet. Honestly our requirement is assigning a /128 for a router to customer connection and then the /48 for the customer. We&#039;ve started looking at pushing IPv6 out to our Metro Fiber customers (&lt;a href=&quot;http://www.phyber.com/network/ontap.html&quot; rel=&quot;nofollow&quot;&gt;Phyber ONTAP&lt;/a&gt;) but that is probably going to be a slow rollout.

-Max</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>I have looked into different IPv6 subnet lengths but because ARIN wants to assign /32s to ISPs and wants the ISP to allocate out a /48 per customer it hasn&#8217;t been a pressing issue as of yet. Honestly our requirement is assigning a /128 for a router to customer connection and then the /48 for the customer. We&#8217;ve started looking at pushing IPv6 out to our Metro Fiber customers (<a href="http://www.phyber.com/network/ontap.html" rel="nofollow">Phyber ONTAP</a>) but that is probably going to be a slow rollout.</p>
<p>-Max</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.clarksys.com/blog/2009/03/12/howto-subnet-ipv6/comment-page-1/#comment-94</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 20 May 2009 19:43:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarksys.com/?p=399#comment-94</guid>
		<description>Your statement &#039; An IPv6 /32 is 2^16 (65536) /48 subnets &#039; is assumed for one pop? Have you explored or researched anything longer than a /32 and shorter than a /48; Example, 32 /37s or 64 /38s if an ISP has several POPs and assigning several /37s or /38s to a single pop and so fourth? Thanks</description>
		<content:encoded><![CDATA[<p>Your statement &#8216; An IPv6 /32 is 2^16 (65536) /48 subnets &#8216; is assumed for one pop? Have you explored or researched anything longer than a /32 and shorter than a /48; Example, 32 /37s or 64 /38s if an ISP has several POPs and assigning several /37s or /38s to a single pop and so fourth? Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max</title>
		<link>http://www.clarksys.com/blog/2009/03/12/howto-subnet-ipv6/comment-page-1/#comment-91</link>
		<dc:creator>Max</dc:creator>
		<pubDate>Sun, 17 May 2009 21:57:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarksys.com/?p=399#comment-91</guid>
		<description>I&#039;ve had the same problem trying to find an IPv6 calculator. The problem seems to be that the output is simply too big for any of them to handle.

-Max</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had the same problem trying to find an IPv6 calculator. The problem seems to be that the output is simply too big for any of them to handle.</p>
<p>-Max</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Werner</title>
		<link>http://www.clarksys.com/blog/2009/03/12/howto-subnet-ipv6/comment-page-1/#comment-90</link>
		<dc:creator>Werner</dc:creator>
		<pubDate>Sun, 17 May 2009 11:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarksys.com/?p=399#comment-90</guid>
		<description>Thank you, that made IPv6 a little clearer to me. Unfortunately there is no ipv6 calculator on the net that can actually handle the subnetting of a /32 into 65536 /48 Networks :-( 

http://www.liquidalchemy.com/liquidalchemy/index.php

e.g. 
2001:f238:/32 into 2^16 /48s doesn&#039;t work :D 

Werner</description>
		<content:encoded><![CDATA[<p>Thank you, that made IPv6 a little clearer to me. Unfortunately there is no ipv6 calculator on the net that can actually handle the subnetting of a /32 into 65536 /48 Networks :-( </p>
<p><a href="http://www.liquidalchemy.com/liquidalchemy/index.php" rel="nofollow">http://www.liquidalchemy.com/liquidalchemy/index.php</a></p>
<p>e.g.<br />
2001:f238:/32 into 2^16 /48s doesn&#8217;t work :D </p>
<p>Werner</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neetee</title>
		<link>http://www.clarksys.com/blog/2009/03/12/howto-subnet-ipv6/comment-page-1/#comment-55</link>
		<dc:creator>Neetee</dc:creator>
		<pubDate>Wed, 22 Apr 2009 15:28:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarksys.com/?p=399#comment-55</guid>
		<description>Keep up the good work.</description>
		<content:encoded><![CDATA[<p>Keep up the good work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
