rfc8651xml2.original.xml   rfc8651.xml 
<?xml version="1.0" encoding="UTF-8"?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" conse
]> nsus="true" docName="draft-ietf-manet-dlep-pause-extension-08" indexInclude="tru
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?> e" ipr="trust200902" number="8651" prepTime="2019-10-03T08:45:31" scripts="Commo
<?rfc toc="yes" ?> n,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="3" tocIn
<?rfc symrefs="yes" ?> clude="true" xml:lang="en">
<?rfc sortrefs="yes"?> <link href="https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-pause-exten
<?rfc iprnotified="no" ?> sion-08" rel="prev"/>
<?rfc strict="yes" ?> <link href="https://dx.doi.org/10.17487/rfc8651" rel="alternate"/>
<rfc category="std" ipr="trust200902" docName="draft-ietf-manet-dlep-pause-exten <link href="urn:issn:2070-1721" rel="alternate"/>
sion-08" > <front>
<title abbrev="DLEP Pause Extension">Dynamic Link Exchange Protocol
<front> (DLEP) Control‑Plane‑Based Pause Extension</title>
<title abbrev="DLEP Pause Extension">DLEP Control Plane Based Pause <seriesInfo name="RFC" value="8651" stream="IETF"/>
Extension</title> <author initials="B." surname="Cheng" fullname="Bow-Nan Cheng">
<author initials='B.' surname="Cheng" fullname='Bow-Nan Cheng'> <organization showOnFrontPage="true">MIT Lincoln Laboratory</organization>
<organization>MIT Lincoln Laboratory</organization> <address>
<address> <postal>
<postal> <extaddr>Massachusetts Institute of Technology</extaddr>
<street>Massachusetts Institute of Technology</street> <street>244 Wood Street</street>
<street>244 Wood Street</street> <city>Lexington</city>
<city>Lexington</city> <region>MA</region>
<region>MA</region> <code>02421-6426</code>
<code>02421-6426</code> <country>United States of America</country>
</postal> </postal>
<email>bcheng@ll.mit.edu</email> <email>bcheng@ll.mit.edu</email>
</address> </address>
</author> </author>
<author initials='D.' surname="Wiggins" fullname='David Wiggins'> <author initials="D." surname="Wiggins" fullname="David Wiggins">
<organization>MIT Lincoln Laboratory</organization> <organization showOnFrontPage="true">MIT Lincoln Laboratory</organization>
<address> <address>
<postal> <postal>
<street>Massachusetts Institute of Technology</street> <extaddr>Massachusetts Institute of Technology</extaddr>
<street>244 Wood Street</street> <street>244 Wood Street</street>
<city>Lexington</city> <city>Lexington</city>
<region>MA</region> <region>MA</region>
<code>02420-9108</code> <code>02420-9108</code>
</postal> <country>United States of America</country>
<email>David.Wiggins@ll.mit.edu</email> </postal>
</address> <email>David.Wiggins@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 showOnFrontPage="true">LabN Consulting, L.L.C.</organization
<address> >
<email>lberger@labn.net</email> <address>
</address> <email>lberger@labn.net</email>
</address>
</author> </author>
<date month="10" year="2019"/>
<date/> <keyword>DLEP, Flow control, Pause</keyword>
<abstract> <abstract pn="section-abstract">
<t> <t pn="section-abstract-1">
This document defines an extension to the Dynamic Link Exchange Protocol (DLEP ) that enables a This document defines an extension to the Dynamic Link Exchange Protocol (DLEP ) that enables a
modem to use DLEP messages to pause and resume data traffic coming modem to use DLEP messages to pause and resume data traffic coming
from its peer router. from its peer router.
</t> </t>
</abstract> </abstract>
</front> <boilerplate>
<section anchor="status-of-memo" numbered="false" removeInRFC="false" toc=
<middle> "exclude" pn="section-boilerplate.1">
<section anchor="sec-1" title="Introduction"> <name slugifiedName="name-status-of-this-memo">Status of This Memo</name
<t> >
The Dynamic Link Exchange Protocol (DLEP) is defined in <xref <t pn="section-boilerplate.1-1">
target="RFC8175"/>. It provides the exchange of link This is an Internet Standards Track document.
related control information between a </t>
<t pn="section-boilerplate.1-2">
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by
the Internet Engineering Steering Group (IESG). Further
information on Internet Standards is available in Section 2 of
RFC 7841.
</t>
<t pn="section-boilerplate.1-3">
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
<eref target="https://www.rfc-editor.org/info/rfc8651"/>.
</t>
</section>
<section anchor="copyright" numbered="false" removeInRFC="false" toc="excl
ude" pn="section-boilerplate.2">
<name slugifiedName="name-copyright-notice">Copyright Notice</name>
<t pn="section-boilerplate.2-1">
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
</t>
<t pn="section-boilerplate.2-2">
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<eref target="https://trustee.ietf.org/license-info"/>) in effect o
n the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
</t>
</section>
<section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" p
n="section-boilerplate.3">
<name slugifiedName="name-table-of-contents">Table of Contents</name>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-bo
ilerplate.3-1">
<li pn="section-boilerplate.3-1.1">
<t keepWithNext="true" pn="section-boilerplate.3-1.1.1"><xref derive
dContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref de
rivedContent="Introduction" format="title" sectionFormat="of" target="name-intro
duction">Introduction</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-boilerplate.3-1.1.2">
<li pn="section-boilerplate.3-1.1.2.1">
<t keepWithNext="true" pn="section-boilerplate.3-1.1.2.1.1"><xre
f derivedContent="1.1" format="counter" sectionFormat="of" target="section-1.1"/
>.  <xref derivedContent="Key Words" format="title" sectionFormat="of" target="n
ame-key-words">Key Words</xref></t>
</li>
</ul>
</li>
<li pn="section-boilerplate.3-1.2">
<t keepWithNext="true" pn="section-boilerplate.3-1.2.1"><xref derive
dContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref de
rivedContent="Extension Usage and Identification" format="title" sectionFormat="
of" target="name-extension-usage-and-identif">Extension Usage and Identification
</xref></t>
</li>
<li pn="section-boilerplate.3-1.3">
<t keepWithNext="true" pn="section-boilerplate.3-1.3.1"><xref derive
dContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref de
rivedContent="Extension Data Items" format="title" sectionFormat="of" target="na
me-extension-data-items">Extension Data Items</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-boilerplate.3-1.3.2">
<li pn="section-boilerplate.3-1.3.2.1">
<t keepWithNext="true" pn="section-boilerplate.3-1.3.2.1.1"><xre
f derivedContent="3.1" format="counter" sectionFormat="of" target="section-3.1"/
>.  <xref derivedContent="Queue Parameters" format="title" sectionFormat="of" ta
rget="name-queue-parameters">Queue Parameters</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="se
ction-boilerplate.3-1.3.2.1.2">
<li pn="section-boilerplate.3-1.3.2.1.2.1">
<t keepWithNext="true" pn="section-boilerplate.3-1.3.2.1.2.1
.1"><xref derivedContent="3.1.1" format="counter" sectionFormat="of" target="sec
tion-3.1.1"/>.  <xref derivedContent="Queue Parameter Sub-Data Item" format="tit
le" sectionFormat="of" target="name-queue-parameter-sub-data-it">Queue Parameter
Sub-Data Item</xref></t>
</li>
</ul>
</li>
<li pn="section-boilerplate.3-1.3.2.2">
<t keepWithNext="true" pn="section-boilerplate.3-1.3.2.2.1"><xre
f derivedContent="3.2" format="counter" sectionFormat="of" target="section-3.2"/
>.  <xref derivedContent="Pause" format="title" sectionFormat="of" target="name-
pause">Pause</xref></t>
</li>
<li pn="section-boilerplate.3-1.3.2.3">
<t keepWithNext="true" pn="section-boilerplate.3-1.3.2.3.1"><xre
f derivedContent="3.3" format="counter" sectionFormat="of" target="section-3.3"/
>.  <xref derivedContent="Restart" format="title" sectionFormat="of" target="nam
e-restart">Restart</xref></t>
</li>
</ul>
</li>
<li pn="section-boilerplate.3-1.4">
<t keepWithNext="true" pn="section-boilerplate.3-1.4.1"><xref derive
dContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref de
rivedContent="Security Considerations" format="title" sectionFormat="of" target=
"name-security-considerations">Security Considerations</xref></t>
</li>
<li pn="section-boilerplate.3-1.5">
<t keepWithNext="true" pn="section-boilerplate.3-1.5.1"><xref derive
dContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref de
rivedContent="IANA Considerations" format="title" sectionFormat="of" target="nam
e-iana-considerations">IANA Considerations</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-boilerplate.3-1.5.2">
<li pn="section-boilerplate.3-1.5.2.1">
<t keepWithNext="true" pn="section-boilerplate.3-1.5.2.1.1"><xre
f derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/
>.  <xref derivedContent="Extension Type Value" format="title" sectionFormat="of
" target="name-extension-type-value">Extension Type Value</xref></t>
</li>
<li pn="section-boilerplate.3-1.5.2.2">
<t keepWithNext="true" pn="section-boilerplate.3-1.5.2.2.1"><xre
f derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/
>.  <xref derivedContent="Data Item Values" format="title" sectionFormat="of" ta
rget="name-data-item-values">Data Item Values</xref></t>
</li>
<li pn="section-boilerplate.3-1.5.2.3">
<t keepWithNext="true" pn="section-boilerplate.3-1.5.2.3.1"><xre
f derivedContent="5.3" format="counter" sectionFormat="of" target="section-5.3"/
>.  <xref derivedContent="Queue Parameter Sub-Data Item Values" format="title" s
ectionFormat="of" target="name-queue-parameter-sub-data-ite">Queue Parameter Sub
-Data Item Values</xref></t>
</li>
</ul>
</li>
<li pn="section-boilerplate.3-1.6">
<t keepWithNext="true" pn="section-boilerplate.3-1.6.1"><xref derive
dContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref de
rivedContent="References" format="title" sectionFormat="of" target="name-referen
ces">References</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-boilerplate.3-1.6.2">
<li pn="section-boilerplate.3-1.6.2.1">
<t keepWithNext="true" pn="section-boilerplate.3-1.6.2.1.1"><xre
f derivedContent="6.1" format="counter" sectionFormat="of" target="section-6.1"/
>.  <xref derivedContent="Normative References" format="title" sectionFormat="of
" target="name-normative-references">Normative References</xref></t>
</li>
<li pn="section-boilerplate.3-1.6.2.2">
<t keepWithNext="true" pn="section-boilerplate.3-1.6.2.2.1"><xre
f derivedContent="6.2" format="counter" sectionFormat="of" target="section-6.2"/
>.  <xref derivedContent="Informative References" format="title" sectionFormat="
of" target="name-informative-references">Informative References</xref></t>
</li>
</ul>
</li>
<li pn="section-boilerplate.3-1.7">
<t keepWithNext="true" pn="section-boilerplate.3-1.7.1"><xref derive
dContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref
derivedContent="Acknowledgments" format="title" sectionFormat="of" target="name-
acknowledgments">Acknowledgments</xref></t>
</li>
<li pn="section-boilerplate.3-1.8">
<t keepWithNext="true" pn="section-boilerplate.3-1.8.1"><xref derive
dContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref
derivedContent="Authors' Addresses" format="title" sectionFormat="of" target="na
me-authors-addresses">Authors' Addresses</xref></t>
</li>
</ul>
</section>
</boilerplate>
</front>
<middle>
<section anchor="sec-1" numbered="true" toc="include" removeInRFC="false" pn
="section-1">
<name slugifiedName="name-introduction">Introduction</name>
<t pn="section-1-1">
The Dynamic Link Exchange Protocol (DLEP) is defined in <xref target="RFC8175"
format="default" sectionFormat="of" derivedContent="RFC8175"/>. It provides the
exchange of link-related
control information between a
modem and a router. DLEP defines a base set of 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 pn="section-1-2">
The base DLEP specification does not include any data plane flow The base DLEP specification does not include any data-plane
control capability. The extension defined in this document supports flow‑control capability. The extension defined in this document supports
flow control of data traffic based on explicit messages sent via DLEP flow control of data traffic based on explicit messages sent via DLEP
by a modem to indicate when a router should hold off sending traffic, by a modem to indicate when a router should hold off sending traffic
and when it should resume. This functionality parallels the flow and when it should resume. This functionality parallels the
control mechanism found in PPP over Ethernet (PPPoE) per flow‑control mechanism found in PPP over Ethernet (PPPoE) per
<xref target="RFC5578"/>. The extension also optionally <xref target="RFC5578" format="default" sectionFormat="of" derivedContent="RFC
supports DSCP (differentiated services codepoint) aware flow control 5578"/>. The extension also optionally
for use by DiffServ-aware modems. (For supports DSCP-aware flow control ("DSCP" stands for "Differentiated
general background on Differentiated Services see <xref Services Code Point") for use by Diffserv-aware modems. (For
target="RFC2475"/>.) general background on Differentiated Services, see <xref target="RFC2475" form
at="default" sectionFormat="of" derivedContent="RFC2475"/>.)
This functionality is very similar to that provided by Ethernet This functionality is very similar to that provided by Ethernet
Priority flow control, see <xref target="IEEE.802.1Q_2014"/>. priority‑based flow control; see <xref target="IEEE.802.1Q_2014" format="defau lt" sectionFormat="of" derivedContent="IEEE.802.1Q_2014"/>.
The extension defined in this document is referred The extension defined in this document is referred
to as "Control Plane Based Pause". Other flow control methods are to as "Control-Plane-Based Pause". Other flow-control methods are
possible with DLEP, e.g., see <xref possible with DLEP; for example, see <xref target="I-D.ietf-manet-dlep-da-cred
target="I-D.ietf-manet-dlep-da-credit-extension"/> and <xref it-extension" format="default" sectionFormat="of" derivedContent="DLEP-DIFFSERV"
target="I-D.ietf-manet-dlep-credit-flow-control"/>. /> and
<xref target="I-D.ietf-manet-dlep-credit-flow-control" format="default" sectio
nFormat="of" derivedContent="DLEP-CREDIT"/>.
</t> </t>
<t> <t pn="section-1-3">
Note that Note that
this mechanism only applies to traffic that is to be transmitted on the this mechanism only applies to traffic that is to be transmitted on the
modem's attached data channel and not to DLEP control messages modem's attached data channel and not to DLEP control messages
themselves. Furthermore it applies only to the single sub-network themselves. Furthermore, it applies only to the single subnetwork
that is used to connect a modem and a router, and for traffic sent that is used to connect a modem and a router, and for traffic sent
from a router to a modem. from a router to a modem.
</t> </t>
<t> <t pn="section-1-4">
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" format="def
extension, and three new DLEP Data Items in <xref ault" sectionFormat="of" derivedContent="Section 2"/>.
target="sec-data-items"/>. Three new DLEP Data Items are defined in <xref target="sec-data-items" format=
</t> "default" sectionFormat="of" derivedContent="Section 3"/>.
<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="include" removeInRFC="false
</section> " pn="section-1.1">
<section anchor="sec-ext-type" title="Extension Usage and Identification"> <name slugifiedName="name-key-words">Key Words</name>
<t> <t pn="section-1.1-1">The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST
The use of the Control Plane Based Pause Extension SHOULD be configurable. NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>",
To indicate that the implementation supports use of the Control Plane Based P "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp
ause Extension, an 14>", "<bcp14>RECOMMENDED</bcp14>",
implementation MUST include the Control Plane Based Pause Extension Type "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL
</bcp14>" in this document
are to be interpreted as described in BCP 14
<xref target="RFC2119" format="default" sectionFormat="of" derivedContent="R
FC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedCont
ent="RFC8174"/> when,
and only when, they appear in all capitals, as shown here.</t>
</section>
</section>
<section anchor="sec-ext-type" numbered="true" toc="include" removeInRFC="fa
lse" pn="section-2">
<name slugifiedName="name-extension-usage-and-identif">Extension Usage and
Identification</name>
<t pn="section-2-1">
The use of the Control-Plane-Based Pause Extension <bcp14>SHOULD</bcp14> be c
onfigurable.
To indicate that the implementation supports the use of the
Control-Plane-Based Pause Extension, an
implementation <bcp14>MUST</bcp14> include the Control-Plane-Based Pause Exte
nsion Type
Value in the Extensions Supported Data Item. The Extensions Supported Value in the Extensions Supported Data Item. The Extensions Supported
Data Item is sent and processed according to <xref Data Item is sent and processed according to <xref target="RFC8175" format="d
target="RFC8175"/>. efault" sectionFormat="of" derivedContent="RFC8175"/>.
</t> </t>
<t> <t pn="section-2-2">
The Control Plane Based Pause Extension Type Value is TBA1, see <xref The Control-Plane-Based Pause Extension Type Value is 2; see <xref target="sec
target="sec-iana"/>. -iana" format="default" sectionFormat="of" derivedContent="Section 5"/>.
</t> </t>
</section> </section>
<section anchor="sec-data-items" title="Extension Data Items"> <section anchor="sec-data-items" numbered="true" toc="include" removeInRFC="
<t> false" pn="section-3">
Three data items are defined by this extension. The Queue Parameters <name slugifiedName="name-extension-data-items">Extension Data Items</name
>
<t pn="section-3-1">
Three Data Items are defined by this extension. The Queue Parameters
Data Item is used by a modem to provide information about the DSCPs it Data Item is used by a modem to provide information about the DSCPs it
uses in forwarding. The Pause Data Item is used by a modem to uses in forwarding. The Pause Data Item is used by a modem to
indicate when a router should cease sending packets and the Restart indicate when a router should cease sending packets, and the Restart
Data Item is used by a modem to indicate when a router can resume Data Item is used by a modem to indicate when a router can resume
sending packets. sending packets.
</t> </t>
<section anchor="sec-di-qp" title="Queue Parameters"> <section anchor="sec-di-qp" numbered="true" toc="include" removeInRFC="fal
<t> se" pn="section-3.1">
The Queue Parameters Data Item is sent by a modem to to a router to indicate D <name slugifiedName="name-queue-parameters">Queue Parameters</name>
SCP <t pn="section-3.1-1">
values that may be independently paused. This data item MUST be The Queue Parameters Data Item is sent by a modem to a router to indicate DSCP
values that may be independently paused. This Data Item <bcp14>MUST</bcp14> b
e
included in a Session Initialization Response Message that also included in a Session Initialization Response Message that also
contains the Control Plane Based Pause Extension Type Value in the contains the Control-Plane-Based Pause Extension Type Value in the
Extensions Supported Data Item. Updates to these parameters MAY be Extensions Supported Data Item. Updates to these parameters <bcp14>MAY</bcp14
sent by a modem by including the data item in Session Update > be
sent by a modem by including the Data Item in Session Update
Messages. Messages.
</t> </t>
<t> <t pn="section-3.1-2">
The Queue Parameters Data Item groups DSCPs into The Queue Parameters Data Item groups DSCPs into
logical queues, each of which is identified by a "Queue Index". The logical queues, each of which is identified by a "Queue Index" field. The
number of logical queues, or queue indexes, is variable as is the number of logical queues is variable, as is the
number of DSCPs associated with each queue. A queue size (in bytes) number of DSCPs associated with each queue. A queue size (in bytes)
is provided for informational purposes. Queue Indexes are numbered is provided for informational purposes. Queue Index fields are numbered
sequentially from zero, where queue index zero is a special case sequentially from zero, where queue index zero is a special case
covering DSCPs which are not otherwise associated with a Queue Index. covering DSCPs that are not otherwise associated with a Queue Index field.
</t> </t>
<t> <t pn="section-3.1-3">
An implementation that does not support DSCPs would indicate 1 queue An implementation that does not support DSCPs would indicate one queue
with 0 DSCPs, and the number of bytes that may be in its associated with zero DSCPs, and the number of bytes that may be in its associated
link transmit queue. Additional logical queues are represented in a link transmit queue. Additional logical queues are represented in a
variable series of Queue Parameter sub data items. variable series of Queue Parameter Sub-Data Items.
</t> </t>
<t> <t pn="section-3.1-4">
The format of the Queue Parameters Data Item is: The format of the Queue Parameters Data Item is:
</t> </t>
<t> <artwork name="" type="" align="left" alt="" pn="section-3.1-5">
<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 | | Num Queues | Scale | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Num Queues | Scale | Reserved | | Queue Parameter Sub-Data Item 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Queue Parameter Sub Data Item 1 | : ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: ... : | Queue Parameter Sub-Data Item n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
| Queue Parameter Sub Data Item n | <dl newline="true" spacing="normal" pn="section-3.1-6">
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ <dt pn="section-3.1-6.1">Data Item Type:</dt>
</artwork> <dd pn="section-3.1-6.2">23</dd>
</figure> <dt pn="section-3.1-6.3">Length:</dt>
</t> <dd pn="section-3.1-6.4">
<t> <t pn="section-3.1-6.4.1">Variable
<list style="hanging"> </t>
<t hangText="Data Item Type:">TBA2</t> <t pn="section-3.1-6.4.2">
<t hangText="Length:">Variable Per <xref target="RFC8175" format="default" sectionFormat="of" derivedCont
<vspace blankLines="1"/> ent="RFC8175"/>, Length
Per <xref target="RFC8175"/> Length is the number of octets in the Data Item, excluding the Type and
is the number of octets in the data item, excluding the Type and
Length fields. Length fields.
</t> </t>
<t hangText="Num Queues:"> </dd>
<vspace blankLines="1"/> <dt pn="section-3.1-6.5">Num Queues:</dt>
An 8-bit unsigned integer indicating the number of queues <dd pn="section-3.1-6.6">
represented in the data item. This field MUST contain a value of An 8-bit unsigned integer indicating the number of Queue Parameter
at least one (1), and is equal to one greater than the number of Sub‑Data Items that follow. This field <bcp14>MUST</bcp14> contain a valu
included Queue Parameter Sub Data Items. e of
</t> at least one (1).
<t hangText="Scale:"> </dd>
<vspace blankLines="1"/> <dt pn="section-3.1-6.7">Scale:</dt>
<dd pn="section-3.1-6.8">
<t pn="section-3.1-6.8.1">
A 4-bit unsigned integer indicating the scale used in the Queue A 4-bit unsigned integer indicating the scale used in the Queue
Size fields. The valid values are: Size Qn field. The valid values are:
<figure> </t>
<artwork> </dd>
Value Scale </dl>
------------ <table anchor="scale-table" align="center" pn="table-1">
0 B - Bytes (Octets) <name slugifiedName="name-queue-size-qn-field-values">Queue Size Qn Fi
1 KiB - Kilobytes (1024 B) eld Values</name>
2 MiB - Megabytes (1024 KiB) <thead>
3 GiB - Gigabytes (1024 MiB) <tr>
</artwork> <th align="left" colspan="1" rowspan="1">Value</th>
</figure> <th align="left" colspan="1" rowspan="1">Scale</th>
</t> </tr>
<t hangText="Reserved:"> </thead>
<vspace blankLines="1"/> <tbody>
A 20-bit field that MUST be set to zero by the sender (a modem) and ignore <tr>
d by the <td align="left" colspan="1" rowspan="1">0</td>
<td align="left" colspan="1" rowspan="1">B - Bytes (Octets)</td>
</tr>
<tr>
<td align="left" colspan="1" rowspan="1">1</td>
<td align="left" colspan="1" rowspan="1">KB - Kilobytes (1024 B)</
td>
</tr>
<tr>
<td align="left" colspan="1" rowspan="1">2</td>
<td align="left" colspan="1" rowspan="1">MB - Megabytes (1024 KB)<
/td>
</tr>
<tr>
<td align="left" colspan="1" rowspan="1">3</td>
<td align="left" colspan="1" rowspan="1">GB - Gigabytes (1024 MB)<
/td>
</tr>
</tbody>
</table>
<dl newline="false" spacing="normal" pn="section-3.1-8">
<dt pn="section-3.1-8.1">Reserved:</dt>
<dd pn="section-3.1-8.2">
A 20-bit field that <bcp14>MUST</bcp14> be set to zero (0) by the sender (
a modem) and ignored by the
receiver (a router). receiver (a router).
</t> </dd>
</list> </dl>
</t> <section anchor="sec-di-qp-sub" numbered="true" toc="include" removeInRF
C="false" pn="section-3.1.1">
<section anchor="sec-di-qp-sub" title="Queue Parameter Sub Data Item"> <name slugifiedName="name-queue-parameter-sub-data-it">Queue Parameter
Sub-Data Item</name>
<t> <t pn="section-3.1.1-1">
Queue Parameter Sub Data Items are an unordered list composed of Queue Parameter Sub-Data Items are an unordered list composed of
sub data items with a common format. The format of the Queue Parameter Su Sub‑Data Items with a common format. The format of the Queue
b Parameter Sub‑Data Item is patterned after the standard format for
Data Item is patterned after the standard DLEP data item format, the DLEP Data Item; see <xref target="RFC8175" sectionFormat="comma" secti
see <xref target="RFC8175"/> Section 11.3. Any errors on="11.3" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8175#secti
or inconsistencies encountered in parsing Sub Data Items are on-11.3" derivedContent="RFC8175"/>.
Any errors or inconsistencies encountered in parsing Sub-Data Items are
handled in the same fashion as any other Data Item parsing error handled in the same fashion as any other Data Item parsing error
encountered in DLEP. encountered in DLEP.
In particular, the receiving implementation MUST issue a In particular, the receiving implementation <bcp14>MUST</bcp14> issue a
Session Termination Message containing a Status Data Item with Session Termination Message containing a Status Data Item with
status code set to 130 'Invalid Data' and transition to the status code set to 130 ("Invalid Data") and transition to the
Session Termination state. Session Termination state.
</t> </t>
<t> <t pn="section-3.1.1-2">
The format of the Queue Parameter Sub Data Item is: The format of the Queue Parameter Sub-Data Item is:
</t> </t>
<t> <artwork name="" type="" align="left" alt="" pn="section-3.1.1-3">
<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 | Sub-Data Item Type (1) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub Data Item Type (1) | Length | | Value... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
| Value... | <t pn="section-3.1.1-4">
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure>
</t>
<t>
and Value has the format: and Value has the format:
</t> </t>
<t> <artwork name="" type="" align="left" alt="" pn="section-3.1.1-5">
<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 | Queue Index | Queue Size Qn |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Queue Index | Queue Size Qn | | Num DSCPs Qn | DS Field Qn | ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Num DSCPs Qn | DS Field Qn | ... : : ... | DS Field Qn |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
: ... | DS Field Qn | <dl newline="true" spacing="normal" pn="section-3.1.1-6">
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ <dt pn="section-3.1.1-6.1">Sub-Data Item Type:</dt>
</artwork> <dd pn="section-3.1.1-6.2">
</figure>
</t>
<t>
<list style="hanging">
<t hangText="Sub Data Item Type:">
<vspace blankLines="1"/>
A 16-bit unsigned integer that indicates the type and A 16-bit unsigned integer that indicates the type and
corresponding format of the Sub Data Item's Value field. Sub Data corresponding format of the Sub-Data Item's Value field. Sub-Data
Item Types are scoped within the Data Item in which they are Item Types are scoped within the Data Item in which they are
carried, i.e., the Sub Data Item Type field MUST be used together carried, i.e., the Sub-Data Item Type field <bcp14>MUST</bcp14> be used to
with the Queue Parameters Data Item Type to identify the format of the Sub gether
Data with the Queue Parameters Data Item Type to identify the format of the Sub
Item. This field MUST be set to one (1) for the Queue Parameter -Data
Sub Data Item. Item. This field <bcp14>MUST</bcp14> be set to one (1) for the Queue Para
</t> meter
<t hangText="Length:">Variable Sub-Data Item.
<vspace blankLines="1"/> </dd>
<dt pn="section-3.1.1-6.3">Length:</dt>
<dd pn="section-3.1.1-6.4">
<t pn="section-3.1.1-6.4.1">Variable
</t>
<t pn="section-3.1.1-6.4.2">
Length Length
is the number of octets in the sub data item, excluding the Type and is the number of octets in the Sub-Data Item, excluding the Type and
Length fields. Length fields.
</t> </t>
<t hangText="Queue Index:"> </dd>
<vspace blankLines="1"/> <dt pn="section-3.1.1-6.5">Queue Index:</dt>
<dd pn="section-3.1.1-6.6">
An 8-bit field indicating the queue index of the queue An 8-bit field indicating the queue index of the queue
parameter represented in the sub data item. Only the first parameter represented in the Sub-Data Item. Only the first
instance of a particular Queue Index value is meaningful. instance of a particular Queue Index value is meaningful.
Subsequent sub data items containing the same Queue Index values, Subsequent Sub-Data Items containing the same Queue Index values,
if present, MAY be logged via a management interface and MUST if present, <bcp14>MAY</bcp14> be logged via a management interface and <b
otherwise be ignored. Note that the value 255 is reserved and MUST cp14>MUST</bcp14>
NOT be used in this field. otherwise be ignored. Note that the value 255 is reserved and <bcp14>MUST
</t> NOT</bcp14> be used in this field.
<t hangText="Queue Size Qn:"> </dd>
<vspace blankLines="1"/> <dt pn="section-3.1.1-6.7">Queue Size Qn:</dt>
<dd pn="section-3.1.1-6.8">
A 24-bit unsigned integer representing the size, in the octet A 24-bit unsigned integer representing the size, in the octet
scale indicated by the Scale field, of the queue supporting scale indicated by the Scale field, of the queue that supports
traffic with the DSCPs associated with the queue index. the traffic with the DSCPs associated with the queue index.
</t> </dd>
<t hangText="Num DSCPs Qn:"> <dt pn="section-3.1.1-6.9">Num DSCPs Qn:</dt>
<vspace blankLines="1"/> <dd pn="section-3.1.1-6.10">
An 8-bit unsigned integer indicating the number of DSCPs An 8-bit unsigned integer indicating the number of DSCPs
associated with the queue index associated with the sub data item. associated with the queue index associated with the Sub-Data Item.
This field MUST contain a value of at least one (1). </dd>
</t> <dt pn="section-3.1.1-6.11">DS Field Qn:</dt>
<t hangText="DS Field Qn:"> <dd pn="section-3.1.1-6.12">
<vspace blankLines="1"/> <t pn="section-3.1.1-6.12.1">
The data item contains a sequence of 8 bit DS Fields. The The Data Item contains a sequence of 8-bit DS fields. The
number of DS Fields present MUST equal the value of the number of DS fields present <bcp14>MUST</bcp14> equal the Num DSCPs Qn fie
Num DSCPs field. ld value.
<vspace blankLines="1"/>
The DS Field structure is the same as <xref target="RFC2474"/>.
<figure>
<artwork>
0 1 2 3 4 5 6 7
+---+---+---+---+---+---+---+---+
| DSCP | CU |
+---+---+---+---+---+---+---+---+
DSCP: differentiated services codepoint </t>
CU: currently unused, MUST be zero <t pn="section-3.1.1-6.12.2">
</artwork> The DS field structure is the same as the structure shown in
</figure> <xref target="RFC2474" format="default" sectionFormat="of" derivedContent=
</t> "RFC2474"/>.
</list> </t>
</t> <artwork name="" type="" align="left" alt="" pn="section-3.1.1-6.1
</section> 2.3">
</section> 0 1 2 3 4 5 6 7
<section anchor="sec-di-pause" title="Pause"> +---+---+---+---+---+---+---+---+
<t> | DSCP | CU |
+---+---+---+---+---+---+---+---+</artwork>
<t pn="section-3.1.1-6.12.4">DSCP: Differentiated Services Code Po
int</t>
<t pn="section-3.1.1-6.12.5">CU: Currently Unused; <bcp14>MUST</bc
p14> be zero</t>
</dd>
</dl>
</section>
</section>
<section anchor="sec-di-pause" numbered="true" toc="include" removeInRFC="
false" pn="section-3.2">
<name slugifiedName="name-pause">Pause</name>
<t pn="section-3.2-1">
The Pause Data Item is sent by a modem to a router to indicate to its peer tha t The Pause Data Item is sent by a modem to a router to indicate to its peer tha t
traffic is to be suppressed, i.e., paused. traffic is to be suppressed, i.e., paused.
The motivating use case for this data item is when a modem's The motivating use case for this Data Item is when a modem's
internal queue length exceeds a particular threshold. Other use cases internal queue length exceeds a particular threshold. Other use cases
are possible, e.g., when there are non queue related congestion points are possible, e.g., when there are non‑queue-related congestion points
within a modem. Such cases are not explicitly described in this within a modem. Such cases are not explicitly described in this
document. document.
</t> </t>
<t> <t pn="section-3.2-2">
A modem can indicate that traffic is to be suppressed on a device-wide A modem can indicate that traffic is to be suppressed on a device‑wide
or destination-specific basis. An example of when a modem might use or destination-specific basis. An example of when a modem might use
device wide indications is when output queues are shared across all device‑wide suppression is when output queues are shared across all
destinations, and destination specific might be used when per destinations. Destination-specific suppression might be used when
destination queuing is used. To indicate that suppression applies to per‑destination queuing is used. To indicate that suppression applies to
all destinations, a modem MUST send the Pause Data Item in a Session all destinations, a modem <bcp14>MUST</bcp14> send the Pause Data Item in a Se
ssion
Update Message. To indicate that suppression applies to a particular Update Message. To indicate that suppression applies to a particular
destination a modem MUST send the Pause Data Item in a Destination destination, a modem <bcp14>MUST</bcp14> send the Pause Data Item in a Destina tion
Update Message. Update Message.
</t> </t>
<t> <t pn="section-3.2-3">
Each Pause Data Item identifies the traffic to be suppressed by the Each Pause Data Item identifies the traffic to be suppressed by the
Queue Index defined by <xref target="sec-di-qp"/>, which in turn Queue Index field (<xref target="sec-di-qp" format="default" sectionFormat="of
indicates a set of traffic identified by DSCPs. The special value of " derivedContent="Section 3.1"/>), which in turn
255 is used to indicate that all traffic is to be suppressed. indicates traffic identified by one or more DSCPs. The special value of 255
is used to indicate that all traffic is to be suppressed.
</t> </t>
<t> <t pn="section-3.2-4">
While there is no restriction on the number of Messages containing While there is no restriction on the number of messages containing
Pause Data Item that may be sent by a modem, a modem SHOULD include Pause Data Items that may be sent by a modem, a modem <bcp14>SHOULD</bcp14> in
clude
multiple queue indexes in the same message when possible. multiple queue indexes in the same message when possible.
</t> </t>
<t> <t pn="section-3.2-5">
A router which receives the Pause Data Item MUST cease sending A router that receives the Pause Data Item <bcp14>MUST</bcp14> cease sending
the identified traffic to the modem. This may of course translate into the identified traffic to the modem. This may of course translate into
the router's queues exceeding their own thresholds. the router's queues exceeding their own thresholds.
If a received Pause Data Item contains a Queue Index value other than If a received Pause Data Item contains a Queue Index value other than
255 or a queue index established by a Session Initialization or 255 or a queue index established by a Session Initialization or
Session Update Message, the router MUST terminate the session with a Session Update Message, the router <bcp14>MUST</bcp14> terminate the session w
Status Data Item indicating Invalid Data. ith a
Status Data Item indicating "Invalid Data".
</t> </t>
<t> <t pn="section-3.2-6">
The format of the Pause Data Item is: The format of the Pause Data Item is:
</t> </t>
<t> <artwork name="" type="" align="left" alt="" pn="section-3.2-7">
<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 | | Queue Index | ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Queue Index | ... : : ... | Queue Index |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
: ... | Queue Index | <dl newline="true" spacing="normal" pn="section-3.2-8">
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ <dt pn="section-3.2-8.1">Data Item Type:</dt>
</artwork> <dd pn="section-3.2-8.2">24</dd>
</figure> <dt pn="section-3.2-8.3">Length:</dt>
</t> <dd pn="section-3.2-8.4">
<t> <t pn="section-3.2-8.4.1">Variable
<list style="hanging"> </t>
<t hangText="Data Item Type:">TBA3</t> <t pn="section-3.2-8.4.2">
<t hangText="Length:">Variable Per <xref target="RFC8175" format="default" sectionFormat="of" derivedCont
<vspace blankLines="1"/> ent="RFC8175"/>, Length
Per <xref target="RFC8175"/> Length is the number of octets in the Data Item, excluding the Type and
is the number of octets in the data item, excluding the Type and
Length fields. It will equal the number of Queue Index fields Length fields. It will equal the number of Queue Index fields
carried in the data item. carried in the Data Item.
</t> </t>
<t hangText="Queue Index:"> </dd>
<vspace blankLines="1"/> <dt pn="section-3.2-8.5">Queue Index:</dt>
<dd pn="section-3.2-8.6">
One or more 8-bit fields used to indicate a queue index defined by One or more 8-bit fields used to indicate a queue index defined by
a Queue Parameters Data Item. The special value of 255 indicates a Queue Parameters Data Item. The special value of 255 indicates
all traffic is to be suppressed to the modem, when the data item that (1) all traffic to the modem is to be suppressed when the
is carried in a Session Update Message, or is to be suppressed to a destin Data Item is carried in a Session Update Message or (2) all
ation, when the traffic to a particular destination is to be suppressed when the
data item is carried in Destination Update Message. Data Item is carried in a Destination Update Message.
</t> </dd>
</list> </dl>
</t> </section>
<section anchor="sec-di-restart" numbered="true" toc="include" removeInRFC
</section> ="false" pn="section-3.3">
<section anchor="sec-di-restart" title="Restart"> <name slugifiedName="name-restart">Restart</name>
<t> <t pn="section-3.3-1">
The Restart Data Item is sent by a modem to a router to indicate to its peer t hat The Restart Data Item is sent by a modem to a router to indicate to its peer t hat
transmission of previously suppressed traffic may be resumed. An transmission of previously suppressed traffic may be resumed. An
example of when a modem might send this data item is when an internal example of when a modem might send this Data Item is when an internal
queue length drops below a particular threshold. queue length drops below a particular threshold.
</t> </t>
<t> <t pn="section-3.3-2">
The sending of this data item parallels the Pause Data Item, see the The sending of this Data Item parallels the Pause Data Item
previous section, and follows the same rules. As above, to (see <xref target="sec-di-pause" format="default" sectionFormat="of" derivedCo
indicate that transmission can resume to all destinations, a modem MUST ntent="Section 3.2"/>) and follows the same rules.
send the Restart Data Item in a Session Update Message. It also To indicate that transmission can resume
includes that to indicate that transmission can resume to a particular to all destinations, a modem <bcp14>MUST</bcp14> send the Restart Data Item in
destination a modem MUST send the Pause Restart Item in a Destination a
Update Message. Finally, queue indexes are interpreted in the same Session Update Message. To indicate that
way as in the Pause Data Item.. transmission can resume to a particular destination, a modem <bcp14>MUST</bcp1
4> send
the Restart Data Item in a Destination Update Message.
Finally, the same rules apply to queue indexes.
</t> </t>
<t> <t pn="section-3.3-3">
A router which receives the Restart Data Item SHOULD resume A router that receives the Restart Data Item <bcp14>SHOULD</bcp14> resume
transmission of the identified traffic to the modem. transmission of the identified traffic to the modem.
</t> </t>
<t> <t pn="section-3.3-4">
The format of the Restart Data Item matches the Pause Data Item and is: The format of the Restart Data Item matches the Pause Data Item and is:
</t>
<t>
<figure>
<artwork>
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Queue Index | ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: ... | Queue Index |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure>
</t>
<t>
<list style="hanging">
<t hangText="Data Item Type:">TBA4</t>
<t hangText="Length:">See <xref target="sec-di-pause"/>.</t>
<t hangText="Queue Index:">See <xref target="sec-di-pause"/>.</t>
</list>
</t> </t>
</section> <artwork name="" type="" align="left" alt="" pn="section-3.3-5">
</section> 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
<section anchor="sec-sec" title="Security Considerations"> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<t> | Data Item Type | Length |
The extension introduces a new mechanism for flow control between a +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Queue Index | ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: ... | Queue Index |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
<dl newline="false" spacing="normal" pn="section-3.3-6">
<dt pn="section-3.3-6.1">Data Item Type:</dt>
<dd pn="section-3.3-6.2">25</dd>
<dt pn="section-3.3-6.3">Length:</dt>
<dd pn="section-3.3-6.4">See <xref target="sec-di-pause" format="defau
lt" sectionFormat="of" derivedContent="Section 3.2"/>.</dd>
<dt pn="section-3.3-6.5">Queue Index:</dt>
<dd pn="section-3.3-6.6">See <xref target="sec-di-pause" format="defau
lt" sectionFormat="of" derivedContent="Section 3.2"/>.</dd>
</dl>
</section>
</section>
<section anchor="sec-sec" numbered="true" toc="include" removeInRFC="false"
pn="section-4">
<name slugifiedName="name-security-considerations">Security Considerations
</name>
<t pn="section-4-1">
The extension defined in this document introduces a new mechanism for flow co
ntrol between a
router and modem using DLEP. The router and modem using DLEP. The
extension does not introduce any vulnerabilities that are inherently differen t extension does not introduce any vulnerabilities that are inherently differen t
from those documented in <xref target="RFC8175"/>. from those documented in <xref target="RFC8175" format="default" sectionForma
The approach taken to Security in that document applies equally t="of" derivedContent="RFC8175"/>.
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>
<t> <t pn="section-4-2">
Implementations of the extension defined in this document MUST support Implementations of the extension defined in this document <bcp14>MUST</bcp14>
configuration of TLS usage, as describe in <xref target="RFC8175"/>, support
the configuration and use of TLS, as described in <xref target="RFC8175" form
at="default" sectionFormat="of" derivedContent="RFC8175"/>,
in order to protect configurations where injection attacks are in order to protect configurations where injection attacks are
possible, i.e., when the link between a modem and router is not possible, i.e., when the link between a modem and router is not
otherwise protected. otherwise protected.
</t> </t>
<t> <t pn="section-4-3">
Note that this extension does allow a compromised or impersonating Note that this extension does allow a compromised or impersonating
modem to suppress transmission by the router or a switch that modem to suppress transmission by the router or a switch that
interconnects the modem and router. Similar attacks are interconnects the modem and router. Similar attacks are
generally possible base DLEP, for example an impersonating modem may generally possible with base DLEP -- for example, an impersonating modem may
cause a session reset or a compromised modem simply can cause a session reset, or a compromised modem can simply
drop all traffic destined to, or sent by a router. <xref drop all traffic destined for or sent by a router.
target="RFC8175"/> defines the use of TLS to protect against the <xref target="RFC8175" format="default" sectionFormat="of" derivedContent="RFC
impersonating attacker. 8175"/> defines the use of TLS to protect against such
</t> impersonating attackers.
</section>
<section anchor="sec-iana" title="IANA Considerations">
<t>
This document requests the assignment of 4 values by IANA. All
assignments are to registries defined by <xref
target="RFC8175"/>.
</t> </t>
<section anchor="sec-iana-ext" title="Extension Type Value"> </section>
<t> <section anchor="sec-iana" numbered="true" toc="include" removeInRFC="false"
This document requests 1 new assignment to the DLEP Extensions pn="section-5">
Registry named "Extension Type Values" in the range with the <name slugifiedName="name-iana-considerations">IANA Considerations</name>
"Specification Required" policy. The requested value is as <t pn="section-5-1">
follows: This document assigns four new values and creates a new subregistry in the
"Dynamic Link Exchange Protocol (DLEP) Parameters" registry.
</t> </t>
<texttable anchor="table_et" title="Requested Extension Type Value"> <section anchor="sec-iana-ext" numbered="true" toc="include" removeInRFC="
<preamble></preamble> false" pn="section-5.1">
<ttcol>Code</ttcol> <ttcol>Description</ttcol> <name slugifiedName="name-extension-type-value">Extension Type Value</na
<c>TBA1</c> <c>Control Plane Based Pause</c> me>
<postamble></postamble> <t pn="section-5.1-1">
</texttable> This document adds a new assignment to the DLEP extensions
</section> registry named "Extension Type Values" <xref target="RFC8175" format="default"
<section anchor="sec-iana-di" title="Data Item Values"> sectionFormat="of" derivedContent="RFC8175"/>, per the
<t> "Specification Required" policy <xref target="RFC8126" format="default" sectio
This document requests 3 new assignments to the DLEP Data Item nFormat="of" derivedContent="RFC8126"/>. IANA
Registry named "Data Item Type Values" in the range with the "Specification has assigned the following value:
Required" policy. The requested values are as follows:
</t> </t>
<texttable anchor="table_di" title="Requested Data Item Values"> <t pn="section-5.1-2"/>
<preamble></preamble> <table anchor="table_et" align="center" pn="table-2">
<ttcol>Type Code</ttcol> <ttcol>Description</ttcol> <name slugifiedName="name-extension-type-value-2">Extension Type Value
<c>TBA2</c> <c>Queue Parameters</c> </name>
<c>TBA3</c> <c>Pause</c> <thead>
<c>TBA4</c> <c>Restart</c> <tr>
<postamble></postamble> <th align="left" colspan="1" rowspan="1">Code</th>
</texttable> <th align="left" colspan="1" rowspan="1">Description</th>
</section> </tr>
</thead>
<section anchor="sec-iana-sdi" title="Queue Parameters Sub Data Item Values"> <tbody>
<t> <tr>
Upon approval of this document, IANA is requested to create a new <td align="left" colspan="1" rowspan="1">2</td>
DLEP registry, named "Queue Parameters Sub Data Item Type Values". <td align="left" colspan="1" rowspan="1">Control-Plane-Based Pause
</td>
</tr>
</tbody>
</table>
<t pn="section-5.1-4"/>
</section>
<section anchor="sec-iana-di" numbered="true" toc="include" removeInRFC="f
alse" pn="section-5.2">
<name slugifiedName="name-data-item-values">Data Item Values</name>
<t pn="section-5.2-1">
This document adds three new assignments to the DLEP Data Item
registry named "Data Item Type Values" <xref target="RFC8175" format="default"
sectionFormat="of" derivedContent="RFC8175"/>, per the
"Specification Required" policy <xref target="RFC8126" format="default" sectio
nFormat="of" derivedContent="RFC8126"/>. IANA
has assigned the following values:</t>
<t pn="section-5.2-2"/>
<table anchor="table_di" align="center" pn="table-3">
<name slugifiedName="name-data-item-values-2">Data Item Values</name>
<thead>
<tr>
<th align="left" colspan="1" rowspan="1">Type Code</th>
<th align="left" colspan="1" rowspan="1">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" colspan="1" rowspan="1">23</td>
<td align="left" colspan="1" rowspan="1">Queue Parameters</td>
</tr>
<tr>
<td align="left" colspan="1" rowspan="1">24</td>
<td align="left" colspan="1" rowspan="1">Pause</td>
</tr>
<tr>
<td align="left" colspan="1" rowspan="1">25</td>
<td align="left" colspan="1" rowspan="1">Restart</td>
</tr>
</tbody>
</table>
<t pn="section-5.2-4"/>
</section>
<section anchor="sec-iana-sdi" numbered="true" toc="include" removeInRFC="
false" pn="section-5.3">
<name slugifiedName="name-queue-parameter-sub-data-ite">Queue Parameter
Sub-Data Item Values</name>
<t pn="section-5.3-1">IANA has created a new DLEP registry named "Queue
Parameter Sub-Data Item
Type Values".
</t> </t>
<t> <t pn="section-5.3-2"><xref target="table_sdi" format="default" sectionF
The following table provides initial registry values and the <xref ormat="of" derivedContent="Table 4"/> provides initial registry values and the
target="RFC8126"/> defined policies that should apply to the registry: registration policies <xref target="RFC8126" format="default" sectionFormat="o
f" derivedContent="RFC8126"/> that apply:
</t> </t>
<texttable anchor="table_sdi" title=""> <table anchor="table_sdi" align="center" pn="table-4">
<preamble></preamble> <name slugifiedName="name-initial-registry-values">Initial Registry Va
<ttcol>Type Code</ttcol> <ttcol>Description/Policy</ttcol> lues</name>
<c>0</c> <c>Reserved</c> <thead>
<c>1</c> <c>Queue Parameter</c> <tr>
<c>2-65407</c> <c>Specification Required</c> <th align="left" colspan="1" rowspan="1">Type Code</th>
<c>65408-65534</c> <c>Private Use</c> <th align="left" colspan="1" rowspan="1">Description/Policy</th>
<c>65535</c> <c>Reserved</c> </tr>
<postamble></postamble> </thead>
</texttable> <tbody>
</section> <tr>
<td align="left" colspan="1" rowspan="1">0</td>
</section> <td align="left" colspan="1" rowspan="1">Reserved</td>
</middle> </tr>
<tr>
<?rfc needLines="20"?> <td align="left" colspan="1" rowspan="1">1</td>
<back> <td align="left" colspan="1" rowspan="1">Queue Parameter</td>
<references title="Normative References"> </tr>
<tr>
<?rfc include="reference.RFC.2119"?> <td align="left" colspan="1" rowspan="1">2-65407</td>
<?rfc include="reference.RFC.8174"?> <td align="left" colspan="1" rowspan="1">Specification Required</t
<?rfc include="reference.RFC.8175"?> d>
</tr>
</references> <tr>
<td align="left" colspan="1" rowspan="1">65408-65534</td>
<references title="Informative References"> <td align="left" colspan="1" rowspan="1">Private Use</td>
</tr>
<?rfc include="reference.I-D.ietf-manet-dlep-da-credit-extension"?> <tr>
<?rfc include="reference.I-D.ietf-manet-dlep-credit-flow-control"?> <td align="left" colspan="1" rowspan="1">65535</td>
<?rfc include="reference.RFC.2474"?> <td align="left" colspan="1" rowspan="1">Reserved</td>
<?rfc include="reference.RFC.2475"?> </tr>
<?rfc include="reference.RFC.5578"?> </tbody>
<?rfc include="reference.RFC.8126"?> </table>
</section>
<?rfc include="https://xml2rfc.tools.ietf.org/public/rfc/bibxml6/reference.IEEE. </section>
802.1Q_2014.xml"?> </middle>
</references> <back>
<?rfc needLines="100"?> <displayreference target="I-D.ietf-manet-dlep-da-credit-extension" to="DLEP-
<section title="Acknowledgments"> DIFFSERV"/>
<t> <displayreference target="I-D.ietf-manet-dlep-credit-flow-control" to="DLEP-
The sub data item format was inspired by Rick Taylor's "Data Item CREDIT"/>
<references pn="section-6">
<name slugifiedName="name-references">References</name>
<references pn="section-6.1">
<name slugifiedName="name-normative-references">Normative References</na
me>
<reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2
119" quoteTitle="true" derivedAnchor="RFC2119">
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</tit
le>
<author initials="S." surname="Bradner" fullname="S. Bradner">
<organization showOnFrontPage="true"/>
</author>
<date year="1997" month="March"/>
<abstract>
<t>In many standards track documents several words are used to sig
nify the requirements in the specification. These words are often capitalized.
This document defines these words as they should be interpreted in IETF document
s. This document specifies an Internet Best Current Practices for the Internet
Community, and requests discussion and suggestions for improvements.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="2119"/>
<seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference>
<reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8
174" quoteTitle="true" derivedAnchor="RFC8174">
<front>
<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</ti
tle>
<author initials="B." surname="Leiba" fullname="B. Leiba">
<organization showOnFrontPage="true"/>
</author>
<date year="2017" month="May"/>
<abstract>
<t>RFC 2119 specifies common key words that may be used in protoco
l specifications. This document aims to reduce the ambiguity by clarifying tha
t only UPPERCASE usage of the key words have the defined special meanings.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="8174"/>
<seriesInfo name="DOI" value="10.17487/RFC8174"/>
</reference>
<reference anchor="RFC8175" target="https://www.rfc-editor.org/info/rfc8
175" quoteTitle="true" derivedAnchor="RFC8175">
<front>
<title>Dynamic Link Exchange Protocol (DLEP)</title>
<author initials="S." surname="Ratliff" fullname="S. Ratliff">
<organization showOnFrontPage="true"/>
</author>
<author initials="S." surname="Jury" fullname="S. Jury">
<organization showOnFrontPage="true"/>
</author>
<author initials="D." surname="Satterwhite" fullname="D. Satterwhite
">
<organization showOnFrontPage="true"/>
</author>
<author initials="R." surname="Taylor" fullname="R. Taylor">
<organization showOnFrontPage="true"/>
</author>
<author initials="B." surname="Berry" fullname="B. Berry">
<organization showOnFrontPage="true"/>
</author>
<date year="2017" month="June"/>
<abstract>
<t>When routing devices rely on modems to effect communications ov
er wireless links, they need timely and accurate knowledge of the characteristic
s of the link (speed, state, etc.) in order to make routing decisions. In mobil
e or other environments where these characteristics change frequently, manual co
nfigurations or the inference of state through routing or transport protocols do
es not allow the router to make the best decisions. This document introduces a
new protocol called the Dynamic Link Exchange Protocol (DLEP), which provides a
bidirectional, event-driven communication channel between the router and the mod
em to facilitate communication of changing link characteristics.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="8175"/>
<seriesInfo name="DOI" value="10.17487/RFC8175"/>
</reference>
</references>
<references pn="section-6.2">
<name slugifiedName="name-informative-references">Informative References
</name>
<reference anchor="I-D.ietf-manet-dlep-credit-flow-control" quoteTitle="
true" target="https://tools.ietf.org/html/draft-ietf-manet-dlep-credit-flow-cont
rol-04" derivedAnchor="DLEP-CREDIT">
<front>
<title>DLEP Credit-Based Flow Control Messages and Data Items</title
>
<author initials="B" surname="Cheng" fullname="Bow-Nan Cheng">
<organization showOnFrontPage="true"/>
</author>
<author initials="D" surname="Wiggins" fullname="David Wiggins">
<organization showOnFrontPage="true"/>
</author>
<author initials="L" surname="Berger" fullname="Lou Berger">
<organization showOnFrontPage="true"/>
</author>
<author initials="S" surname="Ratliff" fullname="Stan Ratliff">
<organization showOnFrontPage="true"/>
</author>
<date month="March" day="6" year="2019"/>
<abstract>
<t>This document defines new DLEP protocol Data Items that are use
d to support credit-based flow control. Credit window control is used to regula
te when data may be sent to an associated virtual or physical queue. The Data I
tems are defined in an extensible and reusable fashion. Their use will be manda
ted in other documents defining specific DLEP extensions.</t>
</abstract>
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-manet-dlep-credit-
flow-control-04"/>
<format type="TXT" target="http://www.ietf.org/internet-drafts/draft-i
etf-manet-dlep-credit-flow-control-04.txt"/>
<refcontent>Work in Progress</refcontent>
</reference>
<reference anchor="I-D.ietf-manet-dlep-da-credit-extension" quoteTitle="
true" target="https://tools.ietf.org/html/draft-ietf-manet-dlep-da-credit-extens
ion-07" derivedAnchor="DLEP-DIFFSERV">
<front>
<title>DLEP DiffServ Aware Credit Window Extension</title>
<author initials="B" surname="Cheng" fullname="Bow-Nan Cheng">
<organization showOnFrontPage="true"/>
</author>
<author initials="D" surname="Wiggins" fullname="David Wiggins">
<organization showOnFrontPage="true"/>
</author>
<author initials="L" surname="Berger" fullname="Lou Berger">
<organization showOnFrontPage="true"/>
</author>
<date month="March" day="6" year="2019"/>
<abstract>
<t>This document defines an extension to the DLEP protocol that en
ables a DiffServ aware credit-window scheme for destination-specific and shared
flow control.</t>
</abstract>
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-manet-dlep-da-cred
it-extension-07"/>
<format type="TXT" target="http://www.ietf.org/internet-drafts/draft-i
etf-manet-dlep-da-credit-extension-07.txt"/>
<refcontent>Work in Progress</refcontent>
</reference>
<reference anchor="IEEE.802.1Q_2014" target="https://ieeexplore.ieee.org
/document/6991462" quoteTitle="true" derivedAnchor="IEEE.802.1Q_2014">
<front>
<title>IEEE Standard for Local and metropolitan area networks--Bridg
es
and Bridged Networks</title>
<seriesInfo name="IEEE" value="802.1Q-2014"/>
<author>
<organization showOnFrontPage="true">IEEE</organization>
</author>
</front>
</reference>
<reference anchor="RFC2474" target="https://www.rfc-editor.org/info/rfc2
474" quoteTitle="true" derivedAnchor="RFC2474">
<front>
<title>Definition of the Differentiated Services Field (DS Field) in
the IPv4 and IPv6 Headers</title>
<author initials="K." surname="Nichols" fullname="K. Nichols">
<organization showOnFrontPage="true"/>
</author>
<author initials="S." surname="Blake" fullname="S. Blake">
<organization showOnFrontPage="true"/>
</author>
<author initials="F." surname="Baker" fullname="F. Baker">
<organization showOnFrontPage="true"/>
</author>
<author initials="D." surname="Black" fullname="D. Black">
<organization showOnFrontPage="true"/>
</author>
<date year="1998" month="December"/>
<abstract>
<t>This document defines the IP header field, called the DS (for d
ifferentiated services) field. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="2474"/>
<seriesInfo name="DOI" value="10.17487/RFC2474"/>
</reference>
<reference anchor="RFC2475" target="https://www.rfc-editor.org/info/rfc2
475" quoteTitle="true" derivedAnchor="RFC2475">
<front>
<title>An Architecture for Differentiated Services</title>
<author initials="S." surname="Blake" fullname="S. Blake">
<organization showOnFrontPage="true"/>
</author>
<author initials="D." surname="Black" fullname="D. Black">
<organization showOnFrontPage="true"/>
</author>
<author initials="M." surname="Carlson" fullname="M. Carlson">
<organization showOnFrontPage="true"/>
</author>
<author initials="E." surname="Davies" fullname="E. Davies">
<organization showOnFrontPage="true"/>
</author>
<author initials="Z." surname="Wang" fullname="Z. Wang">
<organization showOnFrontPage="true"/>
</author>
<author initials="W." surname="Weiss" fullname="W. Weiss">
<organization showOnFrontPage="true"/>
</author>
<date year="1998" month="December"/>
<abstract>
<t>This document defines an architecture for implementing scalable
service differentiation in the Internet. This memo provides information for th
e Internet community.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="2475"/>
<seriesInfo name="DOI" value="10.17487/RFC2475"/>
</reference>
<reference anchor="RFC5578" target="https://www.rfc-editor.org/info/rfc5
578" quoteTitle="true" derivedAnchor="RFC5578">
<front>
<title>PPP over Ethernet (PPPoE) Extensions for Credit Flow and Link
Metrics</title>
<author initials="B." surname="Berry" fullname="B. Berry" role="edit
or">
<organization showOnFrontPage="true"/>
</author>
<author initials="S." surname="Ratliff" fullname="S. Ratliff">
<organization showOnFrontPage="true"/>
</author>
<author initials="E." surname="Paradise" fullname="E. Paradise">
<organization showOnFrontPage="true"/>
</author>
<author initials="T." surname="Kaiser" fullname="T. Kaiser">
<organization showOnFrontPage="true"/>
</author>
<author initials="M." surname="Adams" fullname="M. Adams">
<organization showOnFrontPage="true"/>
</author>
<date year="2010" month="February"/>
<abstract>
<t>This document extends the Point-to-Point Protocol over Ethernet
(PPPoE) with an optional credit-based flow control mechanism and an optional Li
nk Quality Metric report. These optional extensions improve the performance of
PPPoE over media with variable bandwidth and limited buffering, such as mobile p
oint-to-point radio links. This document is not an Internet Standards Track sp
ecification; it is published for informational purposes.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="5578"/>
<seriesInfo name="DOI" value="10.17487/RFC5578"/>
</reference>
<reference anchor="RFC8126" target="https://www.rfc-editor.org/info/rfc8
126" quoteTitle="true" derivedAnchor="RFC8126">
<front>
<title>Guidelines for Writing an IANA Considerations Section in RFCs
</title>
<author initials="M." surname="Cotton" fullname="M. Cotton">
<organization showOnFrontPage="true"/>
</author>
<author initials="B." surname="Leiba" fullname="B. Leiba">
<organization showOnFrontPage="true"/>
</author>
<author initials="T." surname="Narten" fullname="T. Narten">
<organization showOnFrontPage="true"/>
</author>
<date year="2017" month="June"/>
<abstract>
<t>Many protocols make use of points of extensibility that use con
stants to identify various protocol parameters. To ensure that the values in th
ese fields do not have conflicting uses and to promote interoperability, their a
llocations are often coordinated by a central record keeper. For IETF protocols
, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
<t>To make assignments in a given registry prudently, guidance des
cribing the conditions under which new values should be assigned, as well as whe
n and how modifications to existing values can be made, is needed. This documen
t defines a framework for the documentation of these guidelines by specification
authors, in order to assure that the provided guidance for the IANA Considerati
ons is clear and addresses the various issues that are likely in the operation o
f a registry.</t>
<t>This is the third edition of this document; it obsoletes RFC 52
26.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="26"/>
<seriesInfo name="RFC" value="8126"/>
<seriesInfo name="DOI" value="10.17487/RFC8126"/>
</reference>
</references>
</references>
<section numbered="false" toc="include" removeInRFC="false" pn="section-appe
ndix.a">
<name slugifiedName="name-acknowledgments">Acknowledgments</name>
<t pn="section-appendix.a-1">
The format for the Sub-Data Item was inspired by Rick Taylor's "Data Item
Containers" idea. Containers" idea.
</t> </t>
</section> </section>
<section anchor="authors-addresses" numbered="false" removeInRFC="false" toc
</back> ="include" pn="section-appendix.b">
<name slugifiedName="name-authors-addresses">Authors' Addresses</name>
<author initials="B." surname="Cheng" fullname="Bow-Nan Cheng">
<organization showOnFrontPage="true">MIT Lincoln Laboratory</organizatio
n>
<address>
<postal>
<extaddr>Massachusetts Institute of Technology</extaddr>
<street>244 Wood Street</street>
<city>Lexington</city>
<region>MA</region>
<code>02421-6426</code>
<country>United States of America</country>
</postal>
<email>bcheng@ll.mit.edu</email>
</address>
</author>
<author initials="D." surname="Wiggins" fullname="David Wiggins">
<organization showOnFrontPage="true">MIT Lincoln Laboratory</organizatio
n>
<address>
<postal>
<extaddr>Massachusetts Institute of Technology</extaddr>
<street>244 Wood Street</street>
<city>Lexington</city>
<region>MA</region>
<code>02420-9108</code>
<country>United States of America</country>
</postal>
<email>David.Wiggins@ll.mit.edu</email>
</address>
</author>
<author initials="L." surname="Berger" fullname="Lou Berger" role="editor"
>
<organization showOnFrontPage="true">LabN Consulting, L.L.C.</organizati
on>
<address>
<email>lberger@labn.net</email>
</address>
</author>
</section>
</back>
</rfc> </rfc>
<!-- Local Variables: -->
<!-- fill-column:72 -->
<!-- End: -->
 End of changes. 73 change blocks. 
481 lines changed or deleted 1096 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/