



idr                                                              T. Tong
Internet-Draft                                              China Unicom
Intended status: Standards Track                                   D. Li
Expires: 8 July 2026                                 Tsinghua University
                                                                 N. Geng
                                                                  Huawei
                                                                 N. Wang
                                                            China Unicom
                                                               S. Zhuang
                                                                  Huawei
                                                                 J. Zhao
                                                            China Unicom
                                                          4 January 2026


     Advertisement of Multi-Sourced SAV Rules using BGP Link-State
                   draft-tong-idr-bgp-ls-sav-rule-03

Abstract

   This document describes the protocol extensions of BGP Link-State to
   collect source address validation (SAV) rules generated by different
   protocols/mechanisms, to facilitate multi-sourced SAV rules
   monitoring and management.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 8 July 2026.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors.  All rights reserved.





Tong, et al.               Expires 8 July 2026                  [Page 1]

Internet-Draft      BGP-LS for Advertising SAV Rules        January 2026


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  BGP-LS NLRI Advertisement for SAV Rules . . . . . . . . . . .   3
     2.1.  SAV Rule NLRIs  . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  SAV Rule Descriptors TLVs . . . . . . . . . . . . . . . .   4
       2.2.1.  Interface Name TLV  . . . . . . . . . . . . . . . . .   5
       2.2.2.  Interface Group TLV . . . . . . . . . . . . . . . . .   5
       2.2.3.  SAV Prefix TLV  . . . . . . . . . . . . . . . . . . .   6
   3.  BGP-LS Attribute for SAV Mode . . . . . . . . . . . . . . . .   7
   4.  BGP-LS Attribute for SAV Actions  . . . . . . . . . . . . . .   7
   5.  Example of Validation Modes and SAV rule NLRI
           Configuration . . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  IBA-SAV: Interface-based prefix allowlist . . . . . . . .   8
     5.2.  IBB-SAV: Interface-based prefix blocklist . . . . . . . .   8
     5.3.  PBA-SAV: Prefix-based interface allowlist . . . . . . . .   9
     5.4.  PBB-SAV: Prefix-based interface blocklist . . . . . . . .   9
   6.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  Manageability Considerations  . . . . . . . . . . . . . . . .  10
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  "BGP-LS NLRI-Types" registry  . . . . . . . . . . . . . .  10
     8.2.  "BGP-LS SAV Rule Descriptors TLVs" registry . . . . . . .  10
     8.3.  "BGP-LS SAV Mode Attribute TLV" registry  . . . . . . . .  10
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Source Address Validation (SAV) can efficiently prevent source
   address spoofing-based attacks.  SAV rules, which indicate the valid/
   invalid incoming interfaces of a specific source IP address or source
   IP prefix, are installed on routers for checking the source addresses
   of received packets.





Tong, et al.               Expires 8 July 2026                  [Page 2]

Internet-Draft      BGP-LS for Advertising SAV Rules        January 2026


   SAV rules can be generated by static configuration, management tools,
   or based on different routing protocols such as OSPFv2, OSPFv3, IS-
   IS, BGP, or their extensions [I-D.ietf-savnet-intra-domain-architectu
   re][I-D.ietf-savnet-inter-domain-architecture].  Due to the
   requirements of application scenarios, a router may use more than one
   tool at the same time to obtain SAV rules.  Therefore, the rules on
   the router will be multi-sourced, which complicates management.  What
   is more challenging is that there may exist conflicts among these
   multi-sourced rules and the rules can be dynamic.

   To facilitate SAV rules monitoring and management, this document
   proposes to extend BGP-LS ([RFC9552]) for advertising SAV rules on
   routers to a centralized server.  The centralized server can
   effectively collect multi-sourced SAV rules from routers.  For the
   purpose of advertising SAV rules within BGP-LS advertisements, two
   new NLRIs called SAV Rule NLRIs are proposed for IPv4 and IPv6,
   respectively.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  BGP-LS NLRI Advertisement for SAV Rules

   The "Link-State NLRI" defined in [RFC9552] is extended to carry the
   SAV rule information.  The format of "Link-State NLRI" is defined in
   [RFC9552] as follows:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |            NLRI Type          |     Total NLRI Length         |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                                                               |
       //                  Link-State NLRI (variable)                 //
       |                                                               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                         Figure 1: Link-State NLRI

   This document defines two new NLRI Types known as SAV Rule NLRIs
   (values are TBD) for the advertisement of SAV rule Information.





