<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
<!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC7471 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7471.xml">
<!ENTITY RFC8174 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
<!ENTITY RFC8570 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8570.xml">
<!ENTITY RFC8571 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8571.xml">
<!ENTITY RFC8754 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8754.xml">
<!ENTITY RFC9502 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9502.xml">
<!ENTITY RFC5305 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5305.xml">
<!ENTITY RFC4203 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4203.xml">
<!ENTITY RFC9346 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9346.xml">
<!ENTITY RFC5120 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5120.xml">
<!ENTITY RFC9552 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9552.xml">
]>
<rfc submissionType="IETF" docName="draft-gandhi-lsr-ber-01" category="std" ipr="trust200902" consensus="true">
    <!-- Generated by id2xml 1.5.0 on 2020-02-06T01:41:26Z -->
    <?rfc compact="yes"?>
    <?rfc text-list-symbols="oo*+-"?>
    <?rfc subcompact="no"?>
    <?rfc sortrefs="no"?>
    <?rfc symrefs="yes"?>
    <?rfc strict="yes"?>
    <?rfc toc="yes"?>
    <front>
        <title abbrev="IS-IS, OSPF and BGP-LS BER Extensions"> IS-IS, OSPF and BGP-LS Traffic Engineering and Flexible Algorithm Extensions for Utilizing Bit Error Rate Metrics</title>
    <seriesInfo name="Internet-Draft" value="draft-gandhi-lsr-ber-01"/>    

    <author fullname="Rakesh Gandhi" initials="R." role="editor" surname="Gandhi">
    <organization>Cisco Systems, Inc.</organization>
    <address>
    <postal><street>Canada</street>
    </postal>
        <email>rgandhi@cisco.com</email>
    </address>
    </author>

    <date year="2026"/>
    <workgroup>LSR Working Group</workgroup>
    <abstract>
    <t>
This document describes extensions to IS-IS, OSPF, and BGP-LS Traffic Engineering to distribute the Bit Error Rate (BER) and Packet Error Rate (PER) metrics for the links that can be used for flexible algorithm and path selection purpose. 
    <t>
    </t>
   Note that this document only covers the mechanisms with which
   network-performance information is distributed.  The mechanisms for
   measuring network performance or acting on that information, once
   distributed, are outside the scope of this document.
    </t>
    </abstract>
    </front>

    <middle>

   <section title="Introduction" anchor="sect-1">
<t>
Networks may experience transmission bit errors due to various factors, such as poor fiber quality. The bit error can be a single bit error or a burst of bit errors at a time. 
Bit errors include layer-2 bit errors (e.g., causing CRC errors) or layer-3 and layer-4 bit errors (e.g., causing checksum failures).
It is feasible to measure the Bit Error Rate (BER) and Packet Error Rate (PER) of the links using measurement packets. 
However, the measured BER and PER metrics are currently not used in flexible-algorithm and traffic engineering as they are not advertised in IS-IS, OSPF or BGP-LS. 
</t>

<t> 
<xref target="RFC8570" format="default"/> for IS-IS, <xref target="RFC7471" format="default"/> for OSPF, and <xref target="RFC8571" format="default"/> for BGP-LS, define TE metrics extensions for distributing latency, loss, and bandwidth metrics. These documents, however, do not define extensions for distributing BER and PER metrics.
</t>

<t>
In this document, IS-IS, OSPF, and BGP-LS extensions are defined to advertise the BER and PER metrics for the links in the network that can be used for flexible algorithm and TE. Also, IS-IS, OSPF and BGP-LS extensions are defined to advertise anomaly state of the links that can be used to avoid the links with anomaly state.
 </t>

   </section>

   <section title="Conventions Used in This Document" anchor="sect-2">
       
   <section title="Requirements Language" anchor="sect-2.1">

   <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" format="default"/> <xref target="RFC8174" format="default"/>
   when, and only when, they appear in all capitals, as shown here.
   </t>

    </section>

    <section title="Abbreviations" anchor="sect-2.2">

    <t> BER:    Bit Error Rate </t>

    <t> EMA:    Exponential Moving Average </t>

    <t> MTU:    Maximum Transmission Unit </t>

    <t> PER:    Rate of Packets with Bit Errors </t>

    <t> TLV:    Type-Length-Value </t>

    </section>

    </section>

    <section title="Overview" anchor="sect-3">
<t>
In this document, IS-IS, OSPF, and BGP-LS extensions are defined to advertise the BER and PER metrics for the links in the network that can be used for flexible algorithm and TE. Also, IS-IS, OSPF and BGP-LS extensions are defined to advertise anomaly state of the links that can be used to avoid the links with anomaly state.
</t>

