[Search] [txt|html|xml|pdf|bibtex] [Tracker] [Email] [Nits]

Versions: 00 01                                                         
Manet                                                         H.R. Rogge
Internet-Draft                                           Fraunhofer FKIE
Intended status: Standards Track                         1 February 2021
Expires: 5 August 2021


                DLEP Radio Channel Utilization Extension
             draft-rogge-manet-dlep-channel-utilization-00

Abstract

   This document defines an extension to the Dynamic Link Exchange
   Protocol (DLEP) to provide the utilization of a radio channel.

Status of This Memo

   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 Notice

   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.







Rogge                     Expires 5 August 2021                 [Page 1]


Internet-Draft          DLEP Channel Utilization           February 2021


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Extension Usage and Identification  . . . . . . . . . . . . .   2
   3.  Radio Channel Active Data Item  . . . . . . . . . . . . . . .   2
   4.  Radio Channel Busy Data Item  . . . . . . . . . . . . . . . .   3
   5.  Radio Channel Rx Data Item  . . . . . . . . . . . . . . . . .   4
   6.  Radio Channel Tx Data Item  . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Extension Type Value  . . . . . . . . . . . . . . . . . .   5
     8.2.  Data Item Value . . . . . . . . . . . . . . . . . . . . .   6
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   10. Informative References  . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   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.

1.1.  Requirements Language

   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].

2.  Extension Usage and Identification

   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.

3.  Radio Channel Active Data Item

   Radio Channel Active Item is mandatory and contains information how
   long the radio channel has been active.  This value is usually
   interface specific.




Rogge                     Expires 5 August 2021                 [Page 2]


Internet-Draft          DLEP Channel Utilization           February 2021


   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:

   0                   1                   2                   3
   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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Data Item Type                | Length                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                          Active Time                          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                          Active Time                          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                                  Figure 1

   Data Item Type:  TBD

   Length:  8

   Active Time:  Time in nanoseconds since the channel has been active.

4.  Radio Channel Busy Data Item

   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:

   0                   1                   2                   3
   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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Data Item Type                | Length                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           Busy Time                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           Busy Time                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                                  Figure 2

   Data Item Type:  TBD



Rogge                     Expires 5 August 2021                 [Page 3]


Internet-Draft          DLEP Channel Utilization           February 2021


   Length:  8

   Busy Time:  Time in nanoseconds the channel was busy during its
      active time.

5.  Radio Channel Rx Data Item

   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:

   0                   1                   2                   3
   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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Data Item Type                | Length                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                            Rx Time                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                            Rx Time                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                                  Figure 3

   Data Item Type:  TBD

   Length:  8

   Rx Time:  Time in nanoseconds the local radio was receiving data from
      other radios during its active time.

6.  Radio Channel Tx Data Item

   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:






Rogge                     Expires 5 August 2021                 [Page 4]


Internet-Draft          DLEP Channel Utilization           February 2021


   0                   1                   2                   3
   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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Data Item Type                | Length                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                            Tx Time                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                            Tx Time                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                                  Figure 4

   Data Item Type:  TBD

   Length:  8

   Tx Time:  Time in nanoseconds the local radio was transmitting data
      to other radios during its active time.

7.  Security Considerations

   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.

8.  IANA Considerations

   As described below, IANA has assigned two values per this document.
   Both assignments are to registries defined by [RFC8175].

8.1.  Extension Type Value

   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 |
                   +------+---------------------------+

                    Table 1: New Extension Type Value





Rogge                     Expires 5 August 2021                 [Page 5]


Internet-Draft          DLEP Channel Utilization           February 2021


8.2.  Data Item Value

   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     |
                   +-----------+----------------------+

                       Table 2: New Data Item Value

9.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC8175]  Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B.
              Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175,
              DOI 10.17487/RFC8175, June 2017,
              <https://www.rfc-editor.org/info/rfc8175>.

10.  Informative References

   [RFC8126]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for
              Writing an IANA Considerations Section in RFCs", BCP 26,
              RFC 8126, DOI 10.17487/RFC8126, June 2017,
              <https://www.rfc-editor.org/info/rfc8126>.

Author's Address

   Henning Rogge
   Fraunhofer FKIE
   Fraunhofer Strasse 20
   53343 Wachtberg
   Germany




Rogge                     Expires 5 August 2021                 [Page 6]


Internet-Draft          DLEP Channel Utilization           February 2021


   Email: henning.rogge@fkie.fraunhofer.de


















































Rogge                     Expires 5 August 2021                 [Page 7]