wdiff rfc8757xml2.original.xml rfc8757.xml

<?xml version="1.0" encoding="UTF-8"?> version='1.0' encoding='utf-8'?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
  ]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?> "rfc2629-xhtml.ent">

<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
category="std"
ipr="trust200902" docName="draft-ietf-manet-dlep-latency-extension-05">
docName="draft-ietf-manet-dlep-latency-extension-05"
number="8757"
consensus="true"
obsoletes=""
updates=""
submissionType="IETF"
xml:lang="en"
tocInclude="true"
symRefs="true"
sortRefs="true"
version="3">
  <front>
    <title abbrev="DLEP Latency Range Extension">Dynamic Link Exchange Protocol (DLEP) Latency Range
Extension</title>
    <seriesInfo name="RFC" value="8757"/>
    <author initials='B.' initials="B." surname="Cheng" fullname='Bow-Nan Cheng'> fullname="Bow-Nan Cheng">
      <organization>MIT Lincoln Laboratory</organization>
      <address>
        <postal>
        <street>Massachusetts
          <extaddr>Massachusetts Institute of Technology</street> Technology</extaddr>
          <street>244 Wood Street</street>
          <city>Lexington</city>
          <region>MA</region>
          <code>02421-6426</code>
          <country>USA</country>
        </postal>
        <email>bcheng@ll.mit.edu</email>
      </address>
    </author>
    <author initials='L.' initials="L." surname="Berger" fullname='Lou Berger' role='editor'> fullname="Lou Berger" role="editor">
      <organization>LabN Consulting, L.L.C.</organization>
      <address>
        <email>lberger@labn.net</email>
      </address>
    </author>

  <date/>
    <date year="2020" month="March"/>
<keyword>MANET</keyword>
    <abstract>
      <t>
  This document defines an extension to the Dynamic Link Exchange Protocol (DLEP) to provide the
  range of latency that can be experienced on a link.
</t>
    </abstract>
  </front>
  <middle>
    <section anchor="sec-1" title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>
  The Dynamic Link Exchange Protocol (DLEP) is defined in <xref
  target="RFC8175"/>. target="RFC8175" format="default"/>.
  It provides the exchange of link
  related 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>
      <t>
   The base DLEP specification includes the Latency metric Data Item, which
   provides a single single, implementation-dependent latency value on a link, which is implementation dependent.
   link.  This document adds the ability to relay
  the minimum and maximum latency range seen on a link.  The extension
  defined in this document is referred to as "Latency Range".
</t>
      <t>
  This document defines a new DLEP Extension Type Value in <xref
  target="sec-ext-type"/> which that is used to
  indicate the use of the
  extension, and one extension; see <xref target="sec-ext-type"
  format="default"/>. A new DLEP Data Item is defined in <xref
  target="sec-data-items"/>.
  target="sec-data-items" format="default"/>.
</t>
      <section anchor="sec-1.1" title="Key Words"> numbered="true" toc="default">
        <name>Key Words</name>
        <t>
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
    NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and
   "OPTIONAL" "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
    described in
   BCP 14 BCP&nbsp;14 <xref target="RFC2119"/> target="RFC2119" format="default"/> <xref target="RFC8174"/> target="RFC8174" format="default"/>
    when, and only when, they appear in all capitals, as shown here.
        </t>
      </section>
    </section>
    <section anchor="sec-ext-type" title="Extension numbered="true" toc="default">
      <name>Extension Usage and Identification"> Identification</name>
      <t>
   The use of the Latency Range Extension SHOULD <bcp14>SHOULD</bcp14> be configurable.  To
   indicate that the Latency Range Extension is to be used, an
   implementation MUST <bcp14>MUST</bcp14> include the Latency Range Extension Type Value in
   the Extensions Supported Data Item. The Extensions Supported Data
   Item is sent and processed according to <xref target="RFC8175"/>. target="RFC8175" format="default"/>.
</t>
      <t>
  Note: the The usage of the extension defined in this document does not
  impact processing associated with the Latency Data Item defined in
  <xref target="RFC8175"/>. target="RFC8175" format="default"/>.
</t>

      <t>
  The Latency Range Extension Type Value is TBA1, 4; see <xref
  target="sec-iana"/>. target="sec-iana" format="default"/>.
</t>
    </section>
    <section anchor="sec-data-items" title="Latency numbered="true" toc="default">
      <name>Latency Range Data Item"> Item</name>
      <t>
  The Latency Range Data Item serves much the same purpose as the
  Latency Data Item defined in <xref target="RFC8175"/> target="RFC8175" format="default"/> with
  the addition of being able to communicate the latency range that can
  be experienced by traffic on a link.  The Latency Range Data Item
  MUST
  <bcp14>MUST</bcp14> be included in the Session Initialization Response Message, with
  default values to be used on a session-wide basis.
  The Latency Range Data Item also MAY <bcp14>MAY</bcp14> be
  carried in any message where the Latency Data Item [RFC8175] <xref target="RFC8175" format="default"/> is
  allowed and is carried as an additional data item.  When present, the
  Latency Range Data Item MUST <bcp14>MUST</bcp14> be processed according to the same rules
  as the Latency Data Item defined in <xref target="RFC8175"/>. target="RFC8175" format="default"/>.
