Last Call Review of draft-ietf-sipcore-refer-clarifications-04
review-ietf-sipcore-refer-clarifications-04-secdir-lc-perlman-2015-06-10-00

Request Review of draft-ietf-sipcore-refer-clarifications
Requested rev. no specific revision (document currently at 04)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2015-06-17
Requested 2015-06-05
Authors Robert Sparks, Adam Roach
Draft last updated 2015-06-10
Completed reviews Genart Last Call review of -04 by Wassim Haddad
Secdir Last Call review of -04 by Radia Perlman
Opsdir Last Call review of -04 by Tom Taylor
Assignment Reviewer Radia Perlman
State Completed
Review review-ietf-sipcore-refer-clarifications-04-secdir-lc-perlman-2015-06-10
Reviewed rev. 04
Review result Ready
Review completed: 2015-06-10

Review
review-ietf-sipcore-refer-clarifications-04-secdir-lc-perlman-2015-06-10

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 is a clarifications document describing the changes to RFC3515 that

were implied by the publication of RFC6665. The document is fairly opaque to

readers not familiar with those two RFCs (including me), but its claim that

it does not change the security considerations for RFC3515 beyond those

already stated in RFC6665 seem highly plausible. It's a little surprising

that the contentof this document wasn't folded into RFC6665, but assuming

that document was adequately reviewed, this one should be fine.

Radia