Tong, et al.               Expires 8 July 2026                  [Page 3]

Internet-Draft      BGP-LS for Advertising SAV Rules        January 2026


2.1.  SAV Rule NLRIs

   This document defines SAV Rule NLRI Types with their common format as
   shown in the following figure:

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+
      |  Protocol-ID  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           Identifier                          |
      +                           (8 octets)                          +
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      //            Local Node Descriptors TLVs (variable)            //
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      //            SAV Rule Descriptors TLVs (variable)             //
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                      Figure 2: BGP-LS SAV Rule NLRI

   The fields are defined as follows:

   *  Protocol-ID: Specifies the source of SAV rules in this NLRI.
      Protocol-ID values defined in [RFC9552][RFC9086] can be reused.

   *  Identifier: An 8 octet value as defined in [RFC9552].

   *  Local Node Descriptors TLV: Contains Node Descriptors for the
      nodes storing SAV rules.  This is a mandatory TLV in SAV Rule
      NLRIs.  The Type is 256.  The length of this TLV is variable.  The
      value contains one or more Node Descriptor sub-TLVs defined in
      [RFC9552].

   *  SAV Rule Descriptors TLVs: There can be one or more SAV Rule
      Descriptors TLVs for carrying SAV rules.

2.2.  SAV Rule Descriptors TLVs

   The SAV Rule Descriptor field is a set of TLV triplets.  SAV Rule
   Descriptors TLVs identify a set of SAV rules having the same set of
   valid interfaces as defined in
   [I-D.ietf-savnet-general-sav-capabilities].  The following TLVs are
   valid as SAV Rule Descriptors in the SAV Rule NLRI:







Tong, et al.               Expires 8 July 2026                  [Page 4]

Internet-Draft      BGP-LS for Advertising SAV Rules        January 2026


       +-------------+---------------------+----------+
       |   TLV Code  | Description         |  Length  |
       |    Point    |                     |          |
       +-------------+---------------------+----------+
       |     TBD     | Interface Name      | variable |
       |     TBD     | Interface Group     |    4     |
       |     TBD     | SAV Prefix          | variable |
       +-------------+---------------------+----------+

                     Figure 3: SAV Rule Descriptor TLVs

2.2.1.  Interface Name TLV

   An Interface Name TLV is used to identify one valid interface of the
   source prefixes carried in SAV Prefix TLVs.  The format of Interface
   Name TLV is as follows:

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |              Type             |             Length            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       //                     Interface Name    (variable)            //
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                       Figure 4: Interface Name TLV

   There can be zero, one or more Interface Name TLVs in the SAV Rule
   Descriptor field.

2.2.2.  Interface Group TLV

   An Interface Group TLV is to identify a group of valid interfaces of
   the source prefixes carried in SAV Prefix TLVs.  The format of
   Interface Group TLV is as follows:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |              Type             |             Length            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       //                       Interface Group (4 octets)            //
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                       Figure 5: Interface Group TLV






Tong, et al.               Expires 8 July 2026                  [Page 5]

Internet-Draft      BGP-LS for Advertising SAV Rules        January 2026


   The Interface Group value can have either a local meaning or a global
   meaning.  On the one hand, it can be a local interface property on
   the target routers, and the meaning of it depends on the
   configurations of network administrator
   [I-D.ietf-idr-flowspec-interfaceset].  On the other hand, a global
   meaning Group Identifier field carries an AS number, which represents
   all the interfaces connected to the neighboring AS with the AS
   number.  [I-D.geng-idr-flowspec-sav]

   Interface Group value can also be an Interface ID for identifying a
   specific interface.

   There can be zero, one or more Interface Group TLVs in the SAV Rule
   Descriptor field.  Interface Group TLVs can be used together with
   Interface Name TLVs.

   When there is neither an Interface Name TLV nor an Interface Group
   TLV, the source prefixes carried in SAV Prefix TLVs are considered
   valid for all the interfaces on the router.

