Re: MIB for RFC3576

Bernard Aboba <aboba@internaut.com> Mon, 10 May 2004 14:36 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Mon, 10 May 2004 14:33:37 +0000
Date: Mon, 10 May 2004 07:36:55 -0700
From: Bernard Aboba <aboba@internaut.com>
To: stefaan.de_cnodder@alcatel.be
cc: radiusext@ops.ietf.org
Subject: Re: MIB for RFC3576
Message-ID: <Pine.LNX.4.56.0405100735460.16598@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"

Only an update for IPv6 is in the charter currently.  To add a MIB,
there needs to be interest from multiple parties in implementing it.

On Mon, 10 May 2004 stefaan.de_cnodder@alcatel.be wrote:

>
> Hi,
>
> There are 2 new drafts describing a MIB for dynamic authorization
> clients and servers (RFC 3576) available at:
>
> http://www.ietf.org/internet-drafts/draft-decnodder-radext-dynauth-server-mib-00.txt
>
> http://www.ietf.org/internet-drafts/draft-decnodder-radext-dynauth-client-mib-00.txt
>
> All comments are welcome.
>
> The charter says that all work has to be compatible with RFC 3576
> and that MIB updates are also part of the charter. Does this mean
> that these drafts are also in scope of the charter after all it
> completes the existing MIBs in RFC2618-2621, or are only the IPv6
> updates without a full revision of the current MIBs the scope of the
> charter?
>
> thanks,
>
> Stefaan
>
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
>

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>