Request to publish RFC 3576 MIBs as Informational RFCs

"Bernard Aboba" <Bernard_Aboba@hotmail.com> Tue, 17 January 2006 21:20 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Tue, 17 Jan 2006 21:21:24 +0000
Message-ID: <BAY106-DAV239FA90ACABBEC324590B8931A0@phx.gbl>
From: Bernard Aboba <Bernard_Aboba@hotmail.com>
To: iesg@ietf.org
Cc: ietf-secretary@ietf.org, dnelson@enterasys.com, radiusext@ops.ietf.org
Subject: Request to publish RFC 3576 MIBs as Informational RFCs
Date: Tue, 17 Jan 2006 13:20:52 -0800
Message-ID: <000301c61bab$e54eebb0$49883b9d@ntdev.corp.microsoft.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01C61B68.D73066A0"
Thread-Index: AcYbq+T9q2Y25V2SQ2CpTb/QRWYfdg==

The RFC 3576 client and server MIBs have completed RADEXT WG last call, and
there are no open issues. We are therefore requesting that the IESG consider
these documents for publication as Informational RFCs.  

 
The documents are available here:
http://www.ietf.org/internet-drafts/draft-ietf-radext-dynauth-client-mib-03.
txt
http://www.ietf.org/internet-drafts/draft-ietf-radext-dynauth-server-mib-03.
txt
 
These documents provide MIBs corresponding to the functionality defined in
RFC 3576. Our understanding is that the MIBs are in the process of being
implemented by at least two vendors.   The documents have been reviewed by
at least 5 members of the WG (including MIB Doctors) in addition to the
RADEXT WG chairs.  Discussion of the documents has occurred on the RADEXT WG
list with very little controversy, so that an appeal seems unlikely. Issues
filed and resolved relating to these specifications are available here:
 
http://www.drizzle.com/~aboba/RADEXT/

Request to publish RFC 3576 MIBs as Informational… Bernard Aboba