<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - Hyper-V Extensible Switch, Part III – The Ins and Outs of the Data Path for Capture and Filter Extensions</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/posts/Hyper-V-Extensible-Switch-Part-III--The-Ins-and-Outs-of-the-Data-Path-for-Capture-and-Filter-Extensi/rss"></atom:link>
	<image>
		<url>http://media.ch9.ms/ch9/361d/7f54bc63-efd3-4182-979e-e377984a361d/HyperVExtensibleSwitch03_100.jpg</url>
		<title>Channel 9 - Hyper-V Extensible Switch, Part III – The Ins and Outs of the Data Path for Capture and Filter Extensions</title>
		<link></link>
	</image>
	<description>This is the third in a series on the Windows Server 2012 Hyper-V Extensible Switch.&amp;nbsp;These are for architects, software engineers and developers who are designing and building extensions to the Hyper-V Extensible Switch. In this video, Microsoft software design engineer Claire Mitchell focuses on how extensions handle data flowing through extensions, specifically for extension types Capture and Filter.&amp;nbsp;The viewer will learn about the Hyper-V Extensible Switch ingress and egress paths, along with the basic switch specific NDIS information and structures. Previous - Understanding the Control Path Next - Writing a Forwarding Extension (to be published...) </description>
	<link></link>
	<language>en</language>
	<pubDate>Thu, 20 Jun 2013 10:46:05 GMT</pubDate>
	<lastBuildDate>Thu, 20 Jun 2013 10:46:05 GMT</lastBuildDate>
	<generator>Rev9</generator>
</channel>
</rss>