Last Call Review of draft-ietf-ospf-ipv4-embedded-ipv6-routing-07
review-ietf-ospf-ipv4-embedded-ipv6-routing-07-secdir-lc-laurie-2013-04-11-00
Request | Review of | draft-ietf-ospf-ipv4-embedded-ipv6-routing |
---|---|---|
Requested revision | No specific revision (document currently at 14) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2013-03-29 | |
Requested | 2013-03-07 | |
Authors | Dean Cheng , Mohamed Boucadair , Alvaro Retana | |
I-D last updated | 2013-04-11 | |
Completed reviews |
Genart Last Call review of -07
by Ben Campbell
(diff)
Genart Telechat review of -11 by Ben Campbell (diff) Secdir Last Call review of -07 by Ben Laurie (diff) |
|
Assignment | Reviewer | Ben Laurie |
State | Completed | |
Request | Last Call review on draft-ietf-ospf-ipv4-embedded-ipv6-routing by Security Area Directorate Assigned | |
Reviewed revision | 07 (document currently at 14) | |
Result | Has nits | |
Completed | 2013-04-11 |
review-ietf-ospf-ipv4-embedded-ipv6-routing-07-secdir-lc-laurie-2013-04-11-00
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. Summary: I-D is ready with potential nits. Detail: as far as I can tell, this I-D does not introduce any new mechanism and instead describes a particular configuration of existing mechanisms. As such, it is hard for it to introduce security issues that do not already exist. However, it is entirely possible the document's advice is not optimal - I'm afraid my knowledge of IPv6 is too limited to be a good judge of that. The security considerations section does mention some potential pitfalls, but it is hard to judge whether they are comprehensive, and I would suggest they should be. I would advise the security ADs to have it reviewed by an IPv6 security expert.