Last Call Review of draft-ietf-ospf-rfc3137bis-03
review-ietf-ospf-rfc3137bis-03-secdir-lc-yu-2013-02-14-00
| Request | Review of | draft-ietf-ospf-rfc3137bis |
|---|---|---|
| Requested revision | No specific revision (document currently at 04) | |
| Type | Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2013-02-11 | |
| Requested | 2013-01-31 | |
| Authors | Alvaro Retana , Liem Nguyen , Alex D. Zinin , Russ White , Danny R. McPherson | |
| Draft last updated | 2013-02-14 | |
| Completed reviews |
Genart Last Call review of -03
by
Joel M. Halpern
(diff)
Secdir Last Call review of -03 by Taylor Yu (diff) |
|
| Assignment | Reviewer | Taylor Yu |
| State | Completed Snapshot | |
| Review |
review-ietf-ospf-rfc3137bis-03-secdir-lc-yu-2013-02-14
|
|
| Reviewed revision | 03 (document currently at 04) | |
| Result | Has Nits | |
| Completed | 2013-02-14 |
review-ietf-ospf-rfc3137bis-03-secdir-lc-yu-2013-02-14-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. The Security Considerations section of this document states: The technique described in this document does not introduce any new security issues into the OSPF protocol. I believe this is true. Editorial comments: * The acronym LSA appears in this document, but there appears to be no expansion of it in the document. * Section 2 mentions MaxLinkMetric, but the document doesn't define it until Section 3. I looked in vain in the OSPF RFCs until I realized this document newly defines this value. Consider indicating this forward reference in Section 2, e.g. "...set to MaxLinkMetric (defined in Section 3)".