DLEP Radio Band ExtensionFraunhofer FKIEFraunhofer Strasse 20Wachtberg53343DEhenning.rogge@fkie.fraunhofer.de
Routing
ManetDLEPPHYTLVThis document defines an extension to the Dynamic Link Exchange Protocol (DLEP) to provide the bands used by the radio, their signal strength and their usage statistics.IntroductionThe dynamic Link Exchange Protocol (DLEP) is defined in
.
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.Requirements LanguageThe 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 .Extension Usage and IdentificationThe use of the Radio Band Extension SHOULD be
configurable. To indicate that the Radio Band Extension
is to be used, an implementation MUST include the Radio Band
Extension Type Value in the Extensions Supported Data Item. The Extensions Supported Data Item is sent and processed according to
.The Radio Band Extension Type Value is TBD; see Section TBD.Radio Band Data ItemRadio Band Data Item contains information which radio frequency resources
are being used. These values are interface specific and usually static during the DLEP session.The Radio Band Data Item can be used multiple times to represent multiple radio bandsThe format of the Radio Band Data Item is:
Data Item Type:
TBD
Length:
17
Center Frequency:
The center frequency of the band in Hz.
Bandwidth:
The bandwidth of the band in Hz.
Flags:
Flags field as defined below.
The Flags field is defined as:
U:
Uplink Flag, indicating the band is used for transmitting data.
D:
Downlink Flag, indicating the band is used for receiving data.
Reserved:
MUST be zero. Left for future assignment.
Security ConsiderationsThe extension introduces a new Data Item for DLEP.
The extension does not inherently introduce any additional
vulnerabilities above those documented in
.
The approach taken to security in that document applies
equally when running the extension defined in this document.IANA ConsiderationsAs described below, IANA has assigned two values per this document.
Both assignments are to registries defined by
.Extension Type ValueIANA 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" policy:
New Extension Type Value
Code
Description
TBD
Radio Band
Data Item ValueIANA 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"
policy:
New Data Item Value
Type Code
Description
TBD
Radio Band
Normative ReferencesKey words for use in RFCs to Indicate Requirement LevelsIn many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.Dynamic Link Exchange Protocol (DLEP)When routing devices rely on modems to effect communications over wireless links, they need timely and accurate knowledge of the characteristics of the link (speed, state, etc.) in order to make routing decisions. In mobile or other environments where these characteristics change frequently, manual configurations or the inference of state through routing or transport protocols does not allow the router to make the best decisions. This document introduces a new protocol called the Dynamic Link Exchange Protocol (DLEP), which provides a bidirectional, event-driven communication channel between the router and the modem to facilitate communication of changing link characteristics.Informative ReferencesGuidelines for Writing an IANA Considerations Section in RFCsMany protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.This is the third edition of this document; it obsoletes RFC 5226.