<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Roller Network Newspipe &#187; IPv6</title>
	<atom:link href="http://www.rollernet.us/wordpress/category/ipv6/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rollernet.us/wordpress</link>
	<description>News, Announcements, and Status Updates</description>
	<lastBuildDate>Wed, 10 Mar 2010 17:29:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Verizon; Still No Progress</title>
		<link>http://www.rollernet.us/wordpress/2010/02/verizon-still-no-progress/</link>
		<comments>http://www.rollernet.us/wordpress/2010/02/verizon-still-no-progress/#comments</comments>
		<pubDate>Sun, 14 Feb 2010 04:44:28 +0000</pubDate>
		<dc:creator>Roller Network</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[New Facility]]></category>

		<guid isPermaLink="false">http://www.rollernet.us/wordpress/?p=601</guid>
		<description><![CDATA[It&#8217;s been a while since we posted a Verizon update. The last time we had contact with them was at the end of December, and we recently learned that as of Friday (02-12-2010) that no progress has been made in re-provisioning the circuit to match what was ordered. The latest roadblock is that there isn&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s been a while since we posted a Verizon update. The last time we had contact with them was at the end of December, and we recently learned that as of Friday (02-12-2010) that no progress has been made in re-provisioning the circuit to match what was ordered. The latest roadblock is that there isn&#8217;t any capacity at the San Jose hub for us. This has become the longest attempt at a new circuit turn-up that we have ever had the displeasure to experience.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rollernet.us/wordpress/2010/02/verizon-still-no-progress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Return of Outbound Account (AUTH) Logs</title>
		<link>http://www.rollernet.us/wordpress/2010/02/return-of-outbound-account-auth-logs/</link>
		<comments>http://www.rollernet.us/wordpress/2010/02/return-of-outbound-account-auth-logs/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 01:32:03 +0000</pubDate>
		<dc:creator>Roller Network</dc:creator>
				<category><![CDATA[Changes]]></category>
		<category><![CDATA[IPv6]]></category>

		<guid isPermaLink="false">http://www.rollernet.us/wordpress/?p=567</guid>
		<description><![CDATA[The logs for Outbound Accounts have returned!
We have added preliminary IPv6 support (display only, no CIDR searching yet) and our queue ID will now be logged if the message was accepted into the mail queue. Viewing is now by outbound account name instead of domain name, which means that submissions from &#8220;mail server&#8221; account types [...]]]></description>
			<content:encoded><![CDATA[<p>The logs for Outbound Accounts have returned!</p>
<p>We have added preliminary IPv6 support (display only, no CIDR searching yet) and our queue ID will now be logged if the message was accepted into the mail queue. Viewing is now by outbound account name instead of domain name, which means that submissions from &#8220;mail server&#8221; account types are now viewable in the logs.</p>
<p>Due to these changes there&#8217;s a new URL for the outbound account logs:</p>
<p><a href="https://acc.rollernet.us/mail/authlog.php">https://acc.rollernet.us/mail/authlog.php</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.rollernet.us/wordpress/2010/02/return-of-outbound-account-auth-logs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Send Mail Using IPv6!</title>
		<link>http://www.rollernet.us/wordpress/2010/02/send-mail-using-ipv6/</link>
		<comments>http://www.rollernet.us/wordpress/2010/02/send-mail-using-ipv6/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 00:48:07 +0000</pubDate>
		<dc:creator>Roller Network</dc:creator>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.rollernet.us/wordpress/?p=557</guid>
		<description><![CDATA[If you&#8217;re feeling brave and have IPv6 connectivity, you can now submit  mail to our Outbound Mail service (SMTP AUTH) over IPv6 by connecting to  &#8220;smtpauth6.rollernet.us&#8221;. All of the same ports and TLS available under  IPv4 also apply as we have simply dual-stacked the service. Please see &#8220;Submitting Outbound Mail via IPv6&#8221; [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re feeling brave and have IPv6 connectivity, you can now submit  mail to our Outbound Mail service (SMTP AUTH) over IPv6 by connecting to  &#8220;smtpauth6.rollernet.us&#8221;. All of the same ports and TLS available under  IPv4 also apply as we have simply dual-stacked the service. Please see &#8220;<a href="http://forums.rollernet.us/viewtopic.php?f=14&amp;t=624">Submitting Outbound Mail via IPv6</a>&#8221; on the forums for current limitations.</p>
<p>As far as we&#8217;re aware, Roller Network one of the very few &#8211; maybe even the first &#8211; provider in our arena  to enable IPv6 for transport-level SMTP. This is quite a bit more  substantial than simply making a website IPv6 available, so please send  us feedback if you try it.</p>
<p><a href="http://forums.rollernet.us/viewforum.php?f=14">A new IPv6 section has also been added to the forums.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.rollernet.us/wordpress/2010/02/send-mail-using-ipv6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Colocation, Hosting Delays, and the Holiday Season</title>
		<link>http://www.rollernet.us/wordpress/2009/12/colocation-hosting-delays/</link>
		<comments>http://www.rollernet.us/wordpress/2009/12/colocation-hosting-delays/#comments</comments>
		<pubDate>Thu, 24 Dec 2009 17:11:08 +0000</pubDate>
		<dc:creator>Roller Network</dc:creator>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[New Facility]]></category>
		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.rollernet.us/wordpress/?p=494</guid>
		<description><![CDATA[If you&#8217;ve been keeping up on our newspipe you&#8217;ll know that the long story of delays with Verizon continues. We were informed yesterday (Dec 22.) that the circuit was ready, however it still does not need our basic requirements (IPv4/IPv6 dual stack). This is continuing to impact our ability to expand our colocation, dedicated servers, [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;ve been keeping up on our newspipe you&#8217;ll know that the long story of delays with Verizon continues. We were informed yesterday (Dec 22.) that the circuit was ready, however it still does not need our basic requirements (IPv4/IPv6 dual stack). This is continuing to impact our ability to expand our colocation, dedicated servers, and hosting options.</p>
<p>As such, we have decided to enact a backup plan and bring in an additional circuit from Sprint so we can get back to business with a predictable timeline. The installation interval should be about 60 days plus we have requested an expedite on the order. As we&#8217;ve been a Sprint customer for 5 years and already have existing service with them, we do not expect the same problems that have plagued our attempt at obtaining service with Verizon. Furthermore, we are pleased to report that <a href="http://www.sprintv6.net/">Sprint&#8217;s IPv6 offering</a> is moving to their native network after we&#8217;ve been on their test network for the last 4 years. As soon as we have more information from Sprint we will share it here.</p>
<p>Again, we apologize for the delays and problems we&#8217;ve faced beyond our control in not meeting our original October/November 2009 opening of the new facility.</p>
<p>As today is December 24 this will be our last post on the newspipe for 2009. We&#8217;re going to take it easy for the next week so we can recharge and regroup for what lies ahead. As many of you (and us) are on vacation, holiday, or spending the new year with family and friends, we will be operating on a reduced schedule. Technical support will still be available. See you in 2010!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rollernet.us/wordpress/2009/12/colocation-hosting-delays/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Verizon FOC Update</title>
		<link>http://www.rollernet.us/wordpress/2009/12/verizon-foc-update/</link>
		<comments>http://www.rollernet.us/wordpress/2009/12/verizon-foc-update/#comments</comments>
		<pubDate>Sat, 12 Dec 2009 17:21:57 +0000</pubDate>
		<dc:creator>Roller Network</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[New Facility]]></category>
		<category><![CDATA[Status]]></category>

		<guid isPermaLink="false">http://www.rollernet.us/wordpress/?p=468</guid>
		<description><![CDATA[We were notified on December 10 that the circuit was finally ready to be turned up. However, during the process of assigning point-to-point addresses to the link, we discovered that it was out of Sacramento, CA. That means it was provisioned incorrectly yet again, just like back in September.
]]></description>
			<content:encoded><![CDATA[<p>We were notified on December 10 that the circuit was finally ready to be turned up. However, during the process of assigning point-to-point addresses to the link, we discovered that it was out of Sacramento, CA. That means it was provisioned incorrectly yet again, <a href="http://www.rollernet.us/wordpress/2009/09/verizon-delay/">just like back in September</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rollernet.us/wordpress/2009/12/verizon-foc-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Verizon FOC Passed</title>
		<link>http://www.rollernet.us/wordpress/2009/12/verizon-foc-passed/</link>
		<comments>http://www.rollernet.us/wordpress/2009/12/verizon-foc-passed/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 02:06:52 +0000</pubDate>
		<dc:creator>Roller Network</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[New Facility]]></category>
		<category><![CDATA[Status]]></category>

		<guid isPermaLink="false">http://www.rollernet.us/wordpress/?p=453</guid>
		<description><![CDATA[The Verizon FOC date (as previously mentioned) passed without any changes. We&#8217;ve requested an update.
[Dec. 9] The status lights on the port lit up today.
]]></description>
			<content:encoded><![CDATA[<p>The Verizon FOC date (as <a href="http://www.rollernet.us/wordpress/2009/12/verizon-soon/">previously mentioned</a>) passed without any changes. We&#8217;ve requested an update.</p>
<p>[Dec. 9] The status lights on the port lit up today.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rollernet.us/wordpress/2009/12/verizon-foc-passed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Verizon Soon?</title>
		<link>http://www.rollernet.us/wordpress/2009/12/verizon-soon/</link>
		<comments>http://www.rollernet.us/wordpress/2009/12/verizon-soon/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 03:19:18 +0000</pubDate>
		<dc:creator>Roller Network</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[New Facility]]></category>
		<category><![CDATA[Status]]></category>

		<guid isPermaLink="false">http://www.rollernet.us/wordpress/?p=436</guid>
		<description><![CDATA[It&#8217;s been a while since our last Verizon update, but today we received word that they have given us a Firm Order Commitment (FOC) of 12/4/2009 for the corrections that needed to be made. Since that&#8217;s a Friday, it means they probably will get started next week at the earliest, not that it will be [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s been a while since our last Verizon update, but today we received word that they have given us a Firm Order Commitment (FOC) of 12/4/2009 for the corrections that needed to be made. Since that&#8217;s a Friday, it means they probably will get started next week at the earliest, not that it will be ready to put into production. We&#8217;re not entirely sure what exactly they&#8217;re delivering since someone was already out on November 13 to test and qualify a new port on the existing install.</p>
<p>Unfortunately this snafu has caused massive delays in being able to accept additional colocation and hosting customers due to a lack of redundancy and bandwidth. We&#8217;re trying to push the resolution forward as best we can, and we appreciate your patience.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rollernet.us/wordpress/2009/12/verizon-soon/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Outbound Mail Now IPv6 Enabled</title>
		<link>http://www.rollernet.us/wordpress/2009/11/outbound-mail-now-ipv6-enabled/</link>
		<comments>http://www.rollernet.us/wordpress/2009/11/outbound-mail-now-ipv6-enabled/#comments</comments>
		<pubDate>Fri, 06 Nov 2009 21:50:25 +0000</pubDate>
		<dc:creator>Roller Network</dc:creator>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[IPv6]]></category>

		<guid isPermaLink="false">http://www.rollernet.us/wordpress/?p=396</guid>
		<description><![CDATA[We recently enabled IPv6 in Postfix on our outgoing mail (SMTP AUTH, smarthost) service. This means that if a destination you&#8217;re sending mail to is accessible via IPv6 it will automatically connect and deliver using IPv6. If not, it will transparently fall back to IPv4 and continue to deliver as before.
]]></description>
			<content:encoded><![CDATA[<p>We recently enabled IPv6 in Postfix on our outgoing mail (SMTP AUTH, smarthost) service. This means that if a destination you&#8217;re sending mail to is accessible via IPv6 it will automatically connect and deliver using IPv6. If not, it will transparently fall back to IPv4 and continue to deliver as before.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rollernet.us/wordpress/2009/11/outbound-mail-now-ipv6-enabled/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Verizon Update: Contact!</title>
		<link>http://www.rollernet.us/wordpress/2009/11/verizon-update-contact/</link>
		<comments>http://www.rollernet.us/wordpress/2009/11/verizon-update-contact/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 21:05:34 +0000</pubDate>
		<dc:creator>Roller Network</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[New Facility]]></category>

		<guid isPermaLink="false">http://www.rollernet.us/wordpress/?p=370</guid>
		<description><![CDATA[We finally have a Verizon account manager for the first time since we last heard from our original account manager on August 3. While the IPv6 issues are not resolved, we&#8217;re trying to put a rush on the fixes we needed to be made back in August so we can at least have some basic [...]]]></description>
			<content:encoded><![CDATA[<p>We finally have a Verizon account manager for the first time since we last heard from our original account manager on August 3. While the IPv6 issues are not resolved, we&#8217;re trying to put a rush on the fixes we needed to be made back in August so we can at least have some basic connectivity while Verizon performs an engineering assessment with regards to IPv6. To replace the circuit would take another 3 to 6 months to get new fiber brought in, so we&#8217;re going to stick with it and see what the results of the engineering assessment are.</p>
<p>The fiber we have is Verizon-provided but our ILEC is AT&amp;T which means that nobody but Verizon can use it. Back in the 90&#8217;s a company called Brooks Fiber installed a whole bunch of fiber in Reno. They were bought by MCI and MCI/UUNet eventually became Verizon Business. While we are technically in a lit building because it already had a fiber on the property, it&#8217;s a light industrial park and there was no equipment that could carry our order and a new OC-12 was installed to our telco room.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rollernet.us/wordpress/2009/11/verizon-update-contact/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Verizon Update: No Contact Yet</title>
		<link>http://www.rollernet.us/wordpress/2009/10/verizon-update-no-contact-yet/</link>
		<comments>http://www.rollernet.us/wordpress/2009/10/verizon-update-no-contact-yet/#comments</comments>
		<pubDate>Fri, 09 Oct 2009 03:42:29 +0000</pubDate>
		<dc:creator>Roller Network</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[New Facility]]></category>
		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.rollernet.us/wordpress/?p=321</guid>
		<description><![CDATA[We had a promising conference call with Verizon on Tuesday and a couple emails from Verizon representatives (who deferred to our assigned account team, whoever that may be, we don&#8217;t know), but unfortunately nobody who can officially help has yet to contact us as promised and no further progress has been made as of this [...]]]></description>
			<content:encoded><![CDATA[<p>We had a promising conference call with Verizon on Tuesday and a couple emails from Verizon representatives (who deferred to our assigned account team, whoever that may be, we don&#8217;t know), but unfortunately nobody who can officially help has yet to contact us as promised and no further progress has been made as of this post.</p>
<p>For us this is merely a continuation of the same problem we had in August/September when our original account manager disappeared.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rollernet.us/wordpress/2009/10/verizon-update-no-contact-yet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
