Early Review of draft-ietf-roll-rnfd-02
review-ietf-roll-rnfd-02-secdir-early-lonvick-2023-12-02-00
Request | Review of | draft-ietf-roll-rnfd-02 |
---|---|---|
Requested revision | 02 (document currently at 07) | |
Type | Early Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2023-11-30 | |
Requested | 2023-11-05 | |
Requested by | Ines Robles | |
Authors | Konrad Iwanicki | |
I-D last updated | 2023-12-02 | |
Completed reviews |
Rtgdir Early review of -02
by Victoria Pritchard
(diff)
Secdir Early review of -02 by Chris M. Lonvick (diff) Opsdir Telechat review of -04 by Ron Bonica (diff) Tsvart Telechat review of -06 by Mirja Kühlewind (diff) Iotdir Telechat review of -05 by Peter Van der Stok (diff) |
|
Comments |
We kindly request a Routing and Security Directorate Review of this document, Thank you very much in advance, Ines and Dominique |
|
Assignment | Reviewer | Chris M. Lonvick |
State | Completed | |
Request | Early review on draft-ietf-roll-rnfd by Security Area Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/secdir/OBxjiqSrYF0cTLlBgRCPhVrBwuk | |
Reviewed revision | 02 (document currently at 07) | |
Result | Ready | |
Completed | 2023-12-02 |
review-ietf-roll-rnfd-02-secdir-early-lonvick-2023-12-02-00
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. First, I've not been following RPL so I read through the draft a few times and looked at a few of the references to familiarize myself. That is to say that I'm not an expert at this. I found the draft explains the concepts well and has an appropriate Security Considerations section. A couple of nits: Section 1.1 discusses what happens when an LBR crashes. In some places, the section uses the term "dead LBR". However, in other places, it just uses "LBR" and I can't always tell if it's referring to a live or dead LBR. It would help to clarify if in each case, it would be designated that the LBR is live, or dead. Section 5.5 uses the phrase "sufficiently many messages". As I said, I'm not familiar with RPL so I don't know how many would be sufficient. Can this be better quantified? Also, s/acros/across Best regards, Chris