Last Call Review of draft-ietf-precis-7700bis-07
review-ietf-precis-7700bis-07-secdir-lc-migault-2017-06-09-00

Request Review of draft-ietf-precis-7700bis
Requested rev. no specific revision (document currently at 10)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2017-06-13
Requested 2017-05-30
Other Reviews Genart Last Call review of -07 by Russ Housley (diff)
Opsdir Last Call review of -07 by Nevil Brownlee (diff)
Genart Telechat review of -08 by Russ Housley (diff)
Review State Completed
Reviewer Daniel Migault
Review review-ietf-precis-7700bis-07-secdir-lc-migault-2017-06-09
Posted at https://mailarchive.ietf.org/arch/msg/secdir/57U6wgLkyQb5UiNJ8gOpFxFWXkw
Reviewed rev. 07 (document currently at 10)
Review result Ready
Draft last updated 2017-06-09
Review completed: 2017-06-09

Review
review-ietf-precis-7700bis-07-secdir-lc-migault-2017-06-09

Hi,

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.

The summary of the review is READY


nits:

COMMENT A)

"""
2.1.  Rules

   The following rules apply within the Nickname profile of the PRECIS
   FreeformClass.
"""

I might be helpful to add the reference to RFC7564 after the FreeformClass
as you did in section 2.2. Another way could also to assume in the
introduction the reader is familiar with RFC7564. I also agree RFC7564 is
mentioned in the terminology section.

COMMENT B)

"""
 4.  Normalization Rule: Apply Unicode Normalization Form KC.  Because
"""

Two unexpected white spaces. Can be fixed by rfc-editor

COMMENT C)

"""
6.  Security Considerations

6.3.  Visually Similar Characters
"""

Maybe a reference to the example section with the names 5/7 or 6/7 can
illustrate that the current profile does not prevent visually similar
characters.