idnits 2.17.1 draft-rogge-manet-dlep-channel-utilization-00.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 (1 February 2021) is 1170 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Manet H.R. Rogge 3 Internet-Draft Fraunhofer FKIE 4 Intended status: Standards Track 1 February 2021 5 Expires: 5 August 2021 7 DLEP Radio Channel Utilization Extension 8 draft-rogge-manet-dlep-channel-utilization-00 10 Abstract 12 This document defines an extension to the Dynamic Link Exchange 13 Protocol (DLEP) to provide the utilization of a radio channel. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at https://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on 5 August 2021. 32 Copyright Notice 34 Copyright (c) 2021 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 39 license-info) in effect on the date of publication of this document. 40 Please review these documents carefully, as they describe your rights 41 and restrictions with respect to this document. Code Components 42 extracted from this document must include Simplified BSD License text 43 as described in Section 4.e of the Trust Legal Provisions and are 44 provided without warranty as described in the Simplified BSD License. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 49 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 50 2. Extension Usage and Identification . . . . . . . . . . . . . 2 51 3. Radio Channel Active Data Item . . . . . . . . . . . . . . . 2 52 4. Radio Channel Busy Data Item . . . . . . . . . . . . . . . . 3 53 5. Radio Channel Rx Data Item . . . . . . . . . . . . . . . . . 4 54 6. Radio Channel Tx Data Item . . . . . . . . . . . . . . . . . 4 55 7. Security Considerations . . . . . . . . . . . . . . . . . . . 5 56 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 57 8.1. Extension Type Value . . . . . . . . . . . . . . . . . . 5 58 8.2. Data Item Value . . . . . . . . . . . . . . . . . . . . . 6 59 9. Normative References . . . . . . . . . . . . . . . . . . . . 6 60 10. Informative References . . . . . . . . . . . . . . . . . . . 6 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 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 1.1. Requirements Language 73 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 74 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 75 document are to be interpreted as described in [RFC2119]. 77 2. Extension Usage and Identification 79 The use of the Channel Utilization Extension SHOULD be configurable. 80 To indicate that the Channel Utilization Extension is to be used, an 81 implementation MUST include the Radio Channel Active and Radio 82 Channel Busy Value in the Extensions Supported Data Item. The 83 Extensions Supported Data Item is sent and processed according to 84 [RFC8175]. 86 The Radio Band Extension Type Value is TBD; see Section TBD. 88 3. Radio Channel Active Data Item 90 Radio Channel Active Item is mandatory and contains information how 91 long the radio channel has been active. This value is usually 92 interface specific. 94 The value in this item must be larger than the values in the other 95 three Data Items this extensions define together. 97 The format of the Radio Channel Active Data Item is: 99 0 1 2 3 100 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 101 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 102 | Data Item Type | Length | 103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 104 | Active Time | 105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 106 | Active Time | 107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 Figure 1 111 Data Item Type: TBD 113 Length: 8 115 Active Time: Time in nanoseconds since the channel has been active. 117 4. Radio Channel Busy Data Item 119 Radio Channel Busy Item is mandatory and contains information how 120 much time the radio channel has been busy but has not been, not 121 including the time in the Channel Rx and Chanel Tx Data Item. This 122 value is usually interface specific. 124 The value in the Channel Active item must be larger than the values 125 in the other three Data Items this extensions define together. 127 The format of the Radio Channel Busy Data Item is: 129 0 1 2 3 130 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 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 | Data Item Type | Length | 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | Busy Time | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | Busy Time | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 Figure 2 141 Data Item Type: TBD 142 Length: 8 144 Busy Time: Time in nanoseconds the channel was busy during its 145 active time. 147 5. Radio Channel Rx Data Item 149 Radio Channel Rx Item is optional and contains information how much 150 time the local radio has been receiving data from other radios. This 151 value is usually interface specific. 153 The value in the Channel Active item must be larger than the values 154 in the other three Data Items this extensions define together. 156 The format of the Radio Channel Rx Data Item is: 158 0 1 2 3 159 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 160 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 161 | Data Item Type | Length | 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 | Rx Time | 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | Rx Time | 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 168 Figure 3 170 Data Item Type: TBD 172 Length: 8 174 Rx Time: Time in nanoseconds the local radio was receiving data from 175 other radios during its active time. 177 6. Radio Channel Tx Data Item 179 Radio Channel Tx Item is optional and contains information how much 180 time the local radio has been transmitting data to other radios. 181 This value is usually interface specific. 183 The value in the Channel Active item must be larger than the values 184 in the other three Data Items this extensions define together. 186 The format of the Radio Channel Tx Data Item is: 188 0 1 2 3 189 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 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 | Data Item Type | Length | 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | Tx Time | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | Tx Time | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 198 Figure 4 200 Data Item Type: TBD 202 Length: 8 204 Tx Time: Time in nanoseconds the local radio was transmitting data 205 to other radios during its active time. 207 7. Security Considerations 209 The extension introduces a new Data Item for DLEP. The extension 210 does not inherently introduce any additional vulnerabilities above 211 those documented in [RFC8175]. The approach taken to security in 212 that document applies equally when running the extension defined in 213 this document. 215 8. IANA Considerations 217 As described below, IANA has assigned two values per this document. 218 Both assignments are to registries defined by [RFC8175]. 220 8.1. Extension Type Value 222 IANA has assigned the following value in the "Extension Type Values" 223 registry within the "Dynamic Link Exchange Protocol (DLEP) 224 Parameters" registry. The new value is in the range with the 225 "Specification Required" [RFC8126] policy: 227 +------+---------------------------+ 228 | Code | Description | 229 +------+---------------------------+ 230 | TBD | Radio Channel Utilization | 231 +------+---------------------------+ 233 Table 1: New Extension Type Value 235 8.2. Data Item Value 237 IANA has assigned the following value in the "Data Item Type Values" 238 registry within the "Dynamic Link Exchange Protocol (DLEP) 239 Parameters" registry. The new value is in the range with the 240 "Specification Required" [RFC8126] policy: 242 +-----------+----------------------+ 243 | Type Code | Description | 244 +-----------+----------------------+ 245 | TBD | Radio Channel Active | 246 +-----------+----------------------+ 247 | TBD | Radio Channel busy | 248 +-----------+----------------------+ 249 | TBD | Radio Channel Rx | 250 +-----------+----------------------+ 251 | TBD | Radio Channel Tx | 252 +-----------+----------------------+ 254 Table 2: New Data Item Value 256 9. Normative References 258 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 259 Requirement Levels", BCP 14, RFC 2119, 260 DOI 10.17487/RFC2119, March 1997, 261 . 263 [RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B. 264 Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175, 265 DOI 10.17487/RFC8175, June 2017, 266 . 268 10. Informative References 270 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 271 Writing an IANA Considerations Section in RFCs", BCP 26, 272 RFC 8126, DOI 10.17487/RFC8126, June 2017, 273 . 275 Author's Address 277 Henning Rogge 278 Fraunhofer FKIE 279 Fraunhofer Strasse 20 280 53343 Wachtberg 281 Germany 282 Email: henning.rogge@fkie.fraunhofer.de