Skip to main content

Telechat Review of draft-ietf-6lo-rfc6775-update-11
review-ietf-6lo-rfc6775-update-11-secdir-telechat-lonvick-2018-02-22-00

Request Review of draft-ietf-6lo-rfc6775-update
Requested revision No specific revision (document currently at 21)
Type Telechat Review
Team Security Area Directorate (secdir)
Deadline 2018-03-06
Requested 2018-02-05
Authors Pascal Thubert , Erik Nordmark , Samita Chakrabarti , Charles E. Perkins
I-D last updated 2018-02-22
Completed reviews Intdir Early review of -11 by Tim Chown (diff)
Iotdir Early review of -11 by Dave Thaler (diff)
Opsdir Telechat review of -11 by Jürgen Schönwälder (diff)
Secdir Telechat review of -11 by Chris M. Lonvick (diff)
Genart Telechat review of -14 by Peter E. Yee (diff)
Rtgdir Telechat review of -13 by Adrian Farrel (diff)
Genart Telechat review of -16 by Peter E. Yee (diff)
Secdir Telechat review of -16 by Chris M. Lonvick (diff)
Assignment Reviewer Chris M. Lonvick
State Completed
Request Telechat review on draft-ietf-6lo-rfc6775-update by Security Area Directorate Assigned
Reviewed revision 11 (document currently at 21)
Result Has nits
Completed 2018-02-22
review-ietf-6lo-rfc6775-update-11-secdir-telechat-lonvick-2018-02-22-00
Hello,

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 with Nits.

I skimmed through the document, which appears thorough and well laid out.

The Security Considerations section is appropriate.

Below are some nits that I found in the Security Considerations section:

Current:
Backbone Router in a way that prevents tempering with or replaying
Suggested:
s/tempering/tampering/

Current:
This specification recommends to using privacy techniques (see
Suggested:
s/to using/the use of/

Section B.5 is a section on Requirements Related to Security. This is an 
appropriate threat model.

Also, just because I'm a bit late in doing this, I reviewed the Privacy 
Considerations section of this document. This is also well written and 
provides guidance to implementers in the way of pointers to other RFCs.

Regards,
Chris