Last Call Review of draft-ietf-ecrit-ecall-21
review-ietf-ecrit-ecall-21-secdir-lc-zhang-2017-01-05-00
| Request | Review of | draft-ietf-ecrit-ecall |
|---|---|---|
| Requested revision | No specific revision (document currently at 27) | |
| Type | Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2017-01-06 | |
| Requested | 2016-12-16 | |
| Authors | Randall Gellens , Hannes Tschofenig | |
| I-D last updated | 2017-01-05 | |
| Completed reviews |
Genart Last Call review of -21
by Meral Shirazipour
(diff)
Secdir Last Call review of -21 by Dacheng Zhang (diff) Opsdir Last Call review of -21 by Nevil Brownlee (diff) Genart Telechat review of -23 by Meral Shirazipour (diff) |
|
| Assignment | Reviewer | Dacheng Zhang |
| State | Completed | |
| Request | Last Call review on draft-ietf-ecrit-ecall by Security Area Directorate Assigned | |
| Reviewed revision | 21 (document currently at 27) | |
| Result | Has issues | |
| Completed | 2017-01-05 |
review-ietf-ecrit-ecall-21-secdir-lc-zhang-2017-01-05-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 cites multiple RFCs. In those RFCs, the security issues related with this work are extensively discussed, although I have to look up those RFCs to find out how to deal with, for example, DDoS attacks. I think it would really helpful if authors can briefly introduce what issues are discuss in those RFCs. Apart from this, this document is ready for publication.