MIB for RFC3576
stefaan.de_cnodder@alcatel.be Mon, 10 May 2004 09:48 UTC
Envelope-to: radiusext-data@psg.com
Delivery-date: Mon, 10 May 2004 09:49:05 +0000
Message-ID: <409F4FD6.FC83A201@alcatel.be>
Date: Mon, 10 May 2004 11:48:06 +0200
From: stefaan.de_cnodder@alcatel.be
MIME-Version: 1.0
To: radiusext@ops.ietf.org
Subject: MIB for RFC3576
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
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/>
- Re: MIB for RFC3576 Bernard Aboba
- MIB for RFC3576 stefaan.de_cnodder