<t>
Various BER metrics are distributed including:
</t>
<t>
(1) Average BER 
</t>
<t>
(2) Maximum BER 
</t>
<t>
(3) Minimum BER 
</t>
<t>
(4) Exponential Moving Average of BER 
</t>
<t>
(5) Variance of BER (difference of minimum and average, for example) 
</t>
<t>
(6) BER anomaly state 
</t>

<t>
Various PER metrics are distributed including:
</t>
<t>
(1) Average PER
</t>
<t>
(2) Maximum PER
</t>
<t>
(3) Minimum PER
</t>
<t>
(4) Exponential Moving Average EMA) of PER
</t>
<t>
(5) Variance of PER metrics (difference of minimum and average, for example) 
</t>
<t>
(6) PER anomaly state 
</t>

<t>
Editor's note: The PER metric can be added in the existing packet loss metric (instead of using it as a separate metric).
However, the BER metric can provide different characteristics of the network, as depending on the BER pattern (bursty or single), there can be high BER but low packet loss, and vice versa.
</t>

<t>
Editor's note: The BER and PER metrics of the links can be used as generic metrics in IS-IS, OSPF and BGP-LS. 
</t>

    </section>

    <section title="IS-IS Extensions" anchor="sect-4">
<t>
This document extends the sub-TLV structure define in <xref target="RFC8570" format="default"/>.
This document registers new IS-IS TE sub-TLVs in the "Sub-TLVs for TLVs 22, 23, 141, 222, and 223" registry.  
These new sub-TLVs provide ways to distribute network-performance information. 
The extensions in this document build on the extensions provided in IS-IS TE <xref target="RFC5305" format="default"/> and GMPLS <xref target="RFC4203" format="default"/>.
</t>
<t>
The Extended IS Reachability TLV (type 22) (defined in <xref target="RFC5305" format="default"/>), Inter-AS Reachability TLV (also called "inter-AS reachability information TLV") (type 141) (defined in <xref target="RFC9346" format="default"/>), and MT-ISN TLV (type 222) (defined in <xref target="RFC5120" format="default"/>) have nested sub-TLVs that permit the TLVs to be readily extended.  This document registers several sub-TLVs:
</t>
<t>
      Type    Description
</t>
<t>
      ----------------------------------------------------
</t>
<t>
      TBA1    Unidirectional Link Average BER
</t>
<t>
      TBA2    Unidirectional Link Average PER

</t>
<t>
Example Sub-TLV for distributing BER metric in IS-IS is shown in Figure 1. 
</t>
<t>

   <figure anchor="is-is-ber">
        <name>IS-IS Unidirectional Average BER Metric Sub-TLV </name>
  <artwork name="" type="" align="left" alt=""><![CDATA[
   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=4    |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |A|  RESERVED   |                     BER                       |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      ]]></artwork>
    </figure>

</t>
<t>
A bit
</t>
<t>
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>
Unit for BER and PER Metrics
</t>
<t>
This 24-bit field carries BER or PER as a percentage over a configurable interval. The basic unit is 0.000003%, where (2^24 - 2) is 50.331642%. 
This value is the highest percentage that can be expressed (the assumption that high-speed links with over 50% BER/PER are unusable). 
Measured values that are larger than the field maximum SHOULD be encoded as the maximum value. 
</t>
<t>
The BER metric added is the exponential moving average (EMA) of the BER in order to suppress the frequent advertisements.
The metric is only distributed when user-configured threshold is crossed for the same reason.
This applies to PER metric as well.
</t>

    </section>

    <section title="OSPF Extensions" anchor="sect-5">
<t>
OSPF extensions for TE are defined in <xref target="RFC7471" format="default"/>.
This document defines several additional sub-TLVs for the Link TLV:
</t>
<t>
      Type    Description
</t>
<t>
      ----------------------------------------------------
</t>
<t>
      TBA3    Unidirectional Link Average BER
</t>
<t>
      TBA4    Unidirectional Link Average PER
</t>

<t>
Example Sub-TLV for distributing BER metric in OSPF is shown in Figure 2. 
</t>

   <figure anchor="ospf-ber">
        <name>OSPF Unidirectional Average BER Metric Sub-TLV </name>
  <artwork name="" type="" align="left" alt=""><![CDATA[
   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 = 4             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |A|  RESERVED   |                   BER                         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      ]]></artwork>
    </figure>

<t>
The A flag and Unit of BER and PER metrics are defined the same way as for IS-IS.
</t>

    </section>

    <section title="BGP-LS Extensions" anchor="sect-6">
