idnits 2.17.1 draft-ietf-manet-dlep-da-credit-extension-11.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 (June 21, 2021) is 1012 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-07 == Outdated reference: A later version (-07) exists of draft-berger-manet-dlep-ether-credit-extension-05 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: December 23, 2021 L. Berger 6 LabN Consulting, L.L.C. 7 June 21, 2021 9 DLEP DiffServ Aware Credit Window Extension 10 draft-ietf-manet-dlep-da-credit-extension-11 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 December 23, 2021. 35 Copyright Notice 37 Copyright (c) 2021 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 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 1.1. Key Words . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Extension Usage and Identification . . . . . . . . . . . . . 3 55 3. Management Considerations . . . . . . . . . . . . . . . . . . 3 56 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 57 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 58 5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 4 59 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 6.1. Normative References . . . . . . . . . . . . . . . . . . 5 61 6.2. Informative References . . . . . . . . . . . . . . . . . 5 62 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 5 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 65 1. Introduction 67 The Dynamic Link Exchange Protocol (DLEP) is defined in [RFC8175]. 68 It provides the exchange of link related control information between 69 DLEP peers. DLEP peers are comprised of a modem and a router. DLEP 70 defines a base set of mechanisms as well as support for possible 71 extensions. This document defines one such extension. 73 The base DLEP specification does not include any flow control 74 capability. There are various flow control techniques theoretically 75 possible with DLEP. This document defines a DLEP extension which 76 provides a DiffServ-based flow control mechanism for traffic sent 77 from a router to a modem. Flow control is provided using one or more 78 logical "Credit Windows", each of which will typically be supported 79 by an associated virtual or physical queue. Traffic sent by a router 80 will use traffic flow classification information provided by the 81 modem to identify which traffic is associated with each credit 82 window. Credit windows may be shared or dedicated on a per flow 83 basis. See [I-D.berger-manet-dlep-ether-credit-extension] for an 84 Ethernet-based version of credit window flow control. 86 This document uses the traffic classification and credit window 87 control mechanisms defined in 88 [I-D.ietf-manet-dlep-traffic-classification] and 89 [I-D.ietf-manet-dlep-credit-flow-control] to provided credit window 90 based flow control based on on DLEP destination and DiffServ 91 [RFC2475] DSCPs (differentiated services codepoints). The defined 92 mechanism allows for credit windows to be shared across traffic sent 93 to multiple DLEP destinations and DSCPs, or used exclusively for 94 traffic sent to a particular destination and/or DSCP. The extension 95 also supports the "wildcard" matching of any DSCP. 97 The extension defined in this document is referred to as "DiffServ 98 Aware Credit Window" or, more simply, the "DA Credit" extension. The 99 reader should be familiar with both the traffic classification and 100 credit window control mechanisms defined in 101 [I-D.ietf-manet-dlep-traffic-classification] and 102 [I-D.ietf-manet-dlep-credit-flow-control]. 104 This document defines a new DLEP Extension Type Value in Section 2 105 which is used to indicate support for the extension. 107 1.1. Key Words 109 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 110 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 111 "OPTIONAL" in this document are to be interpreted as described in BCP 112 14 [RFC2119] [RFC8174] when, and only when, they appear in all 113 capitals, as shown here. 115 2. Extension Usage and Identification 117 The extension defined in this document is composed of the mechanisms 118 and processing defined in 119 [I-D.ietf-manet-dlep-traffic-classification] and 120 [I-D.ietf-manet-dlep-credit-flow-control]. To indicate that the 121 DiffServ Aware Credit Window Extension is to be used, an 122 implementation MUST include the DiffServ Aware Credit Window Type 123 Value in the Extensions Supported Data Item. The Extensions 124 Supported Data Item is sent and processed according to [RFC8175]. 125 Any implementation that indicates use of the DiffServ Aware Credit 126 Window Extension MUST support all Messages, Data Items, the DiffServ 127 Traffic Classification Sub Data Item, and all related processing 128 defined in [I-D.ietf-manet-dlep-traffic-classification] and 129 [I-D.ietf-manet-dlep-credit-flow-control]. 131 The DiffServ Aware Credit Window Extension Type Value is TBA1, see 132 Section 5. 134 3. Management Considerations 136 This section provides several network management guidelines to 137 implementations supporting the DiffServ Aware Credit Window 138 Extension. 140 The use of the extension defined in this document SHOULD be 141 configurable on both modems and routers. 143 Modems SHOULD support the configuration of DSCP to credit window 144 (queue) mapping. 146 Modems MAY support the configuration of the number of credit windows 147 (queues) to advertise to a router. 149 Routers may have limits on the number of queues that they can support 150 and, perhaps, even limits in supported credit window combinations, 151 e.g., if per destination queues can even be supported at all. When 152 modem-provided credit window information exceeds the capabilities of 153 a router, the router MAY use a subset of the provided credit windows. 154 Alternatively, a router MAY reset the session and indicate that the 155 extension is not supported. In either case, the mismatch of 156 capabilities SHOULD be reported to the user via normal network 157 management mechanisms, e.g., user interface or error logging. 159 4. Security Considerations 161 This document defines a DLEP extension that uses base DLEP mechanisms 162 and the credit window control and flow mechanisms defined in 163 [I-D.ietf-manet-dlep-traffic-classification] and 164 [I-D.ietf-manet-dlep-credit-flow-control]. The use of those 165 mechanisms, and the introduction of a new extension, do not 166 inherently introduce any additional vulnerabilities above those 167 documented in [RFC8175]. The approach taken to Security in that 168 document applies equally to the mechanism defined in this document. 170 5. IANA Considerations 172 This document requests one assignment by IANA. All assignments are 173 to registries defined by [RFC8175]. 175 5.1. Extension Type Value 177 This document requests 1 new assignment to the DLEP Extensions 178 Registry named "Extension Type Values" in the range with the 179 "Specification Required" policy. The requested value is as follows: 181 +------+------------------------------+ 182 | Code | Description | 183 +------+------------------------------+ 184 | TBA1 | DiffServ Aware Credit Window | 185 +------+------------------------------+ 187 Table 1: Requested Extension Type Value 189 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", draft- 195 ietf-manet-dlep-credit-flow-control-07 (work in progress), 196 December 2020. 198 [I-D.ietf-manet-dlep-traffic-classification] 199 Cheng, B., Wiggins, D., and L. Berger, "DLEP Traffic 200 Classification Data Item", August 2018. 202 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 203 Requirement Levels", BCP 14, RFC 2119, 204 DOI 10.17487/RFC2119, March 1997, 205 . 207 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 208 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 209 May 2017, . 211 [RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B. 212 Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175, 213 DOI 10.17487/RFC8175, June 2017, 214 . 216 6.2. Informative References 218 [I-D.berger-manet-dlep-ether-credit-extension] 219 Wiggins, D. and L. Berger, "DLEP IEEE 802.1Q Aware Credit 220 Window Extension", draft-berger-manet-dlep-ether-credit- 221 extension-05 (work in progress), December 2020. 223 [RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z., 224 and W. Weiss, "An Architecture for Differentiated 225 Services", RFC 2475, DOI 10.17487/RFC2475, December 1998, 226 . 228 Appendix A. Acknowledgments 230 The sub data item format was inspired by Rick Taylor's "Data Item 231 Containers". He also proposed the separation of credit windows from 232 traffic classification at IETF98. Many useful comments were received 233 from contributors to the MANET working group. 235 Authors' Addresses 236 Bow-Nan Cheng 237 MIT Lincoln Laboratory 238 Massachusetts Institute of Technology 239 244 Wood Street 240 Lexington, MA 02421-6426 242 Email: bcheng@ll.mit.edu 244 David Wiggins 245 MIT Lincoln Laboratory 246 Massachusetts Institute of Technology 247 244 Wood Street 248 Lexington, MA 02421-6426 250 Email: David.Wiggins@ll.mit.edu 252 Lou Berger 253 LabN Consulting, L.L.C. 255 Email: lberger@labn.net