<?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: Identifying Ethernet Header Types</title>
	<atom:link href="http://bradhedlund.com/2007/11/19/identifying-ethernet-header-types/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradhedlund.com/2007/11/19/identifying-ethernet-header-types/</link>
	<description>Studies in Data Center Networking, Virtualization, Computing</description>
	<lastBuildDate>Sat, 04 Feb 2012 19:38:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: owlman</title>
		<link>http://bradhedlund.com/2007/11/19/identifying-ethernet-header-types/comment-page-1/#comment-3026</link>
		<dc:creator>owlman</dc:creator>
		<pubDate>Fri, 12 Nov 2010 08:26:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradhedlund.com/articles/5/identifying-ethernet-header-types/#comment-3026</guid>
		<description>Ethernet is a type of self-clocking synchronous serial communication. On the wire, the Ethernet signal has an embedded clock, so the hardware knows exactly when the first and last bits arrive (because no clock information means no data). It simply has to count the bits, then divide by 8 to get the byte count of the frame.

http://en.wikipedia.org/wiki/Manchester_code

I think 35 years ago when they invented Ethernet it was quite expensive hardware-wise to count the bits, so they included the length in the frame for easier processing...</description>
		<content:encoded><![CDATA[<p>Ethernet is a type of self-clocking synchronous serial communication. On the wire, the Ethernet signal has an embedded clock, so the hardware knows exactly when the first and last bits arrive (because no clock information means no data). It simply has to count the bits, then divide by 8 to get the byte count of the frame.</p>
<p><a href="http://en.wikipedia.org/wiki/Manchester_code" rel="nofollow">http://en.wikipedia.org/wiki/Manchester_code</a></p>
<p>I think 35 years ago when they invented Ethernet it was quite expensive hardware-wise to count the bits, so they included the length in the frame for easier processing&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas B.</title>
		<link>http://bradhedlund.com/2007/11/19/identifying-ethernet-header-types/comment-page-1/#comment-2765</link>
		<dc:creator>Thomas B.</dc:creator>
		<pubDate>Mon, 01 Nov 2010 18:08:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradhedlund.com/articles/5/identifying-ethernet-header-types/#comment-2765</guid>
		<description>This is probably obvious to everyone else, but I can&#039;t seem to figure it out. If Type/Length indicates a Type, how do you determine the Length? Do you just look for an interframe gap or something?</description>
		<content:encoded><![CDATA[<p>This is probably obvious to everyone else, but I can&#8217;t seem to figure it out. If Type/Length indicates a Type, how do you determine the Length? Do you just look for an interframe gap or something?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Internetwork Expert .org &#187; Identifying Ethernet Multicast</title>
		<link>http://bradhedlund.com/2007/11/19/identifying-ethernet-header-types/comment-page-1/#comment-2</link>
		<dc:creator>Internetwork Expert .org &#187; Identifying Ethernet Multicast</dc:creator>
		<pubDate>Wed, 21 Nov 2007 21:52:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradhedlund.com/articles/5/identifying-ethernet-header-types/#comment-2</guid>
		<description>[...] like there are 3 different Ethernet header formats, there are also 3 different types of Ethernet [...]</description>
		<content:encoded><![CDATA[<p>[...] like there are 3 different Ethernet header formats, there are also 3 different types of Ethernet [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

