draft-ietf-radius-auth-servmib-03.txt   draft-ietf-radius-auth-servmib-04.txt 
RADIUS Working Group Glen Zorn RADIUS Working Group Glen Zorn
INTERNET-DRAFT Microsoft INTERNET-DRAFT Microsoft
Category: Standards Track Bernard Aboba Category: Standards Track Bernard Aboba
<draft-ietf-radius-auth-servmib-03.txt> Microsoft <draft-ietf-radius-auth-servmib-04.txt> Microsoft
2 February 1999 10 February 1999
RADIUS Authentication Server MIB RADIUS Authentication Server MIB
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts. Internet- may also distribute working documents as Internet-Drafts. Internet-
Drafts are draft documents valid for a maximum of six months and may be Drafts are draft documents valid for a maximum of six months and may be
updated, replaced, or obsoleted by other documents at any time. It is updated, replaced, or obsoleted by other documents at any time. It is
inappropriate to use Internet- Drafts as reference material or to cite inappropriate to use Internet- Drafts as reference material or to cite
them other than as "work in progress." them other than as "work in progress."
To view the list Internet-Draft Shadow Directories, see To view the list Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
The distribution of this memo is unlimited. It is filed as <draft-ietf- The distribution of this memo is unlimited. It is filed as <draft-ietf-
radius-auth-servmib-03.txt>, and expires August 1, 1999. Please send radius-auth-servmib-04.txt>, and expires August 1, 1999. Please send
comments to the authors. comments to the authors.
2. Copyright Notice 2. Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
3. Abstract 3. Abstract
This memo defines a set of extensions which instrument RADIUS This memo defines a set of extensions which instrument RADIUS
authentication server functions. These extensions represent a portion of authentication server functions. These extensions represent a portion of
skipping to change at page 4, line 28 skipping to change at page 4, line 28
Redmond, WA 98052 Redmond, WA 98052
US US
Phone: +1 425 936 6605 Phone: +1 425 936 6605
EMail: bernarda@microsoft.com" EMail: bernarda@microsoft.com"
DESCRIPTION DESCRIPTION
"The MIB module for entities implementing the server "The MIB module for entities implementing the server
side of the Remote Access Dialin User Service (RADIUS) side of the Remote Access Dialin User Service (RADIUS)
authentication protocol." authentication protocol."
DESCRIPTION "Initial version as published in RFC xxxx" DESCRIPTION "Initial version as published in RFC xxxx"
-- RCC xxx to be assigned by IANA -- RCC xxxx to be assigned by IANA
::= { radiusAuthentication 1 } ::= { radiusAuthentication 1 }
radiusMIB OBJECT-IDENTITY radiusMIB OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA." "The OID assigned to RADIUS MIB work by the IANA."
::= { mib-2 xxx } -- To be assigned by IANA ::= { mib-2 xxx } -- To be assigned by IANA
radiusAuthentication OBJECT IDENTIFIER ::= {radiusMIB 1} radiusAuthentication OBJECT IDENTIFIER ::= {radiusMIB 1}
skipping to change at page 15, line 8 skipping to change at page 15, line 4
for such a secure environment. for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network itself SNMPv1 by itself is not a secure environment. Even if the network itself
is secure (for example by using IPSec), there is no control as to who on is secure (for example by using IPSec), there is no control as to who on
the secure network is allowed to access and GET/SET the secure network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB. (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the User- as provided by the SNMPv3 framework. Specifically, the use of the User-
based Security Model RFC 2274 [12] and the View-based Access Control based Security Model RFC 2274 [12] and the View-based Access Control
Model RFC 2275 [15] is recommended. Using these security features, Model RFC 2275 [15] is recommended. Using these security features,
customer/users can give access to the objects only to those principals customer/users can give access to the objects only to those principals
(users) that have legitimate rights to GET or SET (change/create/delete) (users) that have legitimate rights to GET or SET (change/create/delete)
them. them.
10. Acknowledgments 10. Acknowledgments
Thanks to Narendra Gidwani of Microsoft, Allan C. Rubens of MERIT, Carl The authors acknowledge the contributions of the RADIUS Working Group in
Rigney of Livingston and Peter Heitman of American Internet Corporation the development of this MIB. Thanks to Narendra Gidwani of Microsoft,
for useful discussions of this problem space. Allan C. Rubens of MERIT, Carl Rigney of Livingston and Peter Heitman of
American Internet Corporation for useful discussions of this problem
space.
11. Authors' Addresses 11. Authors' Addresses
Bernard Aboba Bernard Aboba
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
Phone: 425-936-6605 Phone: 425-936-6605
EMail: bernarda@microsoft.com EMail: bernarda@microsoft.com
skipping to change at page 16, line 39 skipping to change at page 16, line 38
perpetual and will not be revoked by the Internet Society or its perpetual and will not be revoked by the Internet Society or its
successors or assigns. This document and the information contained successors or assigns. This document and the information contained
herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE
INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
14. Expiration Date 14. Expiration Date
This memo is filed as <draft-ietf-radius-auth-servermib-03.txt>, and This memo is filed as <draft-ietf-radius-auth-servermib-04.txt>, and
expires August 1, 1999. expires August 1, 1999.
 End of changes. 6 change blocks. 
8 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/