datatracker.ietf.org
Sign in
Version 5.6.3.p2, 2014-09-29
Report a bug

RADIUS Accounting Server MIB for IPv6
RFC 4671

Network Working Group                                          D. Nelson
Request for Comments: 4671                            Enterasys Networks
Obsoletes: 2621                                              August 2006
Category: Informational

                 RADIUS Accounting Server MIB for IPv6

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   This memo defines a set of extensions that instrument RADIUS
   accounting server functions.  These extensions represent a portion of
   the Management Information Base (MIB) for use with network management
   protocols in the Internet community.  Using these extensions,
   IP-based management stations can manage RADIUS accounting servers.

   This memo obsoletes RFC 2621 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 2621 are carried forward into this document.  This memo also adds
   UNITS and REFERENCE clauses to selected objects.

Nelson                       Informational                      [Page 1]
RFC 4671             RADIUS Acct Server MIB (IPv6)           August 2006

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 ........................................20
   9. References .....................................................22
      9.1. Normative References ......................................22
      9.2. Informative References ....................................22
   Appendix A. Acknowledgements ......................................23

Nelson                       Informational                      [Page 2]
RFC 4671             RADIUS Acct Server MIB (IPv6)           August 2006

1.  Introduction

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   The objects defined within this memo relate to the Remote
   Authentication Dial-In User Service (RADIUS) Accounting Server as
   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" with respect to RADIUS
   packets, particularly in the context of counters of "malformed
   packets".  While RFC 2866 does not provide an explicit definition of
   "malformed", malformed generally means that the implementation has
   determined the packet does not match the format defined in RFC 2866.
   Those implementations are used in deployments today, and thus set the
   de facto definition of "malformed".

3.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   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 defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the 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 2621 [RFC2621], RADIUS Accounting Server
   MIB, by deprecating the radiusAccClientTable table and adding a new
   table, radiusAccClientExtTable, containing
   radiusAccClientInetAddressType and radiusAccClientInetAddress.  The
   purpose of these added MIB objects is to support version-neutral IP

[include full document text]