<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-wang-grow-bmp-bgp-rib-stats-ext-00"
     ipr="trust200902">
  <front>
    <title abbrev="BMP Stats Ext">BGP Monitoring Protocol (BMP) Statistics
    Types Extension</title>

    <author fullname="Lili Wang" initials="L." surname="Wang">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street>Huawei Bld., No.156 Beiqing Rd.</street>

          <city>Beijing</city>

          <code>100095</code>

          <country>China</country>
        </postal>

        <email>lily.wong@huawei.com</email>
      </address>
    </author>

    <author fullname="Nan Geng" initials="N." surname="Geng">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street>Huawei Bld., No.156 Beiqing Rd.</street>

          <city>Beijing</city>

          <code>100095</code>

          <country>China</country>
        </postal>

        <email>gengnan@huawei.com</email>
      </address>
    </author>

    <author fullname="Lei Li" initials="L." surname="Li">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street>Huawei Bld., No.156 Beiqing Rd.</street>

          <city>Beijing</city>

          <code>100095</code>

          <country>China</country>
        </postal>

        <email>kenny.lilei@huawei.com</email>
      </address>
    </author>

    <author fullname="Shunwan Zhuang" initials="S." surname="Zhuang">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street>Huawei Bld., No.156 Beiqing Rd.</street>

          <city>Beijing</city>

          <region/>

          <code>100095</code>

          <country>China</country>
        </postal>

        <phone/>

        <facsimile/>

        <email>zhuangshunwan@huawei.com</email>

        <uri/>
      </address>
    </author>

    <date day="31" month="December" year="2025"/>

    <abstract>
      <t><xref target="RFC7854"/>, <xref target="RFC8671"/> and <xref
      target="I-D.ietf-grow-bmp-bgp-rib-stats"/> define different BGP
      Monitoring Protocol (BMP) statistics message types to observe events
      that occur on a monitored router. This document defines some additional
      statistics type to monitor BMP Adj-RIB-In, Loc-RIB and Adj-RIB-Out
      Routing Information Bases (RIBs).</t>

      <t/>
    </abstract>

    <note title="Requirements Language">
      <t>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
      <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when,
      they appear in all capitals, as shown here.</t>
    </note>
  </front>

  <middle>
    <section title="Introduction">
      <t>.</t>

      <t>Section 4.8 of <xref target="RFC7854"/> and section 6.2 of <xref
      target="RFC8671"/> define a number of different BGP Monitoring Protocol
      (BMP) statistics types to observe major events that occur on a monitored
      router, and <xref target="I-D.ietf-grow-bmp-bgp-rib-stats"/> defines
      some new statistics type to monitor BMP Adj-RIB-In and Adj-RIB-Out
      Routing Information Bases (RIBs). This document defines some additional
      statistics type to monitor BMP Adj-RIB-In, Loc-RIB and Adj-RIB-Out
      Routing Information Bases (RIBs).</t>

      <t/>
    </section>

    <section title="RIB Monitoring Statistics">
      <t>This section defines different statistics type for Adj-RIB-In and
      Adj-RIB-Out monitoring type. Some of these statistics are also
      applicable to Loc-RIB, The Statistics Format follows the definition in
      Section 3.1 of <xref target="I-D.ietf-grow-bmp-bgp-rib-stats"/>.</t>

      <t/>

      <section title="Adj-RIB-In RIB Monitoring Statistics Definition">
        <t>Type = TBD1: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In rejected due to exceeding the received route threshold.</t>

        <t>Type = TBD2: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In rejected due to insufficient memory.</t>

        <t>Type = TBD3: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In that cannot be downloaded to the FIB module due to
        insufficient forwarding resources.</t>

        <t>Type = TBD4: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In that cannot be downloaded to the FIB module due to
        insufficient label resources or SID resources.</t>

        <t>Type = TBD5: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In rejected due to invalid next-hop.</t>

        <t>Type = TBD6: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In rejected due to next-hop unreachable.</t>

        <t>Type = TBD7: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In that are inactive due to the inability to resolve the
        next-hop tunnel.</t>

        <t>Type = TBD8: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In rejected due to Type 1 Route Leak as defined in <xref
        target="RFC7908"/>: Hairpin Turn with Full Prefix.</t>

        <t>Type = TBD9: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In rejected due to Type 2 Route Leak as defined in <xref
        target="RFC7908"/>: Lateral ISP-ISP-ISP Leak.</t>

        <t>Type = TBD10: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In rejected due to Type 3 Route Leak as defined in <xref
        target="RFC7908"/>: Leak of Transit-Provider Prefixes to Peer.</t>

        <t>Type = TBD11: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In rejected due to Type 4 Route Leak as defined in <xref
        target="RFC7908"/>: Leak of Peer Prefixes to Transit Provider.</t>

        <t>Type = TBD12: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In rejected due to Type 5 Route Leak as defined in <xref
        target="RFC7908"/>: Prefix Re-origination with Data Path to Legitimate
        Origin.</t>

        <t>Type = TBD13: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-In rejected due to Type 6 Route Leak as defined in <xref
        target="RFC7908"/>: Accidental Leak of Internal Prefixes and More-
        Specific Prefixes.</t>

        <t>Type = TBD14: (64-bit Gauge) Current number of routes in
        per-AFI/SAFI post-policy Adj-RIB-In invalidated through the AS_PATH
        Verification <xref target="I-D.ietf-sidrops-aspa-verification"/>. This
        is total number of routes invalidated due to AS_PATH Verification. The
        value is structured as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit
        Gauge.</t>

        <t>Type = TBD15: (64-bit Gauge) Current number of routes in
        per-AFI/SAFI post-policy Adj-RIB-In validated through the AS_PATH
        Verification <xref target="I-D.ietf-sidrops-aspa-verification"/>. This
        is total number of routes validated due to AS_PATH Verification. The
        value is structured as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit
        Gauge.</t>

        <t>Type = TBD16: (64-bit Gauge) Current number of routes in
        per-AFI/SAFI post-policy Adj-RIB-In whose AS_PATH Verification state
        is Unknown due to the AS_PATH Verification <xref
        target="I-D.ietf-sidrops-aspa-verification"/>. The value is structured
        as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit Gauge.</t>

        <t/>
      </section>

      <section title="Adj-RIB-Out RIB Monitoring Statistics Definition">
        <t>Type = TBD17: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-Out rejected due to exceeding the sent route threshold.</t>

        <t>Type = TBD18: Number of routes currently in per-AFI/SAFI pre-policy
        Adj-RIB-Out that cannot be advertised to its peer due to insufficient
        label resources or SID resources.</t>

        <t>Type = TBD19: (64-bit Gauge) Current number of routes in
        per-AFI/SAFI post-policy Adj-RIB-Out invalidated through the AS_PATH
        Verification <xref target="I-D.ietf-sidrops-aspa-verification"/> <xref
        target="I-D.zhang-sidrops-aspa-egress"/>. This is total number of
        routes invalidated due to AS_PATH Verification. The value is
        structured as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit
        Gauge.</t>

        <t>Type = TBD20: (64-bit Gauge) Current number of routes in
        per-AFI/SAFI post-policy Adj-RIB-Out validated through the AS_PATH
        Verification <xref target="I-D.ietf-sidrops-aspa-verification"/> <xref
        target="I-D.zhang-sidrops-aspa-egress"/>. This is total number of
        routes validated due to AS_PATH Verification. The value is structured
        as: 2-byte AFI, 1-byte SAFI, followed by a 64-bit Gauge.</t>

        <t>Type = TBD21: (64-bit Gauge) Current number of routes in
        per-AFI/SAFI post-policy Adj-RIB-Out whose AS_PATH Verification state
        is Unknown due to the AS_PATH Verification <xref
        target="I-D.ietf-sidrops-aspa-verification"/> <xref
        target="I-D.zhang-sidrops-aspa-egress"/>. The value is structured as:
        2-byte AFI, 1-byte SAFI, followed by a 64-bit Gauge.</t>

        <t/>
      </section>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This document requests that IANA assign the following new parameters
      to the BMP parameters name space (https://www.iana.org/assignments/
      bmp-parameters/bmp-parameters.xhtml).</t>

      <t>They will be added in subsequent versions.</t>

      <t/>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>Procedures and protocol extensions defined in this document do not
      affect the BMP security model. All security and authentication
      mechanisms required by Section 11 of <xref target="RFC7854"/>, Section 8
      of <xref target="RFC8671"/>, and Section 7 of <xref target="RFC9069"/>
      are also applicable to the gauges defined in this document. This
      document does not add any additional security considerations.</t>

      <t>Monitored devices SHOULD be configured to implement rate-limited
      reporting of new gauges.</t>

      <t/>
    </section>

    <section title="Contributors ">
      <t>The following people made significant contributions to this
      document:</t>

      <t><figure>
          <artwork align="left"><![CDATA[To be added.

]]></artwork>
        </figure></t>
    </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>The authors would like to acknowledge the review and inputs from
      xxx.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.2119"?>

      <?rfc include='reference.RFC.4271'?>

      <?rfc include='reference.RFC.4760'?>

      <?rfc include='reference.RFC.7908'?>

      <?rfc include='reference.RFC.8174'?>

      <?rfc include='reference.RFC.7854'?>

      <?rfc include='reference.RFC.8671'?>

      <?rfc include='reference.RFC.9069'?>

      <?rfc include='reference.I-D.ietf-grow-bmp-bgp-rib-stats'?>

      <?rfc include='reference.I-D.ietf-sidrops-aspa-verification'?>

      <?rfc include='reference.I-D.zhang-sidrops-aspa-egress'?>
    </references>

    <references title="Informative References"/>
  </back>
</rfc>
