idnits 2.17.1 draft-rogge-manet-dlep-radio-band-03.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 752 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 Band Extension 8 draft-rogge-manet-dlep-radio-band-03 10 Abstract 12 This document defines an extension to the Dynamic Link Exchange 13 Protocol (DLEP) to provide the frequency bands used by the radio. 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 Band Data Item . . . . . . . . . . . . . . . . . . . . 2 52 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 53 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 54 5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 4 55 5.2. Data Item Value . . . . . . . . . . . . . . . . . . . . . 4 56 6. Normative References . . . . . . . . . . . . . . . . . . . . 5 57 7. Informative References . . . . . . . . . . . . . . . . . . . 5 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 60 1. Introduction 62 The dynamic Link Exchange Protocol (DLEP) is defined in [RFC8175]. 63 It provides the exchange of link-related control information between 64 DLEP peers. DLEP peers are comprised of a modem and a router. DLEP 65 defines a base set of mechanisms as well as support for possible 66 extensions. This document defines one such extension. 68 1.1. Requirements Language 70 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 71 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 72 document are to be interpreted as described in [RFC2119]. 74 2. Extension Usage and Identification 76 The use of the Radio Band Extension SHOULD be configurable. To 77 indicate that the Radio Band Extension is to be used, an 78 implementation MUST include the Radio Band Extension Type Value in 79 the Extensions Supported Data Item. The Extensions Supported Data 80 Item is sent and processed according to [RFC8175]. 82 The Radio Band Extension Type Value is TBD; see Section TBD. 84 3. Radio Band Data Item 86 Radio Band Data Item contains information which radio frequency 87 resources are being used. These values are usually interface 88 specific and static during the DLEP session. 90 The Radio Band Data Item can be used multiple times to represent 91 multiple radio bands. 93 The Item can be used in a neighbor specific message if the radio use 94 dedicated subcarriers to talk to neighbors. 96 The information in this Item gives the router an easy way to 97 calculate the spectral efficiency of a radio link, how much bandwidth 98 is used for the current data-rate reported by DLEP. This can be 99 integrated into the routing metric to focus traffic on links that use 100 the spectrum efficiently. 102 The Item can also be used as an interface to a cognitive radio 103 controller on the router, analyzing the correlation of transmission 104 disruptions with the frequency bands and could (together with the 105 Request Link Characteristics message) be used to change the frequency 106 of the radio in a standardized way. 108 The format of the Radio Band Data Item is: 110 0 1 2 3 111 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 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | Data Item Type | Length | 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 | Carrier Frequency | 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 | Carrier Frequency | 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 | Bandwidth | 120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 121 | Bandwidth | 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 | Flags | 124 +-+-+-+-+-+-+-+-+ 126 Figure 1 128 Data Item Type: TBD 130 Length: 17 132 Center Frequency: The center frequency of the band in Hz. 134 Bandwidth: The bandwidth of the band in Hz. 136 Flags: Flags field as defined below. 138 The Flags field is defined as: 140 0 1 2 3 4 5 6 7 141 +-+-+-+-+-+-+-+-+ 142 | Reserved |U|D| 143 +-+-+-+-+-+-+-+-+ 145 Figure 2 147 U: Uplink Flag, indicating the band is used for transmitting data. 149 D: Downlink Flag, indicating the band is used for receiving data. 151 Reserved: MUST be zero. Left for future assignment. 153 4. Security Considerations 155 The extension introduces a new Data Item for DLEP. The extension 156 does not inherently introduce any additional vulnerabilities above 157 those documented in [RFC8175]. The approach taken to security in 158 that document applies equally when running the extension defined in 159 this document. 161 5. IANA Considerations 163 As described below, IANA has assigned two values per this document. 164 Both assignments are to registries defined by [RFC8175]. 166 5.1. Extension Type Value 168 IANA has assigned the following value in the "Extension Type Values" 169 registry within the "Dynamic Link Exchange Protocol (DLEP) 170 Parameters" registry. The new value is in the range with the 171 "Specification Required" [RFC8126] policy: 173 +------+-------------+ 174 | Code | Description | 175 +------+-------------+ 176 | TBD | Radio Band | 177 +------+-------------+ 179 Table 1: New Extension 180 Type Value 182 5.2. Data Item Value 184 IANA has assigned the following value in the "Data Item Type Values" 185 registry within the "Dynamic Link Exchange Protocol (DLEP) 186 Parameters" registry. The new value is in the range with the 187 "Specification Required" [RFC8126] policy: 189 +-----------+-------------+ 190 | Type Code | Description | 191 +-----------+-------------+ 192 | TBD | Radio Band | 193 +-----------+-------------+ 195 Table 2: New Data Item 196 Value 198 6. Normative References 200 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 201 Requirement Levels", BCP 14, RFC 2119, 202 DOI 10.17487/RFC2119, March 1997, 203 . 205 [RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B. 206 Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175, 207 DOI 10.17487/RFC8175, June 2017, 208 . 210 7. Informative References 212 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 213 Writing an IANA Considerations Section in RFCs", BCP 26, 214 RFC 8126, DOI 10.17487/RFC8126, June 2017, 215 . 217 Author's Address 219 Henning Rogge 220 Fraunhofer FKIE 221 Fraunhofer Strasse 20 222 53343 Wachtberg 223 Germany 224 Email: henning.rogge@fkie.fraunhofer.de