idnits 2.17.1 draft-rogge-manet-dlep-radio-quality-02.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 (7 March 2022) is 779 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 7 March 2022 5 Expires: 8 September 2022 7 DLEP Radio Quality Extension 8 draft-rogge-manet-dlep-radio-quality-02 10 Abstract 12 This document defines an extension to the Dynamic Link Exchange 13 Protocol (DLEP) to provide the quality of incoming radio signals. 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 8 September 2022. 32 Copyright Notice 34 Copyright (c) 2022 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 Revised BSD License text as 43 described in Section 4.e of the Trust Legal Provisions and are 44 provided without warranty as described in the Revised 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 Quality Data Items . . . . . . . . . . . . . . . . . . 2 52 3.1. Radio SNR Data Item . . . . . . . . . . . . . . . . . . . 3 53 3.2. Radio Signal Strength Data Item (also called RSSI) . . . 4 54 3.3. Radio Biterror Rate Data Item . . . . . . . . . . . . . . 4 55 3.4. Radio Noise Data Item . . . . . . . . . . . . . . . . . . 5 56 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 57 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 58 5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 6 59 5.2. Data Item Value . . . . . . . . . . . . . . . . . . . . . 6 60 6. Normative References . . . . . . . . . . . . . . . . . . . . 6 61 7. Informative References . . . . . . . . . . . . . . . . . . . 7 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 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 1.1. Requirements Language 74 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 75 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 76 document are to be interpreted as described in [RFC2119]. 78 2. Extension Usage and Identification 80 The use of the Radio Quality Extension SHOULD be configurable. To 81 indicate that the Radio Quality Extension is to be used, an 82 implementation MUST include the Radio Quality Extension Type Value in 83 the Extensions Supported Data Item. The Extensions Supported Data 84 Item is sent and processed according to [RFC8175]. 86 The Radio Quality Extension Type Value is TBD; see Section TBD. 88 3. Radio Quality Data Items 90 This section describes the quality related Data Items of this 91 extension. 93 All Data Items available in this extension provide access to the 94 radios physical layer measurements related to signal quality. 95 Because of different designs of Radio PHY layers, this quality can be 96 expressed in different ways, by referring to signal-to-noise ratio or 97 by measuring the biterror rate (e.g. by using a forward error 98 correction). Both of these possible informations are very valuable 99 for calculating MANET metrics for radio networks with moving nodes 100 and low datarates, e.g. VHF radio networks. Estimating channel 101 quality based on packet loss can be impractical, because the 102 estimated value changes too fast (because of movement) compared to 103 the number of received frames. Signal Strength (or Biterror rate) 104 can provice the additional information necessary to build a 105 reasonable stable and agile metric. 107 3.1. Radio SNR Data Item 109 Radio SNR Data Item contains information which signal to noise ratio 110 the radio measured. This Data Item can be both interface and 111 neighbor specific. 113 The format of the Radio SNR Data Item is: 115 0 1 2 3 116 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 117 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 118 | Data Item Type | Length | 119 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 120 | SNR | Flags | 121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 Figure 1 125 Data Item Type: TBD 127 Length: 3 129 SNR: SNR measured in dB multiplied by 10 as a signed integer. 131 Flags: Flags field as defined below. 133 The Flags field is defined as: 135 0 1 2 3 4 5 6 7 136 +-+-+-+-+-+-+-+-+ 137 | Reserved |I| 138 +-+-+-+-+-+-+-+-+ 140 Figure 2 142 I: Interference Flag, indicating the the data includes interference 143 into the noise value (SINR). 145 Reserved: MUST be zero. Left for future assignment. 147 3.2. Radio Signal Strength Data Item (also called RSSI) 149 Radio Signal Strength Data Item contains information which absolute 150 signal strength the radio measured. This Data Item can be both 151 interface and neighbor specific. 153 This Data Item could also be used together with the Request Link 154 Characteristics message to reconfigure the outgoing signal strength, 155 either to reduce the size of the collision domain or to increase the 156 range of the radio. 158 The format of the Radio Signal Strength Data Item is: 160 0 1 2 3 161 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 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 | Data Item Type | Length | 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | Signal | 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 168 Figure 3 170 Data Item Type: TBD 172 Length: 2 174 Signal: Signal Strength measured in dBm multiplied by 10 as a signed 175 integer. 177 3.3. Radio Biterror Rate Data Item 179 Radio Biterror Rate Data Item contains information which absolute 180 noise value the radio measured. This Data Item can be both interface 181 and neighbor specific. 183 The format of the Radio Biterror Rate Data Item is: 185 0 1 2 3 186 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 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 | Data Item Type | Length | 189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 190 | Biterror | 191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 Figure 4 195 Data Item Type: TBD 197 Length: 1 199 Biterror: Biterror rate measured as a negative exponent to base 10, 200 e.g. "4" for an error rate of 1 to 10^-4. An error rate of 0 is 201 encoded with a 255. 203 3.4. Radio Noise Data Item 205 Radio Noise Data Item contains information which absolute noise value 206 the radio measured. This Data Item SHOULD be interface specific. 208 The format of the Radio Noise Data Item is: 210 0 1 2 3 211 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 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 | Data Item Type | Length | 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 | Noise | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 218 Figure 5 220 Data Item Type: TBD 222 Length: 2 224 Noise: Noise measured in dBm multiplied by 10 as a signed integer. 226 4. Security Considerations 228 The extension introduces a new Data Item for DLEP. The extension 229 does not inherently introduce any additional vulnerabilities above 230 those documented in [RFC8175]. The approach taken to security in 231 that document applies equally when running the extension defined in 232 this document. 234 5. IANA Considerations 236 As described below, IANA has assigned two values per this document. 237 Both assignments are to registries defined by [RFC8175]. 239 5.1. Extension Type Value 241 IANA has assigned the following value in the "Extension Type Values" 242 registry within the "Dynamic Link Exchange Protocol (DLEP) 243 Parameters" registry. The new value is in the range with the 244 "Specification Required" [RFC8126] policy: 246 +------+---------------+ 247 | Code | Description | 248 +------+---------------+ 249 | TBD | Radio Quality | 250 +------+---------------+ 252 Table 1: New Extension 253 Type Value 255 5.2. Data Item Value 257 IANA has assigned the following value in the "Data Item Type Values" 258 registry within the "Dynamic Link Exchange Protocol (DLEP) 259 Parameters" registry. The new value is in the range with the 260 "Specification Required" [RFC8126] policy: 262 +-----------+---------------------+ 263 | Type Code | Description | 264 +-----------+---------------------+ 265 | TBD | Radio SNR | 266 +-----------+---------------------+ 267 | TBD | Radio Signal | 268 +-----------+---------------------+ 269 | TBD | Radio Biterror Rate | 270 +-----------+---------------------+ 271 | TBD | Radio Noise | 272 +-----------+---------------------+ 274 Table 2: New Data Item Value 276 6. Normative References 278 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 279 Requirement Levels", BCP 14, RFC 2119, 280 DOI 10.17487/RFC2119, March 1997, 281 . 283 [RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B. 284 Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175, 285 DOI 10.17487/RFC8175, June 2017, 286 . 288 7. Informative References 290 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 291 Writing an IANA Considerations Section in RFCs", BCP 26, 292 RFC 8126, DOI 10.17487/RFC8126, June 2017, 293 . 295 Author's Address 297 Henning Rogge 298 Fraunhofer FKIE 299 Fraunhofer Strasse 20 300 53343 Wachtberg 301 Germany 302 Email: henning.rogge@fkie.fraunhofer.de