{"service":"corpus","corpus":"rfc","source":"RFC Editor","license":"IETF Trust / RFC Editor terms","record":{"id":"10078","title":"Problem Statement, Gap Analysis, and Requirements for Intra-Domain Source Address Validation","text":"﻿\n\n\n\nInternet Engineering Task Force (IETF)                            L. Qin\nRequest for Comments: 10078                      Zhongguancun Laboratory\nCategory: Informational                                            D. Li\nISSN: 2070-1721                                                    J. Wu\n                                                     Tsinghua University\n                                                                M. Huang\n                                                 Zhongguancun Laboratory\n                                                                 N. Geng\n                                                                  Huawei\n                                                            October 2026\n\n\n   Problem Statement, Gap Analysis, and Requirements for Intra-Domain\n                       Source Address Validation\n\nAbstract\n\n   Source Address Validation (SAV) is an important means to mitigate IP\n   source address spoofing (RFC 2827).  This document analyzes the gaps\n   in current operational mechanisms for intra-domain SAV.  It also\n   identifies the properties that new intra-domain SAV mechanisms are\n   expected to provide.\n\nStatus of This Memo\n\n   This document is not an Internet Standards Track specification; it is\n   published for informational purposes.\n\n   This document is a product of the Internet Engineering Task Force\n   (IETF).  It represents the consensus of the IETF community.  It has\n   received public review and has been approved for publication by the\n   Internet Engineering Steering Group (IESG).  Not all documents\n   approved by the IESG are candidates for any level of Internet\n   Standard; see Section 2 of RFC 7841.\n\n   Information about the current status of this document, any errata,\n   and how to provide feedback on it may be obtained at\n   https://www.rfc-editor.org/info/rfc10078.\n\nCopyright Notice\n\n   Copyright (c) 2026 IETF Trust and the persons identified as the\n   document authors.  All rights reserved.\n\n   This document is subject to BCP 78 and the IETF Trust's Legal\n   Provisions Relating to IETF Documents\n   (https://trustee.ietf.org/license-info) in effect on the date of\n   publication of this document.  Please review these documents\n   carefully, as they describe your rights and restrictions with respect\n   to this document.  Code Components extracted from this document must\n   include Revised BSD License text as described in Section 4.e of the\n   Trust Legal Provisions and are provided without warranty as described\n   in the Revised BSD License.\n\nTable of Contents\n\n   1.  Introduction\n     1.1.  Terminology\n   2.  Problem Statement\n   3.  Current Operational Intra-Domain SAV Mechanisms\n   4.  Gap Analysis\n     4.1.  Asymmetric Routing Scenario\n     4.2.  Hidden Prefix Scenario\n   5.  Requirements for New SAV Mechanisms\n     5.1.  Accurate Validation\n     5.2.  Automatic Updates\n     5.3.  Incremental Deployment Support\n     5.4.  No Adverse Impact on Routing Convergence and Fast Reroute\n     5.5.  Authentication of Information Used for SAV\n   6.  Security Considerations\n   7.  IANA Considerations\n   8.  References\n     8.1.  Normative References\n     8.2.  Informative References\n   Acknowledgements\n   Authors' Addresses\n\n1.  Introduction\n\n   Source Address Validation (SAV) defends against IP source address\n   spoofing [RFC2827].  Network operators can enforce SAV at the\n   following levels (see [RFC5210]):\n\n   *  IP SAV in the access network\n\n   *  IP SAV at intra-AS/ingress point\n\n   *  IP SAV in the inter-AS case (neighboring Autonomous System (AS))\n\n   Some access networks have already deployed SAV mechanisms.  These\n   mechanisms are typically deployed on switches in the access network\n   and prevent hosts connected to those switches from using the source\n   address of another host on the Internet [RFC5210].  Mechanisms\n   include:\n\n   *  Source Address Validation Improvement (SAVI) Solution for DHCP\n      [RFC7513]\n\n   *  IP Source Guard (IPSG) based on DHCP snooping [IPSG]\n\n   *  Cable Source-Verify [cable-verify]\n\n   However, access-network SAV mechanisms are not universally deployed\n   [CAIDA-spoofer].  Therefore, intra-domain (i.e., intra-AS) SAV and\n   inter-domain (i.e., inter-AS) SAV are required [RFC5210].  For the\n   purpose of this document, intra-domain SAV is defined as follows:\n\n      The AS validates the source addresses of data traffic that it\n      originates directly or indirectly.  Intra-domain SAV is applied at\n      external interfaces (on routers) facing entities that are not\n      deployed as neighboring ASes and are therefore not covered by\n      inter-domain SAV.  For example, as illustrated in Figure 1, an\n      entity can be a single host, a set of hosts, or a customer network\n      with no AS that manages one or more IP prefixes.  The entity may\n      source traffic using prefixes assigned by the AS or its own Bring\n      Your Own IP (BYOIP) prefixes.  From the perspective of other ASes,\n      such traffic is originated by the AS.\n\n   SAV on traffic received on external interfaces facing a neighboring\n   AS is considered inter-domain SAV, regardless of whether the\n   neighboring AS uses a public Autonomous System Number (ASN) or a\n   private ASN.  SAV on internal interfaces (e.g., interfaces between\n   Router 1 and Router 3 in Figure 1) is also outside the scope of this\n   document.  This is because routers inside the same AS are generally\n   assumed to be trusted, so SAV on internal interfaces provides limited\n   additional benefit when SAV is already applied at external\n   interfaces.  In addition, techniques such as fast reroute can make\n   SAV at internal interfaces technically challenging.\n\n       +--------------------+\n       |  A neighboring AS  |\n       +--------------------+\n                 |\n                 |\n                 |\n   +-------------|-------------------------------------+\n   |Domain       |                                     |\n   |         +----------+               +----------+   |\n   |         | Router 3 +---------------+ Router 4 |   |\n   |         +----------+               +----------+   |\n   |          /        \\                     |         |\n   |         /          \\                    |         |\n   |        /            \\                   |         |\n   | +----------+     +----------+      +----------+   |\n   | | Router 1 |     | Router 2 +------+ Router 5 |   |\n   | +------*---+     +--*-------+      +----X-----+   |\n   |        /\\           /\\                  /\\        |\n   |         \\           /                   |         |\n   +----------\\---------/--------------------|---------+\n          +----------------+         +---------------+\n          | A customer     |         | A single host |\n          | network with   |         | or a set of   |\n          | no AS          |         | hosts         |\n          +----------------+         +---------------+\n\n             Figure 1: Deployment Locations of Intra-Domain SAV\n\n   Intra-domain SAV is applied at interfaces \"*\" and \"X\".\n\n   This document analyzes the gaps in current operational mechanisms for\n   intra-domain SAV.  It also identifies the properties that new intra-\n   domain SAV mechanisms are expected to provide.\n\n1.1.  Terminology\n\n   SAV Rule:\n      The rule that indicates the validity of a specific source IP\n      address or source IP prefix per router interface.  It is used by a\n      router to make SAV decisions.\n\n   Improper Block:\n      The validation results in packets with legitimate source addresses\n      being blocked improperly due to inaccurate SAV rules.  (The terms\n      \"improper block\" and \"false positive\" are used synonymously.)\n\n   Improper Permit:\n      The validation results in packets with spoofed source addresses\n      being permitted improperly due to inaccurate SAV rules.  (The\n      terms \"improper permit\" and \"false negative\" are used\n      synonymously.)\n\n   Proper Block:\n      The validation results in packets with spoofed source addresses\n      being blocked.\n\n   Proper Permit:\n      The validation results in packets with legitimate source addresses\n      being permitted.\n\n   SAV-specific Information:\n      The information specialized for SAV rule generation.\n\n   Direct Server Return (DSR):\n      A traffic delivery model commonly used by Content Delivery\n      Networks (CDNs) that use anycast service addresses while\n      delivering data from edge locations that do not announce those\n      addresses.  In such deployments, a request is received by the\n      anycast server or location, but the response is sent directly by\n      another server (i.e., the edge location) with the anycast service\n      address as the source address, rather than the address used to\n      reach the edge server.  This can create a legitimate hidden-prefix\n      scenario.\n\n2.  Problem Statement\n\n   The problems of existing intra-domain SAV mechanisms can be\n   characterized along three dimensions: improper block, improper\n   permit, and operational overhead:\n\n   Improper block:  Existing intra-domain SAV mechanisms may block data\n      packets using legitimate source addresses when the applied SAV\n      rules are inaccurate.\n\n   Improper permit:  Existing intra-domain SAV mechanisms may permit\n      data packets using spoofed source addresses when the applied SAV\n      rules are inaccurate.\n\n   Operational overhead:  Existing intra-domain SAV mechanisms may\n      require operator involvement to determine and update SAV rules.\n      This overhead depends on how much manual effort is needed to keep\n      the SAV rules up to date.\n\n   In this document, these three dimensions are used to analyze the gaps\n   in existing intra-domain SAV mechanisms.\n\n3.  Current Operational Intra-Domain SAV Mechanisms\n\n   Although [RFC2827] and [RFC3704] specify several ingress filtering\n   methods primarily intended for inter-domain SAV, some of these\n   methods have also been applied to intra-domain SAV in operational\n   practice.  This section introduces the mechanisms currently used to\n   implement intra-domain SAV.\n\n   *  Access Control Lists (ACLs) can be used as SAV filters [RFC2827]\n      to check the source address of each packet against a set of\n      permitted or prohibited prefixes.  When applied on a router\n      interface, each Access Control Entry (ACE) used for SAV filtering\n      specifies both matching conditions (i.e., prefixes) and the\n      corresponding action (e.g., permit or deny), and packets are\n      processed accordingly.\n\n   *  Strict unicast Reverse Path Forwarding (uRPF) [RFC3704] provides\n      an automated SAV filter by validating the source address of each\n      packet against the router's local Forwarding Information Base\n      (FIB).  A packet is accepted only if (i) the FIB contains a prefix\n      covering the source address and (ii) the FIB entry's outgoing\n      interface matches the packet's incoming interface.  Otherwise, the\n      packet is discarded.\n\n   *  Loose uRPF [RFC3704] also relies on the local FIB for validation\n      but only checks for the presence of a covering prefix.  A packet\n      is accepted if the FIB contains a prefix that covers the source\n      address, regardless of the incoming interface.\n\n4.  Gap Analysis\n\n   This section analyzes the gaps of the current operational intra-\n   domain SAV mechanisms.\n\n   ACLs can be used on interfaces facing a customer network with no AS\n   or a set of hosts to permit only packets whose source addresses\n   belong to specific prefixes.  To ensure correct filtering behavior,\n   the ACLs used for SAV filtering need to be updated when the permitted\n   prefixes change; otherwise, packets may be improperly permitted or\n   blocked.  In ACL-based SAV deployments, keeping these ACLs up to date\n   can introduce operational challenges when operators need to detect\n   prefix changes and determine and apply the corresponding ACL updates.\n\n   As described in Section 3 and also noted in [RFC3704], loose uRPF\n   sacrifices directionality when validating source addresses of data\n   packets.  Since its rules are overly permissive, any spoofed packet\n   with a source address present in the FIB may be permitted by loose\n   uRPF (i.e., an improper permit problem).\n\n   Strict uRPF may block legitimate traffic in the asymmetric routing or\n   hidden prefix scenarios (see Sections 4.1 and 4.2).  It may\n   mistakenly consider a valid incoming interface as invalid, resulting\n   in legitimate packets being blocked (i.e., an improper block\n   problem).\n\n   The following subsections describe two specific gap scenarios for\n   intra-domain SAV.\n\n4.1.  Asymmetric Routing Scenario\n\n   Asymmetric routing means a packet traverses from a source to a\n   destination in one path and takes a different path when it returns to\n   the source.  Asymmetric routing can occur due to routing policy,\n   traffic engineering, etc.\n\n   For example, a customer network with no AS connected to multiple\n   routers of the AS may need to perform load balancing on incoming\n   traffic, thereby resulting in asymmetric routing.  Figure 2\n   illustrates an example of asymmetric routing.  The customer network\n   owns prefix 2001:db8::/55 and connects to two routers of the AS,\n   Router 1 and Router 2.  Router 1, Router 2, and Router 3 exchange\n   routing information via the intra-domain routing protocol.  To\n   achieve load balancing for inbound traffic, the customer network\n   expects traffic destined for 2001:db8:0::/56 to enter through Router\n   1 and traffic destined for 2001:db8:0:100::/56 to enter through\n   Router 2.  To this end, Router 1 advertises 2001:db8:0::/56 and\n   Router 2 advertises 2001:db8:0:100::/56 through the intra-domain\n   routing protocol.  Figure 2 also shows the corresponding FIB entries\n   of Router 1 and Router 2 for the two prefixes.\n\n    +----------------------------------------------------------+\n    |Domain                                                    |\n    |                      +----------+                        |\n    |                      | Router 3 |                        |\n    |                      +----------+                        |\n    |                       /       \\                          |\n    |                      /         \\                         |\n    |                     /           \\                        |\n    |            +----------+       +----------+               |\n    |            | Router 1 |       | Router 2 |               |\n    |            +-----*----+       +----------+               |\n    |                  /\\               /                      |\n    |                   \\              /                       |\n    +--------------------\\------------/------------------------+\n     Traffic with         \\          / Traffic with\n     source IP addresses   \\        /  destination IP addresses\n     of 2001:db8:0:100::/56 \\      \\/  of 2001:db8:0:100::/56\n                       +----------------+\n                       |Customer network|\n                       |with no AS      |\n                       |(2001:db8::/55) |\n                       +----------------+\n\n    FIB of Router 1                FIB of Router 2\n    Dest                Next_hop   Dest                Next_hop\n    2001:db8:0::/56     Customer   2001:db8:0:100::/56 Customer\n                        Network                        Network\n    2001:db8:0:100::/56 Router 3   2001:db8:0::/56     Router 3\n\n                 Figure 2: An Example of Asymmetric Routing\n\n   The legitimate traffic originated from the customer network with\n   source addresses in 2001:db8:0:100::/56 will be improperly blocked by\n   strict uRPF on Router 1.\n\n   Although the customer network does not expect to receive inbound\n   traffic for 2001:db8:0:100::/56 via Router 1, it can send outbound\n   traffic with source addresses in that prefix through Router 1.  As a\n   result, data packets between the customer network and Router 1 may\n   follow asymmetric paths.  Arrows in Figure 2 indicate the direction\n   of traffic flow.\n\n   If Router 1 enforces strict uRPF by checking the FIB entry for the\n   prefix 2001:db8:0:100::/56, the corresponding SAV rule would only\n   allow packets with a source address from 2001:db8:0:100::/56 that\n   arrive via Router 3.  Consequently, when the customer network sends\n   packets with a source address in 2001:db8:0:100::/56 to Router 1,\n   strict uRPF would improperly drop these legitimate packets.\n   Similarly, if Router 2 enforces strict uRPF, it would improperly\n   block legitimate packets from the customer network that use source\n   addresses within the prefix 2001:db8:0::/56.\n\n4.2.  Hidden Prefix Scenario\n\n   The intra-domain hidden prefix scenario refers to situations in which\n   a host or a customer network with no AS legitimately originates\n   traffic using source addresses that are not visible to the intra-\n   domain routing protocol within the domain.\n\n   *  A host (for example, a cloud server instance operated by a tenant)\n      may originate traffic using a source address not allocated by the\n      AS operator.  This can occur in deployments such as DSR, where\n      return traffic is sent directly from the server using a service IP\n      address that is not part of the operator's internal routing view.\n\n   *  A customer network with no AS may originate traffic using source\n      addresses that are not advertised to the AS operator.  This can\n      occur in scenarios such as DSR deployments or when the customer\n      network uses address space assigned by another provider (e.g., in\n      multi-homing or hybrid connectivity scenarios), and such prefixes\n      are not propagated within the operator's intra-domain routing\n      system.\n\n   For ACL-based SAV, enforcing correct filtering in these scenarios\n   requires authoritative information that explicitly specifies which\n   source addresses the host or the customer network is authorized to\n   use.  In practice, such authoritative information is often missing.\n   Strict uRPF and loose uRPF also fail in hidden prefix scenarios.\n   They will drop packets from hidden prefixes because the source\n   addresses are absent from the router's FIB or are received from\n   unexpected interfaces.\n\n5.  Requirements for New SAV Mechanisms\n\n   This section identifies five requirements that can inform the design\n   of new intra-domain SAV mechanisms.  These requirements describe the\n   properties that new mechanisms are expected to provide in order to\n   improve upon existing mechanisms but do not make assumptions about\n   how those properties are achieved.  They do not mandate or justify\n   any specific extension to routing or other protocols and therefore\n   cannot be used to directly initiate standards-track protocol changes.\n\n   Existing intra-domain SAV mechanisms have problems in terms of\n   validation accuracy and operational overhead.  Current uRPF-based\n   mechanisms derive SAV decisions solely from routing or forwarding\n   state, which is intended to express reachability rather than\n   authorization of source address usage.  More generally, current\n   mechanisms lack authoritative information specifically intended for\n   SAV that can be consistently and automatically consumed by SAV\n   mechanisms.  As a result, uRPF-based mechanisms may not provide\n   accurate validation in scenarios such as asymmetric routing or hidden\n   prefixes (Section 4).  Existing ACL-based SAV deployments may have\n   limited applicability in dynamic environments when they rely on\n   operator-driven ACL maintenance.  These problems motivate the first\n   two requirements below (in Sections 5.1 and 5.2).  The remaining\n   three requirements (in Sections 5.3, 5.4, and 5.5) are motivated by\n   deployment and operational considerations.\n\n5.1.  Accurate Validation\n\n   Any new intra-domain SAV mechanism must improve SAV accuracy over\n   existing intra-domain SAV mechanisms.  This improvement can be\n   reflected in reduced improper blocks (false positives), reduced\n   improper permits (false negatives), or both.  Furthermore, it must\n   seek to mitigate improper blocks and improve the ability to reject\n   spoofed traffic in the gap scenarios described in Section 4.  To\n   support this, additional information beyond the local FIB, such as\n   SAV-specific information, may be needed to make validation decisions\n   and generate accurate SAV rules.\n\n5.2.  Automatic Updates\n\n   Any new intra-domain SAV mechanism must be capable of automatically\n   collecting and processing relevant information and updating the\n   corresponding SAV rules in response to relevant information changes.\n   Automation helps reduce operational complexity and maintenance\n   overhead while allowing some initial configuration to improve SAV\n   accuracy.  This ensures the mechanism is deployable in practical\n   networks without introducing an excessive management burden.\n\n5.3.  Incremental Deployment Support\n\n   Any new intra-domain SAV mechanism must support incremental\n   deployment and provide measurable benefits even when deployed on only\n   a subset of external interfaces facing hosts or customer networks\n   with no AS.\n\n5.4.  No Adverse Impact on Routing Convergence and Fast Reroute\n\n   If any new intra-domain SAV mechanism requires disseminating SAV-\n   specific information among intra-domain routers via a protocol, it\n   must not adversely affect the convergence of existing routing\n   protocols or the operation of fast-reroute mechanisms.\n\n5.5.  Authentication of Information Used for SAV\n\n   Any new intra-domain SAV mechanism must use information that is\n   authenticated or trusted, either through verification of its\n   integrity and authenticity or via an established trust relationship\n   with the information source.\n\n6.  Security Considerations\n\n   This document discusses the problems with existing intra-domain SAV\n   practices and identifies informational requirements for new intra-\n   domain SAV mechanisms.  As it does not specify any new protocol/\n   mechanism or protocol extension, it does not introduce new security\n   considerations.\n\n7.  IANA Considerations\n\n   This document has no IANA actions.\n\n8.  References\n\n8.1.  Normative References\n\n   [RFC2827]  Ferguson, P. and D. Senie, \"Network Ingress Filtering:\n              Defeating Denial of Service Attacks which employ IP Source\n              Address Spoofing\", BCP 38, RFC 2827, DOI 10.17487/RFC2827,\n              May 2000, <https://www.rfc-editor.org/info/rfc2827>.\n\n   [RFC3704]  Baker, F. and P. Savola, \"Ingress Filtering for Multihomed\n              Networks\", BCP 84, RFC 3704, DOI 10.17487/RFC3704, March\n              2004, <https://www.rfc-editor.org/info/rfc3704>.\n\n   [RFC5210]  Wu, J., Bi, J., Li, X., Ren, G., Xu, K., and M. Williams,\n              \"A Source Address Validation Architecture (SAVA) Testbed\n              and Deployment Experience\", RFC 5210,\n              DOI 10.17487/RFC5210, June 2008,\n              <https://www.rfc-editor.org/info/rfc5210>.\n\n   [RFC7513]  Bi, J., Wu, J., Yao, G., and F. Baker, \"Source Address\n              Validation Improvement (SAVI) Solution for DHCP\",\n              RFC 7513, DOI 10.17487/RFC7513, May 2015,\n              <https://www.rfc-editor.org/info/rfc7513>.\n\n8.2.  Informative References\n\n   [cable-verify]\n              Cisco, \"Cable Source-Verify and IP Address Security\",\n              January 2021, <https://www.cisco.com/c/en/us/support/docs/\n              broadband-cable/cable-security/20691-source-verify.html>.\n\n   [CAIDA-spoofer]\n              CAIDA, \"State of IP Spoofing\",\n              <https://spoofer.caida.org/summary.php?>.\n\n   [IPSG]     Cisco, \"Configuring DHCP Features and IP Source Guard\",\n              August 2008,\n              <https://www.cisco.com/c/en/us/td/docs/switches/lan/\n              catalyst2960/software/release/12-\n              2_53_se/configuration/guide/2960scg/swdhcp82.html>.\n\nAcknowledgements\n\n   The authors thank Jared Mauch, Joel Halpern, Aijun Wang, Michael\n   Richardson, Gert Doering, Tony Przygienda, Yingzhen Qu, James\n   Guichard, Ron Bonica, Xueyan Song, and others for their valuable\n   comments.  The authors also thank Kotikalapudi Sriram for his\n   suggestions on the definition of \"intra-domain SAV\".  The authors\n   thank the IETF directorates and the IESG for their reviews and\n   comments, which helped improve the clarity of this document.\n\nAuthors' Addresses\n\n   Lancheng Qin\n   Zhongguancun Laboratory\n   Beijing\n   China\n   Email: qinlc@mail.zgclab.edu.cn\n\n\n   Dan Li\n   Tsinghua University\n   Beijing\n   China\n   Email: tolidan@tsinghua.edu.cn\n\n\n   Jianping Wu\n   Tsinghua University\n   Beijing\n   China\n   Email: jianping@cernet.edu.cn\n\n\n   Mingqing Huang\n   Zhongguancun Laboratory\n   Beijing\n   China\n   Email: huangmq@mail.zgclab.edu.cn\n\n\n   Nan Geng\n   Huawei\n   Beijing\n   China\n   Email: gengnan@huawei.com\n","snippet":"","snippet_marked":"","source":"RFC Editor","citation":"https://www.rfc-editor.org/rfc/rfc10078","license":"IETF Trust / RFC Editor terms","year":"","url":"/record/10078","fields":{"status":"INFORMATIONAL","stream":"IETF","wg":"savnet","date":"October 2026","obsoletes":"","updates":""}},"generated_at":"2026-11-22T20:18:35Z"}