Checks on draft-decnodder-radext-dynauth-server-mib-02.txt
"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Tue, 21 December 2004 17:00 UTC
Envelope-to: radiusext-data@psg.com
Delivery-date: Tue, 21 Dec 2004 17:01:09 +0000
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550604E818@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: radiusext@ops.ietf.org
Subject: Checks on draft-decnodder-radext-dynauth-server-mib-02.txt
Date: Tue, 21 Dec 2004 18:00:21 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1255"
--- running idnits ... fyi --- $ idnits draft-decnodder-radext-dynauth-server-mib-02.txt idnits 1.58 draft-decnodder-radext-dynauth-server-mib-02.txt: Checking nits according to http://www.ietf.org/ID-Checklist.html : * The document seems to lack an IANA Considerations section. Checking conformance with RFC 3667/3668 boilerplate... the boilerplate looks good. Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt : Nothing found here (but these checks does not cover all of 1id-guidelines.txt yet). Miscellaneous warnings: - Line 308 has weird spacing: '... client with ...' Run idnits with the --verbose option for more detailed information. -- 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/>
- Checks on draft-decnodder-radext-dynauth-server-m… Wijnen, Bert (Bert)