<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Remote Access Design Guidelines – Part 1: Overview</title><link>http://blogs.technet.com/b/rrasblog/archive/2009/03/17/remote-access-design-guidelines-part-1.aspx</link><description>Hello Customers, In last few releases, we have added plenty of “cool” features in RAS – like NAP based health check, SSTP based SSL tunnel, IPv6 support in Vista SP1/WS08 and IKEv2 based IPSec tunnel in Windows 7/WS08 R2. As a result, we have seen a lot</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Remote Access Deployment – Part 1:  Configuring Remote Access Clients</title><link>http://blogs.technet.com/b/rrasblog/archive/2009/03/17/remote-access-design-guidelines-part-1.aspx#3217785</link><pubDate>Wed, 25 Mar 2009 11:11:41 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3217785</guid><dc:creator>Routing and Remote Access Blog</dc:creator><description>&lt;p&gt;Hello Customers, In my last few articles , I discussed about the design guidelines to consider before&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3217785" width="1" height="1"&gt;</description></item><item><title>re: Remote Access Design Guidelines – Part 1: Overview and References</title><link>http://blogs.technet.com/b/rrasblog/archive/2009/03/17/remote-access-design-guidelines-part-1.aspx#3214582</link><pubDate>Wed, 18 Mar 2009 13:28:50 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3214582</guid><dc:creator>SamirJ [MSFT]</dc:creator><description>&lt;p&gt;Joe Klein wrote:&lt;/p&gt;
&lt;p&gt;&amp;quot;DHCP relay agent can be IPv4 or IPv6 – depending upon IPv4 or IPv6 protocol is enabled on top of VPN client.&lt;/p&gt;
&lt;p&gt;I think you meant:&lt;/p&gt;
&lt;p&gt;DHCP relay agent and VPN client supports both the IPv4 and Ipv6 transport.&amp;quot;&lt;/p&gt;
&lt;p&gt;SAMIRJ wrote:&lt;/p&gt;
&lt;p&gt;You are right - I will fix the same as it is confusing :). Thanks for pointing that out&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3214582" width="1" height="1"&gt;</description></item><item><title>re: Remote Access Design Guidelines – Part 1: Overview and References</title><link>http://blogs.technet.com/b/rrasblog/archive/2009/03/17/remote-access-design-guidelines-part-1.aspx#3214161</link><pubDate>Tue, 17 Mar 2009 21:12:05 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3214161</guid><dc:creator>Joe Klein</dc:creator><description>&lt;p&gt;You Said:&lt;/p&gt;
&lt;p&gt;DHCP relay agent can be IPv4 or IPv6 – depending upon IPv4 or IPv6 protocol is enabled on top of VPN client.&lt;/p&gt;
&lt;p&gt;I think you meant:&lt;/p&gt;
&lt;p&gt;DHCP relay agent and VPN client supports both the IPv4 and Ipv6 transport. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3214161" width="1" height="1"&gt;</description></item></channel></rss>