RFC 5342: IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7042.
Current document in this lineage: RFC 9542 — IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters
In plain English — editorial summary, not part of the RFC
Some IETF protocols make use of Ethernet frame formats and IEEE 802 parameters. This document discusses some use of such parameters in IETF protocols and specifies IANA considerations for allocation of code points under the IANA OUI (Organizationally Unique Identifier). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5342
- Published
- September 2008
- Authors
- D. Eastlake 3rd
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 21
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 5342 (2008)
- RFC 7042 (2013)
- RFC 9542 (2024) ✓
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9542IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 ParametersCurrent
April 2024
- RFC 5171Cisco Systems UniDirectional Link Detection (UDLD) ProtocolCurrent
April 2008
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 7043Resource Records for EUI-48 and EUI-64 Addresses in the DNSCurrent
October 2013
- RFC 3638Applicability Statement for Reclassification of RFC 1643 to Historic StatusCurrent
October 2003
- RFC 7448MIB Transfer from the IETF to the IEEE 802.3 WGCurrent
February 2015
- RFC 7973Assignment of an Ethertype for IPv6 with Low-Power Wireless Personal Area Network (LoWPAN) EncapsulationCurrent
November 2016
- RFC 8381Transparent Interconnection of Lots of Links (TRILL): Vendor-Specific RBridge Channel ProtocolCurrent
May 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?