By Topic

802a-2003  -  IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture - Amendment 1: Ethertypes for Prototype and Vendor-Specific Protocol Development

StatusInactive  -  Superseded

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$49.0 $44.0
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

IEEE Std 802-2001, IEEE Local and Metropolitan Area Networks: Overview and Architecture, provides an overview to the family of IEEE 802 Standards. This amendment to IEEE Std 802 identifies a set of Ethertypes that may be used for prototype and vendor specific use, and defines how the ethertypes should be used. The "IEEE Get Program" grants public access to view and download individual PDFs of select standards at no charge. Visit http://standards.ieee.org/about/get/index.html for details.

Scope
Provision of a small number of Ethernet type values for prototype and experimental use. Provision of a mechanism for vendor assignment of protocol identifiers for use with proprietary protocols.
Purpose
The existing Ethernet Type number space is a finite resource. In order to develop protocols that will use an Ethernet Type value as a protocol identifier, it is necessary for vendors to apply for type values from this limited number space, both for development purposes and for assignment to the final protocol. This can lead to wastage of the number space for no useful purpose. This amendment to IEEE Standard 802 will allow prototype and experimental protocols to be developed without consuming type values, and will also provide a means whereby protocol developers can assign permanent protocol identifier values without consuming type values.