RFC 2013
SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2
RFC 2013: SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2 🎀
Network Working Group · Request for Comments: 2013 · November 1996 🌸
Author/Editor: K. McCloghrie, Cisco Systems 💜 Category: Standards Track ✨ Updates: RFC 1213 🦋 (it doesn't list anything it obsoletes)
Status of This Memo
okay so this doc is an Internet standards track protocol for the Internet community, and it's literally asking for discussion and suggestions for improvements 🫶 For the standardization state and status of this protocol, go check the current edition of the "Internet Official Protocol Standards" (STD 1). Distribution of this memo is unlimited, so share it with everyone 💅
IESG Note
ngl this part is important 😭 The IP, UDP, and TCP MIB modules currently only support IPv4. They use the IpAddress type, which is an OCTET STRING of length 4 to represent the 32-bit IPv4 internet addresses. (See RFC 1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6 internet addresses, so no IPv6 slay here yet 🙈
Table of Contents 📚
1. Introduction ................................................. 1
2. Definitions .................................................. 2
2.1 The UDP Group ............................................... 3
2.2 Conformance Information ..................................... 5
2.2.1 Compliance Statements ..................................... 5
2.2.2 Units of Conformance ...................................... 5
3. Acknowledgements ............................................. 6
4. References ................................................... 6
5. Security Considerations ...................................... 6
6. Editor's Address ............................................. 61. Introduction ✨
okay so picture a management system. It has several (potentially many) nodes, and each one has a processing entity called an agent, which can access management instrumentation 🧚 There's also at least one management station, plus a management protocol that carries management information between the agents and the stations. The operations of that protocol run under an administrative framework that defines authentication, authorization, access control, and privacy policies. very organized, very iconic 👑
Management stations run management applications that monitor and control managed elements. Managed elements are devices like hosts, routers, terminal servers, and so on, which get monitored and controlled through access to their management information 💖
All that management information is seen as a collection of managed objects, living in a virtual information store called the Management Information Base (MIB). Related objects get grouped into MIB modules. These modules are written in a subset of OSI's Abstract Syntax Notation One (ASN.1) [1], and that subset is called the Structure of Management Information (SMI) [2] 🎀
This document is the MIB module that defines managed objects for managing implementations of the User Datagram Protocol (UDP) [3] 🦋
The managed objects in this MIB module were first defined under the SNMPv1 framework as part of MIB-II [4]. This document defines those same objects for UDP, but this time using the SNMPv2 framework. same objects, new era 💅
2. Definitions 📖
UDP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32,
IpAddress, mib-2 FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
udpMIB MODULE-IDENTITY
LAST-UPDATED "9411010000Z"
ORGANIZATION "IETF SNMPv2 Working Group"
CONTACT-INFO
" Keith McCloghrie
Postal: Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
US
Phone: +1 408 526 5260
Email: kzm@cisco.com"
DESCRIPTION
"The MIB module for managing UDP implementations."
REVISION "9103310000Z"
DESCRIPTION
"The initial revision of this MIB module was part of MIB-
II."
::= { mib-2 50 }2.1. The UDP Group 🌈
-- the UDP group
udp OBJECT IDENTIFIER ::= { mib-2 7 }
udpInDatagrams OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of UDP datagrams delivered to UDP users."
::= { udp 1 }
udpNoPorts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of received UDP datagrams for which there
was no application at the destination port."
::= { udp 2 }
udpInErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of received UDP datagrams that could not be
delivered for reasons other than the lack of an application
at the destination port."
::= { udp 3 }
udpOutDatagrams OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of UDP datagrams sent from this entity."
::= { udp 4 }
-- the UDP Listener table
-- The UDP listener table contains information about this
-- entity's UDP end-points on which a local application is
-- currently accepting datagrams.
udpTable OBJECT-TYPE
SYNTAX SEQUENCE OF UdpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing UDP listener information."
::= { udp 5 }
udpEntry OBJECT-TYPE
SYNTAX UdpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular current UDP listener."
INDEX { udpLocalAddress, udpLocalPort }
::= { udpTable 1 }
UdpEntry ::= SEQUENCE {
udpLocalAddress IpAddress,
udpLocalPort INTEGER
}
udpLocalAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The local IP address for this UDP listener. In the case of
a UDP listener which is willing to accept datagrams for any
IP interface associated with the node, the value 0.0.0.0 is
used."
::= { udpEntry 1 }
udpLocalPort OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The local port number for this UDP listener."
::= { udpEntry 2 }2.2. Conformance Information 🎯
-- conformance information
udpMIBConformance OBJECT IDENTIFIER ::= { udpMIB 2 }
udpMIBCompliances OBJECT IDENTIFIER ::= { udpMIBConformance 1 }
udpMIBGroups OBJECT IDENTIFIER ::= { udpMIBConformance 2 }2.2.1. Compliance Statements 💖
-- compliance statements
udpMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities which
implement UDP."
MODULE -- this module
MANDATORY-GROUPS { udpGroup
}
::= { udpMIBCompliances 1 }2.2.2. Units of Conformance 🍓
-- units of conformance
udpGroup OBJECT-GROUP
OBJECTS { udpInDatagrams, udpNoPorts,
udpInErrors, udpOutDatagrams,
udpLocalAddress, udpLocalPort }
STATUS current
DESCRIPTION
"The udp group of objects providing for management of UDP
entities."
::= { udpMIBGroups 1 }
END3. Acknowledgements 🫶
This document contains a modified subset of RFC 1213. shoutout to the original 🙌
4. References 📚
- [1] Information processing systems - Open Systems Interconnection Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization. International Standard 8824, (December, 1987).
- [2] McCloghrie, K., Editor, "Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, Cisco Systems, January 1996.
- [3] Postel, J., "User Datagram Protocol", STD 6, RFC 768, USC-ISI, August 1980.
- [4] McCloghrie, K., and Rose, M., "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, March 1991.
5. Security Considerations 💀
Security issues are not discussed in this memo. 😬 so the doc itself doesn't cover security, and that's the whole tea ☕
6. Editor's Address 💌
Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 US
Phone: +1 408 526 5260 EMail: kzm@cisco.com
📦 where this page comes from
- ietf: rfc2013 1996-11
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms