idnits 2.17.1 draft-rogge-manet-dlep-radio-quality-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 (9 August 2021) is 991 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 9 August 2021 5 Expires: 10 February 2022 7 DLEP Radio Quality Extension 8 draft-rogge-manet-dlep-radio-quality-01 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 10 February 2022. 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 Quality Data Items . . . . . . . . . . . . . . . . . . 2 52 3.1. Radio SNR Data Item . . . . . . . . . . . . . . . . . . . 3 53 3.2. Radio Signal Strength Data Item (also called RSSI) . . . 3 54 3.3. Radio Biterror Rate Data Item . . . . . . . . . . . . . . 4 55 3.4. Radio Noise Data Item . . . . . . . . . . . . . . . . . . 4 56 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 57 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 58 5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 5 59 5.2. Data Item Value . . . . . . . . . . . . . . . . . . . . . 6 60 6. Normative References . . . . . . . . . . . . . . . . . . . . 6 61 7. Informative References . . . . . . . . . . . . . . . . . . . 6 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 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 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 3.1. Radio SNR Data Item 95 Radio SNR Data Item contains information which signal to noise ratio 96 the radio measured. This Data Item can be both interface and 97 neighbor specific. 99 The format of the Radio SNR Data Item is: 101 0 1 2 3 102 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 103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 104 | Data Item Type | Length | 105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 106 | SNR | Flags | 107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 Figure 1 111 Data Item Type: TBD 113 Length: 3 115 SNR: SNR measured in dB multiplied by 10 as a signed integer. 117 Flags: Flags field as defined below. 119 The Flags field is defined as: 121 0 1 2 3 4 5 6 7 122 +-+-+-+-+-+-+-+-+ 123 | Reserved |I| 124 +-+-+-+-+-+-+-+-+ 126 Figure 2 128 I: Interverence Flag, indicating the the data includes interference 129 into the noise value (SINR). 131 Reserved: MUST be zero. Left for future assignment. 133 3.2. Radio Signal Strength Data Item (also called RSSI) 135 Radio Signal Strength Data Item contains information which absolute 136 signal strength the radio measured. This Data Item can be both 137 interface and neighbor specific. 139 The format of the Radio Signal Strength Data Item is: 141 0 1 2 3 142 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 143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 144 | Data Item Type | Length | 145 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 146 | Signal | 147 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 149 Figure 3 151 Data Item Type: TBD 153 Length: 2 155 Signal: Signal Strength measured in dBm multiplied by 10 as a signed 156 integer. 158 3.3. Radio Biterror Rate Data Item 160 Radio Biterror Rate Data Item contains information which absolute 161 noise value the radio measured. This Data Item can be both interface 162 and neighbor specific. 164 The format of the Radio Biterror Rate Data Item is: 166 0 1 2 3 167 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 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 169 | Data Item Type | Length | 170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 | Biterror | 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 174 Figure 4 176 Data Item Type: TBD 178 Length: 1 180 Biterror: Biterror rate measured as a negative exponent to base 10, 181 e.g. "4" for an error rate of 1 to 10^-4. An error rate of 0 is 182 encoded with a 255. 184 3.4. Radio Noise Data Item 186 Radio Noise Data Item contains information which absolute noise value 187 the radio measured. This Data Item SHOULD be interface. 189 The format of the Radio Noise Data Item is: 191 0 1 2 3 192 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 193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 194 | Data Item Type | Length | 195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 196 | Noise | 197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 Figure 5 201 Data Item Type: TBD 203 Length: 2 205 Noise: Noise measured in dBm multiplied by 10 as a signed integer. 207 4. 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 5. IANA Considerations 217 As described below, IANA has assigned two values per this document. 218 Both assignments are to registries defined by [RFC8175]. 220 5.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 Quality | 231 +------+---------------+ 233 Table 1: New Extension 234 Type Value 236 5.2. Data Item Value 238 IANA has assigned the following value in the "Data Item Type Values" 239 registry within the "Dynamic Link Exchange Protocol (DLEP) 240 Parameters" registry. The new value is in the range with the 241 "Specification Required" [RFC8126] policy: 243 +-----------+---------------------+ 244 | Type Code | Description | 245 +-----------+---------------------+ 246 | TBD | Radio SNR | 247 +-----------+---------------------+ 248 | TBD | Radio Signal | 249 +-----------+---------------------+ 250 | TBD | Radio Biterror Rate | 251 +-----------+---------------------+ 252 | TBD | Radio Noise | 253 +-----------+---------------------+ 255 Table 2: New Data Item Value 257 6. Normative References 259 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 260 Requirement Levels", BCP 14, RFC 2119, 261 DOI 10.17487/RFC2119, March 1997, 262 . 264 [RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B. 265 Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175, 266 DOI 10.17487/RFC8175, June 2017, 267 . 269 7. Informative References 271 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 272 Writing an IANA Considerations Section in RFCs", BCP 26, 273 RFC 8126, DOI 10.17487/RFC8126, June 2017, 274 . 276 Author's Address 278 Henning Rogge 279 Fraunhofer FKIE 280 Fraunhofer Strasse 20 281 53343 Wachtberg 282 Germany 283 Email: henning.rogge@fkie.fraunhofer.de