Last Call Review of draft-ietf-sidrops-rpkimaxlen-12
review-ietf-sidrops-rpkimaxlen-12-secdir-lc-turner-2022-08-09-00
| Request | Review of | draft-ietf-sidrops-rpkimaxlen |
|---|---|---|
| Requested revision | No specific revision (document currently at 15) | |
| Type | IETF Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2022-07-20 | |
| Requested | 2022-07-06 | |
| Authors | Yossi Gilad , Sharon Goldberg , Kotikalapudi Sriram , Job Snijders , Ben Maddison | |
| I-D last updated | 2022-10-21 (Latest revision 2022-08-14) | |
| Completed reviews |
Genart IETF Last Call review of -11
by Roni Even
(diff)
Rtgdir IETF Last Call review of -12 by Acee Lindem (diff) Secdir IETF Last Call review of -12 by Sean Turner (diff) Artart IETF Last Call review of -11 by Jean Mahoney (diff) |
|
| Assignment | Reviewer | Sean Turner |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-sidrops-rpkimaxlen by Security Area Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/secdir/1xRWKi_Qfh74X_ExlYj-6yzCRRU | |
| Reviewed revision | 12 (document currently at 15) | |
| Result | Ready | |
| Completed | 2022-08-09 |
review-ietf-sidrops-rpkimaxlen-12-secdir-lc-turner-2022-08-09-00
Hi! I know a little about RPKI, but do not operate a network so I am in theoretical land here. I also reviewed the mail list traffic related to this I-D. Since this is an I-D and I'm supposed to comment, I wracked my brain and came up with nothing security-related. To me, it seems that the recommendation to configure your ROAs so that they align exactly with your BGP announcements seems pretty reasonable. Obviously, the more you tighten the screws the more operation impacts there are, but the I-D addresses some of those impacts.