IETF Logo Mail Archive

Re: A plan for moving forward on the RFC 3576 MIB Documents

stefaan.de_cnodder@alcatel.be Fri, 06 January 2006 10:57 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Fri, 06 Jan 2006 10:58:55 +0000
Message-ID: <43BE4D2C.6060201@alcatel.be>
Date: Fri, 06 Jan 2006 11:57:48 +0100
From: stefaan.de_cnodder@alcatel.be
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
CC: radiusext@ops.ietf.org
Subject: Re: A plan for moving forward on the RFC 3576 MIB Documents
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; format="flowed"

Hi,

Version 03 of the RFC 3576 MIBs are available now:

http://www.ietf.org/internet-drafts/draft-ietf-radext-dynauth-server-mib-03.txt
http://www.ietf.org/internet-drafts/draft-ietf-radext-dynauth-client-mib-03.txt

All open issues (issues 137, 143, 145, and 149) should be solved.

regards,
Stefaan


Bernard Aboba wrote:

> These documents have completed WG last call, and from what I can tell 
> there is only a single open Issue (149).  I would therefore propose that 
> the editors prepare a new version of these documents by next week, so 
> that we can get the RFC 3576 MIBs on the IESG agenda immediately.
> 
> The RFC 3576 MIBs are only a month behind schedule, but there seems to 
> be little reason for further delay.  Let's wrap this up ASAP.
> 
> 
> 
> -- 
> 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/>

v2.23.0 | Report a Bug | By Email