<t>
The IGP/TE metrics in BGP Link-State are defined in <xref target="RFC8571" format="default"/>.
New BGP-LS Link Attribute TLVs are defined for BER. TLV formats follow the rules defined in <xref target="RFC9552" format="default"/>.
</t>
<t>
    Value          TLV Code Point      
</t>
<t>
    --------------------------------------------------
</t>
<t>
    TBA5            Unidirectional Link Average BER
</t>
<t>
    TBA6            Unidirectional Link Average PER
</t>

<t>
Example TLV for distributing BER metric in BGP-LS is shown in Figure 3 below.
</t>

   <figure anchor="bgp-ls-ber">
        <name>BGP-LS Unidirectional Average BER Metric Sub-TLV </name>
  <artwork name="" type="" align="left" alt=""><![CDATA[
   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 = 4            |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |  RESERVED     |               BER                             |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      ]]></artwork>
    </figure>

<t>
The A flag and Unit of BER and PER metrics are defined the same way as for IS-IS.
</t>

    </section>

    <section title="Flexible Algorithm Type Extensions" anchor="sect-7">

<t>
IGP Flexible algorithm is defined in RFC 9502 and RFC 9350. 
New IS-IS and OSPF Flexible algorithm type extensions are defined using the BER and PER metrics of the links.
</t>
<t>
Editor's note: Additional details on the procedure will be added in the future revision of this document.
</t>

    </section>

    <section title="Security Considerations" anchor="sect-8">
<t>
The security considerations specified in <xref target="RFC8571" format="default"/>, <xref target="RFC8570" format="default"/>, 
and <xref target="RFC7471" format="default"/> apply to the procedure and extensions defined in this document.
</t>
    </section>

    <section title="IANA Considerations" anchor="sect-9">
<t>
IANA maintains the registry for the sub-TLVs for IS-IS.  IANA is requested to allocate 
the following sub-TLVs in the "Sub-TLVs for TLVs 22, 23, 141, 222, and 223" registry:
</t>

    <table anchor="iana-tlv-type-tbl-is-is" align="center">
       <name>IS-IS Sub-TLV Types</name>
        <thead>
          <tr>
            <th align="left">Value</th>
            <th align="center">Description</th>
            <th align="left">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">TBA1 </td>
            <td align="center">Unidirectional Link Average BER Metric</td>
            <td align="left">This document</td>
          </tr>
          <tr>
            <td align="left">TBA2 </td>
            <td align="center">Unidirectional Link Average PER Metric</td>
            <td align="left">This document</td>
          </tr>
        </tbody>
    </table>

    <t>
    IANA maintains the registry for the sub-TLVs for OSPF link TLV.
    IANA is requested to allocate the following sub-TLVs for the OSPF link TLV.
    </t>

    <table anchor="iana-tlv-type-tbl-ospf" align="center">
       <name>OSPF Sub-TLV Types</name>
        <thead>
          <tr>
            <th align="left">Value</th>
            <th align="center">Description</th>
            <th align="left">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">TBA3 </td>
            <td align="center">Unidirectional Link Average BER Metric</td>
            <td align="left">This document</td>
          </tr>
          <tr>
            <td align="left">TBA4 </td>
            <td align="center">Unidirectional Link Average PER Metric</td>
            <td align="left">This document</td>
          </tr>
        </tbody>
    </table>


    <t>
    IANA maintains the registry for the link attribute TLVs in BGP-LS.
    IANA is requested to allocate the following link attribute TLVs in BGP-LS.
    </t>


       <table anchor="iana-tlv-type-tblbgpls" align="center">
       <name>BGP-LS Link attribute TLV Types</name>
        <thead>
          <tr>
            <th align="left">Value</th>
            <th align="center">Description</th>
            <th align="left">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">TBA5 </td>
            <td align="center">Unidirectional Link Average BER Metric</td>
            <td align="left">This document</td>
          </tr>
          <tr>
            <td align="left">TBA6 </td>
            <td align="center">Unidirectional Link Average PER Metric</td>
            <td align="left">This document</td>
          </tr>
        </tbody>
    </table>

    <t>
Editor's note: Additional Sub-TLVs for carrying minimum, maximum, and variance of the BER and PER metrics will be defined in the future revision of this document.
    </t>

    </section>

    </middle>

    <back>
    <references title="Normative References">
    &RFC2119; 
    &RFC7471;
    &RFC8174; 
    &RFC8570;
    &RFC8571;

    </references>
    <references title="Informative References">
    &RFC5305;
    &RFC4203;
    &RFC9346;
    &RFC5120;
    &RFC9552;

    </references>
    <section title="Acknowledgments" numbered="no" anchor="acknowledgments">
<t>
    TBA.
</t>
    </section>

    </back>

    </rfc>