2.2.3.  SAV Prefix TLV

   A SAV Prefix TLV carries one IP address prefix (IPv4 or IPv6).  The
   format of SAV Prefix TLV is as follows:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |              Type             |             Length            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       | Prefix Length | IP Prefix (variable)                         //
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                          Figure 6: SAV Prefix TLV

   There can be one or more SAV Prefix TLVs in the SAV Rule Descriptor
   field.  The IPv4 SAV Prefix TLVs will only appear in the IPv4 SAV
   Rule NLRI, and The IPv6 SAV Prefix TLVs are only for the IPv6 SAV
   Rule NLRI

   There can be more than one SAV mechanisms based on the same source
   (identified by Protocol-ID).  In order to distinguish the different
   sources of rules in a more fine-grained manner, the Type field needs
   to be allocated for multiple values, and each value identifies a
   specific SAV mechanism based on the same source identified by
   Protocol-ID.





Tong, et al.               Expires 8 July 2026                  [Page 6]

Internet-Draft      BGP-LS for Advertising SAV Rules        January 2026


3.  BGP-LS Attribute for SAV Mode

   The BGP-LS Attribute, an optional and non-transitive BGP Attribute,
   is used to carry the validation mode information of SAV rules {I-
   D.ietf-savnet-general-sav-capabilities}. The following SAV Mode
   Attribute TLV is defined for the BGP-LS Attribute associated with a
   SAV Rule NLRI:

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |              Type             |             Length            |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |M  |  Reserved |
     +-+-+-+-+-+-+-+-+

                           Figure 7: SAV Mode TLV

   The SAV Mode TLV carries a Mode Flag (M flag is shown in the figure
   and occupies two bits) describing the validation mode attribute.

   *  When M flag is set to 00, the mode is IBA-SAV: interface-based
      prefix allowlist.  The NLRI carries the source prefixes and
      interfaces.  Only the carried prefixes are valid on the carried
      interfaces, and any other prefixes are invalid on these
      interfaces.

   *  When M flag is set to 01, the mode is IBB-SAV: interface-based
      prefix blocklist.  The NLRI carries the source prefixes and
      interfaces.  Only the carried prefixes are invalid on the carried
      interfaces, and any other prefixes are valid on these interfaces.

   *  When M flag is set to 10, the mode is PBA-SAV: prefix-based
      interface allowlist.  The NLRI carries the source prefixes and
      interfaces.  Only the carried interfaces are valid for the carried
      prefixes, and any other interfaces are invalid for those prefixes.
      Any other prefixes will not be validated.

   *  When M flag is set to 11, the mode is PBB-SAV: prefix-based
      interface blocklist.  The NLRI carries the source prefixes and
      interfaces.  Only the carried interfaces are invalid for the
      carried prefixes, and any other interfaces are valid for those
      prefixes.  Any other prefixes will not be validated.

4.  BGP-LS Attribute for SAV Actions

   SAV actions in this document adopt the traffic filtering actions
   defined in [RFC8955] and [RFC8956].



Tong, et al.               Expires 8 July 2026                  [Page 7]

Internet-Draft      BGP-LS for Advertising SAV Rules        January 2026


   Traffic filtering actions defined in [RFC 8955] include traffic-rate-
   bytes, traffic-rate-packets, traffic-action, rt-redirect, and
   traffic-marking, which are applicable to IPv4 and IPv6.  Rt-redirect-
   ipv6 is a new traffic filtering action defined in [RFC 8956], which
   is applicable to IPv6.  The encapsulation formats of SAV actions are
   consistent with the encapsulation formats defined in [RFC 8955] and
   [RFC 8956].

   A SAV rule may match multiple SAV actions, and there may be conflicts
   among these SAV actions.  Section 7.7 of [RFC 8955] describes the
   conflicts among Traffic filtering actions.

5.  Example of Validation Modes and SAV rule NLRI Configuration

   In this section, we provide examples of how to configure SAV rule
   NLRI for the four validation modes.  The SAV rule NLRI can carry
   zero, one, or multiple interfaces/interface groups and one or more
   prefixes.

5.1.  IBA-SAV: Interface-based prefix allowlist

   In this mode, only the prefixes carried in the SAV rule NLRI are
   considered valid on the specified interface.  All other prefixes
   arriving at this interface are considered invalid.

   Example:

   *  SAV rule NLRI: prefix = 192.168.1.0/24, interfaces = [Interface A]

   *  Validation: Any packet with a source prefix of 192.168.1.0/24
      arriving at Interface A is valid.  All other prefixes on Interface
      A are invalid.

