RFC 4113: Management Information Base for the User Datagram Protocol (UDP)
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for implementations of the User Datagram Protocol (UDP) in an IP version independent manner. This memo obsoletes RFCs 2013 and 2454. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4113
- Published
- June 2005
- Authors
- B. Fenner; J. Flick
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 11 RFCs, each formally replacing the one before it.
- RFC 2011 (1996)
- RFC 2012 (1996)
- RFC 2013 (1996)
- RFC 2452 (1998)
- RFC 2454 (1998)
- RFC 2465 (1998)
- RFC 2466 (1998)
- RFC 4022 (2005)
- RFC 4113 (2005)
- RFC 4293 (2006)
- RFC 8096 (2017) ✓
Read the full history of The IPv6-Specific MIB Modules Are Obsolete →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2584Definitions of Managed Objects for APPN/HPR in IP NetworksCurrent
May 1999
- RFC 3019IP Version 6 Management Information Base for The Multicast Listener Discovery ProtocolObsoleted
January 2001
- RFC 3498Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) ArchitecturesCurrent
March 2003
- RFC 2932IPv4 Multicast Routing MIBObsoleted
October 2000
- RFC 4087IP Tunnel MIBCurrent
June 2005
- RFC 4292IP Forwarding Table MIBCurrent
April 2006
- RFC 4293Management Information Base for the Internet Protocol (IP)Current
April 2006
- RFC 3678Socket Interface Extensions for Multicast Source FiltersCurrent
January 2004
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?