09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

service enhancement or replacement without affecting <strong>the</strong> communication process<br />

as a whole. To this end, <strong>the</strong> IEEE's standards development focuses on distinct<br />

functional categories. These categories are as follows:<br />

• General Architecture and Inter<strong>network</strong>ing—This category covers bridging,<br />

switching, Layer 2 addressing, and management. These standards are<br />

developed by <strong>the</strong> 802.1 subcommittee. The majority of <strong>the</strong>se standards<br />

define how OSI-RM Layer 2 transmission pro<strong>to</strong>cols will function in an<br />

operational and implementation way.<br />

• Logical Link Control (LLC)—LLC provides <strong>the</strong> software interface between <strong>the</strong><br />

Layer 2 transmission pro<strong>to</strong>col and <strong>the</strong> Layer 3 <strong>network</strong>ing pro<strong>to</strong>col. The LLC<br />

standard was developed by <strong>the</strong> 802.2 subcommittee. LLC is used by all <strong>the</strong><br />

IEEE standards-based pro<strong>to</strong>cols and several non-IEEE pro<strong>to</strong>cols. It is<br />

classified as part of OSI Layer 2 functionality. Never<strong>the</strong>less, it functions as a<br />

distinct service interface <strong>to</strong> manage <strong>the</strong> actual delivery of data between<br />

end-stations. Data link (<strong>the</strong> term used <strong>to</strong> describe this function with WAN<br />

pro<strong>to</strong>cols) or link control is provided differently, depending on <strong>the</strong><br />

transmission pro<strong>to</strong>col, but <strong>the</strong> service's function is <strong>the</strong> same regardless.<br />

• Media Access Control (MAC)—MAC is responsible for <strong>the</strong> data transmission<br />

frame format, data integrity checking, and managing station access <strong>to</strong> <strong>the</strong><br />

physical transmission medium (for example, collision detection in <strong>the</strong> case of<br />

E<strong>the</strong>rnet). For each MAC pro<strong>to</strong>col <strong>the</strong>re is a separate 802 subcommittee.<br />

Currently eight different IEEE subcommittees develop MAC standards for<br />

physical media and wireless communication. In terms of <strong>the</strong> LAN, <strong>the</strong> 802.3<br />

subcommittee develops standards for E<strong>the</strong>rnet, and 802.5 develops<br />

standards for Token Ring. The MAC subcommittee standards encompass<br />

both OSI-RM Layers 1 and 2 functionality. The MAC service interface resides<br />

in Layer 2, and <strong>the</strong> PHY service interface—which defines <strong>the</strong> signaling and<br />

encoding used <strong>to</strong> transmit <strong>the</strong> MAC interface frames—resides at Layer 1. The<br />

MAC pro<strong>to</strong>col is often used <strong>to</strong> generalize <strong>the</strong> Layer 2 function because it<br />

represents for <strong>the</strong> most part <strong>the</strong> common denomina<strong>to</strong>r between <strong>the</strong> PHY and<br />

LLC service layers of <strong>the</strong> data transmission function.<br />

• Security—All security issues and standards dealing with <strong>the</strong> 802.x standards<br />

are developed by <strong>the</strong> 802.10 subcommittee.<br />

The development and implementation of standards-based technologies assures<br />

compatibility between <strong>network</strong>ing products manufactured by different product<br />

vendors. The standards development process is a collaborative effort between <strong>the</strong><br />

IEEE, <strong>network</strong>ing product vendors, and o<strong>the</strong>r interested parties. Actually, quite<br />

often, vendors develop proprietary implementations of technologies and <strong>the</strong>n offer<br />

<strong>the</strong>m as a standard or as an addition <strong>to</strong> <strong>the</strong> existing standard. When a new<br />

technology is developed, a new IEEE subcommittee is formed <strong>to</strong> codify a standard.<br />

In <strong>the</strong> event that an innovation is made <strong>to</strong> an existing IEEE standard, it is handled<br />

as a subcommittee's supplemental project. Each supplement is assigned a one- or<br />

two-letter designa<strong>to</strong>r. For example, <strong>the</strong> IEEE standard for 100Mbps Fast E<strong>the</strong>rnet is

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!