RFC 4441: The IEEE 802/IETF Relationship
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7241.
Current version: RFC 7241 — The IEEE 802/IETF Relationship
In plain English — editorial summary, not part of the RFC
Since the late 1980s, IEEE 802 and IETF have cooperated in the development of Simple Network Management Protocol (SNMP) MIBs and Authentication, Authorization, and Accounting (AAA) applications. This document describes the policies and procedures that have developed in order to coordinate between the two organizations, as well as some of the relationship history. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4441
- Published
- March 2006
- Authors
- B. Aboba
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 22
- Also known as
- —
- Obsoleted by:
- RFC 7241
Topics
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 3539Authentication, Authorization and Accounting (AAA) Transport ProfileCurrent
June 2003
- RFC 3169Criteria for Evaluating Network Access Server ProtocolsCurrent
September 2001
- RFC 2903Generic AAA ArchitectureCurrent
August 2000
- RFC 7155Diameter Network Access Server ApplicationCurrent
April 2014
- RFC 7423Diameter Applications Design GuidelinesCurrent
November 2014
- RFC 9950A YANG Data Model for Terminal Access Controller Access-Control System Plus (TACACS+)Current
March 2026
- RFC 3141CDMA2000 Wireless Data Requirements for AAACurrent
June 2001
- RFC 5779Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter ServerCurrent
February 2010
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?