<?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>Wed, 16 May 2012 06:59:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: naxidavid</title>
		<link>http://bradhedlund.com/2007/11/19/identifying-ethernet-header-types/comment-page-1/#comment-8727</link>
		<dc:creator>naxidavid</dc:creator>
		<pubDate>Thu, 16 Feb 2012 09:12:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradhedlund.com/articles/5/identifying-ethernet-header-types/#comment-8727</guid>
		<description>In order to allow some packets using Ethernet v2 framing and some packets using the original version of 802.3 framing to be used on the same Ethernet segment, EtherType values must be greater than or equal to 1536 (0x0600). That value was chosen because the maximum length of the payload field of an Ethernet 802.3 frame is 1500 octets (0x05DC). Thus if the field&#039;s value is greater than or equal to 1536, the frame must be an Ethernet v2 frame, with that field being a type field.[3] If it&#039;s less than or equal to 1500, it must be an IEEE 802.3 frame, with that field being a length field. Values between 1500 and 1536, exclusive, are undefined.[4] This convention allows software to determine whether a frame is an Ethernet II frame or an IEEE 802.3 frame, allowing the coexistence of both standards on the same physical medium.
http://en.wikipedia.org/wiki/Ethernet_frame#Ethernet_frame_types</description>
		<content:encoded><![CDATA[<p>In order to allow some packets using Ethernet v2 framing and some packets using the original version of 802.3 framing to be used on the same Ethernet segment, EtherType values must be greater than or equal to 1536 (0&#215;0600). That value was chosen because the maximum length of the payload field of an Ethernet 802.3 frame is 1500 octets (0x05DC). Thus if the field&#8217;s value is greater than or equal to 1536, the frame must be an Ethernet v2 frame, with that field being a type field.[3] If it&#8217;s less than or equal to 1500, it must be an IEEE 802.3 frame, with that field being a length field. Values between 1500 and 1536, exclusive, are undefined.[4] This convention allows software to determine whether a frame is an Ethernet II frame or an IEEE 802.3 frame, allowing the coexistence of both standards on the same physical medium.<br />
<a href="http://en.wikipedia.org/wiki/Ethernet_frame#Ethernet_frame_types" rel="nofollow">http://en.wikipedia.org/wiki/Ethernet_frame#Ethernet_frame_types</a></p>
]]></content:encoded>
	</item>
	<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>

