draft-ietf-radext-dynauth-server-mib-00.txt   draft-ietf-radext-dynauth-server-mib-01.txt 
Network Working Group S. De Cnodder Network Working Group S. De Cnodder
Internet-Draft Alcatel Internet-Draft Alcatel
Expires: November 19, 2005 N. Jonnala Expires: January 8, 2006 N. Jonnala
Consult
M. Chiba M. Chiba
Cisco Systems, Inc. Cisco Systems, Inc.
May 18, 2005 July 7, 2005
Dynamic Authorization Server MIB Dynamic Authorization Server MIB
draft-ietf-radext-dynauth-server-mib-00.txt draft-ietf-radext-dynauth-server-mib-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 36
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 19, 2005. This Internet-Draft will expire on January 8, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes the RADIUS dynamic authorization server In particular, it describes the RADIUS dynamic authorization server
skipping to change at page 6, line 16 skipping to change at page 6, line 16
Dynamic Authorization Server (DAS) Dynamic Authorization Server (DAS)
The component that resides on the NAS which processes the Disconnect The component that resides on the NAS which processes the Disconnect
and CoA requests sent by the Dynamic Authorization Client as and CoA requests sent by the Dynamic Authorization Client as
described in [RFC3576]. described in [RFC3576].
Dynamic Authorization Client (DAC) Dynamic Authorization Client (DAC)
The component which sends the Disconnect and CoA requests to the The component which sends the Disconnect and CoA requests to the
Dynamic Authorization Server as described in [RFC3576]. Dynamic Authorization Server as described in [RFC3576]. This is
typically a RADIUS Server, but is not limited to it and may, for
example, be a Rating Engine used for Prepaid Billing.
Dynamic Authorization Server Port Dynamic Authorization Server Port
The UDP port on which the Dynamic Authorization server listens for The UDP port on which the Dynamic Authorization server listens for
the Disconnect and CoA requests sent by the Dynamic Authorization the Disconnect and CoA requests sent by the Dynamic Authorization
Client. Client.
5. Overview 5. Overview
The RADIUS dynamic authorization extensions defined in [RFC3576], The RADIUS dynamic authorization extensions defined in [RFC3576],
skipping to change at page 8, line 8 skipping to change at page 8, line 8
mentioned above, a typical case would be where the MIBs for a RADIUS mentioned above, a typical case would be where the MIBs for a RADIUS
authentication server, a RADIUS accounting server, and a RADIUS authentication server, a RADIUS accounting server, and a RADIUS
dynamic authorization client are implemented by the same device. dynamic authorization client are implemented by the same device.
However, also for these 3 MIBs, they can be implemented independent However, also for these 3 MIBs, they can be implemented independent
from each other. A RADIUS proxy might implement any of these 6 MIBs, from each other. A RADIUS proxy might implement any of these 6 MIBs,
but can also implement any subset of these MIBs. but can also implement any subset of these MIBs.
+---------------+ +---------------+ +---------------+ +---------------+
User 1----| | Disconnect-Request | | User 1----| | Disconnect-Request | |
| Dynamic | CoA-Request | Dynamic | | Dynamic | CoA-Request | Dynamic |
user 2----| Authorization |<---------------------| Authorization | User 2----| Authorization |<---------------------| Authorization |
| Server |--------------------->| Client | | Server |--------------------->| Client |
User 3----| (DAS) | Disconnect-Ack | (DAC) | User 3----| (DAS) | Disconnect-Ack | (DAC) |
| | Disconnect-NAK | | | | Disconnect-NAK | |
+---------------+ CoA-Ack/CoA-NAK +---------------+ +---------------+ CoA-Ack/CoA-NAK +---------------+
Figure 1: Mapping of clients and servers. Figure 1: Mapping of clients and servers.
This MIB module for the dynamic authorization server contains the This MIB module for the dynamic authorization server contains the
following: following:
1. Two scalar objects 1. Two scalar objects
2. One Dynamic Authorization Client Table. This table contains one 2. One Dynamic Authorization Client Table. This table contains one
row for each DAC that the DAS shares a secret with. row for each DAC with which the DAS shares a secret.
6. RADIUS Dynamic Authorization Server MIB Definitions 6. RADIUS Dynamic Authorization Server MIB Definitions
RADIUS-DYNAUTH-SERVER-MIB DEFINITIONS ::= BEGIN RADIUS-DYNAUTH-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Counter32, Integer32, mib-2 FROM SNMPv2-SMI Counter32, Integer32, mib-2 FROM SNMPv2-SMI
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB
InetAddressType, InetAddress FROM INET-ADDRESS-MIB InetAddressType, InetAddress FROM INET-ADDRESS-MIB
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
radiusDynAuthServerMIB MODULE-IDENTITY radiusDynAuthServerMIB MODULE-IDENTITY
LAST-UPDATED "200505160000Z" -- 16 May 2005 LAST-UPDATED "200507020000Z" -- 2 July 2005
ORGANIZATION "IETF RADEXT Working Group" ORGANIZATION "IETF RADEXT Working Group"
CONTACT-INFO CONTACT-INFO
" Stefaan De Cnodder " Stefaan De Cnodder
Alcatel Alcatel
Francis Wellesplein 1 Francis Wellesplein 1
B-2018 Antwerp B-2018 Antwerp
Belgium Belgium
Phone: +32 3 240 85 15 Phone: +32 3 240 85 15
EMail: stefaan.de_cnodder@alcatel.be EMail: stefaan.de_cnodder@alcatel.be
Nagi Reddy Jonnala Nagi Reddy Jonnala
Consult Cisco Systems, Inc.
4-486, Nutakki Divyasree Chambers, B Wing,
AP, India, PIN: 522303 O'Shaugnessy Road,
Bangalore-560027, India.
Phone: +91 8645 275314 Phone: +91 98456 99445
EMail: nagireddyj@yahoo.com EMail: njonnala@cisco.com
Murtaza Chiba Murtaza Chiba
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Dr. 170 West Tasman Dr.
San Jose CA, 95134 San Jose CA, 95134
Phone: +1 408 525 7198 Phone: +1 408 525 7198
EMail: mchiba@cisco.com " EMail: mchiba@cisco.com "
DESCRIPTION DESCRIPTION
"The MIB module for entities implementing the server "The MIB module for entities implementing the server
side of the Dynamic Authorization extensions Remote side of the Dynamic Authorization extensions Remote
Access Dialin User Service (RADIUS) protocol. Access Dialin User Service (RADIUS) protocol.
Copyright (C) The Internet Society (2005). This initial Copyright (C) The Internet Society (2005). This initial
version of this MIB module was published in RFC yyyy; version of this MIB module was published in RFC yyyy;
for full legal notices see the RFC itself. Supplementary for full legal notices see the RFC itself. Supplementary
information may be available on information may be available on
http://www.ietf.org/copyrights/ianamib.html." http://www.ietf.org/copyrights/ianamib.html."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200505160000Z" -- 16 May 2005 REVISION "200507020000Z" -- 2 July 2005
DESCRIPTION "Initial version as published in RFC yyyy." DESCRIPTION "Initial version as published in RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
::= { radiusDynamicAuthorization 1 } ::= { radiusDynamicAuthorization 1 }
radiusDynamicAuthorization OBJECT IDENTIFIER ::= { mib-2 xxx } radiusDynamicAuthorization OBJECT IDENTIFIER ::= { mib-2 xxx }
-- The value xxx to be assigned by IANA. -- The value xxx to be assigned by IANA.
radiusDynAuthServerMIBObjects OBJECT IDENTIFIER ::= radiusDynAuthServerMIBObjects OBJECT IDENTIFIER ::=
{ radiusDynAuthServerMIB 1 } { radiusDynAuthServerMIB 1 }
radiusDynAuthServer OBJECT IDENTIFIER ::= radiusDynAuthServer OBJECT IDENTIFIER ::=
{ radiusDynAuthServerMIBObjects 1 } { radiusDynAuthServerMIBObjects 1 }
radiusDynAuthServerInvalidClientAddresses OBJECT-TYPE radiusDynAuthServerDisconInvalidClientAddresses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS dynamic authorization messages "The number of Disconnect messages received from unknown
(both Disconnect and CoA) received from unknown
addresses." addresses."
::= { radiusDynAuthServer 1 } ::= { radiusDynAuthServer 1 }
radiusDynAuthServerCoAInvalidClientAddresses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of CoA messages received from unknown
addresses."
::= { radiusDynAuthServer 2 }
radiusDynAuthServerIdentifier OBJECT-TYPE radiusDynAuthServerIdentifier OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NAS-Identifier of the RADIUS dynamic authorization "The NAS-Identifier of the RADIUS dynamic authorization
server." server."
REFERENCE REFERENCE
"RFC 2865, Section 5.32, NAS-Identifier." "RFC 2865, Section 5.32, NAS-Identifier."
::= { radiusDynAuthServer 2 } ::= { radiusDynAuthServer 3 }
radiusDynAuthClientTable OBJECT-TYPE radiusDynAuthClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusDynAuthClientEntry SYNTAX SEQUENCE OF RadiusDynAuthClientEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the RADIUS dynamic "The (conceptual) table listing the RADIUS dynamic
authorization clients with which the server shares a authorization clients with which the server shares a
secret." secret."
::= { radiusDynAuthServer 3 } ::= { radiusDynAuthServer 4 }
radiusDynAuthClientEntry OBJECT-TYPE radiusDynAuthClientEntry OBJECT-TYPE
SYNTAX RadiusDynAuthClientEntry SYNTAX RadiusDynAuthClientEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) representing one Dynamic "An entry (conceptual row) representing one Dynamic
Authorization Client with which the server shares a Authorization Client with which the server shares a
secret." secret."
INDEX { radiusDynAuthClientIndex } INDEX { radiusDynAuthClientIndex }
::= { radiusDynAuthClientTable 1 } ::= { radiusDynAuthClientTable 1 }
skipping to change at page 13, line 33 skipping to change at page 13, line 42
SYNTAX Counter32 SYNTAX Counter32
UNITS "sessions" UNITS "sessions"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of user sessions removed for the "The number of user sessions removed for the
Disconnect-Requests received from this Disconnect-Requests received from this
Dynamic Authorization Client. Depending on site Dynamic Authorization Client. Depending on site
specific policies, a single Disconnect request specific policies, a single Disconnect request
can remove multiple user sessions. In the case this can remove multiple user sessions. In the case this
Dynamic Autorization Server has no knowledge on Dynamic Autorization Server has no knowledge of
the number of user sessions that are affected, then the number of user sessions that are affected, then
it counts a single user session for each such it counts a single user session for each such
Disconnect-Request." Disconnect-Request."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 8 } ::= { radiusDynAuthClientEntry 8 }
radiusDynAuthServMalformedDisconRequests OBJECT-TYPE radiusDynAuthServMalformedDisconRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
skipping to change at page 14, line 15 skipping to change at page 14, line 24
Section 2.3, Packet Format." Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 9 } ::= { radiusDynAuthClientEntry 9 }
radiusDynAuthServDisconBadAuthenticators OBJECT-TYPE radiusDynAuthServDisconBadAuthenticators OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Disconnect-Request packets "The number of RADIUS Disconnect-Request packets
which contained invalid Signature attributes which contained invalid Authenticator field
received from this Dynamic Authorization Client." received from this Dynamic Authorization Client."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM), and "RFC 3576, Section 2.1, Disconnect Messages (DM), and
Section 2.3, Packet Format." Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 10 } ::= { radiusDynAuthClientEntry 10 }
radiusDynAuthServDisconPacketsDropped OBJECT-TYPE radiusDynAuthServDisconPacketsDropped OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 15, line 42 skipping to change at page 16, line 4
UNITS "replies" UNITS "replies"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS CoA-NAK packets "The number of RADIUS CoA-NAK packets
sent to this Dynamic Authorization Client." sent to this Dynamic Authorization Client."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)." Messages (CoA)."
::= { radiusDynAuthClientEntry 15 } ::= { radiusDynAuthClientEntry 15 }
radiusDynAuthServCoAUserSessChanged OBJECT-TYPE radiusDynAuthServCoAUserSessChanged OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "sessions" UNITS "sessions"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of user sessions authorization "The number of user sessions authorization
changed for the CoA-Requests received from this changed for the CoA-Requests received from this
Dynamic Authorization Cient. Depending on site Dynamic Authorization Client. Depending on site
specific policies, a single CoA request can change specific policies, a single CoA request can change
multiple user sessions authorization. In the case multiple user sessions' authorization. In the case
this Dynamic Autorization Server has no knowledge on this Dynamic Autorization Server has no knowledge of
the number of user sessions that are affected, then the number of user sessions that are affected, then
it counts a single user session for each such it counts a single user session for each such
CoA-Request." CoA-Request."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)." Messages (CoA)."
::= { radiusDynAuthClientEntry 16 } ::= { radiusDynAuthClientEntry 16 }
radiusDynAuthServMalformedCoARequests OBJECT-TYPE radiusDynAuthServMalformedCoARequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
skipping to change at page 16, line 37 skipping to change at page 16, line 46
Messages (CoA), and Section 2.3, Packet Format." Messages (CoA), and Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 17 } ::= { radiusDynAuthClientEntry 17 }
radiusDynAuthServCoABadAuthenticators OBJECT-TYPE radiusDynAuthServCoABadAuthenticators OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS CoA-Request packets which "The number of RADIUS CoA-Request packets which
contained invalid Signature attributes received contained invalid Authenticator field received
from this Dynamic Authorization client." from this Dynamic Authorization client."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA), and Section 2.3, Packet Format." Messages (CoA), and Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 18 } ::= { radiusDynAuthClientEntry 18 }
radiusDynAuthServCoAPacketsDropped OBJECT-TYPE radiusDynAuthServCoAPacketsDropped OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of incoming CoA packets from this "The number of incoming CoA packets from this
Dynamic Authorization Client silently discarded Dynamic Authorization Client silently discarded
by the server application for some reason other than by the server application for some reason other than
malformed, bad clisdfauthenticators or unknown types." malformed, bad authenticators or unknown types."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA), and Section 2.3, Packet Format." Messages (CoA), and Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 19 } ::= { radiusDynAuthClientEntry 19 }
radiusDynAuthServUnknownTypes OBJECT-TYPE radiusDynAuthServUnknownTypes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 17, line 44 skipping to change at page 18, line 4
radiusAuthServerMIBCompliance MODULE-COMPLIANCE radiusAuthServerMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for entities implementing "The compliance statement for entities implementing
the RADIUS Dynamic Authorization Server." the RADIUS Dynamic Authorization Server."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { radiusDynAuthServerMIBGroup } MANDATORY-GROUPS { radiusDynAuthServerMIBGroup }
::= { radiusDynAuthServerMIBCompliances 1 } ::= { radiusDynAuthServerMIBCompliances 1 }
-- units of conformance -- units of conformance
radiusDynAuthServerMIBGroup OBJECT-GROUP radiusDynAuthServerMIBGroup OBJECT-GROUP
OBJECTS { radiusDynAuthServerInvalidClientAddresses, OBJECTS { radiusDynAuthServerDisconInvalidClientAddresses,
radiusDynAuthServerCoAInvalidClientAddresses,
radiusDynAuthServerIdentifier, radiusDynAuthServerIdentifier,
radiusDynAuthClientAddressType, radiusDynAuthClientAddressType,
radiusDynAuthClientAddress, radiusDynAuthClientAddress,
radiusDynAuthServDisconRequests, radiusDynAuthServDisconRequests,
radiusDynAuthServDupDisconRequests, radiusDynAuthServDupDisconRequests,
radiusDynAuthServDisconAcks, radiusDynAuthServDisconAcks,
radiusDynAuthServDisconNaks, radiusDynAuthServDisconNaks,
radiusDynAuthServDisconUserSessRemoved, radiusDynAuthServDisconUserSessRemoved,
radiusDynAuthServMalformedDisconRequests, radiusDynAuthServMalformedDisconRequests,
radiusDynAuthServDisconBadAuthenticators, radiusDynAuthServDisconBadAuthenticators,
skipping to change at page 19, line 35 skipping to change at page 19, line 35
an attack on the DAC. an attack on the DAC.
radiusDynAuthServerIdentifier radiusDynAuthServerIdentifier
This can be used to determine the Identifier of the DAS. This This can be used to determine the Identifier of the DAS. This
information could be useful in impersonating the DAS. information could be useful in impersonating the DAS.
The other readable objects are not really considered as being The other readable objects are not really considered as being
sensitive or vulnerable. These objects are: sensitive or vulnerable. These objects are:
radiusDynAuthServerInvalidClientAddresses, radiusDynAuthServerDisconInvalidClientAddresses,
radiusDynAuthServerCoAInvalidClientAddresses,
radiusDynAuthServDisconRequests, radiusDynAuthServDisconRequests,
radiusDynAuthServDupDisconRequests, radiusDynAuthServDupDisconRequests,
radiusDynAuthServDisconAcks, radiusDynAuthServDisconAcks,
radiusDynAuthServDisconNaks, radiusDynAuthServDisconNaks,
radiusDynAuthServDisconUserSessRemoved, radiusDynAuthServDisconUserSessRemoved,
radiusDynAuthServMalformedDisconRequests, radiusDynAuthServMalformedDisconRequests,
radiusDynAuthServDisconBadAuthenticators, radiusDynAuthServDisconBadAuthenticators,
radiusDynAuthServDisconPacketsDropped, radiusDynAuthServDisconPacketsDropped,
radiusDynAuthServCoARequests, radiusDynAuthServCoARequests,
radiusDynAuthServDupCoARequests, radiusDynAuthServDupCoARequests,
skipping to change at page 23, line 10 skipping to change at page 23, line 10
The authors would also like to acknowledge the following people for The authors would also like to acknowledge the following people for
their comments to this document: Anjaneyulu Pata, Dan Romascanu, and their comments to this document: Anjaneyulu Pata, Dan Romascanu, and
Bert Wijnen. Bert Wijnen.
10. References 10. References
10.1 Normative References 10.1 Normative References
[DYNCLNT] De Cnodder, S., Jonnala, N., and M. Chiba, "RADIUS Dynamic [DYNCLNT] De Cnodder, S., Jonnala, N., and M. Chiba, "RADIUS Dynamic
Auhtorization Client MIB", Authorization Client MIB",
draft-decnodder-radext-dynauth-client-mib-01.txt, work in draft-decnodder-radext-dynauth-client-mib-01.txt, work in
progress, June 2004. progress, June 2004.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999. April 1999.
skipping to change at page 24, line 17 skipping to change at page 24, line 17
Stefaan De Cnodder Stefaan De Cnodder
Alcatel Alcatel
Francis Wellesplein 1 Francis Wellesplein 1
B-2018 Antwerp B-2018 Antwerp
Belgium Belgium
Phone: +32 3 240 85 15 Phone: +32 3 240 85 15
Email: stefaan.de_cnodder@alcatel.be Email: stefaan.de_cnodder@alcatel.be
Nagi Reddy Jonnala Nagi Reddy Jonnala
Consult Cisco Systems, Inc.
4-486, Nutakki Divyasree Chambers, B Wing, O'Shaugnessy Road
AP, India, PIN: 522303 Bangalore-560027, India
Phone: +91 8645 275314 Phone: +91 98456 99445
Email: nagireddyj@yahoo.com Email: njonnala@cisco.com
Murtaza Chiba Murtaza Chiba
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Dr. 170 West Tasman Dr.
San Jose CA, 95134 San Jose CA, 95134
Phone: +1 408 525 7198 Phone: +1 408 525 7198
Email: mchiba@cisco.com Email: mchiba@cisco.com
Intellectual Property Statement Intellectual Property Statement
 End of changes. 

This html diff was produced by rfcdiff 1.24, available from http://www.levkowetz.com/ietf/tools/rfcdiff/