< draft-ietf-manet-dlep-pause-extension-05.txt   draft-ietf-manet-dlep-pause-extension-06.txt >
Network Working Group B. Cheng Network Working Group B. Cheng
Internet-Draft D. Wiggins Internet-Draft D. Wiggins
Intended status: Standards Track MIT Lincoln Laboratory Intended status: Standards Track MIT Lincoln Laboratory
Expires: September 12, 2019 L. Berger, Ed. Expires: October 5, 2019 L. Berger, Ed.
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
March 11, 2019 April 3, 2019
DLEP Control Plane Based Pause Extension DLEP Control Plane Based Pause Extension
draft-ietf-manet-dlep-pause-extension-05 draft-ietf-manet-dlep-pause-extension-06
Abstract Abstract
This document defines an extension to the DLEP protocol that enables This document defines an extension to the Dynamic Link Exchange
a modem to use DLEP messages to pause and resume data traffic coming Protocol (DLEP) that enables a modem to use DLEP messages to pause
from its peer router. and resume data traffic coming from its peer router.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 12, 2019. This Internet-Draft will expire on October 5, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 13 skipping to change at page 2, line 13
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Key Words . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Key Words . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Extension Usage and Identification . . . . . . . . . . . . . 3 2. Extension Usage and Identification . . . . . . . . . . . . . 3
3. Extension Data Items . . . . . . . . . . . . . . . . . . . . 3 3. Extension Data Items . . . . . . . . . . . . . . . . . . . . 3
3.1. Queue Parameters . . . . . . . . . . . . . . . . . . . . 3 3.1. Queue Parameters . . . . . . . . . . . . . . . . . . . . 3
3.1.1. Queue Parameter Sub Data Item . . . . . . . . . . . . 5 3.1.1. Queue Parameter Sub Data Item . . . . . . . . . . . . 5
3.2. Pause . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.2. Pause . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. Restart . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.3. Restart . . . . . . . . . . . . . . . . . . . . . . . . . 8
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 9 5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 9
5.2. Data Item Values . . . . . . . . . . . . . . . . . . . . 9 5.2. Data Item Values . . . . . . . . . . . . . . . . . . . . 9
5.3. Queue Parameters Sub Data Item Values . . . . . . . . . . 10 5.3. Queue Parameters Sub Data Item Values . . . . . . . . . . 10
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1. Normative References . . . . . . . . . . . . . . . . . . 10 6.1. Normative References . . . . . . . . . . . . . . . . . . 10
6.2. Informative References . . . . . . . . . . . . . . . . . 11 6.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 11 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 11
skipping to change at page 2, line 41 skipping to change at page 2, line 41
defines a base set of mechanisms as well as support for possible defines a base set of mechanisms as well as support for possible
extensions. This document defines one such extension. extensions. This document defines one such extension.
The base DLEP specification does not include any data plane flow The base DLEP specification does not include any data plane flow
control capability. Various flow control methods are possible, e.g., control capability. Various flow control methods are possible, e.g.,
see [I-D.ietf-manet-dlep-da-credit-extension]. The extension defined see [I-D.ietf-manet-dlep-da-credit-extension]. The extension defined
in this document supports flow control of data traffic based on in this document supports flow control of data traffic based on
explicit messages sent via DLEP by a modem to indicate when a router explicit messages sent via DLEP by a modem to indicate when a router
should hold off sending traffic, and when it should resume. The should hold off sending traffic, and when it should resume. The
extension also optionally supports DSCP (differentiated services extension also optionally supports DSCP (differentiated services
codepoint) aware, see [RFC2475], flow control. The extension defined codepoint) aware flow control. For general background on
in this document is referred to as "Control Plane Based Pause". Note Differentiated Services see [RFC2475]. The extension defined in this
that this mechanism only controls traffic that is to be transmitted document is referred to as "Control Plane Based Pause". Note that
on the modem's attached data channel and not to DLEP control messages this mechanism only applies to traffic that is to be transmitted on
the modem's attached data channel and not to DLEP control messages
themselves. themselves.
This document defines a new DLEP Extension Type Value in Section 2 This document defines a new DLEP Extension Type Value in Section 2
which is used to indicate the use of the extension, and three new which is used to indicate the use of the extension, and three new
DLEP Data Items in Section 3. DLEP Data Items in Section 3.
1.1. Key Words 1.1. Key Words
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. Extension Usage and Identification 2. Extension Usage and Identification
The use of the Control Plane Based Pause Extension SHOULD be The use of the Control Plane Based Pause Extension SHOULD be
configurable. To indicate that the Control Plane Based Pause configurable. To indicate that the implementation supports use of
Extension is to be used, an implementation MUST include the Control the Control Plane Based Pause Extension, an implementation MUST
Plane Based Pause Extension Type Value in the Extensions Supported include the Control Plane Based Pause Extension Type Value in the
Data Item. The Extensions Supported Data Item is sent and processed Extensions Supported Data Item. The Extensions Supported Data Item
according to [RFC8175]. is sent and processed according to [RFC8175].
The Control Plane Based Pause Extension Type Value is TBA1, see The Control Plane Based Pause Extension Type Value is TBA1, see
Section 5. Section 5.
3. Extension Data Items 3. Extension Data Items
Three data items are defined by this extension. The Queue Parameters Three data items are defined by this extension. The Queue Parameters
Data Item is used by a modem to provide information on the DSCPs it Data Item is used by a modem to provide information about the DSCPs
uses in forwarding. The Pause Data Item is used by a modem to it 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.
3.1. Queue Parameters 3.1. Queue Parameters
The Queue Parameters Data Item is used by a modem to indicate DSCP The Queue Parameters Data Item is used by a modem to indicate DSCP
values that may be independently paused. This data item MUST be values that may be independently paused. This data item MUST be
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 MAY be
sent by a modem by including the data item in Session Update sent by a modem by including the data item in Session Update
Messages. Messages.
The Queue Parameters Data Item identifies DSCPs based on groups of The Queue Parameters Data Item groups DSCPs into logical queues, each
logical queues, each of which is referred to via a "Queue Index". of which is identified by a "Queue Index". The number of logical
The number of logical queues, or queue indexes, is variable as is the queues, or queue indexes, is variable as is the number of DSCPs
number of DSCPs associated with each queue. A queue size (in bytes) associated with each queue. A queue size (in bytes) is provided for
is provided for informational purposes. Queue Indexes are numbered informational purposes. Queue Indexes are numbered sequentially from
sequentially from zero, where queue index zero is a special case zero, where queue index zero is a special case covering DSCPs which
covering DSCPs which are not otherwise associated with Queue Index. are not otherwise associated with Queue Index.
An implementation that does not support DSCPs would indicate 1 queue An implementation that does not support DSCPs would indicate 1 queue
with 0 DSCPs, and the number of bytes that may be in its associated with 0 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.
The format of the Queue Parameters Data Item is: The format of the Queue Parameters Data Item is:
0 1 2 3 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 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Queue Size Q0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Queue Parameter Sub Data Item 1 | | Queue Parameter Sub Data Item 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: ... : : ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Queue Parameter Sub Data Item n | | Queue Parameter Sub Data Item n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBA2 Data Item Type: TBA2
Length: Variable Length: Variable
skipping to change at page 4, line 49 skipping to change at page 4, line 47
at least one (1), and is equal to one greater than the number of at least one (1), and is equal to one greater than the number of
included Queue Parameter Sub Data Items. included Queue Parameter Sub Data Items.
Scale: Scale:
An 4-bit unsigned integer indicating the scale used in the Queue An 4-bit unsigned integer indicating the scale used in the Queue
Size fields. The valid values are: Size fields. The valid values are:
Value Scale Value Scale
------------ ------------
0 B - Bytes (Octets) 0 B - Bytes (Octets)
1 KB - Kilobytes (B/1024) 1 KiB - Kilobytes (1024 B)
2 MB - Megabytes (KB/1024) 2 MiB - Megabytes (1024 KiB)
3 GB - Gigabytes (MB/1024) 3 GiB - Gigabytes (1024 MiB)
Reserved: Reserved:
MUST be set to zero by the sender (a modem) and ignored by the MUST be set to zero by the sender (a modem) and ignored by the
receiver (a router). receiver (a router).
Queue Size Q0:
A 24-bit unsigned integer representing the size, in the octet
scale indicated by the Scale field, of queue index zero.
3.1.1. Queue Parameter Sub Data Item 3.1.1. Queue Parameter Sub Data Item
Queue Parameter Sub Data Items are an unordered list composed of sub Queue Parameter Sub Data Items are an unordered list composed of sub
data items with a common format. The first sub data item is assigned data items with a common format. The format of the Queue Parameter
a Queue Index value of 1, and subsequent data items are numbered Sub Data Item is patterned after the standard DLEP data item format,
incrementally. The format of the Queue Parameter Sub Data Item is see [RFC8175] Section 11.3. Any errors or inconsistencies
patterned after the standard DLEP data item format, see [RFC8175] encountered in parsing Sub Data Items are handled in the same fashion
Section 11.3. Any errors or inconsistencies encountered in parsing as any other Data Item parsing error encountered in DLEP.
Sub Data Items are handled in the same fashion as any other Data Item
parsing error encountered in DLEP.
The format of the Queue Parameter Sub Data Item is: The format of the Queue Parameter Sub Data Item is:
0 1 2 3 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 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... | | Value... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 21 skipping to change at page 6, line 12
Length is the number of octets in the sub data item, excluding the Length is the number of octets in the sub data item, excluding the
Type and Length fields. Type and Length fields.
Queue Index: Queue Index:
An 8-bit field indicating the queue index of the queue parameter An 8-bit field indicating the queue index of the queue parameter
represented in the sub data item. Only the first instance of a represented in the sub data item. Only the first instance of a
particular Queue Index value is meaningful. Subsequent sub data particular Queue Index value is meaningful. Subsequent sub data
items containing the same Queue Index values, if present, MAY be items containing the same Queue Index values, if present, MAY be
logged via a management interface and MUST otherwise be ignored. logged via a management interface and MUST otherwise be ignored.
Note that the value 255 is reserved and MUST NOT be used in this
field.
Queue Size Qn: Queue Size Qn:
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 supporting
traffic with the DSCPs associated with the queue index. traffic with the DSCPs associated with the queue index.
Num DSCPs Qn: Num DSCPs Qn:
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). This field MUST contain a value of at least one (1).
DS Field Qn: DS Field Qn:
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
position in the sequence identifies the associated queue index. of DS Fields present MUST equal the sum of all Num DSCPs field
The number of DS Fields present MUST equal the sum of all Num values.
DSCPs field values.
The DS Field structure is the same as [RFC2474]. The DS Field structure is the same as [RFC2474].
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+
| DSCP | CU | | DSCP | CU |
+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+
DSCP: differentiated services codepoint DSCP: differentiated services codepoint
CU: currently unused, MUST be zero CU: currently unused, MUST be zero
3.2. Pause 3.2. Pause
The Pause Data Item is used by a modem to indicate to its peer that The Pause Data Item is used by a modem to indicate to its peer that
traffic is to be suppressed. An example of when a modem might send traffic is to be suppressed. The motivating use case is for this
this data item is when an internal queue length exceeds a particular data item is when a modem's internal queue length exceeds a
threshold. particular threshold. Other use cases are possible, e.g., when there
a non queue related congestion points within a modem, but such are
not explicitly described in this document.
A modem can indicate that traffic is to be suppressed on a device 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 wide or destination-specific basis. An example of when a modem might
use device wide indications is when output queues are shared across use device wide indications is when output queues are shared across
all destinations, and destination specific might be used when per all destinations, and destination specific might be used when per
destination queuing is used. To indicate that suppression applies to 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 MUST send the Pause Data Item in a Session
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 MUST send the Pause Data Item in a Destination
Update Message. Update Message.
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 Section 3.1, which in turn indicates a set of Queue Index defined by Section 3.1, which in turn indicates a set of
traffic identified by DSCPs. The special value of 255 is used to traffic identified by DSCPs. The special value of 255 is used to
indicate that all traffic is to be suppressed. indicate that all traffic is to be suppressed.
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 Item that may be sent by a modem, a modem SHOULD include
multiple queue indexes in the same message when possible. multiple queue indexes in the same message when possible.
A router which receives the Pause Data Item MUST cease sending the A router which receives the Pause Data Item MUST cease sending the
identified traffic to the modem. This may of course translate into identified traffic to the modem. This may of course translate into
the router's queues exceeding their own thresholds. If a received the router's queues exceeding their own thresholds. If a received
Pause Data Item contains a Queue Index value other than 0, 255, or a Pause Data Item contains a Queue Index value other than 255, or a
queue index established by a Session Initialization or Session Update queue index established by a Session Initialization or Session Update
Message, the router MUST terminate the session with a Status Data Message, the router MUST terminate the session with a Status Data
Item indicating Invalid Data. Item indicating Invalid Data.
The format of the Pause Data Item is: The format of the Pause Data Item is:
0 1 2 3 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 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 |
skipping to change at page 8, line 15 skipping to change at page 8, line 8
Per [RFC8175] Length is the number of octets in the data item, Per [RFC8175] Length is the number of octets in the data item,
excluding the Type and Length fields. It will equal the number of excluding the Type and Length fields. It will equal the number of
Queue Index fields carried in the data item. Queue Index fields carried in the data item.
Queue Index: Queue Index:
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 all traffic is to be suppressed to the modem, when the data item
is carried in a Session Update Message, or a destination, when the is carried in a Session Update Message, or is to be suppressed to
data item is carried in Destination Update Message. a destination, when the data item is carried in Destination Update
Message.
3.3. Restart 3.3. Restart
The Restart Data Item is used by a modem to indicate to its peer that The Restart Data Item is used by a modem to indicate to its peer that
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.
The sending of this data item parallels the Pause Data Item, see the The sending of this data item parallels the Pause Data Item, see the
previous section, and follows the same rules. This includes that to previous section, and follows the same rules. As above, to indicate
indicate that transmission can resume to all destinations, a modem that transmission can resume to all destinations, a modem MUST send
MUST send the Restart Data Item in a Session Update Message. It also the Restart Data Item in a Session Update Message. It also includes
includes that to indicate that transmission can resume to a that to indicate that transmission can resume to a particular
particular destination a modem MUST send the Pause Restart Item in a destination a modem MUST send the Pause Restart Item in a Destination
Destination Update Message. Finally, the same rules apply to queue Update Message. Finally, queue indexes are interpreted in the same
indexes. way as in the Pause Data Item..
A router which receives the Restart Data Item SHOULD resume A router which receives the Restart Data Item SHOULD resume
transmission of the identified traffic to the modem. transmission of the identified traffic to the modem.
The format of the Restart Data Item matches the Pause Data Item and The format of the Restart Data Item matches the Pause Data Item and
is: is:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 9, line 4 skipping to change at page 8, line 45
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 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 | : ... | Queue Index |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBA4 Data Item Type: TBA4
Length: See Section 3.2. Length: See Section 3.2.
Queue Index: See Section 3.2. Queue Index: See Section 3.2.
4. Security Considerations 4. Security Considerations
The extension introduces a new mechanism for flow control between a The extension introduces a new mechanism for flow control between a
router and modem using the DLEP protocol. The extension does not router and modem using DLEP. The extension does not inherently
inherently introduce any additional threats above those documented in introduce any additional vulnerabilities above those documented in
[RFC8175]. The approach taken to Security in that document applies [RFC8175]. The approach taken to Security in that document applies
equally when running the extension defined in this document. equally when running the extension defined in this document.
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, but this is not a modem to suppress transmission by the router, but this is not a
substantively different threat by such a compromised modem simply substantively different attack by such a compromised modem simply
dropping all traffic destined to, or sent by a router. [RFC8175] dropping all traffic destined to, or sent by a router. [RFC8175]
defines the use of TLS to protect against the impersonating attacker. defines the use of TLS to protect against the impersonating attacker.
5. IANA Considerations 5. IANA Considerations
This document requests the assignment of 4 values by IANA. All This document requests the assignment of 4 values by IANA. All
assignments are to registries defined by [RFC8175]. assignments are to registries defined by [RFC8175].
5.1. Extension Type Value 5.1. Extension Type Value
skipping to change at page 11, line 15 skipping to change at page 11, line 15
[RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B. [RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B.
Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175, Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175,
DOI 10.17487/RFC8175, June 2017, DOI 10.17487/RFC8175, June 2017,
<https://www.rfc-editor.org/info/rfc8175>. <https://www.rfc-editor.org/info/rfc8175>.
6.2. Informative References 6.2. Informative References
[I-D.ietf-manet-dlep-da-credit-extension] [I-D.ietf-manet-dlep-da-credit-extension]
Cheng, B., Wiggins, D., and L. Berger, "DLEP DiffServ Cheng, B., Wiggins, D., and L. Berger, "DLEP DiffServ
Aware Credit Window Extension", draft-ietf-manet-dlep-da- Aware Credit Window Extension", draft-ietf-manet-dlep-da-
credit-extension-06 (work in progress), August 2018. credit-extension-07 (work in progress), March 2019.
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
"Definition of the Differentiated Services Field (DS "Definition of the Differentiated Services Field (DS
Field) in the IPv4 and IPv6 Headers", RFC 2474, Field) in the IPv4 and IPv6 Headers", RFC 2474,
DOI 10.17487/RFC2474, December 1998, DOI 10.17487/RFC2474, December 1998,
<https://www.rfc-editor.org/info/rfc2474>. <https://www.rfc-editor.org/info/rfc2474>.
[RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z., [RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z.,
and W. Weiss, "An Architecture for Differentiated and W. Weiss, "An Architecture for Differentiated
Services", RFC 2475, DOI 10.17487/RFC2475, December 1998, Services", RFC 2475, DOI 10.17487/RFC2475, December 1998,
 End of changes. 25 change blocks. 
67 lines changed or deleted 64 lines changed or added

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