<?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-band-05"
      ipr="trust200902"
      obsoletes=""
      updates=""
      submissionType="IETF"
      xml:lang="en"
      tocInclude="true"
      tocDepth="4"
      symRefs="true"
      sortRefs="true"
      version="3"
      consensus="true">
<front>
  <title>DLEP Radio Band Extension</title>
  <seriesInfo name="Internet-Draft" value="draft-ietf-manet-dlep-radio-band-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 information about frequency bands used by the radio.</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 consist 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 to provide information about the frequency
        bands used by the radio.</t>
      <t>This extension does not consider radios which use frequency hopping.
        Frequency hopping is a much more complicated topic that should be considered
        in a documents of its own.</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 Band Extension SHOULD be
        configurable. To indicate that the Radio Band Extension
        is to be used, an implementation MUST include the Radio Band
        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 Band Data Item</name>
      <t>Radio Band Data Item contains information about which radio frequency resources
        are being used. The Data item MUST be used in the Session Initialization Response message and MAY be used in Session Update messages.</t>
      <t>The Radio Band Data Item can be used multiple times in the same message to represent multiple radio bands.</t>
      <t>If the radio/modem wants to provide the destination specific radio bands, the Radio Band Data Item MAY be used in Destination Up, Destination Update and Destination Announce Response messages.</t>
      <t>Frequency selection is often controlled by the radio configuration. By giving the radio a standardized way to transmit its
         selected frequency configuration the router can aggregate multiple radios settings into a common information page, can do
         some basic checking for configuration mistakes by comparing known radio group configuration with their frequency by radio
         (if the routers have a second communication channel) or forward the data to an upper layer for visualization.</t>
      <t>The information in this Item gives the router an easy way to calculate the spectral efficiency of a radio link,
         how much bandwidth is used for the current data-rate reported by DLEP. This can be integrated into the routing metric
         to focus traffic on links that use the spectrum efficiently.</t>
      <t>The Item can also be used as an interface to a cognitive radio controller on the router, analyzing the correlation of
         transmission disruptions with the frequency bands and could be
         used to change the frequency of the radio in a standardized way. In this case
         the Radio Band Data Item MAY be used in the Link Characteristics Request and Link Characteristics Response message.</t>
      <t>Both values in the TLV (Carrier Frequency and Bandwidth) are 64 bit unsigned integers.</t>
      <t>The format of the Radio Band Data Item is:</t>
      <figure anchor="radio_band">
        <name>Radio Band Data Item Format</name>
        <artwork align="left"><![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                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
+                       Carrier Frequency                       +
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
+                           Bandwidth                           +
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     Flags     |
+-+-+-+-+-+-+-+-+
        ]]></artwork>
      </figure>
      <dl>
        <dt>Data Item Type:</dt><dd>TBD1</dd>
        <dt>Length:</dt><dd>17</dd>
        <dt>Center Frequency:</dt><dd>The center frequency of the band in Hz.</dd>
        <dt>Bandwidth:</dt><dd>The bandwidth of the band in Hz.</dd>
        <dt>Flags:</dt><dd>Flags field as defined below.</dd>
      </dl>
      <t>The Flags field is defined as:</t>
      <figure anchor="radio_band_flags">
        <name>Radio Band Data Item Flags</name>
        <artwork align="left" name="" type="" alt=""><![CDATA[
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| Reserved  |U|D|
+-+-+-+-+-+-+-+-+
        ]]></artwork>
      </figure>
      <dl>
          <dt>U:</dt><dd>Uplink Flag, indicating the band is used for transmitting data.</dd>
          <dt>D:</dt><dd>Downlink Flag, indicating the band is used for receiving data.</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>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 two 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 value is 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 Band</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>TBD2</td><td>Radio Band</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>
