RFC 4663: Transferring MIB Work from IETF Bridge MIB WG to IEEE 802.1 WG
In plain English — editorial summary, not part of the RFC
This document describes the plan to transition responsibility for bridging-related MIB modules from the IETF Bridge MIB Working Group to the IEEE 802.1 Working Group, which develops the bridging technology the MIB modules are designed to manage. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4663
- Published
- September 2006
- Authors
- D. Harrington
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4668RADIUS Authentication Client MIB for IPv6Current
August 2006
- RFC 4669RADIUS Authentication Server MIB for IPv6Current
August 2006
- RFC 4670RADIUS Accounting Client MIB for IPv6Current
August 2006
- RFC 4671RADIUS Accounting Server MIB for IPv6Current
August 2006
- RFC 4672RADIUS Dynamic Authorization Client MIBCurrent
September 2006
- RFC 4673RADIUS Dynamic Authorization Server MIBCurrent
September 2006
- RFC 4626MIB for Fibre Channel's Fabric Shortest Path First (FSPF) ProtocolCurrent
September 2006
- RFC 4625Fibre Channel Routing Information MIBCurrent
September 2006
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?