IETF Last Call Review of draft-ietf-intarea-proxy-config-11
review-ietf-intarea-proxy-config-11-secdir-lc-lonvick-2026-03-22-00
| Request | Review of | draft-ietf-intarea-proxy-config |
|---|---|---|
| Requested revision | No specific revision (document currently at 14) | |
| Type | IETF Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2026-03-03 | |
| Requested | 2026-02-17 | |
| Authors | Tommy Pauly , Dragana Damjanovic , Yaroslav Rosomakho | |
| I-D last updated | 2026-06-02 (Latest revision 2026-05-19) | |
| Completed reviews |
Dnsdir IETF Last Call review of -11
by Florian Obser
(diff)
Genart IETF Last Call review of -11 by Dale R. Worley (diff) Secdir IETF Last Call review of -11 by Chris M. Lonvick (diff) Tsvart Telechat review of -11 by Wesley Eddy (diff) Opsdir IETF Last Call review of -13 by Daniele Ceccarelli (diff) |
|
| Assignment | Reviewer | Chris M. Lonvick |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-intarea-proxy-config by Security Area Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/secdir/T7XNXVwsy-us6nqFH5-Z3Ugy1Dw | |
| Reviewed revision | 11 (document currently at 14) | |
| Result | Has issues | |
| Completed | 2026-03-22 |
review-ietf-intarea-proxy-config-11-secdir-lc-lonvick-2026-03-22-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 with Issues. I agree with the GENART review that the authors appear to be deeply involved in the subject and have provided a comprehensive document, which just isn't easy to read. I also believe that the document may be improved by providing a threat model and some verbiage of how to address the threats. Guidance may be found in BCP 72 (RFC 3552). For instance, I'm not seeing how this is not susceptible to a man-in-the-middle attack, or a resource exhaustion attack. I'm not familiar with the subject matter so they may be in there and I'm just not seeing them. Best regards, Chris