rfc8757xml2.original.xml   rfc8757.xml 
<?xml version="1.0" encoding="UTF-8"?> <?xml 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" ?>
<rfc category="std" ipr="trust200902" docName="draft-ietf-manet-dlep-latency-ext
ension-05">
<front> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<title abbrev="DLEP Latency Range Extension">Dynamic Link Exchange Protocol (DLE
P) Latency Range <rfc xmlns:xi="http://www.w3.org/2001/XInclude"
category="std"
ipr="trust200902"
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> Extension</title>
<author initials='B.' surname="Cheng" fullname='Bow-Nan Cheng'> <seriesInfo name="RFC" value="8757"/>
<organization>MIT Lincoln Laboratory</organization> <author initials="B." surname="Cheng" fullname="Bow-Nan Cheng">
<address> <organization>MIT Lincoln Laboratory</organization>
<postal> <address>
<street>Massachusetts Institute of Technology</street> <postal>
<street>244 Wood Street</street> <extaddr>Massachusetts Institute of Technology</extaddr>
<city>Lexington</city> <street>244 Wood Street</street>
<region>MA</region> <city>Lexington</city>
<code>02421-6426</code> <region>MA</region>
</postal> <code>02421-6426</code>
<email>bcheng@ll.mit.edu</email> <country>USA</country>
</address> </postal>
<email>bcheng@ll.mit.edu</email>
</address>
</author> </author>
<author initials='L.' surname="Berger" fullname='Lou Berger' role='editor'> <author initials="L." surname="Berger" fullname="Lou Berger" role="editor">
<organization>LabN Consulting, L.L.C.</organization> <organization>LabN Consulting, L.L.C.</organization>
<address> <address>
<email>lberger@labn.net</email> <email>lberger@labn.net</email>
</address> </address>
</author> </author>
<date year="2020" month="March"/>
<date/> <keyword>MANET</keyword>
<abstract> <abstract>
<t> <t>
This document defines an extension to the Dynamic Link Exchange Protocol (DLEP ) to provide the 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. range of latency that can be experienced on a link.
</t> </t>
</abstract> </abstract>
</front> </front>
<middle>
<middle> <section anchor="sec-1" numbered="true" toc="default">
<section anchor="sec-1" title="Introduction"> <name>Introduction</name>
<t> <t>
The Dynamic Link Exchange Protocol (DLEP) is defined in <xref The Dynamic Link Exchange Protocol (DLEP) is defined in <xref target="RFC8175"
target="RFC8175"/>. It provides the exchange of link format="default"/>.
related control information between DLEP peers. DLEP peers are It provides the exchange of link-related control information between DLEP peer
s. DLEP peers are
comprised of a modem and a router. DLEP defines a base set of comprised of a modem and a router. DLEP defines a base set of
mechanisms as well as support for possible extensions. This mechanisms as well as support for possible extensions. This
document defines one such extension. document defines one such extension.
</t> </t>
<t> <t>
The base DLEP specification includes the Latency metric which provides The base DLEP specification includes the Latency Data Item, which
a single latency value on a link, which is implementation dependent. provides a single, implementation-dependent latency value on a
This document adds the ability to relay link. This document adds the ability to relay
the minimum and maximum latency range seen on a link. The extension the minimum and maximum latency range seen on a link. The extension
defined in this document is referred to as "Latency Range". defined in this document is referred to as "Latency Range".
</t> </t>
<t> <t>
This document defines a new DLEP Extension Type Value in <xref This document defines a new DLEP Extension Type Value that is used to
target="sec-ext-type"/> which is used to indicate the use of the indicate the use of the extension; see <xref target="sec-ext-type"
extension, and one new DLEP Data Item in <xref 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">
<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> </t>
</section> <section anchor="sec-1.1" numbered="true" toc="default">
</section> <name>Key Words</name>
<section anchor="sec-ext-type" title="Extension Usage and Identification"> <t>
<t> The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
The use of the Latency Range Extension SHOULD be configurable. To IRED</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 "<bcp14>OPTIONAL</bcp14>" in this document are to
be interpreted as
described in BCP&nbsp;14 <xref target="RFC2119" format="default"/> <xref tar
get="RFC8174" format="default"/>
when, and only when, they appear in all capitals, as shown here.
</t>
</section>
</section>
<section anchor="sec-ext-type" numbered="true" toc="default">
<name>Extension Usage and Identification</name>
<t>
The use of the Latency Range Extension <bcp14>SHOULD</bcp14> be configurable.
To
indicate that the Latency Range Extension is to be used, an indicate that the Latency Range Extension is to be used, an
implementation MUST include the Latency Range Extension Type Value in implementation <bcp14>MUST</bcp14> include the Latency Range Extension Type V alue in
the Extensions Supported Data Item. The Extensions Supported Data the Extensions Supported Data Item. The Extensions Supported Data
Item is sent and processed according to <xref target="RFC8175"/>. Item is sent and processed according to <xref target="RFC8175" format="defaul t"/>.
</t> </t>
<t> <t>
Note: the usage of the extension defined in this document does not Note: The usage of the extension defined in this document does not
impact processing associated with the Latency Data Item defined in impact processing associated with the Latency Data Item defined in
<xref target="RFC8175"/>. <xref target="RFC8175" format="default"/>.
</t> </t>
<t>
The Latency Range Extension Type Value is TBA1, see <xref <t>
target="sec-iana"/>. The Latency Range Extension Type Value is 4; see <xref target="sec-iana" forma
t="default"/>.
</t> </t>
</section> </section>
<section anchor="sec-data-items" title="Latency Range Data Item"> <section anchor="sec-data-items" numbered="true" toc="default">
<t> <name>Latency Range Data Item</name>
<t>
The Latency Range Data Item serves much the same purpose as the The Latency Range Data Item serves much the same purpose as the
Latency Data Item defined in <xref target="RFC8175"/> with Latency Data Item defined in <xref target="RFC8175" format="default"/> with
the addition of being able to communicate the latency range that can the addition of being able to communicate the latency range that can
be experienced by traffic on a link. The Latency Range Data Item be experienced by traffic on a link. The Latency Range Data Item
MUST be included in the Session Initialization Response Message, with <bcp14>MUST</bcp14> be included in the Session Initialization Response Message , with
default values to be used on a session-wide basis. default values to be used on a session-wide basis.
The Latency Range Data Item also MAY be The Latency Range Data Item also <bcp14>MAY</bcp14> be
carried in any message where the Latency Data Item [RFC8175] is carried in any message where the Latency Data Item <xref target="RFC8175" form
at="default"/> is
allowed and is carried as an additional data item. When present, the allowed and is carried as an additional data item. When present, the
Latency Range Data Item MUST be processed according to the same rules Latency Range Data Item <bcp14>MUST</bcp14> be processed according to the same
as the Latency Data Item defined in <xref target="RFC8175"/>. rules
as the Latency Data Item defined in <xref target="RFC8175" format="default"/>.
</t> </t>
<t>
<t>
The format of the Latency Range Data Item is: The format of the Latency Range Data Item is:
</t> </t>
<t> <artwork name="" type="" align="left" alt=""><![CDATA[
<figure> 0 1 2 3
<artwork> 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
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Maximum Latency :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum Latency : : Maximum Latency |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Maximum Latency | | Minimum Latency :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minimum Latency : : Minimum Latency |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Minimum Latency | ]]></artwork>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork> <dl newline="true" spacing="normal">
</figure> <dt>Data Item Type:</dt>
</t> <dd>28</dd>
<t> <dt>Length:</dt>
<list style="hanging"> <dd>16</dd>
<t hangText="Data Item Type:">TBA2</t> <dt>Maximum Latency:</dt>
<t hangText="Length:">16</t> <dd>
<t hangText="Maximum Latency:">
<vspace blankLines="1"/>
A 64-bit unsigned integer, representing the longest transmission A 64-bit unsigned integer, representing the longest transmission
delay, in microseconds, that a packet encounters as it is delay, in microseconds, that a packet encounters as it is
transmitted over the link. transmitted over the link.
</t> </dd>
<t hangText="Minimum Latency:"> <dt>Minimum Latency:</dt>
<vspace blankLines="1"/> <dd>
A 64-bit unsigned integer, representing the shortest transmission A 64-bit unsigned integer, representing the shortest transmission
delay, in microseconds, that a packet can encounter as it is delay, in microseconds, that a packet can encounter as it is
transmitted over the link. transmitted over the link.
</t> </dd>
</list> </dl>
</t> </section>
<t> <section anchor="sec-sec" numbered="true" toc="default">
</t> <name>Security Considerations</name>
</section> <t>
<section anchor="sec-sec" title="Security Considerations">
<t>
The extension introduces a new Data Item The extension introduces a new Data Item
for DLEP. The for DLEP. The
extension does not inherently introduce any additional vulnerabilities extension does not inherently introduce any additional vulnerabilities
above those documented in <xref target="RFC8175"/>. above those documented in <xref target="RFC8175" format="default"/>.
The approach taken to Security in that document applies equally The approach taken to security in that document applies equally
when running the extension defined in this document. when running the extension defined in this document.
</t> </t>
</section> </section>
<section anchor="sec-iana" title="IANA Considerations"> <section anchor="sec-iana" numbered="true" toc="default">
<t> <name>IANA Considerations</name>
This document requests the assignment of two values by IANA. All <t>
assignments are to registries defined by <xref As described below, IANA has assigned two values per this document. Both assig
target="RFC8175"/>. nments are to
registries defined by <xref target="RFC8175" format="default"/>.
</t> </t>
<section anchor="sec-iana-ext" title="Extension Type Value"> <section anchor="sec-iana-ext" numbered="true" toc="default">
<t> <name>Extension Type Value</name>
This document requests one new assignment to the DLEP Extensions <t>
Registry named "Extension Type Values" in the range with the IANA has assigned the following value in the
"Specification Required" policy. The requested value is as follows: "Extension Type Values" registry within the "Dynamic Link Exchange Protocol
(DLEP) Parameters" registry. The new value is in the range with the
"Specification Required" <xref target="RFC8126" format="default"/> policy:
</t> </t>
<texttable anchor="table_et" title="Requested Extension Type Value"> <table anchor="table_et" align="center">
<preamble></preamble> <name>New Extension Type Value</name>
<ttcol>Code</ttcol> <ttcol>Description</ttcol> <thead>
<c>TBA1</c> <c>Latency Range</c> <tr>
<postamble></postamble> <th align="left">Code</th>
</texttable> <th align="left">Description</th>
</section> </tr>
<section anchor="sec-iana-di" title="Data Item Value"> </thead>
<t> <tbody>
This document requests one new assignment to the DLEP Data Item <tr>
Registry named "Data Item Type Values" in the range with the "Specification <td align="left">4</td>
Required" policy. The requested values are as follows: <td align="left">Latency Range</td>
</tr>
</tbody>
</table>
</section>
<section anchor="sec-iana-di" numbered="true" toc="default">
<name>Data Item Value</name>
<t>
IANA has assigned the following value in the "Data Item Type Values" registry
within the "Dynamic Link Exchange Protocol (DLEP) Parameters" registry. The ne
w
value is in the range with the "Specification Required" <xref target="RFC8126"
format="default"/> policy:
</t> </t>
<texttable anchor="table_di" title="Requested Data Item Values"> <table anchor="table_di" align="center">
<preamble></preamble> <name>New Data Item Value</name>
<ttcol>Type Code</ttcol> <ttcol>Description</ttcol> <thead>
<c>TBA2</c> <c>Latency Range</c> <tr>
<postamble></postamble> <th align="left">Type Code</th>
</texttable> <th align="left">Description</th>
</section> </tr>
</section> </thead>
</middle> <tbody>
<tr>
<?rfc needLines="20"?> <td align="left">28</td>
<back> <td align="left">Latency Range</td>
<references title="Normative References"> </tr>
</tbody>
<?rfc include="reference.RFC.2119"?> </table>
<?rfc include="reference.RFC.8174"?> </section>
<?rfc include="reference.RFC.8175"?> </section>
</middle>
<back>
<references>
<name>References</name>
<?rfc needLines="100"?> <references>
</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>
<references title="Informative References"> <name>Informative References</name>
<xi:include
href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml
"/>
</references>
<?rfc include="reference.I-D.draft-ietf-manet-credit-window-04.xml"?> </references>
</references> <section numbered="false" toc="default">
<?rfc needLines="100"?> <name>Acknowledgments</name>
<section title="Acknowledgments"> <t>
<t>
Helpful comments were received from members of the MANET working Helpful comments were received from members of the MANET working
grouping, including Ronald in 't Velt, Henning Rogge, and Victoria group, including <contact fullname="Ronald in 't Velt"/>, <contact fullname=
Pritchard. "Henning Rogge"/>, and <contact fullname="Victoria
</t> Pritchard"/>.
</section> </t>
</back> </section>
</back>
</rfc> </rfc>
<!-- Local Variables: -->
<!-- fill-column:72 -->
<!-- End: -->
 End of changes. 34 change blocks. 
178 lines changed or deleted 222 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/