<?xml version='1.0' encoding='utf-8'?>
<?xml-model href="rfc7991bis.rnc"?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<rfc
      xmlns:xi="http://www.w3.org/2001/XInclude"
      category="std"
      docName="draft-ietf-manet-dlep-radio-quality-05"
      ipr="trust200902"
      obsoletes=""
      updates=""
      submissionType="IETF"
      xml:lang="en"
      tocInclude="true"
      tocDepth="4"
      symRefs="true"
      sortRefs="true"
      version="3"
      consensus="true">
<front>
  <title abbrev="DLEP PHY quality">DLEP Radio Quality Extension</title>
  <seriesInfo name="Internet-Draft" value="draft-ietf-manet-dlep-radio-quality-05"/>
  <author fullname="Henning Rogge" initials="H.R." surname="Rogge">
      <organization>Fraunhofer FKIE</organization>
      <address>
        <postal>
          <street>Fraunhofer Strasse 20</street>
          <city>Wachtberg</city>
          <region/>
          <code>53343</code>
          <country>DE</country>
        </postal>
        <email>henning.rogge@fkie.fraunhofer.de</email>
    </address>
    </author>
  <date year="2026"/>
  <area>Routing</area>
  <workgroup>Manet</workgroup>
  <keyword>DLEP</keyword>
  <keyword>PHY</keyword>
  <keyword>TLV</keyword>
  <abstract>
      <t>This document defines an extension to the Dynamic Link Exchange Protocol (DLEP) to provide the quality of incoming radio signals.</t>
    </abstract>
  </front>
  <middle>
    <section numbered="true" toc="default">
      <name>Introduction</name>
      <t>The dynamic Link Exchange Protocol (DLEP) is defined in
        <xref target="RFC8175" format="default"/>.
        It provides the exchange of link-related control information
        between DLEP peers. DLEP peers are comprised of a modem and
        a router.  DLEP defines a base set of mechanisms as well as
        support for possible extensions. This document defines one such
        extension.</t>
      <section numbered="true" toc="default">
        <name>Requirements Language</name>
        <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>
      </section>
    </section>
    <section numbered="true" toc="default">
      <name>Extension Usage and Identification</name>
      <t>The use of the Radio Quality Extension SHOULD be
        configurable. To indicate that the Radio Quality Extension
        is to be used, an implementation MUST include the Radio Quality
        Extension Type Value in the Extensions Supported Data Item. The Extensions Supported Data Item is sent and processed according to
        <xref target="RFC8175" format="default"/>.</t>
    </section>
    <section numbered="true" toc="default">
      <name>Radio Quality Data Items</name>
      <t>This section describes the quality related Data Items of this extension.</t>
      <t>All Data Items available in this extension provide access to the radios physical layer measurements related to signal quality. Because of different designs of Radio PHY layers,
        this quality can be expressed in different ways, by referring to signal-to-noise ratio or by measuring the biterror rate (e.g. by using a forward error correction).
        Both of these possible formats are very valuable for calculating MANET metrics for radio networks with moving nodes and low datarates, e.g. VHF radio networks. Estimating channel quality
        based on packet loss can be impractical, because the estimated value changes too fast (because of movement) compared to the number of received frames. Biterror rate (and Signal Strength)
        can provide the additional information necessary to build a reasonable stable and agile metric. Biterror rate (before error correction) is a more generic way to represent this value, because
        it is a radio independent measurement.</t>
      <t>The biterror rate might be directly measured by the radio or be calculated by a measured Signal-to-Noise radio and the known (to the vendor of the radio) E0/N-to-BER curve of each used modulation coding scheme. It was selected as the mandatory data item because it is easier to compare between different radios than two Signal-to-Noise ratios.</t>
      <t>The Biterror Rate data item is mandatory when using the Radio Quality extension. All other TLVs presented in this document are optional.</t>
      <section numbered="true" toc="default">
        <name>Radio Biterror Rate Data Item</name>
        <t>Radio Biterror Rate Data Item is a mandatory TLV that contains information about the radio receivers estimate of how often a transmitted bit will be received wrong. This value can often be either directly measured
          by the radio by comparing the result of a forward-error-correction to the original received data or calculated from the received signal-to-noise ratio and knowledge about the current
          modulation coding scheme. This Data Item can be both interface and neighbor specific.</t>
        <t>This Data Item MUST be used in the Session Initialization Response message and MAY be used in Session Update messages.</t>
        <t>If the radio supports destination specific quality information, this Data Item MUST be used in Destination Up messages and MAY be used in Destination Update and Destination Announce Response messages.</t>
        <t>The format of the Radio Biterror Rate Data Item is:</t>
        <figure anchor="radio_biterror">
          <artwork align="left" name="" type="" 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type                | Length                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|    Biterror   |
