idnits 2.17.1 draft-ietf-manet-dlep-da-credit-extension-13.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (24 February 2022) is 791 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-13) exists of draft-ietf-manet-dlep-credit-flow-control-09 == Outdated reference: A later version (-11) exists of draft-ietf-manet-dlep-traffic-classification-06 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Cheng 3 Internet-Draft D. Wiggins 4 Intended status: Standards Track MIT Lincoln Laboratory 5 Expires: 28 August 2022 L. Berger 6 LabN Consulting, L.L.C. 7 24 February 2022 9 DLEP DiffServ Aware Credit Window Extension 10 draft-ietf-manet-dlep-da-credit-extension-13 12 Abstract 14 This document defines an extension to the Dynamic Link Exchange 15 Protocol (DLEP) that enables a DiffServ aware credit-window scheme 16 for destination-specific and shared flow control. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on 28 August 2022. 35 Copyright Notice 37 Copyright (c) 2022 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 42 license-info) in effect on the date of publication of this document. 43 Please review these documents carefully, as they describe your rights 44 and restrictions with respect to this document. Code Components 45 extracted from this document must include Revised BSD License text as 46 described in Section 4.e of the Trust Legal Provisions and are 47 provided without warranty as described in the Revised BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.1. Key Words . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Extension Usage and Identification . . . . . . . . . . . . . 3 54 3. Management Considerations . . . . . . . . . . . . . . . . . . 3 55 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 56 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 57 5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 4 58 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 60 6.2. Informative References . . . . . . . . . . . . . . . . . 5 61 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 6 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 64 1. Introduction 66 The Dynamic Link Exchange Protocol (DLEP) is defined in [RFC8175]. 67 It provides the exchange of link related control information between 68 DLEP peers. DLEP peers are comprised of a modem and a router. DLEP 69 defines a base set of mechanisms as well as support for possible 70 extensions. This document defines one such extension. 72 The base DLEP specification does not include any flow control 73 capability. There are various flow control techniques theoretically 74 possible with DLEP. This document defines a DLEP extension which 75 provides a DiffServ-based flow control mechanism for traffic sent 76 from a router to a modem. Flow control is provided using one or more 77 logical "Credit Windows", each of which will typically be supported 78 by an associated virtual or physical queue. A router will use 79 traffic flow classification information provided by the modem to 80 identify which traffic is associated with each credit window. Credit 81 windows may be shared or dedicated on a per flow basis. See 82 [I-D.berger-manet-dlep-ether-credit-extension] for an Ethernet-based 83 version of credit window flow control. 85 This document uses the traffic classification and credit window 86 control mechanisms defined in 87 [I-D.ietf-manet-dlep-traffic-classification] and 88 [I-D.ietf-manet-dlep-credit-flow-control] to provide credit window 89 based flow control based on DLEP destinations and DiffServ [RFC2475] 90 DSCPs (differentiated services codepoints). The defined mechanism 91 allows for credit windows to be shared across traffic sent to 92 multiple DLEP destinations and DSCPs, or used exclusively for traffic 93 sent to a particular destination and/or DSCP. The extension also 94 supports the "wildcard" matching of any DSCP. 96 The extension defined in this document is referred to as "DiffServ 97 Aware Credit Window" or, more simply, the "DA Credit" extension. The 98 reader should be familiar with both the traffic classification and 99 credit window control mechanisms defined in 100 [I-D.ietf-manet-dlep-traffic-classification] and 101 [I-D.ietf-manet-dlep-credit-flow-control]. 103 This document defines a new DLEP Extension Type Value in Section 2 104 which is used to indicate support for the extension. 106 1.1. Key Words 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 109 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 110 "OPTIONAL" in this document are to be interpreted as described in BCP 111 14 [RFC2119] [RFC8174] when, and only when, they appear in all 112 capitals, as shown here. 114 2. Extension Usage and Identification 116 The extension defined in this document is composed of the mechanisms 117 and processing defined in 118 [I-D.ietf-manet-dlep-traffic-classification] and 119 [I-D.ietf-manet-dlep-credit-flow-control]. To indicate that the 120 DiffServ Aware Credit Window Extension is to be used, an 121 implementation MUST include the DiffServ Aware Credit Window Type 122 Value in the Extensions Supported Data Item. The Extensions 123 Supported Data Item is sent and processed according to [RFC8175]. 124 Any implementation that indicates use of the DiffServ Aware Credit 125 Window Extension MUST support all Messages, Data Items, the DiffServ 126 Traffic Classification Sub-Data Item, and all related processing 127 defined in [I-D.ietf-manet-dlep-traffic-classification] and 128 [I-D.ietf-manet-dlep-credit-flow-control]. 130 The DiffServ Aware Credit Window Extension Type Value is TBA1, see 131 Section 5. 133 3. Management Considerations 135 This section provides several network management guidelines to 136 implementations supporting the DiffServ Aware Credit Window 137 Extension. 139 The use of the extension defined in this document SHOULD be 140 configurable on both modems and routers. 142 Modems SHOULD support the configuration of DSCP to credit window 143 (queue) mapping. 145 Modems MAY support the configuration of the number of credit windows 146 (queues) to advertise to a router. 148 Routers may have limits on the number of queues that they can support 149 and, perhaps, even limits in supported credit window combinations, 150 e.g., if per destination queues can even be supported at all. When 151 modem-provided credit window information exceeds the capabilities of 152 a router, the router MAY use a subset of the provided credit windows. 153 Alternatively, a router MAY reset the session and indicate that the 154 extension is not supported. In either case, the mismatch of 155 capabilities SHOULD be reported to the user via normal network 156 management mechanisms, e.g., user interface or error logging. 158 4. Security Considerations 160 This document defines a DLEP extension that uses base DLEP mechanisms 161 and the credit window control and flow mechanisms defined in 162 [I-D.ietf-manet-dlep-traffic-classification] and 163 [I-D.ietf-manet-dlep-credit-flow-control]. The use of those 164 mechanisms, and the introduction of a new extension, do not 165 inherently introduce any additional vulnerabilities above those 166 documented in [RFC8175]. The approach taken to Security in that 167 document applies equally to the mechanism defined in this document. 169 5. IANA Considerations 171 This document requests one assignment by IANA. All assignments are 172 to registries defined by [RFC8175]. 174 5.1. Extension Type Value 176 This document requests 1 new assignment to the DLEP Extensions 177 Registry named "Extension Type Values" in the range with the 178 "Specification Required" policy. The requested value is as follows: 180 +======+==============================+ 181 | Code | Description | 182 +======+==============================+ 183 | TBA1 | DiffServ Aware Credit Window | 184 +------+------------------------------+ 186 Table 1: Requested Extension Type Value 188 6. References 190 6.1. Normative References 192 [I-D.ietf-manet-dlep-credit-flow-control] 193 Cheng, B., Wiggins, D., Berger, L., and S. Ratliff, "DLEP 194 Credit-Based Flow Control Messages and Data Items", Work 195 in Progress, Internet-Draft, draft-ietf-manet-dlep-credit- 196 flow-control-09, 26 October 2021, 197 . 200 [I-D.ietf-manet-dlep-traffic-classification] 201 Cheng, B., Wiggins, D., and L. Berger, "DLEP Traffic 202 Classification Data Item", Work in Progress, Internet- 203 Draft, draft-ietf-manet-dlep-traffic-classification-06, 29 204 July 2021, . 207 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 208 Requirement Levels", BCP 14, RFC 2119, 209 DOI 10.17487/RFC2119, March 1997, 210 . 212 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 213 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 214 May 2017, . 216 [RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B. 217 Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175, 218 DOI 10.17487/RFC8175, June 2017, 219 . 221 6.2. Informative References 223 [I-D.berger-manet-dlep-ether-credit-extension] 224 Wiggins, D. and L. Berger, "DLEP IEEE 802.1Q Aware Credit 225 Window Extension", Work in Progress, Internet-Draft, 226 draft-berger-manet-dlep-ether-credit-extension-07, 29 July 227 2021, . 230 [RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z., 231 and W. Weiss, "An Architecture for Differentiated 232 Services", RFC 2475, DOI 10.17487/RFC2475, December 1998, 233 . 235 Appendix A. Acknowledgments 237 The Sub-Data item format was inspired by Rick Taylor's "Data Item 238 Containers". He also proposed the separation of credit windows from 239 traffic classification at IETF98. Many useful comments were received 240 from contributors to the MANET working group, notably Ronald in't 241 Velt. 243 Authors' Addresses 245 Bow-Nan Cheng 246 MIT Lincoln Laboratory 247 Massachusetts Institute of Technology 248 244 Wood Street 249 Lexington 250 Email: bcheng@ll.mit.edu 252 David Wiggins 253 MIT Lincoln Laboratory 254 Massachusetts Institute of Technology 255 244 Wood Street 256 Lexington 257 Email: David.Wiggins@ll.mit.edu 259 Lou Berger 260 LabN Consulting, L.L.C. 261 Email: lberger@labn.net