<?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="info" docName="draft-li-lsr-isis-link-ber-00" ipr="trust200902">
  <front>
    <title abbrev="IS-IS Extensions for Link Bit Error Ratio">IS-IS Extensions for
    Link Bit Error Ratio</title>

    <author fullname="Chenxi Li" initials="C. " surname="Li">
      <organization>Huawei</organization>

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

          <city>Beijing</city>

          <code>100095</code>

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

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

    <author fullname="Guoqi Xu" initials="G." surname="Xu">
      <organization>Huawei</organization>

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

          <city>Beijing</city>

          <code>100095</code>

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

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

    <author fullname="Zhibo Hu" initials="Z. " surname="Hu">
      <organization>Huawei</organization>

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

          <city>Beijing</city>

          <code>100095</code>

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

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

    <author fullname="Tianran Zhou" initials="Z." surname="Zhou">
      <organization>Huawei</organization>

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

          <city>Beijing</city>

          <code>100095</code>

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

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

    <date day="19" month="October" year="2021"/>

    <abstract>
      <t>In certain networks, network-performance criteria (e.g., latency) are
      becoming as critical to data-path selection as other metrics.
      This document describes extensions to IS-IS Traffic Engineering (TE) 
      Metric Extensions (RFC 8570).
      This draft provides the necessary IS-IS extensions about the
      link bit error ratio (LBER) that need to be used to describe
      network-performance.</t>
    </abstract>

    <note title="Requirements Language">
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
      "SHOULD", "SHOULD 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.</t>
    </note>
  </front>

  <middle>
    <section title="Introduction">
      <t>In certain networks, network-performance criteria (e.g., latency) are
      becoming as critical to data-path selection as other metrics.
      This document describes extensions to IS-IS Traffic Engineering (TE) 
      Metric Extensions (RFC 8570).
      This draft provides the necessary IS-IS extensions about the
      link bit errror ratio (LBER) that need to be used to describe
      network-performance.A new sub-TLV is introduced for IS-IS.</t>

      <t>As other IS-IS TE Metric Extensions (e.g., unidirectional link loss,
      unidirectional link delay), Unidirectional link bit error ratio described in
      this dicument is also meant to be used as part of the operation of the routing
      protocol to enhance Constrained Shortest Path First (CSPF), or for other uses
      such as supplementing the data used by the controller to compute the policy path.</t>
    </section>

    <section title="LBER Extensions to IS-IS">
      <t>This document registers a new IS-IS TE sub-TLV in the "Sub-TLVs for
      TLVs 22, 23, 141, 222, and 223" registry.  This new sub-TLV provides
      ways to distribute LBER.</t>

      <t>This document registers a sub-TLV:</t>
      <t><figure suppress-title="false"
          title="Figure 1">
          <artwork align="center"><![CDATA[
Type    Description
----------------------------------------------------
TBD     Unidirectional Link BIT ERROR RATIO
]]></artwork>
        </figure></t>

      <t>The new sub-TLV include a bit called the Anomalous (or "A") bit.
      When the A bit is clear (or when the sub-TLV does not include an
      A bit), the sub-TLV describes steady-state link performance.</t>
    </section>

    <section title="Sub-TLV Details">
      <section title="Unidirectional Link BIT ERROR RATIO Sub-TLV">
        <t>This sub-TLV advertises the bit error ratio between two
        directly connected IS-IS neighbors.  The link bit error ratio
        advertised by this sub-TLV MUST be the packet bit error from
        the local neighbor to the remote neighbor (i.e., the forward-path loss).
        The format of this sub-TLV is shown in the following diagram:</t>

        <t><figure suppress-title="false"
            title="Figure 2: Unidirectional Link BIT ERROR RATIO Sub-TLV for the IS-IS extension">
            <artwork align="center"><![CDATA[
 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    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+
|A|  RESERVED   |               Link Bit Error Ratio            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+
]]></artwork>
          </figure></t>

        <t>Type: TBD (suggested value 40) is to be assigned by IANA.</t>

        <t>Length: 4.</t>

        <t>A bit:  This field represents the Anomalous (A) bit.  The A bit is
        set when the measured value of this parameter exceeds its
        configured maximum threshold.  The A bit is cleared when the
        measured value falls below its configured reuse threshold.  If the
        A bit is cleared, the sub-TLV represents steady-state link
        performance.</t>
        
        <t>RESERVED:  This field is reserved for future use.  It MUST be set
        to 0 when sent and MUST be ignored when received.</t>

        <t>Link Bit Error Ratio:  This 24-bit field carries Link Bit Error Ratio
        as a percentage of the total traffic sent over a configurable interval.
        The basic unit is 0.000003%, where (2^24 - 2) is 50.331642%.  This
        value is the highest link bit error percentage that can be expressed
        (the assumptions being that (1) precision is more important on
        high-speed links than the ability to advertise link bit error ratio greater
        than this and (2) high-speed links with over 50% bit error are
        unusable).  Therefore, measured values that are larger than the
        field maximum SHOULD be encoded as the maximum value.</t>

        <t>This sub-TLV is optional.</t>
      </section>
    </section>

    <section title="Announcement Thresholds and Filters">
      <t>This document uses the same principle for announcement thresholds and filters
      as described in RFC 8570.</t>
    </section>
    
    <section title="Announcement Suppression">
      <t>This document uses the same principle for announcement suppression as described
      in RFC 8570.</t>
    </section>
    
    <section title="Network Stability and Announcement Periodicity">
      <t>This document uses the same principle for network stability and announcement periodicity
      as described in RFC 8570.</t>
    </section>
    
    <section title="Enabling and Disabling Sub-TLVs">
      <t>Implementations MUST make it possible to enable or disable each sub-TLV 
      based on configuration.</t>
    </section>
    
    <section title="Compatibility">
      <t>Unrecognized sub-TLVs should be silently ignored.</t>
    </section>
      
    <section title="Acknowledgements">
      <t>TBD.</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This document requests that IANA allocates new sub-TLV types as
      defined in Section 2 from the "Sub-TLVs for TLVs 22, 23, 25, 141, 222,
      and 223 (Extended IS reachability, IS Neighbor Attribute, L2 Bundle
      Member Attributes, inter-AS reachability information, MT-ISN, and MT IS
      Neighbor Attribute TLVs)" registry as specified.</t>

      <t><figure align="center" title="Figure 3: Unidirectional LBER">
          <artwork><![CDATA[
Value                  Description                  Reference
---------------------------------------------------------------
TBD                    Unidirectional LBER          This document
]]></artwork>
        </figure></t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>These extensions to IS-IS do not add any new security issues
      to the existing IGP.</t>
    </section>
  </middle>

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

      <?rfc include="reference.RFC.5305"?>
    </references>
  </back>
</rfc>
