RFC 4670
RADIUS Accounting Client MIB for IPv6
RFC 4670: RADIUS Accounting Client MIB for IPv6 🦋
Okay bestie, so this one is from D. Nelson at Enterasys Networks ✨ It's category Informational and it's dated August 2006 🌸 It obsoletes RFC 2620 💅 and the header doesn't list any updates 🫶
Status of This Memo 📜
This memo gives information to the Internet community, so it's not a standard of any kind 🌈 Distribution is unlimited, so share it with everyone 💖
Copyright Notice ©️
Copyright (C) The Internet Society (2006).
Abstract 🍓
This memo defines extensions that instrument the functions of a RADIUS accounting client 🎀 They're a chunk of the Management Information Base (MIB), which is the data network management protocols use. With them, IP-based management stations can manage RADIUS accounting clients, which is so iconic 👑
This memo obsoletes RFC 2620 by deprecating the MIB table with IPv4-only address formats and adding a new table for version-neutral IP address formats 🦋 The rest of the MIB objects from RFC 2620 get carried forward into this document ✨ It also adds UNITS and REFERENCE clauses to some selected objects 💜
Table of Contents 🗂️
1. Introduction ....................................................3
2. Terminology .....................................................3
3. The Internet-Standard Management Framework ......................3
4. Scope of Changes ................................................3
5. Structure of the MIB Module .....................................4
6. Deprecated Objects ..............................................5
7. Definitions .....................................................5
8. Security Considerations ........................................19
9. References .....................................................20
9.1. Normative References ......................................20
9.2. Informative References ....................................21
Appendix A. Acknowledgements ......................................221. Introduction ✨
This memo defines a piece of the Management Information Base (MIB) for network management protocols in the Internet community 🌸 The objects here are about the Remote Authentication Dial-In User Service (RADIUS) Accounting Client, which is defined in RFC 2866 [RFC2866] 🫶
2. Terminology 💅
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119] 🔥
This document uses terminology from RFC 2865 [RFC2865] and RFC 2866 [RFC2866] 🌈
This document uses the word "malformed" when it talks about RADIUS packets, especially for counters of "malformed packets" 🙈 RFC 2866 doesn't explicitly define "malformed," but generally it means the implementation decided the packet doesn't match the format defined in RFC 2866 💀 Those implementations are running in deployments today, so they set the de facto definition of "malformed" ✨
3. The Internet-Standard Management Framework 🦋
For a detailed overview of the documents describing the current Internet-Standard Management Framework, check out section 7 of RFC 3410 [RFC3410] 💖
Managed objects are accessed through a virtual information store called the Management Information Base, or MIB 🧚 MIB objects are generally accessed through the Simple Network Management Protocol (SNMP) 🌸 Objects in the MIB are defined using the mechanisms in the Structure of Management Information (SMI) 💅 This memo specifies a MIB module that is compliant with SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580] 🫶
4. Scope of Changes 🎀
This document obsoletes RFC 2620 [RFC2620], the RADIUS Accounting Client MIB, by deprecating the radiusAccServerTable table and adding a new table, radiusAccServerExtTable, which contains radiusAccServerInetAddressType, radiusAccServerInetAddress, and radiusAccClientServerInetPortNumber 👑 The added objects exist to support version-neutral IP addressing formats ✨ The existing table with radiusAuthServerAddress and radiusAuthClientServerPortNumber is deprecated 💜 The rest of the MIB objects from RFC 2620 are carried forward into this document 🌈
RFC 4001 [RFC4001], which defines the SMI Textual Conventions for IPv6 addresses, has this recommendation 🍓
"In particular, when revising a MIB module that contains IPv4 specific tables, it is suggested to define new tables using the textual conventions defined in this memo [RFC4001] that support all versions of IP. The status of the new tables SHOULD be "current", whereas the status of the old IP version specific tables SHOULD be changed to "deprecated". The other approach, of having multiple similar tables for different IP versions, is strongly discouraged."
5. Structure of the MIB Module 🧚
The RADIUS accounting protocol, described in RFC 2866 [RFC2866], splits things into a client function and a server function 🌸 In RADIUS accounting, clients send Accounting-Requests, and servers reply with Accounting-Responses 💖 Usually, Network Access Server (NAS) devices implement the client function, so they'd be expected to implement the RADIUS accounting client MIB 🔥 RADIUS accounting servers implement the server function, so they'd be expected to implement the RADIUS accounting server MIB 🫶
It's also possible for one RADIUS accounting entity to do both client and server functions 🦋 For example, a RADIUS proxy can act as a server to one or more RADIUS accounting clients while also acting as an accounting client to one or more accounting servers 🌈 In those situations, RADIUS entities that combine both functions are expected to support both the client and server MIBs 💅 The client MIB is defined in this document, and the server MIB is defined in [RFC4671] ✨
This MIB module has two scalars and a single table, the RADIUS Accounting Server Table 🍓 That table has one row for each RADIUS server the client shares a secret with 👑 Each entry in the RADIUS Accounting Server Table has fifteen columns showing what the RADIUS client is up to 💜
This MIB imports from [RFC2578], [RFC2580], [RFC3411], and [RFC4001] 🎀
6. Deprecated Objects 🙈
The deprecated table in this MIB is carried forward from RFC 2620 [RFC2620] 🌸 There are two conditions where managed entities MAY want to keep supporting the deprecated table:
- The managed entity only supports IPv4 address formats.
- The managed entity supports both IPv4 and IPv6 address formats, and the deprecated table is kept for backwards compatibility with older management stations. This option SHOULD only be used when the IP addresses in the new table are in IPv4 format and can accurately be represented in both the new table and the deprecated table.
Managed entities SHOULD NOT instantiate row entries in the deprecated table, which has IPv4-only address objects, when the RADIUS accounting server address in that row isn't an IPv4 address 💀 Managed entities SHOULD NOT return inaccurate IP address values or SNMP object access errors for IPv4-only address objects in tables that are otherwise populated 🧚 When row entries exist in both the deprecated IPv4-only table and the new IP-version-neutral table for the same RADIUS accounting server, the row indexes SHOULD be the same for the matching rows in each table 💖 That way management applications can correlate the related rows easily 🫶
7. Definitions 🔥
RADIUS-ACC-CLIENT-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, Integer32, Gauge32,
IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI
SnmpAdminString FROM SNMP-FRAMEWORK-MIB
InetAddressType, InetAddress,
InetPortNumber FROM INET-ADDRESS-MIB
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
radiusAccClientMIB MODULE-IDENTITY
LAST-UPDATED "200608210000Z" -- 21 August 2006
ORGANIZATION "IETF RADIUS Extensions Working Group."
CONTACT-INFO
" Bernard Aboba
Microsoft
One Microsoft Way
Redmond, WA 98052
US
Phone: +1 425 936 6605
EMail: bernarda@microsoft.com"
DESCRIPTION
"The MIB module for entities implementing the client
side of the Remote Authentication Dial-In User Service
(RADIUS) accounting protocol. Copyright (C) The
Internet Society (2006). This version of this MIB
module is part of RFC 4670; see the RFC itself for
full legal notices."
REVISION "200608210000Z" -- 21 August 2006
DESCRIPTION
"Revised version as published in RFC 4670.
This version obsoletes that of RFC 2620 by
deprecating the MIB table containing IPv4-only
address formats and defining a new table to add support
for version-neutral IP address formats. The remaining
MIB objects from RFC 2620 are carried forward into this
version."
REVISION "199906110000Z" -- 11 Jun 1999
DESCRIPTION "Initial version as published in RFC 2620."
::= { radiusAccounting 2 }
radiusMIB OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA."
::= { mib-2 67 }
radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2}
radiusAccClientMIBObjects OBJECT IDENTIFIER
::= { radiusAccClientMIB 1 }
radiusAccClient OBJECT IDENTIFIER
::= { radiusAccClientMIBObjects 1 }
radiusAccClientInvalidServerAddresses OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Response packets
received from unknown addresses."
::= { radiusAccClient 1 }
radiusAccClientIdentifier OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAS-Identifier of the RADIUS accounting client.
This is not necessarily the same as sysName in MIB
II."
REFERENCE "RFC 2865 section 5.32"
::= { radiusAccClient 2 }
radiusAccServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAccServerEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"The (conceptual) table listing the RADIUS accounting
servers with which the client shares a secret."
::= { radiusAccClient 3 }
radiusAccServerEntry OBJECT-TYPE
SYNTAX RadiusAccServerEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"An entry (conceptual row) representing a RADIUS
accounting server with which the client shares a
secret."
INDEX { radiusAccServerIndex }
::= { radiusAccServerTable 1 }okay bestie, picking up right where we left off, so the old deprecated RadiusAccServerEntry stuff comes first 💅
RadiusAccServerEntry ::= SEQUENCE {
radiusAccServerIndex Integer32,
radiusAccServerAddress IpAddress,
radiusAccClientServerPortNumber Integer32,
radiusAccClientRoundTripTime TimeTicks,
radiusAccClientRequests Counter32,
radiusAccClientRetransmissions Counter32,
radiusAccClientResponses Counter32,
radiusAccClientMalformedResponses Counter32,
radiusAccClientBadAuthenticators Counter32,
radiusAccClientPendingRequests Gauge32,
radiusAccClientTimeouts Counter32,
radiusAccClientUnknownTypes Counter32,
radiusAccClientPacketsDropped Counter32
}
radiusAccServerIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"A number uniquely identifying each RADIUS
Accounting server with which this client
communicates."
::= { radiusAccServerEntry 1 }
radiusAccServerAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The IP address of the RADIUS accounting server
referred to in this table entry."
::= { radiusAccServerEntry 2 }
radiusAccClientServerPortNumber OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The UDP port the client is using to send requests to
this server."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServerEntry 3 }
radiusAccClientRoundTripTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The time interval between the most recent
Accounting-Response and the Accounting-Request that
matched it from this RADIUS accounting server."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerEntry 4 }
-- Request/Response statistics
--
-- Requests = Responses + PendingRequests + ClientTimeouts
--
-- Responses - MalformedResponses - BadAuthenticators -
-- UnknownTypes - PacketsDropped = Successfully received
radiusAccClientRequests OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of RADIUS Accounting-Request packets
sent. This does not include retransmissions."
REFERENCE "RFC 2866 section 4.1"
::= { radiusAccServerEntry 5 }
radiusAccClientRetransmissions OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of RADIUS Accounting-Request packets
retransmitted to this RADIUS accounting server.
Retransmissions include retries where the
Identifier and Acct-Delay have been updated, as
well as those in which they remain the same."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerEntry 6 }
radiusAccClientResponses OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of RADIUS packets received on the
accounting port from this server."
REFERENCE "RFC 2866 section 4.2"
::= { radiusAccServerEntry 7 }
radiusAccClientMalformedResponses OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of malformed RADIUS Accounting-Response
packets received from this server. Malformed packets
include packets with an invalid length. Bad
authenticators and unknown types are not included as
malformed accounting responses."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServerEntry 8 }
radiusAccClientBadAuthenticators OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of RADIUS Accounting-Response
packets that contained invalid authenticators
received from this server."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServerEntry 9 }
radiusAccClientPendingRequests OBJECT-TYPE
SYNTAX Gauge32
UNITS "packets"
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of RADIUS Accounting-Request packets
sent to this server that have not yet timed out or
received a response. This variable is incremented
when an Accounting-Request is sent and decremented
due to receipt of an Accounting-Response, a timeout,
or a retransmission."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerEntry 10 }
radiusAccClientTimeouts OBJECT-TYPE
SYNTAX Counter32
UNITS "timeouts"
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of accounting timeouts to this server.
After a timeout, the client may retry to the same
server, send to a different server, or give up.
A retry to the same server is counted as a
retransmit as well as a timeout. A send to a different
server is counted as an Accounting-Request as well as
a timeout."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerEntry 11 }
radiusAccClientUnknownTypes OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of RADIUS packets of unknown type that
were received from this server on the accounting port."
REFERENCE "RFC 2866 section 4"
::= { radiusAccServerEntry 12 }
radiusAccClientPacketsDropped OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The number of RADIUS packets that were received from
this server on the accounting port and dropped for some
other reason."
::= { radiusAccServerEntry 13 }ngl the deprecated block is a whole vibe 🥀 now the new stuff ✨ it's literally introduced as "New MIB objects added in this revision," so this is where the fresh objects start 🦋
-- New MIB objects added in this revision
radiusAccServerExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAccServerExtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the RADIUS accounting
servers with which the client shares a secret."
::= { radiusAccClient 4 }
radiusAccServerExtEntry OBJECT-TYPE
SYNTAX RadiusAccServerExtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) representing a RADIUS
accounting server with which the client shares a
secret."
INDEX { radiusAccServerExtIndex }
::= { radiusAccServerExtTable 1 }
RadiusAccServerExtEntry ::= SEQUENCE {
radiusAccServerExtIndex Integer32,
radiusAccServerInetAddressType InetAddressType,
radiusAccServerInetAddress InetAddress,
radiusAccClientServerInetPortNumber InetPortNumber,
radiusAccClientExtRoundTripTime TimeTicks,
radiusAccClientExtRequests Counter32,
radiusAccClientExtRetransmissions Counter32,
radiusAccClientExtResponses Counter32,
radiusAccClientExtMalformedResponses Counter32,
radiusAccClientExtBadAuthenticators Counter32,
radiusAccClientExtPendingRequests Gauge32,
radiusAccClientExtTimeouts Counter32,
radiusAccClientExtUnknownTypes Counter32,
radiusAccClientExtPacketsDropped Counter32,
radiusAccClientCounterDiscontinuity TimeTicks
}
radiusAccServerExtIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A number uniquely identifying each RADIUS
Accounting server with which this client
communicates."
::= { radiusAccServerExtEntry 1 }
radiusAccServerInetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of address format used for the
radiusAccServerInetAddress object."
::= { radiusAccServerExtEntry 2 }
radiusAccServerInetAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of the RADIUS accounting
server referred to in this table entry, using
the version-neutral IP address format."
::= { radiusAccServerExtEntry 3 }
radiusAccClientServerInetPortNumber OBJECT-TYPE
SYNTAX InetPortNumber ( 1..65535 )
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The UDP port the client is using to send requests
to this accounting server. The value zero (0) is
invalid."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServerExtEntry 4 }
radiusAccClientExtRoundTripTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time interval between the most recent
Accounting-Response and the Accounting-Request that
matched it from this RADIUS accounting server."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerExtEntry 5 }
-- Request/Response statistics
--
-- Requests = Responses + PendingRequests + ClientTimeouts
--
-- Responses - MalformedResponses - BadAuthenticators -
-- UnknownTypes - PacketsDropped = Successfully received
radiusAccClientExtRequests OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
sent. This does not include retransmissions.
This counter may experience a discontinuity when the
RADIUS Accounting Client module within the managed
entity is reinitialized, as indicated by the current
value of radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 4.1"
::= { radiusAccServerExtEntry 6 }
radiusAccClientExtRetransmissions OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
retransmitted to this RADIUS accounting server.Okay so this is where the retransmissions counter wraps up, and it's giving a very specific reset rule 🧚
Retransmissions include retries where the
Identifier and Acct-Delay have been updated, as
well as those in which they remain the same.
This counter may experience a discontinuity when the
RADIUS Accounting Client module within the managed
entity is reinitialized, as indicated by the current
value of radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerExtEntry 7 }Next up is the responses counter 📦✨
radiusAccClientExtResponses OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets received on the
accounting port from this server. This counter
may experience a discontinuity when the RADIUS
Accounting Client module within the managed entity is
reinitialized, as indicated by the current value of
radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 4.2"
::= { radiusAccServerExtEntry 8 }Now the malformed responses one. Bestie, pay attention to the examples in here 👀 Malformed packets are described by their length, and bad authenticators and unknown types are explicitly NOT counted here 🙅♀️
radiusAccClientExtMalformedResponses OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of malformed RADIUS Accounting-Response
packets received from this server. Malformed packets
include packets with an invalid length. Bad
authenticators and unknown types are not included as
malformed accounting responses. This counter may
experience a discontinuity when the RADIUS Accounting
Client module within the managed entity is
reinitialized, as indicated by the current
value of radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServerExtEntry 9 }Bad authenticators get their own counter, which makes sense because they're a totally different vibe 🔐
radiusAccClientExtBadAuthenticators OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Response
packets that contained invalid authenticators
received from this server. This counter may
experience a discontinuity when the RADIUS
Accounting Client module within the managed
entity is reinitialized, as indicated by the
current value of
radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServerExtEntry 10 }Pending requests is a Gauge32, so it can go up and down. It's literally the requests still waiting on a reply 🎀 It goes up when an Accounting-Request is sent and comes back down on a response, a timeout, or a retransmission.
radiusAccClientExtPendingRequests OBJECT-TYPE
SYNTAX Gauge32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
sent to this server that have not yet timed out or
received a response. This variable is incremented
when an Accounting-Request is sent and decremented
due to receipt of an Accounting-Response, a timeout,
or a retransmission. This counter may experience a
discontinuity when the RADIUS Accounting Client module
within the managed entity is reinitialized, as
indicated by the current value of
radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerExtEntry 11 }Timeouts are lowkey tricky 🫶 After a timeout, the client can retry the same server, go to a different one, or just give up. The text spells out how each choice gets counted.
radiusAccClientExtTimeouts OBJECT-TYPE
SYNTAX Counter32
UNITS "timeouts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of accounting timeouts to this server.
After a timeout, the client may retry to the same
server, send to a different server, or give up.
A retry to the same server is counted as a
retransmit as well as a timeout. A send to a different
server is counted as an Accounting-Request as well as
a timeout. This counter may experience a discontinuity
when the RADIUS Accounting Client module within the
managed entity is reinitialized, as indicated by the
current value of radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerExtEntry 12 }Unknown types are packets that came in on the accounting port but whose type nobody recognises 🕵️♀️
radiusAccClientExtUnknownTypes OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets of unknown type that
were received from this server on the accounting port.
This counter may experience a discontinuity when the
RADIUS Accounting Client module within the managed
entity is reinitialized, as indicated by the current
value of radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 4"
::= { radiusAccServerExtEntry 13 }Packets dropped is the catch-all for anything that got binned for some other reason. Note there's no REFERENCE clause on this one 🤷♀️
radiusAccClientExtPacketsDropped OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets that were received from
this server on the accounting port and dropped for some
other reason. This counter may experience a
discontinuity when the RADIUS Accounting Client module
within the managed entity is reinitialized, as indicated
by the current value of
radiusAccClientCounterDiscontinuity."
::= { radiusAccServerExtEntry 14 }The discontinuity timer is the one that tells you when the counters were last reset 🕰️ It's measured in centiseconds, so it's a TimeTicks value.
radiusAccClientCounterDiscontinuity OBJECT-TYPE
SYNTAX TimeTicks
UNITS "centiseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of centiseconds since the last
discontinuity in the RADIUS Accounting Client
counters. A discontinuity may be the result of a
reinitialization of the RADIUS Accounting Client
module within the managed entity."
::= { radiusAccServerExtEntry 15 }Now the conformance section, which is where the MIB organises its compliance statements and groups 📚
-- conformance information
radiusAccClientMIBConformance OBJECT IDENTIFIER
::= { radiusAccClientMIB 2 }
radiusAccClientMIBCompliances OBJECT IDENTIFIER
::= { radiusAccClientMIBConformance 1 }
radiusAccClientMIBGroups OBJECT IDENTIFIER
::= { radiusAccClientMIBConformance 2 }
-- units of conformance
radiusAccClientMIBCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for accounting clients
implementing the RADIUS Accounting Client MIB.
Implementation of this module is for IPv4-only
entities, or for backwards compatibility use with
entities that support both IPv4 and IPv6."
MODULE -- this module
MANDATORY-GROUPS { radiusAccClientMIBGroup }
::= { radiusAccClientMIBCompliances 1 }The newer compliance statement is the IPv6 one. It's current, and it's for entities that support IPv6 or support both IPv4 and IPv6 💜 The address rules are where it gets specific 🌈
radiusAccClientExtMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for accounting
clients implementing the RADIUS Accounting
Client IPv6 Extensions MIB. Implementation of
this module is for entities that support IPv6,
or support IPv4 and IPv6."
MODULE -- this module
MANDATORY-GROUPS { radiusAccClientExtMIBGroup }
OBJECT radiusAccServerInetAddressType
SYNTAX InetAddressType { ipv4(1), ipv6(2) }
DESCRIPTION
"An implementation is only required to support
IPv4 and globally unique IPv6 addresses."
OBJECT radiusAccServerInetAddress
SYNTAX InetAddress ( SIZE (4|16) )
DESCRIPTION
"An implementation is only required to support
IPv4 and globally unique IPv6 addresses."
::= { radiusAccClientMIBCompliances 2 }Now the groups. The original MIB group is deprecated and the extension group is the current one, so you'd pick the extension one for new stuff ✨
-- units of conformance
radiusAccClientMIBGroup OBJECT-GROUP
OBJECTS { radiusAccClientIdentifier,
radiusAccClientInvalidServerAddresses,
radiusAccServerAddress,
radiusAccClientServerPortNumber,
radiusAccClientRoundTripTime,
radiusAccClientRequests,
radiusAccClientRetransmissions,
radiusAccClientResponses,
radiusAccClientMalformedResponses,
radiusAccClientBadAuthenticators,
radiusAccClientPendingRequests,
radiusAccClientTimeouts,
radiusAccClientUnknownTypes,
radiusAccClientPacketsDropped
}
STATUS deprecated
DESCRIPTION
"The basic collection of objects providing management of
RADIUS Accounting Clients."
::= { radiusAccClientMIBGroups 1 }
radiusAccClientExtMIBGroup OBJECT-GROUP
OBJECTS { radiusAccClientIdentifier,
radiusAccClientInvalidServerAddresses,
radiusAccServerInetAddressType,
radiusAccServerInetAddress,
radiusAccClientServerInetPortNumber,
radiusAccClientExtRoundTripTime,
radiusAccClientExtRequests,
radiusAccClientExtRetransmissions,
radiusAccClientExtResponses,
radiusAccClientExtMalformedResponses,
radiusAccClientExtBadAuthenticators,
radiusAccClientExtPendingRequests,
radiusAccClientExtTimeouts,
radiusAccClientExtUnknownTypes,
radiusAccClientExtPacketsDropped,
radiusAccClientCounterDiscontinuity
}
STATUS current
DESCRIPTION
"The basic collection of objects providing management of
RADIUS Accounting Clients."
::= { radiusAccClientMIBGroups 2 }
END8. Security Considerations 🔐💖
okay bestie, this section is SO important and I need you to take it seriously 😭 but also, it's giving main character energy because the whole thing is about who gets to touch the data 💅
so first off, the good news ✨ there are NO management objects in this MIB with a MAX-ACCESS of read-write or read-create. which means that if this MIB is implemented correctly, an intruder cannot alter or create any of its objects with direct SNMP SET operations. slay 🫶
but! there are a few objects that might hold sensitive info, and we need to talk about them 🙈
radiusAcctServerIPAddress 🌸 this one can reveal the address of the RADIUS accounting server that the client is talking to. that's super useful info for someone trying to attack the accounting server 💀
radiusAcctServerInetAddress 🌸 same deal here! this one tells you the address of the RADIUS accounting server the client is communicating with, which could be useful for attacking that server 😬
radiusAcctClientServerPortNumber 🦋 this one reveals the port number the RADIUS accounting client is sending on. that's useful for impersonating the client so someone can send data to the accounting server 🙅♀️
radiusAcctClientServerInetPortNumber 🦋 ngl this is the twin of the one above. same port info, same risk of impersonating the client to send data to the accounting server 💅
so it's really important to control even GET access to these objects 😭 and possibly even encrypt their values when they're sent over the network via SNMP. not every version of SNMP gives you features for a secure environment though, so be careful 👀
SNMP versions before SNMPv3 do NOT provide a secure environment, periodt 💀 and even if the network itself is secure (like with IPsec), there's no control over who on that secure network gets to GET/SET (read/change/create/delete) the objects in this MIB. like, the network being safe doesn't mean every user on it is safe 🙃
so here's the plan 🎀
It is RECOMMENDED that implementers look into the security features that the SNMPv3 framework provides (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms for authentication and privacy 🔥
and deploying SNMP versions before SNMPv3 is NOT RECOMMENDED 🙅♀️ instead, it is RECOMMENDED to deploy SNMPv3 and turn on cryptographic security 🔐 then it's a customer or operator responsibility to make sure the SNMP entity giving access to this MIB is configured so that only the principals (users) with legitimate rights can GET or SET (change/create/delete) the objects 👑
9. References 📚
9.1. Normative References 🌈
- [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 💜
- [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 💜
- [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. 💜
- [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. 💜
- [RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000. 💜
- [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002. 💜
- [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005. 💜
9.2. Informative References 🦋
- [RFC2620] Aboba, B. and G. Zorn, "RADIUS Accounting Client MIB", RFC 2620, June 1999. 🌸
- [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000. 🌸
- [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002. 🌸
- [RFC4671] Nelson, D., "RADIUS Accounting Server MIB for IPv6", RFC 4671, August 2006. 🌸
Appendix A. Acknowledgements 🫶
okay so the authors of the original MIB are Bernard Aboba and Glen Zorn 👑
and a huge thank you to all the reviewers, especially Dave Harrington, Dan Romascanu, C.M. Heard, Bruno Pape, Greg Weber, and Bert Wijnen 🥰✨
Author's Address 🖊️
David B. Nelson Enterasys Networks 50 Minuteman Road Andover, MA 01810 USA
EMail: dnelson@enterasys.com
Full Copyright Statement ⭐
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 🙈
Intellectual Property 🌈
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. 💅
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. 🔗
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. 💌
Acknowledgement 🎀
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). ✨💖
📦 where this page comes from
- ietf: rfc4670 2006-08
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms