draft-ietf-manet-dlep-pause-extension-01.txt   draft-ietf-manet-dlep-pause-extension-02.txt 
Network Working Group B. Cheng Network Working Group B. Cheng
Internet-Draft D. Wiggins Internet-Draft D. Wiggins
Intended status: Standards Track Lincoln Laboratory Intended status: Standards Track Lincoln Laboratory
Expires: January 4, 2018 L. Berger, Ed. Expires: May 3, 2018 L. Berger, Ed.
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
July 3, 2017 October 30, 2017
DLEP Control Plane Based Pause Extension DLEP Control Plane Based Pause Extension
draft-ietf-manet-dlep-pause-extension-01 draft-ietf-manet-dlep-pause-extension-02
Abstract Abstract
This document defines an extension to the DLEP protocol that enables This document defines an extension to the DLEP protocol that enables
a simple control plane based flow control mechanism. a modem to use DLEP messages to pause 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 http://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 January 4, 2018. This Internet-Draft will expire on May 3, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
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 . . . . . . . . . . . . . . . . . . . . . . . . 2 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. Pause . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. Restart . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.3. Restart . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 8 5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 9
5.2. Data Item Values . . . . . . . . . . . . . . . . . . . . 9 5.2. Data Item Values . . . . . . . . . . . . . . . . . . . . 9
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.1. Normative References . . . . . . . . . . . . . . . . . . 9 6.1. Normative References . . . . . . . . . . . . . . . . . . 9
6.2. Informative References . . . . . . . . . . . . . . . . . 9 6.2. Informative References . . . . . . . . . . . . . . . . . 10
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 10 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
The Dynamic Link Event Protocol (DLEP) is defined in The Dynamic Link Event Protocol (DLEP) is defined in [RFC8175]. It
[I-D.ietf-manet-dlep]. It provides the exchange of link related provides the exchange of link related control information between
control information between DLEP peers. DLEP peers are comprised of DLEP peers. DLEP peers are comprised of a modem and a router. DLEP
a modem and a router. DLEP defines a base set of mechanisms as well defines a base set of mechanisms as well as support for possible
as support for possible extensions. This document defines one such extensions. This document defines one such extension.
extension.
The base DLEP specification does not include any flow control The base DLEP specification does not include any data plane flow
capability. There are various flow control possible, e.g., see control capability. Various flow control methods are possible, e.g.,
[I-D.ietf-manet-credit-window]. The extension defined in this see [I-D.ietf-manet-credit-window]. The extension defined in this
document supports flow control based on explicit messages sent via document supports flow control of data traffic based on explicit
DLEP by a modem to indicate when a router should hold off sending messages sent via DLEP by a modem to indicate when a router should
traffic, and when it should resume. The extension also optionally hold off sending traffic, and when it should resume. The extension
supports DSCP (differentiated services codepoint) aware, see also optionally supports DSCP (differentiated services codepoint)
[RFC2475], flow control. The extension defined in this document is aware, see [RFC2475], flow control. The extension defined in this
referred to as "Control Plane Pause". document is referred to as "Control Plane Based Pause". Note that
this mechanism only controls traffic that is to be transmitted on the
modem's attached data channel and not to DLEP control messages
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, RFC 2119 [RFC2119]. 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
2. Extension Usage and Identification 2. Extension Usage and Identification
The use of the Control Plane Pause Extension SHOULD be configurable. The use of the Control Plane Based Pause Extension SHOULD be
To indicate that the Control Plane Pause Extension is to be used, an configurable. To indicate that the Control Plane Based Pause
implementation MUST include the Control Plane Pause Extension Type Extension is to be used, an implementation MUST include the Control
Value in the Extensions Supported Data Item. The Extensions Plane Based Pause Extension Type Value in the Extensions Supported
Supported Data Item is sent and processed according to Data Item. The Extensions Supported Data Item is sent and processed
[I-D.ietf-manet-dlep]. according to [RFC8175].
The Control Plane Pause Extension Type Value is TBA1, see Section 5. The Control Plane Based Pause Extension Type Value is TBA1, see
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 on 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.
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 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 identifies DSCPs based on groups of
logical queues, each of which is referred to via a "Queue Index". logical queues, each of which is referred to via a "Queue Index".
The number of logical queues, or queue indexes, is variable as is the The number of logical queues, or queue indexes, 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 Indexes are numbered
sequentially from zero, where queue index zero is a special case sequentially from zero, where queue index zero is a special case
skipping to change at page 4, line 25 skipping to change at page 4, line 32
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: ... : : ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Queue Parameter Sub Data Item n | | Queue Parameter Sub Data Item n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBA2 Data Item Type: TBA2
Length: Variable Length: Variable
Per [I-D.ietf-manet-dlep] Length is the number of octets in the Per [RFC8175] Length is the number of octets in the data item,
data item, excluding the Type and Length fields. excluding the Type and Length fields.
Num Queues: Num Queues:
An 8-bit unsigned integer indicating the number of queues An 8-bit unsigned integer indicating the number of queues
represented in the data item. This field MUST contain a value of represented in the data item. This field MUST contain a value of
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 Item. 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 KB - Kilobytes (B/1024)
skipping to change at page 5, line 10 skipping to change at page 5, line 17
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: Queue Size Q0:
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 queue index zero. 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 ordered list composed of the Queue Parameter Sub Data Items are an ordered list composed of sub
identical format sub data item. The first sub data item is assigned data items with a common format. The first sub data item is assigned
a Queue Index value of 1, and subsequent data item are numbered a Queue Index value of 1, and subsequent data items are numbered
incrementally. The format of the Queue Parameter Sub Data Item is incrementally. The format of the Queue Parameter Sub Data Item is
patterned after the standard DLEP data item format, see patterned after the standard DLEP data item format, see [RFC8175]
[I-D.ietf-manet-dlep] Section 11.3. Any errors or inconsistencies Section 11.3. Any errors or inconsistencies encountered in parsing
encountered in parsing Sub Data Items are handled in the same fashion Sub Data Items are handled in the same fashion as any other Data Item
as any other Data Item parsing error encountered in DLEP. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Must be one (1) | Length | | Must be one (1) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value... : | Value... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 43 skipping to change at page 5, line 50
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Num DSCPs Qn | Queue Size Qn | | Num DSCPs Qn | Queue Size Qn |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DS Field Qn | DS Field Qn | ... : | DS Field Qn | DS Field Qn | ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: ... | DS Field Qn | : ... | DS Field Qn |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: Variable Length: Variable
Per [I-D.ietf-manet-dlep] Length is the number of octets in the Copying [RFC8175], Length is the number of octets in the sub data
data item, excluding the Type and Length fields. item, excluding the Type and Length fields.
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).
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
skipping to change at page 7, line 7 skipping to change at page 7, line 13
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. 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
queue index established by a Session Initialization or Session Update
Message, the router MUST terminate the session with a Status 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Queue Index | ... : | Queue Index | ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: ... | Queue Index | : ... | Queue Index |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBA3 Data Item Type: TBA3
Length: Variable Length: Variable
Per [I-D.ietf-manet-dlep] Length is the number of octets in the Per [RFC8175] Length is the number of octets in the data item,
data item, excluding the Type and Length fields. It will equal excluding the Type and Length fields. It will equal the number of
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 a destination, when the
data item is carried in Destination Update Message. data item is carried in Destination Update Message.
3.3. Restart 3.3. Restart
skipping to change at page 8, line 32 skipping to change at page 8, line 43
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 the DLEP protocol. The extension does not
inherently introduce any additional threats above those documented in inherently introduce any additional threats above those documented in
[I-D.ietf-manet-dlep]. The approach taken to Security in that [RFC8175]. The approach taken to Security in that document applies
document applies equally when running the extension defined in this equally when running the extension defined in this document.
document.
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 [I-D.ietf-manet-dlep]. assignments are to registries defined by [RFC8175].
5.1. Extension Type Value 5.1. Extension Type Value
This document requests 1 new assignment to the DLEP Extensions This document requests 1 new assignment to the DLEP Extensions
Registry named "Extension Tyoe Values" in the range with the Registry named "Extension Type Values" in the range with the
"Specification Required" policy. The requested value is as follows: "Specification Required" policy. The requested value is as follows:
+------+---------------------+ +------+---------------------------+
| Code | Description | | Code | Description |
+------+---------------------+ +------+---------------------------+
| TBA1 | Control Plane Pause | | TBA1 | Control Plane Based Pause |
+------+---------------------+ +------+---------------------------+
Table 1: Requested Extension Type Value Table 1: Requested Extension Type Value
5.2. Data Item Values 5.2. Data Item Values
This document requests 3 new assignments to the DLEP Data Item This document requests 3 new assignments to the DLEP Data Item
Registry named "Data Item Values" in the range with the Registry named "Data Item Values" in the range with the
"Specification Required" policy. The requested values are as "Specification Required" policy. The requested values are as
follows: follows:
skipping to change at page 9, line 36 skipping to change at page 9, line 42
| | | | | |
| TBA4 | Restart | | TBA4 | Restart |
+-----------+------------------+ +-----------+------------------+
Table 2: Requested Data Item Values Table 2: Requested Data Item Values
6. References 6. References
6.1. Normative References 6.1. Normative References
[I-D.ietf-manet-dlep]
Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B.
Berry, "Dynamic Link Exchange Protocol (DLEP)", draft-
ietf-manet-dlep-29 (work in progress), March 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B.
Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175,
DOI 10.17487/RFC8175, June 2017,
<https://www.rfc-editor.org/info/rfc8175>.
6.2. Informative References 6.2. Informative References
[I-D.ietf-manet-credit-window] [I-D.ietf-manet-credit-window]
Ratliff, S., "Credit Windowing extension for DLEP", draft- Ratliff, S., "Credit Windowing extension for DLEP", draft-
ietf-manet-credit-window-07 (work in progress), November ietf-manet-credit-window-07 (work in progress), November
2016. 2016.
[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,
<http://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,
<http://www.rfc-editor.org/info/rfc2475>. <https://www.rfc-editor.org/info/rfc2475>.
Appendix A. Acknowledgments Appendix A. Acknowledgments
The sub data item format was inspired by Rick Taylor's "Data Item The sub data item format was inspired by Rick Taylor's "Data Item
Containers". Containers".
Authors' Addresses Authors' Addresses
Bow-Nan Cheng Bow-Nan Cheng
Lincoln Laboratory Lincoln Laboratory
Massachusetts Institute of Technology Massachusetts Institute of Technology
244 Wood Street 244 Wood Street
Lexington, MA 02420-9108 Lexington, MA 02421-6426
Email: bcheng@ll.mit.edu Email: bcheng@ll.mit.edu
David Wiggins David Wiggins
Lincoln Laboratory Lincoln Laboratory
Massachusetts Institute of Technology Massachusetts Institute of Technology
244 Wood Street 244 Wood Street
Lexington, MA 02420-9108 Lexington, MA 02420-9108
Email: David.Wiggins@ll.mit.edu Email: David.Wiggins@ll.mit.edu
 End of changes. 32 change blocks. 
69 lines changed or deleted 81 lines changed or added

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