Last Call Review of draft-ietf-softwire-map-t-05
review-ietf-softwire-map-t-05-secdir-lc-yu-2014-10-30-00
Request | Review of | draft-ietf-softwire-map-t |
---|---|---|
Requested revision | No specific revision (document currently at 08) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2014-10-28 | |
Requested | 2014-10-02 | |
Authors | Xing Li , Congxiao Bao , Wojciech Dec , Ole Trøan , Satoru Matsushima , Tetsuya Murakami | |
I-D last updated | 2014-10-30 | |
Completed reviews |
Genart Last Call review of -05
by Dan Romascanu
(diff)
Genart Last Call review of -05 by Dan Romascanu (diff) Genart Telechat review of -06 by Dan Romascanu (diff) Genart Last Call review of -08 by Dan Romascanu Secdir Last Call review of -05 by Taylor Yu (diff) Opsdir Last Call review of -05 by Victor Kuarsingh (diff) |
|
Assignment | Reviewer | Taylor Yu |
State | Completed | |
Request | Last Call review on draft-ietf-softwire-map-t by Security Area Directorate Assigned | |
Reviewed revision | 05 (document currently at 08) | |
Result | Has nits | |
Completed | 2014-10-30 |
review-ietf-softwire-map-t-05-secdir-lc-yu-2014-10-30-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: ready with nits The security considerations section of this document seems reasonable. I am wondering if deploying MAP-T has any significant effect on enumeration and topology probing attacks, but I suspect that any such effects are minor. If people with more experience than me in this area have an opinion on this issue, it might be worth mentioning in the security considerations.