MIB for the UDP-Lite protocol
Extracted elements (24)
All non-error counters in the UDP-Lite MIB use 64-bit (Counter64) instead of the 32-bit counters used in the UDP MIB. This choice is justified by UDP-Lite being a newer protocol and the continued growth of network speeds.
The UDP-Lite MIB omits the IPv4-only listener table present in the UDP MIB (RFC 4113), which existed only for compatibility. The endpoint table supersedes it with more informative, IP-version-independent management.
The udpliteEndpointProcess value should use the system's native process identifier and correspond to sysApplElmtRunIndex (SYSAPPL-MIB) or hrSWRunIndex (HOST-RESOURCES-MIB) for interoperability, with zero as a fallback when unique identification is impossible.
udpliteEndpointViolCoverage is optional rather than mandatory because it is not required to manage the transport protocol itself; it is provided only to assist in debugging application design and configuration errors.
OIDs for column instances in udpliteEndpointTable must have no more than 128 sub-identifiers to remain accessible under SNMPv1, SNMPv2c, and SNMPv3. Implementers must size address objects accordingly.
The compliance statement requires that dns(16) address type need not be supported for endpoint local/remote address type fields; only unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4) and zero-length or 4/8/16/20-byte InetAddress values are required.
The InBadChecksum counter can serve as an indicator of residual link bit error rate. By observing InErrors and InBadChecksum and adapting checksum coverage configuration, operators can tune performance for specific link types.
Deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED; instead SNMPv3 with cryptographic security SHOULD be deployed to protect access to the MIB objects.
It is RECOMMENDED that implementers support the full SNMPv3 framework including cryptographic mechanisms for authentication and privacy when implementing this MIB module.
MIB conformance groups: udpliteBaseGroup (mandatory: InDatagrams, NoPorts, InErrors, OutDatagrams, DiscontinuityTime), udplitePartialCsumGroup (mandatory: InPartialCov, InBadChecksum, OutPartialCov), udpliteEndpointGroup (mandatory: EndpointProcess, EndpointMinCoverage), udpliteAppGroup (optional: EndpointViolCoverage).
udpliteEndpointMinCoverage (Unsigned32): per-endpoint minimum acceptable receiver checksum coverage length per RFC 3828. A value of 0 indicates only fully covered datagrams are accepted.
udpliteEndpointProcess (Unsigned32): identifies the software process associated with a UDP-Lite endpoint. Should match sysApplElmtRunIndex if SYSAPPL-MIB is available, or hrSWRunIndex otherwise; zero if not identifiable.
udpliteEndpointTable: IP-version-independent table of active UDP-Lite endpoints indexed by local/remote address type, address, port, and instance. Supports wildcard remote address (unknown(0) and zero-length octet-string) for listening sockets.
udpliteEndpointViolCoverage (Counter32): optional per-endpoint counter of valid datagrams discarded because their checksum coverage was less than the minimum threshold. Assists in debugging misconfiguration.
udpliteInBadChecksum (Counter32): number of received datagrams whose checksum could not be validated, including those with illegal checksum coverage values. Counted also in InErrors.
udpliteInDatagrams (Counter64): total number of UDP-Lite datagrams delivered to UDP-Lite users. Uses 64-bit counter unlike traditional UDP MIB 32-bit counters.
udpliteInPartialCov (Counter64): total number of delivered UDP-Lite datagrams whose checksum coverage was strictly less than the datagram length, indicating use of partial checksum coverage.
udpliteOutPartialCov (Counter64): total number of sent datagrams whose checksum coverage was strictly less than the datagram length.
udpliteStatsDiscontinuityTime (TimeStamp): records sysUpTime at the most recent counter discontinuity event (e.g., module load/unload). A value of zero means no discontinuity since last re-initialization.
IANA assigned OBJECT IDENTIFIER { mib-2 170 } for the udpliteMIB module in the SMI Numbers registry.
All MIB objects are read-only (no read-write or read-create), so there is no risk of an intruder altering or creating management objects via direct SNMP SET operations if the MIB is implemented correctly.
Since UDP-Lite permits delivery of partially corrupted data, the MIB counters (particularly InBadChecksum and InErrors) can be used to infer end-to-end path characteristics and application type, representing an information-disclosure risk.
The udpliteEndpointTable indices (especially udpliteEndpointLocalPort) expose which ports are open on a machine, enabling an attacker to identify attack vectors without running a port scanner. Access to these objects should be controlled and encrypted via SNMPv3.
udpliteEndpointMinCoverage reveals the checksum coverage requirements of a specific UDP-Lite port, providing additional detail about the type of application at the receiver that could be exploited by an attacker.