Last Call Review of draft-ietf-6lo-nfc-13
review-ietf-6lo-nfc-13-secdir-lc-johansson-2019-03-07-00

Request Review of draft-ietf-6lo-nfc
Requested rev. no specific revision (document currently at 13)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2018-12-24
Requested 2018-12-10
Draft last updated 2019-03-07
Completed reviews Intdir Early review of -10 by Sheng Jiang (diff)
Iotdir Early review of -10 by Brian Haberman (diff)
Tsvart Last Call review of -12 by Wesley Eddy (diff)
Opsdir Last Call review of -12 by Qin Wu (diff)
Secdir Last Call review of -13 by Leif Johansson
Genart Last Call review of -12 by Jari Arkko (diff)
Assignment Reviewer Leif Johansson
State Completed
Review review-ietf-6lo-nfc-13-secdir-lc-johansson-2019-03-07
Reviewed rev. 13
Review result Has Issues
Review completed: 2019-03-07

Review
review-ietf-6lo-nfc-13-secdir-lc-johansson-2019-03-07

 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.

I am not a subject matter expert but overall I find the document well 
written and readable. 

The issue I have is in the security considerations section where I 
really think there should be normative language around the use 
of permanent identifiers. In particular:

"Thus, every single touch connection can use a different short address of NFC
link with an extremely short-lived link.  This can mitigate address scanning 
as well as location tracking and device-specific vulnerability exploitation."

This is imo too weak. I suggest reformulating this and related text to 
normative language. Given the possible consequences of NFC correlation
attacks I would have thought that a mandatory requirement on generating
different short addresses for every link would be a good idea.