Last Call Review of draft-ietf-sidrops-ov-egress-01
review-ietf-sidrops-ov-egress-01-genart-lc-sparks-2020-03-13-00
Request | Review of | draft-ietf-sidrops-ov-egress |
---|---|---|
Requested revision | No specific revision (document currently at 04) | |
Type | Last Call Review | |
Team | General Area Review Team (Gen-ART) (genart) | |
Deadline | 2020-03-18 | |
Requested | 2020-03-04 | |
Authors | Randy Bush , RĂ¼diger Volk , Jakob Heitz | |
I-D last updated | 2020-03-13 | |
Completed reviews |
Rtgdir Last Call review of -01
by Yingzhen Qu
(diff)
Genart Last Call review of -01 by Robert Sparks (diff) Opsdir Last Call review of -01 by Linda Dunbar (diff) Intdir Telechat review of -02 by Jouni Korhonen (diff) Opsdir Telechat review of -02 by Linda Dunbar (diff) |
|
Assignment | Reviewer | Robert Sparks |
State | Completed | |
Request | Last Call review on draft-ietf-sidrops-ov-egress by General Area Review Team (Gen-ART) Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/gen-art/4P7LrWrmXsDs6ER9OcHa97IksRw | |
Reviewed revision | 01 (document currently at 04) | |
Result | Ready | |
Completed | 2020-03-13 |
review-ietf-sidrops-ov-egress-01-genart-lc-sparks-2020-03-13-00
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>. Document: draft-ietf-sidrops-ov-egress-01 Reviewer: Robert Sparks Review Date: 2020-03-13 IETF LC End Date: 2020-03-18 IESG Telechat date: Not scheduled for a telechat Summary: Ready for publication as a Proposed Standard RFC Very minor nit - feel free to ignore - This sentence slowed me down when reading: As the origin AS may be modified by outbound policy, policy semantics based on RPKI Origin Validation state MUST be able to be applied separately on distribution into BGP and on egress. I suggest something like: As the origin AS may be modified by outbound policy, a BGP speaker MUST be able to apply policy semantics based on RPKI Origin Validation state separately on distribution into BGP and on egress.