[secdir] secdir review of draft-dekok-radext-datatypes

Sean Turner <sean@sn3rd.com> Sun, 07 August 2016 15:43 UTC

From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <242FE537-8205-4CAC-85BD-AC9CB740AFC4@sn3rd.com>
Date: Sun, 07 Aug 2016 11:43:01 -0400
To: draft-dekok-radext-datatypes.all@ietf.org, The IESG <iesg@ietf.org>, secdir@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/bTpq7JWnahrkkbE6_7RWiAs36_A>
Subject: [secdir] secdir review of draft-dekok-radext-datatypes
Precedence: list

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

[secdir] secdir review of draft-dekok-radext-data… Sean Turner