Last Call Review of draft-ietf-radext-datatypes-04
review-ietf-radext-datatypes-04-secdir-lc-turner-2016-08-11-00

All,

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG. These comments
were written primarily for the benefit of the security area directors. 
Document editors and WG chairs should treat these comments just like any other
last call comments.

This document is essentially one long IANA consideration; the document defines
an IANA registry for data types, and updates the RADIUS Attribute Type registry
to use those newly defined data types.  It’s not just busy work though because
the document does recommend implementations should use the data types. 
Finally, this document mandates no changes to any RADIUS implementation.

Summary: ready

nits (take ‘em or leave ‘em, but please don’t hold anything up for these):

s2.1.4:r/a new data type, it should follow the/a new data type, it SHOULD
follow the

s2.1.4: r/fields “Name”, … /field’s “Name”, …

s2.1.4:r/The "Value" field should be given as to be determined or “TBD” in
specifications./The "Value" field SHOULD be "to be determined" or “TBD".

spt