<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Your guide to the basics of computer networking &#187; Ethernet</title>
	<atom:link href="http://www.networkguruz.com/category/ethernet/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.networkguruz.com</link>
	<description></description>
	<lastBuildDate>Sat, 21 Feb 2009 10:39:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Media Access in Ethernet</title>
		<link>http://www.networkguruz.com/ethernet/media-access-in-ethernet/</link>
		<comments>http://www.networkguruz.com/ethernet/media-access-in-ethernet/#comments</comments>
		<pubDate>Mon, 02 Jun 2008 16:11:00 +0000</pubDate>
		<dc:creator>Raj</dc:creator>
				<category><![CDATA[Ethernet]]></category>

		<guid isPermaLink="false">http://www.networkguruz.com/?p=18</guid>
		<description><![CDATA[What is CSMA/CD?
CSMA/CD is a modified version of CSMA.
A scheme known as carrier sense multiple access with collision detection (CSMA/CD) governs the way the computers share the channel. This scheme is relatively simple compared to the token ring. When one computer on the network wants to send some data to another computer, the following algorithm [...]]]></description>
			<content:encoded><![CDATA[<h2>What is CSMA/CD?</h2>
<p>CSMA/CD is a modified version of <span style="text-decoration: underline;">CSMA.</span></p>
<p>A scheme known as <span style="text-decoration: underline;"><em>carrier sense multiple access with collision detection</em> (CSMA/CD)</span> governs the way the computers share the channel. This scheme is relatively simple compared to the token ring. When one computer on the network wants to send some data to another computer, the following algorithm is followed:</p>
<ol>
<li><strong>Start</strong> &#8211; If the wire (also referred as ethernet cable) is idle, start transmitting, else go to step 4.</li>
<li><strong>Transmitting</strong> &#8211; If detecting a <strong>collision</strong>, continue transmitting until the minimum packet time is reached (to ensure that all other transmitters and receivers detect the collision) then go to step 4.</li>
<li><strong>End successful transmission</strong> &#8211; Report success to higher network layers; exit transmit mode.</li>
<li><strong>Wire is busy</strong> &#8211; Wait until wire becomes idle &#8211; This will go back to step 1 and the loop continues until the wire is idle for data transmission.</li>
<li><strong>Wire just became idle</strong> &#8211; Wait a random time, then go to step 1, unless maximum number of transmission attempts has been exceeded.</li>
<li><strong>Maximum number of transmission attempt exceeded</strong> &#8211; Report failure to higher network layers; exit transmit mode.</li>
</ol>
<p><strong>Ethernet</strong> originally used a shared <span style="text-decoration: underline;">coaxial cable</span> to connect every machine on the network. Computers were connected to an <span style="text-decoration: underline;">Attachment Unit Interface</span> (AUI) transceiver, which in turn was connected to the cable. While a simple passive wire was highly reliable for small Ethernets, it was not reliable for large extended networks, where damage to the wire in a single place, or a single bad connector could make the whole Ethernet segment unusable. This presented a single point of failure at multiple locations.</p>
<p>Since all communications happen on the same wire, any information sent by one computer is received by all, even if that information was intended for just one destination. The network interface card filters out information not addressed to it, interrupting the CPU only when applicable packets are received unless the card is put into &#8220;<span style="text-decoration: underline;">promiscuous mode</span>&#8220;. This &#8220;one speaks, all listen&#8221; property is a security weakness of shared-medium Ethernet, since a node on an Ethernet network can eavesdrop on all traffic on the wire if it so chooses. Use of a single cable also means that the bandwidth is shared, so that network traffic can slow to a crawl when, for example, the network and nodes restart after a power failure.</p>
<p><strong>Note: Collision</strong> is an event that occurs when data is simultaneously transmitted over the same wire by two computers. <strong>Collision is very common on ethernet and should not be considered a problem.</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.networkguruz.com/ethernet/media-access-in-ethernet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ethernet frame types and the Ether Type field</title>
		<link>http://www.networkguruz.com/ethernet/ethernet-frame-types-and-the-ether-type-field/</link>
		<comments>http://www.networkguruz.com/ethernet/ethernet-frame-types-and-the-ether-type-field/#comments</comments>
		<pubDate>Sun, 01 Jun 2008 03:17:29 +0000</pubDate>
		<dc:creator>Raj</dc:creator>
				<category><![CDATA[Ethernet]]></category>
		<category><![CDATA[ethernet frame]]></category>
		<category><![CDATA[ethernet frame size]]></category>
		<category><![CDATA[ethernet frame types]]></category>
		<category><![CDATA[ethernet network]]></category>
		<category><![CDATA[gigabit ethernet]]></category>

		<guid isPermaLink="false">http://www.networkguruz.com/?p=13</guid>
		<description><![CDATA[Frames are the format of data packets on the wire.
There are several types of Ethernet frame:

Original Ethernet Version I (no longer used)
The Ethernet Version 2 or Ethernet II frame, the so-called DIX frame (named after DEC, Intel, and Xerox), this is the most common today, as it is often used directly by the Internet Protocol.
Novell&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>Frames are the format of data packets on the wire.</p>
<p>There are several types of Ethernet frame:</p>
<ol>
<li>Original Ethernet Version I (no longer used)</li>
<li>The <strong>Ethernet Version 2</strong> or Ethernet II frame, the so-called <strong>DIX frame</strong> (named after DEC, Intel, and Xerox), this is the most common today, as it is often used directly by the <strong>Internet Protocol</strong>.</li>
<li>Novell&#8217;s homegrown Variation of IEEE 802.3 (&#8220;raw 802.3 frame&#8221;) without LLC</li>
<li>IEEE 802.2 LLC frame</li>
<li>IEEE 802.2 LLC/SNAP frame</li>
</ol>
<p>In addition, Ethernet frames may optionally contain a IEEE 802.1Q tag to identify what VLAN it belongs to and its IEEE 802.1p priority (quality of service). This doubles the potential number of frame types.</p>
<p>The different frame types have different formats and MTU values, but can coexist on the same physical medium.</p>
<p>The original Xerox Version 1 Ethernet had a 16 bit length field, although the maximum length of a packet was 1500 bytes. This length field was soon re-used in Xerox&#8217;s Version 2 Ethernet as a label field, with the convention that values between 0 and 1500 indicated the use of the original Ethernet format, but higher values indicated what became known as an Ether Type, and the use of the new frame format. This is now supported in the IEEE 802 protocols using the SNAP header.</p>
<table border="1" cellspacing="2" align="center">
<tbody>
<tr>
<td><strong>Ether Type</strong></td>
<td>
<p align="center"><strong>Protocol</strong></p>
</td>
</tr>
<tr>
<td>0&#215;0800</td>
<td>IP Internet Protocol (IPv4)</td>
</tr>
<tr>
<td>0&#215;0806</td>
<td>Address Resolution Protocol (ARP)</td>
</tr>
<tr>
<td>0&#215;8035</td>
<td>Reverse Address Resolution Protocol (RARP)</td>
</tr>
<tr>
<td>0&#215;809b</td>
<td>AppleTalk (Ethertalk)</td>
</tr>
<tr>
<td>0&#215;80f3</td>
<td>Appletalk Address Resolution Protocol (AARP)</td>
</tr>
<tr>
<td>0&#215;8100</td>
<td>(identifies IEEE 802.1Q tag)</td>
</tr>
<tr>
<td>0&#215;8137</td>
<td>Novell IPX (alt)</td>
</tr>
<tr>
<td>0&#215;8138</td>
<td>Novell</td>
</tr>
<tr>
<td>0&#215;86DD</td>
<td>Internet Protocol, Version 6 (IPv6)</td>
</tr>
<tr>
<td>0&#215;8847</td>
<td>MPLS unicast</td>
</tr>
<tr>
<td>0&#215;8848</td>
<td>MPLS multicast</td>
</tr>
<tr>
<td>0&#215;8863</td>
<td>PPPoE Discovery Stage</td>
</tr>
<tr>
<td>0&#215;8864</td>
<td>PPPoE Session Stage</td>
</tr>
</tbody>
</table>
<p align="center"><strong><span style="text-decoration: underline;">Type field (EtherType) for some common protocols</span></strong></p>
<p>IEEE 802.2 defined the 16 bit field after the MAC addresses as a length field again. As Ethernet I framing is no longer used, this allows software to determine whether a frame is an Ethernet II frame or an IEEE 802.2 frame, allowing the coexistence of both standards on the same physical medium. All 802.2 frames have a <strong>logical link control</strong> (LLC) header. By examining this header, it is possible to determine whether it is followed by a SNAP (<strong>subnetwork access protocol</strong>) header. (Some protocols, particularly those designed for the OSI networking stack, operate directly on top of 802.2 LLC, which provides both datagram and connection-oriented network services.) The LLC header includes two additional eight-bit address fields (called <strong>service access points</strong> or SAPs in OSI terminology); when both source and destination SAP are set to the value 0xAA, the SNAP service is requested.</p>
<p>Novell&#8217;s &#8220;raw&#8221; 802.3 frame format was based on early IEEE 802.3 work. Novell used this as a starting point to create the first implementation of its own IPX Network Protocol over Ethernet. They did not use any LLC header but started the IPX packet directly after the length field. In principle this is not interoperable with the other later variants of 802.x Ethernet, but since IPX has always FF at the first byte (while LLC has not), this mostly coexists on the wire with other Ethernet implementations (with the notable exception of some early forms of DECnet which got confused by this).</p>
<p>Novell Netware used this frame type by default until the mid nineties, and since Netware was very widespread back then (while IP was not) at some point in time most of the world&#8217;s Ethernet traffic ran over &#8220;raw&#8221; 802.3 carrying IPX. Since Netware 4.10 Netware now defaults to IEEE 802.2 with LLC (Netware Frame Type Ethernet_802.2) when using IPX. There is a classic series of <a href="http://groups.google.com/groups?hl=en&amp;lr=&amp;ie=UTF-8&amp;c2coff=1&amp;frame=right&amp;th=887b61494cf0c72a&amp;seekm=1993Sep17.191208.13580@novell.com#link1" target="_blank">Usenet postings</a><span class="urlexpansion"> </span>by Novell&#8217;s Don Provan that have found their way into numerous FAQ&#8217;s and are widely considered the definitive answer to the Novell Frame Type jungle.</p>
<p>Mac OS uses 802.2/SNAP framing for the AppleTalk protocol suite on Ethernet (&#8220;EtherTalk&#8221;) and Ethernet 2 framing for <a href="Protocols_TCP.html">TCP</a>/IP.</p>
<p>The 802.2 variants of Ethernet are not in widespread use on common networks currently, with the exception of large corporate Netware installations that have not yet migrated to Netware over IP. In the past, many corporate networks supported 802.2 Ethernet to support transparent translating bridges between Ethernet and IEEE 802.5 Token Ring or FDDI networks. The most common framing type used today is Ethernet Version 2, as it is used by most Internet Protocol-based networks, with its EtherType set to <strong>0&#215;0800</strong>.</p>
<p>There exists an <a title="Internet standard" href="http://www.ietf.org/rfc/rfc1042.txt" target="_blank">Internet standard</a><span class="urlexpansion"> ()</span> for encapsulating IP version 4 traffic in IEEE 802.2 frames with LLC/SNAP headers. It is almost never implemented on Ethernet (although it is used on Token Ring and FDDI networks). IP traffic can not be encapsulated in IEEE 802.2 LLC frames without SNAP because, although there is an LLC protocol type for IP, there is no LLC protocol type for ARP. IP Version 6 over Ethernet is also standardized based on IEEE 802.2 with LLC/SNAP.</p>
<p>The IEEE 802.1Q tag, if present, is placed between the Source Address and the EtherType or Length fields. The first two bytes of the tag are the Tag Protocol Identifier (TPID) value of 0&#215;8100. This is located in the same place as the EtherType/Length field in untagged frames, so an EtherType value of 0&#215;8100 means the frame is tagged, and the true EtherType/Length is located after the tag. The TPID is followed by two bytes containing the Tag Control Information (TCI) (the IEEE 802.1p priority (quality of service) and VLAN id). The tag is followed by the rest of the frame, using one of the types described above.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.networkguruz.com/ethernet/ethernet-frame-types-and-the-ether-type-field/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Varieties of Ethernet</title>
		<link>http://www.networkguruz.com/ethernet/varieties-of-ethernet/</link>
		<comments>http://www.networkguruz.com/ethernet/varieties-of-ethernet/#comments</comments>
		<pubDate>Sun, 01 Jun 2008 03:14:34 +0000</pubDate>
		<dc:creator>Raj</dc:creator>
				<category><![CDATA[Ethernet]]></category>

		<guid isPermaLink="false">http://www.networkguruz.com/?p=12</guid>
		<description><![CDATA[The following sections provide a brief summary of all the official ethernet media types. In addition to these official standards, many vendors have implemented proprietary media types for various reasons—often to support longer distances over fiber optic cabling.
Many Ethernet cards and switch ports support multiple speeds, using auto-negotiation to set the speed and duplex for [...]]]></description>
			<content:encoded><![CDATA[<p>The following sections provide a brief summary of all the official ethernet media types. In addition to these official standards, many vendors have implemented proprietary media types for various reasons—often to support longer distances over fiber optic cabling.</p>
<p>Many Ethernet cards and switch ports support multiple speeds, using auto-negotiation to set the speed and duplex for the best values supported by both connected devices. If auto-negotiation fails, a multiple speed device will sense the speed used by its partner, but will assume half-duplex.</p>
<p>A 10/100 Ethernet port supports 10BASE-T and 100BASE-TX and a 10/100/1000 Ethernet port supports 10BASE-T, 100BASE-TX, and 1000BASE-T.</p>
<h2>10 Mbps Ethernet ( 10Mbit/Second)</h2>
<ol>
<li><strong>10BASE5</strong> (also called <strong>Thick wire or Yellow Cable</strong>) &#8212; this is the original 10 Mbit/s implementation of Ethernet. The early IEEE standard uses a single 50-ohm coaxial cable of a type designated RG-8, of <span style="text-decoration: underline;">maximum length 500 meters.</span> Transceivers could be connected by a so-called &#8220;vampire tap&#8221;, which was attached by drilling into the cable to connect to the core and screen, or using N connectors at the end of a cable segment. An AUI cable then connected the transceiver to the Ethernet device. Largely obsolete, though due to its widespread deployment in the early days, some systems may still be in use. It requires precise termination at each end of the cable.</li>
<li><strong>10BASE2</strong> (also called <strong>Thin wire or Cheaper net</strong>) &#8212; 50 ohm RG-58 coaxial cable, of <strong>maximum length 200 meters</strong>, connects machines together, each machine using a T-adaptor to connect to its NIC, which has a BNC connector. Requires termination at each end. For many years this was the dominant 10 Mbit/s Ethernet standard.</li>
<li><strong>Star LAN 10</strong> &#8212; First implementation of Ethernet on twisted pair wiring at 10 Mbit/s. Later evolved into 10BASE-T.</li>
<li><strong>10BASE-T</strong> &#8212; runs over<span style="text-decoration: underline;"> 4 wires (two twisted pairs)</span> on a cat-3 or cat-5 cable up to <strong>100 meters in length</strong>. A hub or switch sits in the middle and has a port for each node.</li>
<li><strong>FOIRL</strong> &#8212; Fiber-optic inter-repeater link. The original standard for ethernet over fibre.</li>
<li><strong>10BASE-F</strong> &#8212; A generic term for the family of 10 Mbit/s ethernet standards <span style="text-decoration: underline;">using fiber optic cable up to 2 kilometers in length</span>: <strong>10BASE-FL</strong>, <strong>10BASE-FB</strong> and <strong>10BASE-FP</strong>. Of these only <span style="text-decoration: underline;">10BASE-FL</span> is in widespread use.</li>
<li><strong>10BASE-FL</strong> &#8212; An updated version of the FOIRL standard.</li>
<li><strong>10BASE-FB</strong> &#8212; Initially intended for backbones connecting a number of hubs or switches, it is now obsolete.</li>
<li><strong>10BASE-FP</strong> &#8212; A passive star network that required no repeater, it was never implemented.</li>
</ol>
<h2>Fast Ethernet (100Mbit/Second)</h2>
<p>Fast Ethernet is a collective term for a number of Ethernet standards that carry traffic at the nominal rate of 100 Mbit/s, against the original Ethernet speed of 10 Mbit/s.<br />
Fast Ethernet is no longer the fastest form of Ethernet: Gigabit Ethernet and the new 10 Gigabit Ethernet standards are 10 and 100 times faster, respectively.</p>
<ol>
<li><strong>100BASE-T</strong> &#8212; A term for any of the three standards for 100 Mbit/s ethernet over twisted pair cable up to 100 meters long. Includes <strong>100BASE-TX</strong>, <strong>100BASE-T4</strong> and <strong>100BASE-T2</strong>. In practical scenarios, the cable can be extended up to 150 meters but it is not advisable.</li>
<li><strong>100BASE-TX</strong> &#8212; Similar star-shaped configuration to <strong>10BASE-T</strong>. It also uses two pairs, but requires <span style="text-decoration: underline;">cat-5</span> cable to achieve 100Mbit/s.</li>
<li><strong>100BASE-T4</strong> &#8212; 100 Mbit/s ethernet over <span style="text-decoration: underline;">cat-3</span> cabling (as used for 10BASE-T installations). Uses all four pairs in the cable. Now <span style="text-decoration: underline;">obsolete</span>, as cat-5 cabling is the norm. Limited to half-duplex.</li>
<li><strong>100BASE-T2</strong> &#8212; No products exist. 100 Mbit/s ethernet over cat-3 cabling. Supports full-duplex, and uses only two pairs. It is functionally equivalent to 100BASE-TX, but supports old cable.</li>
<li><strong>100BASE-FX</strong> &#8212; 100 Mbit/s ethernet over multimode fibre. Maximum length is 400 meters for half-duplex connections (to ensure collisions are detected) or 2 kilometers for full-duplex.</li>
</ol>
<h2>Gigabit Ethernet</h2>
<p>Gigabit Ethernet (GbE) is a term describing various technologies for implementing Ethernet networking at a nominal speed of one gigabit per second.</p>
<p>Gigabit Ethernet is supported over both optical fiber and twisted pair cable. Physical layer standards include 1000BASE-T, 1 Gbit/s over cat-5e copper cabling and 1000BASE-SX for short to medium distances over fiber.</p>
<p>While it is currently deployed in high-capacity backbone network links (for instance, on a high-capacity campus network) its speed is largely not yet required for small network installations. Gigabit Ethernet has begun to penetrate the desktop (as of 2004), shipping standard on Apple&#8217;s Power Mac G5, the notebook (Apple&#8217;s Power Book), and is built into some high-end Pentium and Athlon motherboards. Desktop applications for it include professional video editing.</p>
<p>It is no longer the fastest Ethernet standard, with the ratification of 10 Gigabit Ethernet in 2002</p>
<ol>
<li><strong>1000BASE-T</strong> &#8212; 1 Gbit/s over cat-5e or cat-6 copper cabling.</li>
<li><strong>1000BASE-SX</strong> &#8212; 1 Gbit/s over multi-mode fiber (up to 550 m).</li>
<li><strong>1000BASE-LX</strong> &#8212; 1 Gbit/s over multi-mode fiber (up to 550 m). Optimized for longer distances (up to 10 km) over single-mode fiber.</li>
<li><strong>1000BASE-LH</strong> &#8212; 1 Gbit/s over single-mode fiber (up to 100 km). A long-haul solution.</li>
<li><strong>1000BASE-CX</strong> &#8212; A short-haul solution (up to 25 m) for running 1 Gbit/s Ethernet over special copper cable. Predates <span style="text-decoration: underline;">1000BASE-T</span>, and now obsolete.</li>
</ol>
<h2>10 Gigabit Ethernet</h2>
<p>Ten-gigabit Ethernet (XGbE or 10GbE) is the most recent (as of 2002) and fastest of the Ethernet standards.</p>
<p>IEEE 802.3ae defines a version of Ethernet with a nominal data rate of 10 Gbit/s, ten times faster than gigabit Ethernet.</p>
<p>The new 10 gigabit Ethernet standard encompasses seven different media types for LAN, MAN and WAN. It is currently specified by a supplementary standard, IEEE 802.3ae, and will be incorporated into a future revision of the IEEE 802.3 standard.</p>
<ol>
<li><strong>10GBASE-CX4</strong> &#8212; designed to support short distances over copper cabling, it uses InfiniBand 4x connectors and CX4 cabling and allows a cable length of up to 15 m.</li>
<li><strong>10GBASE-SR</strong> &#8212; designed to support short distances over deployed multi-mode fiber cabling, it has a range of between 26 m and 82 m depending on cable type. It also supports 300 m operation over a new 2000 MHz.km multi-mode fiber.</li>
<li><strong>10GBASE-LX4</strong> &#8212; uses wavelength division multiplexing to support ranges of between 240 m and 300 m over deployed multi-mode cabling. Also supports 10 km over single-mode fiber.</li>
<li><strong>10GBASE-LR</strong> and <strong>10GBASE-ER</strong> &#8212; these standards support 10 km and 40 km respectively over single-mode fiber.</li>
<li><strong>10GBASE-SW</strong>, <strong>10GBASE-LW</strong> and 10GBASE-EW. These varieties use the WAN PHY, designed to inter operate with OC-192 / STM-64 SONET/SDH equipment. They correspond at the physical layer to 10GBASE-SR, 10GBASE-LR and 10GBASE-ER respectively, and hence use the same types of fiber and support the same distances. (There is no WAN PHY standard corresponding to 10GBASE-LX4.)</li>
<li><strong>10GBASE-T</strong> &#8212; Uses unshielded twisted-pair wiring.<span style="text-decoration: underline;">10GBASE-T</span> should be ready by the Northern Hemisphere summer of 2006.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.networkguruz.com/ethernet/varieties-of-ethernet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Introduction to Ethernet</title>
		<link>http://www.networkguruz.com/ethernet/introduction-to-ethernet/</link>
		<comments>http://www.networkguruz.com/ethernet/introduction-to-ethernet/#comments</comments>
		<pubDate>Sun, 01 Jun 2008 03:10:23 +0000</pubDate>
		<dc:creator>Raj</dc:creator>
				<category><![CDATA[Ethernet]]></category>

		<guid isPermaLink="false">http://www.networkguruz.com/?p=9</guid>
		<description><![CDATA[Ethernet is a frame based technology which defines wiring and signaling for the physical layer, and frame formats and protocols for the MAC (Media Access Control, data link layer). Ethernet is mostly standardized as IEEE&#8217;s 802.3.
Ethernet, by far is the most widely used LAN standard. Every peer node on the network connected using ethernet has [...]]]></description>
			<content:encoded><![CDATA[<p>Ethernet is a frame based technology which defines wiring and signaling for the physical layer, and frame formats and protocols for the MAC (Media Access Control, data link layer). Ethernet is mostly standardized as IEEE&#8217;s 802.3.</p>
<p>Ethernet, by far is the most widely used LAN standard. Every peer node on the network connected using ethernet has a 48-bit unique MAC address such that each system on the network can be distinguished.</p>
<h2>History of Ethernet</h2>
<p>Ethernet was originally developed as one of the many pioneering projects at Xerox PARC. The standard was first published on September 30, 1980. It competed with two largely proprietary systems, token ring and ARCNET, but those soon found themselves buried under a tidal wave of Ethernet products. In the process, 3Com became a major company.</p>
<p>The characteristics of typical traffic on actual networks differ from what had been expected before LAN&#8217;s became common in ways that favor the simple design of Ethernet. Metcalfe and Saltzer worked on the same floor at MIT&#8217;s Project MAC while Metcalfe was doing his Harvard dissertation, in which he worked out the theoretical foundations of Ethernet.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.networkguruz.com/ethernet/introduction-to-ethernet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
