[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Issue: RFC 2618bis-2621bis nits



> Submitter name: David Nelson
> Submitter email address: dnelson@enterasys.com
> Date first submitted: September 15, 2005
> Reference: https://psg.com/lists/radiusext/2005/msg00855.html
> Document: 2618bis-00 through 2621bis-00
> Comment type: 'E'ditorial
> Priority: 'S' Must fix
> Section: 7, MIB Definitions
> Rationale/Explanation of issue:
> 
> >   C:\bwijnen\smicng\work>smicng radiusAuthClient.inc
> >   W: f(radiusAuthClient.mi2), (29,20) Revision date not in
> >      proper order - most recent comes first
> >   W: f(radiusAuthClient.mi2), (27,20) The first revision
> >      should match the last update for MODULE-IDENTITY
> >      radiusAuthClientMIB
> 
> Requested change:
> 
> Locate the latest revision at the top of the revision history list.
> 

By the way, the DESCRIPTION clause of a REVISION should 
contain a description of the (major) changes to the MIB
module.

Bert

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