</t>
      <t>
  The format of the Latency Range Data Item is:
</t>
<t>
<figure>
<artwork>
      <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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type                | Length                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                        Maximum Latency                        :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:                        Maximum Latency                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                        Minimum Latency                        :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:                        Minimum Latency                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure>
</t>
<t>
  <list style="hanging">
    <t hangText="Data Item Type:">TBA2</t>
    <t hangText="Length:">16</t>
    <t hangText="Maximum Latency:">
      <vspace blankLines="1"/>
]]></artwork>

      <dl newline="true" spacing="normal">
        <dt>Data Item Type:</dt>
        <dd>28</dd>
        <dt>Length:</dt>
        <dd>16</dd>
        <dt>Maximum Latency:</dt>
        <dd>
      A 64-bit unsigned integer, representing the longest transmission
      delay, in microseconds, that a packet encounters as it is
      transmitted over the link.
    </t>
    <t hangText="Minimum Latency:">
      <vspace blankLines="1"/>
    </dd>
        <dt>Minimum Latency:</dt>
        <dd>
      A 64-bit unsigned integer, representing the shortest transmission
      delay, in microseconds, that a packet can encounter as it is
      transmitted over the link.
    </t>
  </list>
</t>
<t>
</t>
    </dd>
      </dl>
    </section>
    <section anchor="sec-sec" title="Security Considerations"> 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"/>. target="RFC8175" format="default"/>.
   The approach taken to Security security in that document applies equally
   when running the extension defined in this document.
</t>
    </section>
    <section anchor="sec-iana" title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>
  This document requests the assignment of
  As described below, IANA has assigned two values by IANA.  All per this document. Both assignments are to
  registries defined by <xref
  target="RFC8175"/>. target="RFC8175" format="default"/>.
</t>
      <section anchor="sec-iana-ext" title="Extension numbered="true" toc="default">
        <name>Extension Type Value"> Value</name>
        <t>
  This document requests one new assignment to
  IANA has assigned the following value in the DLEP Extensions
  Registry named
  "Extension Type Values" registry within the "Dynamic Link Exchange Protocol
  (DLEP) Parameters" registry. The new value is in the range with the
  "Specification Required" policy. The requested value is as follows: <xref target="RFC8126" format="default"/> policy:
</t>
<texttable
        <table anchor="table_et" title="Requested align="center">
          <name>New Extension Type Value">
  <preamble></preamble>
  <ttcol>Code</ttcol> <ttcol>Description</ttcol>
    <c>TBA1</c> <c>Latency Range</c>
    <postamble></postamble>
    </texttable> Value</name>
          <thead>
            <tr>
              <th align="left">Code</th>
              <th align="left">Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">4</td>
              <td align="left">Latency Range</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="sec-iana-di" title="Data numbered="true" toc="default">
        <name>Data Item Value"> Value</name>
        <t>
  This document requests one new assignment to
  IANA has assigned the following value in the DLEP Data Item
  Registry named "Data Item Type Values" registry
  within the "Dynamic Link Exchange Protocol (DLEP) Parameters" registry. The new
  value is in the range with the "Specification Required" policy. The requested values are as follows: <xref target="RFC8126"
  format="default"/> policy:
</t>
<texttable
        <table anchor="table_di" title="Requested align="center">
          <name>New Data Item Values">
  <preamble></preamble>
  <ttcol>Type Code</ttcol> <ttcol>Description</ttcol>
    <c>TBA2</c> <c>Latency Range</c>
    <postamble></postamble>
    </texttable> Value</name>
          <thead>
            <tr>
              <th align="left">Type Code</th>
              <th align="left">Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">28</td>
              <td align="left">Latency Range</td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
  </middle>

<?rfc needLines="20"?>
  <back>
<references title="Normative References">

<?rfc include="reference.RFC.2119"?>
<?rfc include="reference.RFC.8174"?>
<?rfc include="reference.RFC.8175"?>

<?rfc needLines="100"?>
    <references>
      <name>References</name>

    <references>
      <name>Normative References</name>
      <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
      <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
      <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8175.xml"/>
    </references>

    <references>
      <name>Informative References</name>
      <xi:include
	  href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
    </references>

<!--
<references title="Informative References">

<?rfc include="reference.I-D.draft-ietf-manet-credit-window-04.xml"?>

    </references>
<?rfc needLines="100"?>
-->

<section title="Acknowledgments"> numbered="false" toc="default">
      <name>Acknowledgments</name>
      <t>
    Helpful comments were received from members of the MANET working
    grouping,
    group, including Ronald <contact fullname="Ronald in 't Velt, Henning Rogge, Velt"/>, <contact fullname="Henning Rogge"/>, and Victoria
    Pritchard. <contact fullname="Victoria
    Pritchard"/>.
      </t>
    </section>
  </back>
</rfc>

<!-- Local Variables: -->
<!-- fill-column:72 -->
<!-- End: -->