+-+-+-+-+-+-+-+-+
          ]]></artwork>
        </figure>
        <dl>
          <dt>Data Item Type:</dt><dd>TBD1</dd>
          <dt>Length:</dt><dd>1</dd>
          <dt>Biterror:</dt><dd>Biterror rate measured as a negative exponent multiplied by 10 (to base 10),
            e.g. "40" for an error rate of 1 to 10^-4. An error rate of 0 is encoded with a 255.</dd>
        </dl>
      </section>
      <section numbered="true" toc="default">
        <name>Radio SNR Data Item</name>
        <t>Radio SNR Data Item contains information about which signal to noise ratio the
          radio measured. This Data Item can be both interface and neighbor specific.</t>
        <t>If supported this Data Item MUST be used in the Session Initialization Response and MAY be used in Session Update messages.</t>
        <t>If the radio supports destination specific quality information, this Data Item MAY Item MAY be used in Destination Up, Destination Update and Destination Announce Response messages.</t>
        <t>The format of the Radio SNR Data Item is:</t>
        <figure anchor="radio_snr">
          <artwork align="left" name="" type="" 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type                | Length                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|              SNR              |     Flags     |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
          ]]></artwork>
        </figure>
        <dl>
          <dt>Data Item Type:</dt><dd>TBD2</dd>
          <dt>Length:</dt><dd>3</dd>
          <dt>SNR:</dt><dd>SNR measured in dB multiplied by 10 as a signed integer.</dd>
          <dt>Flags:</dt><dd>Flags field as defined below.</dd>
        </dl>
        <t>The Flags field is defined as:</t>
        <figure anchor="radio_quality_flags">
          <artwork align="left" name="" type="" alt=""><![CDATA[
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|   Reserved  |I|
+-+-+-+-+-+-+-+-+
          ]]></artwork>
        </figure>
        <dl>
            <dt>I:</dt><dd>Interference Flag, indicating the the data includes interference into the noise value (SINR).</dd>
            <dt>Reserved:</dt><dd>MUST be written as zero. Ignored on receipt and left for future assignment.</dd>
        </dl>
      </section>
      <section numbered="true" toc="default">
        <name>Radio Signal Strength Data Item (also called RSSI)</name>
        <t>Radio Signal Strength Data Item contains information about which absolute signal strength the radio measured. This Data Item can be both interface and neighbor specific.</t>
        <t>If supported this Data Item MUST be used in the Session Initialization Response and MAY be used in Session Update messages.</t>
        <t>If the radio supports destination specific quality information, this Data Item MAY Item MAY be used in Destination Up, Destination Update and Destination Announce Response messages.</t>
        <t>This Data Item could also be used together with the Request Link Characteristics message to reconfigure the outgoing signal strength, either to reduce the size of
          the collision domain or to increase the range of the radio. In this case this Data Item MAY be used in Link Characteristics Request and Link Characteristics Response messages.</t>
        <t>The format of the Radio Signal Strength Data Item is:</t>
        <figure anchor="radio_signal">
          <artwork align="left" name="" type="" 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type                | Length                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|            Signal             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
          ]]></artwork>
        </figure>
        <dl>
          <dt>Data Item Type:</dt><dd>TBD3</dd>
          <dt>Length:</dt><dd>2</dd>
          <dt>Signal:</dt><dd>Signal Strength measured in dBm multiplied by 10 as a signed integer.</dd>
        </dl>
      </section>
      <section numbered="true" toc="default">
        <name>Radio Noise Data Item</name>
        <t>Radio Noise Data Item contains information about which absolute noise value the radio measured. This Data Item SHOULD be interface specific.</t>
        <t>If supported this Data Item MUST be used in the Session Initialization Response and MAY be used in Session Update messages.</t>
        <t>The format of the Radio Noise Data Item is:</t>
        <figure anchor="radio_noise">
          <artwork align="left" name="" type="" 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type                | Length                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|             Noise             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
          ]]></artwork>
        </figure>
        <dl>
          <dt>Data Item Type:</dt><dd>TBD4</dd>
          <dt>Length:</dt><dd>2</dd>
          <dt>Noise:</dt><dd>Noise measured in dBm multiplied by 10 as a signed integer.</dd>
        </dl>
      </section>
    </section>
    <section numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>The extension introduces a new Data Item for DLEP.
        The extension does not inherently introduce any additional
        vulnerabilities above those documented in
        <xref target="RFC8175" format="default"/>.
        The approach taken to security in that document applies
        equally when running the extension defined in this document.</t>
    </section>
    <section numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>As described below, IANA has assigned five values per this document.
        Both assignments are to registries defined by
        <xref target="RFC8175" format="default"/>.</t>
      <section numbered="true" toc="default">
        <name>Data Item Type Values</name>
        <t>IANA has assigned the following value in the "Data Item Type Values" registry defined by <xref target="RFC8175" format="default"/>, chapter 15.4.
          The new values are in the range with the "Specification Required"
          <xref target="RFC8126" format="default"/>
          policy:</t>
        <table>
          <name>Data Item Type Values</name>
          <thead>
            <tr>
              <td>Type Code</td><td>Description</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>TBD1</td><td>Radio Biterror Rate</td>
            </tr>
            <tr>
              <td>TBD2</td><td>Radio SNR</td>
            </tr>
            <tr>
              <td>TBD3</td><td>Radio Signal</td>
            </tr>
            <tr>
              <td>TBD4</td><td>Radio Noise</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section numbered="true" toc="default">
        <name>Extension Type Values</name>
        <t>IANA has assigned the following value in the "Extension Type Values" registry defined by <xref target="RFC8175" format="default"/>, chapter 15.6.
          The new value is in the range with the  "Specification Required"
          <xref target="RFC8126" format="default"/> policy:</t>
        <table>
          <name>DLEP Extension Types</name>
          <thead>
            <tr>
              <td>Code</td><td>Description</td>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>TBD5</td><td>Radio Quality</td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
  </middle>
  <back>
    <references>
      <name>Normative References</name>
      <xi:include href="http://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
      <xi:include href="http://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
      <xi:include href="http://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8175.xml"/>
    </references>
    <references>
      <name>Informative References</name>
      <xi:include href="http://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
    </references>
</back>
</rfc>
