<?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: Facebook Now Available Over IPv6 (Two Weeks Early)</title>
	<atom:link href="http://www.internetsociety.org/deploy360/blog/2012/05/facebook-now-available-over-ipv6-two-weeks-early/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.internetsociety.org/deploy360/blog/2012/05/facebook-now-available-over-ipv6-two-weeks-early/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=facebook-now-available-over-ipv6-two-weeks-early</link>
	<description>Providing real-world deployment info for IPv6, DNSSEC and more...</description>
	<lastBuildDate>Thu, 06 Jun 2013 13:21:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Roland</title>
		<link>http://www.internetsociety.org/deploy360/blog/2012/05/facebook-now-available-over-ipv6-two-weeks-early/#comment-693</link>
		<dc:creator>Roland</dc:creator>
		<pubDate>Wed, 23 May 2012 00:32:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.internetsociety.org/deploy360/?p=12675#comment-693</guid>
		<description><![CDATA[Couldn&#039;t make a request to :443 via the 6-to-4 Gateway my ISP provides for the PPPoE/DHCPv6-unable customers.

Using the nativ IPv6 connection my servers have in the datacenter I was able to request https://www.facebook.com/ and actually getting  a response.

So I think FB doesn&#039;t want to have traffic through (unreliable) 6-to-4 gateways and makes the browser to fallback to IPv4. 

Anyhow, just a wild guess...]]></description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t make a request to :443 via the 6-to-4 Gateway my ISP provides for the PPPoE/DHCPv6-unable customers.</p>
<p>Using the nativ IPv6 connection my servers have in the datacenter I was able to request <a href="https://www.facebook.com/" rel="nofollow">https://www.facebook.com/</a> and actually getting  a response.</p>
<p>So I think FB doesn&#8217;t want to have traffic through (unreliable) 6-to-4 gateways and makes the browser to fallback to IPv4. </p>
<p>Anyhow, just a wild guess&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason T</title>
		<link>http://www.internetsociety.org/deploy360/blog/2012/05/facebook-now-available-over-ipv6-two-weeks-early/#comment-692</link>
		<dc:creator>Jason T</dc:creator>
		<pubDate>Tue, 22 May 2012 22:49:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.internetsociety.org/deploy360/?p=12675#comment-692</guid>
		<description><![CDATA[The commenter on hacker news is incorrect, they are being redirected because the host doesn&#039;t match. Just the fact that it returns a redirect means its being hosted over ipv6. 
This works:
curl -g -H &quot;Host:www.facebook.com&quot; -H &quot;User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.46 Safari/536.5&quot; &quot;http://[2a03:2880:10:1f02:face:b00c::25]&quot;]]></description>
		<content:encoded><![CDATA[<p>The commenter on hacker news is incorrect, they are being redirected because the host doesn&#8217;t match. Just the fact that it returns a redirect means its being hosted over ipv6.<br />
This works:<br />
curl -g -H &#8220;Host:www.facebook.com&#8221; -H &#8220;User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.46 Safari/536.5&#8243; &#8220;http://[2a03:2880:10:1f02:face:b00c::25]&#8220;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan York</title>
		<link>http://www.internetsociety.org/deploy360/blog/2012/05/facebook-now-available-over-ipv6-two-weeks-early/#comment-689</link>
		<dc:creator>Dan York</dc:creator>
		<pubDate>Tue, 22 May 2012 17:54:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.internetsociety.org/deploy360/?p=12675#comment-689</guid>
		<description><![CDATA[Yes, I noticed that, too... and perhaps that&#039;s yet another sign that their full IPv6 support is still underway.]]></description>
		<content:encoded><![CDATA[<p>Yes, I noticed that, too&#8230; and perhaps that&#8217;s yet another sign that their full IPv6 support is still underway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sgucukoglu</title>
		<link>http://www.internetsociety.org/deploy360/blog/2012/05/facebook-now-available-over-ipv6-two-weeks-early/#comment-688</link>
		<dc:creator>sgucukoglu</dc:creator>
		<pubDate>Tue, 22 May 2012 17:46:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.internetsociety.org/deploy360/?p=12675#comment-688</guid>
		<description><![CDATA[Curiously, although www.facebook.com is IPv6-enabled, facebook.com is not.]]></description>
		<content:encoded><![CDATA[<p>Curiously, although <a href="http://www.facebook.com" rel="nofollow">http://www.facebook.com</a> is IPv6-enabled, facebook.com is not.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
