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

RE: I-D ACTION:draft-ietf-radext-fixes-02.txt



IDNITs gives some errors on this document:

idnits 2.04.05

tmp/draft-ietf-radext-fixes-02.txt:

 Checking boilerplate required by RFC 3978 and 3979, updated by RFC 4748:
----------------------------------------------------------------------------

    No issues found here.

 Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:
----------------------------------------------------------------------------

 ** Missing expiration date.  The document expiration date should appear on
    the first and last page.


 Checking nits according to http://www.ietf.org/ID-Checklist.html:
----------------------------------------------------------------------------

 ** The document seems to lack separate sections for Informative/Normative
    References.  All references will be assumed normative when checking for
    downward references.


 Miscellaneous warnings:
----------------------------------------------------------------------------

    No issues found here.

 Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------

 -- Missing reference section? 'RFC2119' on line 924 looks like a
    reference
    '[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate...'

 -- Missing reference section? 'RFC2865' on line 903 looks like a
    reference
'[RFC2865]...'

 -- Missing reference section? 'RFC3579' on line 970 looks like a
    reference
    'The alternate algorithm to [RFC3579] Section 2.6.1 that is descri...'

 -- Missing reference section? 'RFC4669' on line 956 looks like a
    reference
'[RFC4669] Nelson, D, "RADIUS Authentication Server MIB for IPv6", RF...'

 -- Missing reference section? 'RFC2866' on line 907 looks like a
    reference
'[RFC2866]...'

 -- Missing reference section? 'RFC2869' on line 910 looks like a
    reference
'[RFC2869]...'

 -- Missing reference section? 'RFC2618' on line 933 looks like a
    reference
'[RFC2618] Aboba, B. and G. Zorn, "RADIUS Authentication Client MIB",...'

 -- Missing reference section? 'RFC4668' on line 953 looks like a
    reference
'[RFC4668] Nelson, D, "RADIUS Authentication Client MIB for IPv6", RF...'

 -- Missing reference section? '1' on line 627 looks like a reference
'[1] New RADIUS specifications and implementations MUST NOT use Acce...'

 -- Missing reference section? '2' on line 630 looks like a reference
'[2] Access-Reject MUST mean denial of access to the requested servi...'

 -- Missing reference section? '3' on line 634 looks like a reference
    '[3]  New deployments of ARAP [RFC2869] SHOULD use Access-Challenge...'

 -- Missing reference section? 'Note 2' on line 651 looks like a
    reference
    '[Note 2] As per RFC 3579, the use of the Password-Retry in EAP...'

 -- Missing reference section? 'RFC2462' on line 927 looks like a
    reference
    '[RFC2462] Thomson, S. and T. Narten, "IPv6 Stateless Address...'

 -- Missing reference section? 'RFC3927' on line 947 looks like a
    reference
'[RFC3927] Cheshire, S., Aboba, B. and E. Guttman, "Dynamic Configura...'

 -- Missing reference section? 'RFC3162' on line 936 looks like a
    reference
'[RFC3162] Aboba, B., Zorn, G. and D. Mitton, "RADIUS and IPv6", RFC...'

 -- Missing reference section? 'RFC3580' on line 939 looks like a
    reference
'[RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G. and J. Roese,...'

 -- Missing reference section? 'RFC3748' on line 943 looks like a
    reference
    '[RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J. and H....'

 -- Missing reference section? 'RFC4282' on line 950 looks like a
    reference
'[RFC4282] Aboba, B., Beadles, M., Arkko, J. and P. Eronen, "The Netw...'

 -- Missing reference section? 'PREFIX' on line 961 looks like a
    reference
    'The references to [PREFIX] should be replaced with a reference to...'

 -- Missing reference section? 'RFC2607' on line 930 looks like a
    reference
    '[RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy...'


    Summary: 2 errors (**), 0 warnings (==), 20 comments (--).



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