Internet-Draft | DLEP Channel Utilization | February 2021 |
Rogge | Expires 5 August 2021 | [Page] |
This document defines an extension to the Dynamic Link Exchange Protocol (DLEP) to provide the utilization of a radio channel.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 5 August 2021.¶
Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
The dynamic Link Exchange Protocol (DLEP) is defined in [RFC8175]. It provides the exchange of link-related control information between DLEP peers. DLEP peers are comprised of a modem and a router. DLEP defines a base set of mechanisms as well as support for possible extensions. This document defines one such extension.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].¶
The use of the Channel Utilization Extension SHOULD be configurable. To indicate that the Channel Utilization Extension is to be used, an implementation MUST include the Radio Channel Active and Radio Channel Busy Value in the Extensions Supported Data Item. The Extensions Supported Data Item is sent and processed according to [RFC8175].¶
The Radio Band Extension Type Value is TBD; see Section TBD.¶
Radio Channel Active Item is mandatory and contains information how long the radio channel has been active. This value is usually interface specific.¶
The value in this item must be larger than the values in the other three Data Items this extensions define together.¶
The format of the Radio Channel Active Data Item is:¶
Radio Channel Busy Item is mandatory and contains information how much time the radio channel has been busy but has not been, not including the time in the Channel Rx and Chanel Tx Data Item. This value is usually interface specific.¶
The value in the Channel Active item must be larger than the values in the other three Data Items this extensions define together.¶
The format of the Radio Channel Busy Data Item is:¶
Radio Channel Rx Item is optional and contains information how much time the local radio has been receiving data from other radios. This value is usually interface specific.¶
The value in the Channel Active item must be larger than the values in the other three Data Items this extensions define together.¶
The format of the Radio Channel Rx Data Item is:¶
Radio Channel Tx Item is optional and contains information how much time the local radio has been transmitting data to other radios. This value is usually interface specific.¶
The value in the Channel Active item must be larger than the values in the other three Data Items this extensions define together.¶
The format of the Radio Channel Tx Data Item is:¶
The extension introduces a new Data Item for DLEP. The extension does not inherently introduce any additional vulnerabilities above those documented in [RFC8175]. The approach taken to security in that document applies equally when running the extension defined in this document.¶
As described below, IANA has assigned two values per this document. Both assignments are to registries defined by [RFC8175].¶
IANA has assigned the following value in the "Extension Type Values" registry within the "Dynamic Link Exchange Protocol (DLEP) Parameters" registry. The new value is in the range with the "Specification Required" [RFC8126] policy:¶
Code | Description |
TBD | Radio Channel Utilization |
IANA has assigned the following value in the "Data Item Type Values" registry within the "Dynamic Link Exchange Protocol (DLEP) Parameters" registry. The new value is in the range with the "Specification Required" [RFC8126] policy:¶
Type Code | Description |
TBD | Radio Channel Active |
TBD | Radio Channel busy |
TBD | Radio Channel Rx |
TBD | Radio Channel Tx |