5.2.  IBB-SAV: Interface-based prefix blocklist

   In this mode, the prefixes carried in the SAV rule NLRI are
   considered invalid on the specified interface.  All other prefixes
   arriving at this interface are considered valid.

   Example:

   *  SAV rule NLRI: prefix = 10.0.0.0/8, interfaces = [Interface B]

   *  Validation: Any packet with a source prefix of 10.0.0.0/8 arriving
      at Interface B is invalid.  All other prefixes on Interface B are
      valid.





Tong, et al.               Expires 8 July 2026                  [Page 8]

Internet-Draft      BGP-LS for Advertising SAV Rules        January 2026


5.3.  PBA-SAV: Prefix-based interface allowlist

   In this mode, for a specific source prefix, only the interfaces
   carried in the SAV rule NLRI are considered valid.  Packets with this
   source prefix arriving at other interfaces are invalid.  Other
   prefixes are not checked.

   Example:

   *  SAV rule NLRI: prefix = 172.16.0.0/16, interfaces = [Interface C,
      Interface D]

   *  Validation: Packets with a source prefix of 172.16.0.0/16 are
      valid only if they arrive at Interface C or Interface D.  This
      prefix arriving at other interfaces is invalid.  Other prefixes
      are not checked.

5.4.  PBB-SAV: Prefix-based interface blocklist

   In this mode, for a specific source prefix, the interfaces carried in
   the SAV rule NLRI are considered invalid.  Packets with this source
   prefix arriving at other interfaces are valid.  Other prefixes are
   not checked.

   Example:

   *  SAV rule NLRI: prefix = 192.168.2.0/24, interfaces = [Interface E]

   *  Validation: Packets with a source prefix of 192.168.2.0/24
      arriving at Interface E are invalid.  This prefix arriving at
      other interfaces is valid.  Other prefixes are not checked.

6.  Procedures

   SAV rules only exist on the routers running SAV mechanisms/protocols
   and the controller, these routers are usually access routers or
   boundary routers.  This document describes extensions to the BGP-LS
   NLRI.  The Routers running SAV mechanisms/protocols establish BGP-LS
   sessions with the controller respectively to report multi-sourced SAV
   rules.

                    +--------------------------+
                    |        Controller        |
                    +--------------------------+
                      /                      \
                     /                        \  BGP-LS advertisements for SAV Rule NLRIs +-----------------------/--------------------------\-----------------+ |   AS100              /                            \                |   |                  +---------+                +---------+            |  |                  | Router1 | -------------- | Router2 |            |  |                  +---------+                +---------+            |   |                     |                              |               | |                     |                              |               | |                     |                              |               | |                     |                              |               | |                  +---------+                +---------+            |  |                  | Router3 | -------------- | Router4 |            |   |                  +---------+                +---------+            |  |                                                                    |   +--------------------------------------------------------------------+

          Figure 8: Advertisement of SAV Rules using BGP-LS



Tong, et al.               Expires 8 July 2026                  [Page 9]

Internet-Draft      BGP-LS for Advertising SAV Rules        January 2026


   Based on Figure 8, the process of reporting SAV rules via BGP-LS is
   described as follows: Step 1: R1 and R2 run SAV mechanism/protocol,
   and generate multi-sourced SAV rules.  Step 2: R1 and R2 respectively
   establish BGP-LS sessions with the controller.  Step 3: R1 and R2
   generate BGP-LS advertisements for the SAV Rule NLRIs.  Step 4: R1
   and R2 report multi-sourced SAV rules to the controller through the
   sav rule NLRIs (as defined in Section 2).  This enables the
   controller to monitor and manage multi-sourced SAV rules.

7.  Manageability Considerations

   The Existing BGP operational and management procedures apply to this
   document.  No new procedures are defined in this document.  The
   considerations as specified in [RFC9552] apply to this document.

8.  IANA Considerations

   This section describes the code point allocation by IANA for this
   document.

8.1.  "BGP-LS NLRI-Types" registry

   This document requests assigning code-points from the registry for
   SAV Rule NLRIs:

   +------+---------------------------+
   | Type | NLRI Type                 |
   +------+---------------------------+
   | TBD  | IPv4 SAV Rule NLRI        |
   | TBD  | IPv6 SAV Rule NLRI        |
   +------+---------------------------+

