Dismiss
InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Browse Prior Art Database

RADIUS Authentication Client MIB (RFC2618)

IP.com Disclosure Number: IPCOM000003205D
Original Publication Date: 1999-Jun-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 11 page(s) / 25K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Aboba: AUTHOR [+2]

Abstract

This memo defines a set of extensions which instrument RADIUS authentication client 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 authentication clients.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 12% of the total text.

Network Working Group B. Aboba

Request for Comments: 2618 G. Zorn

Category: Standards Track Microsoft

June 1999

RADIUS Authentication Client MIB

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

This memo defines a set of extensions which instrument RADIUS

authentication client 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

authentication clients.

1. Introduction

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 managing RADIUS

authentication clients.

Today a wide range of network devices, including routers and NASes,

act as RADIUS authentication clients in order to provide

authentication and authorization services. As a result, the effective

management of RADIUS authentication clients is of considerable

importance.

2. The SNMP Management Framework

The SNMP Management Framework presently consists of five major

components:

o An overall architecture, described in RFC 2571 [1].

o Mechanisms for describing and naming objects and events for the

purpose of management. The first version of this Structure of

Management Information (SMI) is called SMIv1 and described in

STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].

The second version, called SMIv2, is described in STD 58, RFC

2578 [5], RFC 2579 [6] and RFC 2580 [7].

o Message protocols for transferring management information. The

first version of the SNMP message protocol is called SNMPv1 and

described in STD 15, RFC 1157 [8]. A second version of the

SNMP message protocol, which is not an Internet standards

track protocol, is called SNMPv2c and described in RFC 1901

[9] and RFC 1906 [10]. The third version of the message

protocol is called SNMPv3 and described in RFC 1906 [10], RFC

2572 [11] and RFC 2574 [12].

o Protocol operations for accessing management information. The

first set of protocol operations and associated PDU formats is

described in STD 15, RFC 1157 [8]. A second set of protocol

operations and associated P...