Skip to main content

Last Call Review of draft-ietf-savnet-intra-domain-problem-statement-09
review-ietf-savnet-intra-domain-problem-statement-09-rtgdir-lc-dunbar-2025-01-15-00

Request Review of draft-ietf-savnet-intra-domain-problem-statement
Requested revision No specific revision (document currently at 26)
Type IETF Last Call Review
Team Routing Area Directorate (rtgdir)
Deadline 2025-01-17
Requested 2025-01-03
Requested by Jim Guichard
Authors Lancheng Qin , Dan Li , Jianping Wu , Mingqing(Michael) Huang , Nan Geng
I-D last updated 2026-06-09 (Latest revision 2026-06-01)
Completed reviews Rtgdir IETF Last Call review of -09 by Linda Dunbar (diff)
Secdir IETF Last Call review of -10 by Benjamin M. Schwartz (diff)
Opsdir IETF Last Call review of -10 by Sarah Banks (diff)
Artart IETF Last Call review of -09 by Robert Sparks (diff)
Genart IETF Last Call review of -10 by Tim Evens (diff)
Opsdir IETF Last Call review of -21 by Chongfeng Xie (diff)
Secdir IETF Last Call review of -21 by Benjamin M. Schwartz (diff)
Assignment Reviewer Linda Dunbar
State Completed
Request IETF Last Call review on draft-ietf-savnet-intra-domain-problem-statement by Routing Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/rtg-dir/a5Ic6w7fSZ7FIFpXDDN-Sz1Valc
Reviewed revision 09 (document currently at 26)
Result Has issues
Completed 2025-01-15
review-ietf-savnet-intra-domain-problem-statement-09-rtgdir-lc-dunbar-2025-01-15-00
General Comments:
The document could benefit from more concise wording. Some sections are overly
verbose and could be streamlined without losing critical information.

The document effectively describes two existing methods for Source Address
Validation (SAV): Access Control Lists (ACLs) and Unicast Reverse Path
Forwarding (uRPF). It highlights that ACLs have a high operational cost due to
the need for manual updates and maintenance in dynamic networks. uRPF, while
automated, struggles with asymmetric routing scenarios, leading to improper
blocking of legitimate traffic. These limitations are well known, and the
document does not provide sufficient new insights into overcoming them.

Section 5 (Requirements for New SAV Mechanisms):

The requirements listed in this section reflect desirable outcomes for any SAV
mechanism, such as automatic updates, accurate validation, and support for
incremental deployment. The previous efforts likely shared similar goals but
may have been deemed too complex or expensive to implement at scale. A more
valuable approach would be to discuss the technical challenges or trade-offs
involved in meeting these requirements and propose specific  frameworks to
address them.

The document would benefit from an exploration of why these challenges remain
unresolved and how new methods could overcome them.

Best Regards,
Linda Dunbar