8.2.  "BGP-LS SAV Rule Descriptors TLVs" registry

   This document requests assigning code-points from the registry for
   BGP-LS SAV Rule Descriptors TLVs based on Figure 3.

8.3.  "BGP-LS SAV Mode Attribute TLV" registry

   This document requests assigning a code-point from the registry for
   the BGP-LS SAV Mode attribute TLV.

9.  Security Considerations

   Procedures and protocol extensions defined in this document do not
   affect the base BGP security model.  See [RFC6952] for details.  The
   security considerations of the base BGP-LS specification as described
   in [RFC9552] also apply.



Tong, et al.               Expires 8 July 2026                 [Page 10]

Internet-Draft      BGP-LS for Advertising SAV Rules        January 2026


10.  References

10.1.  Normative References

   [RFC9552]  Talaulikar, K., Ed., "Distribution of Link-State and
              Traffic Engineering Information Using BGP", RFC 9552,
              DOI 10.17487/RFC9552, December 2023,
              <https://www.rfc-editor.org/info/rfc9552>.

   [I-D.ietf-savnet-general-sav-capabilities]
              Huang, M., Cheng, W., Li, D., Geng, N., and L. Chen,
              "General Source Address Validation Capabilities", Work in
              Progress, Internet-Draft, draft-ietf-savnet-general-sav-
              capabilities-02, 10 October 2025,
              <https://datatracker.ietf.org/doc/html/draft-ietf-savnet-
              general-sav-capabilities-02>.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

10.2.  Informative References

   [I-D.ietf-savnet-intra-domain-architecture]
              Li, D., Wu, J., Qin, L., Geng, N., and L. Chen, "Intra-
              domain Source Address Validation (SAVNET) Architecture",
              Work in Progress, Internet-Draft, draft-ietf-savnet-intra-
              domain-architecture-03, 13 October 2025,
              <https://datatracker.ietf.org/doc/html/draft-ietf-savnet-
              intra-domain-architecture-03>.

   [I-D.ietf-savnet-inter-domain-architecture]
              Li, D., Chen, L., Geng, N., Liu, L., and L. Qin, "Inter-
              domain Source Address Validation (SAVNET) Architecture",
              Work in Progress, Internet-Draft, draft-ietf-savnet-inter-
              domain-architecture-02, 31 August 2025,
              <https://datatracker.ietf.org/doc/html/draft-ietf-savnet-
              inter-domain-architecture-02>.

   [I-D.ietf-idr-flowspec-interfaceset]
              Litkowski, S., Simpson, A., Patel, K., and J. Haas,
              "Applying BGP flowspec rules on a specific interface-set",
              Work in Progress, Internet-Draft, draft-ietf-idr-flowspec-



Tong, et al.               Expires 8 July 2026                 [Page 11]

Internet-Draft      BGP-LS for Advertising SAV Rules        January 2026


              interfaceset-06, 2 September 2025,
              <https://datatracker.ietf.org/doc/html/draft-ietf-idr-
              flowspec-interfaceset-06>.

   [I-D.geng-idr-flowspec-sav]
              Geng, N., Li, D., tongtian124, and M. Huang, "BGP Flow
              Specification for Source Address Validation", Work in
              Progress, Internet-Draft, draft-geng-idr-flowspec-sav-06,
              17 October 2025, <https://datatracker.ietf.org/doc/html/
              draft-geng-idr-flowspec-sav-06>.

Authors' Addresses

   Tian Tong
   China Unicom
   Beijing
   China
   Email: tongt5@chinaunicom.cn


   Dan Li
   Tsinghua University
   Beijing
   China
   Email: tolidan@tsinghua.edu.cn


   Nan Geng
   Huawei
   Beijing
   China
   Email: gengnan@huawei.com


   Nan Wang
   China Unicom
   Beijing
   China
   Email: wangn161@chinaunicom.cn


   Shunwan Zhuang
   Huawei
   Beijing
   China
   Email: zhuangshunwan@huawei.com





Tong, et al.               Expires 8 July 2026                 [Page 12]

Internet-Draft      BGP-LS for Advertising SAV Rules        January 2026


   Jing Zhao
   China Unicom
   Beijing
   China
   Email: zhaoj501@chinaunicom.cn














































Tong, et al.               Expires 8 July 2026                 [Page 13]
