RE: Conclusion of IETF Last call on RFC 3576 MIBs, RFC 2618bis-2621bis

["Nelson, David" <dnelson@enterasys.com>]

Bernard Aboba writes...

> Can we go ahead and issue new documents with these 
> issues fixed?

In the case of the RADIUS Accounting MIBs, the change is trivial enough
that I would recommend that the IESG address it with an RFC Editor Note.

s/ACCT/ACC/ one place in each of two documents.

With respect to the Dynamic RADIUS MIBs, it may in fact be preferable to
issue a new draft version, and first run the revisions through an SMIv2
syntax checker.  I'll defer to the preference of the authors in this
regard, but it seemed that's what they had suggested.


--
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/>