What is the status of this and the updates to 2619, 2620 and 2621? Have these already passed last call? Just curious as I am wanting to implement this to get the discontinuity values.
I have three comments:
1) in this MIB I noticed that mosy complains about the definition of radiusAuthClientExtMIBCompliance MODULE-COMPLIANCE
When I make the following change the syntax error is resolved. RFC-2578 indicates that the restricted enumeration is ok for INTEGER. Probably an issue with mosy not interpreting the textual convention, but wanted to mention it in case it needs to be corrected somehow...
OBJECT radiusAuthServerInetAddressType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
SYNTAX INTEGER { ipv4(1), ipv6(2) }
2) In the Accounting Client MIB I get a syntax error with mosy in the radiusAccClientExtMIBCompliance MODULE-COMPLIANCE. However if I make the following change it works. Again, Probably an issue with mosy...
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
SYNTAX INTEGER { ipv4(1), ipv6(2) }
3) the accounting client MIB the first line of the MIB changed from
RADIUS-ACC-CLIENT-MIB DEFINITIONS ::= BEGIN
to
RADIUS-ACCT-CLIENT-MIB DEFINITIONS ::= BEGIN
(the T was added). Is this ok?
Carl
-----Original Message-----
From: owner-radiusext@ops.ietf.org
[mailto:owner-radiusext@ops.ietf.org]On Behalf Of
Internet-Drafts@ietf.org
Sent: Monday, May 15, 2006 2:50 PM
To: i-d-announce@ietf.org
Cc: radiusext@ops.ietf.org
Subject: I-D ACTION:draft-ietf-radext-rfc2618bis-03.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions Working Group of the IETF.
Title : RADIUS Auth Client MIB (IPv6)
Author(s) : D. Nelson
Filename : draft-ietf-radext-rfc2618bis-03.txt
Pages : 24
Date : 2006-5-15
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 memo obsoletes RFC 2618 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 2618 are carried forward into this document. The memo also adds
UNITS and REFERENCE clauses to selected objects.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-radext-rfc2618bis-03.txt
To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.
Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
"get draft-ietf-radext-rfc2618bis-03.txt".
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
Internet-Drafts can also be obtained by e-mail.
Send a message to:
mailserv@ietf.org.
In the body type:
"FILE /internet-drafts/draft-ietf-radext-rfc2618bis-03.txt".
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Attachment:
draft-ietf-radext-rfc2618bis-03.URL
Description: draft-ietf-radext-rfc2618bis-03.URL