draft-ietf-manet-dlep-da-credit-extension-11.txt   draft-ietf-manet-dlep-da-credit-extension-12.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: December 23, 2021 L. Berger Expires: 30 January 2022 L. Berger
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
June 21, 2021 29 July 2021
DLEP DiffServ Aware Credit Window Extension DLEP DiffServ Aware Credit Window Extension
draft-ietf-manet-dlep-da-credit-extension-11 draft-ietf-manet-dlep-da-credit-extension-12
Abstract Abstract
This document defines an extension to the Dynamic Link Exchange This document defines an extension to the Dynamic Link Exchange
Protocol (DLEP) that enables a DiffServ aware credit-window scheme Protocol (DLEP) that enables a DiffServ aware credit-window scheme
for destination-specific and shared flow control. for destination-specific and shared flow control.
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
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 December 23, 2021. This Internet-Draft will expire on 30 January 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Simplified BSD License text
include Simplified BSD License text as described in Section 4.e of as described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as 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 . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Key Words . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Extension Usage and Identification . . . . . . . . . . . . . 3 2. Extension Usage and Identification . . . . . . . . . . . . . 3
3. Management Considerations . . . . . . . . . . . . . . . . . . 3 3. Management Considerations . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 4 5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 5 6.1. Normative References . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . 5 6.2. Informative References . . . . . . . . . . . . . . . . . 5
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 5 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
The Dynamic Link Exchange Protocol (DLEP) is defined in [RFC8175]. The Dynamic Link Exchange Protocol (DLEP) is defined in [RFC8175].
It provides the exchange of link related control information between It provides the exchange of link related control information between
DLEP peers. DLEP peers are comprised of a modem and a router. DLEP DLEP peers. DLEP peers are comprised of a modem and a router. DLEP
defines a base set of mechanisms as well as support for possible 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 flow control The base DLEP specification does not include any flow control
capability. There are various flow control techniques theoretically capability. There are various flow control techniques theoretically
possible with DLEP. This document defines a DLEP extension which possible with DLEP. This document defines a DLEP extension which
provides a DiffServ-based flow control mechanism for traffic sent provides a DiffServ-based flow control mechanism for traffic sent
from a router to a modem. Flow control is provided using one or more from a router to a modem. Flow control is provided using one or more
logical "Credit Windows", each of which will typically be supported logical "Credit Windows", each of which will typically be supported
by an associated virtual or physical queue. Traffic sent by a router by an associated virtual or physical queue. A router will use
will use traffic flow classification information provided by the traffic flow classification information provided by the modem to
modem to identify which traffic is associated with each credit identify which traffic is associated with each credit window. Credit
window. Credit windows may be shared or dedicated on a per flow windows may be shared or dedicated on a per flow basis. See
basis. See [I-D.berger-manet-dlep-ether-credit-extension] for an [I-D.berger-manet-dlep-ether-credit-extension] for an Ethernet-based
Ethernet-based version of credit window flow control. version of credit window flow control.
This document uses the traffic classification and credit window This document uses the traffic classification and credit window
control mechanisms defined in control mechanisms defined in
[I-D.ietf-manet-dlep-traffic-classification] and [I-D.ietf-manet-dlep-traffic-classification] and
[I-D.ietf-manet-dlep-credit-flow-control] to provided credit window [I-D.ietf-manet-dlep-credit-flow-control] to provide credit window
based flow control based on on DLEP destination and DiffServ based flow control based on DLEP destinations and DiffServ [RFC2475]
[RFC2475] DSCPs (differentiated services codepoints). The defined DSCPs (differentiated services codepoints). The defined mechanism
mechanism allows for credit windows to be shared across traffic sent allows for credit windows to be shared across traffic sent to
to multiple DLEP destinations and DSCPs, or used exclusively for multiple DLEP destinations and DSCPs, or used exclusively for traffic
traffic sent to a particular destination and/or DSCP. The extension sent to a particular destination and/or DSCP. The extension also
also supports the "wildcard" matching of any DSCP. supports the "wildcard" matching of any DSCP.
The extension defined in this document is referred to as "DiffServ The extension defined in this document is referred to as "DiffServ
Aware Credit Window" or, more simply, the "DA Credit" extension. The Aware Credit Window" or, more simply, the "DA Credit" extension. The
reader should be familiar with both the traffic classification and reader should be familiar with both the traffic classification and
credit window control mechanisms defined in credit window control mechanisms defined in
[I-D.ietf-manet-dlep-traffic-classification] and [I-D.ietf-manet-dlep-traffic-classification] and
[I-D.ietf-manet-dlep-credit-flow-control]. [I-D.ietf-manet-dlep-credit-flow-control].
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 support for the extension. which is used to indicate support for the extension.
skipping to change at page 3, line 35 skipping to change at page 3, line 35
The extension defined in this document is composed of the mechanisms The extension defined in this document is composed of the mechanisms
and processing defined in and processing defined in
[I-D.ietf-manet-dlep-traffic-classification] and [I-D.ietf-manet-dlep-traffic-classification] and
[I-D.ietf-manet-dlep-credit-flow-control]. To indicate that the [I-D.ietf-manet-dlep-credit-flow-control]. To indicate that the
DiffServ Aware Credit Window Extension is to be used, an DiffServ Aware Credit Window Extension is to be used, an
implementation MUST include the DiffServ Aware Credit Window Type implementation MUST include the DiffServ Aware Credit Window Type
Value in the Extensions Supported Data Item. The Extensions Value in the Extensions Supported Data Item. The Extensions
Supported Data Item is sent and processed according to [RFC8175]. Supported Data Item is sent and processed according to [RFC8175].
Any implementation that indicates use of the DiffServ Aware Credit Any implementation that indicates use of the DiffServ Aware Credit
Window Extension MUST support all Messages, Data Items, the DiffServ Window Extension MUST support all Messages, Data Items, the DiffServ
Traffic Classification Sub Data Item, and all related processing Traffic Classification Sub-Data Item, and all related processing
defined in [I-D.ietf-manet-dlep-traffic-classification] and defined in [I-D.ietf-manet-dlep-traffic-classification] and
[I-D.ietf-manet-dlep-credit-flow-control]. [I-D.ietf-manet-dlep-credit-flow-control].
The DiffServ Aware Credit Window Extension Type Value is TBA1, see The DiffServ Aware Credit Window Extension Type Value is TBA1, see
Section 5. Section 5.
3. Management Considerations 3. Management Considerations
This section provides several network management guidelines to This section provides several network management guidelines to
implementations supporting the DiffServ Aware Credit Window implementations supporting the DiffServ Aware Credit Window
skipping to change at page 4, line 40 skipping to change at page 4, line 40
This document requests one assignment by IANA. All assignments are This document requests one assignment by IANA. All assignments are
to registries defined by [RFC8175]. 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 Type 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 | DiffServ Aware Credit Window | | TBA1 | DiffServ Aware Credit Window |
+------+------------------------------+ +------+------------------------------+
Table 1: Requested Extension Type Value Table 1: Requested Extension Type Value
6. References 6. References
6.1. Normative References 6.1. Normative References
[I-D.ietf-manet-dlep-credit-flow-control] [I-D.ietf-manet-dlep-credit-flow-control]
Cheng, B., Wiggins, D., Berger, L., and S. Ratliff, "DLEP Cheng, B., Wiggins, D., Berger, L., and S. Ratliff, "DLEP
Credit-Based Flow Control Messages and Data Items", draft- Credit-Based Flow Control Messages and Data Items", Work
ietf-manet-dlep-credit-flow-control-07 (work in progress), in Progress, Internet-Draft, draft-ietf-manet-dlep-credit-
December 2020. flow-control-08, 21 June 2021,
<https://www.ietf.org/archive/id/draft-ietf-manet-dlep-
credit-flow-control-08.txt>.
[I-D.ietf-manet-dlep-traffic-classification] [I-D.ietf-manet-dlep-traffic-classification]
Cheng, B., Wiggins, D., and L. Berger, "DLEP Traffic Cheng, B., Wiggins, D., and L. Berger, "DLEP Traffic
Classification Data Item", August 2018. Classification Data Item", Work in Progress, Internet-
Draft, draft-ietf-manet-dlep-traffic-classification-05, 21
June 2021, <https://www.ietf.org/archive/id/draft-ietf-
manet-dlep-traffic-classification-05.txt>.
[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,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[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.berger-manet-dlep-ether-credit-extension] [I-D.berger-manet-dlep-ether-credit-extension]
Wiggins, D. and L. Berger, "DLEP IEEE 802.1Q Aware Credit Wiggins, D. and L. Berger, "DLEP IEEE 802.1Q Aware Credit
Window Extension", draft-berger-manet-dlep-ether-credit- Window Extension", Work in Progress, Internet-Draft,
extension-05 (work in progress), December 2020. draft-berger-manet-dlep-ether-credit-extension-06, 21 June
2021, <https://www.ietf.org/archive/id/draft-berger-manet-
dlep-ether-credit-extension-06.txt>.
[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,
<https://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". He also proposed the separation of credit windows from Containers". He also proposed the separation of credit windows from
traffic classification at IETF98. Many useful comments were received traffic classification at IETF98. Many useful comments were received
from contributors to the MANET working group. from contributors to the MANET working group, notably Ronald in't
Velt.
Authors' Addresses Authors' Addresses
Bow-Nan Cheng Bow-Nan Cheng
MIT Lincoln Laboratory MIT Lincoln Laboratory
Massachusetts Institute of Technology Massachusetts Institute of Technology
244 Wood Street 244 Wood Street
Lexington, MA 02421-6426 Lexington
Email: bcheng@ll.mit.edu Email: bcheng@ll.mit.edu
David Wiggins David Wiggins
MIT Lincoln Laboratory MIT Lincoln Laboratory
Massachusetts Institute of Technology Massachusetts Institute of Technology
244 Wood Street 244 Wood Street
Lexington, MA 02421-6426 Lexington
Email: David.Wiggins@ll.mit.edu Email: David.Wiggins@ll.mit.edu
Lou Berger Lou Berger
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
Email: lberger@labn.net Email: lberger@labn.net
 End of changes. 21 change blocks. 
41 lines changed or deleted 50 lines changed or added

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