Last Call Review of draft-ietf-sipcore-name-addr-guidance-02
review-ietf-sipcore-name-addr-guidance-02-secdir-lc-lonvick-2017-06-02-00

Request Review of draft-ietf-sipcore-name-addr-guidance
Requested rev. no specific revision (document currently at 02)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2017-06-01
Requested 2017-05-18
Draft last updated 2017-06-02
Completed reviews Genart Last Call review of -01 by Francis Dupont (diff)
Opsdir Last Call review of -01 by Bert Wijnen (diff)
Secdir Last Call review of -02 by Chris Lonvick
Assignment Reviewer Chris Lonvick
State Completed
Review review-ietf-sipcore-name-addr-guidance-02-secdir-lc-lonvick-2017-06-02
Reviewed rev. 02
Review result Ready
Review completed: 2017-06-02

Review
review-ietf-sipcore-name-addr-guidance-02-secdir-lc-lonvick-2017-06-02

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

    This document updatesRFC3261 <https://tools.ietf.org/html/rfc3261>  to state the constraint generically,
    and clarifies that the constraint applies to all SIP header fields
    where there is a choice between using name-addr or addr-spec.  It
    also updates the RFCs that define extension SIP header fields using
    the alternative to clarify that the constraint applies (RFCs 3325,
    3515, 3892, 4508, 5002, 5318, 5360, and 5502).

The document is READY. It is well written, to the point, and I found no 
nits.

Thanks,
Chris