idnits 2.17.1 draft-ietf-manet-dlep-ether-credit-extension-01.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 764 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 == Outdated reference: A later version (-16) exists of draft-ietf-manet-dlep-da-credit-extension-12 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group D. Wiggins 3 Internet-Draft MIT Lincoln Laboratory 4 Intended status: Standards Track L. Berger 5 Expires: 28 August 2022 LabN Consulting, L.L.C. 6 24 February 2022 8 DLEP IEEE 802.1Q Aware Credit Window Extension 9 draft-ietf-manet-dlep-ether-credit-extension-01 11 Abstract 13 This document defines an extension to the Dynamic Link Exchange 14 Protocol (DLEP) that enables a Ethernet IEEE 802.1Q aware credit- 15 window scheme for destination-specific and shared flow control. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on 28 August 2022. 34 Copyright Notice 36 Copyright (c) 2022 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 41 license-info) in effect on the date of publication of this document. 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. Code Components 44 extracted from this document must include Revised BSD License text as 45 described in Section 4.e of the Trust Legal Provisions and are 46 provided without warranty as described in the Revised BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 1.1. Key Words . . . . . . . . . . . . . . . . . . . . . . . . 3 52 2. Extension Usage and Identification . . . . . . . . . . . . . 3 53 3. Management Considerations . . . . . . . . . . . . . . . . . . 4 54 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 55 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 56 5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 5 57 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 58 6.1. Normative References . . . . . . . . . . . . . . . . . . 5 59 6.2. Informative References . . . . . . . . . . . . . . . . . 6 60 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 6 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 63 1. Introduction 65 The Dynamic Link Exchange Protocol (DLEP) is defined in [RFC8175]. 66 It provides the exchange of link related control information between 67 DLEP peers. DLEP peers are comprised of a modem and a router. DLEP 68 defines a base set of mechanisms as well as support for possible 69 extensions. This document defines one such extension. 71 The base DLEP specification does not include any flow control 72 capability. There are various flow control techniques theoretically 73 possible with DLEP. This document defines a DLEP extension which 74 provides an Ethernet-based flow control mechanism for traffic sent 75 from a router to a modem. Flow control is provided using one or more 76 logical "Credit Windows", each of which will typically be supported 77 by an associated virtual or physical queue. A router will use 78 traffic flow classification information provided by the modem to 79 identify which traffic is associated with each credit window. Credit 80 windows may be shared or dedicated on a per flow basis. See 81 [I-D.ietf-manet-dlep-da-credit-extension] for a DiffServ-based 82 version of credit window flow control. 84 This document uses the traffic classification and credit window 85 control mechanisms defined in 86 [I-D.ietf-manet-dlep-traffic-classification] and 87 [I-D.ietf-manet-dlep-credit-flow-control] to provide credit window 88 based flow control based on DLEP destinations and Ethernet VLANs and 89 Priority Code Points. Ethernet Priority Code Point support is 90 defined as part of the IEEE 802.1Q [IEEE.802.1Q_2014] tag format and 91 includes a 3 bit "PCP" field. The tag format also includes a 12 bit 92 VLAN identifier (VID) field. The defined mechanism allows for credit 93 windows to be shared across traffic sent to multiple DLEP 94 destinations, VLANs, and PCPs, or used exclusively for traffic sent 95 to a particular destination and/or VLAN and/or PCP. The extension 96 also supports the "wildcard" matching of any PCP or VID. 98 The extension defined in this document is referred to as "IEEE 802.1Q 99 Aware Credit Window" or, more simply, the "Ethernet Credit" 100 extension. The reader should be familiar with both the traffic 101 classification and credit window control mechanisms defined in 102 [I-D.ietf-manet-dlep-traffic-classification] and 103 [I-D.ietf-manet-dlep-credit-flow-control]. 105 This document defines a new DLEP Extension Type Value in Section 2 106 which is used to indicate support for the extension. 108 1.1. Key Words 110 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 111 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 112 "OPTIONAL" in this document are to be interpreted as described in BCP 113 14 [RFC2119] [RFC8174] when, and only when, they appear in all 114 capitals, as shown here. 116 2. Extension Usage and Identification 118 The extension defined in this document is composed of the mechanisms 119 and processing defined in 120 [I-D.ietf-manet-dlep-traffic-classification] and 121 [I-D.ietf-manet-dlep-credit-flow-control]. To indicate that the IEEE 122 802.1Q Aware Credit Window Extension is to be used, an implementation 123 MUST include the IEEE 802.1Q Aware Credit Window Type Value in the 124 Extensions Supported Data Item. The Extensions Supported Data Item 125 is sent and processed according to [RFC8175]. Any implementation 126 that indicates use of the IEEE 802.1Q Aware Credit Window Extension 127 MUST support all Messages, Data Items, the Ethernet Traffic 128 Classification Sub-Data Item, and all related processing defined in 129 [I-D.ietf-manet-dlep-traffic-classification] and 130 [I-D.ietf-manet-dlep-credit-flow-control]. 132 The IEEE 802.1Q Aware Credit Window Extension Type Value is TBA1, see 133 Section 5. 135 3. Management Considerations 137 This section provides several network management guidelines to 138 implementations supporting the IEEE 802.1Q Aware Credit Window 139 Extension. 141 The use of the extension defined in this document SHOULD be 142 configurable on both modems and routers. 144 Modems SHOULD support the configuration of PCP to credit window 145 (queue) mapping. 147 Modems MAY support the configuration of PCP to credit window (queue) 148 mapping on a per VLAN basis. Note that VID value of zero (0) is used 149 by [I-D.ietf-manet-dlep-traffic-classification] to indicate that VID 150 is ignored and any VID value is used in traffic classification. 152 When VLANs are supported by a modem without support from PCPs, the 153 modem SHOULD support the configuration of VLAN to credit window 154 (queue) mapping. 156 Modems MAY support the configuration of the number of credit windows 157 (queues) to advertise to a router. 159 Routers may have limits on the number of queues that they can support 160 and, perhaps, even limits in supported credit window combinations, 161 e.g., if per destination queues can even be supported at all. When 162 modem-provided credit window information exceeds the capabilities of 163 a router, the router MAY use a subset of the provided credit windows. 164 Alternatively, a router MAY reset the session and indicate that the 165 extension is not supported. In either case, the mismatch of 166 capabilities SHOULD be reported to the user via normal network 167 management mechanisms, e.g., user interface or error logging. 169 4. Security Considerations 171 This document defines a DLEP extension that uses base DLEP mechanisms 172 and the credit window control and flow mechanisms defined in 173 [I-D.ietf-manet-dlep-traffic-classification] and 174 [I-D.ietf-manet-dlep-credit-flow-control]. The use of those 175 mechanisms, and the introduction of a new extension, do not 176 inherently introduce any additional vulnerabilities above those 177 documented in [RFC8175]. The approach taken to Security in that 178 document applies equally to the mechanism defined in this document. 180 5. IANA Considerations 182 This document requests one assignment by IANA. All assignments are 183 to registries defined by [RFC8175]. 185 5.1. Extension Type Value 187 This document requests 1 new assignment to the DLEP Extensions 188 Registry named "Extension Type Values" in the range with the 189 "Specification Required" policy. The requested value is as follows: 191 +======+=================================+ 192 | Code | Description | 193 +======+=================================+ 194 | TBA1 | IEEE 802.1Q Aware Credit Window | 195 +------+---------------------------------+ 197 Table 1: Requested Extension Type Value 199 6. References 201 6.1. Normative References 203 [I-D.ietf-manet-dlep-credit-flow-control] 204 Cheng, B., Wiggins, D., Berger, L., and S. Ratliff, "DLEP 205 Credit-Based Flow Control Messages and Data Items", Work 206 in Progress, Internet-Draft, draft-ietf-manet-dlep-credit- 207 flow-control-09, 26 October 2021, 208 . 211 [I-D.ietf-manet-dlep-traffic-classification] 212 Cheng, B., Wiggins, D., and L. Berger, "DLEP Traffic 213 Classification Data Item", Work in Progress, Internet- 214 Draft, draft-ietf-manet-dlep-traffic-classification-06, 29 215 July 2021, . 218 [IEEE.802.1Q_2014] 219 IEEE, "IEEE Standard for Local and metropolitan area 220 networks--Bridges and Bridged Networks", IEEE 802.1Q-2014, 221 DOI 10.1109/ieeestd.2014.6991462, 18 December 2014, 222 . 225 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 226 Requirement Levels", BCP 14, RFC 2119, 227 DOI 10.17487/RFC2119, March 1997, 228 . 230 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 231 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 232 May 2017, . 234 [RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B. 235 Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175, 236 DOI 10.17487/RFC8175, June 2017, 237 . 239 6.2. Informative References 241 [I-D.ietf-manet-dlep-da-credit-extension] 242 Cheng, B., Wiggins, D., and L. Berger, "DLEP DiffServ 243 Aware Credit Window Extension", Work in Progress, 244 Internet-Draft, draft-ietf-manet-dlep-da-credit-extension- 245 12, 29 July 2021, . 248 Appendix A. Acknowledgments 250 The document was motivated by discussions in the MANET working group. 251 Many useful comments were received from contributors to the MANET 252 working group, notably Ronald in't Velt. 254 Authors' Addresses 256 David Wiggins 257 MIT Lincoln Laboratory 258 Massachusetts Institute of Technology 259 244 Wood Street 260 Lexington 261 Email: David.Wiggins@ll.mit.edu 263 Lou Berger 264 LabN Consulting, L.L.C. 265 Email: lberger@labn.net